I remember reading the documentation about VCB where it stated it requires a physical machine .. Now I read the guide and it states it can run on a virtual machine ?!?
Has this changed with a specific update ?
Weird .. I did my VCP on 3.5 and I am certain they told us (hell I even have it in front of me) that it requires a physical machine
Ah well I remember I did my VCP just after they introduced the VCP on 3.5 - I guess just one more example that you have to keep up with the documentation all the time ...
There have been upgrades to VCB, so now you can use VCB inside a vm.
However, if you are backing up from a Fibre SAN you still need a physical VCB server
The additional functionality of having VCB in a vm is for backing up from an ISCSI SAN for example.
If you found this or any other answer useful please consider the use of the Helpful or correct buttons to award points
The biggest problem with using VCB within a VM is where will you send the data once you have a backup? If it is direct to tape, then a locally attached tape device has very poor write performance as opposed to a physical system. In addition, you can not vMotion the VM when it is attached to a tape device.
Edward L. Haletky
VMware Communities User Moderator
Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.
SearchVMware Blog: http://itknowledgeexchange.techtarget.com/virtualization-pro/
As well as the Virtualization Wiki at http://www.astroarch.com/wiki/index.php/Virtualization
The "problem" was that I had to explain vcb to my manager and I looked quite stupid when I told him it musn't be a virtual machine but the documentation says otherwise
What we probably do for this particular client is a 4 U storage server (24TB local SAS storage) and using VCB to simply grab those files of the cluster and via a DIY script moving it to a different location (so the destination folder can be unmounted again) .
We were thinking about using Acronis, but we don't really need the additional step of imaging those files .. this would just add another step when it comes to the restore ..
So far I am quite happt with the result ..
Granted - we don't use VCB the optimal way - but we don't need to anyway
Command I am using at the moment : vcbMounter.exe -h 192.168.10.70 -m hotadd -u vcb -p vcb -a ipaddr:192.168.10.153 -r c:
mnt -t fullvm