askay Posted August 14, 2003 Report Share Posted August 14, 2003 This is another cry for help on Restrospect locking up while building a snapshot. I'm Running Retrospect 5.6 backing up to a SCSI DAT tape drive. My unattended backup hangs reporting that it's building a snapshot of the system drive after having backed up the files. The machine is running Win2k, and this previously working backup developed this problem immediately after installation of Service Pack 4. Retrospect is hung to the point that the "Stop" button won't terminate the backup; I had to kill the process to stop it. Any clues? Quote Link to comment Share on other sites More sharing options...
natew Posted August 15, 2003 Report Share Posted August 15, 2003 Hi To figure out if this is a device or Retrospect problem... What happens if you try a test backup to a file backup set? Can Retrospect build the snapshot then? Nate Quote Link to comment Share on other sites More sharing options...
askay Posted August 15, 2003 Author Report Share Posted August 15, 2003 Thanks, Nate. The retrorun.exe service is running (I should have noted in my original post that the system drive isn't the first one backed up, and Retro already had successfully created snapshots of other drives). An immediate backup of the system drive to a file encounters the same problem, hanging on "Building Snapshot... ." When I have a few minutes, I'm going to reload the executable on the chance that the service pack install munged one or another .dll. Alan Quote Link to comment Share on other sites More sharing options...
askay Posted August 15, 2003 Author Report Share Posted August 15, 2003 Nope, reinstalling Restrospect 5.6 doesn't make any difference. If it's worth anything, the file name showing in the process box when the app hangs is IIS Metabase, but that may simply be the last file it copied. There are no problem entries in the log. Alan Quote Link to comment Share on other sites More sharing options...
askay Posted August 15, 2003 Author Report Share Posted August 15, 2003 The solution, at least for the moment, was a complete uninstall and reinstall of the executable. After that, an immediate backup to file of the system volume ran to completion. We'll see if the scheduled backup of the full network array runs as well -- that is, after I recreate the script<g>. (If it does, I won't clutter up this forum with an additional post.) For the moment, though, I'd caution anyone considering it to assume that installing W2k SP4 will hose Retrospect 5.6. Alan Quote Link to comment Share on other sites More sharing options...
natew Posted August 21, 2003 Report Share Posted August 21, 2003 Hi As a follow up - this was probably a case of corrupt Retrospect preferences. Nate Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.