Jump to content

jpbuse

Members
  • Content count

    12
  • Joined

  • Last visited

Community Reputation

0 Neutral

About jpbuse

  • Rank
    Occasional forum poster
  1. I am trying to add my linux clients to my Retrospect backup server. I have linux clients already added which work fine and have been for quite a long time. One of my clients was added a few months ago and has been running w/o issue until this week when I received the "Error 506 (duplicate activator code)" message when trying to add the client again. I haven't changed/updated anything on the server side. I have run standard OS updates to the linux machine(s) lately. My server is running Retrospect 6.1.126 on a 10.4.10 PPC machine. My linux client is a CentOS 5.x box running retroclient-7.0.110-1. I skimmed the SMC website for some answers but couldn't really find anything useful. Any thoughts? Thanks in advance. Jason
  2. I guess that is one reason I am really confused. There is a cleaning tape (CLNxxxxx) physically in slot #1 of the tape library. Slot #2 of the tape lib as the A00022 tape in it. So, why does screw it up? It looks like Retro doesn't see the cleaning tape CLNxxxx at all. Maybe I have configured something wrong but I thought in Retro I would simply click on a slot # and designate that as the cleaning slot. Below is a dump from the tape library's inventory system... you can see the cleaning tape is in Slot #1 and the A00022 is in slot #2 (element ID #1). Retrospect is showing 23 of 24 slots. I'm guessing Retro recognizes the CLN tape and doesn't count it as a usable slot. I do have the Exabyte drive setup with a dedicated cleaning slot, meaning I have programmed the tapelib to use a fixed slot #1 and autoclean when needed. Perhaps that would affect how Retro sees it and maybe I don't need to designate a cleaning slot within Retro itself. I ran a test. I disabled the fixed cleaning slot in Retrospect and ran my backup that I was having issues with (to A00022) and sure enough, it worked. It grabbed the proper tape and started to write data to it. Element ID Type: Number Status (POVA) Label valid Label 97 Robot Empty (1010) 1 Clean Occupied (1111) 1 CLNA01 1 Slot: 2 Occupied (1111) 1 A00022 2 Slot: 3 Occupied (1111) 1 A00027 3 Slot: 4 Occupied (1111) 1 A00004 4 Slot: 5 Occupied (1111) 1 A00046 5 Slot: 6 Occupied (1111) 1 A00047 6 Slot: 7 Occupied (1111) 1 A00003 7 Slot: 8 Occupied (1111) 1 A00020 8 Slot: 9 Occupied (1111) 1 A00039 9 Slot: 10 Occupied (1111) 1 A00016 10 Slot: 11 Occupied (1111) 1 A00001 11 Slot: 12 Occupied (1111) 1 A00023 12 Slot: 13 Occupied (1111) 1 A00030 13 Slot: 14 Occupied (1111) 1 A00017 14 Slot: 15 Occupied (1111) 1 A00018 15 Slot: 16 Occupied (1111) 1 A00031 16 Slot: 17 Occupied (1111) 1 A00033 17 Slot: 18 Occupied (1111) 1 A00034 18 Slot: 19 Occupied (1111) 1 A00036 19 Slot: 20 Occupied (1111) 1 A00035 20 Slot: 21 Occupied (1111) 1 A00042 21 Slot: 22 Occupied (1111) 1 A00043 22 Slot: 23 Occupied (1111) 1 A00045 23 Slot: 24 Occupied (1111) 1 A00037 E/E Port In Process (1000) 1 81 Drive: 1 Empty (1011) 1 Quote: Then I don't understand. You say: Quote: The tape is indeed the proper CLNxxxx barcode label. The A00022 barcoded tape is a good backup tape which ran last night. Slot 1 is cleaning, slot 2 is the A00022 tape. Your second picture is captioned: Quote: Cleaning slot turn off (showing the correct tape barcode): Yet there is no CLNxxxxx barcode in any slot, and A00022 is always shown in slot 1. Confused, Russ
  3. Russ, Wow, a lot of info. Stupid question/answer first. The tape is indeed the proper CLNxxxx barcode label. The A00022 barcoded tape is a good backup tape which ran last night, Retro was happy with it at one time. When I look at the library web gui, it shows the proper tape, in the proper slot, etc. My guess is a cosmetic issue with Retrospect. The library is loaded (24 tapes, including cleaning), and currently there is no tape in the drive. All other backups are/were working just fine. The library is full. Slot 1 is cleaning, slot 2 is the A00022 tape. Retro seems to be reading the element ID and not the slot ID. Retro only shows 23 slots but its a 24 port including the cleaning tape. Jason
  4. I've got an Exabyte Magnum 224L FC library connected to my Mac xServe G5 running Retrospect (specs below). I have a cleaning tape in slot #1 of the library and I've assigned that slot as a cleaning slot within Retrospect. I *think* it is cleaning when it should. The main problem I have is when I view devices via Retrospect (Configure>Devices), slot #1 is indeed assigned as the cleaning slot, however the tape barcode in slot #1 according to Retro is a backup take, not the cleaning tape. The tape in slot #1 of the lib is the cleaning tape. What gives? xServe G5 Dual 2Ghz, 6GB ram, OS X Server 10.4.9 universal Retrospect 6.1.126, DAV:1.0.107, DUV:6.1.10.100 Connected via fibre channel through a QLogic 5602 FC switch Cleaning slot turned on: Cleaning slot turn off (showing the correct tape barcode):
  5. I'm looking for advice and all-around best practice(s) for archiving. I've read through the basic Retrospect guide on archiving but I'm looking for deeper info and some real-world examples to help guide me. I'm a bit new to archiving and while I have my idea of how to handle it, I'm assuming there are many others before me with much more knowledge they would like to pass down. I want to archive old projects from our online storage to our offline (LTO3) storage. By "archive" I mean move to tape and delete from the source. After reading the Retro Tips docs, I plan to have 2 archive scripts. The first will archive w/o the optional move, and the 2nd will archive to different media w/ the optional move. This way I have two copies of the same archive on different tapes, one for onsite and the other for offsite. My initial thinking was to have a server volume for my users called something like 'Archive', simple enough. I would train my users what to put there, how to name it, etc. This will get the data off the main data share and therefore out of my daily/weekly backup routine. Depending on the amount of data I would most likely commit to tape archive once every month. Once committed to tape, the projects would be removed from the online Archive share. I'm assuming the data has already been backed up before. Although for this post I don't think tech specs matter too much, here is what I've got: - All Mac OS X environment - PowerMac G5 DP 1.8Ghz, 6.5GB RAM, 10.4.8 as dedicated Retro backup server - Connected via FC is a 3.5TB xServe Raid and Exabyte LTO3 Magnum 224LC FC library - Retrospect 6.1.126, DAV: 1.0.107, DUV: 6.1.7.101 Some issues/questions: 1. How will my users know what data is archived so they can retrieve it later down the road? - I was thinking of using something like DiskTracker to catalog every single file in the archive and tag it with the corresponding tape IDs. A user could then tell me they need project X which is showing it is located in the June 07 archive on tape 1234. This is more man hours than I would like to commit to archives. Another option is some sort of FMP database. Perhaps Retrospect has something built-in already that I am clearly missing. 2. If I commit a set of data to archive and it only uses 30% of a tape, is it ok to reuse that same tape next month to maximum the storage capacity of the tapes, or is that a no-no? 3. How would the process actually go, perhaps something like this? a) move data from 'Archive' server share to date-stamped directory such as 2007.02 use DiskTracker to catalog all data in 2007.02 c) run archive script named 'ONSITE' w/o move using 2007.02 as source, once complete d) run archive script named 'OFFSITE' w/ move using 2007.02 as source e) move tapes to proper storage facility/location, etc. 4. Do I simply have 2 archive scripts that keep grabbing new tapes as needed... so in theory in a year I would have done 12 archives and it could have spanned across 10-20 LTO3 tapes. Is that ok, or is it best to treat each archive run as its own?
  6. Just want to make sure I am doing this the right way. I have a selector (lets call it 'never backup') with a TON of excludes for files I never want to backup. Pretty straightforward. I then have another selector that I've tailored to fit my Incremental script needs called 'Inc Selector'. Within 'Inc Selector' I have the 'never backup' selector under the exclude section as "not selected by 'never backup'". I would assume that since 'never backup' excludes the unwanted files, then I would want this 'inc selector' to always exclude files not selected by 'never backup'... but I'm not totally sure thats correct. Little insight?? Thanks.
  7. I'm looking for advice and all-around best practice(s) for archiving. I've read through the basic Retrospect guide on archiving but I'm looking for deeper info and some real-world examples to help guide me. I'm a bit new to archiving and while I have my idea of how to handle it, I'm assuming there are many others before me with much more knowledge they would like to pass down. I want to archive old projects from our online storage to our offline (LTO3) storage. By "archive" I mean move to tape and delete from the source. After reading the Retro Tips docs, I plan to have 2 archive scripts. The first will archive w/o the optional move, and the 2nd will archive to different media w/ the optional move. This way I have two copies of the same archive on different tapes, one for onsite and the other for offsite. My initial thinking was to have a server volume for my users called something like 'Archive', simple enough. I would train my users what to put there, how to name it, etc. This will get the data off the main data share and therefore out of my daily/weekly backup routine. Depending on the amount of data I would most likely commit to tape archive once every month. Once committed to tape, the projects would be removed from the online Archive share. Although for this post I don't think tech specs matter too much, here is what I've got: - All Mac OS X environment - PowerMac G5 DP 1.8Ghz, 6.5GB RAM, 10.4.8 as dedicated Retro backup server - Connected via FC is a 3.5TB xServe Raid and Exabyte LTO3 Magnum 224LC FC library - Retrospect 6.1.126, DAV: 1.0.107, DUV: 6.1.7.101 Some issues/questions: 1. How will my users know what data is archived so they can retrieve it later down the road? - I was thinking of using something like DiskTracker to catalog every single file in the archive and tag it with the corresponding tape IDs. A user could then tel me they need project X which is showing it is located in the June 07 archive on tape 1234. 2. If I commit a set of data to archive and it only uses 30% of a tape, is it ok to reuse that same tape next month to maximum the storage capacity of the tapes, or is that a no-no? 3. How would the process actually go, perhaps something like this? a) move data on 'archive' share to date-stamped directory such as 2007.02 use DiskTracker to catalog all data in 2007.02 c) run archive script named 'ONSITE' w/o move using 2007.02 as source, once complete d) run archive script named 'OFFSITE' w/ move using 2007.02 as source e) move tapes to proper storage facility/location, etc. 4. Do I simply have 2 archive scripts that keep grabbing new tapes as needed... so in theory in a year I would have done 12 archives and it could have spanned across 10-20 LTO3 tapes. Is that ok, or is it best to treat each archive run as its own?
  8. Update: I bought a new SCSI cable from Cables to Go and I have not had any more issues. So far, so good. On a different note, Exabyte has deemed my library a lemon and is replacing it, unrelated to the SCSI issue.
  9. Thanks Russ. I talked again to Exabyte tech support (great people btw) and they've recommended I try a new SCSI cable. According to them about 60% of tech support calls for SCSI LTO devices are due to bad cables. I'll most likely bump up to the fibre channel version of this device for other reasons but for now I'll check out the link you sent me and try a new cable. Thanks for the info. I'll post back w/ results.
  10. My flash version on the ATTO is 1.5.2. The InDesign SavedData file is a secondary issue here really but I will add an exclude in my scripts for the file(s). Again, the biggest problem is the 'error 205 (lost access to storage medium)'. A part of me wishes I spent the extra money for the fibre channel version so I don't have to deal w/ SCSI issues. Fibre either works or doesn't. SCSI has so many varying degrees of failure.
  11. Fair enough... I was being lazy. G5 running 10.4.8 client Retrospect 6.1.126 Retrospect mac os x clients running: 6.1.130, linux clients running 7.0.110 Driver update: 6.1.7.101 DAV: 1.0.107 Exabyte Library Firmware: C113 Exabyte IMB LTO3 drive firmware: 64D0 ATTO UL4S driver 3.6.0 According to Exabyte tech support they are saying its purely a SCSI related issue. I sent them over the system logs from the backup server and they claim to see SCSI bus resets in there. I am using the Exabyte supplied SCSI cable and terminator although I will try swapping these out as they could be faulty. I am using the ATT0 single channel SCSI card and the Exabyte Library is the only device I have on the SCSI chain. In addition Retrospect always hangs when it tried to copies the 'InDesign SavedData' files from the source. I have to force quite Retrospect to get it to recover, then restart the machine for the G5 to see the LTO on the SCSI bus.
  12. I've got an Exabyte LTO Magnum 224L SCSI tape library connected to a DP 1.8Ghz G5 w/ 6.5MB RAM. There is an ATTO ExpressPCI UL4S single channel Ultra320 SCSI in the G5. LTO device is properly terminated. The G5 is running the latest version of Retrospect server backup. G5 is connected via gigabit ethernet to the same switch as my xServes I am backup up data from. I'm trying to backup 2 xServes over a gigabit network. One xServe is running 10.4.7 and the other is running 10.4.8 (server). I've got the latest version of the Retrospect client on both machines. I'll admit that for the past 2-3 years I have not been using Retrospect for my backups. I've been using a homegrown method involving tar, rsync, etc. I wanted a backup solution that would be hands free to handle both daily incrementals and weekly full images. Anyways, so far I've got nothing but problems and I'm not sure where to start to troubleshoot. My Incremental script runs at 10pm M-F. Around 10:20pm the script will fail and the error message left on the screen says 'error 205 (lost access to storage medium)'. This happens every single time as far as I can tell. At this point I can manually run the script and it will work some of the times. I say some because quite often it will choke part way through the backups and just hang and not do anything. For example, I am looking at the server from last night's backup and it is just hanging at maybe 50% completion of the backups. I have to manually stop it and the logs don't give me any useful information. Most of the time when I stop the script I have to force quit Retrospect to use it again. Most of time by doing this I lose connection to the LTO so I must restart the G5 to see the LTO device again. This issue so far is the biggest and most annoying issue I have for obvious reasons. I've been running this system for maybe 10-12 days and have yet to have a single success. I haven't dealt with external SCSI devices on a Mac for many years so a part of me is wondering about the SCSI connection between the server and the LTO. I had thought about going to the fibre channel instead but it didn't seem worth the extra cost at the time. Any ideas on where to start to troubleshoot? I'm going to be calling Exabyte support today and see what they know but my experience with Mac support forums as been good and I'm looking forward to seeing what responses I may get.
×