Ja, ich suche eine Lösung
Hi All,
We have a Quantum Superloader 3 tape library (LTO 6) running Backup Exec 2012 (SP2) Windows Server 2008 R2 SP1
Incremental jobs for 34 servers run nightly at 11pm to the incremental media set (infinite - Allow append).
These backups are consitent in that they backup successfully up until the following point of failure:
After approximately one month of usage, I noticed that one of the incremental tapes had become
'Not Appendable (End marker unreadable)'
Checking through the forums lead me to investigate further and work through the following:
- check backup exec job engine service (bengine.exe) around time media failed (couldn't locate any instances of the service state starting / stopping that could have caused this)
- run live update (SP2 Installed)
- check memory errors
- check scsi controller drivers to address soft write errors (also run the cleaning tape job)
- check windows update
- firmware on tapedrive
- symantec tape drivers up to date
- run long erase on tape (approximately 7 hours / long erase)
Since everything was up to date and none of the windows logs coincided with the last backup run before the errors, I decided to perform the suggestion of duplicating the data to disk and re-duplicating it back to tape after running a long erase. I was able to duplicate the unappendable tape contents to the disk, but after running the following duplicate job from the disk back to a new (empty) tape within the same incremental media set, I receive the following error:
"Completed status: CanceledThe job was canceled because the response to a media request alert was Cancel, or because the alert was configured to automatically respond with Cancel, or because the Backup Exec Job Engine service was stopped."
I am only copying approximately 150 GB to a 2.38 TB drive and it fails every time at the same 5.10 GB point. Some of the data from a few servers is able to copy over to the tape but it alway halts with the above message after 5.10 GB progress.
I ran the Backup Exec Debug Monitor (SGMon.exe) on the duplicate back to tape job and received the following output: (See http://pastebin.com/r1nkqQq0)
It looks like the tape media is constantly performing a dismount / re-mount function on the same tape prior to the error:
PVLSVR: [09/10/13 12:30:45] [4408] AdammSession::DismountMedia()Session = {A5502617-E052-49C4-9E00-A09491FF9FCE}Library = {B0354312-0329-4389-A540-7DD7A18E3332}, "Robotic library 0001"Slot = 0004Drive = {E40F4367-F09B-4613-B6A4-5DCCB7EC4818}, "Tape drive 0001"Media = {C557A4F3-9BDC-43D6-AAB7-875A71D989EB}, "05"Side = 0001
The last message I see is the following (though it still appears earlier in the log):
BESERVER: [09/10/13 12:32:08] [0340] "Cluster" key is not present in the registryBESERVER: [09/10/13 12:32:08] [0340] Did not detect Microsoft cluster ()BESERVER: [09/10/13 12:32:08] [0340] VCS cluster keys do not appear to be present in the registryBESERVER: [09/10/13 12:32:08] [0340] Did not detect VCS cluster ()
My main concern at the moment is getting the job to duplicate back to the empty tape so we are able to retain our incremental data. Thanks in advance.