- Veeam Support Knowledge Base
- Restore/SureBackup from old DC restore point fails due to shadow copy expiration
Restore/SureBackup from old DC restore point fails due to shadow copy expiration
| KB ID: | 2226 |
| Product: | Veeam Backup & Replication |
| Published: | 2017-01-18 |
| Last Modified: | 2021-12-09 |
Get weekly article updates
Cheers for trusting us with the spot in your mailbox!
Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest
Oops! Something went wrong.
Please, try again later.
Challenge
DC restore results in DSRM boot and event id 1918 from ActiveDirectory_DomainService stating:
The shadow copy service cannot restore Active Directory Domain Services because the shadow copy used is too old.Cause
The backup of the DC is older than the tombstone period.
Active Directory protects itself from restoring data older than the tombstone lifetime (180 days) by disallowing the restore. As a result, the useful life of a backup is equivalent to the tombstone lifetime setting for the enterprise. Reference: https://technet.microsoft.com/en-us/library/bb727048.aspx
Thus Veeam does not support restore from such backups either.
Active Directory protects itself from restoring data older than the tombstone lifetime (180 days) by disallowing the restore. As a result, the useful life of a backup is equivalent to the tombstone lifetime setting for the enterprise. Reference: https://technet.microsoft.com/en-us/library/bb727048.aspx
Thus Veeam does not support restore from such backups either.
Solution
Restore or run sure backup from the backups which were created within the tombstone period.
Setting the time on the DC before the shadow copy expiration date may be a solution for the a single DC restore scenario, but if it is not a single DC, even if the replication starts, there can be a situation when the object remains present only on the restored domain controller, resulting in inconsistent data. So it is not advisable to perform that in case the DC you are restoring is not a single one.
Setting the time on the DC before the shadow copy expiration date may be a solution for the a single DC restore scenario, but if it is not a single DC, even if the replication starts, there can be a situation when the object remains present only on the restored domain controller, resulting in inconsistent data. So it is not advisable to perform that in case the DC you are restoring is not a single one.
If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
