Gosi - what you suggest is fine, especially for backing up with limited space on the output side. However, my strategy is to simply copy the most recently changed M megabytes every day to a new, dated directory. Every now and then I'll consolidate these dated directories by copying the most recent over the second-most recent, and so on until I have a cumulative backup with everything that's changed since the last date of consolidation.
My main quibble, which Chris addressed, was keeping static files separate from frequently changing ones. My only dislike of my earlier solution was that I had to change "profile.ijs" in the J system area. I see now that I can just keep my own profile wherever I want and change my invocation of J as Chris suggested. I like this solution because it's clean - I don't have to worry about a new J install overwriting my customized code and I can back up my own work separately from J and other installed applications. I'll look at making your suggestion an alternative in my overall backup scheme. Thanks, Devon On 10/1/06, Björn Helgason <[EMAIL PROTECTED]> wrote:
One thing you can do is to add into your backup routines is to check the date of a file and only back it up if it has changed since X then you can include more directories and not increase your backupvolume a lot I find the USB volumes good for backups - easy/big/fast 2006/9/30, Devon McCormick <[EMAIL PROTECTED]>: > > This principle is embedded in my home-made backup utility, written > in J, in that I allow certain parts of the directory tree to be > excluded from consideration when figuring out what to back up.
... -- Devon McCormick ^me^ at acm. org is my preferred e-mail ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
