SQL BackTrack

SQL-BackTrack for Sybase

高正宗System Consultant Manager黃仁政System Consultant

Agenda

資料庫的可用性系統架構產品功能說明實機展示產品比較

資料可用性的策略

Severity o

f Datab

ase Do

wn

time

Planned

Unplanned

Catastrophic

Latency of Database Recovery

No Downtime

HighAvailability

ContinuousAvailability

DisasterRecovery

OnlineMaintenance

OfflineMaintenance

HighAvailability

Clusters

Switchingand WarmStandby

Replication

ColdStandby

80% 80% of all unplanned downtime is caused by of all unplanned downtime is caused by software or human error*software or human error*

70% of recovery is 70% of recovery is "think time""think time"!!

*Source: Gartner, “Aftermath: Disaster Recovery”, Vic Wheatman, September 21, 2001*Source: Gartner, “Aftermath: Disaster Recovery”, Vic Wheatman, September 21, 2001

Diagnose20%

Investigate20%

Analyze30%

Recover30%

復原作業的問題

Analysis Source Preparation Restore Recover Post-op

Identify location of and

retrieve backup

data

Issues theappropriatecommandsneeded to prepare thedatabase forthe recovery

process

Copiesbackup

data to thecorrect

destination

Issues theappropriatecommand

in the correct

sequence

Perform appropriate

post-recoveryclean-up

processes

Investigate data loss/ corruption

and discover

what information

must be replaced

SQL-BackTrack SQL-BackTrack automates the automates the entire process!entire process!

確保復原作業

Why SQL-BackTrack? An example of a recovery of a Sybase database using the native utility

1. Determine which database to recover2. Determine where backups are located3. If the backups are striped locate all the stripes4. Order the backups in the required sequence to be applied.5. Determine the recovery type: physical, transaction log , is there a

specific point in time for the recovery6. If it is a point in time recovery determine the transaction log backups

to be applied.7. Start an isql session8. Issue load database9. Issue load transaction for all the transaction log backups10. If the recovery is PIT issue load transaction with until_time11. Issue online database or online for standby access12. 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. Determine which database to recover2. Determine where backups are located3. If the backups are striped locate all the stripes4. Order the backups in the required sequence to be applied.5. Determine the recovery type: physical, transaction log , is there a

specific point in time for the recovery6. If it is a point in time recovery determine the transaction log backups

to be applied.7. Start an isql session8. Issue load database9. Issue load transaction for all the transaction log backups10. If the recovery is PIT issue load transaction with until_time11. Issue online database or online for standby access12. Determine if the database and application are ready for production

use.

SQL-BackTrack

reduces this effort

to 2 STEPS!!SQL-BackTrack

reduces this effort

to 2 STEPS!!

Agenda


ddttssdduummpp

queries &commands

controlchannel

bcp out

dump database

IPCchannel

ddttssbbaacckkuupp

SSYYBBAASSEEddaattaasseerrvveerr

SSYYBBAASSEEbbaacckkuuppsseerrvveerr

controldirectory

BBaacckkuuppDDeessttiinnaattiioonnOBSI

備份作業

ddttssllooaadd

queries &commands

controlchannel

bcp in

load database

IPCchannel

SSYYBBAASSEEddaattaasseerrvveerr

SSYYBBAASSEEbbaacckkuuppsseerrvveerr

controldirectory

BBaacckkuuppDDeessttiinnaattiioonnOBSIddttssrreeccoovveerr

復原作業

ASE

SQL-BackTrack

BT Module

ServerProgram

Media/ Client Program

TapeDevices

JukeBoxes

IBM Tivoli Storage Manager

VERITAS NetBackup DataCenter

Legato NetWorker

OBSI模組整合

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 it’s dependent objects

Default is fast bcp in, unless told to do otherwise. Automatically takes care of rebuilding indexes.


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.


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)

sbacktrackExecutables

(main BT program)

.dtoptions file

.dtoptions file

.dtoptions file

SQL Server

SQL Server

SQL Server

Backup device

OBSI Software

Backup device

OBSISoftware

Backup device

OBSI Software

SQL-BackTrack Executables

(lower-level SQL-BackTrack programs)

sbacktrack(main BT program)

dtsbackup dtsrecover

dtsloaddtsdump

dtscheckdtscreate

SQL-BackTrack Control Directory

sbackups.logicalsbackups.physical

/usr/sbt/

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

ASE and extension are limited to scripts. SBT obtains relevant logs at backup time automatically.

LimitedLimitedYESTransaction Log Backup Automation

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

NONOYES Logical object recovery from a physical backup

NONOYES Logical database backup

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

LimitedLimitedYES Logical object backup

NO

YES

Extensions (VERITAS &

Legato)YESYESPhysical database

backup (full)

NO

ASE 12.0/ 12.5

SBT’s intelligent incremental backup feature writes only physical data blocks that have changed since last backup

YES Physical database backup (Incremental)

CommentsSBTFunction

Unique/noteworthy feature


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

NONOYESRecover to alternate host, database

NONOYESDry Run Recovery

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.

LimitedLimitedYESMigration

Limited

Extensions (VERITAS & Legato)

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.

LimitedYES Automation

ASE 12.0/ 12.5

CommentsSBTFunction



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

LimitedLimitedYESMaster Database Recovery Template

Extensions (VERITAS &

Legato)

ASE 12.0/ 12.5

CommentsSBTFunction


Limited

NO

Extensions provide vendor specific support. SBT Modules provide seamless integration with IBM Tivoli Storage Manager (TSM), VERITAS NetBackup DataCenter, and Legato NetWorker

NOYESStorage Manager Integration

NO SBT can recover tables, stored procedures, triggers, etc. directly from a physical backup

YESEncryption

Questions and Discussion

SQL BackTrack

Documents

Transcript of SQL BackTrack