I am backing up to a Western Digital network drive (via Ethernet LAN), but my Time Machine won't run automatically. Whenever I run it manually from the status bar, selecting Back Up Now it fails with the following error message:
Time Machine couldn't complete the backup to "DeviceName".
The backup disk is not available.
However, if I open Time Machine Preferences, right click on the disk and select Back Up Now, the backup runs just fine.
I tried removing / adding the drive, ⌥ alt/option + ⌃ ctrl + Click on the drive and Verify Backups but I still get this error, and I don't understand why Back Up Now behaves differently depending on how it was executed?
Edit following @AllInOne comment: when I backup from the status bar, I get the following messages in the console:
10/1/13 9:23:04.857 AM com.apple.backupd: Starting manual backup
10/1/13 9:23:05.275 AM com.apple.backupd: Backup failed with error: 19
Backing up from Time Machine Preferences first mounts the disk:
10/1/13 9:34:39.473 AM com.apple.backupd: Starting manual backup
10/1/13 9:34:39.523 AM com.apple.backupd: Attempting to mount network destination URL: afp://[email protected]/WD_Backup
10/1/13 9:34:45.000 AM kernel: ASP_TCP CheckReqQueueSize: increasing req queue from 32 to 128 entries. so 0xffffff804ab26b80
10/1/13 9:35:02.486 AM com.apple.backupd: Mounted network destination at mount point: /Volumes/WD_Backup using URL: afp://[email protected]/WD_Backup
10/1/13 9:35:02.000 AM kernel: AFP_VFS afpfs_mount: /Volumes/WD_Backup, pid 37105
10/1/13 9:35:02.000 AM kernel: AFP_VFS afpfs_mount : succeeded on volume 0xffffff8271491008 /Volumes/WD_Backup (error = 0, retval = 0)
10/1/13 9:35:45.297 AM com.apple.backupd: Disk image /Volumes/WD_Backup/lindinglab_XR_iMac.sparsebundle mounted at: /Volumes/Time Machine Backups 1 10/1/13 9:35:45.308 AM com.apple.backupd: Backing up to: /Volumes/Time Machine Backups 1/Backups.backupdb
However even if I mount the disk beforehand (for instance from the Finder, Go, Connect to server and enter its address), Back Up Now in the status bar still fails with the same message (including in the console).