Gostev wrote:Hi Tyler, it is not clear if you are having the issue with ShadowProtect, Symantec or Veeam?
Gostev wrote:I understand that, but what product's backup process puts the VM in the saved state?
Gostev wrote:First, it is simply not fair to say you did not get any help from Veeam, because I have been answering all your questions above promptly.
Second, I can only repeat that Veeam does not put anything permanent in the VSS stack of the processed VM. The setting you have referred to is not used unless you actually run the Veeam job - in which case, temporary run-time VSS coordination process is injected into the guest by the job. This process only exists in the guest while Veeam is backing up the specific VM, and is removed immediately as soon as the backup is taken. Thus, there is literally nothing VSS-related to "backout" from guest before uninstalling Veeam. And all job settings are only used in the run-time too (when you actually run the job).
exportgoldman wrote:I don't think it's unfair to say this took too long to resolve - you may answer quickly but not with anything useful sorry.
Gostev wrote:Please appreciate that this forum is not intended to provide technical support, and as such is not monitored by support staff. The product management team behind this forum is unable to provide assistance troubleshooting complex technical issues, so kindly please set your expectations accordingly.
Users browsing this forum: Google [Bot], Yahoo [Bot] and 1 guest