Recovery Manager for AD 10.3.2 - User Guide

Typical sizes of databases

Configuration database files

Recovery Manager for Active Directory employs the following database files (.mdb):

• Rmad.db3. RMAD configuration database. It contains information on the console configuration, such as the managed Computer Collections, backup creation sessions, etc.

• Backups.mdb. RMAD 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.

Reports database files

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.

RMAD 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 RMAD.

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 empirical formula:

• 6 x <Number of processed objects> / 1000 [MB]

For example, if the Online Restore Wizard has processed 3,000 objects, the reports database file size will be approximately 18 MB.

Best practices for creating backups

This section provides some best practices for backing up Active Directory® data using RMAD.

Develop a backup and restore plan

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 forest wide failure you could identify the approximate failure time.