Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


Everything posted by twickland

  1. A recent poster found that the disappearing volumes problem may be related to Symantec AntiVirus v10 on the clients. He was able to resolve the issue by downgrading the clients from v7.0 to v6.5. One caveat: we found that the Retrospect application would hang at media member changes with Windows clients v6.5. We have been successfully using Windows client v6.0.110 with all our XP SP2 clients.
  2. If you set up a client with a fixed IP address, you can't change it later. Your best bet would be to have your networking people change the fixed or reserved IP address to the new computer. However, this will only save you having to add the client back into your script or volume group. Retrospect's matching function doesn't care where or on which client a file resides (unless you have selected the script option "match only same location"), so whether the IP address is the same or not won't affect the size of the next incremental backup. Unless the physical hard drive is swapped between the old and new computers, Retrospect is going to see a number of files as having changed when they were copied from the old drive to the new, and will back them up again. If you've selected "match only same location," ALL files will be backed up again, because they will be located on a new, different volume.
  3. Quote: It seems as though the delay in writing caused by the need to switch the DVDs is causing a timeout in the network connection between Retrospect server and the client - the "Piton protocol violation." Yep. The 515 error incurred at media member changes while backing up OS X clients has been a problem for us from day 1 that we have never been able to eliminate under Retrospect 5.0, 5.1, or 6.0. We back up multiple subnets across switches, and it's my hunch that the filtering set up by our network guru is implicated in the problem. Because we run into this error only every couple of months (we use DDS tapes that hold 15-25 GB and 90% of our clients are Windows, which don't exhibit this problem at media transition), because our networking staff are loath to make any changes that might compromise security, and because they only tolerate rather than support our independent Retrpospect backups, it hasn't seemed worth it for me to dig any further into the causes of this problem. I would be interested in any solutions that other users come up with. A concrete idea would give me some leverage to get our networking folks to look at this issue again.
  4. If your concern is primarily about having to back up the retropds.log file, I would just exclude it from your backup script.
  5. Perform a Restore from Backup, selecting the option "Replace Corresponding Files." As part of its preparations, Retrospect will scan the destination drive and compare it with the backup snapshot. When the backup summary window appears ("Not ready to execute"), click on "Files Chosen," then double-click on the drive icon to mark all files. The files preceded by a diamond are the ones on the destination drive that are exactly the same as in the backup set; these will not be replaced during the restore. Note that any files on the destination drive that have been modified since the time of backup are not exactly the same and will be replaced by default. You can scan through the file list and manually unmark any such files that you don't want replaced
  6. If you will be using the same backup set as on the PowerBook, you will need to tell Retrospect where the catalog is. Either double-click on the backup set's catalog file, or go to Configure> Backup Sets> [Name of backup set] Configure...> and navigate to the new location of the catalog. Then go to Configure> Volumes and forget the old PowerBook volumes from the Volumes list.
  7. If you remove RDU 6.5 from the Applications> Retrospect folder, can you then launch the application?
  8. Can we assume that all the clients are in the same subnet? It doesn't sound to me like the problem is with the Retrospect client software per se. I would try playing with the auto-protect settings for your anti-viral software, and perhaps uninstalling and reinstalling these. As you note, you can access the clients; it's just that something on the client computers (likely related to the anti-viral software) is preventing access to the hard drives. We haven't used the v7 client software with our Windows clients, but did have some communications issues with the v6.5 client. On the off-chance that this may be part of the problem, you could try downgrading the troublesome clients to v6.0.110 and see if that helps.
  9. We're using Retrospect 6.0.204 on a Graphite G4 450 DP running 10.3.9, writing to SCSI (ATTO UL4S) DDS tape drives (HP DAT-72 and Sony SDT-10000) and a FW HD. A problem has developed recently where our Backup Server scripts periodically lose the ability to see media in the SCSI tape drives. When this occurs, the script goes the the first client, flashes "Media", and goes no further. A second backup server script (which doesn't write to the tapes, just to the FW drive) does not run because the first script is stuck. Our regular backup scripts which write to the SCSI tapes run just fine, even while a backup server script is still running, stuck, and flashing "Media." Going to Configure> Devices>, the tape drives and their associated media are shown correctly. Rescanning the SCSI bus in Retrospect doesn't help, nor does quitting and relaunching Retrospect; however, using the ATTO Configuration Tool to rescan (which resets the SCSI bus) does allow Backup Server to behave properly for a while. When the misbehavior occurs, it usually appears with the first client. However, in about a quarter of the failures, the tape backup server script backs up the first client successfully before flashing "Media." Thus far, if the script manages to back up two clients to tape, it successfully backs up all clients to the tape. Any idea why this is happening, or why backup server scripts should see the SCSI bus differently?
  10. When you first back up to a partition, does the log show any errors during backup or compare? Does the catalog for the problematic file backup set show the proper file sizes and dates/times, compared to what you see on the source in Finder?
  11. Actually, a Recycle Backup will not by itself create a new backup set. Selecting "New Media" _will_ create a new backup set with a similar name as the old backup set, having a number in brackets appended to the old name; e.g., My Backup Set [001]. The next New Media backup will then create new backup set "My Backup Set [002]," etc. Your scripts will automatically be modified each time to begin using the new backup set in place of the old. The old backup set catalog belongs to the old media. You should not trash it (i.e., erase it from the drive) until you trash or erase the old media; otherwise, you will need to rebuild the catalog if you ever want to retrieve data from the older backup set. Forgetting the backup set from the list of backup sets is not the same as erasing the catalog. You can safely forget the old set and then reaccess it as needed (though there is no need to forget the old set unless you're just trying to remove clutter from your Backup Set list).
  12. You need to create a Backup Server script for your laptop clients. You can set the backup interval (say, once every 23 hours) and also permit (or preclude) early backups. Early backup is what is controlled by the client preference you note above. Read the User Manual for more details.
  13. On the other hand, the drive may indeed be faulty. I had a LaCie 500 GB Big Disk that was giving an increasing number of 206 errors on compare. Finder copies and Carbon Copy Cloner seemed to work just fine, and I tried reformatting the drive numerous times, all to no avail. One day when I was writing to the disk, it locked up, requiring a reboot. When the system came back up, Disk Utility showed two LaCie mechanisms (not partitions): one 236 GB and the other 2 TB. The 2 TB "mechanism" could not be formatted. Since the drive was replaced, I have not had further problems. (FW cable was not replaced.)
  14. The file you want is /Library/Preferences/Retrospect/Retro.Config (6.0). Note that this is the library at the root level, not your user library. Because you are using Retrospect to recover the file, you will need to restore the file to a new folder. Then, quit Retrospect, manually drag the file to the proper folder, and restart.
  15. Quote: The second disk ie. the one I changed to had already been prepared for me What do you mean? When did the preparation occur; i.e., what did you do to prepare the disk? A recycle backup will erase the old catalog and will look for the first member of the backup set (I'm assuming that you are using the two FW drives as members of a removable disk backup set). Quote: so I did not have to do anything except to perform "recycle" I was told... clearly, they forgot to tell me to choose "New media" instead of recycling. By "they," do you mean the Retrospect application? If you are indeed reusing the same media, you don't want a "New Media" backup set. Quote: thing is, upon running the script Retrospect ends up "Waiting for backup media". How do I make Retrospect work automatically again? (Manual back-up works) What backup set did you use as a destination for the manual backup? Does this differ from the backup set listed as a destination in your backup script? What are the names of the backup sets appearing in your regular script and in the Immediate Backup window?
  16. Check the script you're using to back up to the On the Go drive to be sure that in Options> Matching>, both "Match source files to catalog" and "Don't add duplicates to backup set" are selected (this is the default).
  17. It sounds like your original action (Recycle) was what you wanted to do. If you just want to reuse your original disk, erasing the old data to replace it with new, you want a Recycle backup. A New Media backup is called for if what you want is to save the old data in the existing backup set, create a new backup set using new media (in your case, a third FW drive), and have Retrospect use its existing scripts to start writing data to the new backup set in place of the old.
  18. Does the AirPort Express have the same configuration settings as your old base station? Did you update to AirPort 4.2 at the same time? Some users have reported connection difficulties after that particular update. If you connect the AirPort Express to your cube via Ethernet, are you able to back up the PowerBooks, or do the clients then lose communication with the base station?
  19. Quote: I'm assuming that different types of files compress at different rates... is this correct? Yes. In fact, certain files will not compress at all. In addition, if the rate of data fed to the drive is less than what the drive can accept, the drive will not achieve optimum efficiency.
  20. Each catalog is specific to a given backup set. The only way to "merge" the catalogs would be to copy (transfer) the data from each old backup set to either your current backup set or a new backup set. However, you may have no need to do this. In performing a Restore, you can easily search across multiple backup sets.
  21. Click on Configure> Backup Sets> Configure....[name of backup set]> Members> to see the amount of data stored on each member.
  22. If there are a lot of members (tapes) in your backup set, you might consider an alternative and just copy and erase the members which contain the client's files. The catalog does not indicate which member contains a particular backup, so unless you have an extraordinary memory, you would need to identify the dates and times of backup of the files in question (easiest way to do this would be to run a mock Restore), and then compare this information with the date and time that data was first written to each backup set member (listed in Configure> Backup Sets> Configure...[name of backup set]> Members> ). Then, after you perform the Transfer, instead of forgetting the entire catalog of the old backup set, you would return to Configure> Backup Sets> and mark the copied tape members as "Missing" before erasing them.
  23. You cannot remove individual files from a tape. To fulfil the demands of your client, you would need to use Tools> Copy> Transfer> to transfer all other files from your old backup set to a new backup set. You will need two tape drives to accomplish this in one step. You can either define criteria for selecting files to be excluded from the transfer, or you can manually select the files before performing the transfer. Once you've done this, forget the catalog of your old backup set and erase the tape(s) that were members of the old set.
  24. "Lock Application" and "Run Unattended" both mean the same thing. I use both, and tend not to distinguish one term from the other. However, as Dave points out, the menu option "Lock Application" is available only when a script is not running. When a script has been launched, the option you want is "Run Unattended." Sorry for any confusion my too-quick reply may have caused.
  25. Quote: Then i tried to have a look at the volume snapshots and - THEY WERE EMPTY or had rather nothing than one or two folders. How are you looking at the volume snapshots? I was not aware that one could browse the snapshot contents in the Mac version of Retrospect. (If you could view the contents, each snapshot should list the entire directory of the volume at the time of backup.) Did you instead mean "sessions," as are found in Report> Contents> ? If so, these do indicate only the files backed up at a particular time. In a normal incremental backup, a session will only contain files that have changed AND that meet the selection criteria set for the backup script. That could be a small number of files. I would check and see if the selection criteria are what you intend. If you are using a defined Selector, you can test it independently in edit mode to see if it behaves as you expect. If you run an Immediate Backup using the same selection criteria, do you back up all the files you expect? What if you select "All Files" instead? If the behavior continues to be anomalous, it may mean that your Retro.Config file is corupt.