Jump to content

adrianw

Members
  • Content count

    7
  • Joined

  • Last visited

Community Reputation

0 Neutral

About adrianw

  • Rank
    Occasional forum poster
  1. Hello. In attempt to resolve problems with an aging (but reportedly supported-by Retrospect) OnStream ADR2 SCSI tape drive, I interested to hear whether any one has worked with the following combination: Dell PV110T LTO-2L External SCSI Tape Drive ATTO ExpressPCI UL4S (single-channel Ultra320 SCSI) controller Retrospect 6.1.126, Device Access Version 1.0.107, Driver Update Version 6.1.7.101 Power Macintosh G4 (AGP Graphics) with 10.4.7 I realize that this list is specific, so I would be curious to hear people's experiences with similar configurations. The hope is to avoid another reportedly supported configuration on paper but does not work in the real world. In regards to EMC Retrospect's web site for device compatibility, the Dell PV110T LTO-2 drive, the drive is listed as "Qualified" <http://www.emcinsignia.com/supportupdates/technical/retrospect/detail/?id=8977>. (Interestingly, the OnStream ADR2 SCSI tape drive which has not yet successfully and consistently worked with the aforementioned combination of hardware and software - <http://forums.dantz.com/ubbthreads/showflat.php?Cat=0&Board=devicesx&Number=74722>.) Thank you, -Adrian
  2. Thank you for the reply. Having tried different cables, SCSI terminators, SCSI ID settings, and updating the Retrospect Driver Update Version to 6.1.7.101, the device is now listed in the Storage Devices window. Unfortunately, I do not know which one of the above changes caused the device to display (as I was not available to view and record the process of these changes). Now, having resolved this problem, there is an issue with backups to tapes not completing successfully. It seems that the backups will indefinitely wait after backing up and before verifying (with status such as rewinding). During these times, the Operations Log reports "Decompression failed due to corrupt input data" at the "Comparing" (verification) stage of a backup. Different media will be tried and disabling data compression.
  3. Quote: Sounds like you might have SCSI issues. Good cables? Short cables? Good terminators? Is the tape drive on the same circuit (UPS) as the server so that you don't have ground loop issues? The cable is brand new so I would hope it is good. The cable is 3 feet in length. As far as I know the terminators are fine. The tape drive is on the same circuit as the server. What confuses me is the fact that the OS and ATTO configuration tool seems to be able to recognize (or at least display the name of) the tape drive. Additionally, the device was working fine in the past 24 hours but since and before than it has not been recognized.
  4. Hello. Our current setup: Retrospect 6.1.126, Device Access Version 1.0.107, Driver Update Version 6.1.6.100 on a Power Macintosh G4 (AGP Graphics) running 10.4.7. An ATTO ExpressPCI UL4S (single-channel Ultra320 SCSI) controller with ATTO driver version 3.6.0 and flash version 1.5.0 card is connected to an OnStream ADR2 SCSI tape drive. OS X and ATTO's configuration tool (version 3.06) recognize both the SCSI controller and tape drive. However, Retrospect only sometimes recognizes the tape drive. In fact, a transfer of a backup set was successfully performed within the past 24 hours from a file set to a tape set using this SCSI controller and tape drive. A few hours after this successfully job, a scheduled job was configured to backup to the tape drive using a tape set. However, this failed with a an error message, "Can't find any tape storage devices." Within Retrospect viewing the devices (or "Storage Devices") the window reports "No backup devices found", yet under "Device Status..." the tape drive is listed under the "Currently visible devices..." at SCSI ID 3. This is both frustrating and confusing. Why does the tape drive intermittently appear and work sometimes but not at other times? Is there a Retrospect configuration file that can reset or rebuilt which might resolve this issue? Thank you, -Adrian
  5. Our current setup: Retrospect 6.1.126, Device Access Version 1.0.107, on a Power Macintosh G4 (AGP Graphics) with 10.4.7. The file set destinations resides on two internal drives (each 120 GB). One drive contains the OS and some Retrospect file backup sets and catalogs. The other internal drive being used a removable disks as a destination for the Backup Server. There are two "Source Groups" setup. One for a few servers and another for a couple workstations. Creating a "Backup Server" script and assigning it the source group for the workstations causes ALL clients to be processed by the "Backup Server" script. However, if the source group for the workstations is removed and an individual client is added to the Backup Server" script - only the individual client is processed, as expected. Recreating the source group for the workstations and reassigning to the "Backup Server" script did NOT solve this issue. It seems there is an issue with "Source Groups" and Backup Server" scripts. Have other people experienced this as well?
  6. Quote: The basic problem is the same: Normal backup scripts and duplicate scripts run fine, writing to the designated storage set (DDS or removable disk). Backup server scripts also work fine under most circumstances. However, backup server scripts often get stuck (usually after backing up a single client) when the destination storage set chosen is one of the DDS storage sets AND two other conditions are fulfilled: a backup set on one of the LaCie FW HD's partitions is listed as one of the destinations in Backup Server AND the disk itself is mounted. "Stuck" means that the Backup Server "Backup Sets" window's "Action" indication flashes alternately between "Polling" and "Checking media," while the "Sources" window flashes "Media" opposite the client due for backup, and nothing further happens. Quitting and relaunching Retrospect will fix the problem temporarily; unmounting the LaCie Drive or removing it from ALL backup server scripts (active and inactive) seems to fix the problem for good. Our backup configuration is exhibiting this behavior while trying to use the Backup Server to backup clients. The "stuck" description explains exactly what is happening on this system. Our current setup: Retrospect 6.1.126, Device Access Version 1.0.107, on a Power Macintosh G4 (AGP Graphics) running 10.4.7. The destination drives are two 120 GB internal hard drives (one drive contains the OS and some Retrospect file backup sets and catalogs. The other internal drive being used a removable disks as a destination for the Backup Server). Quitting and relaunching Retrospect does not solve this problem. I am surprised to read that after a year and several releases later in the both the OS and Retrospect software that this would still be an issue. Any suggestions as to why Retrospect may be exhibiting this kind of behavior, as the original poster requested, would be appreciated. Changing the destination to a file set instead of using an internal hard drive as a removable disk seems to have corrected this behavior.
×