I have managed to build a successful VCB infrastructure in which the majority of my virtual machines will backup nicely using VCB.
There is one holdout giving me this in the saveset report:
1 retry attempted
\[2007-03-13 10:39:39.886 'App' 4588 info] Current working directory: C:\
\[2007-03-13 10:39:40.573 'BaseLibs' 5744 warning] \[Vmdb_Unset] Unsetting unknown path: /vmomi/
\[2007-03-13 10:39:41.792 'vcbMounter' 4588 error] Error: Backup snapshot already exists.
\[2007-03-13 10:39:41.792 'vcbMounter' 4588 error] An error occured, cleaning up...
External command failed. See error above.
Exit Code: 1
*******************************************************
Networker 7.3.2 with compatibility Module
ESX 3.x
VC 3.x
guest os is windows 2k3
datastore is cx500
Anyone seen this kind of stuff with a VCB backup on one of their VM's?
Thanks,
Looks like your VM has a leftover snapshot that was never committed (deleted) from a previous backup. Use the VI client and browse to the VM and use the Snapshot Manager button to delete the snapshots. Then you should be good to go.
Thanks SO much!!
That did the trick. Still trying to get this whole VCB thing fully understood. Just had a successful backup of that VM and another that was doing the same thing.
I LOVE the forums!
I'm getting this on another VM. I have full name resolution going on between the Networker server and the VM so I don't know how I could be getting this:
1 retry attempted
\[2007-03-14 12:26:33.218 'App' 2596 info] Current working directory: C:\
\[2007-03-14 12:26:33.781 'BaseLibs' 2988 warning] \[Vmdb_Unset] Unsetting unknown path: /vmomi/
\[2007-03-14 12:26:34.749 'vcbMounter' 2596 error] Error: Host is unreachable.
External command failed. See error above.
Exit Code: 1
Make sure you are using the same DNS name case that is displayed when you view the server in VC.
Hi,
The DNS name in VC is ASPTTS in upper case so I changed it to that in the SaveSet selection and got the same errors.
1 retry attempted
\[2007-03-19 06:58:15.070 'App' 5640 info] Current working directory: C:\
\[2007-03-19 06:58:15.617 'BaseLibs' 6092 warning] \[Vmdb_Unset] Unsetting unknown path: /vmomi/
\[2007-03-19 06:58:18.227 'vcbMounter' 5640 error] Error: Host is unreachable.
External command failed. See error above.
Exit Code: 1
This is the output in the Virtual Center Events screen:
Name Target Status
Create Virtual Machine Snapshot ASPTTS Unable to communicate with the remote host, since it is disconnected
Remove Snapshot ASPTTS Unable to communicate with the remote host, since it is disconnected
I have this same issue. Two of my VMs have names in uppercase, but one of them won't resolve. I've tried looking it up with vcbVmName and it just refuses to lookup that one machine. Good thing it's a test box and not a production one!
When you run the 'esxtop' command, does it show you the proper name as it should with vcbVmName?
No, esxtop is showing the "friendly" name for the VM.
The VCB scripts specify the 'ipaddr:' switch to vcbMounter.exe .
If the script is looking for ipaddr: it should return the actual IP, not the FQDN.
From glue.js in the VCB Framework:
// set the VM identifier. - In our case, it is always a DNS name
// or an IP address.
cmd += "-a ipaddr:" + VMinfo.name + " ";
This would lead me to believe that a DNS name will work. It works for all my other VMs.. It just doesn't like one of them for some reason...
Ok, yes you are right, you can use either to query with vcbVmName. Both should work, but I guess in your case you may want to modify the script to return IP addresses instead of FQDN.
Exactly.. but I would like to figure out why it doesn't work.. I mean, come on.. DNS names came about so that people didn't have to remember IP Addresses. It would make my scripts look "cleaner" and easier to read/maintain if I could just use DNS names across the board.
When you run the ESXBackup script do you specify :any to backup all vms? Or do you do PoweredON?
With VCB, you specify individual VMs to backup.
Very sorry, I accidentally mixed my thread posts. Can you send the output of the vcbVmName for the stubborn VM and what the name should be?
Ah, well, I just figured out my issue.. We had an incorrect reverse DNS entry for the server it couldn't find...
I tried upper and lower case on this command that I use for each vm:
VM:ASPTTS.ccchsd.gov:\*FULL*
It doesn't work either way.
I'm using this command
VM:ASPTTS.ccchsd.gov:\*FULL*
The name of the vm in virtual center is ASPTTS in upper case. I've tried the command shown in upper and lower case with the same resut.
Here is output from nslookup. It appears to be resolving just fine and this was run from the Networker Server
H:\>nslookup
Default Server: ptdc1.ccchsd.gov
Address: 172.18.10.164
asptts
Server: ptdc1.ccchsd.gov
Address: 172.18.10.164
Name: asptts.ccchsd.gov
Address: 172.18.13.172
172.18.13.172
Server: ptdc1.ccchsd.gov
Address: 172.18.10.164
Name: asptts.ccchsd.gov
Address: 172.18.13.172
ASPTTS
Server: ptdc1.ccchsd.gov
Address: 172.18.10.164
Name: ASPTTS.ccchsd.gov
Address: 172.18.13.172
172.18.13.172
Server: ptdc1.ccchsd.gov
Address: 172.18.10.164
Name: asptts.ccchsd.gov
Address: 172.18.13.172
I use the save_vcb.bat in the client properties.
I know it sounds stupid, but have you verified that you can ping the VM and your ESX hosts from your VCB box? Do you have any sort of firewall on it that would prohibit VCB traffic?