VMs with disks on two datastores and snapvault/mirror

[plandata_at]

Hi!

Conisidering the following scenario as described in case id 01672449.

- VMs with disks on two datastores, one of the datastores snapvaulted to secondary storage over low bandwith wan link, the other datastore NOT snapvaulted because having disks that should not be backuped (for several reasons, for example lot of temporay data change)
-Veeam Backup Job with datastore selection as a source
-Now starting backub job, veeam takes fall back to primary storage because some disks are not found in secondary destination (no warning, no errors, nothing, just of course job taking forever because of wan link)
- Only workaround is to manually exclude every disk in every job that should not ba backuped, excuding the full datastore that should not backuped is not working (i think that is because veeam is in background not selecting datastores but the VMS). This adds a lot of additional work for backupadmin and has the problem that newly addes disks could be forgotten. Considering the worst case scenario: backup admin excludes disk id because this disk id should not be backuped. VM admin delete this disk and adds another one that should be backuped, this disk is getting the scsi id of the deleted disk an VOOOOM: disk os excluded from backup. That would be really bad!

In my opinion this could be seen as a bug and not only as a feature request, because Veeam is doing a fallback to primary storage without error even though the fact that checkbox "failover to primary storage" is disabled, and also thorugh the fact that you are able to exclude datastores from processing in the job settings, but this excludions have no consequence when VM has disks on two datastores.

I recommend some of the following changes:

a) Clearly display in the gui what is selected (not datastores, but instead VMs relaying on the datastore)
b) When selecting datastores, just process the disks on the selected datastores.
c) Give the possibility to exclude a complete datastore meaning exclude the disks of a complete datastore .(THIS WOULD BE MY PREFERED SOLUTION --> FEATURE REQUEST!)
d) At least when the checkbox failover to primary storage is disabled and not all disks are found on the secondary destination, abort the job with an error. In this case the checkbox is useless.

Thanks for hopefully supporting this feauture request!
Gernot

[BMG IT Department]

Yes, definitivley this is a problem veeam has, please solve this issue!

[foggy]

Thanks guys, this is a known behavior and we're looking into the ways of making it more expected. Thanks for the feedback though.

[plandata_at]

are there any changes in beahvior of this in Veeam 9.5? Thx!

[foggy]

Behavior described in point 'd' was introduced back in v9 Update 1: the job fails in case not all VM disks reside on the SV/SM volume and failover to primary storage is disabled.

[plandata_at]

Any news for:
c) Give the possibility to exclude a complete datastore meaning exclude the disks of a complete datastore .(THIS WOULD BE MY PREFERED SOLUTION --> FEATURE REQUEST!) ?

it's really annoying to exclude all disks from other datastore......

[foggy]

No news so far.