Originating Author: Nicholas Allen
For some users, it might be a good idea to let the Exchange administrator handle first level backups and restores. The key advantage here is expediency. Only one organization needs to be involved when Exchange data needs to be recovered.
NTBackup is the built-in backup utility of Microsoft Windows, introduced in Windows NT around 1997 and part of all subsequent versions up to and including Windows Server 2003, Windows 2000 and Windows XP. It uses a proprietary backup format (BKF) to backup files. It also supports backing up files to tape, but not very well, and we don’t recommend it.
NTBackup from Windows XP and later includes Volume Shadow Copy (VSS)(see The_chicken_and_egg_of_VSS) support and thus can backup locked files. Microsoft also includes integrated VSS Requestor/Writer/Provider software for Exchange.
In Windows Vista and later operating systems, NTBackup was replaced by Windows Backup, which uses the Virtual Hard Disk (VHD) file format and supports backing up to modern media such as CDs/DVDs. For reading older backups, Microsoft has made available the NTBackup Restore utility which can only read BKF files.
Many shops have found that they can delegate responsibility for first level Exchange backups to the Exchange administrator who creates these BKF files using NTBackup. Then the storage team subsequently backs up these files using a more robust BURA infrastructure.
But NTBackup is not for everybody. Many users use third-party BURA software such as Backup Exec across the entire shop and not just for Exchange. Responsibility for this infrastructure clearly falls in the storage camp and not the Exchange administrator.
Action Item: Consider delegating first level Exchange backup and restore to the Exchange administrator.
Footnotes:
