Replies to This Discussion

Permalink Reply by DoubleDensity on May 6, 2013 at 7:39am

Do your backups for these VMs fail as well or is it just these alerts which are generated? For the VM 'SERVER1' is it possible it has a disk attached which does not support snapshot? (Independent Disk or Physical-Mode Raw Device Mapping are not supported for snapshots) 

• ▶ Reply

Permalink Reply by Leho on May 6, 2013 at 8:32am

Backup fails in any case when message is "Cannot find which virtual machine the disk [DATASTORE01] SERVER2/SERVER2-000002.vmdk belongs to: No such file or directory: No such file or directory".

If the message is like "The following disk on VM 'SERVER1' does not support snapshot and will not be exported for backup", then backup is generally made.

All VM-s has the same configuration:
SCSI Bus Sharing: None
Hard Disk Mode: Not Configured
I don't use Raw Mappings.

• ▶ Reply

Permalink Reply by Leho on May 7, 2013 at 10:10am

In addition, for some reason entries from vCenter database table VPX_DISABLED_METHODS are not removed after a virtual machine backup task completes. If this true, then I can't migrate VM-s. It happens completely randomly, sometimes the entries are deleted from the table.

• ▶ Reply

Permalink Reply by Leho on May 9, 2013 at 4:51am

I noticed that two (-000001, -000002) delta files are created per virtual disk then vmPRO start backup process. Then I make snapshot using vSphere Client then a single delta file is created.

• ▶ Reply

Permalink Reply by Barry Herman on May 16, 2013 at 3:34pm

Hi, Two snapshots could be created when the VM has the VSS option (Quiesce Enabled) selected in vmPRO and the VM does not have the vmPRO's VSS agent installed in the guest.

Please try disabling the Quiesce Enabled option in vmPRO, to see whether that resolves the problem.

• ▶ Reply

Permalink Reply by Leho on May 22, 2013 at 12:54am

Hi, thanks! Problem resolved.

• ▶ Reply