the hyper-v vss writer has problems with this configuration - not the Veeam, since Veeam plays a role of the vss software requester and only triggers VSS provider and VSS writers (since, the same issue you'll see if you use any other backup solution - Microsoft DPM for example).
So, the shadow copy location should be on the same drive - this is a Microsoft limitation.
In the Veeam 6th we skipped guest processing (if it fails) and didn't crash the backup job itself - that was not a good solution. In the same situation the job will fail now.
JohnV wrote:I originally had v7r2 installed on a 2008R2 box and was getting the exact same error. None of the registry settings mentioned had any effect on it.
I moved v7r2 to a 2012r2 VM with no change in the error.
JohnV wrote:To answer your question none of my VM's have 'dynamic' disks they are all 'basic' disks. There are 'dynamically expanding virtual disks' in these VM's but no one is saying that is a problem.
03.02.2014 12:21:14 :: Unable to create snapshot (Microsoft Software Shadow Copy provider 1.0) (mode: Crash consistent). Details: Guest processing skipped (check guest OS VSS state and integration components version)
Users browsing this forum: Google [Bot], Vitaliy S. and 13 guests