Shulou(Shulou.com)06/01 Report--

I would like to share with you how to solve the backup problem of windows 2003 domain controller. I believe most people don't know much about it, so share this article for your reference. I hope you will learn a lot after reading this article. Let's take a look at it!

Whether the domain control can use ghost backup and whether the reinstallation system can use the backup data of ntbackup to restore the system state is a problem that people often encounter when using domain controllers. Let me briefly talk about this problem:

First of all, let's understand the difference between ghost and ntbackup. Ntbackup is a system state backup tool that comes with windows. It can back up the system status in real time. The system can be restored when the system is damaged and the operation after the damage is not damaged. It can be understood as a way of patching the system after backup. Ghost's work is aimed at hardware partitions. It cannot back up a system state or a program group. It can only be used to mirror the entire partition. To be clear, it's not a backup function. It's a mirror function. It can only be restored to a certain mirror creation time. And the files that are mirrored cannot still exist after recovery and are completely overwritten. So they are two essentially different pieces of software.

Second, if only from a technical point of view, ghost is available, but in the actual environment is not recommended to use ghost. Most of the facts in the past have proved that there will be a lot of problems in ghsot backup domain control restore, which eventually lead to the system can not be restored to the original condition. Let's look at three questions:

1. If the primary DC hard drive is damaged and must be replaced, can I reinstall the system and restore it with ntbackup after replacing the hard drive?

2. If the main DC motherboard is broken, the machine must be replaced. Can I still use ntbackup?

3. If the secondary DC has to be removed suddenly due to a hardware failure, can I use the Ntbackup backup of the secondary DC to restore on a new system on a new secondary DC?

The answers are as follows:

1. Yes, and this operation risk is very small, but you must have a backup of system state data within 60 days. After reinstalling the system, you must upgrade to a domain controller and then restore the system state data.

2. Yes, Microsoft has a KB to guide you to solve this problem, but you still need a full backup of the boot disk and a backup of system state data within 60 days. Now HAL rarely causes blue screen problems, which are basically caused by storage drivers. Of course, there is still a risk, which is not so convenient, so it is recommended that you add additional DC to prevent this kind of disaster.

3. If you have extra DC, you don't have to deal with it this way; you can clean up the original DC information in AD and add the new computer to AD as an extra DC.

Generally speaking, the significance of backup and restore of AD lies not in disaster recovery, but also in recovery after mismodification of data.

1. If the hard drive is broken, if you have done raid, you can directly replace the hard drive without reinstalling the system. Of course, it depends on what kind of RAID you are doing and how many hard drives are broken. In this case, it can be restored with ntbackup.

two。 If the motherboard is broken, ntbackup depends on whether your new motherboard is exactly the same as the old motherboard. If so, ntbackup is possible, or even lucky, even the restore operation is not needed, you can start to provide services directly. If the model is different, it is not recommended to use ntbackup to restore previous backups.

3. In theory, the hardware of the new auxiliary DC must be exactly the same as the existing secondary DC hardware configuration before the restore operation can be performed, but there will be no problem with similar models, such as restoring HP 380G4 to HP 380G5.

Third, the general server will use to do raid to achieve high availability and high reliability of the server. In common raid1,raid5 and other ways, even the physical failure of a certain number of disks does not affect the normal operation of the server.

In addition, this backup tool has changed a lot since the advent of windows2008. Compared with the previous version of the system backup tool, 2008 has made the following changes:

1. When you upgrade to Windows Server 2008, the settings that create backups are not upgraded. two。 You cannot use Windows Server Backup to restore backups created with Ntbackup.exe. 3. A separate dedicated disk is required to run the scheduled backup. Only volumes in NTFS format on locally attached disks can be backed up. 4. You can no longer back up to tape.

The 2008 backup tool also brings us some new features as follows: 1. A simplified restore. two。 Faster backup technology. Windows Server Backup uses Volume Shadow copy Service (VSS). The improvement to VSS is a big improvement in 2008. 3. Simplified operating system recovery. 4. Restore the functionality of the application. 5. Improved planning capabilities. 6. Delete backups offsite for disaster protection. 7. Remote management. 8. Automatic disk usage management. 9. Extended command line support. 10. A new command line tool, WbBackup.exe. 11. Optical media drives and removable media are supported.

The above is all the contents of the article "how to solve the backup problem of windows 2003 domain controller". Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!

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.