Recovery Manager for Active Directory employs the following database files (.mdb):
ERDiskAD.mdb. Recovery Manager for Active Directory configuration database. It contains information on the console configuration, such as the managed Computer Collections, backup creation sessions, etc.
Backups.mdb. Recovery Manager for Active Directory backup registration database. It contains information on the registered Active Directory and AD LDS (ADAM) backups.
As a rule, the file size for .mdb files does not exceed 10 MB.
The database files are stored in the folder %AllUsersProfile%\Application Data\Quest\Recovery Manager for Active Directory.
The Online Restore Wizard provides comparison and restore reports based on per-attribute comparisons of directory objects selected from a backup, with their counterparts in Active Directory or another backup.
Recovery Manager for Active Directory incorporates Microsoft SQL Reporting Services (SRS). Microsoft SRS is the new reporting standard, replacing the XML-based comparison and restore reports offered by previous versions. For more information, refer to the User Guide supplied with this release of Recovery Manager for Active Directory.
The size of the reports database file depends on the following parameters:
Number of the directory objects the Online Restore Wizard has processed.
Number of the processed attributes.
Type of the processed attributes.
Number of the available Online Restore Wizard sessions. Note that the information on all sessions is stored in a single reports database file.
To estimate the reports database file size, use the following empiric formula:
6 x <Number of processed objects>/1000 [MB]
For example, if the Online Restore Wizard has processed 3000 objects, the reports database file size will be approximately 18 MB.
This section provides some best practices for backing up Active Directory data using Recovery Manager for Active Directory.
It is recommended to follow these rules to prevent Active Directory failure:
Use only reliable and tested hardware, such as hard disks and uninterruptible power supply.
Test any new configuration in a test lab before deploying it in your production environment.
Ensure that each domain in your Active Directory forest has at least two domain controllers.
Keep detailed logs about the health state of Active Directory on a daily basis, so that in case of a forestwide failure you could identify the approximate failure time.