I've got a VCB 1.1 implementation that seems to work fine when I run the vcbmounter command as the administrator user, but errors out when I run the command as my 'vcbuser' which only has the "VMware Consolidated Backup User" role. It works flawlessly if I run it as either the Administrator user, or if I add the vcbuser to the local Administrators group on the VC server. I've tried granting the vcbuser the Administrator role within VC and still get the same error.
The command I am running on the VCB proxy looks like this
vcbmounter -h myvcserver -u vcbuser -p password -a moref:vm-53 -r D:\test-fullVM -t fullvm
output trimmed
2007-12-18 10:04:49.982 'blocklist' 3028 error Could not renew disk lease. Aborting operation.
2007-12-18 10:04:50.013 'BlockList' 3028 error
Converting "D:\test-fullVM\scsi0-0-0-test-w2k3.vmdk" (compact file):
0%=====================50%=====================100%
**************************************************
2007-12-18 10:04:50.435 'vcbMounter' 3028 error Error: Failed to export the disk: I/O Operation failed
2007-12-18 10:04:50.435 'vcbMounter' 3028 error An error occurred, cleaning up...
Deleted directory D:\test-fullVM
VC shows the creation of a snapshot, the removal of the snapshot, and release of the disk lease during both the successful (Administrator) and the unsuccessful (non-Administrator) cases, so those actions are successful. The vcbuser is a domain account that is in the Administrators group on the VCB proxy.
Ideas?
I had similar problem.
Try defining your "vcbuser" not only on "Datacenter" level but also on "Hosts&Clusters" level. For me that solved the problem.
Bye
Can you post the permissions for the backup role you assigned the vcbuser?
Try using a directory instead of the root of the drive: D:\mnt\test-full. Also, use the fqdn for the guest or ip address.
Sure, I used the new VCB role included with VC 2.5. I assigned my user that role at the datacenter level. The permissions match what I have used before when creating the role by hand in VC 2.0:
VirtualMachine/Provisioning/AllowVirtualMachineDownload
VirtualMachine/State/CreateSnapshot
VirtualMachine/State/RemoveSnapshot
VIrtualMachine/Configuration/DiskLease
I think there is one other in VC 2.5, but this is pretty much the idea.
I will give those a shot, but the moref works for my admin user, but it isn't an issue finding the VM, but getting the blocklist for the VMDK -- I watch as the directory gets creates and the vmware*.log files get copied down. The only error happens when it tries to get the VMDK.
The permissions match my VC 2.0 environment as well so that's probably not it. You don't have any storage quotas setup for D:\ on the VCB proxy do you?
No quotas
I had similar problem.
Try defining your "vcbuser" not only on "Datacenter" level but also on "Hosts&Clusters" level. For me that solved the problem.
Bye
THAT WAS IT! Thanks! :smileygrin:
WOW!! That makes absolutely NO sense. That means it must be a feature.
Dave
Glad I could help.
Yes, it must be a feature
Work Well ! good job :smileygrin:
Stroll on, adding the VCB user at the Hosts & Clusters level worked for me too.. Winner. Irony is I defined it there first then decided to move it down to the datacentre coz I though it looked tidier before using VCB and getting the errors. Doh!
Cheers Kastro!