ChrisGundryCEGA wrote:Hi. Why has my thread been merged into this one with no explanation? This is a real problem with these forums...
Yes, i was also a little irritated as i read this post, since i can't remember that there were more posts before my answer... Anyway.
I don't have any Microsoft cluster running at my customers, so i can't really tell you more about clustering.
What operating system is the cluster running? Server 2003 or newer? Since with Server 2008 and 2008 R2 the cluster functionality became renamed to "Windows Server Failover Clustering" and the Component Load Balancing (CLB) feature has been deprecated.
What virtualization platform are you using?
At least when i have a look to VMware KB i find this article: http://kb.vmware.com/selfservice/micros ... Id=1006392
If you require bus-sharing:
Consider running backup software within your guest operating system as an alternative solution.
If your virtual machine currently has snapshots and it is preventing you from configuring bus-sharing, delete the snapshots. For more information, see the Using Snapshots section of the vSphere Basic Administration Guide for your version of VMware ESX.
Note: If snapshot consolidation fails, see Consolidating Snapshots(1007849).
If you do not require bus-sharing:
If your virtual machine is currently configured with bus-sharing, but you want to create snapshot, you must disable bus-sharing. For more information, see the Managing Mapped LUNs section of the ESX Configuration Guide for your version of VMware ESX.
For me it seems as you have the following possibilities:
- If bus-sharing is required, you have to use a backup software within the VM. For this i would recommend Veeam Endpoint Backup FREE
, since you can backup in an existing Veeam repository.
- If bus-sharing is not required, you have to disable it.
Veeam create a snapshot of the VM (or tells vSphere to create a snapshot of a VM) and then retrieves the data out of this snapshot. Bus-sharing and snapshot don't work as VMware says.