cparker4486 wrote:Why doesn't B&R remove these snapshots itself when found?
cparker4486 wrote:Here's the problem: My backup logs report successful backups. Jobs should not be successful if there are unaccounted for snapshots. If an existing temp snapshot cannot be removed the job log should indicate so with a warning.
cparker4486 wrote:Also, I find it hard to believe that just by chance, every time B&R went to remove this specific snapshot, vCenter was not responding yet worked perfectly at all other moments.
cparker4486 wrote:In any case, I'm sure you would agree this aspect of B&R needs to be more robust (because I know you want your software to work flawlessly).
Gostev wrote:Unless vCenter server tells us that the snapshot was in fact successfully removed, when in fact it was not... which unfortunately happens quite often.
Gostev wrote:How do you know it worked perfectly at all other moments? Thing is, we had two cases in support with this behavior confirmed in the past few weeks alone.
cparker4486 wrote:Can B&R not check for the existence of snapshots before it begins a new run? If it finds a snapshot called VEEAM BACKUP TEMPORARY SNAPSHOT doesn't that indicate a previous run's snapshot was not removed
Gostev wrote:That's easy. Because the job log shows me all green check marks and no warnings indicating anything went wrong.
Users browsing this forum: No registered users and 23 guests