Jump to content

greggerman

Members
  • Content count

    15
  • Joined

  • Last visited

Community Reputation

0 Neutral

About greggerman

  • Rank
    Newbie
  1. I'm trying to rebuild my Retrospect 6 backup sets so that I can access them in Retrospect 9. These old sets are on LTO-3 tape media that I access via a Quantum SuperLoader 3 with 16 tape slots and an LTO-5 drive. I'm using an Xserve running OS X Server 10.6.8. I've seen the directions in the Read Me file for Retrospect 9, but it doesn't specifically address how it works for tapes. Here's what I've tried: 1) Create a new Media Set 2) Click on Rebuild 3) It asks what type of media set I'd like to rebuild. I choose Tape, Removable, or Optical and click Next... 4) At this point it says Select a device. I cannot directly select the set members at this point. I can see them in the tape library, but I can only select one at a time, and even when I select just one, the Next... button remains greyed out. So what does it mean for me to select? I've tried selecting the top level device "Quantum Library", the drive itself "Quantum Ultrium 5 DC", the slot in that drive (currently empty), and the tape library "Library slots 1to 16". I'll attach a screenshot that shows exactly what I just described... 5) It then asks me to select a folder for the new Catalog. I select a location, but no matter which choice I made in step 4, when I press Rebuild I immediately get an error stating "An error occurred". I don't know what I'm missing. Can anyone help here? I'll gladly provide more information if needed...
  2. I have Retrospect 9.0.0 (319) Multi Server w/Unlimited Clients installed on an Xserve running OS X 10.5.8 Server. We back up our user machines using a Proactive Backup script. It's working generally quite well, but I have one issue I'd like to address. In the Clients panel of Retrospect Preferences, the "Backup on demand to" and "Restore on demand" choices are greyed out and can't be selected. All of the choices above that are selectable and are in fact selected. Any ideas as to why the "on demand" choices are unavailable? Thanks in advance...
  3. In version 6 you can look at the contents of any particular backup and export said contents in a tab-delimited text format. I haven't been able to figure out how to do this in version 8. Is it possible?
  4. With this in mind, I decided to install a trial version of Retrospect 8 on my server and redo the archive. It worked without a hitch! This indicates to me that Retrospect 6 is the problem. And since development on v6 is dead, it's probably time to upgrade to v8. There may be a way to get v6 to work again, but I'm tired of fighting with it...
  5. Our autoloader is the only SCSI device connected to the ATTO UL5D, so it is on it's own channel. That sounds like a good idea. I'll try that soon. Now that I think about it, we started having this issue when the server was running OS X 10.4.11, so it's doubtful that 10.5.7 has anything to do with my problem. I would guess that this is not an issue with the Quantum drive. As I mentioned, we had the autoloader replaced with a new one after the issue surfaced, and it hasn't made any difference. Also, Quantum's diagnostic tools are Windows only (boo hiss!), so I can't run them anyhow. Thanks for your suggestions, Russ!
  6. I have a Quantum tape library and I'm having problems archiving with Retrospect. It gets through the writing portion fine, but it fails in the verification stage. I have tried re-verifying several times and it always fails. Basically, the verify will go up to a certain point, but never the same point, and then just stall. If I go look at the tape library, I can see that the activity light has stopped blinking, meaning the drive is no longer reading data. If I wait long enough, Retrospect will eventually error out and say that the verification failed and show which files were not verified. At this point, Retrospect can no longer communicate with the tape library. So I have to force quit Retrospect and reboot both the server and the tape library before they will communicate again. Yes, more configuration details of course... CONFIGURATION Server: Xserve 2 x 2.0 GHz Dual-Core Intel Xeon, 4 GB RAM OS: OS X Server 10.5.8 SCSI Card: ATTO ExpressPCI UL5D, Driver Version 4.40, Flash Bundle Version 2009_04_10 Retrospect version 6.1.230, Driver Update Version 6.1.16.100 Autoloader: Quantum SuperLoader 3 tape library (LTO-3 Half-Height SCSI Tape Drive), Library Firmware V61, Drive Firmware V2181 Note: All above versions are the latest available. SPECIFICS OF ARCHIVE I was attempting to archive about 800 GB of data from a fibre attached Xsan 1.4.2 volume. The data definitely finished writing, but fails on verification. I should also note that this is not an isolated incident. I noticed a little while back that my nightly backups were always failing in the verification stage. I didn't have time to deal with it at the time, so I just turned off verification in my backup script. But clearly, an archive cannot be considered complete without verification. This setup used to work fine for a couple of years (with earlier versions of all of the drivers and software), but started behaving badly while I was addressing a hardware issue with the Quantum tape drive (which has since been replaced). In assessing the problem, I began upgrading software and drivers and it has never worked properly since. I have tried reverting to the last known working state, but I neglected to write down the firmware version of the tape drive, so I wouldn't know which version to revert to, even if Quantum made older versions available. RETROSPECT LOG + Executing Verify at 10/8/2009 5:05 PM To backup set Summer 09 Archive… Trouble reading: “1-Summer 09 Archive†(2160271), error 205 (lost access to storage medium). 1140 files were not verified. 10/8/2009 7:21:35 PM: Execution incomplete. Remaining: 1140 files, 687.0 GB Completed: 2284 files, 131.9 GB Performance: 992.8 MB/minute Duration: 02:16:05 (00:00:07 idle/loading/preparing) Quit at 10/8/2009 8:42 PM SYSTEM LOG Whenever I want to look at the tape library through Retrospect (Configure > Devices), I start to get a steady stream of the following message: 10/9/09 11:54:20 AM kernel SCSITaskUserClient - Invalid arguments: scatterGatherEntries = 1, requestedTransferCount = 0, transferDirection is 0 This continues until I leave that screen. The same message reappears about 5 or 6 times when I start the verify process in Retrospect. I haven't seen anything in the system logs that seems to correspond to verification failure. WRAPPING IT UP I have read on this forum that error 205 points to a SCSI issue. I have replaced both the SCSI cable and terminator, and even tried it without a terminator, all to no avail. I have also seen some things in the Retrospect 8 forum that mention the above SCSITaskUserClient error and that it had something to do with the Mac OS X 10.5.7 update. But I don't know if this also applies to Retrospect 6, or if it even has anything to do with my issue. I'm in quite a bind here, as my SAN is filling up and I need to remove some data, but I can't until I can verify that it has been archived. Any ideas or tips would be appreciated. Thanks!
  7. greggerman

    Backup fails during verification

    I can confirm that both the firmware and drivers for the UL5D have been updated to the latest version. ATTO provides an installer package that takes care of both. And it requires that you restart after installation. I'm not sure that I can actually do that. The only archived version that ATTO still provides is 4.3.2, and I was on 4.3.1. And even if I could, it seems that I would be stuck using the old drivers if I ever wanted to access this backup set in the future. So unless there is some way to re-associate the media set members with the actual corresponding tapes, it's looking like I'm going to have to redo the archive. Grumble grumble... Thanks. There's plenty to go around! :cryy:
  8. greggerman

    Backup fails during verification

    Yikes! Now that I have upgraded my UL5D drivers (from 4.3.1 to 4.3.3), Retrospect is suddenly very crashy. I tried to run my verify script...crash. I tried a manual verify...crash. I tried to repair and rebuild my media set...crash...crash. It is interesting to note that before the driver upgrade, Retrospect wasn't showing the barcode numbers on my tapes. Tapes were just listed as Erased, and were relabeled with their media set names once they were used in the backup (ie, 1-Spring 09 Archive, etc.) as they should. Now, after the upgrade, the barcodes are showing up, but quite ominously, even the tapes that should be named with their media set names are being shown with their barcode numbers. And when I look at the members of my media set, they have their media set names, but the location and barcode fields are blank. Is it possible that Retrospect is crashing because it doesn't realize that the tapes it needs for the media set are the ones in the library? Did upgrading the drivers for my SCSI card cause me to lose my archive? The data must certainly still be on the tapes, but Retrospect doesn't know it...
  9. greggerman

    Backup fails during verification

    Well, it looks like I don't have the latest firmware for my UL5D installed. (I could have sworn that I updated that...) Anyhow, I stopped my verification script and am installing the latest firmware. I'll try my script again after that is done. As far as I can tell, my tape library does have the latest firmware. Thanks for your help!
  10. greggerman

    Backup fails during verification

    Aha! Okay, so I created a verify script and am running it now. Hopefully it makes it through this time. I'll post again when it does (or doesn't). My tape library is set to automatically clean the drive when it needs it, so I hope it is doing that. I took a look at it and it claimed it didn't need cleaning. Perhaps the error message just shows up in the log when it needs cleaning and then the library just takes care of it, without reporting it in the log. I would hope none of the tapes are failing because they are all brand new. And my SCSI card is a ATTO ExpressPCI UL5D LP.
  11. I have a newly installed tape library and I was doing my first backup with Retrospect. It seems to have gotten through the writing portion fine, but it failed in the verification stage. Is it possible to re-verify the data, or do I need to do the backup over again? Yes, more details of course... CONFIGURATION Server: Xserve 2 x 2.8 GHz Quad Core Intel Xeon OS: OS X 10.5.7 Retrospect version 8.1 (build 150) Autoloader: AP Series TL2000 2U tape library (identified by Retrospect as BDT FlexStor II) SPECIFICS OF BACKUP I was attempting to back up about 5.5 TB of data from a fibre attached Xsan volume. In the Activities panel, I see a red X for this backup and it's status says "Execution incomplete". But in the Past Backups panel, the backup shows up with a green check and it's status says "Successful backup". It even allows me to browse the files. THE LOG + using Backup Assistant - 8/7/09 6:53 PM at 8/7/2009 6:58 PM (Execution unit 1) To Media Set Spring 09 Archive... 8/7/2009 6:58:41 PM: Copying SFS MapError: unknown Mac error 93 > !Trouble writing: "5-Spring 09 Archive" (2172649472), error -205 ( lost access to storage medium) !Trouble writing media: "5-Spring 09 Archive" error -205 ( lost access to storage medium) MapError: unknown Mac error 93 MapError: unknown Mac error 93 8/9/2009 3:57:35 AM: Snapshot stored, 13.5 MB 8/9/2009 3:57:38 AM: Comparing SFS > !Trouble reading: "3-Spring 09 Archive" (5248303), error 0 ( unknown) 8/9/2009 3:07:32 PM: Execution incomplete Remaining: 41109 files, 3627.0 GB Completed: 270 files, 1863.4 GB Performance: 2908.9 MB/minute (2923.2 copy, 2867.7 compare) Duration: 1 20:08:51 (01:00:14 idle/loading/preparing) THE END So since it failed during verification, can I attempt to verify again, or do I need to try to backup the full 5.5 TB again? Any ideas or tips would be appreciated. Thanks!
  12. Thanks for your advice, twickland and rhwalker. It turns out that this was a hardware issue. Quantum has replaced the SuperLoader with a new unit and now I am getting 400+ GB per tape again. Of course, now it looks like I'm having other issues with Retrospect 6.1.230, but that is another story...
  13. Yes, by capacity I mean the amount of data that's being written to each tape. And by "steadily decreasing" I mean not that each individual member is smaller than the last, but that the overall average tape capacity in a backup or archive session has been decreasing over time. I'll list some backup/archive dates and the average member size to show you what I mean: 2/20/08 409 GB 3/18/08 406 GB 4/15/08 408 GB 5/28/08 405 GB 8/25/08 403 GB 12/06/08 350 GB 1/27/09 358 GB 3/20/09 319 GB 4/24/09 290 GB 5/1/09 292 GB 5/15/09 289 GB 6/12/09 283 GB We are backing up mostly video data, so we didn't expect there to be much compression. We are certainly fine with the 400 GB/tape that we were originally getting. We'd just like to get it back to that level as we are wasting tapes as things are now. We are generally backing up the same kind of data that we always have, though perhaps we have more HD content than we used to. But it doesn't seem like that should make a difference, as there was never much compression going on to begin with. But perhaps it's more complicated than I think... There hasn't been anything of note in the operations log. Does Retrospect keep any additional logs? The "Operations Log" doesn't generally give out much information. I'll take your advice about looking into the drive itself to see if that is causing the issue. From looking at my data points, it almost appears as if something is wearing down. I'll post again after I've looked into it. Thanks for your help!
  14. I am using Retrospect 6.1.230 on a Mac to backup and archive data from an Xsan volume mounted on this Mac. Retrospect is writing to LTO-3 tapes in a Quantum SuperLoader 3. I have been using this setup since 4/07. For some reason, this Spring I have noticed that Retrospect no longer fills any of the tapes to their 400 GB capacity like it used to. The tape capacity has been steadily decreasing and seems to be maxing out at around 300 GB now. And it makes no difference whether the tapes are new or recycled. As a bit of additional background, I was running Retrospect 6.1.138 up until about a week ago. I then upgraded to 6.1.230 in hopes that it might help with this issue, but I ran another archive and the problem persists. And for completeness' sake, my Mac is an Xserve (Xserve1,1) Dual-Core 2 GHz Intel Xeon with 4 GB RAM. So . . . any ideas?
  15. Did you ever get this issue resolved? I'm having the same issue. My LTO-3 tapes used to fill right up to the 400 GB limit, but recently (the past six months or so) my capacity has decreased to between 280 - 310 GB range. However, I'm using Retrospect Backup 6.1.138 for Mac.
×