Article ID: 160850 - View products that this article applies to.
This article was previously published under Q160850
This article has been archived. It is offered "as is" and will no longer be updated.
When a directory is restored from backup it attempts to get back copies of all the objects that it last modified or added and that it replicated out to other computers since it was backed up; this is called backsync. During backsync, you can get into a situation where it is not possible to make directory changes for up to 16 hours. When you attempt to modify the directory while it is in this state, the Microsoft Exchange Server Administrator program will display the following message:
The following event ID will also be logged:
The directory is busy. Wait a few minutes and try again.
Microsoft Exchange Directory
ID no: DS_E_BUSY
Event ID: 1173. A privileged operation (rights required = 0x4) on object failed because a non-security related error occurred.
This will most often occur after the restoration of a directory on a server that has the schedule on its connectors set to Never. The directory service agent (DSA) is hardcoded to try to backsync for up to 16 hours even if it is unable to do so.
To work around this problem, do one of the following:
Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 4.0. This problem has been corrected in the latest U.S. Service Pack for Microsoft Exchange Server version 4.0. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):
S E R V P A C KMicrosoft has confirmed this to be a problem in Microsoft Exchange Server version 5.0. This problem has been corrected in the latest U.S. Service Pack for Microsoft Exchange Server version 5.0. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):
S E R V P A C K
When a directory is restored from backup it attempts to get back -- backsync -- copies of all the objects which it last modifed or added which it replicated out to other computers since it was backed up. These computers can be in the same site or another site. Backsync is necessary becuase normally changes made at a DSA do not replicate back to that DSA, and also the Update Sequence Number (USN) for a restored computer will be lower than the USN it had before being restored. This means that if any changes are made at the restored computer before it has backsync'ed, they will not replicate out until the USN climbs to the value it was before the server was restored.
If the backsync is overridden by reducing the timeout, there is a risk of this replication loss. Therefore the backsync timeout should only be reduced or eliminated when you are sure that no changes were made at the restored computer since the computer was backed up."
Article ID: 160850 - Last Review: October 4, 2013 - Revision: 3.3
Contact us for more help