The table below lists the minimum user account permissions required to access the SQL reporting database.
Table 3: Minimum permissions
|To access the SQL reporting database||
To access the SQL reporting database (%ProgramData%\Quest\Recovery Manager for Active Directory\DBReporting\RecoveryManager-Reporting-<host name>), the account must be assigned to db_datareader, db_datawriter roles and have rights to execute all the usp_* procedures, as follows:
It is recommended to add computers to the same Computer Collection if you want to do any of the following:
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.
The following diagram provides an example of using Computer Collections:
Figure 1: 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.
This section provides some recommendations for performing granular restore operations with Recovery Manager for Active Directory.
With Recovery Manager for Active Directory, you can access the target domain controller by using either LDAP functions (agentless method) or Restore Agent supplied with Recovery Manager for Active Directory (agentbased method). Each of these methods has its advantages, limitations, and requirements.