VCB is slowly evolving into a product I may actually feel safe using. Friday I had a ticket opened with VMWare because I could not get VCB to correctly mount a virtual machines vmdk for backup. At first the problem looked to me as though vcb did not actually see the LUN. I double checked my SAN configurations and was confident it was a VMWare problem. One test we used was manually mounting the lun with vcbmounter. When we started to use mountvm to see if we could mount the vmdk, someone in the background asked what backup agent and version we used. I told the engineer to tell them we used Tivoli Storage Manager 126.96.36.199.
The distant voice let us know that 5.5 was out and had some special support for vcb. I have had 188.8.131.52 deployed for some clients already and the server was currently running 184.108.40.206 as well. The distant voice came on the line and let me know how cool the support in 220.127.116.11 was. I had already begun taking over the webex session and installing the 18.104.22.168 client on the vcb server. He let me know of a problem where tsm baclient 22.214.171.124 and VCB 126.96.36.199559 do not automaticcly create the directories needed for mounting the lun. If you manaully create the directories it will delete them when VCB cleans up, leaving you with no directories again for next backup. I found the fix for this issue, it’s a maintainence release for 188.8.131.52. TSM baclient 184.108.40.206 is what you need to be upgraded to. This PDF talks about using VCB with Tivoli Storage Manager 5.5 check out page 329 in the document which is 347 of 402 in the pdf.
The APAR IC54709 is included as a fix in 220.127.116.11. You can download the patch here that will take you to 18.104.22.168.
A few features I feel are key:
1. The VCB server backs up the virtual machines using proxynode. This means that you can install an agent on the virtual machines and do file level restores as if they were backed up like normal.
2. License savings for TSM if your VCB server requires less licensing than your physical ESX servers.
Once you setup everything and create a vmlist file with all of your virtual machines. The only thing left is using a macro in your schedules to run “dsmc backup vm”. The product seems to work pretty good after that. I’ll try to test some restores next week and let you all know how that turns out. I’m very interested in keeping an eye on VCB as it develops and I certianly appreciate the intergration that Tivoli and VMWare are providing.