Recovery Manager for Active Directory provides two different methods of restoring objects online. A check box in the Online Restore Wizard allows you to specify which method to use. The agentless method uses Microsoft Tombstone Reanimation interface to undelete the object and then re-applies all attributes that are not stored in the object's tombstone from the backup using ADSI calls. This method requires that the target domain controller be running Windows Server® 2008 R2 or later.
Aside from operating system support, there are some additional differences between the two methods. The agentless and agent-based methods require different permissions to run. For example, the agentless method supports delegated permissions as outlined in the User Guide. The agentless method may not restore some attributes, depending on the operating system and service pack level, namely user passwords and SIDHistory, as these attributes cannot be set using ADSI. In order to restore these attributes using the agentless method, you can configure the Active Directory® schema to store these attributes in the object tombstone as described in the User Guide.
Yes, you can undelete mailbox-enabled users with the online restore function of RMAD. When you undelete a mailbox-enabled user within the mailbox retention period, the user’s access to the mailbox is also restored.
After a user is deleted, the Exchange Server retains the user’s mailbox for a specified period, before permanently deleting the mailbox. If the mailbox retention period has expired, the mailbox access associated with the undeleted user is not recovered. RMAD cannot restore mailboxes that have been permanently deleted.
If a link’s No Override option or Disabled option has been changed, RMAD treats the link as having been deleted, and assumes that a new link was created with new options. This behavior is by design.
A primary restore is intended to recover the initial member of the SYSVOL replica set, only when the entire replica set has been lost. A primary restore should therefore not be used if there are two or more operational domain controllers in the domain. If there are other members in the replica set with which the restored SYSVOL can synchronize, a primary restore should not be performed, as it disrupts the replication of SYSVOL data.
For more information about primary restore, see the Microsoft article “Authoritative, Primary, and Normal Restores” at How to force authoritative and non-authoritative synchronization for DFSR-replicated sysvol replication.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Conditions d’utilisation Confidentialité Cookie Preference Center
