Shulou(Shulou.com)05/31 Report--

How to interpret the Server 2008 subsidiary backup tool Ntbackup, I believe that many inexperienced people do not know what to do, so this paper summarizes the causes of the problem and solutions, through this article I hope you can solve this problem.

For many years, the Ntbackup program has been an accessory tool of the Windows system. Although the old version of the tool never included many of the hot features seen in commercial backup programs, the Windows Server Backup features for Windows Server 2008 are completely different from previous versions.

On the face of it, Microsoft has decided to simplify the tool. I say this because the new version no longer allows you to back up individual files or folders. Instead, you have to back up the entire volume, even if you are really only interested in a file.

When I first saw this new backup interface on Windows vista, I was disappointed, but I think Microsoft was trying to make it easier for users to back up their computers. But when I found that the same version was applied to Windows server 2008 in the same way, I was completely shocked. Despite the results, there are still a lot of places in the new version that don't just satisfy the vision. Although I may disagree that Microsoft's decision reduces our flexibility when using NTBackup, they do so for a number of reasonable reasons.

The main reason is that the new Windows server backup developed by Microsoft will be smarter. after all, backup is the first line of defense after a disaster, and losing data because backups are not configured correctly is a real disgrace.

Improve disk space management

Microsoft Windows server backup includes a new data management mechanism, which is automatic disk space usage. For example, suppose you are writing your backup data to a network volume or external hard drive. With NTbackup, you have to plan repeated backups in some way to prevent volumes from running out of disk space. With Windows server 2008, you can automatically manage the disk space that contains backup volumes anyway. If Windows Server Backup finds that the volume does not have enough space to save a backup, it automatically deletes one or more old backups to provide space for the new backup.

Block level backup

Another good change to Windows server backup is the use of block-level backups, which means that its incremental backups will be smaller and faster than NTbackup's. This is because incremental backups are usually backups of files that have changed since the last full backup. Windows Server Backup follows this approach, but instead of backing up the entire changed file, it backs up only the changed blocks.

The same block-level backup technique is also applied to file repair because Windows Server Backup is version-aware. Therefore, instead of manually recovering data from multiple increments, Windows server 2008 allows you to select the files you want to restore and then determine the backup date you want to use.

Off-machine recovery backup

It is also possible to restore Windows to replacement hardware through Windows server backup. In my years with Windows server 2003, I was only able to restore one backup to another server (that is, everything went well but followed by a number of failures that I had to deal with). In fact, Windows Server 2008 requires that the replacement hardware be the same as the original server as much as possible; however, even so, it makes the whole process quite easy.

System volume recovery

In the end, my view is that the progress of Windows server backup*** is that it can recover after the loss of server system volumes. If you lose the system volume on Windows server 2003, you can only hope that the drive has a full, system-state backup. Suppose you do that, then you need to replace the drive, restore the Windows, install the correct patch pack, adjust a large number of backup settings, and restore the backup. This fix works, but it's tricky to get the process right.

Windows Server 2008 allows you to do bare metal recovery on your new hard drive without installing Windows. This greatly reduces the total time it takes to recover the system in the event of a failure, but more importantly, it increases the chances of a successful recovery of the server-mainly because you don't need to do complex operations to overwrite existing operations as you do on Windows server 2003.

As you can see, Microsoft has made a lot of improvements to the backup tool of Windows server 2008.

After reading the above, have you mastered how to interpret the Server 2008 subsidiary backup tool Ntbackup? If you want to learn more skills or want to know more about it, you are welcome to follow the industry information channel, thank you for reading!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.