twickland Posted August 4, 2015 Report Share Posted August 4, 2015 I recently discovered that there is nothing to prevent Retrospect from backing up a media set to itself! I was creating a test backup script and inadvertently selected as a source the volume that contained the destination media set. When the script ran, it dutifully began copying the various .rdb files belonging to the media set into new .rdb files in the same media set. It seems pretty obvious that this process would continue until manually stopped or until all available blank media was filled. It would seem to be a good idea to have Retrospect perform a check to ensure that this kind of loop cannot occur. Quote Link to comment Share on other sites More sharing options...
Lennart_T Posted August 5, 2015 Report Share Posted August 5, 2015 It seems pretty obvious that this process would continue until manually stopped or until all available blank media was filled. I'm not so sure about that. Retrospect scans the source for files and then backs up the files it already have found. I'm pretty sure it doesn't copy/backup the .rdb files (or any other files for that matter) that was created after scanning. Copying .rdb files is of dubious value anyway, so I always use a filter to exclude them. 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.