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 requirementsSybase server software requirements for NetBackup for Sybase
- 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 a Sybase database
- Adding a new NetBackup for Sybase policy
- About policy attributes
- About adding schedules to a NetBackup for Sybase policy
- NetBackup for Sybase backup types
- About schedule properties
- Adding clients to a policy
- Adding NetBackup for Sybase scripts to the backup selections list
- Rules for NetBackup for Sybase scripts
- 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 (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 Windows 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
Sybase backup strategy
One of the major tasks in developing a backup plan is to determine how often to back up your databases. The backup strategy in this section is an example. For guidelines on developing your own backup and recovery plan, refer to your Sybase documentation.
The frequency of your backups determines how much work you can restore in the event of a disaster. Dump each database immediately after you create it to provide a base point, and then dump it on a fixed schedule thereafter.
The following is an example database backup strategy:
- Perform a full database backup by running a database dump every Friday night.
- Back up your Sybase configuration files every Friday night at the same time as the full-database backup.
Sybase recommends that you save all the Sybase scripts. This includes the scripts that contain the disk init, create database, and alter database commands.
Sybase also recommends that you save a hard copy of your sysdatabases, sysusages, and sysdevices tables each time you issue one of these commands. In addition, keep a copy of the syslogins.
- Perform an incremental backup each night by running a transaction log dump.