kazeeks Posted September 29, 2005 Report Share Posted September 29, 2005 Hi... So I set up a restore and started it. 30GB in it decided to stop and threw an error in the log "205 - lost access to storage medium". Of course, the drive and loader were still visible in devices, so i'm not sure what it was pissed about, but i digress. If I set up my restore again, Retrospect wants to restore everything again. I've tried using the restored folder as the destination, as well as the parent volume. I've tried rplace corresponding files as well as retrieve files/folders. Either way, it seems incapable of knowing that most of it is already restored. I currently inspect the restore, match the files myself, and only select what's remaining; retrospect should do that for me. I'm not using snapshots, all my restores are searches. That shouldn't matter, however, as retro should still scan the destination and say "half of this is already here!". Link to comment Share on other sites More sharing options...
natew Posted September 30, 2005 Report Share Posted September 30, 2005 Hi It sounds like the date and time on the restored files is changing. Is the disk you are restoring to formatted the same as the disk the files were backed up from? Thanks nate Link to comment Share on other sites More sharing options...
kazeeks Posted September 30, 2005 Author Report Share Posted September 30, 2005 > Is the disk you are restoring to formatted the same as the disk the files were backed up from? Negative. The source disk was a journaled HFS+ partition on an OS X server. The destination is a UFS volume on a FreeBSD server. The destination volume is AFP shared. I've mounted the volume as root on the Retrospect machine, and saved the AFP password, so Retro knows how to log in. All systems involved, the original source server, the Retrospect machine, and the FreeBSD system are set to Phoenix time (no getting confused at the time shifts), and are locked to NTP. All systems display an identical time, down to the second. Link to comment Share on other sites More sharing options...
natew Posted October 3, 2005 Report Share Posted October 3, 2005 Hi That is why then. The time stamp or the file size on the files is not being preserved when they are restored to the network disk. As a result Retrospect will try to back them up again. Files must match exactly in order for Retrospect to resume a restore from where it left off. Thanks Nate Link to comment Share on other sites More sharing options...
kazeeks Posted October 14, 2005 Author Report Share Posted October 14, 2005 >The time stamp or the file size on the files is not being preserved when they are restored to the network disk. I have the feature "Restore mod dates on duplicate or restore" enabled in the "secret" prefs. Is that just for show? Link to comment Share on other sites More sharing options...
natew Posted October 19, 2005 Report Share Posted October 19, 2005 Hi, This isn't a Retrospect problem so the settings don't matter. In the past OSX would cause this problem for every network volume. Modify dates would be off by 1 second every time on the network files. Samba servers can also do this. Thanks, Nate Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.