protecting vmware environments with commvault software and … · 2007-03-07 · protecting vmware...

Third party information provided to you courtesy of Dell

............................................................................................................................................................................

Protecting VMware Environments with CommVault Software and Dell Hardware

Kelly Harriman-Polanski

Director, Product Marketing CommVault

January 2007

............................................................................................................................................................................

Table of Contents

Overview of the Data Management Challenge for VMware Systems...................................................................2

Understanding the Disk Structure of VMware ESX Server and VMware Server Systems...............................3 Disk Files and Redo Logs on ESX Server ................................................................................................................................ 4 Raw Device Mappings (RDMs) ................................................................................................................................................. 4

Data Protection Considerations for ESX Servers.......................................................................................................................... 4 Options for Protecting an ESX Server or VMware Server with CommVault Software......................................5

Protection Option 1: Treating Virtual Machines as “Real” Machines........................................................................................... 6 Obtain Cost-Effective Virtual Machine Protection..................................................................................................................... 7 Protecting Virtual Machine System State.................................................................................................................................. 8 Avoid Sending Backup Copies Across the Network................................................................................................................. 8

Protection Option 2. Preparing Today for ESX Server Backup Options Available Tomorrow................................................... 9 Protection Option 3: Treating Virtual Machines as Files on an ESX Server ............................................................................. 11

How CommVault Disaster Recovery Capabilities Enhance VMware Disaster Recovery Operations................................ 12 More Details on Using [vmkfstools] Commands to Gain Access to Virtual Disk Files.......................................................... 13 Using [vmsnap] and [vmres] Commands to Assist Backup and Recovery........................................................................... 13

Step-by-Step Protection of a VMware ESX Server Virtual Machine ...................................................................14

Extending Data Management into Virtual Machine Environments Using CommVault Replication.............15

Key Features and Benefits for VMware Server Systems Protected with CommVault Galaxy Software.....16

System Requirements.................................................................................................................................................18

See it For Yourself........................................................................................................................................................18

The information contained in this document, including all instructions, cautions, and regulatory approvals and certifications, is provided by CommVault and has not been independently verified or tested by Dell. Dell cannot be responsible for damage caused as a result of either following or failing to follow these instructions. All statements or claims regarding the properties, capabilities, speeds or qualifications of the part referenced in this document are made by CommVault and not by Dell. Dell specifically disclaims knowledge of the accuracy, completeness or substantiation for any such statements. All questions or comments relating to such statements or claims should be directed to CommVault.

Visit www.dell.com for more information.


2

Overview of the Data Management Challenge for VMware Systems Backup, restore, and disaster recovery are crucial topics to consider when managing the infrastructure of a data center. The same is true for virtual infrastructures built on VMware ESX Server. VMware enables traditional backup and recovery methods to be used to protect ESX Server and VMware Server (which supersedes GSX Server systems); however, it is important to consider additional options for protecting both systems and data within a virtual infrastructure. This white paper describes your options for using CommVault for Unified Data Management to protect and manage data in VMware systems:

• Backing up and recovering data in virtual machine environments, including information on options that are available with the release of ESX Server 3.0

o Object-level backup and recovery of file system data residing within virtual machine

environments o Granular backup and recovery of application data residing within virtual machine environments o Deployment options for placement of the backup server components – within a virtual machine

and on a separate servers o Advantages of storing virtual disks on SAN-mounted virtual machine file system (VMFS) o File system-consistent protection of virtual machines

• Disaster recovery options for virtual machine environments

o Physical-to-Virtual (P:V) data replication to enable data consolidation and disaster recovery o Virtual-to-Physical (V:P) and Virtual-to-Virtual (V:V) recovery options o Using replication to migrate data from P:V during initial virtual machine deployment

CommVault provides a unified architecture for data management, one that integrates data backup and recovery with replication, snapshot and archive – all managed from a single GUI console. CommVault’s modular design creates a variety of options for deploying data protection and management capabilities into a VMware environment. CommVault is particularly well-equipped to enable a cost-effective, scalable, and easy-to-use data management solution with the full range of options needed for reliable protection of VMware virtual infrastructure.


3

Understanding the Disk Structure of VMware ESX Server and VMware Server Systems Before we discuss the options for protecting and managing VMware data, it’s necessary to understand the structure of the ESX Server disk and virtual machine environments. If you are already familiar with ESX Server systems, you can proceed to the section titled, “Options for Protecting an ESX Server with CommVault Software.” VMware provides its own file system called the Virtual Machine File System (VMFS) for storage of the component files of virtual machines. VMFS is optimized for storage of large files—for example, virtual files. VMFS-2, used by ESX Server 2, can span multiple LUNs or physical disks, and may exceed 2 terabytes in capacity. ESX Server is the foundation of datacenter-class virtual infrastructure, serving mission-critical environments. Because ESX Server runs directly on the hardware, it provides more scalability, providing resources to run many more virtual machines than ”hosted” architectures. In contrast, VMware Server is enterprise-class virtual infrastructure software suitable for workgroup consolidation and usage. It installs as an application on top of a “host” OS, (Windows or Linux) as its base operating environment. This does simplify both set up and use, at cost of performance and scalability. Both ESX Server and VMware Server support virtual machines running mixed combinations of Microsoft Windows, Red Hat Linux, Novell NetWare, SuSE Linux, Sun Solaris, and other operating system platforms. Note: VMware Server is the name for the free virtualized server environment introduced by VMware in early 2006, which replaces and supersedes the VMware GSX Server system. In this white paper, descriptions of support for VMware Server refer collectively to ESX, GSX and VMware Server versions unless ESX-specific capability is specifically described.

Figure 1. Logical Depiction of ESX Server and VMware Server with Virtual Machines


4

Disk Files and Redo Logs on ESX Server In its simplest use, all of the information contained in the virtual machines running on an ESX Server resides in disk files on the VMFS. These files, which generally end in a [.dsk] or [.vmdk] file extension, may be used to do backup of the entire virtual machine. While the virtual machine is in operation these files remain open and in-use, therefore, VMware has provided methods for gaining access to these files to allow them to be backed up. Obviously, one method for releasing the lock on the virtual disk file is to stop the virtual machine entirely during the time that the file is backed up. As this is infeasible for the vast majority of all applications, VMware provides a procedure for releasing the disk file. To do this, ESX adds what is called a “REDO” log to the base vmdk file. All writes from the virtual machine to its disk are trapped in this REDO log, allowing the base vmdk file, to be backed up freely. The details describing when and how to do this are provided later in this document.

Table 1. VMFS Files Capturing Virtual Machine Image

File What it Captures

file.vdmk Base disk image, where “file” can be any name given to the base disk.

basefile.vmdk.REDO Redo log for the base diskfile.vmdk, capturing the changes to the base disk written since the disk snapshot was taken. Provides a bit-by-bit Consists of a bitmap map of changes to the base disk.

Raw Device Mappings (RDMs) In more advanced usage, VMware ESX Server has the flexibility to map virtual machines to raw LUN devices. Information about the raw LUN is stored in a mapping file, providing a consistent location for the virtual machine to find its disk across ESX Servers – even if the LUN is presented differently to each. Please note that some methods of data protection are not supported when Raw Device Maps (RDMs) are used.

Data Protection Considerations for ESX Servers To ensure recovery of the VMs on an ESX server, two main components must be protected:

• Virtual disks – which contain the guest OS, applications and their data • Virtual machine configuration files

In addition, protection of the Service Console of ESX Server may accelerate system rebuild in a disaster-recovery scenario. The Service Console may be thought of as a specialized virtual machine that works as a user interface to the ESX Server and the VMs running on it. The Service Console is nearly stateless. It may not be necessary to back up the Service Console as frequently as the virtual machines and their associated data.


5

Options for Protecting an ESX Server or VMware Server with CommVault Software There are several approaches for protecting an ESX Server or VMware Server, each of which has advantages and disadvantages. Which option is best for any given situation depends on the tradeoffs of each, and how these tradeoffs affect operational concerns. In most situations, a combination of options may be employed to maximize flexibility of recovery. CommVault has found that most administration teams combine these options for maximum protection benefits. CommVault Galaxy backup and recovery software is flexible and modular – so you can select the protection option for VMware that makes the most sense for you. Reduced-cost Galaxy VMware iDataAgents are available for file systems and ensure a good value for your protection in virtualized environments – rather than charging full price for agents running in each virtual machine. Table 2 summarizes the options for protecting a VMware environment, along with the advantages and disadvantages of each option. These options are described in detail following the table.

Table 2. Summary of Data Protection Options for ESX and GSX Server Environments

Protection Level

Options Advantages Disadvantages Considerations

Option 1A. Virtual Machines Run Backup Agents Backup data sent across the network to a separate backup server with backup devices attached

• Uses consistent backup methods and operations across your entire infrastructure

• File-level backup and recovery

• “Hot” backup of applications data

• Email-level and document-level recovery options

• Use of all backup options, including fulls, incrementals, differentials, and synthetic fulls

• Backup loads are multiplied across the physical machine – a small percent for each virtual machine is multiplied by the number of virtual machines on a given host

• Backup data must be sent across the network

• Usable with all virtual disk formats and RDM disks

• CommVault backup agents for Windows and Linux file systems include protection of OS and application configuration

Granular Protection of Virtual Machine Data For ESX Server and VMware Server

Option 1B. Virtual Machines Run Backup Agents Backup devices connected locally to one of the virtual machines

• Same advantages as for 1A

• Backup loads on virtual machines must include the management of locally attached backup devices in ONE of the virtual machines

• Only available with SCSI-attached backup devices

• Same considerations as for 1A

RDM-based off-host backups

Option 2: Using RDMs • Removes backup components from ESX Server – no backup load

• Provides file-level backup and recovery

• Requires SAN snapshot software

• ESX architectural limits reduce maximum Virtual Infrastructure famr size

• Preferred when RDMS are called for: high performance demands for I/O within a virtual machine’s daily operation

Granular Protection of Virtual

Option 3 VMware Consolidated Backup

• Removes all backup components from the ESX Server environment

• Limited to Windows VM’s only

• Extended integration

• Requires ESX Server version 3.0

• Starting with Option 1


6

Protection Level

Options Advantages Disadvantages Considerations

Machine Data For ESX Servers only

entirely – no backup load • Still provides file-level

backup and recovery for Windows virtual machines

required for application-level protection

• Works only on SAN-attached storage

• Works only on ESX Servers

today provides easy migration forward from current CommVault deployment – just add a Proxy iDA & system

“Crash-Consistent” Protection of Virtual Machines For ESX Servers only

Option 4. Backup the Virtual Disk Files on ESX Server

• Protects the virtual machine environment and enables its recovery including OS and applications configurations

• Crash consistent point-in-time backup copy (until ESX 3.0)

• Enables disk snapshot to provide near-line backup protection

• Extremely valuable for disaster recovery protection: backing up disk files protects the entire virtual machine.

• Reduces the backup components required

• No file-level recovery for file systems nor granular recovery of applications data

• No applications-awareness

• Backup process must be optimized to protect >2GB file sizes

• Recovery process may be more difficult and require more steps

• Usable only with virtual disks (any format)

• Not usable with RDM disks

• With ESX 3.0, this style of backup will become filesystem-consistent

Protection Option 1: Treating Virtual Machines as “Real” Machines To use this option, Galaxy software may be deployed within VMware virtual machines just as if the VMs were separate physical servers. This applies to virtual machines running on VMware Server and ESX Server systems. One advantage of this approach is the ability to run traditional incremental, differential and synthetic full backups in addition to full backups—using all the capabilities of Galaxy software. Using this approach also prepares for migration to ESX Server 3.0 when that version is available from VMware. The major disadvantage of this method is that it does not take advantage of the encapsulation feature inherent in VMware virtual machines. Note that you can combine this approach with “crash-consistent” protection, for comprehensive disaster recovery capability. Combining these approaches is recommended. By treating VMs as “real” machines, you are able to install Galaxy iDataAgents (iDAs) within the virtual machines and then use a Galaxy CommServe deployed on a “real” system to protect those environments by sending backup data across the network. Figure 1 depicts an ESX Server with four virtual machines, each of which are protected by a Galaxy backup server running on a separate physical machine. The file systems and applications running within the virtual machines are protected normally using Galaxy file system and application iDAs. Backup and recovery is performed using the normal Galaxy process, with each virtual machine presented as a unique client system within the Galaxy Unified Console.


7

x86 Architecture

VMware Virtualization Layer

Application

Operating System

VMware Server

Application

Operating System

Application

Operating System

Application

Operating System

CommVault CommServe

& MediaAgent

iDAiDAiDAiDA

PowerVault MD1000

PowerVault ML6010

Figure 2. Typical Deployment of CommVault Galaxy Software

Protecting an ESX Server Virtual Machine Environment

Note that in this scenario, Galaxy software makes it simple to configure data movement from the virtual server environment into the backup server using standard Galaxy configuration options over the LAN. Backup devices, whether disk or tape, are configured and managed from the Galaxy MediaAgent running on the backup server and can be shared among all virtual machines as well as other systems. In most cases, a single Galaxy MediaAgent backup server supports multiple VMware Server systems. These drives can also be specifically allocated to protect specific virtual machines if you desire, again using standard Galaxy configuration options.

Obtain Cost-Effective Virtual Machine Protection CommVault offers unique licensing of VMware iDAs (VM iDAs) for file systems running in virtual machine environments. Galaxy FS VM iDAs perform the same protection functions as Galaxy FS iDAs, but are offered at a significantly reduced price point. On a VMware system running more than one virtual machine, CommVault requires a “real” Galaxy FS iDA on only the first virtual machine. All other virtual machines may run Galaxy FS VM iDAs. An appropriate configuration showing an FS iDA and three FS VM iDAs is shown in Figure 3.


8

Figure 3. CommVault Virtual Agents Provide Best Value for

File-Level Backup and Recovery of Virtual Machine File Systems

Depending on the number of virtual machines that you are running on your VMware Server, the value of this unique licensing from CommVault can be dramatic.

Protecting Virtual Machine System State Unlike most other backup options described by VMware for protecting virtual machines, treating virtual machines as “real” systems does not provide the added benefit of being able to protect and recover the entire virtual machine all at once. Being able to protect and recover the encapsulated virtual machine and its configuration is, therefore, a unique advantage of using virtual disk files as a means for protecting virtual machine file system and application data. With CommVault Galaxy protection, however, this full system state protection for both Windows and Linux file systems along with individual file protection and recovery is available from within virtual machines – because CommVault builds it into the FS iDA. For this reason, the advantage of combining “real” system support with virtual disk file support is primarily for ease of restoration on dissimilar hardware. In other words, combined protection enables faster and easier disaster recovery. If you are DR requirements, a combined approach is recommended.

Avoid Sending Backup Copies Across the Network It is possible to avoid sending backup data from virtual machines in a VMware Server across the LAN. Doing so, however, requires the Galaxy MediaAgent be deployed within a virtual machine, which will then be bound to a backup device. The Galaxy MediaAgent will then manage this device. This is recommended to be a shared backup device for all virtual machines running together on the VMware Server system. Running MediaAgents in more than one virtual machine attached to more than one backup device, is also supported, depending on factors including amount of data to be backed up, and what load a particular virtual machines can support. This type of configuration is seen most frequently in branch offices, in which having an extra physical machine to simply do tape backups is untenable. This option allows the media server to run inside of a virtual machine, eliminating the need for the extra hardware.


9

With the MediaAgent deployed, attach the appropriate backup device – which can be disk or tape – to a SCSI port on the VMware Server. Then, use the VMware Server Web management interface to assign the device to the appropriate virtual machine. When the device is “seen” in the virtual machine, it is available for configuration using normal Galaxy procedures. Figure 4 depicts how this configuration would look. Note: Although not shown in the figure, CommVault Galaxy customers also successfully run the CommVault CommServe with its management console within virtual machines – thus further avoiding the need for additional hardware and equipment.

x86 Architecture


Application

Operating System

VMware Server

Application

Operating System

Application

Operating System

Application

Operating System

CommVault CommServe

Media Agent

iDA VMiDA

VMiDA

VMiDA

iDAiDAiDAiDA

PowerVault ML6010

Figure 4. Deployment of CommVault Galaxy Software Managing

Backup Devices Connected Directly to the VMware Server

Note: Only SCSI-attached devices are supported. SAN connected backup devices are not supported at this time. This is again consistent with the environments typically found in remote office locations. In this configuration, all of the data to be backed up from each virtual machine on the VMware Server is written to tape by the Galaxy MediaAgent running in the fourth virtual machine. Therefore, backup data is not sent over the physical LAN.

Protection Option 2. Preparing Today for ESX Server Backup Options Available Tomorrow With the release of ESX Server 3.0, VMware is providing an enhancement which enables backup and protection of Windows file system data from a separate backup server – without having to send backup data over the network AND without having to manage locally-attached backup devices from a virtual machine. This approach is limited only to the Windows file system data. Other operating system environments are not currently supported.


10

This configuration requires the use of a SAN-attached storage volume and a Windows 2003 proxy server to back up the data. CommVault Galaxy Proxy iDA works with VMware’s Consolidated Backup framework to enable this workflow. First, the Proxy iDA requests the Consolidated Backup (VCB) framework to mount a specific VM on the proxy server as a snapshot. The VCB Framework talks to the virtual infrastructure to add a REDO log to the VMDK of that virtual machine, then present the now-static VMDK to the backup proxy as a locally mounted filesystem within the Windows proxy. The Consolidated Backup framework then notifies the backup software that the snapshot image is available. CommVault Galaxy software running a Proxy iDA on a separate backup server then backs up the snapshot as if it was a normal Windows file system. The Galaxy Proxy iDA keeps track of the virtual machine associated with the backup, to make data recovery easy and intuitive. Recovery operations are transparent: simply select the original Client name as before, browse the backup data, and complete the recovery – just as if the backup had been done using a FS iDA running in the virtual machine. CommVault simplifies migration to ESX Server 3.0: The infrastructure used for backups can remain the same until the Proxy iDA is in place—when converting to ESX 3, simply add the Proxy iDA to the backup server connected to the SAN. Galaxy software ensures that the virtual machine data is recoverable before, during and after the migration.

Figure 5. Depiction of the Process of Migrating CommVault

Data Protection Components for ESX Server 2.5 to ESX Server 3.0 – All Components Remain the Same with the Addition of a Proxy Agent

In the ESX Server 3.0 configuration, CommVault embeds pre- and post-processing commands into its backup operation to automate the process of obtaining the virtual machine snapshot. This includes committing the aforementioned REDO log after the backup is complete, returning the virtual machine to normal operations. Data recovery using this scenario is the same as performing a normal, file-based recovery process for each virtual machine – each of which is managed as a Galaxy Client in the Unified Console.


11

Figure 6. Galaxy Unified Console Managing Backup and Recovery of Four Virtual Machine Clients Running on an ESX Server System

Protection Option 3: Treating Virtual Machines as Files on an ESX Server This option takes advantage of the unique storage architecture of VMware ESX Server. Because virtual machines are encapsulated in a small set of files, backup and recovery using this method is significantly simpler than similar operations on physical infrastructure. With ESX 2.5.x, when using this method, the backups obtained will be crash-consistent. With the release of ESX 3.0, all backups using this method are filesystem consistent. Combining this method of protection with granular protection of individual virtual machines is recommended when disaster recovery is a consideration. For example, you can deploy a single Galaxy iDA for Linux file system protection on the ESX Server to protect the entire ESX Server and all of its virtual machines. This presents two advantages:

• First, recovery of OS, filesystem data, and application within the virtual machine is accomplished with a restore of a single file.

• Second, because VMware presents a consistent virtual hardware platform across dissimilar physical hardware devices, “bare metal” recovery of virtual machines does not require identical source and destination hardware.

In this deployment, a single Galaxy Linux File System iDA is deployed at the physical machine level of the ESX Server. Similar capabilities exist in conjunction with VMware Server, though as the host OS for VMware Server may be either Windows or Linux, the FS iDA may be either in that case as well.


12

x86 Architecture


Application

Operating System

VMware Server

Application

Operating System

Application

Operating System

Application

Operating System

iDA

CommVault CommServe

& MediaAgent

PowerVault MD1000

PowerVault MD6010

Figure 7. Basic Protection of an ESX Server at the Physical System Level

Using this option requires a plan to protect and recover what may be very large files—much greater than 2GB in size. In cases in which recovery of a single file within a guest filesystem is required, the first step is to recover the entire virtual disk. Obviously, this may take significantly longer than recovery of the single file. This option is most effective when used in the context of disaster recovery. Because of the aforementioned hardware-independence, backing up an entire virtual machine in one pass is an extremely effective foundation for a low-cost disaster recovery strategy. An option for reduction of backup size is to utilize the [vmkfstools] command with the [–export] option as a means to potentially shrink the size of the virtual disk file; for more information see the discussion on [vmkfstools] provided in the “More Details” section later in this document. By default, virtual disk files cannot be protected while the virtual machine is running. To protect a virtual disk file a redo log must be added – which makes the virtual disk file static and, therefore, available for backup.

How CommVault Disaster Recovery Capabilities Enhance VMware Disaster Recovery Operations CommVault provides unique disaster recovery capability that makes it faster and easier to rebuild a CommVault CommCell and the Galaxy index database. DR is an Advanced Feature Pack option offered with Galaxy software, as a built-in method for rapid rebuild. Often times, the process of rebuilding a backup server environment can take significant time and unnecessarily delay recovery operations by days and even weeks of time. The time is usually required to scan tapes and rebuild catalogs or indexes, along with redeploying backup software. CommVault Galaxy software simplifies and accelerates rebuilding the backup environment and re-establishing the index database, so that recovery operations can begin much more quickly. This enhances and extends the DR benefits provided by VMware. For more information on using CommVault Galaxy software in combination with VMware Server systems for disaster recovery, see the detailed best practices guide entitled “Best Practice Disaster Recovery Guide for VMware Server Systems Protected with CommVault Galaxy Software.”


13

More Details on Using [vmkfstools] Commands to Gain Access to Virtual Disk Files VMware provides the [vmkfstools] command set to perform a variety of management tasks for virtual disk files. This command set is optimized to work with very large files of >2GB in size, and is used to manage redo logs as well as base disk files in the VMFS environment. Complete instructions for the use of [vmkfstools] commands are documented in the ESX Server Administration Guide. One use of [vmkfstools] that can assist with backup is to export virtual disk files into 2-GB pieces. One effect of the export can be to dramatically shrink the size of the file, using the shrink option which zeros out all unused parts of the virtual disk file. Performing this export prior to backup can, therefore, dramatically reduce the time required for backup and recovery of the file, as well as reduce the size of the disk or tape required to store it. Note that the export command cannot be used to segment redo logs. Export in this manner will shrink virtual disk files most dramatically – and help most for backup and recovery – when only a fraction of the disk space allocated to a given virtual machine is used. As is described above for the Consolidated Backup Framework in ESX Server 3.0, Galaxy pre- and post-processing commands can be helpful to automate the process of releasing the virtual disk files and enable their backup. The sequence of steps required for each virtual machine is as follows:

1. If there is an application running in the virtual machine, quiesce the application. This ensures that the virtual disk file contains a coherent set of application data for backup protection.

2. Create and apply a REDO log to release the virtual disk file. 3. Perform a backup of the virtual disk file image. 4. Commit the REDO log to apply to the base disk changes made since the REDO log was created, and

return the virtual machine to normal operations.

Using [vmsnap] and [vmres] Commands to Assist Backup and Recovery VMware provides the [vmsnap] and [vmres] commands as separately installable Perl scripts, which can be embedded into CommVault Galaxy pre- and post-processing operations. The [vmsnap] script performs ESX Server snapshots of virtual disks, to store point-in-time snapshot copies of disks, config, log, and nvram files with little or no virtual machine downtime. You can use a local or remote archive directory. CommVault Galaxy can then perform backup of these snapshot copies quickly and easily.


14

Step-by-Step Protection of a VMware ESX Server Virtual Machine CommVault Galaxy provides protection of VMware virtual disk files without having to shut down the virtual machine environment, using the following method: 1. CommVault Galaxy is deployed to protect VMware ESX Server virtual machines. Galaxy File System iDA

for Linux is deployed on the VMware system, in the Service Console 2. Run [vmsnap.pl] to create a local snapshot (also called a backup by VMware) of the virtual machine. For

example:

[root@localhost VM1winXPPro]# vmsnap.pl – c /root/vmware/VM1winXPPro/winXPPro.vmx –d /vmimages/winXPProsnap -1 In this example, we are snapping a virtual machine with the configuration file located in [/root/vmware/VM1winXPPro] locally to a directory [/vmimages/winXPProsnap] without segmenting the disk files. The snapshot includes a virtual machine configuration log file, log files, and the disk file. This command may be run run manually, but a better alternative is to embed this command in the Galaxy pre-processing operation – so that the [vmsnap] is performed as part of the backup operation itself.

3. In the CommVault Unified Console, configure a new Storage Policy that protects the VMware system

hosting the virtual machines. This is also the time to embed the pre-processing command, if desired. 4. Enter the fully qualified path to the files of the [vmsnap] output, in this case:

/vmimages/winXPProsnap/WinXPPro/* 5. Perform an on-demand backup by right-clicking on the VMware system client name in the Console – and

specify on-demand backup. You can also set a regular backup schedule for the Storage Policy, using full backup protection.

To recover the virtual disks, simply right-click on the client name in the CommVault Unified Console and select the files for recovery. Galaxy restores them to the [vmsnap] path name location. Use the VMware [–import] command option to then bring the recovered virtual disk file back into the virtual machine environment. The [–import] command can be embedded in Galaxy post-processing to automate that portion of the procedure.


15

Extending Data Management into Virtual Machine Environments Using CommVault Replication CommVault ContinuousDataReplicator (CDR) software provides continuous, real-time capture and wide-area replication of Windows data written to disk. CDR operates on Windows host-based environments, and is fully supported on Windows virtual machines hosted on ESX Server or VMware Server systems. CommVault CDR can assist with movement and protection of Windows virtual machine data, in many ways:

• By centralizing Windows data from physical to virtual (P:V) systems, so that you can run backup and recovery operations on a centralized virtual system to save on hardware and equipment

• By migrating Windows data from physical to virtual (P:V) systems, as part of the initial deployment of

virtual machines.

• By continuously replicating data from physical to virtual (P:V) systems, for disaster recovery purposes when the cost-savings offered by virtualized environments for disaster recovery infrastructure are compelling—rather than having to duplicate the primary site, it may be consolidated into fewer physical systems.

• By continuously replicating data from virtual to virtual (V:V) systems, for data centralization and

protection at a centralized site from remote virtual systems

• Virtual to physical (V:P) replication is also fully supported, for full flexibility and recovery of data


16

Key Features and Benefits for VMware Server Systems Protected with CommVault Galaxy Software Key Feature Benefit

Easy, fast recovery of file system, database and application data using object-level recovery capability

Fast data recovery and business resumption. No need to recover an entire Exchange database, SharePoint database, or volume – which could take days – when all you need is a single data object which restores in minutes. The same granular recovery benefits apply to VMware virtual machine file system environments, and applications that may be running there including SQL Server, Oracle, Exchange, Lotus Notes, GroupWise, and SharePoint.

Easy right-click selection among multiple file versions

See multiple versions of the same file, and easily select all, some or one to recover the exact version that your business-user requires. This can enable recovery of multiple versions of the same VMware virtual disk files, for selection from multiple point-in-time copies.

OnePass Restore volume-level recovery Speeds recovery and reduces tape wearing, by restoring all data using a single pass through the tape without needing to recover multiple versions of the same file like other backup offerings do.

Distributed relational index Eliminates issues typically associated with managing backup software catalogs. Relational structure ensures high-speed performance for index look-ups. Double-commit store of index ensures recoverability, and eliminates the need for administrative management of the index.

Full, incremental, differential and synthetic full backup options

Enables most efficient data protection possible, and with appropriate use of storage media to ensure just as rapid recovery from synthetics as from fulls.

Easy Auxiliary copies, configurable for inline, selective, synchronous, or cascading

Ensures compliance with policies for data protection and retention, and ensures recoverability since a copy of the data is always available.

Granular backup job control and management Fine-tune operation by controlling all jobs by queue, pre-emption, priority, on-demand restart, and update interval. Suspend, resume or kill any job using the Job Controller Window at will.

Multi-streaming and multiplexing Depending on backup needs, such as when managing many small files or when writing to fast-performing drives, these capabilities can offer improved performance and efficiencies to perform backups more quickly and fit into smaller windows.

Round-robin load balancing of backup loads using available systems

Perform backups more quickly and fit into smaller windows, by dividing backup loads among UNIX, Linux, NetWare and Windows systems.

Efficient port utilization when backing up through firewalls

Depending on your needs and configuration, as few as two ports are required to backup through a firewall, saving money and resources.

Dynamic and static disk sharing Increase ROI from expensive disk storage, by sharing access to disk with static and dynamic configurations.

Span disk mount points Configurable to “spill and fill” or “fill and spill” according to your requirements, reduces problems with disk management by enabling Galaxy backup to work across multiple mount points and treat them as a single disk device.

Data aging, which is the automated pruning of older data from disk

Saves disk space and reduces backup failures, by removing data that has aged past your immediate-term retention requirement. This can also be overridden for specific backup jobs that you need to retain.

Disk space monitoring with configurable watermarks

Saves disk space and reduces backup failures, by monitoring available disk space, tracking disk usage for trend analysis and capacity planning, and triggering automatic pruning of aged data when watermarks are reached. You can also set alerts to notify you when disk thresholds are exceeded.

Shared library management Increased ROI on expensive library equipment, by providing shared access to libraries and built-in robot management from multiple backup servers. Because library sharing is built-in to Galaxy software, it is easier to deploy, manage, and maintain than with other backup offerings.


17

Key Feature Benefit

Shared drive management Append data and fill removable media such as tape, rather than wasting tape and increases your costs if tapes are not filled when you need to rotate them off-site.

Management of more than one type of drive in the same library

Avoid the need for expensive add-on or third-party software to manage different types of tape drives in the same library.

Encapsulation of Virtual Machines into files. Create full system backups by backing up single files for archival or disaster purposes

Hardware Independent of Virtual Machines Allows for cost-effective disaster recovery plans: last generation hardware may be used for DR instead of requiring identical hardware at primary and DR site

VMware Consolidated Backup Framework Easily offload backups from production or critical ESX servers while maintaining easy integration with existing backup schemes


18

System Requirements A minimum Galaxy data protection environment requires one CommServe system to establish the CommVault Unified Data Management environment, one system to run the Console, and one MediaAgent to perform the backup and recovery operations. Client systems running applications, databases, and file systems can then be protected. CommVault ContinuousDataReplicator (CDR) is supported on Windows systems running in the CommVault data protection environment and is deployed as an add-on module. CDR is managed through the same Unified Console as Galaxy data protection.

Galaxy Component System Requirements

CommServe System Windows 2000 or Windows Server 2003

Console JAVA App Windows NT, Windows 2000, Windows XP, Windows Server 2003, or Mac OS

Console JAVA Applet AIX, HP-UX, or Solaris with Netscape Red Hat Linux with Mozilla Windows NT, Windows 2000, Windows XP, Windows Server 2003 with Microsoft Internet Explorer

MediaAgent backup and recovery operations

AIX, HP-UX, Solaris, or Tru64 OSF1 UNIX Red Flag, Red Hat, or SuSE Linux NetWare Windows 2000, Windows Server 2003 and Storage Server VMware ESX or GSX Microsoft Virtual Server

See it For Yourself To find out more about how Galaxy Backup & Recovery along with other parts of CommVault’s Unified Data Management suite can save your time and money along with your data, visit www.dell.com/galaxy or visit us at: www.commvault.com.

The information contained in this document, including all instructions, cautions, and regulatory approvals and certifications, is provided by CommVault and has not been independently verified or tested by Dell. Dell cannot be responsible for damage caused as a result of either following or failing to follow these instructions. All statements or claims regarding the properties, capabilities, speeds or qualifications of the part referenced in this document are made by CommVault and not by Dell. Dell specifically disclaims knowledge of the accuracy, completeness or substantiation for any such statements. All questions or comments relating to such statements or claims should be directed to CommVault.

Visit www.dell.com for more information.

http://www.dell.com/galaxy

http://www.commvault.com/

protecting vmware environments with commvault software and … · 2007-03-07 · protecting vmware...

Documents