Master teaches you how to back up Active Directory

Because a sudden power outage damages all the drives of a domain controller, causing you to lose the results of years of work, or the crash of a domain controller, it is a nightmare for network administrators, then the Active Directory should How to backup? This tutorial will explain this problem to everyone. Before explaining this problem, you should first understand that the backup method selected should have enough ability to recover data files and Active Directory database. When choosing a software backup method and the hardware devices used, you can consider the following:

Server Mirroring

A real-time backup that can create identical data on the backup hardware. This can be done with a RAID1 system or with a full mirror server hardware device. This type of real-time backup is usually done locally. When the primary system is compromised, you can quickly fail over through mirroring, using a backup device.

Electronic Link

This backup method is to periodically transfer the changed file to a different location. Also known as batch processing. This offsite backup is not real-time, it provides a more appropriate method for you to recover the AD network when the main system receives serious damage.

Remote Logs

This real-time offsite backup transfers incremental (changed elements) instead of the entire changed file. When the primary system is severely damaged, it is a very reliable way to recover the AD network.

Database Image

The combination of server mirroring and remote logging allows for a variety of 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, it is the best choice for restoring AD.

Regardless of the method chosen, backup media, including tape, fiber and hard drives, must be guaranteed 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 of the backup media. At the same time, ensure that the connection between the primary data resource and the backup medium is sufficient to support the transfer of backup data. Real-time backup requires sufficient bandwidth to ensure 100% feasibility and uptime for instant change of information. Backups sometimes interfere with the capacity of the network. This requires the deployment of a second network with backup capabilities, especially in networks that work around the clock with high-level AD interaction.

Finally, please pay attention to the following points:

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

2. In a multi-domain control environment, if Seize is used, then the broken server should not be returned to the network before reinstalling the system. Even if it has been repaired, it must be reinstalled. Operating system, why? Because the FSMO role is unique, if you return to the network at this time, there will be a phenomenon of FSMO role duplication.

3, in the multi-domain control environment, after the bad domain control repair, reinstall the system, please try not to use the original computer name to prevent some unexplained problems, let that server It will disappear forever in the network!