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

This article is about how to make Active Directory backups. The editor thinks it is very practical, so share it with you as a reference and follow the editor to have a look.

Backup to network share

Backing up to a network share is as easy as backing up to a local volume. The main difference between the two is that it cannot create Volume Shadow copy Service snapshots of remote volumes. Therefore, each full backup overwrites the previous full backup, leaving you only the full backup image of each server on the network share. Because of this limitation, you cannot use the Windows Server Backup scheduler to schedule backups to a network share. However, you can use Windows Task Scheduler to run the WBADMIN command line program to perform a full backup to the network share. If you choose to schedule a full backup to a network share in this way, change the destination folder for each backup to avoid overwriting the previous backup.

Backup to recordable DVD

Windows Server Backup also supports backup to optical media, such as writable DVD. You can also create backup sets that contain multiple volumes. Windows Server Backup always compresses backups to DVD, which means that you can only restore full systems or volumes from DVD. Windows Server Backup does not support using DVD to perform system state or file-level backups and restores. Also, you cannot schedule backups to DVD.

System state backup and restore

System state backup, which includes only the selected files and some application databases (not the entire volume), is simple but usually critical. However, system state backup and restore are not supported in earlier versions of Windows Server 2008. The backup tool backs up only critical system volumes (that is, any volumes necessary to restore and restart the operating system and critical applications). These critical system volumes are equivalent to volume-oriented system state backups.

In response to the request of customer feedback, Microsoft added system state backup and restore functions to Windows Server Backup. The application creates multiple VHD files, one VHD file for each volume that hosts system state data, but it copies only the necessary files and databases to VHD. Another problem is that when you perform a system state backup, Windows Server Backup does not create a snapshot of the target volume, which is different from the normal backup process. Instead, each system state backup produces an entirely new set of VHD files, which means that snapshot-based volume backups do not have the same space efficiency.

You can only use the WBADMIN.EXE command line program to perform system state backups-this option is not available in the MMC snap-in. To perform a system state backup, use the following command:

C:\ > wbadmin start systemstatebackup-backuptarget

WBADMIN then backs up critical system files and application databases to the target volume (in the folder reserved for system state backups). System state backups run slightly larger than 6GB on a 32-bit Windows Server 2008 domain controller (DC) with a default directory information tree (DIT)-this is larger 5GB than on Windows Server 2003, in part because Windows Server Backup captures core operating system files that NTBACKUP does not capture.

As you might expect, it takes longer to back up the state of the system. Of course, these initial numbers are based on the pre-release version of the operating system. You must test this in your own environment, and if you want to move the domain controller to Windows Server 2008, you need to plan for larger system state backups (and longer backup times).

Back up the server using MMC

When running Windows Server Backup MMC (see figure 2), you can choose to set up a backup schedule or run a specific backup immediately. In this example, I choose "Backup once" (backup now) to perform the backup immediately.

Figure 2 Windows Server Backup MMC (click the image for a larger view)

As you can see in figure 3, I can choose whether to back up all the volumes on the server or only the selected specific volumes. If you select Full server (full server), Windows Server Backup will back up all mounted volumes, but I cannot back up to a mounted hard drive-only to a recordable DVD or network share.

Figure 3 Using the backup configuration dialog to specify all or select volumes (click the image for a larger view)

In this example, I want to back up to my local hard drive, so I choose the "Custom" option. Then a dialog box is displayed asking me to select the volume to back up (see figure 4). By default, Windows Server Backup checks the "Enable system recovery" box, which allows Windows Server Backup to select boot volumes, operating system volumes, and any other volumes with critical system files and application databases. On DC, this includes volumes that host SYSVOL, Active Directory DIT, and Active Directory logs. This is equivalent to a system state backup, but it backs up all critical volumes, not just the critical files on those volumes. In fact, I can even perform a system state restore from the system restore backup set.

Figure 4 Selecting specific volumes to back up (click the image for a larger view)

After selecting the destination type (local drive or network share) and specifying the destination, Windows Server Backup prompts me to choose either "VSS copy" (VSS copy) backup or "VSS full" (VSS full) backup. The term is a bit confusing because both options make a full backup of the selected volume. The difference lies in how Windows Server Backup handles source files after they are backed up. "if you select the copy option, Windows Server Backup keeps the backed up files as is." If you select the full option, Windows Server Backup will then reset the archive.

Back up the server from the command line

If you want to script the backup process, or back up the server on a Server Core installation, you can use the WBADMIN.EXE command line program. WBADMIN provides a complete set of options that perform essentially the same functions as the MMC snap-in, including managing backup schedules.

Suppose I want to start the WBENGINE service, which then performs a backup. I only need to enter the following command:

C:\ > wbadmin start backup-include:c:,d:-backuptarget

To back up all critical system volumes, enter the following command:

C:\ > wbadmin start backup-allcritical-backuptarget

After you start the backup, WBADMIN continues to run and displays the progress of the backup. If the WBADMIN is terminated, the backup continues to be performed in the background. You can then reconnect the WBADMIN to the running backup using the following command:

C:\ > wbadmin get status

If you want to terminate a running backup, simply enter the following:

C:\ > wbadmin stop job

Schedule backups using MMC

The backup scheduler integrated with Windows Server Backup is actually dedicated to the task of simplifying the daily schedule for full system backups of local disk volumes. You can use the built-in scheduler to automatically rotate backups among multiple target volumes. If you have a removable hard drive (or are using a USB-connected hard drive), you can use this feature to establish a conversion scheme where you remove the backup disk, store it externally, and return the earliest backup disk to the server for the next scheduled backup.

The Windows Server Backup scheduler only lets you schedule backups that always occur daily. That is, there is no separate way to schedule backups for individual Mondays, Wednesdays, and Fridays. Therefore, if you do not want to run scheduled backups every day, you must use Windows Task Scheduler directly.

When a scheduled backup to the local disk is established, Windows Server Backup is responsible for the disk, that is, formatting the disk, establishing a specific folder structure, and making the target disk not displayed in Windows Explorer. The destination disk must be a basic volume-Windows Server Backup cannot back up to a disk that is configured as a dynamic volume.

It is easy to schedule backups through the MMC snap-in. In this example, I first select the "Backup Schedule" link, specify the backup type and the volume to back up, and then Windows Server Backup displays the "Specify backup time" dialog box (see figure 5).

Figure 5 Specifying when daily backups should occur (click the image for a larger view)

After selecting the time that I want the backup to be performed, I can select one or more target volumes for the backup. In this example, I select the backup volume ERO, as shown in figure 6. Windows Server Backup will try to choose a suitable target volume for you, but if the destination disk you want to back up does not appear, you can use the "Show All Available Disks" button to view all attached disk devices. After two "confirm" dialog boxes are displayed, Windows Server Backup formats the target volume and uses Windows Task Scheduler to schedule the backup task.

Figure 6 Specifying the destination disk for a scheduled backup (click the image for a larger view)

"each time a scheduled backup completes, Windows Server Backup takes a snapshot of the target volume." And every seven days, it creates a new base image. The activity is recorded in the Microsoft/Backup/Operational log. There you can check that the backup completed successfully, or you can associate a task, such as sending an email message, with success and failure events so that you always know the status of the scheduled backup.

Schedule backups from the command line

If you are planning backups on your Server Core installation, or if you just want to script the process, you can use the WBADMIN command line to manage the backup schedule. To add a scheduled backup, use the WBADMIN ENABLE BACKUP command to specify the destination, source, and scheduled time, as follows:

C:\ > wbadmin enable backup-addtarget:e:-include:c:,d:-schedule:06:00,12:00,18:00

This command backs up the C: and D: drives to the E: drive three times a day at 6:00, 12:00, and 6:00 (note that all times are specified using the 24-hour system.) To back up all critical system volumes from which a bare metal restore or system state restore can be performed, use the-allcritical replace-include switch.

"you can also disable all scheduled backups using WBADMIN, as follows:"

C:\ > wbadmin disable backup

This command deletes all scheduled backup work created by the Windows Server Backup scheduler and frees all backup target volumes for normal use. Note that you can always use the WBADMIN MMC snap-in to remotely manage backup and restore activities for Server Core servers.

Thank you for reading! This is the end of the article on "how to make Active Directory backup". I hope the above content can be of some help to you, so that you can learn more knowledge. if you think the article is good, you can share it out for more people to see!

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.