Business Continuity Implementation

Front 1

Local Business Continuity Framework

Back 1

Platform
Backup/Recovery
Information Repurpose

Front 2

Remote Information Business Continuity Framework (more complex)

Back 2

Remote Information
Remote Processing
Multi-site

Front 3

Platform

Back 3

The implementation of robust hardware and software technology, high levels of performance and availability, no single point of failure.

o Flexible
o Scalable
o Manageable
o Reconfigurable
o Multiple oConnectivity Options

Front 4

Backup/Recovery

Back 4

Ensuring the ability to backup and recover info w/ minimal impact

o Non-disruptive backups
o Instant Restore
o Consistent across applications
o Mask Complexity

Front 5

Information Repurposing

Back 5

Ability to reuse production data w/o impacting performance

o Repeatable
o Affordable
o All aspects of enterprise

Front 6

Remote Information

Back 6

Ability to assure data availability at a remote location

o Zero data loss to seconds to hours
o A yard, a mile, a thousand miles
o Transport and restore
o Electronic data synchronization
 Differed or periodic
 Real time

Front 7

Remote Processing

Back 7

Ensure availability of appropriate servers and networking to assume application restart at remote location

o Build your own
o Provider

Front 8

Multi-site

Back 8

Ensure data availability with minimal performance impact at remote location

o Highest availability
o Flexibility
o Automated management
o No single point of failure

Front 9

Raw Device

Back 9

o Special device file identifies volume directly
o Any process that can open the device file can read and write any specific volume
o Virtual disk devices that looks like a disk device
o Can be mirror, spanned, striped, and moved
o Can only be opened as a single direct-access file
o Performing I/O directly can eliminate File System overhead

Front 10

File Systems

Back 10

o Provide syscalls to create/access files residing on disk
o OS file systems files virtualizes physical disk storage as a collection of logical files
o Hierarchical structure of files and directories
o Consists of five components
 Set of inode storage cells
• (files set aside when file system is made)
 Set of scattered super blocks
• contain info on the file system characteristics, several scattered copies are maintained
 Map of disk blocks in the file system
 Block usage summary
 Set of data block

Front 11

File Systems

Back 11

UFS, Journal Filing System (IBM), Enhanced Journaling Filing System JFS2 (IBM), VxFS (Veritas), Veritas Quick for i/o databases, Windows FAT32, FAT16, NTFS.

Front 12

UFS

Back 12

Conceptually viewed as inverted tree structure

Front 13

Journaling File System (IBM)

Back 13

o JFS uses database-like journaling technique
o Only complete updates are applied after a crash
o Updates are first built in a journal log
o Max system size: 1TB
o Max file size: 64GB

Front 14

Enhanced Journaling File System (JFS2, also IBM)

Back 14

o Designed to support large files and large files systems
o 64bit Functionality
o Max system size: 16TB
o Max file size: 16TB

Front 15

VxFS (Veritas)

Back 15

o Installable file system
o Uses intent logging to provide quick recovery after failure
o Extendable w/o unmounting
o Extent based allocation

Front 16

Veritas Quick I/O for Databases

Back 16

o Nearly equal to that of raw devices
o References real file using extended name

Front 17

Windows

Back 17

o FAT16/32
 Often uses to support duel boot environment
o NTFS
 FAT32 + MORE AWESOME
 Win2k and up
 File and directory level security
 Disk compression & quotas
 Encryption

Front 18

Hierarchical Database

Back 18

Data representation based on parent-child (tree structure)

Front 19

Network database model

Back 19

Representation where data entities are on a lattice structure

Front 20

Relational database model

Back 20

Represented as two dimensional tables that relate by common attributes

Front 21

Object-Oriented database model

Back 21

Representation of object attributes and behavior

Front 22

Hybrid data model

Back 22

Mix of relational and object-oriented

Front 23

Database Applications

Back 23

OLTP and DSS

Front 24

OLTP (Online Transaction Processing)

Back 24

o Used to manage and modify data
o Many small & random reads and writes

Front 25

• DSS (Decision Support System)

Back 25

o OLAP (Online Application Processing)
o Long reads during business hours
o Long writes during refresh
o Sequential reads and writes

Front 26

Database Backup Types

Back 26

Cold Backup (Offline)

Hot Backup (online)o Requires DBMS capability to perform backup while the db is running

Point-in-time Backup
o Requires EMC consistency technology (ECA, PPath)

Front 27

Statement of Work

(Implementation Collateral)

Back 27

o Legal document between EMC and customer
o Defines scope
 Derived from the design
 Outlines the work effort

Front 28

Configuration Guide

Back 28

o Solution design
o Steps to meet customer objectives

Front 29

• Test and Acceptance plan

Back 29

o Contains test cases that must be successfully executed
o Defines customer’s exit criteria

Front 30

Implementation process
(DPIIT)

Back 30

1. Data collection
2. Preparation
3. Installation
4. Implementation
5. Testation

Front 31

Data collection

Back 31

• EMC Grab
• EMC Reports (Windows)
• HEAT (Host Environment Analysis Tool)
• Ad Hoc Commands/Scripts
• Change Tracker (DeltaMark)

Front 32

Change Tracker (DeltaMark)

Back 32

• Licensed through the symchg facility DeltaMark

• Interval length should be set to half the RPO or to the desired cycle time (nothing lower than 10min)

Front 33

SUM Reports (Change Tracker)

Back 33

i. Track changes from the point in time the DeltaMark bitmap was marked and gives a running total
ii. Reports trend up ( exponential graph )

Front 34

DELTA Reports (Change Tracker)

Back 34

i. Track changes that have occurred since the last interval
ii. Reports specific intervals ( many peaks )

Front 35

Preparation

Back 35

Configuration (Symm Configure (Preview, Prepare, Commit))
o Install additional file sets, patches or service packs
o Establish application baseline
o Change device attributes to map to solution
o Zone and mask device for host access
o Configure additional devices

Front 36

Changes to the current environment

Back 36

o Configuration manager

Front 37

Application considerations

Back 37

o Current level of OS
o Data layout
o A metric that determines if an application is running well
o Understanding application characteristics
 Start and stop procedures
 Support for online backups
 Support for consistency options

Front 38

Reconfirm the design

Back 38

o Using the real-time data, verify the solurtion
 Expected behavior
 Installation impact/benefits
 Recovery/return home behavior

Front 39

Configuration Manager

Back 39

preview, prepare and commit

Front 40

Installation

Back 40

• Licensing consideration
• Symlmf (licensing command)
• License Database: symapiliceneses.dat

Front 41

Implementation

Back 41

Customization, Automation, Scheduling, Notification

Front 42

Automation

Back 42

RM
Custom Scripts

Front 43

Scheduling

Back 43

PIT
CRON

Front 44

Notification

Back 44

Logs
Email
SNMP

Front 45

Customization

Back 45

SymQOS
SymACL

Front 46

Quality of Service

Back 46

Allows users to adjust the data transfer pace for Timefinder and SRDF applications

Front 47

Testing

Back 47

• Post implementation tasks
o Verify the implementation
o Diagnostics and troubleshooting
• Customer acceptance and signoff

Front 48

EMC has standards to which implementers must adhere (MD5 Checksum)

Back 48

• Each command line parameter listed should have a short description with it
• Each script should be written with re-usability in mind
• Each time a script is updated, it should be reviewed for accuracy, robustness and to confirm it follows documented standards
• Write all scripts to use standard in/out error
• Report when something goes wrong, not when it works
• Small procedures are easier to understand and maintain

Front 49

The name of each script must reflect its use

Back 49

sh for Bourne shell
• .bat for Windows batch
• .pl for Perl scripts
• .cgi for Common Gateway Interface

Front 50

Configuration/initialization files

Back 50

Extension must be one of the following
o .conf
o .ini
o .txt
• Remarks must start with a #

Front 51

MD5 checksums

Back 51

• Generated when script has been accepted

• Old and new checksums are compared to determine if any changes were made to the script

Front 52

Initial BCV pairings

Back 52

• With the –opt option, Timefinder attempts to
o Pair devices on separate disk adapters
o Pair devices that are on the same disk adapter but are on different SCSI interfaces
o Pair devices that may be on the same DA and SCSI interface but on a separate spindle
• -exact option
o Pairs BCVs in the exact order in which the devices were added to the device group

Front 53

TimeFinder Exchange Integration Module (TEIM)

Back 53

streamlines the collective TimeFinder/Mirror actions required in backup operations of the storage enterprise for Exchange servers

Front 54

TimeFinder Integration Module for SQL Server (TSIM)

Back 54

integrates and automates the features of TimeFinder/Mirror, Solutions Enabler (SYMCLI) and tools supplied with Microsoft SQL Server products.

Front 55

Filesystem and database consistency split

Back 55

• ECA
o –consistant
• PowerPath
o –ppath
 Stdevs (BCVs/Mirrors)
 ?? Srcdevs (Clone/Snap) ??
o –rdb database type ( Oracle, SQL, IBM, etc)
o –VxFS

Front 56

What is symqos?

Back 56

Provides quality of service (QOS) controls on specific devices.

Front 57

What is symacl?

Back 57

Sets up or updates Symmetrix Access Control Information.

Front 58

Data Migration Tools

Back 58

Windows (xcopy, robocopy, open migrator)

UNIX (rsync, volume managers AIX migratepv, HP pvmove, vertias, vxexac).

SRDF

Front 59

What is migratepv?

Back 59

AIX Data Migration Tool

Front 60

What is pvmove?

Back 60

HP-UX Data Migration Tool

Front 61

What is vxevac?

Back 61

Veritas Data Migration Tool.

Front 62

Open Replicator Technology

Back 62

Controls and Remote refer to the control of Open Replicator oeprations, not the direction of the copy.