Replication fails with an error: "Failed to create backup on device. Internal library error. Failed build snapshot sequence"
Challenge
Replication fails with the following message in Acura's Events section or in the agent's logs:
- "Failed to create backup on device <...>: Internal library error.
- Failed to filter snapshots
- Failed to find end snapshot(<...>).
- Failed build snapshot sequence. Expected begin - <...>, end - <...>
- Guid of vss record header is empty. Broken snapshot id
- Failed to read header record
- Can't find last page.
- Unexpected vss record native offset. Actual(<...>), was expected(<...>)"
Cause
This is caused by faulty VSS operations and data inconsistency on the source machine which has led to the snapshot chain being broken.
Solution
1. Make sure there are no 3rd party backup tools installed on the machine as they will interfere with Acura's operations while snapshots are being taken possibly causing corrupted data.
2. Check that there are no automated scheduled tasks (disk defragmentation, maintenance) on the machine. Turn them off if any.
3. Check the machine's shadowstorage configuration with the vssadmin list shadowstorage command for any discrepancies.
4. Execute the vssadmin delete shadows /all command to remove any existing snapshots. Sometimes, there is conflict when trying to delete VSS copies that causes the following message:
- Error: Snapshots were found, but they were outside of your allowed context. Try removing them with the backup application which created them.
In that case, alternative commands may be necessary:
- wmic shadowcopy delete — executed in the command prompt.
- diskshadow — open command prompt as administrator → Type diskshadow→ then on the DISKSHADOW> prompt type delete shadows all to delete/remove all shadow copies from the machine.
5. Once the obsolete snapshots have been removed, start a new replication for this machine through Acura's UI.