MultiBackup backup program for Windows

• versatile
  Specification of files for backup is done with DIR-style wildcards or regular expressions. DIR-style is more familiar to most, regular expressions are more versatile. The local machine can act as data source, backup repository, both, or neither. Using FTP, files can be copied from remote data source to remote backup directly.
• simple
  Good graphical user interface. Fill out Job name, Source directory, and Destination directory, press Apply, and then the Run button. Files are copied and the job is remembered next time you run MultiBackup.
• scalable
  A single job, multi-part job, a job list, and multiple job lists are easily managed. Jobs are defined logically, so that a single job may access multiple directories and computers with various backup parameters.
• featured
  
  • network access
    address networked Windows computers with UNC format: \\machine\share\directory
    address FTP servers with: ftp:machine directory. Passwords are encoded in MultiBackup's job files.
  • rotating backups
    write to day- and/or time-based backup versions
  • backup cleanup
    interactive deletion of orphaned backup files
  • backup scheduling
    register jobs with the Windows scheduler
  • reverse job cloning
    support for data mirroring
    
  • more...
  
  view the Windows help file MultiBackup.hlp (link on home page) for complete descriptions
  
  

  ---

Things that MultiBackup does NOT have

• No compression
  MultiBackup does not perform data compression. Compressed files can take up less network bandwidth and less space on the backup media. If your backup disk resources are scarce compared to your working data sets, or you want to retain so many backup versions that you may run out of room, a data-compressing backup program might be the solution.
  -- mitigating fact: when backing up over a modem (when transfer speed is lowest and therefor most crucial), data compression is part of the modem protocol, so the speed benefit of pre-compression is reduced if not lost entirely. (note to self: measure this)
  -- mitigating fact: if a compressed filesystem is used for backup (easily created under Windows NT, 2000, XP) every file is automatically compressed
  -- mitigating fact: disk space is ever less expensive (typically 1/2 cent per Megabyte, spring 2002)
  

• No tape backup
  MultiBackup does not write or read tape devices. Tape storage media are less expensive than disks and may be desirable for other reasons.
  -- mitigating fact: disks are cheap, see previous mitigating fact
  

• No multi-volume sets
  MultiBackup duplicates directory structure in the backup. Any single backup task has to fit on the backup medium in an identical directory tree, so it cannot, for instance, be placed on multiple floppies or CDs.
  -- mitigating fact: none. This ability would be nice, but would entail management of a file catalog so you could find the file you wanted to recover from the set. Well... storing the catalog on the last backup volume would maximize transparency for the user (such as matching the catalog with the backup set, and backing up the catalog itself).... so I'm considering it for a future version, depending on user requests.

• No file encryption
  MultiBackup does not encrypt files, but saves them as duplicates of the original.

• No boot recovery
  MultiBackup does not make disk images and does not differentiate system files from user files. It does not backup disk boot tracks or CMOS settings.