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
NetBackup for Sybase technical overview
NetBackup for Sybase has a dynamically loadable library that provides the functions necessary for Sybase backup server to use NetBackup. This library is installed when NetBackup for Sybase is installed.
NetBackup for Sybase is integrated with Sybase backup server through the Sybase backup server archive API. Sybase backup server uses the archive API routines to issue I/O requests to an archive-byte stream. At run time, Sybase backup server loads the NetBackup for Sybase library and makes calls to the API routines to open, close, read, and write to the byte stream through this API interface.
The dump-device string of the Sybase DUMP and LOAD commands is extended to support the archive API. The following syntax instructs Sybase backup server to use the NetBackup archive device to transfer data to and from NetBackup:
"sybackup::"
The Sybase DUMP command is as follows:
dump database model to "sybackup::"
SQL Server and Sybase backup server do not have a backup-catalog feature. However, when you perform a database or transaction dump, NetBackup for Sybase automatically creates a file name for the dump image. You must then specify this file name during a subsequent load operation.
The file naming convention for the database and transaction dumps is the following:
sql_server_name.database_name.backup_type.stripe_number.pid.dd-mm-yyyy.hh:mm:ss
The backup_type is either D for database or T for transaction.
For example:
SYBASE11.mydb.D.0.24312.17-12-2003.14:05:25