Once the scheduler service has been started it is possible to submit a backup command using the ntbackup.exe image (image is a name for an executable) The command above would schedule a backup at 10:00 p.m. on weekdays of drive D: and the local registry with verification. If you are having problems with the scheduling you may want to use the /interactive switch so in the event of a problem you can interact with the backup program.

Most of the registry hives are open, making them unable to be copied in the normal way, however there are several methods available to you If you have a tape drive attached to NT, the NTBACKUP utility will perform a full backup of the registry if you select the "backup local registry" when performing the backup. Please note that NTBACKUP cannot backup registry's on remote machines. REGBACK.

There is no right or wrong answer to this question. We suggest that you backup your files as frequently as required so that if you had to restore your data, only the least amount of work as possible is at risk. For most people, backing up changed files every night is enough.

With most hosting accounts, Yes. Many virtual server account come with an included "backup plan". All virtual server accounts have this as an option. If you don't have us backing up your server, you should definitely do it yourself. Backup plans also include options for "local", "remote", and "mirrored" backups.

Even if you are currently backing up to tape, zip disk, CD-RW, or other form of media, more than likely, the process is not completely automated. An employee must change out the media periodically and manually verify that completed backups are successful. Our online backup system bypasses this tedious process. Backups are 100% automated, and backup reports are sent by email daily.

This is a matter of opinion. Think about this. If you had to re-enter all the data what day do you want to start from? Yesterday, last week, last month, from scratch? Two weeks worth of backup's is recommended. Your End of Month should be saved forever. These backup's should be stored in a safe place separate from your computer.

We recommend backup nightly with the backup being rotated each day and stored off-site. Your electronic medical records (EMR) are valuable, so we make it easy to keep them safe. Simply run Backup from the Utilities menu, or set up your computer to automatically run a backup as often as you like! We recommend backing up four separate ways and testing your backups regularly.

The Active Directory is backed up using the NTBACKUP.EXE utility. The Active Directory is part of the machines System State which is defined as follows: For all Windows 2000 machines the System State includes the registry, class registration database and the system boot files. For a Windows 2000 Server that is a certificate server it also contains the Certificate Services database.

you know an incremental backup only backs up those files that have changed since the last backup and then sets them as backed up so this type of backup should be quite fast. In the event of a failure you would have to first restore the normal backup and then any subsequent incremental backups. Differential backups and incremental backups are the same except that differential does not mark the files as backed up, therefore files backed up on Monday will still be backed up on Tuesday etc.

Sometimes files can be corrupted as a backup program will try to backup an open file and when restored the file is corrupt. To stop NTBACKUP from backing up open files perform the following Check "Backup files in use". If it is set to 1 double click on the value and set to 0. Click OK If you do have "Backup files in use" set to 1 then you should also set the following parameter For more information have a look at Q159218 (http://support.microsoft.

The operator performing the backup requires the "back up files and directories" user right. This can be given directly using user manager, or the preferred way is to make the user a member of either the Administrators group or the backup operators group.

In general, rdiff-backup does not strive to make newer clients compatible with older servers (or vice versa). However, there is no intention to purposefully make different versions incompatible across the network -- changes are introduced primarily to fix bugs or introduce new features that cannot be implemented without breaking the network protocol. Furthermore, rdiff-backup does try to make it possible to read older archives.

Yes, however you will likely need to specify the "-o workaround=rename" option to sshfs, which is available in sshfs 1.3 and newer. On MacOSX, this sshfs option is enabled by default. For more information on this option, see the sshfs FAQ. More information about using sshfs and rdiff-backup is available on the rdiff-backup wiki.