Highlighted
Thierry101
2 Iron

AD backup

Jump to solution

Hi all

Using 7.6.3.7...currently reconfirming DC backups which was configured by others..now supporting this

AD/DC is VM.

As pre guide

Backing up Active Directory

The NetWorker software automatically backs up AD as a component of the SYSTEM

STATE or VSS SYSTEM BOOT save set. An AD backup or restore includes the AD log

files, database, patch files, and expiry token.

Group called have DC clients in it and save set

VSS SYSTEM BOOT:\

VSS SYSTEM FILESET:\

VSS SYSTEM SERVICES:\

VSS USER DATA:\

VSS OTHER:\

Nothing in Apps & Modules tab

is that all needed to recover DC? SYSTEM STATE need to be added as per guide?

Any files within drives?

Thanks

Tags (4)
0 Kudos
1 Solution

Accepted Solutions
TimQuan
3 Zinc

Re: AD backup

Jump to solution

A full backup of the DISASTER_RECOVERY:\ save set backs up all of the critical volumes.

The following volumes are considered critical and are included in the disaster recovery backup:

◆ Any volume that contains operating system files or files needed by an installed service.
◆ A non-critical volume that has a critical volume mounted on it, or a non-critical volume that serves as a parent to a critical volume.
◆ All volumes on all dynamic disks if at least one of those volumes is critical.

So as long as Drive C is a system drive, it will be considered as a critical volume and will be backed up if you specify DISASTER_RECOVERY:\ save set.

The easiest way to backup DC is to specify the following save sets:

All
VSS SYSTEM BOOT:\
VSS SYSTEM SERVICES:\
VSS SYSTEM FILESET:\

Since the save set All cannot be listed with other save sets, to backup a host using the All save set and the VSS SYSTEM save sets:

1. Create two NetWorker client resources for the host.
2. Specify the save set All in one resource and specify the VSS SYSTEM save sets in the other resource.
3. Ensure that each client resource is included in a separate backup group.

In addition, if you have NetWorker Module for Microsoft Applications (NMM) installed, I suggest using NMM to backup AD. It is the recommended way to backup AD as NMM is specially used to backup Microsoft applications. It will create snapshots and make AD backup faster and lower the workload of NetWorker server.

Besides, NMM supports granular backup and recovery of the following Active Directory objects:

◆ Users
◆ Groups
◆ Organizational units
◆ Computer
◆ Contact
◆ InetOrgPerson
◆ Shared folder
◆ MSMQ queue alias

~~~~~~~~~~~
Best Regards,
Tim
Please mark my reply as “Correct Answer” or “Helpful Answer” if it helps you. Thanks.

0 Kudos
4 Replies
TimQuan
3 Zinc

Re: AD backup

Jump to solution

Yes, this is correct for Windows 2003 clients. For Windows 2008 and Windows 7 clients, you should backup:

◆ DISASTER_RECOVERY:\
◆ VSS SYSTEM BOOT
◆ VSS SYSTEM SERVICES
◆ VSS SYSTEM FILESET

Alternatively, you can disable the backup of the special DISASTER_RECOVERY:\ save set and instead, backup the regular VSS save sets by adding the VSS:DISASTER_RECOVERY=off keyword to the Save Operations attribute of the NetWorker client resource. When this keyword is set to off and the All save set is specified, the following VSS save sets will be available for online restore operations:

◆ VSS SYSTEM BOOT
◆ VSS SYSTEM SERVICES
◆ VSS SYSTEM FILESET
◆ VSS OTHER
◆ VSS USER DATA

~~~~~~~~~~~
Best Regards,
Tim
Please mark my reply as “Correct Answer” or “Helpful Answer” if it helps you. Thanks.

0 Kudos
Thierry101
2 Iron

Re: AD backup

Jump to solution

Thanks Tim

So that's all needed for recovery? any AD drives (c:\drives content?) - need to backup or best leave without back them up?

0 Kudos
TimQuan
3 Zinc

Re: AD backup

Jump to solution

A full backup of the DISASTER_RECOVERY:\ save set backs up all of the critical volumes.

The following volumes are considered critical and are included in the disaster recovery backup:

◆ Any volume that contains operating system files or files needed by an installed service.
◆ A non-critical volume that has a critical volume mounted on it, or a non-critical volume that serves as a parent to a critical volume.
◆ All volumes on all dynamic disks if at least one of those volumes is critical.

So as long as Drive C is a system drive, it will be considered as a critical volume and will be backed up if you specify DISASTER_RECOVERY:\ save set.

The easiest way to backup DC is to specify the following save sets:

All
VSS SYSTEM BOOT:\
VSS SYSTEM SERVICES:\
VSS SYSTEM FILESET:\

Since the save set All cannot be listed with other save sets, to backup a host using the All save set and the VSS SYSTEM save sets:

1. Create two NetWorker client resources for the host.
2. Specify the save set All in one resource and specify the VSS SYSTEM save sets in the other resource.
3. Ensure that each client resource is included in a separate backup group.

In addition, if you have NetWorker Module for Microsoft Applications (NMM) installed, I suggest using NMM to backup AD. It is the recommended way to backup AD as NMM is specially used to backup Microsoft applications. It will create snapshots and make AD backup faster and lower the workload of NetWorker server.

Besides, NMM supports granular backup and recovery of the following Active Directory objects:

◆ Users
◆ Groups
◆ Organizational units
◆ Computer
◆ Contact
◆ InetOrgPerson
◆ Shared folder
◆ MSMQ queue alias

~~~~~~~~~~~
Best Regards,
Tim
Please mark my reply as “Correct Answer” or “Helpful Answer” if it helps you. Thanks.

0 Kudos
Thierry101
2 Iron

Re: AD backup

Jump to solution

Thanks Tim!

But using NMM to backup AD with DDBoost not supported

NMM2.3 Admin G pg 86

Not supported

The Data Domain Boost on NMM client is not supported for the following Microsoft

applications:


Active Directory

DPM Server

Exchange Server 2003

Exchange Server 2007

Hyper-V

SharePoint Server 2007 (VSS based)

SharePoint Server 2010 (VSS based)

SQL Server 2005

SQL Server 2008

0 Kudos