Using Veeam BR, we cannot BU a few VM's that we have that have iSCSI volumes. I mean the iSCSI volumes are not seen by Veeam (or VMW for that matter) so we installed VAW on the VM's. We're BU the entire computer and tested a VM restore. We exported the .vmdk files, created a VM and copied the .vmdk's into the folder on the datastore.
We were BU the VM with Veeam BR except the iSCSI drives but the Snapshot was causing the iSCSI Vols to disconnect from the VM. Did I mention these are MS Clusters... it caused it to lose the Cluster resource and hung the Cluster. So we started BU the entire computer with VAW.
So far so good, we wish we didn't have to go through the motions of copying the .vmdk's but no alternative yet. I was wondering if anyone else has faced this challenge, that is BU a VM that has iSCSI volumes using Veeam BR (or Agent!).
-
- Novice
- Posts: 9
- Liked: never
- Joined: Feb 21, 2016 9:07 pm
- Full Name: Paul
- Contact:
-
- Product Manager
- Posts: 14715
- Liked: 1702 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: VAW for iSCSI on a VM
Hi Paul,
Generally, VAW can work with iSCSI volumes without issues (it can VSS them).
Generally, VAW can work with iSCSI volumes without issues (it can VSS them).