The document announces a seminar on Tivoli Storage Manager (TSM) 6.4 hosted by IBM and Peanuts. The agenda includes presentations on IBM and Peanuts, new features in TSM 6.3 and 6.4 like deduplication and replication, improved reporting, TSM and virtualization, and a demonstration of the solution.

1. IBM og Peanuts ønsker velkommen til seminar
Tivoli Storage Manager 6.4
Agenda:
• Om IBM og Peanuts v/Olaf Frøseth og Jan E.
Danielsen
• TSM 6.3 og 6.4
• De-duplisering og replkering over WAN/LAN
• Ny TSM rapportering
• TSM og Virtualisering
• Demonstrasjon av løsningen v/Roger Stakkestad

3. •
vStorage API
Utilize VMware vStorage APIs for Data Protection for image-level backup and recovery
File level backup through Backup Server, File level recovery through TSM B/A client
Full VM level backup through Backup Server
Full VM restore through Backup Server
vStorage API support TSM B/A client
Running on Backup
File-level backups
Server*
Full VM backups
Tivoli Storage Manager
Storage Pool
• vStorage APIs provides the
capability to read directly from
the ESX storage
* Backup Server can be a physical or virtual machine 3

4. CBT (Changed Block Tracking)
1. Snapshot of virtual guest
volumes (vSphere API) is
initiated
VM1
C: D: 2a. Full Backup: All used data Centralized
blocks from snapshots are backed Backup Server
up or
(physical or
2b. Differential/Incremental backup: virtual machine)
/a VM2 Only changed changed blocks
reported by VMware are being
backed up (Changed Block
Tracking)
vSphere/ESX Server
SAN
3. Client backups
additional control VM
control information
VMFS (vStorage API for Data
Protection)
Snaps
vmdk vmdk vmdk VM1
4. Client removes
snapshot
Backup Server
SAN Storage Subsystem
4

5. TSM
File-­‐level
Backup
ESX/ESXi Server Backup Server
VM1
C D
vStorage APIs
Service
Console C:mntvm1lettersc
C:mntvm1lettersd TSM Client
C VM2
SAN/LAN/Local
VMFS
SAN/LAN/Local
vmdk vmdk vmdk C:...
D:...
Storage System TSM Server 5

6. TSM Full-VM-Level Backup
ESX/ESXi Server Backup Server
VM1
C D
VM1
Service vStorage APIs
Console
C VM2
TSM Client
SAN/LAN
VMFS
SAN/LAN
vmdk vmdk vmdk C:...
D:...
Storage System 6
TSM Server

7. Recovery Agent: File Recovery
Partition Mount
1. User launches Windows or Linux Data Protection for
VMware Restore Agent to mount partition
a. Enters TSM node name for authentication with
TSM server
b. Select VM, recovery point and disk
c. Select partition mount / partition
2. Volume is presented to local system (if off-host mount,
make volume available to VM guest)
3. User copies files (files restored from TSM storage pool)
TSM Agent Deployment
Server Linux and Windows
install
packages Hypervisor
1. In-guest for VM user
initiated restore Virtual Machines
2. Off-host centralized
file
restore (windows
package typically on
same machine as B/A
client)
7

8. TSM
for
VE
Plug-­‐In
in
vSphere
Client

9. IBM Tivoli FlashCopy Manager
Application FlashCopy Manager ü Online, near instant snapshot
System Local backups with minimal
Application Snapshot performance impact
Data Versions
Snapshot
ü High performance, near
Backup
instant restore capability
ü Integrated with IBM Storage
Hardware
ü Simplified deployment
For IBM Storage Storage Manager 6
Custom Apps With Optional ü Database Cloning
File Systems
ü SVC TSM Backup
ü V7000
ü XIV Integration
ü DS8000
ü DS 3/4/5*
*VSS Integration
9

10. FlashCopy Manager and VMware
§ Supports
ESX
/
vSphere
4.1
and
5.0
§ Off-­‐host
(proxy
based)
hardware
snapshot
backups
with
VMFS
datastore
granularity
– Scheduled
or
ad-­‐hoc
execuNon
– No
need
to
deploy
OS
specific
agents
to
each
VM
§ OpNonal
offloaded
backup
to
TSM
with
VM
granularity
– SupporNng
block
level
incremental
backups
with
VMware
Changed
Block
Tracking
§ Restore
of
individual
VMs
from
• a)
from
a
Hardware
snapshot
of
a
VMFS
datastore
• b)
from
oflloaded
TSM
backup
§ Restore
of
individual
files
– Mount
of
a
backup
to
a
guest
VM
for
individual
drive
/
files
access
§ Restore
of
individual
virtual
disk
(vmdk
files)
– Volume
Restore
using
Recovery
Agent
§ User
interface
– vCenter
client
integraNon
(plug-­‐in
web
GUI)
and
CLI
(on
proxy
node)
§ ReporNng
and
Monitoring
– summary
view
with
drill
down
for
details
– backup
&
restore
stats
– Managed
capacity
report
§ Policy
based
management
of
local
snapshot
backups
10

11. Full-VM Backup with FlashCopy Manager
leveraging vStorage API
1. FCM initiates a software
snapshot of virtual guest
VM1 volumes (vSphere API)
C: D: Linux Proxy
Server
(physical or
virtual
/a VM2 machine)
FlashCopy Manager
SAN ESXESXi Server
VMFS
Snaps
vmdk vmdk vmdk VM1
TSM Server
SAN Storage Subsystem
11

12. Full-VM Backup with FlashCopy Manager
leveraging vStorage API
1. FCM initiates a software
snapshot of virtual guest
VM1 volumes (vSphere API)
C: D: Linux Proxy
2. FCMdetermines which LUN(s)
are associated with virtual Server
machines (physical or
virtual
/a VM2 machine)
FlashCopy Manager
SAN ESXESXi Server
VMFS
LUN 2 LUN 1
Snaps
vmdk vmdk vmdk VM1
TSM Server
SAN Storage Subsystem
12

13. Full-VM Backup with FlashCopy Manager
leveraging vStorage API
1. FCM initiates a software
snapshot of virtual guest
VM1 volumes (vSphere API)
C: D: Linux Proxy
2. FCMdetermines which LUN(s)
are associated with virtual Server
machines (physical or
3. FCM invokes hardware copy
virtual
/a VM2 machine)
services to create a persistent
snapshot copy of the LUN(s)
hosting the .vmdk and software FlashCopy Manager
SAN snapshot
ESXESXi Server
VMFS
LUN 2 LUN 1
Snaps
vmdk vmdk vmdk VM1
LUN 2’ LUN 1’
Snaps
vmdk vmdk vmdk VM1
TSM Server
SAN Storage Subsystem
13

14. Full-VM Backup with FlashCopy Manager
leveraging vStorage API
1. FCM initiates a software
snapshot of virtual guest
VM1 volumes (vSphere API)
C: D: Linux Proxy
2. FCMdetermines which LUN(s)
are associated with virtual Server
machines (physical or
3. FCM invokes hardware copy
virtual
/a VM2 machine)
services to create a persistent
snapshot copy of the LUN(s)
hosting the .vmdk and software FlashCopy Manager
SAN snapshot
ESXESXi Server
VMFS
LUN 2 LUN 1 4. Hardware snapshot
is persisted for use as
Snaps
vmdk vmdk vmdk VM1 source for recovery
operation, software
snapshots are deleted.
LUN 2’ LUN 1’
Snaps
vmdk vmdk vmdk VM1
TSM Server
SAN Storage Subsystem
14

15. Full-VM Backup with FlashCopy Manager
leveraging vStorage API
1. FCM initiates a software
snapshot of virtual guest
VM1 volumes (vSphere API)
C: D: Linux Proxy
2. FCMdetermines which LUN(s)
are associated with virtual Server
machines (physical or
3. FCM invokes hardware copy
virtual
/a VM2 machine)
services to create a persistent
snapshot copy of the LUN(s)
hosting the .vmdk and software FlashCopy Manager
SAN snapshot (+ TSM for VE)
ESXESXi Server
VMFS
LUN 2 LUN 1 4. Hardware snapshot
is persisted for use as
vmdk vmdk vmdk source for recovery
operation, software
snapshots are deleted.
LUN 2’ LUN 1’ 5. FCM optionally
creates additional copy
of data on TSM server
Snaps
vmdk vmdk vmdk VM1 (Objects saved in
TSM Server common data format to
enable individual file
SAN Storage Subsystem recovery using
Recovery Agent Mount)
15