An IBM Proof of Technology
Tivoli Storage Manager for Virtual Environments
Tivoli Storage Manager for Virtual
Environments Overview
Gary Graham | Tivoli Storage Specialist | [email protected]
© 2011 IBM Corporation
IBM Software
Analyst Predictions
How do you manage data protection and recovery in your virtual servers?
•Sources – Gartner, IDC, ESG
2 © 2011 IBM Corporation
IBM Software
Challenges and Requirements for VMware Backups
Backup Challenges
Large amount of data, large number of virtual machines
Very dynamic environment, especially if vMotion load balancing used.
Backup and Restore can impact physical machine and shared disk resources.
Requirements
Make backups more efficient to have less impact.
Centralize backup and automatically discover / backup new VMs
Allow backups to be offloaded from ESX/ESXi host
Support all recovery scenarios (file, volume and image) from a single source backup
Support the significant improvements provided with VMware vSphere™ 4 using the vStorage
APIs for Data Protection (VADP)
Provide simple to use GUI that is an extension of VMware’s vSphere client interface with
similar look and feel characteristics
© 2011 IBM Corporation
IBM Software
Traditional Backup Agent for Each VM Model
Backup Agent in each VM/Guest
Solution used by majority of
customers today.
Manage Agents, Backups and
Schedules just like a physical server.
Volume of Guests creates a
management headache.
Easy to overload the physical
machine’s resources.
LAN-Only
LAN
BMR of a VM using this method is a
two-step process (define and
configure a new VM, restore).
Benefits:
In-VM agents interface better with applications.
In-VM agents do allow better file-level archiving and
searches through backups.
© 2011 IBM Corporation
IBM Software
TSM for Virtual Environments
- Deployment Options
© 2011 IBM Corporation
IBM Software
TSM for Virtual Environments 6.2 Components
vStorage Backup Server
►Machine where the B/A client is installed
►VM guest machine or off-host physical machine
6.2.3 B/A Client
►Installed on 1 or more vStorage backup servers
►vStorage backup server can host 1 or more B/A client instances.
6.2 Data Protection for VMware Recovery Agent
►Centralized file-level restore for Windows and Linux
►Individual
VM guest file-level restore and instant volume restore for
Windows and Linux
6 © 2011 IBM Corporation
IBM Software
TSM for Virtual Environments
Use vStorage API for Data
Protection to interface with VMware
hypervisors or vCenter.
Backups of individual virtual
machines, including block-level
incremental backup.
VM, volume or file-level restore
capability from single backup.
Offload backups from hypervisor to
vStorage backup server LAN
SAN
Movement of VMs by vMotion will not break
or duplicate backups.
Physical vStorage
New or moved VMs are automatically Backup server
discovered.
© 2011 IBM Corporation
IBM Software
TSM for Virtual Environments
vStorage Backup Server(s) can be
physical machines or virtual
machines (or a combination of
both). Virtual vStorage
All virtual machines on a Backup server
hypervisor can be protected, or
specific ones can be selected for a
higher priority backup, excluded
from backup, etc.
VM backups, like all data to TSM LAN
will take advantage of all TSM data
management automation.
SAN
Virtual Machine backups can exploit native
TSM compression or deduplication, device
deduplication, etc.
© 2011 IBM Corporation
IBM Software
Example Backup Flow
TSM for Virtual Environments
contacts VMware to get list of VMs
to backup. The list will be
processed one VM at a time.
VMware will create a logical
snapshot of the virtual machine.
The vStorage Backup Server will
read the virtual machines data
directly over the SAN (or LAN if
SAN pathway is not available. LAN
The backup will proceed with the next
virtual machine.
The process can be multi-threaded if
SAN
needed.
© 2011 IBM Corporation
IBM Software
TSM for Virtual Environments and In-VM Agents can coexist.
You can run both TSM for Virtual
Environments and in-VM Agent
backups on the same Virtual
Machine(s).
You may wish advanced
application recovery (like SQL roll-
forward to a specific point-in-time)
which requires an agent on the
same machine as the application.
You can protect the application LAN
with daily backups, and perform
weekly virtual machine backups for
DR protection.
SAN
© 2011 IBM Corporation
IBM Software
Example Virtual Machine Restore
TSM for Virtual Environments
allows you to recover the virtual
machine to the original hypervisor
or datastore, or to redirect the
restore to other parts of the
VMware infrastructure. Supports
any OS.
During a virtual machine restore,
TSM for Virtual environments will
contact VMware to define and
configure the Virtual machine.
Data will be written directly to the LAN
datastore over the SAN (if that
pathway exists.
Once the restore completes the virtual
SAN
machine is ready for service once again.
© 2011 IBM Corporation
IBM Software
Instant Volume Recovery
TSM for Virtual Environments
allows you to recover a volume
(partition) to the original machine,
or any with the same OS (Linux or
Windows)
To start the Instant Restore, start
the TSM for VE recovery agent,
select the volume from TSM
backups, and begin the restore.
During the restore, users,
applications and the OS will
behave as if the restore completed
instantly!
After the volume is restored, there is
no need to disconnect users or SAN
applications already using it during the
recovery.
© 2011 IBM Corporation
IBM Software
File-Level Recovery
TSM for Virtual Environments
allows a previous backup of a
volume (partition) to be mounted to
the original machine or a machine
of the same OS (Windows or
Linux).
You can get access to the entire
volume without restoring it.
To begin the file recovery, start the
TSM for VE Recovery Agent and
select the volume within TSM, then LAN
click Mount.
You can copy files just as if you
were copying between 2 local
volumes. SAN
You can also perform other
functions to the mounted volume
(searches, consistency checking,
etc.)
© 2011 IBM Corporation
IBM Software
Best Practice: Define Data Center Level Node
By default, all of the backups
done by any vStorage Backup
Server will be tracked by
separate nodes within TSM. Hypervisors
This will cause problems if H1 H2 H3
virtual machines are moved
between hypervisors (manually
or by vMotion).
To prevent this problem, define Backup
a node to represent the B1 B2 B3 Servers
vSphere Data Center to which
all the hypervisors belong.
Grant the nodes associated
with the backup servers TSM TSM Nodes
B1 B2 B3
ProxyNode access and have
them do backups and restores
for the data center node.
DC1
© 2011 IBM Corporation
IBM Software
What should full backup cycle be?
Days between full backups
– Recommendation: 7 days or 14 days
Note about setting up schedules:
– TSM schedules normally are based on calendar week.
– To use TSM scheduler, should adhere schedule based on calendar week
15 © 2011 IBM Corporation
IBM Software
TSM for VE Demonstration Environment
© 2011 IBM Corporation
IBM Software
TSM for VE Demonstration Environment
© 2011 IBM Corporation
IBM Software
17 © 2011 IBM Corporation
