Hi,
Is there any issue on installing the vCenter Server and VCB Proxy Server in the same Physical Server? What about installing VCB Proxy Server in a Virtual Machine?
Thanks,
As long as they are all in the same cluster and managed by the same vCenter server
Dave
************************
If the automobile had followed the same development cycle as the computer, a Rolls-Royce would today cost $100, get a million miles per gallon, and explode once a year, killing everyone inside.
Robert X. Cringely, InfoWorld magazine
It depends on how many guests you will be backing up and your IT budget. I would only do it if I had to. VirtualCenter requires atleast 2GB of memory etc, and if you've got Update Manager running on the VC as well and then add VCB to the mix - that's a lot of load on a box that demands resource and manages your VI!
Again - I wouldn't recommend it.
VCB proxy can be on a VM, however not if your VM's are stored on a FC SAN..
VCB have to be installed on your backup machine or the "holdingtank". When ever you interruped the vcb task during a mount in 90% of all cases a reboot is needed because the "umount" doesnt work. Its not a good idea installing this on such a important machine like the vCenter Server.
One of the benefits of VCB is backing up directly from the SAN without producing load on the ESX Hosts so running it in a VM wouldnt my 1st choice.
Regards
Joerg
'Remember if you found this or others answers helpful do not forget to award points by marking an answer as helpful or correct'
OK.. here's the real scoop...
You can install VCB on the vCenter server, but the load may cause problems with disconnections, etc. It is not really a best practice. You CAN make the VCB proxy a VM, even with FC LUNs, but then you are relying on network bandwidth (NBD Mode) or ESX Server processing (Hot-Add Mode) to complete the task. If you have limited hardware resources, you are better off creating a new VM for vCenter. This will give you the benefit of DRS and HA for availability and portability of your vCenter server. The VCB porxy can then be installed on the physical hardware.
In order to gain the most from the VCB proxy, IMHO, you should have it attached to the FC SAN with its own dedicated "holding tank" LUN and access to all of the VMFS partitions to be protected. The VCB proxy should also be a "media server". This would mean that it is attached to the tape drive, tape library or VTL. This gives you direct paths from VMFS to holding tank and then to tape and give you true LAN-free backups.
Take a look at VIOPS for some "Proven Practice" guides to give you an idea how to set up for your particular backup software _>http://viops.vmware.com/home/community/availability?view=all
If you are running Backup Exec, check out my doc ->http://communities.vmware.com/docs/DOC-2770
Also, make sure you check out the VM Backup Guide -> http://www.vmware.com/pdf/vi3_35/esx_3/r35u2/vi3_35_25_u2_vm_backup.pdf
Dave
************************
If the automobile had followed the same development cycle as the computer, a Rolls-Royce would today cost $100, get a million miles per gallon, and explode once a year, killing everyone inside.
Robert X. Cringely, InfoWorld magazine
I read the VM Backup Guide, and looks like putting the VCB Proxy in a VM is possible, but can only backup the VM on that same host where the VCB Proxy VM resides. Is this true?
Thanks,
Not true. Using hot-add mode assumes that all VMFS LUNs are accessible by the ESX server hosting the VCB.
Dave
************************
If the automobile had followed the same development cycle as the computer, a Rolls-Royce would today cost $100, get a million miles per gallon, and explode once a year, killing everyone inside.
Robert X. Cringely, InfoWorld magazine
So I can backup the virtual disk of a VM that resides on the other hosts?
As long as they are all in the same cluster and managed by the same vCenter server
Dave
************************
If the automobile had followed the same development cycle as the computer, a Rolls-Royce would today cost $100, get a million miles per gallon, and explode once a year, killing everyone inside.
Robert X. Cringely, InfoWorld magazine