gearbox Posted October 1, 2007 Report Share Posted October 1, 2007 I tried searching and found the bad backup set header troubleshooter, but it hasn't helped yet. Here's a quick rundown: PMG4 Quicksilver running 10.4.5, and Retrospect 6.1.126, using an Atto UL3S card, VXA-3 packetloader 1x10, and the fanciest cable and terminator that Granite Digital sells. This machine backs up an XServe G4 and a windows box over the network. A user came to me looking for a restore of some files that were deleted, but when I try to add snapshots in the snapshot viewer, it ruminates for a little while, fails, and the log gives me: Bad backup set header found (0xc0ff5c8e at 819,283,969). Can't retrieve Snapshot, general error. The numbers are different depending on which set and which snapshot I try, but I get them no matter what set and snapshot I've tried so far. I don't think anything is wrong with my drive, because the backups have been running nightly without complaint, and do verify successfully, and I am able to restore from the most current snapshot (default one in the viewer) even though its contents span back several tapes worth. The current snapshot doesn't help me of course, since it was made after the files went missing. I did try using the catalog rebuild, which claims to run successfully but doesn't fix the problem. Any ideas? Link to comment Share on other sites More sharing options...
rhwalker Posted October 1, 2007 Report Share Posted October 1, 2007 Are you using a relatively recent RDU? What shows in Configure > Devices, Device Status, for the drivers? We have an Xserve G5 with ATTO UL4D driving our VXA-2 1x10 1u PacketLoader (SCSI), and I've never seen this. Our retrospect drivers show as: Exabyte library: 5.03 Exabyte VXA DC: 5.05 You are aware that Exabyte issued recent firmware updates for its drives and autoloader, aren't you? You don't mention firmware versions. Russ Link to comment Share on other sites More sharing options...
CallMeDave Posted October 1, 2007 Report Share Posted October 1, 2007 Quote: The current snapshot doesn't help me of course, since it was made after the files went missing. In the meantime, can you find the file(s) you're looking for through a Searching restore? That operation does not use Snapshots at all, and might satisfy your user's need while you troubleshoot what's going on with the other issue. Dave Link to comment Share on other sites More sharing options...
gearbox Posted October 1, 2007 Author Report Share Posted October 1, 2007 My RDU and VXA firmware were out of date, but now they're patched up and the problem persists. It's very weird, I can restore with no problem from the snapshots that appear in the initial list for each set, including older snapshots that were added in the past using the add snapshot button, but when I try to add any more I get the failure. The searching restore didn't work because the users aren't coherent enough about the file names to be of use... it's a whole folder that's gone missing, and the folder name is generic enough that there are hundreds with the same name scattered around various project folders. Link to comment Share on other sites More sharing options...
CallMeDave Posted October 1, 2007 Report Share Posted October 1, 2007 Quote: I did try using the catalog rebuild, which claims to run successfully but doesn't fix the problem. Claimed? If you Rebuild the catalog, you'd know it, as otherwise you wouldn't have a catalog available to use! Two ways I would proceed: # Update one of your more current backup copies of your Catalog file: - Move the current Catalog file to a different location then where you generally store your catalogs. - Forget the Backup Set from the Backup Set database. - Copy over a recent backup of the Catalog file at issue (it's a critically valuable data file; you've been making backup copies of it all along, I hope). - Tools -> Repair -> Update existing catalog file -> More -> Open -> YourCatalog - Feed tapes as requested If that doesn't work, # Rebuild your Catalog file from scratch: - Move the current Catalog file to a different location then where you generally store your catalogs. - Forget the Backup Set from the Backup Set database. - Tools -> Repair -> Rebuild from tapes. - Save your Catalog to an appropriate location. - Feed tapes as requested Dave Link to comment Share on other sites More sharing options...
gearbox Posted October 2, 2007 Author Report Share Posted October 2, 2007 Ah, it was actually update existing I was using, not a full-on rebuild. That's something to try. How likely is it that the catalogs for three different backup sets are all bad though? Link to comment Share on other sites More sharing options...
rhwalker Posted October 2, 2007 Report Share Posted October 2, 2007 There's always the possibility that there is some corruption in the Retrospect preferences that is causing this. Have you had any crashes while backing up? Link to comment Share on other sites More sharing options...
gearbox Posted October 2, 2007 Author Report Share Posted October 2, 2007 Crashes while backing up? Doesn't everybody? Actually it's been pretty stable for some time now, though it does occasionally die. I can't remember if it's died during a backup on any of the current sets, but I'm pretty sure it hasn't done it on all of them. Link to comment Share on other sites More sharing options...
rhwalker Posted October 2, 2007 Report Share Posted October 2, 2007 Quote: Crashes while backing up? Doesn't everybody? No, not everybody. Last crash our server had was March 2006, when Retrospect's device scan prior to backup caused, I believe, a SCSI transfer to be aborted on the OS boot volume on the same SCSI channel. It was hard to track down the cause, because it only happened once every few days, but the workaround was to move Retrospect's tape drive (Exabyte VXA-2 1x10 1u PacketLoader (SCSI)) to its own SCSI channel. No issue since. Not that Retrospect doesn't have its issues.... Link to comment Share on other sites More sharing options...
CallMeDave Posted October 2, 2007 Report Share Posted October 2, 2007 Quote: There's always the possibility that there is some corruption in the Retrospect preferences that is causing this. This would certainly be a good tack to take in advance of rebuilding catalogs. It would have been helpful to note more specifically that this was happening with multiple Backup Sets (additional study of the second post reveals "each set," which I missed on first read). - Start Retrospect with the preference file removed from /Library/Preferences/Retrospect/ - Enter license information when prompted - Configure -> Catalogs -> More -> Open... -> YourCatalogFile -> Snapshots -> Add -> Retrieve Any difference in behavior? Dave Link to comment Share on other sites More sharing options...
gearbox Posted October 5, 2007 Author Report Share Posted October 5, 2007 Tried ditching the preferences, and reopening the catalog files, but that failed in the same manner. I'm going to run a full rebuild of one of the sets over the weekend and see where it gets me. Link to comment Share on other sites More sharing options...
gearbox Posted October 8, 2007 Author Report Share Posted October 8, 2007 Rebuild failed, I got this: + Executing Recatalog at 10/5/2007 11:57 AM To backup set XServe Daily A V5… Bad backup set header found (0x69006e00 at 204,800). Backup set format inconsistency (4 at 205312) Bad backup set header found (0x03a6bb81 at 410,112). Backup set format inconsistency (4 at 410624) Bad backup set header found (0x61ffec7c at 615,424). Backup set format inconsistency (4 at 615936) Bad backup set header found (0xf9610188 at 820,736). Backup set format inconsistency (4 at 821248) Bad backup set header found (0xc5b4c9c7 at 1,026,048). Backup set format inconsistency (4 at 1026560) Bad backup set header found (0x58f53b27 at 1,231,360). Backup set format inconsistency (4 at 1231872) Bad backup set header found (0x1b7e8331 at 1,436,672). Backup set format inconsistency (4 at 1437184) Bad backup set header found (0xfdd43ad2 at 1,641,984). Backup set format inconsistency (4 at 1642496) Bad backup set header found (0x73817481 at 1,847,310). Backup set format inconsistency (4 at 1847808) Bad backup set header found (0x32303722 at 2,052,608). Backup set format inconsistency (4 at 2053120) Bad backup set header found (0x22207661 at 2,257,920). Backup set format inconsistency (4 at 2258432) Bad backup set header found (0x02660274 at 2,463,242). Backup set format inconsistency (4 at 2463744) Bad backup set header found (0x72756c65 at 2,668,544). Backup set format inconsistency (4 at 2669056) Bad backup set header found (0x2b122f0a at 2,873,856). Backup set format inconsistency (4 at 2874368) Bad backup set header found (0x4b494847 at 3,079,168). Backup set format inconsistency (4 at 3079680) Bad backup set header found (0x38210060 at 3,284,480). Backup set format inconsistency (4 at 3284992) Bad backup set header found (0x80010114 at 3,489,792). Backup set format inconsistency (4 at 3490304) Bad backup set header found (0x7104003b at 3,695,104). Backup set format inconsistency (4 at 3695616) Bad backup set header found (0x98dc81ff at 3,900,416). Backup set format inconsistency (4 at 3900928) Bad backup set header found (0x8009000c at 4,105,728). Backup set format inconsistency (4 at 4106240) Bad backup set header found (0x23464646 at 4,311,042). Backup set format inconsistency (4 at 4311552) Bad backup set header found (0x73cea36b at 4,516,352). Backup set format inconsistency (4 at 4516864) Bad backup set header found (0xb1e2d6d5 at 4,721,664). Backup set format inconsistency (4 at 4722176) Backup set format inconsistency (5 at 4722272) Trouble positioning: “1-XServe Daily A V5” (0), error 109 (unexpected filemark or FTP end of file). 10/5/2007 12:13:39 PM: Execution incomplete. Completed: 479 files, 4.7 GB Performance: 355.0 MB/minute Duration: 00:15:43 (00:02:10 idle/loading/preparing) Link to comment Share on other sites More sharing options...
CallMeDave Posted October 8, 2007 Report Share Posted October 8, 2007 This sort of error generally points to a problem with the physical media. But in your case, as you are seeing the same problem with multiple sets of media, it's possible the the drive itself is causing the problem. Still, a tech support incident purchase with EMC might be a good use of funds at this point. Dave Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.