SHARE Orlando February 25, 2008

Session Number: 9802Pat Fitzsimmons

© 2008 Innovation Data Processing

Th FDR/UPSTREAM S itThe FDR/UPSTREAM Suite A single INNOVATION solution that leveragesA single INNOVATION solution that leverages the unique strengths of IBM zSeries, pSeries AIX, SUN SPARC and Intel x-86 servers to

id t i t th t ti fprovide enterprise strength protection for databases and data on distributed storage.The FDR/UPSTREAM suite is a comprehensiveThe FDR/UPSTREAM suite is a comprehensive business resiliency solution that provides data protection and business continuance for servers and databases everywhere in the enterprise.

FDR/UPSTREAMz/OS Mainframe Backup Server Enterprise Solution

A z/OS server-based solution, for enterprise-wide, file level, backup/restore, archival, storage management and disaster recovery of distributedmanagement and disaster recovery of distributed data.Dual component system offering high performance, reliability and automation.Employs existing z/OS tape management, scheduling and security systemsscheduling, and security systems

TSO ISPF & JAVA GUI user interfaces

UPSTREAM LINUX f SERIESUPSTREAM LINUX for zSERIES

SuSE and Red Hat Linux on zSeries inSuSE and Red Hat Linux on zSeries in z/VM or LPAR

Extensive data base and file systemExtensive data base and file system supportAdmin, User and z/OS Batch interfacesAdmin, User and z/OS Batch interfacesDe-duplication/data transfer reductionOperationsOperationsClient SupportRescuer Bare-metal recoveryRescuer Bare-metal recovery

UPSTREAM LINUX f SERIESUPSTREAM LINUX for zSERIESOn-Line Database Agents forOn Line Database Agents for Oracle, DB2, and DominoExtensive file system features

Hard links, symbolic links, owners, Reiser, ext2, ext3, GFS, XFS, NFS, MAPFS, GPFS i l fil t t tGPFS, single file system support, etcSupport for user specified file systems

Full featured daemonFull-featured daemonUPSTREAM Rescuer

U I t fUser InterfacesJAVA GUI TSO/ISPF

Administration Command/UserAdministration Command/User Control

JAVA GUIJAVA GUIStorage Manager DirectorEnd-User Restore Interface

TSO/ISPF Interactive ControlReal Time Monitor

Command Line/Character modez/OS Batch

UPSTREAM D t M tUPSTREAM Data ManagementIndividual client or global policy managedg p y gBackup data managed by existing external tape management systemR t ti i d ll d ith GDGRetention periods usually managed with GDGs with benefit that system maintains itself Can also use expiration datesCan also use expiration datesMigrate Disk Backups to TapeRepro Tape for Off-Site VaultingBi-Directional File Transfer

/OS BATCH I f USTBATCHz/OS BATCH Interface – USTBATCH

Initiate Backups, Restores, File Transfers, Run Functions, and UPSTREAM

dcommandsCan wait for process completionCan initiate multiple, concurrent operationsUsed as the interface to host based JOB scheduling systems (CA-7, OPCA, etc.)

S h d li O tiScheduling Operations z/OS with your EXISTING Job Scheduler ysuch as CA7, Zeke, OPCAorUPSTREAM z/OS Integrated SchedulerUPSTREAM z/OS Integrated Scheduler

Client InitiatedUPSTREAM Dispatcher Client SchedulerorYour EXISTING Client Scheduler

De-duplication TechnologyDe duplication Technology Minimizes Data Transmission

Advanced Data Reduction Technology gyOperations employ De-Dupe technology to reduce backup time

D t C iData CompressionLogical Volume Full Merge BackupLogical File GranularityLogical File GranularityIncremental Backup ProcessingDuplicate File RecognitionSegmented backup supportExclude/IncludeAuto Migrate inactive dataAuto Migrate inactive data

O tiOperations

Backup/Restore/InquiryBackup/Restore/InquiryStatus DisplayFile TransfersFile TransfersRun Process

Backup Types and MethodsBackup Types and Methods

Backups are keyed by Profile Name andBackups are keyed by Profile Name and VersiondateEvery backup consists of File Sets

Sequential DASD and TapeFirst Time FullNon Merge (looks like an incremental)Non-Merge (looks like an incremental)Merge

IncrementalF llFull

DeferredNon-Deferred

Backup Types and MethodsBackup Types and MethodsContinued…

CombinationsCombinationsAll tape – Incremental and full backups to tapetape Fulls on tape, incrementals on DASDDeferred backups to DASD merged toDeferred backups to DASD, merged to tape.

DASD Migration IssuesDASD Migration Issues Available spaceTape unit availabilityTape unit availability

F ll M B kFull Merge BackupUPSTREAM Storage Server or Reservoir

Client

Tape Disk

Full Merged Backup

Tape Disk

Full Backup Incremental Backup (1)

Incremental Backup (2)Backup (1) Backup (2)

Merge Backups The way to go for best performance and tapeThe way to go for best performance and tape utilization

A form of de-duplication: Takes incrementals and the prior full to provide a picture of the current disk state nowCreates real fulls without sending up all of the files.

I b k fImprove backup performanceBy not reading and transmitting all files for fulls or incrementals

Reduce tape utilizationReduce tape utilizationBy piggybacking multiple backups onto a tapePointing to files on incrementals in the full

All “hi hli ht d b k t f ll” d “hi hli ht dAllows “highlighted back to full” and “highlighted back to oldest” inquires and restores.

Where incrementals and fulls are combined into a full up to date view of the systemfull, up to date view of the system

R l #1 f M B kRule #1 for Merge Backups

Always use the same backup profile forAlways use the same backup profile for the same data (typically a file server or database))

Don’t mix profiles with different dataThe merge requires that the same profileThe merge requires that the same profile always relate to the same files.

For example: Profile PAT is my machineFor example: Profile PAT is my machine. Never mix my databases or BOB’s files with my profile.y p

T f M B kTypes of Merge Backups

First-time fullFirst time fullA traditional full backup – read and write every fileevery fileUse for the first backup of a server/instance

Restartable throughout the backup processSlightly faster than a full merge with no prior backup

If to tape, uses only one drive.

T f M B kTypes of Merge BackupsIncremental MergeIncremental Merge

Simply an incremental (changed file) backup.Managed by the storage server in the same way as a non-merge backup.F ll R t t bl ( t f d h ki )Fully Restartable (except for dup checking)If duplicate checking is enabled for the backup the server will lookup older files inbackup, the server will lookup older files in the repository.If to tape, uses only one drive.p , y

T f M B kTypes of Merge BackupsFull Mergeg

Only transmits the same files as an incremental plus a “picture of the disk”.Server matches files backed up in prior backupsServer matches files backed up in prior backups by date, time and size.The client sends mismatched files.Result: A tape or disk file with all of the files as a first-time full without all of the data movement from client to server.De-duplicated: a file is only read and transmitted when it has changed. It may appear on multiple backups but only read by the file server once forbackups, but only read by the file server once for each change.

M B kMerge BackupsDo first-time fulls the first time. You can do a full merge for simplicity (you don’t have to setup a special backup).Do periodic full merges (weekly bi weeklyDo periodic full merges (weekly, bi-weekly, monthly) and daily incrementals.

Fulls (first time or full merge) are required to properly free tapes and reflect deleted files.Do first-time fulls rather than full merges if:

They’re faster (determine by testing).They re faster (determine by testing).You need restartability throughout the process.

F ll M B kFull Merge Backups

3 phases3 phasesPhase 1:

The client sends any changed files plus aThe client sends any changed files plus a “picture of the disk”This is the only phase of a full merge backup which is restartableIf to tape requires one drive during this phase

F ll M B kFull Merge BackupsPhase 2:Phase 2:

The server notes files which already exist on this backup tape (if to tape)The server notes (and optionally copies) files in theThe server notes (and optionally copies) files in the duplicate repositoryThe server copies files from prior backups Th li t di l t t f th tiThe client displays status of the copy operationThe server sends the list of mismatched files to the clientIf to tape requires two drives during this phaseIf an old backup was on tape a drive is required even if the backup is to disk.

F ll M B kFull Merge BackupsPhase 3:Phase 3:

The client sends mismatched filesIf to tape requires one drive during this phasep q g pBecause of the 3 phases, you can do a full merge even if you have never done a first-time fullfull.

M B k t Di kMerge Backups to Disk

Fulls and incrs on disk:Fulls and incrs on disk:

M B k t Di kMerge Backups to DiskEach backup (full or incremental) is a single new disk p ( ) gfile on the serverz/OS:

Can be either a sequential file or a GDGCan be either a sequential file or a GDG.Cleanup of expired backups is by catalog control or GDG management.

Reservoir:Reservoir:Cleanup of expired backups is by Reservoir profile policy.

Number of backups, number of fulls, expiration date, number of tape sets (backups)number of tape sets (backups)

If there is not enough space in the primary directory you can setup the profile definition to point to an alternate directory (spare tank)( p )

M B k t TMerge Backups to Tape

Fulls and incrs on tape:Fulls and incrs on tape:

M B k t TMerge Backups to Tape

Fulls on tape incrs on disk:Fulls on tape, incrs on disk:

M B k t TMerge Backups to TapeEach backup can start a new tape OREach backup can start a new tape ORThe first incremental after a full starts a new tape and incrementals up to and including the full are appended to the tape.

Saves tapesM lti l b k tMultiple backups on a tapeFiles on the incremental which are on the full are not recopied(Reservoir) Profile sets allow multiple profiles on a single tape

The Original De-duplicationThe Original De duplication technology Duplicate File Support

Full, Incremental & Merge Backup

SystemASysteFile 1

SystemBFile 1File 1

SystemCFile 1

File 1

SystemDFile 1

li il SDuplicate File Support

UPSTREAM/MVS only/ yIn development for Reservoir

Database on host (USTFILED) which contains fil hi h b d li tfiles which may be duplicate

Special backup profile (USTDUPFL)

Client path name is not usedClient path name is not used File name

Modification date

Size

Preliminary host setup required

li il SDuplicate File Support

Manually populateManually populate

A non-merge, duplicates backup using USTDUPFL

Automatically populate

Setup on host

High overhead

USTFILEI entry for every file name

Duplicates are detected on 2nd backup usedDuplicates are detected on 2nd backup, used on 3rd

li il SDuplicate File Support

“Duplicate checking” in ISPF backupDuplicate checking in ISPF backup More... dialog or Director Options dialogdialog

Required for UPSTREAM duplicate supportpp

Enable this option for client use per backup

Uses modification date (days old) to determine if a file’s duplicate

Merge Incrementals and fulls

li il SDuplicate File Support

Duplicate Management to manageDuplicate Management to manage duplicate database

“Management” menuManagement menu

Inquire (with wildcards) the contents of the duplicate repositorythe duplicate repository

Inquiry does not use directory specificationspec cat o

Select one, several or all files to delete

Segmented File SupportSegmented File SupportA form of block level de-duplication

Based on the assumption that large files are usually updated in place or data is added at the end of the file, a new technology can aid in backup. As only relatively small portion(s) of the file change between b k t it l th h dbackups, we can transmit only those changed segment…thereby introducing “file segmentation”

Segmented file support, a form of block level de-d li ti h l d d i tduplication, helps reduce and manage growing amount of data to be backed up and stored

Normal Setup per backup jobDefine the minimum file size to invoke segmented file checking

default is 1GB

D fi th t i f UPSTREAM t b k filDefine the segments size for UPSTREAM to break file into pieces

default is 1MB

S d il SSegmented File Support

During backup UPSTREAM will cut the file into pieces of the specified size (segment size), and back them up as separate files.

The “Signature” of every backed up segment is kept in a “Digest” on the client system.

During subsequent incremental backups the signature for every read segment is compared with the stored ones, and UPSTREAM backs up only segments with a changed signature .

During full merge backups unchanged segments from prior fulls are combined with the incremental segments, and the most current full set of segments gets copied to create the new full backup.

The result can be a dramatic Reduction in the amount of data sent and stored.

S d kSegmented Backup

Indication of blockIndication of block change on each client machine

LocalDigest

LocalDigest C

CC

LocalDigest

LocalDigest

C

S A lUPSTREAM Recovery Tools

UPSTREAM RescuerUPSTREAM RescuerFast reliable data files and system databases restore

Linux for zSeries – SUN - X86 Linux

NDS

Active Directory

System State

Wi d XP A d SWindows XP Automated System Recovery

Off Sit V ltiAdditional Copies

for

Off-Site VaultingPowerful utility for offsite tapes for

Off-site Vaulting

y pCreates secondary tape copy for DR to be stored in an offsite vaultoffsite vaultFor on-site recovery if primary backups are damaged p y p gor unusable Can also be used for backups requiring long term retentionrequiring long-term retention

Th UPSTREAM E t i S itFDR/UPSTREAM

The UPSTREAM Enterprise Suite FDR/UPSTREAMUPSTREAM/SOSFDR/UPSTREAM z/OS UNIXFDR/UPSTREAM z/OS UNIXFDR/UPSTREAM LINUX for zSERIESUPSTREAM RESERVOIRUPSTREAM RESERVOIR

Ch i f St SChoice of Storage ServersReservoirReservoir

WindowsAIXLinux (x86, Linux for pSeries & Linux for zSeriesSolaris (Intel and SPARC)

FDR/UPSTREAM z/OS mainframe S li t th R iSame client as the ReservoirTape compatible with the Reservoir

FDR/UPSTREAM Cli tFDR/UPSTREAM ClientsWindows 2000/2003 HP-UXWindows XPWindows Vista

OS/2Tru64 UNIXX86 LiNovell NetWare

Novell OES LinuxIBM AIX

X86 LinuxLinux for pSeriesLinux for zSeriesIBM AIX

Sun SolarisSun X86

Linux for zSeries z/OS UNIXAny storage system that

b NFS t dSun X86 VMware

can be NFS mounted can be backed up/restored

Business Continuance and DataBusiness Continuance and Data Protection Software

FDR/UPSTREAMFDR/UPSTREAMandUPSTREAM Reservoir Enterprise Data Protection & Business continuance for Enterprise Storage