What follows is a list of Yosemite Server Backup errors that I have encountered while using the software, along with a few notes or comments from me. Maybe they will be useful to you, and maybe not. I'm not intending on being your tech support, but was always frustrated that there wasn't a whole lot on the Internet talking about these.
In the future, I hope to get more of a page set up where others can add errors and the fixes or workarounds that they know.
The file probably existed while creating the backup list, and then was deleted before being backed up. Linux filesystems seem to give error 3020. Can also be seen in the Media Maintenance of a virtual library if a media file is missing.
Unknown if this is talking about a particular file, or the virtual media files.
There was a problem writing a to the backup device for some reason. Once seen when the virtual library file had error 208 during a backup.
The server or some device closed a connection.
"Yosemite Server Backup is unable to connect to a remote host."
Seen when some part of the program can not connect to another machine, or the connection was lost in the middle.
Seen once when I rebooted a server for Windows Updates while it was in the middle of a backup.
Seen when you cancel a job.
I believe that this is the error that is given when I am trying to backup a computer that normally gives error 5093, but have "safely removed the device" from the computer beforehand. It does not matter if I am using the device in the backup job or not.
Probably similar to error 16, although the whole directory the file used to be in was gone instead.
Unknown what caused this error.
Unknown.
Seen when an alert showed that it could not find the media (since the tape was not in the drive). Upon hitting cancel on that alert, the job failed with this error. Can also see this error with virtual media if the virtual library is offline.
You need to insert a tape into your tape drive. If you are dealing with virtual libraries, then this can be seen sometimes if the device has gone offline since the job started (although sometimes other error messages are shown instead depending on exactly when it went offline).
An incorrect tape is in your tape drive. If using virtual media, then an incorrect media is "loaded" in the virtual "device". For removeable media, it could be set to have multiple sets and does not want to overwrite the prior media.
Probably seen when the server was told to reboot, but a job was in progress. Also seen when a running job is stopped.
This file was not backed up since it was locked by another process.
Possibly seen during backups if the file existed when the backup list was created, but did not exist by the time the process got around to trying to back it up. The file then gets counted as "Not attempted". See also error 16, which seems to be the same type of error for Windows filesystems.
Seen when trying to backup WMI Repository (part of the System State). Never saw it again.
Can see this message if you try to view the properties of a virtual library while the virtual library is in use by a backup or restore job. From the description: "The current task cannot use the device because the device is in use by another task."
Seen on a tape drive where the tape or drive was going bad. Eventually turned into error 4075.
The tape is write protected, or in my case, the USB drive was having a little trouble and thought it was write protected.
Seen during a restore. The virtual media may be corrupt. Looking at the file identifiers for the virtual media, I saw that I actually had about 70 files (1 GB each) but the library was listing it as a 2 GB media in the media maintenance. I disassociated the media and then associated it and it correctly showed the larger size. Running the restore again worked without a problem.
Seen when the virtual library was out of available disk space.
Usually accompanied with another error as well. From the description: "The operation has stopped because an error has occurred while reading or writing data which the drive cannot correct."
Your tape is bad. From the description: "Your data is at risk: 1. Copy any data you require from this tape. 2. Do not use this tape again. 3. Restart the operation with a different tape."
Seen in conjunction with errors 4074 and 4075. From the description: "The tape is from a faulty batch or the tape drive is faulty: 1. Use a good tape to test the drive. 2. If the problem persists, call the tape drive supplier helpline."
The manual eject button on the tape drive was pushed while this job was still in progress. From the description: "You cannot eject the cartridge because the tape drive is in use. Wait until the operation is complete before ejecting the cartridge."
Seen on a file when the job returned error 4409. Also seen on a job with an overall error 18. Also seen on a job with an overall error 4436.
This one is no fun. Probably means that your backup is corrupted. You could maybe try a repair in the devices area if it's a virtual media, not sure how it works for actual tapes.
Either the object changed between being backed up and being verified, or your media may be going bad.
Saw this error while trying to repair a virtual media that had error 16. From the description: "A read or open operation has failed on the selected virtual media extent file."
Seen in the virtual library maintenance area. Running a repair appeared to fix this error several times (although I have not tested it beyond that).
I have seen this when trying to repair a virtual media that had error 16. From the description: "A failure occurred during a read operation of the virtual library device inventory control file."
Seen during a repair of a virtual media that had error 4434.
Seen while trying to repair some virtual media that had error 16. From the description: "The repair process failed to repair the virtual media because there are no extent files present to operate on."
A repair did not seem to work at first (failed with error 4431), but did on another media with the same error. Have also seen error 4435 when trying to repair this error.
After disassociating some virtual media with this (4434) error, it changed to error 4426 (and the size it listed for the virtual media changed). A repair then appeared to work and I could reassociate the media.
Seen when trying to repair some degraded virtual media with error 4434. From the description: "The virtual library device is reporting a internal error. Please contact support for assistance in resolving this error."
Seen during backing up to virtual media. Unknown was causes it.
Seen while trying to delete some "Foreign, Degraded" virtual media with error 16. From the description: "It is likely that this file is in use by another process, or the file no longer exists."
Seen with a virtual library, although I cannot remember the circumstances of making this happen.
Yosemite Server Backup was unable to create a Disaster Recovery boot image because the WinPE files have not been installed on this machine.
Other files are still backed up with this error message, just not a Disaster Recovery boot image.
Unknown.
Probably talking about the VSS writers on this Windows XP machine. I seem to recall reading somewhere that Windows XP only allows one snapshot to be created at a time, where the Windows Server versions allow more. I could be remembering wrong though. A reboot of the machine throwing the error seems to fix this problem, although perhaps you could just check and make sure two backup jobs (that use VSS, like System State) aren't trying to run at the same time.
I see this error on Windows Server 2003, and error 5094 on Windows Server 2008 and 2008 R2.
On Windows, the VSS services returned an error when asked to make a snapshot. Also, oddly enough, VSS will throw back errors consistently if you have a large USB hard drive plugged into the computer.* You don't even have to be using it for your backup, just being plugged in is enough.
*Maybe someday I will go dig up the link, but people were talking about how Windows expects a default sector size of 512 bytes, but some of these larger hard drives don't use that and it causes VSS to fail -- and therefore Yosemite won't back up that computer. Seen on Windows Server 2003, 2008, and 2008 R2. I haven't tested Windows Server Backup (the built-in backup program with Server 2008) to see if it would also have troubles trying to use the VSS writers.
Last updated: 2012-02-06