Presentation on theme: "SQL-BackTrack for Sybase System Consultant Manager System Consultant."— Presentation transcript:
SQL-BackTrack for Sybase System Consultant Manager System Consultant
Severity of Database Downtime Planned Unplanned Catastrophic Latency of Database Recovery No Downtime High Availability Continuous Availability Disaster Recovery Online Maintenance Offline Maintenance High Availability Clusters Switching and Warm Standby Replication Cold Standby
80% of all unplanned downtime is caused by software or human error* 80% of all unplanned downtime is caused by software or human error* 70% of recovery is "think time"! 70% of recovery is "think time"! *Source: Gartner, Aftermath: Disaster Recovery, Vic Wheatman, September 21, 2001
AnalysisSourcePreparation Restore RecoverPost-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 post- recovery clean-up processes Investigate data loss/ corruption and discover what information must be replaced SQL-BackTrack automates the entire process!
Why SQL-BackTrack? An example of a recovery of a Sybase database using the native utility 1. Determine which database to recover 2. Determine where backups are located 3. If the backups are striped locate all the stripes 4. 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 recovery 6. If it is a point in time recovery determine the transaction log backups to be applied. 7. Start an isql session 8. Issue load database 9. Issue load transaction for all the transaction log backups 10. If the recovery is PIT issue load transaction with until_time 11. Issue online database or online for standby access 12. 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 recover 2. Determine where backups are located 3. If the backups are striped locate all the stripes 4. 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 recovery 6. If it is a point in time recovery determine the transaction log backups to be applied. 7. Start an isql session 8. Issue load database 9. Issue load transaction for all the transaction log backups 10. If the recovery is PIT issue load transaction with until_time 11. Issue online database or online for standby access 12. Determine if the database and application are ready for production use. SQL-BackTrack reduces this effort to 2 STEPS!!
ASE SQL-BackTrack BT Module Server Program Media/ Client Program Tape Devices Juke Boxes IBM Tivoli Storage Manager VERITAS NetBackup DataCenter Legato NetWorker OBSI
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.
SQL-BackTrack Components SQL-BackTrack Control Directory (with Control Files) sbacktrack Executables (main BT program). dtoptions file SQL Server Backup device OBSI Software Backup device OBSI Software Backup device OBSI Software
SQL-BackTrack Control Directory sbackups.logicalsbackups.physical /usr/sbt/ Server1Server 2Server 1Server 2.dtoptionsDB1DB2
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)
SQL-BackTrack for Sybase vs Competition ASE and extension are limited to scripts. SBT obtains relevant logs at backup time automatically. Limited YES Transaction Log Backup Automation SBTs Logical Extraction feature can recover tables, stored procedures, triggers, etc. directly from a physical backup NO YES Logical object recovery from a physical backup NO YES Logical database backup ASE and extensions will only migrate data. SBT backups up table schema, dependencies, and data. (SBT unique) Limited YES Logical object backup NO YES Extensions (VERITAS & Legato) YES Physical database backup (full) NO ASE 12.0/ 12.5 SBTs intelligent incremental backup feature writes only physical data blocks that have changed since last backup YES Physical database backup (Incremental) CommentsSBTFunction Unique/noteworthy feature
SQL-BackTrack for Sybase vs Competition SBT allows users to recover information to alternate locations (Powerful DR support tool) NO YES Recover to alternate host, database NO YES Dry 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. Limited YES Migration 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 Unique/noteworthy feature
SQL-BackTrack for Sybase vs Competition Master Database recovery is a tedious, manual process. SBT greatly simplifies process by generating template with relevant information in support of recovery. Limited YES Master Database Recovery Template Extensions (VERITAS & Legato) ASE 12.0/ 12.5 CommentsSBTFunction Unique/noteworthy feature Limited NO Extensions provide vendor specific support. SBT Modules provide seamless integration with IBM Tivoli Storage Manager (TSM), VERITAS NetBackup DataCenter, and Legato NetWorker NOYES Storage Manager Integration NO SBT can recover tables, stored procedures, triggers, etc. directly from a physical backup YES Encryption