Your SlideShare is downloading. ×
Protecting Virtual Machines
Protecting Virtual Machines
Protecting Virtual Machines
Protecting Virtual Machines
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Protecting Virtual Machines

849

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
849
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
10
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. CA ARCserve® Backup r12, CA XOsoft™ Replication r12, and CA XOsoft™ High Availability r12 – Virtualization Support Server virtualization is becoming widely used because of benefits such as reduced hardware and power costs, but to realize these potential benefits it is essential that virtual machines (VMs) are protected by using specific data protection technologies. Virtualization can also be an important recovery management and business continuity technology, if used with appropriate management and backup tools. Overview Benefits CA ARCserve® Backup r12, CA XOsoft™ Replication r12, CA ARCserve Backup r12, CA XOsoft Replication r12, and and CA XOsoft™ High Availability r12 provide several key CA XOsoft High Availability r12 provide the following features that enable you to both protect virtualized servers virtualization support benefits: and benefit from server virtualization in your overall recovery management strategy: • Snapshot technologies to backup VMs, without adversely affecting VM performance. • Protect virtualized servers by using the Agent for VMware or Microsoft Volume Shadow Copy Service - • Simple disaster recovery procedures to enable rapid based snapshots for snapshot-based backups. physical-to-virtual bare-metal restores. • Restore physical servers to VMs. • Replication and failover technologies to enable VMs to be used as cost-effective replica and standby systems. • Use VMs as disaster recovery hosts. Protecting Virtual Machines Server virtualization is becoming widely used to help organizations to reduce hardware and power costs. However, VMs must be protected by using specific data protection technologies, such as CA ARCserve Backup r12, which uses snapshot technologies to backup VMs, without affecting VM performance: • For VMware VMs, CA ARCserve Backup includes a new Agent for VMware, which uses VMware Consolidated Backup (VCB). By using the CA ARCserve® Backup r12 for Windows Agent for VMware and VCB you can offload VM backup activity to a dedicated backup proxy system and the proxy system can access and mount VMware snapshots for backups. • For Microsoft Virtual Server 2005 SP2, and the new Hyper-V virtualization, CA ARCserve Backup integrates with Microsoft Volume Shadow Copy Service (VSS) snapshots to create point-in-time copies of VMs, and then uses VSS writers to back up these VM snapshots. The CA solution for protecting VMware VMs consists of the following components: • CA ARCserve Backup server • CA ARCserve Backup Agent for VMware • VMware Consolidated Backup VMware Consolidated Backup CA ARCserve Backup r12 provides backup support for VMware virtual servers, by using VCB. A storage area network (SAN) is required to perform VCB operations; by using a SAN you reduce the overhead on your VMware ESX server and you can significantly increase the speed and performance of backup operations. You can also back up a VM that is not powered on. The following figure shows a typical VCB environment using CA ARCserve Backup.
  • 2. With VCB, you can also use a backup proxy server to offload the backup tasks, which reduces the impact that backing up has on the LAN that is used by your VMs. By using a VCB proxy, you transfer data to the backup server through the SAN and the backup proxy, rather than directly across the network from the VMs. To support VCB, you must also store your VMs on a SAN that is accessible from your CA ARCserve Backup proxy server. Your VCB server must be running Windows 2003 Server and have access to the SAN where your VMware images are stored. After installing VCB you can view and backup all of your physical and virtual servers from a single CA ARCserve Backup console. By using a single console, you can perform your entire backup and restore procedures for physical and virtual servers from the same location. CA ARCserve Backup r12 provides a logical view of your physical and virtual servers, which enables you to perform backup and restore operations from backup catalogs without seeing the complexity of your virtual environment. You must register one CA ARCserve Backup Agent for each ESX server that is running in your VMware environment, so you do not need to deploy a backup agent onto every virtual server. Another advantage of VCB is the additional restore and recovery options that enable you to take incremental and differential backups of your VMware environment by using the CA ARCserve Backup r12 console. CA ARCserve Backup VMware Agent The CA ARCserve Backup agent allows you to backup raw VM files including the entire VM, and to perform file-level VM backups on supported Windows systems. Raw backups are useful if the operating system you plan to back up is not a VMware supported Windows-based operating system. After installing CA ARCserve Backup r12, you must populate the CA ARCserve Backup database with the details of your VMs by using the CA ARCserve VMware Configuration Tool (available through the ca_vcbpopulatedb script, or the VCBUI utility). You should run the CA ARCserve VMware Configuration Tool periodically so that you can browse all of your VMs in CA ARCserve Backup Manager. You should always run this tool immediately after the following events: • Enabling of virtual servers that were unavailable the previous time that you populated the ARCserve database. • Adding or removing a volume from a virtual server. • Deleting or moving a virtual server from an ESX server. CA ARCserve Backup Integrated Anti-virus CA ARCserve Backup includes integrated anti-virus. This enables you to configure anti-virus scanning during backups, so that you do not need to add overhead by running virus scans on the VM, and you do not need to install and manage separate anti-virus agents on all of your virtual servers. Restoring Backup Data The restore process for data contained in a VM in CA ARCserve Backup r 12 is identical to restoring from any physical server. By using a familiar restore process, you can reduce your administration and training requirements, which saves time and money. The following limitations apply to the restore process on a VM:
  • 3. • To restore files to their original location on a VM, you must install the CA ARCserve Backup Client Agent for Windows. • You can only restore raw, full VM backups to an alternate location. • To restore data you must use the appropriate CA ARCserve Backup Agent, such as the Agent for Windows for file server backups, to transfer the data across the network, by using exactly the same procedure that you would for a normal restore. Restoring to Bare-Metal by Using Virtual Machines By using the Disaster Recovery tools in CA ARCserve Backup and the data replication features in CA XOsoft Replication, it is easy to restore physical servers to a bare-metal virtual server, which has no operating system or application software and is restored to a previously backed up state. Using physical-to-virtual (P2V) restores to a bare-metal virtual server reduces both downtime and disaster recovery costs, and gives you time to fix problems on the physical primary server. If you have a backup of your physical servers, or a backup of raw VMs, you can restore a working server quickly and efficiently by using disaster recovery restore options to restore a backup to a virtual server. To restore to a bare-metal server you must have created a backup by using the disaster recovery tools in CA ARCserve Backup r12. This process creates a bootable CD/DVD that you can use to recover from server failure. By enabling you to add drivers to your bootable image CD/DVD, CA ARCserve Backup r12 simplifies the recovery process and provides additional flexibility for server recovery. You add drivers through the GUI when creating a bootable disaster recovery CD/DVD, which allows you to easily select drivers and add them to your recovery CD/DVD. By adding network drivers, you can quickly restore data from a file share or Network Attached Storage device, which can decrease the time taken to recover a server. CA ARCserve Backup r12 provides the following data restoration features: • Restoring data from full backups • Restoring data from incremental backups • Restoring data from differential backup • Recovering data using password encrypted backup files • Restoring data from NAS or file shares • Adding additional drivers to images CA ARCserve Backup r12 supports the following Windows versions: • Windows 2000 • Windows XP • Windows 2003 • Windows 2008 • x86, x64 and IA64 architectures By restoring to a VM, you can circumvent any potential delays in restoring data that are caused by waiting for delivery of replacement hardware for failed servers. By using virtual servers to perform disaster recovery, you can also practice your disaster recovery techniques and minimize the costs that are associated with additional disaster recovery hardware to replicate every physical server in your organization. This recovery method enables you to restore data to any hardware that is available and has sufficient disk space. Virtual Machines as Disaster Recovery Hosts Virtualization can also be an important recovery management and business continuity technology, if used with appropriate management and backup tools. You can use CA XOsoft Replication and CA XOsoft High Availability with virtual servers to
  • 4. create cost-effective replica and stand-by servers. By replicating data to a virtual server, and then using CA ARCserve Backup to backup replicated data, you can reduce, or eliminate, the potentially high processor and network bandwidth requirements of traditional backup windows by using continuous low bandwidth replication to your central data center and then using traditional backup methods to back up the replica servers. One of the most significant server virtualization benefits for many organizations is the ability to replicate multiple physical servers to a virtual environment to create a cost-effective disaster recovery solution, as shown in the following figure. CA XOsoft Replication is easily installed on a VM to provide full replication to a virtual replica server. With CA XOsoft High Availability, you can configure failover from a physical server to a virtual server, and depending on your application requirements, you may be able to consolidate your standby servers so that several physical master servers are configured to failover to a single host computer that is running multiple virtual standby servers. The CA XOsoft Assured Recovery option, adds low impact backups, by automatically creating VSS snapshots, and it is the snapshot that is backed up rather than the live, shared file system. Summary The virtualization support features in CA ARCserve Backup r12 and CA XOsoft Replication r12/CA XOsoft High Availability r12 enable you to both protect virtualized servers, and to use server virtualization in your overall recovery management strategy. You can protect VMs by using snapshot-based backups, easily restore physical servers to VMs, and use VMs as disaster recovery hosts. To get maximum value from your investment in CA software, CA Education can help you to get the right training for your unique challenges. Visit http://ca.com/education for additional training information. Copyright © 2008 CA. All rights reserved. All trademarks, trade names, service marks and logos referenced herein belong to their respective companies.

×