Recovery Manager for AD 10.3.1 - User Guide

How do I change the Backup Agent port number?

RMAD uses a TCP port to communicate with Backup Agent installed on the target domain controllers to be backed up. To change the Backup Agent port number, perform the following procedures.

On each target domain controller to be backed up, perform the following steps:

1. Start Registry Editor (Regedit.exe), and then locate the registry key:

   HKLM\SYSTEM\CurrentControlSet\Services\ErdAgent

2. In the details pane, double-click the ImagePath value, and in the Value data text box, specify the port number in the following way:

   %SystemRoot%\RecoveryManagerAD\ErdAgent.exe -I -P:3899

   In this example, Backup Agent will use port 3899. When finished, click OK.

3. Close Registry Editor.

4. Restart the Backup Agent service.

Start the Recovery Manager for Active Directory Console (snap-in), and then perform the following steps:

1. In the console tree, select the node RMAD, and then on the Action menu, click Settings.

2. On the Ports tab, select the Connect to Backup Agent using a specific TCP port. check box, and then specify the port number in the Port text box.

3. Click OK to close the Recovery Manager for Active Directory Properties dialog box.

How and where is LDAP used in RMAD?

When is LDAP used in RMAD?

LDAP is used to search AD-LDS (ADAM) to retrieve Active Directory object information. During the Online Restoration (agentless and agent-based) and Group Policy Restoration, the LDAP API is used to perform modifications to specified Active Directory objects.

Is LDAP used to authenticate?

RMAD does not use LDAP for authentication of credentials or for Domain Controller connectivity. RMAD is using LDAP version 3, and the password is not in plain text, but is "encrypted". RMAD uses the Generic Security Services Application Program Interface (GSSAPI) to authenticate user logon. GSSAPI is included in the Kerberos protocol.

Is LDAP used to transfer data from AD during backups?

RMAD does not use LDAP for transfer, but deploys a Backup Agent to the domain controller. The Backup agent will collect data and make a backup file. If you store the backup file on console side, the backup file will be transfer by encrypted RPC protocol; if you use Remote Storage and assign a UNC path, the backup is copied by SMB protocol. The user can assign a password to encrypt the backup file.

Best practices for using Computer Collections

It is recommended to add computers to the same Computer Collection if you want to do any of the following:

• Back up the same System State components on all these computers.

• Apply the same backup storage policy to all these computers.

For instance, you may want to store domain controller backups in one central location accessible to the Recovery Manager Console over a fast link. This scenario eliminates the need to copy the backups across the network before running an online restore operation and allows you to centrally manage the restore.

• Set up the same backup creation schedule for all these computers.

The following diagram provides an example of using Computer Collections:

Example of Using Computer Collections

In this example, the Recovery Manager Console is installed in the London site. Computer Collections 1, 2, and 3 include all domain controllers from the Tokyo, London, and New York sites, respectively. Computer Collection 4 includes two domain controllers from the London site. Backups of these two domain controllers are accessible to the Recovery Manager Console via a fast link and can be used to perform selective online restores of Active Directory® objects.

Technical characteristics

This section provides some technical characteristics of the product.

• Typical sizes of databases

• Typical backup creation times

• Typical times to unpack backups