Chat now with support
Chat with Support

Recovery Manager for AD Disaster Recovery Edition 10.0.1 - User Guide

Overview Backing up data
Permissions required for the Backup operation Managing Backup Agent Using a least-privileged user account to back up data Creating backups Retrying backup creation Enabling backup encryption Backing up AD LDS (ADAM) Backing up cross-domain group membership Backing up distributed file system (DFS) data Backup scheduling Setting performance options Setting advanced backup options Using Forest Recovery Agent Unpacking backups Using e-mail notification Viewing backup creation results Getting started
Permissions required to use Recovery Manager for Active Directory Recovery Manager Console Icons in the user interface Getting and using help Configuring Windows Firewall Using Computer Collections Managing Recovery Manager for Active Directory configuration Licensing
Restoring data
Getting started with Active Directory recovery Managing deleted or recycled objects Restoring backed up System State components Using granular online restore Restoring AD LDS (ADAM) Selectively restoring Active Directory object attributes Restoring objects in an application directory partition Restoring object quotas Restoring cross-domain group membership Performing a restore without having administrator privileges Reports about objects and operations Using complete offline restore Offline restore implications Restoring SYSVOL authoritatively Performing a granular restore of SYSVOL Recovering Group Policy Restoring data from third-party backups Using the Extract Wizard Restoring passwords and SID history
Fault tolerance Consolidating backup registration data Monitoring Recovery Manager for Active Directory Recovering an Active Directory forest
Permissions required to use Forest Recovery Console Forest Recovery Console Managing a recovery project Install Active Directory from Media recovery method Install Active Directory recovery method Managing Forest Recovery Agent Rebooting domain controllers manually Specifying fallback IP addresses to access a domain controller Resetting DSRM Administrator Password Purging Kerberos Tickets Managing the Global Catalog servers Managing FSMO roles Manage DNS Client Settings Configuring Windows Firewall Forest recovery overview Selectively recovering domains in a forest Recovering SYSVOL Deleting domains during recovery Resuming an interrupted forest recovery Recovering read-only domain controllers (RODCs) Checking forest health Collecting diagnostic data for technical support
Bare metal forest recovery Using Management Shell Creating virtual test environments Using Recovery Manager for Active Directory web interface Appendices
Frequently asked questions Best practices for creating backups for forest recovery Best practices for recovering a forest Descriptions of recovery or verification steps Backup Wizard Online Restore Wizard Online Restore Wizard for AD LDS (ADAM) Group Policy Restore Wizard Repair Wizard Extract Wizard Events generated by Recovery Manager for Active Directory

Collecting diagnostic data for technical support

There may be a situation where technical support requests you to gather and supply diagnostic data from your computer collection. For this purpose, you can use a special tool provided in the Forest Recovery Console. This tool is called Diagnostic Data Collector.

NOTE: From version 8.7, the diagnostic data can be collected for the Recovery Manager Console as well. For more details, refer the Collecting diagnostic data for technical support section in Recovery Manager for Active Directory User Guide.

When gathering diagnostic data, the Diagnostic Data Collector collects the following:

  • From Forest Recovery Console machine
    • Collects the data saved in the current Recovery Project (.frproj) file, except for the passwords stored in that file.
    • Collects the Forest Recovery Console log
    • Collects the Recovery Manager for Active Directory Disaster Recovery Edition event logs
    • .mdb database files
    • Recovery Manager for Active Directory Disaster Recovery Edition
  • From Domain Controller
    • Collects Backup and Restore agent logs
    • Collects system event logs
    • Windows debug logs
    • Runs Microsoft Netdiag, Dcdiag, Nltest, MsInfo32 and Repadmin tools (in diagnostic mode only), and then collects the output provided by these tools. The tools are started by Collectdcdata.cmd and you can modify the list of collected logs.

To gather diagnostic data for your recovery project by using the Diagnostic Data Collector, you need to complete the following steps:

  • Step 1: Use Diagnostic Data Collector to automatically gather data. In this step, you use the Diagnostic Data Collector to automatically gather diagnostic data from each domain controller in your recovery project and save the data to the folder you specify. You can perform this step regardless of whether or not a recovery operation is currently running on the recovery project. If this step completes successfully for all domain controllers, Step 2 is not needed.
  • Step 2: Gather remaining data manually. You need to perform this step only for those domain controllers from which you could not successfully collect data in Step 1. In Step 2, you copy several files supplied with Recovery Manager for Active Directory to the target domain controller, and then run one of the copied files. As a result, diagnostic data is collected from the domain controller and saved to a new folder created in the location from which you ran the file.

The next sections provide instructions on how to complete each of these steps.

Step 1: Use Diagnostic Data Collector to automatically gather data

To automatically gather diagnostic data

  1. In the Forest Recovery Console, open the recovery project for which you want to collect diagnostic data.
  2. Make sure you specify credentials to access each domain controller in the project. To check whether you specified access credentials for a particular domain controller, do the following:
    1. Select that domain controller in the list of domain controllers.
    2. Open the Settings tab.
    3. Make sure you specify the correct credentials in the Domain Controller Access option.

The Forest Recovery Console will use the specified credentials to access the domain controller and gather diagnostic data from it.

  1. From the menu bar, select Tools | Diagnose | Collect Diagnostic Data.
  2. Use the Drop folder text box to specify the local or UNC path to the folder where you want to save the diagnostic data to be collected. The collected data is saved to a .zip, e.g. CollectedLogs_10_20_2015 07_23_25.zip
  3. You can change credentials to access the domain controllers that were specified on the step 2.
  4. Select the Delete collected logs from domain controllers option to delete collected RMAD\RMADFE logs from domain controllers.
  5. Click the Collect button and wait for the operation to complete.

If you successfully collected data from all the domain controllers in this step, you can submit the .zip file to Quest technical support. Otherwise, complete Step 2: Gather remaining data manually.

Step 2: Gather remaining data manually

Perform the next steps for each domain controller from which you could not successfully collect data in Step 1: Use Diagnostic Data Collector to automatically gather data.

To gather diagnostic data manually

  1. Create a temporary folder on the local disk of the target domain controller.
  2. Copy Collectdcdata.cmd from the Recovery Manager for Active Directory Disaster Recovery Edition installation folder to the folder you created in step 1 of this procedure.
  3. Run the Collectdcdata.cmd file in the location to which you copied it and wait for the script to complete.

The collected diagnostic data is saved to the CollectedData folder created in the location where you ran the Collectdcdata.cmd file.

  1. Rename the CollectedData folder so that its name reflects the name of the domain controller from which you collected data.
  2. Add the folder to the .zip file created in Step 1: Use Diagnostic Data Collector to automatically gather data.

Now you can submit the .zip file to Quest technical support.

Bare metal forest recovery

Active Directory failure, which includes corruption, is something that scares any administrator. There can be a lot of reasons for the loss of valuable data. It can be caused by any error, a virus, or a natural disaster. With our disaster recovery plan, you get an insurance policy for your business information.

This section contains recommendations for recovering an Active Directory forest if forest-wide failure renders all domain controllers (DCs) in the forest incapable of functioning normally.




Related Documents