Time Machine error 19 - but backups not failing

Question

Level 2

152 points

Time Machine error 19 - but backups not failing

My Time Machine backups consistently say "Backup failed with error: 19" -- but the backups aren't ultimately failing. I wouldn't even know about it if I hadn't seen the errors in Console, because the backups then proceed to complete successfully. (I tried restoring an item from a backup, and it worked....)

I back up to 2 external HDs, and this happens with both of them every time (both with hourly and manual backups).

I recently upgraded to Mountain Lion; I don't know if it was happening before.

My question: What should I do? Of course it's not good to have errors, but if the backups are working, should I still do a full reset of Time Machine or something? Would it cause any problems to try "removing disk" in System Preferences and then re-adding them?

Thank you.

iMac

Posted on Apr 19, 2013 11:28 AM

Reply

Answer 1

Linc Davis

Level 10

209,547 points

Apr 19, 2013 12:22 PM in response to DonnaR

If you have more than one user account, these instructions must be carried out as an administrator.

Launch the Console application in any of the following ways:

☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

☞ Open LaunchPad. Click Utilities, then Console in the icon grid.

Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select

View ▹ Show Log List

from the menu bar.

Enter the word "Starting" (without the quotes) in the String Matching text field. You should now see log messages with the words "Starting * backup," where * represents any of the words "automatic," "manual," or "standard." Note the timestamp of the last such message. Clear the text field and scroll back in the log to that time. Select the messages timestamped from then until the end of the backup, or the end of the log if that's not clear. Copy them (command-C) to the Clipboard. Paste (command-V) into a reply to this message.

If there are runs of repeated messages, post only one example of each. Don't post many repetitions of the same message.

When posting a log extract, be selective. Don't post more than is requested.

Please do not indiscriminately dump thousands of lines from the log into this discussion.

Some personal information, such as the names of your files, may be included — anonymize before posting.

Reply

Answer 2

DonnaR Author

Level 2

152 points

Apr 19, 2013 1:29 PM in response to Linc Davis

Thank you, Linc.

Before posting the log, I want to add that I tried changing the name of my computer in System Preferences / Sharing (per Pondini's advice to another posting), but that didn't help.

In the log below, I changed the names of the computer and the user. Did I leave in any personal info that I should have deleted? ... Thanks again in advance.

So, the log:

Apr 19 15:38:36 my-iMac.local com.apple.backupd[379]: Starting manual backup

Apr 19 15:38:36 my-iMac.local com.apple.SecurityServer[19]: Succeeded authorizing right 'com.apple.ServiceManagement.daemons.modify'

Apr 19 15:38:37 --- last message repeated 1 time ---

Apr 19 15:38:37 my-iMac.local com.apple.backupd[379]: Backup failed with error: 19

Apr 19 15:38:37 my-iMac.local com.apple.backupd[379]: Starting manual backup

Apr 19 15:38:37 my-iMac.local com.apple.SecurityServer[19]: Succeeded authorizing right 'com.apple.ServiceManagement.daemons.modify'

Apr 19 15:38:37 my-iMac.local com.apple.backupd[379]: Backing up to: /Volumes/First Passport/Backups.backupdb

Apr 19 15:38:37 my-iMac.local com.apple.SecurityServer[19]: Succeeded authorizing right 'com.apple.ServiceManagement.daemons.modify'

Apr 19 15:38:38 my-iMac.local com.apple.backupd[379]: Using file event preflight for Collins' HD

Apr 19 15:38:39 my-iMac.local com.apple.backupd[379]: Will copy (22.8 MB) from Collins' HD

Apr 19 15:38:39 my-iMac.local com.apple.backupd[379]: Found 287 files (22.8 MB) needing backup

Apr 19 15:38:39 my-iMac.local com.apple.backupd[379]: 782.7 MB required (including padding), 903.48 GB available

Apr 19 15:38:48 my-iMac.local distnoted[385]: # distnote server agent absolute time: 487.502554890 civil time: Fri Apr 19 15:38:48 2013 root: no

Apr 19 15:38:54 my-iMac.local sandboxd[389] ([388]): mdworker(388) deny file-write-owner /Users/kc/Library/Containers/com.apple.Notes/Data/Library/Notes/NotesV1.storeda ta-walplugin:/Library/Spotlight/Notes.mdimporter - find suspect file using: sudo mdutil -t

Apr 19 15:38:54 my-iMac kernel[0]: Sandbox: sandboxd(389) deny mach-lookup com.apple.coresymbolicationd

Apr 19 15:38:54 my-iMac.local sandboxd[389] ([388]): mdworker(388) deny file-write-owner /Users/kc/Library/Containers/com.apple.Notes/Data/Library/Notes/NotesV1.storeda ta-shmplugin:/Library/Spotlight/Notes.mdimporter - find suspect file using: sudo mdutil -t

Apr 19 15:39:04 my-iMac.local com.apple.SecurityServer[19]: Session 100014 created

Apr 19 15:39:05 my-iMac.local com.apple.backupd[379]: Copied 2013 files (23 MB) from volume Collins' HD.

Apr 19 15:39:05 my-iMac.local com.apple.backupd[379]: Using file event preflight for Collins' HD

Apr 19 15:39:05 my-iMac.local com.apple.backupd[379]: Will copy (Zero KB) from Collins' HD

Apr 19 15:39:05 my-iMac.local com.apple.backupd[379]: Found 10 files (Zero KB) needing backup

Apr 19 15:39:05 my-iMac.local com.apple.backupd[379]: 755.3 MB required (including padding), 903.45 GB available

Apr 19 15:39:08 my-Mac.local com.apple.backupd[379]: Copied 809 files (93 bytes) from volume Collins' HD.

Apr 19 15:39:08 my-iMac.local com.apple.SecurityServer[19]: Succeeded authorizing right 'com.apple.ServiceManagement.daemons.modify'

Apr 19 15:39:08 my-iMac.local com.apple.backupd[379]: Created new backup: 2013-04-19-153908

Apr 19 15:39:09 my-iMac.local com.apple.backupd[379]: Starting post-backup thinning

Apr 19 15:39:09 my-iMac.local com.apple.backupd[379]: No post-back up thinning needed: no expired backups exist

Apr 19 15:39:09 my-Mac.local com.apple.SecurityServer[19]: Succeeded authorizing right 'com.apple.ServiceManagement.daemons.modify'

Apr 19 15:39:09 my-iMac.local com.apple.backupd[379]: Backup completed successfully.

Reply

Answer 3

Linc Davis

Level 10

209,547 points

Apr 19, 2013 10:50 PM in response to DonnaR

That log extract shows two attempts at manual backup. The first one failed because the backup volume was offline. The second, immediately following, succeeded. It seems that your backup drive is failing intermittently. I suggest you immediately start a new backup on another external drive. You need more than one backup to be safe anyway.

Reply

Answer 4

DonnaR Author

Level 2

152 points

Apr 20, 2013 4:36 AM in response to Linc Davis

I actually only chose "Back Up Now" once during that time; i.e., that log entry was the result of one manual backup attempt (the volume was online -- the icon was green). Backup always fails with error 19, but then proceeds to complete successfully.

Also, I back up to 2 external HDs (rotating each week). I looked at the logs for both, and the same thing happens with both.

Thanks for any input!

Reply

Answer 5

Linc Davis

Level 10

209,547 points

Apr 20, 2013 8:00 AM in response to DonnaR

Are these drives connected through a hub?

Reply

Answer 6

DonnaR Author

Level 2

152 points

Apr 20, 2013 8:27 AM in response to Linc Davis

No, they're connected directly to the computer through FireWire. Since I only have 1 FireWire port, I rotate them.

Reply

Answer 7

Linc Davis

Level 10

209,547 points

Apr 20, 2013 9:31 AM in response to DonnaR

If you're using the same data cable with both drives, use another one. If the drives are bus-powered but can also run off an AC adapter, connect the adapter. If the drives have a USB interface, use that to connect them. See whether there's any change.

Reply

Answer 8

DonnaR Author

Level 2

152 points

Apr 20, 2013 11:24 AM in response to Linc Davis

That's an excellent idea.

So I tried switching to a USB cable instead of FireWire -- same error 19. Also, each drive has its own FireWire cable, and the error happens with both FireWire cables. One hard drive came with (and runs off) an AC adapter, and one doesn't.

Thanks again for your interest in my case and your willingness to brainstorm about it!

Reply

Answer 9

Linc Davis

Level 10

209,547 points

Apr 20, 2013 11:38 AM in response to DonnaR

Please read this whole message before doing anything.

This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.

The purpose of the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login, or by a peripheral device.

Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards. Boot in safe mode and log in to the account with the problem. Note: If FileVault is enabled, or if a firmware password is set, or if the boot volume is a software RAID, you can’t do this. Post for further instructions.

Safe mode is much slower to boot and run than normal, and some things won’t work at all, including wireless networking on certain Macs. The next normal boot may also be somewhat slow.

The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.

Test while in safe mode. Same problem?

After testing, reboot as usual (i.e., not in safe mode) and verify that you still have the problem. Post the results of the test.

Reply

Answer 10

DonnaR Author

Level 2

152 points

Apr 21, 2013 7:44 AM in response to Linc Davis

Thank you so much for your time on this.

I disconnected peripherals (my printer and an iPod) and booted in Safe Mode, but unfortunately I still got the same error 19! Also, after rebooting, the log file looks the same as before.

I wanted to change the title of this discussion -- I think it's a bit misleading, because my backups do say they're "failing" at first. But based on the title, other people with the same problem in the future may not read it. Since I can't edit the title, I'm posting another discussion (with the title I want) with a link to this one.

Reply

Answer 11

Linc Davis

Level 10

209,547 points

Apr 21, 2013 9:54 AM in response to DonnaR

Boot into Recovery by holding down the key combination command-R at the startup chime. Release the keys when you see a gray screen with a spinning dial.

Note: You need an always-on Ethernet or Wi-Fi connection to the Internet to use Recovery. It won’t work with USB or PPPoE modems, or with proxy servers, or with networks that require a certificate for authentication.

When the OS X Utilities screen appears, follow the prompts to reinstall the OS. You don't need to erase the boot volume, and you won't need your backup unless something goes wrong. If your Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade, so make a note of those before you begin.

Reply

Answer 12

DonnaR Author

Level 2

152 points

Apr 23, 2013 12:30 PM in response to Linc Davis

The solution was surprising -- it ended up not being a problem after all! Turns out that Time Machine was looking for whichever drive hadn't been backed up to most recently, but because I rotate the 2 drives, it wasn't there. So Time Machine would give an error message and then proceed to back up to whichever drive was available.

More details at:

https://discussions.apple.com/thread/4987826?answerId=21854717022#21854717022&ac_cid=op123456#21854717

Reply

Answer 13

Linc Davis

Level 10

209,547 points

Apr 23, 2013 12:44 PM in response to DonnaR

I see. There's no need to rotate the drives yourself, unless you want to keep one of them off-site (which is a good thing to do.) TM does that automatically.

Reply