Backup completes but gives a warning that it "Backed up in a crash-consistent state"
The "Backed up in a crash-consistent state" warning is given when the shadow copy fails internally within one of the VMs you are backing up. The most likely cause is that one of the VSS writers of the applications installed on the VM was unresponsive or not functioning as it should, however, there could be other reasons too. You should proceed to troubleshoot as follows:
- Firstly, check whether your VM actually requires an Application-Consistent backup. If it does not, you can disable it from the "VSS Settings" screen. Simply uncheck "Application Consistent" and Save changes. More information here.
- Ensure that the VM meets all of the requirements for online/live backups listed here
- Run the command below in command prompt inside the VM that is crash-consistent:
vssadmin list writers
In the results check that all writers inside the VM are in a "Stable" state and showing "No error"
- Check that the shadowstorage on each drive is not full, ideally set to unbounded. You can set it as unbounded by running the following command in command prompt:
vssadmin add shadowstorage /For=C: /On=C: /MaxSize=UNBOUNDED
vssadmin resize shadowstorage /For=C: /On=C: /MaxSize=UNBOUNDED
Note: Run the two above commands for each drive, each time replacing the drive letter from C: to the drive in question.
- If the VM giving trouble is running Microsoft SBS 2011, then please go through this article.
- If the issue persists check for warnings or errors in the Application and System event logs on the VM that is giving trouble.
- If none of the above helps, please contact our support team.
The Microsoft shadow copy was unsuccessful from within one or more VSS writers on the VM itself.