We recently reinstalled vCenter after an SQL issue, then reinstalled the VCB Framework and the application that rides on top of it. Most of our VMs backup, however, a handful will absolutely not. I've been looking at logs, trying to find similarities, etc. Last night I destroyed the backup application and its jobs and rebuilt them all. Again, most VMs backup, but a handful will not. Taking the application out of it, here is the vcbmounter output...
Current working directory: C:\Users\xxx
HOSTINFO: Seeing Intel CPU, numCoresPerCPU 2 numThreadsPerCore 1.
HOSTINFO: This machine has 1 physical CPUS, 2 total cores, and 2 logical CPUs.
Using system libcrypto, version 90709F
SSLVerifyCertAgainstSystemStore: The remote host certificate has these problems:
The host certificate chain is not complete.
SSLVerifyIsEnabled: failed toread registry value. Assuming verification is disabled. LastError = 0
SSLVerifyCertAgainstSystemStore: Certificate verification is disabled, so connection will proceed despite the
error
Copying "[VMI1-FC1] xxx.xxx.com/xxx.xxx.com.vmx":
0%=====================50%=====================100%
**************************************************
Error: Could not back up config file: xxx.xxx.com/xxx.xxx.com.vmx
An error occurred, cleaning up...
Deleted directory C:\Temp\2\veeamvcbcdc5d8b5-7aa5-443c-b733-76068ab9d2d5
This is very strange. This VM is using less than 200GB of disk space, while I've got a 500GB server that is backing up without any problems.
Prior to submitting an official case, I thought I'd run it by the experts.
Thanks in advance!
Brian Ethington
PlanetEd Technologies, Inc
The config files are copied over the network, even if you are running in SAN mode or hotadd mode. CHeck the network and authentication. You can also run vcbMounter with the "-L 6" option to produce a more verbose output. Direct that to a text file and attach it here. DO not past the text because the forum software messes it up.
Also, check out my VCB Proven Practice Guide on VI:OPS -> http://viops.vmware.com/home/docs/DOC-1392
Dave Convery, VCDX
VMware vExpert 2009
http://www.dailyhypervisor.com
Careful. We don't want to learn from this.
Bill Watterson, "Calvin and Hobbes"
Dave,
Thank you for your response. it looks like a reboot of the ESX server resolved the issues. i was unaware when i entered into the issue that there was a power "blip" that occurred. I appreciate your suggestions.
Brian Ethington, vSphere VCP
PlanetEd Technologies, Inc
Go Figure! Well, I'm glad to hear you figured it out.
Dave Convery, VCDX
VMware vExpert 2009
Careful. We don't want to learn from this.
Bill Watterson, "Calvin and Hobbes"