Replies to This Discussion

Permalink Reply by Jon McNerny on August 26, 2013 at 9:58am

Do you export data fine regarless of the error?

• ▶ Reply

Permalink Reply by rdc on August 26, 2013 at 11:05am

no, it only sees some of the virtual disks, so misses out on half the data.

• ▶ Reply

Permalink Reply by Jon McNerny on August 26, 2013 at 11:26am

Do all disks being exported meet vmwares requirment for snapshots?

http://pubs.vmware.com/vsphere-4-esx-vcenter/index.jsp?topic=/com.v...

 

Jon

• ▶ Reply

Permalink Reply by rdc on August 26, 2013 at 12:18pm

If you are referring to the below, then yes, it does not fall into the list:

VMware does not support snapshots of raw disks, RDM physical mode disks, independent disks, or of virtual machines configured with bus-sharing.

• ▶ Reply

Permalink Reply by Jon McNerny on August 26, 2013 at 3:18pm

Yes, that is the criteria.

If you look at the \\vmpro_appliance_ip\export folder from a UNC path; drilling down to that VM, do you see the .vmdk files appear for the missing disks that don't backup?

• ▶ Reply

Permalink Reply by rdc on August 26, 2013 at 3:56pm

no they are not there, only the subject message in the logs.

• ▶ Reply

Permalink Reply by Jon McNerny on August 27, 2013 at 8:55am

Are you connecting to the vcenter?  Do you see the files if you connect directly to the ESX host with vmpro?

• ▶ Reply

Permalink Reply by rdc on August 27, 2013 at 9:01am

I was, I've just tried direct, no change.

• ▶ Reply

Permalink Reply by rdc on August 27, 2013 at 9:08am

https://mosaic.quantum.com/docs/ProblemsAndSolutions/SnapshotsNotFound

I think this has something to do with it, but I'm not comfortable making changes to the datastore names just to get this to work -especially as I don't yet have a VM backup :)

I say this because datastore names that are unique across the hosts are the ones that worked. I have no such entry in my vmx files - it's all as VMWare had as default.

I'd have thought then that repointing from vCenter to the direct host would have resolved it, but could vmPRO keep a reference to the original? if so perhaps I should start from scratch with vmPRO.

Are you able to elaborate on alternatives to the suggested workaround?

Permalink Reply by rdc on August 29, 2013 at 8:55am

I've re-installed pointing at just the one VMWare host and it's still only seeing some of the vmdk's.

So I'm afraid in the absence of further direction, given that it cannot backup all our data, then that's the end of our evaluation.Which is a shame as it seems quite usable and comfortable in most aspects.

Thanks for trying anyway,

R

• ▶ Reply