Hi All,
just looking for a bit of help getting VCB and Backup Exec 11D Working with a iSCSI san. setup my config.js files correctly and running my browse start job to mount the VM in BE.
browse-start.bat myjob server.mycompany.com
but im getting the following error
Error: Error while opening disk blklst://snapshot-898[VM Datastore] myserver[/myserver.vmdk@myvc01.mycompany.com:443?xxxx/xxxx|mailto:myserver/myserver.vmdk@myvc01.mycompany.com:443?xxxx/xxxx]: A virtual disk could not be opened. -- An invalid field name was used in a query string (Exception from HRESULT: 0x80040204)[2008-06-24 13:00:01.468 'vcbMounter' 3864 error] An error occurred, cleaning up...
Deleted directory C:\mnt\_myserver.mycompany.com_
anyone have any ideas for me to try?
thanks
Will
Hi everyone,
Still having trouble getting this working but after doing some reading i've seen people saying that they need to make sure that the VCB proxy can run vcbmounter corrctly first.
Now im running the following command
vcbmounter -richdc02 -administrator -password -a ipaddr:richdc02-r c:\mnt\ -t fullvm
and im getting the following output.
'App' 2040 error] Error: Invalid command line option
could someone help me point out the invalid command line option please?
thanks
Will
Would have thought your command should look like this:-
vcbMounter -h richdc02 -u administrator -p password -a name:richdc02 -r c:\mnt -t fullvm
It appears that your ESX host and VM both have the same machine name (richdc02) correct?
think you may have pointed out the problem to me...
werent putting in the correct host.
now i've changed the command to
vcbMounter -h richesx03.mydomain.com -u root -p password -a ipaddr:richdc02.mydomain.com -r c:\mnt -t fullvm
it's running but now im getting this error
No path to device LVID:484fe4d1-2ab83c6b-6c9c-001f296bdb5d/484fe4d0-d0959
90e-fdcc-001f296bdb5d/1 found.
Error: Failed to open the disk: Cannot access a SAN/iSCSI LUN back
ing this virtual disk. (Hint: Option "-m ndb" swtiches vcbMounter to network base disk access if this is what you w
ant.)
An error occurred, cleaning up...
Deleted directory c:\mnt
tried adding the -m ndb switch but it's still generating the same error.
thanks
Will
Not seen that error before, sorry.
Do you have an iSCSI initiator set up on the VCB Proxy that can connect to the VMFS LUN? Also, did you do a "Complete" install of VMware tools and not a "Typical" install?
Hi Dconvery,
you pointed me in the right direction, reinstalled vmtools with a full install (couldnt remember if i did a full install to start with) and changed the MS iscsi initiator to point to the VM LUNS and everything is working.
THANKS
1 last question, when doing a FULLVM backup i thougth i would have seen exactly what you see when browsing the datastore on the VI client rather than a list of files like this on the VCB proxy
scsi0-0-0-RichDC02.vmdk
scsi0-0-0-RichDC02-s001.vmdk
scsi0-0-0-RichDC02-s002.vmdk
scsi0-0-0-RichDC02-s003.vmdk
scsi0-0-0-RichDC02-s004.vmdk
scsi0-0-0-RichDC02-s005.vmdk
so how does this impact trying to restore the orginal vmdk file?
thanks again
Glad I could help with it. What you are seeing is the VMDK broken into "sparse" files. It breaks it down to 2GB increments. It is perfectly normal. You can set a switch to change it to monolithic, but it seems like it performs better this way. For recovery, you wil use Backup Exec to restore the files to the VCB proxy. Then you will use VMware Converter to convert from a "hosted" VM to a VI3 VM. Converter will take care of putting it all back together. It will be a NEW VM from a VI3/ESX perspective, so it will have a ne UUID.
If you don't mind, please mark the thread as answered.
Dave
Hi Dave,
Sorry for the delay - thanks for explaining this to me.
enjoy the points.
Cheers
Will
Will -
Its not so much about the points as it is about having it marked as answered. This way others may see a solution to their problem...
Dave