Vizioncore vRanger 4.5 Technical Overview

vRanger

Technical Deck Library

5/24/2010

2

IMAGE-LEVEL BACKUPS AND THE VIRTUAL ENVIRONMENT

Why is it important?

5/24/2010

3

What is an Image?

A VMware Snapshot is a recording of all the changes that occurred since the VM was created

Snapshots can be created on running VMs• Changes/deltas tracked separately & merged later

vRanger creates an Image based on snapshot technology• combination of the snapshot & tracked changes• Exact representation of the VM at time of backup

5/24/2010

4

What is a VM Image?

A VM image contains:• Hypervisor Configuration• OS, App• Data

A VM image can be reconstituted on any system running the correct hypervisor base.

Reconstitution enables point-in-time DR.

5/24/2010

5

What is Image-Based BR?

Image-Based Backup & Recovery (BR):• Creates images using HV snapshot technology• Backs up and recovers images • Enables reconstitution of images into servers

5/24/2010

6

What is Image-Based BR: Backup

Creating a snapshot is fast, but:• Images can be large• Diffs, compression and dedup are must haves

File-based backups of VMs work, but:• Backups may be slower (copy instead of snapshot)• Reconstitution is not automatic• Limited scalability (may require proxies)• Limited compression of large VM files

5/24/2010

7

Are Image-Based Backups Safe?

YES!!! Applications and Data are secure through entire process.

The snapshot process:• Does not disrupt a running VM• Keeps apps in the image consistent• Can be integrated with VSS for added integrity

5/24/2010

8

What is Image-Based BR: Recovery

Three things are recoverable from an image:• Image (reconstituted server)• File• Object (e.g.: email)

Files and objects can be recovered without image reconstitution.

Stored Image

Recovered Object

Recovered File

5/24/2010

9

What is Image-Based BR: Recovery

Image portability enables multiple “where” recovery options:• Restore on-premise• Restore to cloud• Restore to dissimilar hardware

Non-virtualized systems can be converted to images using P2V tools:• Backup physical systems using image BR• Recover a physical box into a VM

5/24/2010

10

Image-Based BR Scenarios

Lab Automation: Maintaining test images

Replication: Maintaining synchronized failover environments

Data Security: Protect data and meet compliance requirements

Disaster Recovery: Recreate production environments

5/24/2010

11

HOW IT WORKS

vRanger Pro 4

5/24/2010

12

How vRanger Works

Source Target

Installs and discovers the environment in minutes.

1

vRanger

5/24/2010

13

Direct To Target

How vRanger Works

Source Target

Backup

Jobs


SOURCES transmit images to TARGETS without proxying.

We call this Direct To Target.

1 2

vRanger

5/24/2010

14

Direct To Target

How vRanger Works

Source Target

Backup

Restore

Jobs Restore


SOURCES transmit images to TARGETS without proxying.

We call this Direct To Target.

SOURCES and vRanger restore directly from

TARGETS.

1 2 3

vRanger

5/24/2010

15

Direct To Target

How vRanger Works

Source Target

Backup

Restore

Jobs Restore

vRanger

Direct to Target Benefits:- Shorter Windows: no proxy; no bottleneck- Shorter Windows: Parallel backups within and across sources- Fewer Resources: Data is dedup’d before going on the wire- Flexible: Intelligent mgmt of jobs on sources

5/24/2010

16

How vRanger Works: Backup (1..3)

vRanger uses a patented binary injection process to implement Direct-To-Target.

The latest vRanger libraries are injected into source’s runtime.The runtime manages connections to targets.

1 vRanger

Inject

Source

Binary Runtime

Other Processes

vRanger issues snapshot requests to vCenter or ESX host.

2

Target

Repository

Comm

vRanger VCenter

ESX Host

Req

Req

or

Source SAN / NAS

Snap

5/24/2010

17


The vRanger source binary grabs the snapshot from storage.

3Source

Binary Runtime

Other ProcessesTarget

Repository

Send

SAN / NAS Storage

Snapshot Files.VMDK.VHD

Grab SnapshotsDedup, Compress

EncryptReconstitute Image

Grab

We perform intelligent middleman logic including dedup, compression, encryption, and target connection mgmt.

4

5/24/2010

18

Shorten Backup Window: Parallel Backups

vRanger provides:• Simultaneous backups on each host• Simultaneous backups across hosts

Source 1Binary Runtime

Target

RepositorySendConnection MgmtThreaded Access

Source 2Binary Runtime

Connection MgmtThreaded Access

Send

Send

Send5/24/2010

19


vRanger supports two types of modes:

Source Type

Used For Deployed In

Hypervisor Console “Network”

Performing BR directly from a hypervisor host.

We use binary injection to install an agent in ESX console.

HV Console Runtime

LAN-Free Performing LAN-Free BR over FC using vStorage APIs.

We dynamically install an agent on source system.

Windows Physical Host

5/24/2010

20

CBT AND ABMvRanger Pro 4

5/24/2010

How CBT and ABM work together

A typical disk layout

Active Block

White Space

Deleted Data

Changed Block

Without ABM or CBT

1• without ABM or CBT enabled • engine removes only the whitespace • applies to both 3.5 and 4.0 hosts

Active Block

White Space

Deleted Data

Changed Block

With ABM

2• Initial pass – with ABM enabled • Active Block Mapping (ABM) selects only active blocks. • Blocks occupied by deleted data not backed-up.

Active Block

White Space

Deleted Data

Changed Block

At the next backup…

3 Typical disk layout for subsequent backup pass

Active Block

White Space

Deleted Data

Changed Block

CBT and Incremental/Differentials

4• Only changed blocks are backed up• Without ABM both active and deleted changed blocks are

backed up

Active Block

White Space

Deleted Data

Changed Block

ABM on Incremental/Differentials

5• Backup pass with ABM enabled, no CBT• With ABM, only Active changed blocks are backed-up

Active Block

White Space

Deleted Data

Changed Block

Both on Incremental/Differentials

6• Backup pass with ABM and CBT enabled

• (Only supported on ESX 4 hosts)• Blocks backed-up does not change, but

• scan times are much lower, • resulting in much faster backups

Active Block

White Space

Deleted Data

Changed Block

Change Block Tracking (CBT)

a vStorage API feature• Eliminates change-scanning during inc/diff’s

Reduces data to be backed-up

Shortens backup window

Why CBT?

Large disks• Removes scan time needed to ID changes

Network based VMFS• Scanning for change slower on network based VMFS: CBT

helps dramatically• Example: A 94 minute backup of 2.8 GB could be dramatically

reduced to only 3 minutes

CBT Support in vSphere

Most VMs supported on ESX4• vSphere API has flag indicating VM support• VMs must:

- Be Hardware Version 7- Be able to add Snapshots to the VMDK’s

• No independent disks or RDM LUNs

- Have a stun or unstun cycle to enable or disable

No support on ESX3

Activating CBT

CBT must be turned on, in vSphere• Disabled by default

Is enabled per VM, on an individual basis

• When activated, icon is shown on “My Inventory”

PowerShell script exists to Bulk-enable CBT

http://vcommunity.vizioncore.com/administration/vecoshell/b/weblog/archive/2010/04/19/bulk-enabling-cbt-for-vms.aspx

http://vcommunity.vizioncore.com/administration/vecoshell/b/weblog/archive/2010/04/19/bulk-enabling-cbt-for-vms.aspx

Active Block Mapping (ABM)

What is it?• A tool that reads the Windows NTFS file system in a VMDK

and identifies - blocks that are actually used by the OS vs. - blocks have been deleted to recycle bin

Benefit• Faster incremental/differential backups:

- Only blocks that are actually used are read.

ABM: Details

• Activated in a backup job as an option.

• New jobs: on by default- (remains off on jobs

migrated from earlier versions)

• While CBT is VM-specific, ABM is Job-specific

• Can be used in conjunction with CBT

ABM, CBT and Backup Mode

If ABM and CBT are both enabled• ABM is always used on fulls• incremental or differential use both the AB and CB filter.

If only ABM is enabled• ABM works regardless of backup type

ABM – Restore Behavior

Note that undeleted programs will not work on a restored VM that was backed up with ABM.

Deleted files from recycle bin are not available after a VM is restored from a save-point.

ABM: Support

Windows XP - Windows 2008 R2• Windows NTFS only• Basic disks only

Supported only on ESX and LAN backups• ABM not currently supported for vStorage API (vRanger: LAN-

free and ESXi backups)

Note: master file table needs to be ‘clean’• ‘file table not supported’ error: run chckdsk

37

LAN-FREE AND ESXI BACKUPS

vRanger Pro 4

5/24/2010

38

How It Works: Network Backups

5/24/2010

39

ESX Network backups

To Backup Repository

ESX Host

Nic 0

Storage Connections (Ethernet or FC)

vCenter vRanger Pro

Service Console

Mmgt Connection

vStorage API uses this

connection for Network transport backups

Direct t

o targ

et

Compressed

5/24/2010

40

How It Works:LAN-Free & ESXi Network Backups

5/24/2010

41

vStorage API for data protection ESXi Network backups

ESXi Host

Nic 0

Storage Connections

(Ethernet or FC)

vCenter vRanger Pro

Uncompressed

Mmgt Connection

vStorage API uses this

connection for Network transport backups

Compressed To Backup Repository

5/24/2010

42

Requirements for LAN free backups

vRanger Pro installed on a physical proxy server

One proxy per set of VMFS luns

VMFS luns zoned so vRanger Pro can see and read them

VCB application is no longer used

Works with ESX 3.0.2 - ESX 4 (vSphere)

ESX 4 hosts require minimum “Essentials” license to use the vStorage API.

5/24/2010

43

vRanger Pro LAN free jobs

5/24/2010

Compatible with 3.0.2 – 4.x ESX hosts

Compatible with 3.5 – 4.x ESXi hosts

44

How vRanger Pro proxy should see disks

5/24/2010

45

Job Option for LAN free backups

5/24/2010

46

vRanger Pro Architecture for LAN free backups

SAN Storage

Lun 0 Lun 1 Lun 2

Fibre Channel Switch

ESXHost

ESXHost

5/24/2010

47


SAN Storage

Lun 0 Lun 1 Lun 2

Fibre Channel Switch

vRangerServer

ESXHost

ESXHost

5/24/2010

48


vRangerServer

ESXHost

ESXHost

The storage is presented to both the ESX hosts and the vRanger Pro server.

iSCSI Switch(s)

SAN Storage

Lun 0 Lun 1 Lun 2

5/24/2010

49


ESXHost

ESXHost

The storage is presented to both the ESX hosts and the vRanger server.

FC / iSCSI Switch(s)

SAN Storage

Lun 0 Lun 1 Lun 2

vRanger Server

Read Only Access

5/24/2010

50

vRanger Pro Architecture for LAN free backups using a FC SAN

Nic0

HBA2

HBA1

vRanger Pro (Proxy)

Prod Network – to vCenter

Shared Storage (VMs)


SAN Storage

Lun 0 Lun 1 Lun 2

SAN Storage

Lun 10 Lun 11 Lun 12

5/24/2010

51

vRanger Pro Architecture for LAN free backups using an iSCSI SAN

Nic0

Nic1

Nic2

vRanger Pro (Proxy)




SAN Storage

Lun 0 Lun 1 Lun 2

SAN Storage


5/24/2010

52

vRanger Pro Architecture for LAN free backups using an iSCSI SAN (2)

To Backup Repository Device B

vRanger Pro (Proxy)

Nic0

Nic1

Nic2

Nic3

Nic4

Nic5


To Backup Repository Device A


5/24/2010

53

Data Flows with LAN free backups

Nic 0

vRanger Pro (Proxy)




SAN Storage

Lun 0 Lun 1 Lun 2

SAN Storage


Reads

Reads

Rea

ds

5/24/2010

54

Data Flows with LAN free Backups

Nic 0

vRanger Pro (Proxy)



SAN Storage

Lun 0 Lun 1 Lun 2


SAN Storage


Reads

Reads

Rea

ds

5/24/2010

55

Data Flows with LAN FREE Backups

Nic0

vRanger Pro (Proxy)


Backup Repository


SAN Storage

Lun 0 Lun 1 Lun 2

SAN Storage


Reads

Reads

Rea

ds

Writes

Writes

Writes

Read Connection

Write Connection

5/24/2010

Custom Backup Groups

Goal: more flexibility for backup jobs

Groups disparate VMs, hosts, folders• Separate structure from Virtual Center

Accessible in “My Inventory” view

Thin Disk Support: Details

vSphere-only feature• ESX4 to ESX3 restoration isn’t supported

GUI indicates if a disk is ‘Flat’ or ‘Thin’.

Support for backup and restore

Only blocks w/ data are restored

Encrypted Repositories

What it is• All save point in the repository is encrypted.• Password is specified as part of the repository configuration. All

save point in the repository will have the same password.

Benefit• Save point cannot be restored by unauthorized entities (i.e. those

without the password)

AES 256 Encryption• No “backdoors”

61

SUPPORTED ENVIRONMENTS

The Fine Print

5/24/2010

62

vRanger Supported Environments

Platforms VMware ESX 3.x & 4.x (vSphere)ESXi

vCenter 2.0.1 – 4.0

OS Requirements for Install

• Microsoft Windows XP SP2 (x86 or x64)• Microsoft Windows XP SP3 (x86)• Microsoft Windows 2003 Server SP2 (x86 or x64)• Microsoft Vista Business or Ultimate (x86 or x64)• Windows Server 2008 SP2 (x86 or x64) (Network backups only)• Windows 7 (Network backups only)

Installable in a VM? Yes (Network and ESXi backups only)

vRanger Database MS SQL Server 2005, 2008 or Express

Languages English, Spanish, French, Italian, German, Chinese, Japanese

Protocols CIFS, FTP

Encryption SSH, 256-bit AES, SHA-5125/24/2010

63

SCREENSHOTSvRanger Pro 4

5/24/2010

64

Backup Process

5/24/2010

65

Job Status Monitor

5/24/2010

66

Restore Process

5/24/2010

67

Instant File Level Restore

5/24/2010

68

Configuration Options

5/24/2010

Technology

Vizioncore vRanger 4.5 Technical Overview