We´re having a strange error when trying to mount a virtual machine vmdk with vcb 1.5, using the -t file flag. The strange is that it works perfect with full-vm mount mode. Here is the interesting part of the log (suppresed some redundant lines):
I could not find anything related in a quick google search. The VCB server has been restarted a couple of times with same results. As far as I know the file type backup has never worked in this enviroment. As mentioned before, the full-vm flavour works fine with this VM.
Any idea what´s going wrong?
Thanks in advance.
Unlike fullvm backups, the file level ones rely on the:
VMware Virtual Mount Manager Extended service on the VCB server.
Is that definitely running OK?
Also there do sometimes seem to be issues between different users accessing it to do file level backups - it sometimes needs restarting in between...
It's not the most resilient of services....
Thanks for pointing me in the right direction
The VMware Virtual Mount Manager Extended service is set to manual start, and when I try to start it i get he following error in the event log:
DCOM got error "The service did not respond to the start or control request in a timely fashion. " attempting to start the service vmount2 with arguments "-Service" in order to run the server:
Any idea where to look further ?
Can't help much - that service is an integral part of VCB - you could uninstall and reinstall VCB I guess?
Guess it could be to do with the way your LUNS are configured?, all same LUN IDs across your ESX servers and VCB server?
No multipathing software on the VCB server?
Though I would have thought all that type of thing would have also caused issues with the full backups too?
PS please award points if any suggestions are helpful