- Posts: 315
- Liked: 37 times
- Joined: Sep 29, 2010 3:37 pm
Exchange VSS Writer (instance 020e30fc-3d76-4b32-9816-4f7ac3c9be11:1182) has unsuccessfully completed the backup of storage group 'First Storage Group'. No log files have been truncated for this storage group.
During a backup job this is successful.
The replica jobs are completing successfully.
Anyone see this before? Is this normal behavior? Does this mean my databases are just crash consistent? Or is this a result of having the log truncate option disabled for the replica jobs?
I can submit a ticket if needed.
- Product Manager
- Posts: 25112
- Liked: 2153 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Veeam ProPartner
- Posts: 67
- Liked: 6 times
- Joined: Dec 09, 2014 4:28 pm
- Full Name: Gary Busey
So what we have right now is Veeam backing up the OS but we also back it up with BackupExec at a completely different time interval so we get the mail objects for us to restore.
The job is currently configured to require successful VSS performance and perform copy only and not truncate logs.
When the job starts it does trigger VSS and but then ends up erroring "Exchange VSS Writer (instance $GUID) has unsuccessfully completed the backup of storage group '$Storage_Group'. No log files have been truncated for this storage group."
Is this expected behaviour when using VSS but not truncating logs?
- Product Manager
- Posts: 5979
- Liked: 609 times
- Joined: May 19, 2015 1:46 pm
Please see Vitaliy's answer.
Actually SureBackup was designed to test backups' recoverability, not to restore from. Also that would be great if you could provide more info regarding the issue you had with SureBackup.as we encountered an issue in the VeeamSure backup that wasn't resolved for us to be able to restore data from it
Users browsing this forum: Bing [Bot] and 28 guests