Veritas NetBackup™ for Sybase Administrator's Guide
- Introduction to NetBackup for Sybase
- Installing NetBackup for Sybase
- Planning the installation of NetBackup for Sybase
- Verifying the operating system and platform compatibility
- NetBackup server and client requirements
- Sybase server software requirements
- Requirements for using NetBackup for Sybase in a NetBackup cluster
- About the license for NetBackup for Sybase
- Copying the NetBackup for Sybase library to each Sybase instance
- Running the sybase_config script
- Adding new Sybase instances
- Configuring NetBackup for Sybase
- About NetBackup for Sybase configuration
- About configuring a backup policy for Sybase
- About the backup, restore, and load scripts for NetBackup for Sybase on UNIX
- About the backup, restore, and load scripts for NetBackup for Sybase on Windows
- Modifying the backup script for NetBackup for Sybase on Windows
- sybase_mdb_backup.cmd script
- Additional information for editing the backup script for NetBackup for Sybase on Windows
- Modifying the restore script for NetBackup for Sybase on Windows
- sybase_mydb_restore.cmd script example for NetBackup
- Additional information for editing the restore script for NetBackup for Sybase on Windows
- Modifying the NetBackup for Sybase load script
- NetBackup for Sybase environment variables
- NetBackup for Sybase configuration or bp.conf file settings
- Configuring the logon account for the NetBackup Client Service for NetBackup for Sybase
- About striped dumps and loads with NetBackup for Sybase
- Reviewing the auto-discovered mappings in Host Management
- About permissions for NetBackup for Sybase log files (UNIX)
- Configuring the Maximum jobs per client
- Performing a manual backup
- Using NetBackup for Sybase
- Troubleshooting NetBackup for Sybase
- NetBackup debug logs and reports
- Enabling the debug logs for a NetBackup for Sybase client automatically (Windows)
- Enabling the debug logs manually (UNIX)
- About the bphdb directory on the Windows database client
- About the bphdb directory on the UNIX database client
- About the sybackup directory on the UNIX database client
- About the sybackup directory on the Windows database client
- Setting the debug level on a UNIX client
- About NetBackup server reports
- Sybase Backup Server log and messages
- Minimizing timeout failures on large database restores
- Minimizing the loading and unloading of tapes for database backups
- Delays in completion of backup jobs
- NetBackup debug logs and reports
- Appendix A. Register authorized locations
Using isql to restore a Sybase database
The steps required to recover a Sybase database depend on the database that is involved and the problem that you have on your system.
These steps can include the following:
Using buildmaster, installmaster, and installmodel for system databases
Re-creating database devices
Re-creating databases
Loading database dumps
Applying transaction logs
For information on how to perform the preceding steps, see your Sybase documentation.
A load can take significantly longer than a dump. The time required to load a database depends on the overall number of pages in the database. The load database command loads all used pages from the dump into the target database and runs recovery of syslogs to ensure consistency. The load process initializes any unused pages.
You can load database and transaction dumps by manually submitting the Sybase LOAD command to SQL server (UNIX and Linux) or the isql utility on the client (Windows).
The LOAD command must include the appropriate dump file name. More information is available about how to edit the LOAD command with the correct dump file name.
Make sure to load the database dump and all of the transaction logs before bringing the database back online.
The following example shows you how to restore the database mydb to the level of a recent database dump plus two transaction log dumps:
Execute the LOAD commands directly from SQL server.
This loads the database dump and transaction log dumps.
Check database consistency.
When you have brought the database up-to-date, use DBCC commands to check the consistency of the database.
load database mydb from "sybackup::SYBASE.mydb.D.0.14693.12-12-1997.09:29:37 -SERV saturn" go