VMware Consolidated Backup 3.5 – new features

Just to explain some new features in the VCB 3.5. Installing VCB on a virtual machine is now possible. It is not really recommended for larger environments, but possible for small businesses. You can also install the Proxy VCB onto a Virtual Machine running inside of your ESX Server. But I would not do it. Why? If your Storage break down, you are out of bussiness… -:(

When your proxy server is running in a virtual machine, you can store your backups on secondary NAS storage or on iSCSI storage. You can also store backups on the proxy server’s VMDK or RDM storage. You can get the PDF explaining all the new features at the VMware’s website. Just click on the link below.

VMware Consolidated backup improvements in 3.5 PDF at VMware website

In short what’s new in VCB 3.5? :

  • Support for backing up virtual machines stored on iSCSI SAN storage, Network Attached Storage (NAS) and local storage inside the ESX Server host
  • Support for moving the backup snapshots of virtual machines over the LAN, removing the need for SAN-based storage (it means that you can copy the shapshots into a shared folder on your 2003 server for tape backup)
  • Support for installing the Consolidated Backup proxy and VirtualCenter Management Server on the same host.
  • Support for storage array WWNs, so device mapping need not be exactly the same on ESX Server hosts and the backup proxy

One of the cool new features is that now you can use VMware Converter as a restore tool. VMware converter has many advantages over other methods of restoring a backup image.

First of all you can restore your Virtual machine directly into your ESX Server host. With VMware Converter you can also customize the virtual machine as it is restored. This gives you an easy way to change networking parameters for the virtual machine.

Technorati : , , , , ,
Del.icio.us : , , , , ,

Share

Technorati Tags: , , , , ,

Leave a Reply

Other posts from Server Virtualization