Jump to content

twickland

Members
  • Content count

    1,679
  • Joined

  • Last visited

  • Days Won

    39

Everything posted by twickland

  1. Those are developer debug errors that many of us wish would not be displayed. You can safely ignore errors that look like those. The errors and warnings that may matter will be preceded by a colored symbol in the log.
  2. We had an issue in Retrospect 12.0.0 (213) where a Copy Backup script set to match files in the source and destination media sets, and to not add duplicates, nonetheless copied many files that were already in the media set. The Copy Backup script was configured to copy a single selected backup using the All Files rule. Here are the relevant details: On April 2, we created a new tape media set, "B-2." Also on April 2, source "Vic" was backed up to disk media set "C;" this was the last backup from that source to that media set. Over the intervening days, additional tape members were added to set B-2; member 3 was added on April 4. On April 5, a Copy Backup script ran, configured to copy the most recent backup of each source from disk media set C to tape media set B-2. According to the log, the April 2 backup of Vic was copied at that time. On April 6, a backup was performed from source Vic to tape media set B-2. My intention today was to get the most recent files from set B-2 to set C, running the script described at the beginning of this post. If the matching had proceeded properly, only a few hundred files from tape member 3 should have been copied. Instead, Retrospect requested tape member 1 and proceeded to copy tens of thousands of files comprising many GB.
  3. Looking at your log excerpts, I don't see any problem. It would appear that Retrospect did exactly what it should have done. The log shows that you had a total of just over 1.9 TB of data to back up on March 30. It was able to write 527 GB of this data before you stopped the script. When you were successfully able to add the 5th member and began running the script again on April 1, Retrospect backed up the remaining 1.4 TB to this new member. Is there something I've missed here?
  4. Losing a member of any media set only loses the data on that member; the rest of the data is accessible. If a member ever becomes lost or unreadable you should mark it as lost in the Media Sets window. That way, Retrospect will back up the data from that member again (assuming, of course, that the files are still on the source volumes).
  5. There is no good way to delete backup data from a media set. You could mark member #4 as missing and erase the drive, but you would lose everything that was on that member. Are you sure that Retrospect is really trying to back everything up again? And what is "everything?" The source that was being backed up at the time that Retrospect failed to recognize the new member, or literally everything? Normally, when a backup is interrupted, Retrospect will only try to back up new or changed files at the next backup, assuming, of course, that the usual "match files" and "don't add duplicates" options are checked. Of course, if you have a large amount of data on the source that is frequently being modified, you could have a lot of data to back up, even after a relatively brief interruption. Have you confirmed that your script parameters (rules, options, etc.) haven't changed?
  6. Although a disk media set can't be configured to span two disk volumes, it can use the second and any subsequent volumes as additional members of the media set. (The only downside is, if you are grooming a multi-disk media set, you can only reuse the free space generated on the last member.) Would this meet your needs?
  7. If you highlight the member in the Media Sets window and click on the edit (pencil) icon, you should be able to navigate to the correct location. BTW, where are your media sets' catalogs located? On a local volume or on the same volume holding the backup data?
  8. If you want to avoid this issue, you can turn off instant scan in the Retrospect engine preference pane.
  9. When you launch the Retrospect console app, it should automatically offer to install the Retrospect engine. If it does not, go to the Preferences window, Console tab, and click on "Export server installer." You will then be able to install the engine manually.
  10. You need to run the uninstall script, located in the Retrospect app folder. Then reinstall Retrospect 11.5.3.
  11. You should run the Uninstall script located in the Retrospect app folder; then reboot. (Although the script is supposed to ignore your media set catalogs and configuration file, if you don't have a recent copy of these files, I would drag these items from /Library/Application\ Support/Retrospect to the Desktop just to be safe.) I would then try running the Retrospect 12 installer again to see if you have better luck this time.
  12. The setting in Preferences is for how many past activities (not past backups) are shown; there is no setting for past backups. The Past Backups list corresponds to the list of your available restore snapshots; that is, it will list the most recent backup of each source to each of your media sets, plus any additional backup snapshots you might have retrieved from your backup media. If you have a large number of sources and a large number of media sets, you will normally have a large number of past backups as well. If you have any media sets that are not in active use, you can remove them from the media set list, which will cause their snapshots to disappear from the past backups list. (They will, of course, also disappear from any scripts where they are listed as a destination.) This option would be my first choice, because if you ever need to restore from one of those old media sets, you can use the Locate button to find the media set and all of the snapshots will reappear. You can also remove any number of past backups in the Past Backups window that belong to an active media set (that is, one that is listed in the Media Sets window). Just remember, though, that those snapshots will no longer be available to use in a Restore until you retrieve them from the backup media.
  13. Scripts are not stored in the catalog file; they are stored in the file Config80.dat, located at /Library/Application Support/Retrospect. Where is the media set catalog stored? On the same volume as the data? The disk media set catalog and the folders containing the actual data need to have the same name as the media set. In the past, Retrospect would not allow one to rename any media set; I haven't played around to see whether this limitation is still in place for disk media sets. As to why Retrospect is trying to back up more data than you expect, there are several possibilities. If your backup script has the option "Match only files in same location/path" selected, it would definitely want to back up everything, since you are now backing up a different volume. Likewise, if "Use attribute modification date when matching" is selected, Retrospect would want to back up a lot of data. If both of these options are unchecked, it may be that in copying the files from MacHD to SSD Drive, some parameters that Retrospect uses for matching may well have changed. If the latter is the case, you will have to put up with a large initial backup, after which the normal incremental backups should resume. I don't have a clue as to why Retrospect appears to have changed the name of your media set. Normally, after moving Retrospect to a different volume, the only thing one needs to do is to click on Locate in the media sets window and then navigate to the location of the catalog.
  14. twickland

    Add Sources

    Have any changes been made to your LAN? It sounds like subnet broadcasts are now being blocked.
  15. Don't know about that, but I do know that grooming is not so useful for multiple-member disk sets. Although Retrospect will groom out the earlier backups, the space recovered on the earlier members cannot be reclaimed, as Retrospect will only write to the last member and you can't move backup files from one disk volume to another. Grooming is really only effective for a single volume media set.
  16. In what window do you see the "Script not active" status? Could you post a screenshot? When the script gets into this status, are you able to edit it: change destinations, sources, schedule of allowed operation, etc.?
  17. As long as the version is any 6.1.x, you'll be OK. The later (.230) build should be better (more bug fixes, etc.). After you copy over the catalog files, you'll need to tell Retrospect about them. Double-clicking in Finder is probably the easiest way to do this.
  18. Your log indicates you're using an HP tape drive. HP does offer a Mac version of their Library and Tape Tools that runs in the Terminal command line environment. The current link for the download page is http://h20564.www2.hp.com/hpsc/swd/public/readIndex?sp4ts.oid=406731. If that link is broken, try searching for "hp_ltt mac" on HP's support page.
  19. I assume by "'Backup Sets' files," you mean the backup set catalogs. Keeping the catalog files will speed future access to the data. If you don't retain the catalogs, you would need to recreate them from the backup media anytime you needed to access the data. If your backup sets are large, recreating the catalogs can be quite time-consuming. I recommend that you find someplace to keep the catalog files.
  20. Retrospect has always had a limited ability to report out its parameters and data. This ability became much more limited beginning with Retrospect 8 and hasn't been improved since. There is no practical way to obtain a complete listing of every file in a media set. The only way I know to even approach it is to initiate a restore operation, searching for all files in the media set. Then in the preview pane, you would need to turn all of the disclosure triangles so that all files are visible. You would then need to take a series of screenshots, scrolling through the preview pane.
  21. twickland

    Help Getting System Up Again

    You don't say that you uninstalled and reinstalled the Retrospect client software. Can we assume you did this? What client version did you install? The only time the client software itself will ask for a password is during the installation process. If you have created and are using a public/private keypair, the installer will not ask for a password, and you won't need a password to log in from the Retrospect server. I would try running the uninstaller again and trash retroclient.state if it hasn't already been deleted. You might also check whether there are any other files or folders referencing Retrospect in the root or user Library and trash any that you find. Run the client installer again. Make sure you are using the client version appropriate to your version of Retrospect.
  22. twickland

    Help Getting System Up Again

    This would This is likely because the hard drive volume on his new computer was cloned from his previous computer. Assuming you can log in to the client, there is probably no reason to reset the Retrospect client, since everything important about the client (favorite folders, etc.) resides on the Retrospect server. If you do use favorite folders, you will need to add them for his new hard drive volume, since the old volume is now unavailable. If you do want to completely reset the client software, you will need to uninstall the Retrospect client and then check that the file retroclient.state, located at /Library/Preferences, has been deleted.
  23. This sounds like it may be related to the bug I reported a couple of months back at http://forums.retrospect.com/index.php?/topic/151506-retrospect-1152-wont-properly-accept-source-options-in-copy-backup-scripts/
  24. Those types of errors would typically be caused by problems in your SCSI chain or the tape drive itself, which may be failing. Are you using a single stand-alone tape drive or a tape library? Are there any other devices on your SCSI chain? What brand and model of SCSI adapter are you using? Whenever Retrospect encounters serious problems writing to a tape member, it will ask for a new tape. Sometimes this means that the tape member is faulty, but the -102 error combined with the fact that you have used 6 tape members would pretty much rule that out. You might try running a cleaning tape and see if that helps. Then try the diagnostic procedures described at http://www.retrospect.com/en/support/kb/troubleshooting-error-102-trouble-communicating. In my own experience with tape drives, though, I think the problem is most likely the tape drive itself. These are mechanical devices, and the tape heads and other parts will eventually wear out.
  25. If the snapshot is on the media and if the media is readable, the rebuild should do the trick. If you're looking to restore specific files, though, you may find it easier and quicker to use the "Search for files..." option, which doesn't require snapshots.
×