Jump to content

twickland

Members
  • Content count

    1,679
  • Joined

  • Last visited

  • Days Won

    39

Everything posted by twickland

  1. So many things can affect backup speed, including network traffic, activity on clients and the backup Mac, size and number of files being backed up, etc., that you'll just have to wait and see. On our 100Base-T network, where we back up across routers, clients may back up anywhere between 25 MB/min and 225 MB/min. Compare usually runs faster than backup, but sometimes is slower. Overall speed (backup & compare) probably averages around 90-100 MB/min. By the way, I notice you're not using the latest version of Retrospect. I recommend that you update.
  2. Quote: Is it possible to make Retospect NOT skip to blank media that has been explicitly named? No. If there is no data on a tape, it is blank, no matter what you may name it. Frankly, what I'd recommend is simply to label the tapes AFTER they have data on them, which is what we do. I find this a lot simpler. If you really want to label the tapes in advance, you will have to adjust the schedules of your scripts. It sounds like you are probably using Backup Server scripts, rather than Backup Scripts. If so, you could set the active schedule for the next week's server script to "Never active" via the radio button (this will retain any custom schedule you have created). When you switch tapes, change the schedule of the current week's server script by selecting the "Custom" or "Always Active" radio button, as appropriate, and change the server script for the previous week's server script to "Never active" via its radio button. Alternatively, create a custom schedule for your backup server scripts that makes them inactive during the period of time you are likely to be changing tapes. If you are using regular backup scripts, avoid having the script(s) run on Mondays, and instead launch the script manually on those days from the Run menu, or else set the script to run late enough in the day that you will have time to change your tapes.
  3. Adaptec claims on its web site that the 2906 card is compatible with 10.3.x. However, you also need to be sure that your SCSI card meets the needs of your device. The Adaptec 2906 card is a narrow SCSI-2 card, while I believe the StorageWorks tape drive is a 68-pin wide-LVD device. Such incompatibility can cause problems.
  4. Why don't you just create a selector that will always exclude files named "retropds.log?" You don't really care that the files exist on the client hard drives; you just don't want to back them up.
  5. OK, let me see if I understand you: Retrospect always autolaunches, but the backup script sometimes doesn't run. The Retrospect application hasn't completely locked up, because you can still access the Preview window; yet something is clearly hosed, since you cannot manually run the script, nor run an Immediate Backup, unless you delete the scheduled event that's waiting to execute. Has this been going on as long as you've been using Retrospect? You have a pretty unusual setup. Do you really have 85 licensed copies of the Retrospect application? Did you install Retrospect on each of the X-serves independently from the CD-ROM, or did you use an installer downloaded or copied to a server? If the latter, perhaps an installer file is corrupt. Are you able to quit Retrospect normally when it gets into this condition? What happens if you then relaunch the program? Normally, if a script event is waiting to execute and the time is within the schedule of allowed operation, it should try to execute as soon as the program is launched. Have you tried leaving Retrospect running all the time and see if this helps? Success wouldn't be diagnostic, but at least the problem would be gone. If you haven't already begun, I'd keep a log of each server to be sure that the problem isn't limited to a particular subset. There's got to be something in common with the problematic systems.
  6. As I understand your setup from what you write, you have 85 servers, each with its own copy of Retrospect and its own tape drive, backing up only local drives (i.e., no network/client backups). Is that correct? Is the problem limited to some particular group of servers, or is it completely random? My first thought is that either the script or the general preferences has a schedule of allowed operation that doesn't coincide with the desired backup times/days. Are you allowing Retrospect to autolaunch, or is the application always active? What does the Operations Log say? Are you able to get the script in question to run from the Run menu, or do you need to perform an immediate backup or use a different script?
  7. From what you say, it sounds like the problem is almost certainly with the client computer. Are you absolutely sure it isn't going to sleep? Could the client be running some kind of processor-intensive application in the middle of the night that may cause it to delay responding to Retrospect? (Retrospect will only take a certain amount of time waiting for a response--in my experience, just over 5 seconds--before it decides that a client is not visible on the network.)
  8. Are you aware that VPC drive images are packages? Packages will show up as folders in Retrospect when you try to restore them. It will be easiest to restore using a snapshot. Double-click on the folder(s) with the desired drive names to mark it (them) for restore. After restoring, double-click on a restored drive image in Finder. This should launch VPC, and you should be on your way.
  9. One other caveat: When using "exactly matches," be sure that the name really does match; i.e., that you haven't inadvertently typed any leading or following invisible characters, such as spaces, in either the selector or the folder's Finder name.
  10. Yes, this is due to the DST time change. Windows uses a different method of implementing the time change than Macs. Retrospect sees the creation/modification dates of the files as not matching what had previously been backed up (they've shifted by 1 hour), and so backs them all up again. Once it does this, you will be back to normal, incremental backups on the Windows clients. Because of this issue, we use the Monday after each time change as the point where we rotate in new backup media.
  11. I can only speak from my own experience, but the only problem I have noticed in the 10+ years we have been using Retrospect is related to the different way that Windows computers account for the DST change as compared to Macs. This means that at the time change, Retrospect on the backup Mac (running a normal, incremental backup) interprets all files on Windows clients as having changed, and so backs up everything again. Since this is going to happen anyway, we have been performing our backup set media changes to coincide with the time change. Almost all of our Restores have been of selected files, not an entire disk, and all of our entire disk Restores have been to Mac clients. We have never had any problems, though I'd expect that restoring files to Windows clients that had been copied in a different time regime would probably have their creation and modification time stamps shifted by an hour. I have never checked this, and in any case that I can imagine, such a shift would be of no consequence to us.
  12. Do you mean you get the message "Content Unrecognized?" If so, that would probably mean that the tapes have some v6 data on them, which is incompatible with v5. Go to Configure> Devices> and try erasing the tape.
  13. Are you using the latest version of the Driver Update? Did you check Dantz's website to be sure that your drive is compatible with the latest version of Retrospect? Assuming that these are OK, it really sounds like a tape or tape drive issue. To confirm this, try launching your previous version of Retrospect. Create a new backup set and attempt to back up to one of the tapes that has been causing problems.
  14. Check the Knowledgebase at Dantz's support page for troubleshooting suggestions. Tech Note 307 in particular has a lot of information. If you have been backing up copies of the catalog file, you can try restoring an earlier version and updating it from your backup media. This will take less time than rebuilding the entire file. It's too late now for this problem, but in the future I'd recommend backing up to multiple backup sets in case you have problems with one set. It's also a good idea to do a New Media or Recycle Backup periodically so your backup sets don't become so large.
  15. If you are encrypting your data, Retrospect will command the tape drive to disable its hardware compression. Even if you're not doing this, you will rarely if ever reach the advertised (ideal) capacity of a tape. See the section on tape capacity in the User's Guide for more info.
  16. To expand on what Dave said, you can enable use of the Firewire HD as if it were a removable disk, provided you are willling to dedicate the entire drive solely to backups. Doing so will erase the entire drive, so be sure to move or copy any existing files on the LaCie drive that you want to save. Go to Preferences> Media Handling> and check the appropriate option. (If you have multiple Firewire devices, be sure that you have not checked the minimal erase confirmation under Preferences> Media Erasure> so you don't accidentally erase the wrong drive when backing up.) Then go to Configure> Backup Sets> to create a new removable disk backup set. Store the catalog in the desired location.
  17. Are you saying if you go to Directory> Configure> Devices you cannot see the tape drive? How is the tape drive connected to the server? With some connectors (e.g., LVD-SCSI) it's easy to get a bent pin in the plug, which can prevent a proper connection.
  18. Have you tries swapping the VXA-2 drives between the G4 and G5? That should tell you whether the problem is with the drive or with software/hardware on the G4. Have you performed any checks on the G4 hard drive(s) to see if the HD catalog needs repair? Have you tried uninstalling/reinstalling the Retrospect app? There could also be a hardware problem with the FW bus or a memory module on the G4.
  19. In my experience, every version of Retrospect going back at least to 1.3 has behaved badly whenever it loses communication with a backup device or a client. The only resolution in such cases, as you note, is to force quit the application. Have you updated to the latest version of the Retrospect driver software? We had a similar problem where Retrospect would hang while changing tapes in the middle of backing up a Windows client. We were able to solve this by downgrading the client software to an earlier version.
  20. Are you saying that changing the time zone ("Time Zone" tab) no longer works but did work in the past? Did you quit Retrospect before changing the time zone? When Retrospect reports the time offset, have you gone back to System Preferences to confirm that the time and time zone are still set for Central Time? I agree with you that Dantz should provide some means to deal better with time zone (and Standard Time/DST) changes.
  21. Quote: "Mark" isn't enabled for the folder itself, but rather only for the contents of the folder (package). Ah, there seems to be a peculiarity in Retrospect where the"Mark" button is not enabled for a folder if the folder is open, displaying contents (arrow pointing down). However, despite this, if you double-click on the folder, it and its contents will be highlighted and marked. Alternatively, if you click on the folder arrow so the folder closes (arrow points sideways), the "Mark" button is enabled. I usually just double-click, so I never noticed this anomaly before.
  22. The log will indicate what backup script ran; typically, "Normal backup to [script name] at..." Is it the name you expect?. Are you saying that the Automate> Scripts window is completely blank? Can you see the script in the Run menu, the Automate> Check window, or the Automate> Preview window? If you can see scheduled events in the Preview window, try highlighting an event and click on Edit Script. I don't suppose there's a chance someone renamed the script with all spaces or something like that. If all else fails, the configuration file may be hosed. It's found at /Library/Preferences/Retrospect/Retro.Config (6). (Note that this is the library at the root level; not your user library.) Try moving it to the desktop and see if Retrospect behaves better If you don't have a backup of this file and it is indeed corrupt, you'll need to recreate your scripts and lists.
  23. There's no direct way to do this, but you could approximate it by using Tools> Copy> Transfer to copy sessions after a specified date to a new Backup Set. This would require a second backup drive, but for safety's sake you should not be relying on a single backup set anyway. However, once you have a second drive (three would be even better), an even better idea would be to rotate your backups through all the drives. You could then establish a staggered schedule for performing a recycle backup on each drive, at frequent enough intervals such that the drive doesn't become full. That way you will always have at least one copy of the most recent backup sessions.
  24. The only way to back up to whatever drive happens to be attached is to use a Backup Sever script. A standard backup script has to have available whatever media set is scheduled to be used, or it won't run. If you really want to back up 24/7, a Backup Server script sounds ideal. However, if you just mean you want to back up once a day and then quit or shut down, a regular script might be better. I would question your wanting to rotate backup sets only once per month. That would mean you would lose a whole month's worth of data in the event of damage or loss to one of the drives. We use a different backup set every day, which you might find excessive, but even weekly rotations would be a lot safer than monthly. Whatever you want to do, it's possible to add enough day of the week or repeating interval schedulers to a script to accomplish the task. If you really insisted on approximately monthly intervals, I would suggest rotating backup sets every 4 weeks rather than each month, as you would need to create fewer schedulers (12, as opposed to 93). Doing the safer weekly rotations can be done with 3 schedulers. The only downside would be the hassle of swapping out the drive weekly rather than monthly.
  25. Sounds like either the Retro.Config file or the application itself may be hosed, or you may have a corrupt HD directory. I would first reboot from a CD and check/repair your hard drives using Disk Utility or DiskWarrior. If the problem persists, try dragging the config file (/Library:Preferences:Retrospect:Retro.Config (6) ) to the desktop temporarily and see if the application will launch. If it still doesn't, then try uninstalling and reinstalling the Retrospect application. If you have a lot of custom scripts or clients, you may want to save the config file and (assuming it's not corrupt) drag it back to the proper folder once you get Retrospect to launch.
×