I was asked recently if Disk-to-disk-to-tape backup was possible in BackupAssist.
The answer is YES, if your tape drive sits on a Windows 2003, XP or 2000 machine. Note: Our support for tape drives in Server 2008 is still in development, and is due out in July.
There are two main scenarios for this:
- Replicate your file system to disk on a dedicated backup server, and then to tape (tape drive is installed on the backup server) – you can even backup multiple servers to the one backup server, then take those backups to tape.
- Replicate to disk on the same server, and then to tape (tape drive installed on same server)
In both situations, the setup is the same:
On each of your source servers
- Set up a “File Replication” backup job in BackupAssist. Choose your destination device (for same server D2D2T, it will be a local or external hard drive; for backup server D2D2T choose a NAS / network location). Select the “Mirror” scheme, so that your destination will be a mirror of the source. Select your files and folders to replicate, and complete the wizard.
- If you are also backing up VSS aware applications (eg. Exchange 2003/7, SQL 2005/8), go to the “Open files” tab and check the checkbox to enable VSS writer support. This means that your applications will be in a consistent state when backed up.
On your server with the tape drive installed
- Set up a “NTBackup” job in BackupAssist. Then choose the Tape Drive destination, choose your media rotation strategy, select the paths to backup, and complete the wizard.
- Modify the job run time to give the File Replication job(s) plenty of time to complete before the Tape job starts.
This setup requires one BackupAssist license per source server, and also one on the server with the tape drive.
If you are performing the D2D2T on the one server, then only one license is required.
We recommend this strategy when your primary concern is backing up and protection data – that is, files and folders, and VSS aware applications.
The BackupAssist File Replication Engine will not backup System State in the way that NTBackup.exe or wbadmin.exe will – so if you need to protect the System State, you will need to set up a different job to do this.