SQL-BackTrack for Sybase

System Consultant Manager System Consultant

Agenda

Catastrophic

Disaster Recovery

Severity of Database Downtime

Unplanned

High Availability
High Availability Clusters

Planned

Offline Maintenance

Switching and Warm Standby Replication

Cold Standby

No Downtime

Online Maintenance

Continuous Availability

Latency of Database Recovery

80% of all unplanned downtime is caused by software or human error* 70% of recovery is "think time"!
Investigate 20% Diagnose 20% Analyze 30%

Recover 30%
*Source: Gartner, Aftermath: Disaster Recovery, Vic Wheatman, September 21, 2001

Analysis

Investigate data loss/ corruption and discover what information must be replaced

SQL-BackTrack automates the entire process!

Source Preparation Restore Recover Post-op
Identify location of and retrieve backup data Issues the appropriate commands needed to prepare the database for the recovery process Copies backup data to the correct destination Issues the appropriate command in the correct sequence

Perform appropriate postrecovery clean-up processes

Why SQL-BackTrack?
An example of a recovery of a Sybase database using the native utility
1. 2. 3. 4. 5. 6. 7. 8. 9.

10.
11. 12.

Determine which database to recover Determine where backups are located If the backups are striped locate all the stripes Order the backups in the required sequence to be applied. Determine the recovery type: physical, transaction log , is there a specific point in time for the recovery If it is a point in time recovery determine the transaction log backups to be applied. Start an isql session Issue load database Issue load transaction for all the transaction log backups If the recovery is PIT issue load transaction with until_time Issue online database or online for standby access Determine if the database and application are ready for production use.

Why SQL-BackTrack?
An example of a recovery of a Sybase database using the native utility
1. 2. 3. 4. 5. 6. 7. 8. 9.

10.
11. 12.

Determine which database to recover Determine where backups are located If the backups are striped locate all the stripes Order the backups in the required sequence to be applied. Determine the recovery type: physical, transaction log , is there a specific point in time for the recovery If it is a point in time recovery determine the transaction log backups to be applied. Start an isql session Issue load database Issue load transaction for all the transaction log backups If the recovery is PIT issue load transaction with until_time Issue online database or online for standby access Determine if the database and application are ready for production use.

Agenda

d t s b a c ku p

control channel

d ts du mp

OBSI
IPC channel

Backup Destination

control directory

queries & commands bcp out

dump database

SYBASE dataserver

SYBASE backupserver

control channel d t s r e co ver

d ts lo ad

OBSI
IPC channel

Backup Destination

control directory

queries & commands bcp in

load database

SYBASE dataserver

SYBASE backupserver

OBSI

ASE SQL-BackTrack BT Module Server Program

Tape Devices Juke Boxes

Media/ Client Program

IBM

Tivoli Storage Manager

VERITAS
Legato

NetBackup DataCenter

NetWorker

OBSI

Agenda

Common SQL-BackTrack Features

Dry run backup and recovery Table recovery from physical backup Unattended on-line and off-line backup Incremental backups Compression and encryption Storage management integration Guided recovery

Unique SQL-BackTrack Features for Sybase

Master database recovery

Needs to be rebuilt, if lost or damaged Generates Master Database Recovery template script to recover

Remote administration Warm stand-by server support Table level recovery includes recovery of dependent objects (triggers, etc.)

Unique SQL-BackTrack Features over Sybase Native Utilities

Logical Object extraction features:

DDL Only DDL + Data Specific objects or object types like: stored procedures only or tables only Will add objects to database in dependency order. For instance, will compile stored procedures into database in dependency order. Can exclude specific objects like: exclude sysusers, sysalternates tables when copying database to another server. Or you can exclude a type of object like exclude all triggers. Extract/restore database object and all of its dependent objects Default is fast bcp in, unless told to do otherwise. Automatically takes care of rebuilding indexes.

Unique SQL-BackTrack Features over Sybase Native Utilities

Logical restore options make shrinking your database much easier. 1 step - do a logical restore to a smaller database. Warm Stand-by Server Support Master database info, writes a text file of useful information about the master database such as device, configuration, database, sysusages, and syslogin information taken from a physical backup. Very useful in recovering the master database.

Unique SQL-BackTrack Features over Sybase Native Utilities

Can restore data to a database using full sql insert statements -- useful if select into/bulk copy option is turned off Can restore data to a different segment. Useful if you want to eliminate segments or move data from one segment to another Prints database allocation info. (sysusages) from a physical backup. Useful if you have to manually recreate the database. Supports calling SQL-BackTrack log dump commands from a stored procedure. Useful for thresholds.

Agenda

SQL-BackTrack Components
SQL-BackTrack Control Directory (with Control Files) SQL Server

.dtoptions file .dtoptions file

OBSI Software OBSI Software OBSI Software

Backup device Backup device

SQL Server

SQL Server

.dtoptions file
sbacktrack Executables (main BT program)

Backup device

SQL-BackTrack Executables
sbacktrack
(main BT program)

dtsbackup dtsdump dtscreate

(lower-level SQL-BackTrack programs)

dtsrecover dtsload dtscheck

SQL-BackTrack Control Directory

/usr/sbt/

sbackups.physical

sbackups.logical

Server1

Server 2

Server 1

Server 2

.dtoptions

DB1

DB2

Special Recovery Situations

Copying a database to a different machine / Migrating a database Object extraction from physical backups Resizing a database Generating recovery templates(Master)

Agenda

SQL-BackTrack for Sybase vs Competition

Function SBT ASE 12.0/ 12.5
YES NO

Extensions (VERITAS & Legato)

YES NO

Comments

Physical database backup (full) Physical database backup (Incremental) Transaction Log Backup Automation Logical database backup Logical object backup

YES YES

SBTs intelligent incremental backup feature writes only physical data blocks that have changed since last backup ASE and extension are limited to scripts. SBT obtains relevant logs at backup time automatically.

YES

Limited

Limited

YES YES

NO Limited

NO Limited ASE and extensions will only migrate data. SBT backups up table schema, dependencies, and data. (SBT unique)

Logical object recovery from a physical backup

YES

NO

NO

SBTs Logical Extraction feature can recover tables, stored procedures, triggers, etc. directly from a physical backup

Unique/noteworthy feature

SQL-BackTrack for Sybase vs Competition

Function SBT ASE 12.0/ 12.5
NO

Extensions (VERITAS & Legato)

NO

Comments

Recover to alternate host, database Dry Run Recovery Automation

YES

SBT allows users to recover information to alternate locations (Powerful DR support tool)

YES YES

NO Limited

NO Limited
ASE automation limited to commands included in scripts created by DBA. Extensions allow ASE scripts to be scheduled for execution. SBT provides guided recovery to automate backup & recovery as well as generate scripts automatically for use in scheduler. ASE (BCP utility) and extensions will logically backup data but not schema and is limited to environments with same OS and ASE levels. SBT will migrate data between differing ASE and OS versions as well as between varying database page sizes.

Migration

YES

Limited

Limited

Unique/noteworthy feature

SQL-BackTrack for Sybase vs Competition

Function SBT ASE 12.0/ 12.5
Limited

Extensions (VERITAS & Legato)

Limited

Comments

Master Database Recovery Template

YES

Master Database recovery is a tedious, manual process. SBT greatly simplifies process by generating template with relevant information in support of recovery.

Encryption

YES

NO

NO

SBT can recover tables, stored procedures, triggers, etc. directly from a physical backup
Extensions provide vendor specific support. SBT Modules provide seamless integration with IBM Tivoli Storage Manager (TSM), VERITAS NetBackup DataCenter, and Legato NetWorker

Storage Manager Integration

YES

NO

Limited

Unique/noteworthy feature

Questions and Discussion