Why do I need Windows Server Backup?

Orin Thomas
Microsoft has often reminded consumers that the NTBackup utility in the Windows NT 4.0, Windows 2000 and Windows Server 2003 is not a full-featured backup solution offerings. However, if you need many administrators used it that way. However, they can not use the new built-in tool Windows Server 2008 for large-scale archiving within the company as easy as NTBackup. The reason is a component functionality Windows Server Backup, which replaced the NTBackup utility in the Server 2008. This article discusses several differences between NTBackup and Windows Server Backup, and shows how, in some cases, you can bypass the appropriate limits. In addition, I will explain why it is useful to think about using a full-featured backup solution.

Problem 1
Windows Server Backup is not installed by default
Unlike utility NTBackup, which is installed by default with Windows 2003 and Windows 2000, Windows Server Backup is not installed by default in the operating system Server 2008. To use Windows Server Backup, please refer to the master Add Features, which allows you to install Windows Server Backup, and command-line utility wbadmin. Exe, used to back up your computer in Server Core.
In some cases the lack of built-in backup program delivers significant inconvenience. For example, asked to see the server administrator, whose behavior is questionable, but it appears that he has never been archived and new programs can not be installed on it. Before making any changes, make sure to back up the server, and the absence of the default Backup Server additionally difficult to diagnose. It is known that companies, especially small, often forget to back up until the accident occurred.
The only way to avoid the trap - install Windows Server Backup and wbadmin. Exe during deployment Server 2008. Yet the IT professional may have to examine the servers are never archived, and may not have the tool Windows Server Backup. Unfortunately, Server 2008 does not warn of the need to regularly back up with the same persistence as an automatic update. Thanks for such a warning only the most careless administrators could ignore Backup.



Problem 2
Lack of support for tape drives
One of the most striking features of the Windows Server Backup - lack of support for tape drives. This is not a typo: Windows Server Backup, and a command line utility wbadmin. Exe unsuitable for writing backups to tape. For this, there is at least one good reason: tape drives share the fate of the floppy disk. Modern hard drives not only provide storage for large amounts of data, but also much faster than the magnetic tape during backup and restore. However, most IT organizations have used magnetic tape, and the price is not good streamer low. In the transition to Server 2008, this expensive equipment may be useless.
When replacing a previous version of Windows Server 2008 on the company may refuse to obsolete equipment and variables to buy hard drives or use backup solution from another vendor. Also, you need to prepare a plan for the restoration of data stored on magnetic tape, after the full transition to Server 2008. Windows Server Backup can not import backups produced using NTBackup, and can not be used to recover NTBackup data archived by using Windows Server Backup. But Microsoft released version of NTBackup, intended only for data recovery, at go. Microsoft. Com / fwlink /? LinkId = 82917. With this version of NTBackup can read data from the tape, but did not record them. Consumers can retrieve previously recorded historical data from the tape, only then tape useless. Designed to use only readable version NTBackup tape drive, you need the correct driver for the tape drive Server 2008. Since Windows Server Backup does not work with the tape, some manufacturers have been reluctant to support tape Server 2008.

Problem 3
For routine requires a dedicated backup disk
To store scheduled backups in Windows Server Backup requires a dedicated disk (not just section). When a new disc is recorded the first backup copy, the disk is divided into partitions and formats. Can not be used for any purpose other than archival data, and can not be seen in Windows Explorer Windows. Using Windows Server Backup to write data to the internal hard drive or on a disc that is compatible with USB 2.0 or IEEE 1394. As recommended by Microsoft, the disk capacity should be approximately two and a half times larger than the amount of data a full backup, and the minimum amount of data being backed up is a volume. Windows Server Backup mode by default: full backup and subsequent incremental backup operations. Windows Server Backup automatically deletes the oldest backup, when the disk runs out of space. The purpose of this approach - to appoint a scheduled backup, and then forget about it until then, until it is time to recover.
This method is quite good for a basic backup solution, but would not like managers who are accustomed to the settings of NTBackup. Can be a time to copy to a network drive or an optical drive, but you can not schedule a backup to these devices. Resourceful administrator can prepare a script called targets, which uses a utility wbadmin. Exe to store the backup, but did not get a message about the presence on the target disk has enough space for the successful completion of the backup. Expanding the boundaries of the planned backup is possible, but should not rely on dangerous techniques, as it is noticed administrators.
Because of the need to allocate disk rotation hindered remote backups. Many companies set backups are transported in a safe place each week to recover data if the building burns down, go under the water and will be destroyed meteorite. Principle of Windows Server Backup is based on the assumption that that is tied to the backup server, and is unlikely to be moved to a remote location. If it is important to restore data after a crash, should look for a comprehensive solution.

Problem 4
Tom - the minimum unit of archival
Unlike utility NTBackup, you can use to back up individual files and folders, the minimum unit of backup using Windows Server Backup - a volume. The reason for this limitation, the following: in Windows Server Backup uses full disk image instead of just writing to files and folders, with a contraction in the binary "lump". However, you can restore individual files and folders.
Many administrators are surprised that using Windows Server Backup can back up only the system state. You can back up the system state using the command start systemstatebackup utility wbadmin. Exe, but not all administrators are used to perform a relatively simple task from the command line.
Why utility Windows Server Backup?

For optimal use Windows Server Backup to remember that the utility is not designed to back up at the company level. Many administrators are unhappy with this fact, because that is how they used NTBackup decade. If we consider the Windows Server Backup, according to its true potential - WordPad archiving of programs - it turns out that the utility is consistent with its purpose. If you apply the Windows Server Backup to schedule a regular backup to a removable disk or internal hard drive, it is very easy to completely restore the operating system Windows. Windows Server Backup should not be used to back up Exchange Server or SQL Server, but the NTBackup utility is not designed for this purpose.
Orin Thomas (orin @ windowsitpro. Com) - Editor of Windows IT Pro, certificate holder Windows Security MVP