Tracey
Trust me. SecondCopy 2000 most definitely does NOT copy whole directories each time - it only copies those files which have changed. If you are in any doubt you can look in its log file which will contain full details of which files have been copied when and also any error conditions encountered (such as file in use). I have absolutely no idea if 2ndCopy is better or worse than the other programs you mention.
It is worth recognising that 2ndCopy operates by polling (ie scanning) the source and destination directories to determine if a file has changed and should be copied. For this reason it does not make sense to run it too frequently. Other programs (eg diskeeper) I suspect operate by intercepting O/S Interrupts when a file has been closed. Personally, I prefer the former just because it is simple and foolproof. The second method could get flooded with interrupts if, say, I copied a whole batch of files to my source directory; this in turn would mean that the number of processes available to the backup program would have to be throttled and arrangements would have to be made to remember which interrupts had been received but not acted upon in the event of the system shutting down before they had all finished. An unlikely situation you might say, but that is what bulletproof software is all about. With the simpler polling scenario you just have to restart (by automatic schedule) the backup again when the system is restarted and everything comes out in the wash.
But I don't understand why I would want to copy a fle as soon as it were closed (saved). I normally save my work every 5-10 minutes which means that my backup is going to run every 5-10 minutes. If I keep 3 generational copies than my oldest backup is going to be 30 minutes old. That's not a lot of use to me.
As far as I can see there are 3 disaster scenarios I want to avoid:
1) the application corrupts the output.
2) I make some changes that I subsequently want to back out.
3) My hard disk fails
I take care of (1) by configuring all my applications to rename the input file (eg .bak)before saving the output.
In the case of (2) I name my files file_1.xar, file_2.xar etc
In the case of (3) I use SecondCopy to incrementally backup to a separate drive.
Brian
Bookmarks