BJB Posted March 21, 2006 Report Share Posted March 21, 2006 Greetings, I use Retrospect 6.5 as part of a kit to backup a Fireball music server. I have read the FAQ's and documents and am pretty familiar with the Retrospect software and other backup software. What has me confused is this. I used the "duplicate" "replace entire volume" option for the second time to backup the unit. Now based on the documentation, I expected it to ONLY have to copy the NEW files. In other words, files that were not there the last time the duplicate was run. If files were exactly the same, it should have left them alone. But retrospect re-copied everything. The new files (as expected) but also each and every old file that was absolutely there for the last duplicate. Now at the end of the day, I had a good backup, but it took forever vs. just taking a short time to copy the new files... Now I talked to Dantz support.....and their suggestion was to use the "replace corresponding files" option. Now again, after reading the documentation, I understand the difference between the two options. And based on what I read, if the files are the SAME (name, path, date, etc) either option should leave them alone. Is there a setting somewhere that I am missing here? Was phone support totally offbase??? I am running a Dell XPS 3ghz PC with 1 gig memory running XP Pro backing up an escient fireball E-120 over a wired network to an external Maxtor drive connected to the PC via Firewire. Is there a place in your user setup to allow you to input your equipment etc? I did not see it, just personal stuff. I utilized retrospect express 6.5 duplicate>replace entire volume> I went to source> advanced and set the UNC path for the source content directory. Selected all files. Started the backup. I saw it scan the drives, and then it started copying. And it obviously copied the entire drive again as the new files should have only been a handful. This takes hours.... Is there a setting in the backup software that changes this behaviour? I have the external drive letter hardcoded so that path should not change. I am using the UNC path for the source so that does not change....I guess somehow the fireball might have flipped a bit or something on the files but I doubt it. If there are no ideas I guess I will just try it again with the "replace entire volume" option and see what happens. It is just that support absolutely understood my question, but all the documentation I have read disputes their recommendation. BJB Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.