New support for Windows 2008 R2
I’m at to TechED in Berlin … great party for the fall of the Berlin Wall 2009 (shameful timing) – once again Microsoft mess up my weekend. Windows Server 2008 R2 is pretty bold and it will have a significant impact on the market. Piles of guys I have spoken to are interested in the new capabilities.
There are some significant features in the R2 operating system that can help to boost productivity and help administrators gain more management control. It will be of specific interest to companies that have an extensive investment, or plans a complex deployment, of Hyper-V-based virtualisation; any company that has vast swaths of Windows servers in data centres where space, power or both are becoming tight; as well as any company that is planning to deploy Windows 7 on a wide scale in the near future.
In terms of support for R2 BE is already there with Backup Exec 12.5 for Windows Servers revision 2213 Hotfix 331998. This hot-fix contains recommended fixes for Backup Exec for Windows Servers version 12.5 revision 2213. New support for Windows 2008 R2 (RAWS – Remote Agent Support Only) and a Agent for VMware Virtual Infrastructure fix (AVVI).
Affected versions
- Backup Exec 12.5 revision 2213 32bit Media Servers
- Backup Exec 12.5 revision 2213 x64bit Media Servers
Prerequisites
Before installing this hotfix, Backup Exec for Windows 12.5 Service Pack 2 must be installed. Service Pack 2 can be obtained here: http://library.veritas.com/docs/334937. Administrative privileges are required to install this hotfix.
Post requisites
A full backup is recommended after installing this hotfix. Backup Exec Remote Agents must be updated
Download links
- Backup Exec 12.5 or Windows Servers revision 2213 Hotfix 327135 – 32 bit download: http://support.veritas.com/docs/334937
- Backup Exec 12.5 for Windows Servers revision 2213 Hotfix 327135 – 64 bit download: http://support.veritas.com/docs/334938
Issue(s) resolved
After applying Backup Exec 12.5 Hotfix 328462, an Agent for VMWare Virtual Infrastructure (AVVI) backup job with the “Granular Recovery Technology” (GRT) option enabled, completes with the exception “Failed to mount one or more virtual disk images” (For more details please refer to this document: http://support.veritas.com/docs/331927)
Installation Guide – The installation guide here contains general information for installing Backup Exec product updates as well as special instructions for configurations including CPS, Remote Agents for Windows Servers, Remote Agent for Linux/Unix/Macintosh Server (RALUS/RAMS), Clustered Backup Exec, Shared Storage (SSO) installations, Central Admin Servers (CASO) installations, and SAP/R3 Oracle Agents. http://support.veritas.com/docs/300795
VCB (VMware Consolidated Backup)
Protecting the VMware environment has its own unique set of data protection challenges. There are basically three ways to protect VMware: the guest OS method, the console backup method and the VMware Consolidated Backup (VCB) method. The guest OS method treats each virtual machine as a standalone server and backups take place as usual as if the virtual is physical server. The second practice is the console backup practice, in which virtualisation administrators back up the VMware ESX Server with no regard of the underlying virtual machines in the ESX environment. (There is a “free” product, ESXi, but it has no console, and requires add-ons to manage.)
VCB Backup requires VMware Infrastructure 3 (VI3) and initially SAN attached disk (iSCSI or Fibre Chanel) but now supports VMFS with local, JBOD, iSCSI and Fibre-Channel-attached disk, network file system (NFS) and virtual compatibility mode raw device mapping (RDM). The only mode not currently supported is physical compatibility mode RDM, together with a dedicated Windows Server 2003 acts as the backup proxy. You then install the VCB software on the Windows Server and provide access to the same SAN Logical Unit Number (LUN) used for the VMware Virtual Disk Files.
The Symantec Backup Exec 12.5 Agent for VMware Virtual Infrastructure (AVVI) is specifically related to the VMware Consolidated Backup framework and is designed and built to communicate directly with VMware ESX and VirtualCenter.VCB was originally introduced in 2006 as nothing more than a collection of interfaces and utilities that backup vendors could exploit. Since then VCB itself and backup vendor support has expanded considerably. The many different code levels for both VCB and backup applications have caused considerable confusion around what environments are supported and what VCB is today.
It is best to think of VCB as a backup framework with a collection of VMware utilities that facilitates backups. Today VCB utilises standard backup products together with snapshot capabilities. It uses command line interface (CLI) capabilities in VMware to take a VM snapshot of Windows-based VMs to offload a copy of the data for the backup product which Backup Exec then mounts and backs up.
Effectively, VCB provides a centralised backup facility that enables you to use Backup Exec to protect system, application, and user data in your virtual machines while reducing the load on virtualised servers. This allows you to backup your virtual machines without disrupting users and applications. So, VCB provides a way to do server-free and LAN-free backup and VM snapshots can be NFS mounted for quicker recovery and GRT as well as centrally manage backups to simplify management of IT resources.
Cool so far?
If you are not using VCB you do not need the BE 12.5 AVVI. Most organisations not using VCB are likely to be using ESXi. Although ESXi is free, there is no service console anymore. So you can’t use local agents on your ESXi host. Everything needs to be able to communicate with the VI API or any other remote connect method to gather information – not so cool.
So, the bottom line is AVVI is only needed when there is a VCB framework around the Virtual infrastructure.
VMware’s Virtual Infrastructure 3 (VI3) family includes: VMware ESX, VirtualCenter, VCB, VMware Converter & VMotion. Backup Exec 12.5′s Agent for VMware Virtual Infrastructure (AVVI) can leverage all of these components of VMware VI3 to automatically discover, protect, and recover virtual machines and their data. All Guest virtual machines (VM’s) hosted by V3I, including Windows and Linux virtual machines, can be protected using Backup Exec’s AVVI integrated support of VCB.
