Error Message: The transaction does not exist to call rollback on!
The job would run a full but when it ran an incremental it would fail at the end when it rewrites the files and updates the DB.
This was a VM with 4 disks. The 4th disk was a large disk (over 1 TB). The issue was with the disk, so VM configuration. This looked like an issue with the DB, so we tried repo sync first and then we tried purge DB script and neither resolved the issue.
We turned off the option to backup disk 4 and the backup ran. Then we added a new disk (disk 4), moved all the data to it, removed the old disk and ran a backup that way. It works.
© 2025 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center