TSM og virtualisering

Tivoli Storage Manager 6.4 IBM og Peanuts ønsker velkommen til seminar

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

• 

Tivoli Storage Manager Storage Pool

TSM B/A client Running on Backup Server*

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 File-level backups Full VM backups

* Backup Server can be a physical or virtual machine

• vStorage APIs provides the capability to read directly from the ESX storage

vStorage API

3

VM1

/a

D: C:

VM2

VMFS

vSphere/ESX Server

SAN Storage Subsystem

vmdk vmdk vmdk

SAN

Backup Server

1. Snapshot of virtual guest volumes (vSphere API) is initiated

Snaps VM1

2a. Full Backup: All used data blocks from snapshots are backed up or 2b. Differential/Incremental backup: Only changed changed blocks reported by VMware are being backed up (Changed Block Tracking)

3. Client backups additional control VM control information (vStorage API for Data Protection)

4. Client removes snapshot

Centralized Backup Server (physical or virtual machine)

CBT (Changed Block Tracking)

4

VM1

C

D C

VM2

Service Console

VMFS

TSM Server

TSM Client

vStorage APIs

Backup Server ESX/ESXi Server

vmdk vmdk vmdk C:\... D:\...

C:\mnt\vm1\letters\c C:\mnt\vm1\letters\d

SAN/LAN/Local

SAN/LAN/Local

Storage System

TSM File-‐level Backup

5

TSM Full-VM-Level Backup

VM1

C

D C

VM2

Service Console

VMFS

TSM Server

TSM Client

vStorage APIs

Backup Server ESX/ESXi Server

Storage System

vmdk vmdk vmdk C:\... D:\...

SAN/LAN

SAN/LAN

VM1

6

Recovery Agent: File Recovery

7

Partition Mount

Hypervisor

Virtual Machines

TSM Server

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)

Agent Deployment Linux and Windows

install packages 1. In-guest for VM user

initiated restore 2. Off-host centralized

file restore (windows package typically on same machine as B/A client)

TSM for VE Plug-‐In in vSphere Client

9

IBM Tivoli FlashCopy Manager

Application System

Application Data

Local Snapshot Versions

Snapshot Backup

FlashCopy Manager

Storage Manager 6

With Optional TSM Backup Integration

ü SVC ü V7000 ü XIV ü DS8000 ü DS 3/4/5*

For IBM Storage

ü  Online, near instant snapshot backups with minimal performance impact

ü  High performance, near instant restore capability

ü  Integrated with IBM Storage Hardware

ü  Simplified deployment

ü  Database Cloning

*VSS Integration

Custom Apps File Systems

10

§  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

FlashCopy Manager and VMware

Full-VM Backup with FlashCopy Manager leveraging vStorage API

11

VM1

/a

D: C:

VM2

VMFS ESX\ESXi Server


vmdk vmdk vmdk

SAN

TSM Server

1. FCM initiates a software snapshot of virtual guest volumes (vSphere API)

Snaps VM1

Linux Proxy Server (physical or virtual machine)

FlashCopy Manager

12

VM1

/a

D: C:

VM2



vmdk vmdk vmdk

SAN

TSM Server


Snaps VM1

LUN 1


FlashCopy Manager

LUN 2

2. FCMdetermines which LUN(s) are associated with virtual machines


13

VM1

/a

D: C:

VM2



vmdk vmdk vmdk

SAN

TSM Server


Snaps VM1

LUN 1


FlashCopy Manager

LUN 2

2. FCMdetermines which LUN(s) are associated with virtual machines 3. FCM invokes hardware copy

services to create a persistent snapshot copy of the LUN(s) hosting the .vmdk and software snapshot

vmdk vmdk Snaps VM1

LUN 1’ LUN 2’

vmdk


14

VM1

/a

D: C:

VM2



vmdk vmdk vmdk

SAN

TSM Server


Snaps VM1

LUN 1


FlashCopy Manager

LUN 2



vmdk vmdk Snaps VM1

LUN 1’ LUN 2’

vmdk

4. Hardware snapshot is persisted for use as source for recovery operation, software snapshots are deleted.


15

VM1

/a

D: C:

VM2



vmdk vmdk vmdk

SAN

TSM Server


LUN 1


FlashCopy Manager (+ TSM for VE)

LUN 2



vmdk vmdk Snaps VM1

LUN 1’ LUN 2’

vmdk

4. Hardware snapshot is persisted for use as source for recovery operation, software snapshots are deleted.

5. FCM optionally creates additional copy of data on TSM server (Objects saved in common data format to enable individual file recovery using Recovery Agent Mount)


TSM og virtualisering

Technology

Transcript of TSM og virtualisering