Jump to content

shadowspawn

Members
  • Content count

    215
  • Joined

  • Last visited

Everything posted by shadowspawn

  1. Reinstalling the client is a good step to take. As well as the issue Dave pointed out, reinstalling will replace the behind-the-scenes files that make the client start when the computer boots.
  2. Are you running Mac OS X? Do you have the DAT drive turned on when you boot? I think the paranoid advice for SCSI has always been: turn on the SCSI device first, then the computer; shut down the computer first, the the devices. We have been spoilt for years with getting away with less, but on Mac OS X the operating system does not automatically recognise new devices added live, and does not allow allow a user invoked rescan. I believe the software can in theory discover new devices, but the safest thing to do is have the SCSI devices turned on when you boot the computer.
  3. Did you use the same hardware for the original backups as you are using for the restores? I am very surprised that Retrospect claimed to have performed a restore without retrieving any files, Retrospect is usually very conservative and accurate about what happened. Were you restoring selected files to a local disk? When doing a restore using a search, Retrospect puts the files in a folder in the restore destination with a folder name based on the backup set name. (You probably know this, but just in case it was your first restore like this!)
  4. My guess for a magic solution is Energy Saver. Make sure that the client computers are set to Never go to sleep. What state are the client computers left in: user logged in or out? Do people leave CPU intensive operations running, like a SETI screen saver at high priority?
  5. It depends a lot on how much is running on the (any) client. If the user was logged out, then you would not expect many busy or changed files. If a user was logged into the client with seventeen application running, and actually using the computer too, you do get a few busy and changed files! It is tedious looking through them, but Retrospect is telling you about files that were not backed up, so the backup did not get every single file on disk. You can hopefully tailor what you backup, or when you backup, to get the files you care about with minimal warnings.
  6. What Paul said. I use Retrospect Desktop to back up clients, but do need to switch the "server" to a network configuration with only one network interface selected while doing the backup. Also as Paul said, the client seems to be less sensitive to this issue.
  7. This card does not seem to be listed on the Dantz compatible hardware list . Large numbers of errors during the compare can indicate unreliable communication with the backup device, so the backups should not be trusted.
  8. Just ran my first backup at home since upgrading to Panther. Retrospect 5.0.238 on Mac OS X 10.3 backing up to VXA 1 on firewire, incremental backup of ~2 GB. Immediate backup ran to completion with no problems. (Your milage may vary.)
  9. We are in the middle of the same problem, VXA1 on SCSI with Adaptec 2930, seriously unreliable after changes to a working configuration. Changing the SCSI card to a different manufacturer seemed to help, but among the various different failures we twice saw serious hardware errors on the VXA unit itself (flashing red light). We sent our unit in for repair hoping that it is the underlying cause of the problems.
  10. In my experience it is hard to stop Retrospect from backing up mounted disk images. Interesting to hear from someone for whom this is a feature rather than a bug. There was a problem with Retrospect 5.0 with the default settings and a read-only image, Retrospect would hang after trying to change the volume backup time. You are probably not affected by this issue assuming your disk images are mounted writable (and the work-around is to change the backup settings to leave the volume backup time alone).
  11. Quote: I have checked ram, drives, connection, tapes, everything I can think of. If ANYBODY has any ideas out there PLEASE mention it. You have eliminated the tape drive as the point of failure, and also tried various SCSI connections. That still leaves the computer itself. Three possible approaches: 1) Reinstall Retrospect and apply all available updates 2) Clean install OS and all available updates and Retrospect 3) Try a different (newer) computer I suggest trying a newer computer as the best and simplest approach. The beige G3 is unfortunately right at the bottom of the Mac OS X supported computers. Although it was working previously, it isn't now!
  12. Quote: 10/21/2003 7:30:38 PM: Comparing Mirror2… 10/21/2003 8:56:15 PM: Execution completed successfully. Completed: 19338 files, 70.9 GB Performance: 34.5 MB/minute (38.1 copy, 31.4 compare) Duration: 02:36:20 (00:01:46 idle/loading/preparing) There is something odd going on with this backup, the numbers do not match up. With that performance it should have taken over 24 hours to back up 70 GB. The later backup that ran out of time shows a duration that matches the performance, and the total backup does not fit into 12 hours. I suggest taking a look at which files have been backed up using Reports > Contents. (Wild speculation, perhaps a very large and inappropriate file, like a virtual memory or cache backing file, is included in the backup. It might consist mostly of zeroes when the computer is first booted. I don't whether this explains the odd performance figures though!)
  13. No info on Panther, but... Quote: and I'm hoping that version 5.1 fixes the bugs in 5. You don't need to hope, you should find out. Retrospect 5.1 in use so you can ask about specific problems and find out ahead of laying down the money whether they are addressed. No point blindly upgrading and them being disappointed.
  14. Quote: Is this still an issue with Retrospect 5.1? Yes. Quote: What is the best approach for having Retrospect 5.1 server do a proper backup with Mac OS X users. Should the Mac OS X users be logged out or logged in? Should I turn the hard drive sleep options off? Energy Saver settings Put the computer to sleep when it is inactive for: Never Hard disk and monitor sleep settings do not affect backup, so set them to whatever suits. The paranoid way to backup is to have the users logged out, so that the hard disk is in a known state (less chance of running programs holding open files, or caching data in memory and not writing to disk). In practice, I leave it up to the client. I have not noticed problems with overnight backup of logged in computers.
  15. Quote: is all the information I need to recreate the most recent set of files on the primary drive all contained in that backup set "Q"????? Yes. (Or to be more exact, you can recreate the set of files at your last backup.) Quote: And I'm hoping Retrospect's "incremental" function is capable of retaining xyz.doc and xyz1.doc, even if xyz.doc is erased or completely missing. Yes. The backup set contains every version of every file that has been backed up. Copies do not get replaced by newer versions or deleted from the backup set, until you do a "Recycle" and start over again.
  16. The short answer is that Retrospect does not currently wake up the computer, so you need to arrange for your computer being awake for the whole backup period.
  17. Quote: So, I believe I have successfully created a revision to the BackUp Set A file. And I guess what I was thinking is that retrospect will automatically write/copy all the changed files to the backup drive. However, when I looked for a particular file that I knew had been recently modified/created, it was not on the backup drive. It sounds like you are almost there, but are slightly confused about how Retrospect works. Assuming you are doing a Backup (not a duplicate), then when you do an incremental backup Retrospect is putting a copy of all the changed files into the backup set file. You can't see inside this file in the Finder to see what is in the backup. You can see how big it is though, it should be large after your original backup! To do another incremental backup by hand without previewing all the files: Immediate > Backup Select the sources, say Local Desktop. Select the destination, say "Backup Set A". Click Backup. When it is finished, you can check what went into the backup by using Reports > Contents and browsing the last session in the backup set. This should list just the changed files that got backed up, which is a much smaller list than previewing the whole backup. The alternative to a Backup is a Duplicate. A Duplicate is quite like copying the files using the Finder, but smarter.
  18. Found the answer when I rechecked previous postings (I missed it first time around). There is an upper limit of 2 GB on the catalog file. Obviously it would help if the Retrospect failure mode was a little more informative! Retro 5 under OSX -- 2G catalog file error? HELP! The catalog files on disk are: Eta: 1.99 GB Theta: 1.98 GB I think both the catalogs are actually uncompressed. Attempting to compress the catalog gives error -39 (unexpected end of file). The catalog options then still have the radio button showing the intent to have the catalog compressed, although the reality is different.
  19. Did this ever get resolved? I have just started getting very similar behavior with errors occurring and the catalog being damaged in the process. NB: I am not seeing chunk checksum errors. However, the main advice in the chunk checksum link that Amy gave was to try a different disk and/or different computer, which is what I am going to try. Drive Setup > First Aid reported no problems on the disk. Retrospect Server 5.1.167 DP G4 867 MHz Mac OS X 10.2.6 768 MB RAM VXA-1 tape drive (2C8C) Adaptec 2930CU SCSI adaptor, ROM 4.0 revision 3, driver 1.1.0 Backing up mounted volumes, macintosh clients, windows clients, to VXA-1 tape unit. Catalogs stored on 12 GB local partition, 4.75 GB available. Problem has occurred multiple times in last two weeks, no other hardware errors in log, two different backup sets, three different tapes. Backups sometimes run ok, and have been running fine in past with same configuration. Backup set Theta is 408.7 G for 4,340,168 files, catalog compression on Backup set Eta is 421.0 G for 4,261,950 files, catalog compression off These are the biggest backup sets I have ever had, so I wonder if the size is significant? Entries from log: - 2/9/2003 8:01:20 PM: Copying Orange on Orange MacX… 2/9/2003 8:01:20 PM: Connected to Orange MacX Can't save Snapshot in Theta, error -39 (unexpected end of file). Can't save catalog, error -24204 (chunk file damaged during access). [Theta] - 4/9/2003 10:31:31 PM: Copying DocumentationG3 on Documentation MacX… 4/9/2003 10:31:31 PM: Connected to Documentation MacX Couldn't write Snapshot, error -198 (unknown). Can't create session, error -40 (file positioning error). - 5/9/2003 10:52:59 AM: Copying System on Dxxx MacX… 5/9/2003 10:52:59 AM: Connected to Dxxx MacX Can't save Snapshot in Theta, error -39 (unexpected end of file). Can't save catalog, error -24204 (chunk file damaged during access). [Eta] - 17/9/2003 10:16:32 PM: Copying DRIVE C (C:) on Mxxx PC… 17/9/2003 10:16:32 PM: Connected to Mxxx PC Couldn't write Snapshot, error -198 (unknown). Can't create session, error -40 (file positioning error). - 18/9/2003 9:34:03 PM: Copying DRIVE C (C:) on Sxxx PC… 18/9/2003 9:34:03 PM: Connected to Sxxx PC Can't save Snapshot in Eta, error -39 (unexpected end of file). Can't save catalog, error -24204 (chunk file damaged during access).
  20. Quote: Problem is, after I successfully backup 35GB to three removable tapes, the local "normal/incremental backup" tries to back the entire 35GB again. I only want to back up the changed files in their own local backup file. As Dave pointed out, backup sets are independent, and you gain convenience with a full local backup. If you use a selector for the local backup that only includes files modified in the last seven days (say) you get something like what you were looking for. You do still get files backed up in both the tape and local backup, but you don't get the old files into the local backup. (So this is only a saving for the first local backup.)
  21. According to the Upgrade Pricing Matrix, all versions of Macintosh Retrospect Express or Desktop are eligible for the $59.95 upgrade price. On the Upgrades page there are two links. One is for when you already have an Upgrade Authentication Code from a reseller, and one is for buying the upgrade. Sounds like you followed the wrong link, try the Buy Now link instead. Quote: If you have not already purchased an upgrade, Buy Now.
  22. It is quite subtle the first time, but make sense after you find it. Click on the popup for an existing criteria. Note that it says "And..." in the popup. Click on the popup at the bottom of the criteria list. Note that it says "Or..." in the popup. (Or "New..." if you have no criteria.) So to make more restrictive criteria (And) you have two fairly direct ways: you can add new criteria to existing criteria using the popup; or combine existing criteria as Dave described.
  23. It sounds like Retrospect gave up (and things are bad!). What does it say at the end of the log from the verify? Quote: How should a verify proceed with a backup set of 10 members? And does a Retrospect "Verify" compare the backup catalog with the ability to read the file from the media? Is there some other verify tool I should use? The verify should ask for each backup set member. The "Verify" compares very closely with the ability to read the file from the media (it is exactly what it is for!). Additional information which might be useful: - are you doing verify on same DVD drive as the original backup? - Mac OS version? - DVD, model and firmware version? - the log from the verify
  24. Quote: First, is this somehow better than doing a full backup, and using that to restore the internal drive in the event of a disaster? Not much difference for a restore of the whole original disk. The advantage of a duplicate is that the result is directly useable in the Finder. You can manually search it for files, and in an emergency you can boot from it to restore or switch directly to using the duplicate. To a minor extent another advantage can be that it is a known size (i.e. same as original). In contrast a normal backup starts out with a smaller result, but each "normal" incremental backup after that makes the backup set bigger. The big advantage of a backup set is that it can contain multiple versions of files, including files that are no longer on the original disk. Any backup is better than no backup, so either way you can't lose. Quote: Second, I have a number of file backups as well as folders with other information in the external drive. I don't want to destroy that data. It looks like if I select the "Replace corresponding files" option, that data will be left alone (since even if the file name is the same, the path is different). Am I right about this? Yes. Files that you have deleted from the original disk will not be removed from the copy. This could be an advantage at time, but means more care is probably required if you want the duplicate bootable. After a system upgrade on the original you would want to clean out the duplicate system folders so that you don't have obsolete files left in the duplicate system. (I think you can do a "Replace entire disk" to a sub-volume" which gives you an exact copy, but am unclear whether the disk will still be bootable with the system files down a level!) For true piece of mind no matter what you choose, testing is required. e.g. after a duplicate, see if you really can boot of the spare disk!
  25. shadowspawn

    Subvolume Selection

    The trick is that Retrospect is running with elevated privileges (in particular, as root) to allow it to back up all of the local computer. This interacts in unexpected ways with what you see yourself in the Finder. You and Retrospect are effectively logged in as two different users. If you are lucky, it just works. (It does for me!) If you are unlucky (probably because of strict permissions on your server volumes), you need to be careful to mount volumes in the "right" way. So you should set up the mounted volumes using the instructions Dave pointed out in the previous post. After that, my advice is to always dismount all mounted volumes before you launch Retrospect. That way there is no conflict between ones mounted by "you" and the access "Retrospect/root" requires. Retrospect can mount the volumes itself as required once they are set up correctly.
×