Veritas NetBackup™ for Sybase Administrator's Guide

Last Published:
Product(s): NetBackup (8.2, 8.1.2)
  1. Introduction to NetBackup for Sybase
    1.  
      About NetBackup for Sybase
    2.  
      Features of NetBackup for Sybase
    3.  
      NetBackup for Sybase terminology
    4. NetBackup for Sybase overview
      1.  
        SQL server and Sybase backup server
      2.  
        NetBackup for Sybase technical overview
      3.  
        Sequence of operation for NetBackup for Sybase backups
  2. Installing NetBackup for Sybase
    1.  
      Planning the installation of NetBackup for Sybase
    2.  
      Verifying the operating system and platform compatibility
    3.  
      NetBackup server and client requirements
    4.  
      Sybase server software requirements
    5.  
      Requirements for using NetBackup for Sybase in a NetBackup cluster
    6.  
      About the license for NetBackup for Sybase
    7.  
      Copying the NetBackup for Sybase library to each Sybase instance
    8.  
      Running the sybase_config script
    9.  
      Adding new Sybase instances
  3. Configuring NetBackup for Sybase
    1.  
      About NetBackup for Sybase configuration
    2. About configuring a backup policy for Sybase
      1.  
        Adding a new NetBackup for Sybase policy
      2.  
        About policy attributes
      3.  
        About schedule properties
      4. NetBackup for Sybase backup types
        1.  
          Configuring an application backup schedule
        2.  
          Example application backup schedule
        3.  
          Configuring automatic backup schedules
        4.  
          Example automatic backup schedule
      5.  
        Adding clients to a policy
      6.  
        Adding NetBackup for Sybase scripts to the backup selections list
      7.  
        Rules for NetBackup for Sybase scripts
    3. About the backup, restore, and load scripts for NetBackup for Sybase on UNIX
      1.  
        Modifying the backup script for NetBackup for Sybase on UNIX
      2.  
        Example sybase_mydb_backup.cmd script for NetBackup
      3.  
        Modifying the restore script for NetBackup for Sybase on UNIX
      4.  
        Example of a sybase_mydb_restore script
    4. About the backup, restore, and load scripts for NetBackup for Sybase on Windows
      1.  
        Modifying the backup script for NetBackup for Sybase on Windows
      2.  
        sybase_mdb_backup.cmd script
      3.  
        Additional information for editing the backup script for NetBackup for Sybase on Windows
      4.  
        Modifying the restore script for NetBackup for Sybase on Windows
      5.  
        sybase_mydb_restore.cmd script example for NetBackup
      6.  
        Additional information for editing the restore script for NetBackup for Sybase on Windows
    5.  
      Modifying the NetBackup for Sybase load script
    6.  
      NetBackup for Sybase environment variables
    7. NetBackup for Sybase configuration or bp.conf file settings
      1.  
        Creating a $SYBASE_HOME/bp.conf file on the UNIX client
      2.  
        Specifying options in /usr/openv/netbackup/bp.conf on the UNIX client
    8.  
      Configuring the logon account for the NetBackup Client Service for NetBackup for Sybase
    9. About striped dumps and loads with NetBackup for Sybase
      1.  
        Example Sybase scripts for striped dumps and loads
      2.  
        NetBackup for Sybase multiplexing considerations - duplicating tapes
      3.  
        NetBackup for Sybase multiplexing considerations - using more than 12 stripes
    10.  
      Reviewing the auto-discovered mappings in Host Management
    11.  
      About permissions for NetBackup for Sybase log files (UNIX)
    12.  
      Configuring the Maximum jobs per client
    13.  
      Performing a manual backup
  4. Using NetBackup for Sybase
    1. About Sybase database backups
      1.  
        Sybase backup strategy
      2.  
        Automatic backups of a Sybase database
      3.  
        Backing up a Sybase database manually
      4.  
        Performing a user-directed backup for Sybase
    2.  
      Browsing Sybase backups
    3. About restoring a Sybase database
      1.  
        Using isql to restore a Sybase database
      2.  
        Configuring a redirected restore on the NetBackup for Sybase client
  5. Troubleshooting NetBackup for Sybase
    1. NetBackup debug logs and reports
      1.  
        Enabling the debug logs for a NetBackup for Sybase client automatically (Windows)
      2.  
      3.  
        Enabling the debug logs manually (UNIX)
      4.  
        About the bphdb directory on the Windows database client
      5.  
        About the bphdb directory on the UNIX database client
      6.  
        About the sybackup directory on the UNIX database client
      7.  
        About the sybackup directory on the Windows database client
      8.  
      9.  
        Setting the debug level on a UNIX client
      10.  
        About NetBackup server reports
    2.  
      Sybase Backup Server log and messages
    3.  
      Minimizing timeout failures on large database restores
    4.  
      Minimizing the loading and unloading of tapes for database backups
    5.  
      Delays in completion of backup jobs
  6. Appendix A. Register authorized locations
    1.  
      Registering authorized locations used by a NetBackup database script-based policy

Registering authorized locations used by a NetBackup database script-based policy

During a backup, NetBackup checks for scripts in the default script location and any authorized locations. The default, authorized script location for UNIX is usr/openv/netbackup/ext/db_ext and for Windows is install_path\netbackup\dbext. If the script is not in the default script location or an authorized location, the policy job fails. You can move any script into the default script location or any additional authorized location and NetBackup recognizes the scripts. You need to update the policy with the script location if it has changed. An authorized location can be a directory and NetBackup recognizes any script within that directory. An authorized location can also be a full path to a script if an entire directory does need to be authorized.

If the default script location does not work for your environment, use the following procedure to enter one or more authorized locations for your scripts. Use nbsetconfig to enter an authorized location where the scripts reside. You can also use bpsetconfig, however this command is only available on the master or the media server.

Note:

One recommendation is that scripts should not be world-writable. NetBackup does not allow scripts to run from network or remote locations. All scripts must be stored and run locally. Any script that is created and saved in the NetBackup db_ext (UNIX) or dbext (Windows) location needs to be protected during a NetBackup uninstall.

For more information about registering authorized locations and scripts, review the knowledge base article:

http://www.veritas.com/docs/000126002

To add an authorized location

  1. Open a command prompt on the client.
  2. Use nbsetconfig to enter values for an authorized location. The client privileged user must run these commands.

    The following examples are for paths you may configure for the Oracle agent. Use the path that is appropriate for your agent.

    • On UNIX:

      [root@client26 bin]# ./nbsetconfig
      nbsetconfig>DB_SCRIPT_PATH = /Oracle/scripts
      nbsetconfig>DB_SCRIPT_PATH = /db/Oracle/scripts/full_backup.sh
      nbsetconfig>
      <ctrl-D>
    • On Windows:

      C:\Program Files\Veritas\NetBackup\bin>nbsetconfig
      nbsetconfig> DB_SCRIPT_PATH=c:\db_scripts
      nbsetconfig> DB_SCRIPT_PATH=e:\oracle\fullbackup\full_rman.sh
      nbsetconfig>
      <ctrl-Z>
      

    Note:

    Review the NetBackup Command Reference Guide for options, such as reading from a text file and remotely setting clients from a NetBackup server using bpsetconfig. If you have a text file with the script location or authorized locations listed, nbsetconfig or bpsetconfig can read from that text file. An entry of DB_SCRIPT_PATH=none does not allow any script to execute on a client. The none entry is useful if an administrator wants to completely lock down a server from executing scripts.

  3. (Conditional) Perform these steps on any clustered database or agent node that can perform the backup.
  4. (Conditional) Update any policy if the script location was changed to the default or authorized location.