How to easily back up windows active catalogs

Because a sudden blackout damages all the drives of a domain controller, makes you lose the results of years of work, or the crash of a domain controller, which is a nightmare for network administrators, how should the Active Directory be backed up? The small part of XP system to explain this problem, before explaining this question, The first thing you need to know is that the backup method you choose should have sufficient ability to recover data files and Active Directory databases. When choosing a software backup method and the hardware devices you use, consider the following:

Server Mirroring

A real-time backup in which identical data can be created on the backup hardware. It can be done through the RAID1 system or with a full mirror server hardware device. This real-time backup is usually done locally. When the primary system is compromised, you can quickly failover through mirroring, using the backup device.

Electronic links

The backup method is to periodically transfer the changed files offsite. Also known as batch processing. This offsite backup is not real-time and provides a more appropriate way for you to recover ad networks when the primary system is severely compromised.

Remote Log

This real-time offsite backup delivers incremental (changed elements) rather than the entire change of the file. It is a very reliable way to recover ad networks when the primary system is severely compromised.

Database image

The combination of server mirroring and remote logging can create multiple local and offsite backups. This real-time backup can be local or offsite. This method is the most expensive, but when the domain controller is affected by any impact, it is the best choice to recover ad.

Whichever method you choose, you must ensure that your backup media, including tape, fiber, and hard disk drives, have sufficient capacity to meet current and short-term needs. The size of the ad database increases every week, so plan ahead to take full advantage of the storage space in the backup medium. It is also necessary to ensure that the main data resource and the connection line in the backup medium are sufficient to support the transfer of backup data. Real-time backup requires sufficient bandwidth to ensure 100% feasibility and uptime, allowing for the transmission of real-time change information. Backups can sometimes interfere with the capacity of the network. This requires the deployment of a second network with functionality, especially on a 24x7 network with high-level ad interactions.

Finally, please note the following points:

1, in a single domain control environment, please try to backup as much as possible to ensure the validity of backup, the best several types of backup to use together.

2, in a multi-domain control environment, if the use of seize, then the broken server in the reload system before please do not return to the network, even if it has been repaired, you must reinstall the XP system, why? Because FSMO roles are unique, if you return to the network at this time, Then there is the phenomenon of FSMO role duplication.

3, in a multi-domain control environment, the bad domain control repair, reload system, please try not to use the original computer name, in order to prevent some inexplicable problems, let that server in the network forever disappear!