VERITAS NetBackup™ System Administrator’s...

®

VERITAS NetBackup™System Administrator’s Guide

for SQL-BackTrackRelease 3.2

UNIX

August 1999

P/N 100-000992

NetBackup 3.2 System Administrator's Guide for SQL-BackTrack - UNIX




© 1996 - 1999 VERITAS® Software Corporation. All rights reserved.

Portions of this software are derived from the RSA Data Security, Inc. MD5 Message-Digest Algorithm. Copyright 1991-92,RSA Data Security, Inc. Created 1991. All rights reserved.

TRADEMARKS

VERITAS, VxVM, VxVA, VxFS, FirstWatch, and the VERITAS logo are registered trademarks of VERITAS SoftwareCorporation in the United States and other countries.

VERITAS Volume Manager, VERITAS File System, VERITAS NetBackup, VERITAS HSM, VERITAS Media Librarian,CVM, VERITAS Quick I/O, and VxSmartSync are trademarks of VERITAS Software Corporation.

Other products mentioned in this document are trademarks or registered trademarks of their respective holders.



iii

Contents

1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Terminology for NetBackup for SQL-BackTrack . . . . . . . . . . . . . . . . . . . . 2

Features of NetBackup for SQL-BackTrack . . . . . . . . . . . . . . . . . . . . . . . . 3

Technical Overview of NetBackup for SQL-BackTrack . . . . . . . . . . . . . . 5

How Does NetBackup for SQL-BackTrack Work? . . . . . . . . . . . . . . . 6

Sequence of Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2. Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Install NetBackup for SQL-BackTrack . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

3. Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Configure the Media Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Add DataTools-SQL-BackTrack Classes to NetBackup . . . . . . . . . . . . . . 17

Set Maximum Jobs per Client Global Attribute. . . . . . . . . . . . . . . . . . . . . 24

Create Directories for Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Create Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

SQL-BackTrack for Sybase Example . . . . . . . . . . . . . . . . . . . . . . . . . . 27

SQL-BackTrack for Oracle Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Configure NetBackup for SQL-BackTrack on the Client . . . . . . . . . . . . . 30

Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30



iv NetBackup for DataTools SQL-BackTrack System Administrator’s Guide - UNIX

SQL-BackTrack nb_obsi Backup Pool Configuration . . . . . . . . . . . 30

Configure the bp.conf Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Test NetBackup for SQL-BackTrack Configuration Settings . . . . . . . . . . 33

Parallel Backup Streams and Dump Striping . . . . . . . . . . . . . . . . . . . . . . 34

Alternate Client Restore Configuration on the Client . . . . . . . . . . . . . . . 35

4. Using NetBackup for SQL-BackTrack. . . . . . . . . . . . . . . . . . . . . . . . . 37

Performing a Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Automatic Backup of a DataTools-SQL-BackTrack Class . . . . . . . . . 38

Manual Backup of a DataTools-SQL-BackTrack Class . . . . . . . . . . . . 38

User-Directed Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Using the SQL-BackTrack Interface to Backup . . . . . . . . . . . . . . 39

Using xbp to Back Up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Using bp to Back Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Performing a Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Using SQL-BackTrack User Interface to Restore . . . . . . . . . . . . . . . . 45

Using xbp to Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Using bp to Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Performing Other SQL-BackTrack Actions . . . . . . . . . . . . . . . . . . . . . . . . 53

5. Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

NetBackup Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

NetBackup Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

NetBackup Client Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

NetBackup Server Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Other NetBackup Activity Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

dtwatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Debug Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58



v

Preface

This guide describes how to install, configure and use VERITAS NetBackup forSQL-BackTrack on a UNIX platform. VERITAS NetBackup for SQL-BackTrackbacks up and restores Oracle and Sybase databases. Refer to the readme fileprovided with the distribution package for details on version levels supported.

This product integrates the SQL-BackTrack API with VERITAS NetBackup andessentially makes all the features of both products available to the databaseadministrator. SQL-BackTrack is an independent product that must bepurchased separately from BMC Software, Inc.

In this guide, VERITAS NetBackup for SQL-BackTrack is referred to asNetBackup for SQL-BackTrack.

For specific information about the NetBackup Server software, refer to:

• NetBackup System Administrator’s Guide - UNIX, if you have a UNIX server.

or

• NetBackup System Administrator’s Guide - Windows NT Server if you have aWindows NT server.

This document is the same as nbag_sql_backtrack.pdf distributed withthe NetBackup for SQL-BackTrack software.



vi NetBackup for DataTools SQL-BackTrack System Administrator’s Guide - UNIX

AudienceThis guide is intended for the:

• Oracle or Sybase database system administrator who will be configuringNetBackup for SQL-BackTrack.

• The NetBackup system administrator responsible for configuringNetBackup.

A system administrator is defined as a person with system administratorprivileges and responsibilities.

This guide assumes:

• A basic understanding of system administration.

• A working understanding of the NetBackup client and server software.

• A familiarity with the information covered in the following NetBackupmanuals:

• NetBackup User’s Guide - UNIX

• NetBackup System Administrator’s Guide - UNIX or NetBackup SystemAdministrator’s Guide - Windows NT Server

• NetBackup Troubleshooting Guide

• A thorough understanding of SQL-BackTrack software is required.



Preface vii

OrganizationThis guide is organized as follows:

• Chapter 1, “Introduction” is an overview of the product’s capabilities.

• Chapter 2, “Installation” provides instructions for installing NetBackup forSQL-BackTrack.

• Chapter 3, “Configuration” explains how to configure your system to useNetBackup for SQL-BackTrack.

• Chapter 4, “Using NetBackup for SQL-BackTrack” explains how to useNetBackup for SQL-BackTrack to back up and recover your databases.



viii NetBackup for DataTools SQL-BackTrack System Administrator’s Guide - UNIX

Related DocumentsThe following documents provide related information. For a more detailedlisting of NetBackup documents, refer to NetBackup Release Notes - UNIX orNetBackup Release Notes - Windows NT Server.

If you have a UNIX server, refer to these documents:

• NetBackup Release Notes - UNIX

Provides important information about UNIX NetBackup server software,such as the platforms and operating systems that are supported andoperating notes that may not be in the manuals or the online help.

• NetBackup System Administrator’s Guide - UNIX

Explains how to configure and manage NetBackup on a UNIX system.

• Media Manager System Administrator’s Guide - UNIX

Explains how to configure and manage the storage devices and media onUNIX NetBackup servers. Media Manager is part of NetBackup.

• NetBackup Troubleshooting Guide

Provides troubleshooting information for UNIX based NetBackup products.

If you have a Windows NT server, refer to these documents:

• NetBackup Release Notes - Windows NT Server

Provides important information about Windows NT NetBackup serversoftware, such as the platforms and operating systems that are supported andoperating notes that may not be in the manuals or the online help.

• NetBackup System Administrator’s Guide - Windows NT Server

Explains how to configure and manage NetBackup on a Windows NT serversystem.

• Media Manager System Administrator’s Guide - Windows NT Server

Explains how to configure and manage the storage devices and media onWindows NT NetBackup servers. Media Manager is part of NetBackup.

• NetBackup Troubleshooting Guide - Windows NT Server

Provides troubleshooting information for Windows NT based NetBackupproducts.



Preface ix

ConventionsThe following explains typographical and other conventions used in this guide.

Type Style

The following table describes the typographic conventions used in this guide.

Notes and Cautions

Note: This is a Note and is used to call attention to information that makes iteasier to use the product or helps you to avoid problems.

CAUTION! This is a Caution and is used to warn you about situations that cancause data loss.

Keyboard Sequences

Some keyboard command sequences use two or more keys at the same time.For example, you may have to hold down the Ctrl key before you press anotherkey. When this type of command is referenced, the keys are connected byhyphens. For example, Ctrl-t.

Typeface Usage Examples

courier Computer output; user input;names of commands, files, anddirectories

You have mail.

The mkdir commandcreates a new directory.

mkdir new

italics New terms; document titles;words to be emphasized;variables to be substituted witha real name or value

mkdir filename

Refer to the User’s Guide fordetails.

bold Glossary terms



x NetBackup for DataTools SQL-BackTrack System Administrator’s Guide - UNIX

Command Usage

The following conventions are frequently used in the synopsis of commandusage.

brackets [ ]

The enclosed command line component is optional.

Vertical bar or pipe (|)

Separates optional arguments from which the user can choose. Forexample, when a command has the following format:

command [ arg1| arg2]

the user can use either arg1 or arg2.

Getting HelpFor license information or information about VERITAS service packages,contact VERITAS Customer Support.

US Customers: 1-800-342-0652

International Customers: +1 (650) 335-8555

Fax: (650) 335-8428

VERITAS Customer Support can also be reached through electronic mail at:

[email protected]



1

Introduction 1

NetBackup for SQL-BackTrack integrates the database backup and restorecapabilities of SQL-BackTrack with the backup and restore managementcapabilities of NetBackup and its Media Manager.

This chapter introduces NetBackup for SQL-BackTrack and how it relates toboth SQL-BackTrack and NetBackup. Read this chapter for a description of:

• Terminology for NetBackup for SQL-BackTrack

• Features of NetBackup for SQL-BackTrack



2 NetBackup for SQL-BackTrack System Administrator’s Guide

1

Terminology for NetBackup for SQL-BackTrackThis section explains important terms that may be new to an Oracle or Sybasedatabase administrator or to a NetBackup administrator.

NetBackupNetBackup backs up and restores files, directories, raw partitions,and databases on client systems that have Oracle or Sybasedatabases. The following lists some major features of NetBackup.

Automatic-scheduled backupsNetBackup schedules control NetBackup operations such as: whenbackups can occur, the type of backup to perform, and how longNetBackup retains the backup image (retention level).

Administrator-directed backupsNetBackup administrators are able to perform remote backups of allfiles, directories, databases, and raw partitions contained on clientsystems within a client/server network.

User-directed backups and restoresNetBackup client users are able to perform backups of all files,directories, databases, and raw partitions contained on clientsystems.

Graphical interfacesxbp (Motif) and Java interfaces are available for both users andadministrators.

Media ManagerThe Media Manager provides complete management and tracking ofall devices and media used during backups and restores.

SQL-BackTrackSQL-BackTrack manages backup and recovery functions of Oracle orSybase databases on UNIX systems. There are separate versions forOracle and Sybase. SQL-BackTrack must be installed on theNetBackup for SQL-BackTrack client.

SQL-BackTrack scriptThis script file specifies the action that SQL-BackTrack performs (forexample, backups and restores). Refer to “Create Scripts” on page 26for a detailed description of an SQL-BackTrack script.



Introduction 3

1

Features of NetBackup for SQL-BackTrackThis section describes the NetBackup for SQL-BackTrack main features.

Feature Description

Media and devicemanagement.

All devices supported by Media Manager are availableto NetBackup for SQL-BackTrack.

Scheduling facilities. NetBackup scheduling facilities on the master server canbe used to schedule automatic and unattended backups.This also lets you choose the times when theseoperations can occur. For example, to preventinterference with normal daytime operations, you canschedule your database backups to occur only at night.

Multiplexed backups andrestores.

NetBackup for SQL-BackTrack lets you take advantageof NetBackup’s multiplexing capabilities. Multiplexingdirects multiple data streams to one storage device,thereby reducing the time necessary to complete theoperation.

Transparent execution ofboth database andregular file systembackup and restoreoperations.

All backups and restores are executed simultaneouslyand transparently without any action from theNetBackup administrator.A database administrator can execute databaseoperations through NetBackup or use SQL-BackTrack asif NetBackup were not present.An administrator or any other authorized user can useNetBackup to execute database backups and restores.

Sharing the same devicesand tapes used duringother file backups.

It is possible to share the same devices and media usedfor other backups or to give SQL-BackTrack exclusiveuse of certain devices and media.

Centralized andnetworked backupoperations.

From the NetBackup master server, you can scheduledatabase backups or start them manually for any client.The databases can also reside on hosts that are differentfrom the devices on which NetBackup stores thebackups.




1

Graphical user interfaces. NetBackup provides the following graphical userinterfaces:• Client user interface on Motif, xbp• Administrator interface on Motif, xbpadm• Client user interface on Java, jbpSA• Administrator user interface on Java, jnbSAA database administrator or NetBackup administratorcan easily start an Oracle or Sybase backup or restoreoperation through the NetBackup client user interfaceon the client. The administrator can use the NetBackupadministrator utility for configuration and manualbackups.

Menu interface. NetBackup has two character-based menu interfaces forUNIX users without X Window capabilities. bp is forusers and bpadm is for administrators.

Parallel backup andrestore operations.

NetBackup for SQL-BackTrack supports the parallelbackup and restore capabilities of the SQL-BackTrack.This permits the user to run more than one tape deviceat a time for a single Oracle or Sybase backup or restore,thereby reducing the time necessary to complete theoperation.

Feature Description



Introduction 5

1

Technical Overview of NetBackup for SQL-BackTrackThe example network below shows the major components in a NetBackup forSQL-BackTrack configuration.

The storage devices are connected to the NetBackup master server. ANetBackup media server can access the storage devices through the masterserver. Both the master server and the media server must have NetBackupserver software installed.

The database host must also be a NetBackup client. NetBackup for SQL-BackTrack and SQL-BackTrack must also be installed on the NetBackup client.

Host marsOracle orSybase database

Host jupiter

NetBackupMaster-Server Installation

Tape or Optical

NetBackup for

SQL-BackTrack

NetBackupClient Installation

Network (TCP/IP)

DB

DB

to back up or restore

SQL-BackTrack

NetBackup database




1

How Does NetBackup for SQL-BackTrack Work?

SQL-BackTrack controls the data streams going into or out of the database anddirects the data to and from the desired backup device through an OBSI (OpenBackup Stream Interface) module.

The type of OBSI used depends upon the backup device. SQL-BackTrack hasOBSI modules for disk and tape. The NetBackup for SQL-BackTrack softwareincludes its own OBSI, called nb_obsi , that routes data between SQL-BackTrack and NetBackup.

The administrator specifies the desired OBSI in the SQL-BackTrack BackupProfile or Control directory (see the SQL-BackTrack User’s Guide). When usingNetBackup for SQL-BackTrack, the administrator specifies nb_obsi .

To schedule an automatic backup of a database, the administrator needs tocreate an SQL-BackTrack script with the commands for controlling databasebackup or recovery. For example, an SQL-BackTrack script to back up Oracle orSybase databases would have a dtobackup or dtsbackup command. Aseparate SQL-BackTrack script is needed for each type of operation. “CreateScripts” on page 26 has more information on these SQL-BackTrack scripts.

SQL-BackTrack nb_obsi

NetBackup

Database

bphdb xbp/bpscript

NetBackup

scheduler

NetBackup Master Server

NetBackup Client

OBSI

NetBackup forSQL-BackTrack

Command Line



Introduction 7

1

Sequence of Operation

NetBackup users or the scheduler start database backups or restores byselecting an SQL-BackTrack script. For scheduler started backups,

1. A NetBackup process called bphdb starts the SQL-BackTrack script on theclient.

2. The SQL-BackTrack application starts the requested operation on thedatabases.

3. The SQL-BackTrack application connects to nb_obsi .

4. nb_obsi issues a backup request.

5. nb_obsi sends data to the NetBackup server.

A restore works in essentially the same manner except that nb_obsi issues arestore request, causing the NetBackup master server to retrieve the data fromsecondary storage and send it to nb_obsi on the client.




1



9

Installation 2

If SQL-BackTrack or NetBackup are new to you, it is important to get themworking separately before attempting to use NetBackup for SQL-BackTrack.Install NetBackup server software on the NetBackup server. Also install theNetBackup client software on the client where you will be using NetBackup forSQL-BackTrack. Perform some test backups and restores with the NetBackupinstallations.

After installing and testing the NetBackup server software and the NetBackupclient software, install SQL-BackTrack on your machine. Perform some backupsand restores using SQL-BackTrack’s disk OBSI.

After installing and testing the NetBackup software and the SQL-BackTracksoftware, you can install NetBackup for SQL-BackTrack on the client whereyou will be backing up the databases. Refer to “Install NetBackup for SQL-BackTrack” on page 10 for more details.

For the Oracle or Sybase version level supported, refer to the readme fileprovided with the distribution package.




2

Install NetBackup for SQL-BackTrack1. Login as a root on your machine.

su root

If you are going to perform a local install of NetBackup for SQL-BackTrack,the client you log onto must have SQL-BackTrack software installed.

2. Mount the NetBackup for SQL-BackTrack CD-ROM.

3. Change your working directory to the CD-ROM directory.

cd /CD_mount_point

• If you have a Solaris NetBackup master server, go to Step 4.

• If you do not have a Solaris NetBackup master server:

go to Step 5 to install NetBackup for SQL-BackTrack directly onto aclient.

or

go to Step 6 to install NetBackup for SQL-BackTrack directly onto a non-Solaris NetBackup server for distribution to other clients.

4. Installing NetBackup for SQL-BackTrack with pkgadd on your NetBackupmaster server.

a. Execute the following.

pkgadd -d . SUNWnbtrk

This will place the Solaris SQL-BackTrack tar file in/usr/openv/netbackup/dbext .

b. If the NetBackup master server is also your NetBackup for SQL-BackTrack client then go to Step 9.

c. Use an ftp application to manually transfer the appropriate tar file and/usr/openv/netbackup/dbext/install_btr script into the/usr/openv/netbackup/dbext directory on each client where youwill be backing up databases.

d. Go to Step 7.

5. Local installation on the SQL-BackTrack client.



Installation 11

2

If you choose to install locally, the NetBackup for SQL-BackTrack files areextracted onto the local machine and you are prompted for configurationinformation.

a. Be sure you have logged on as root on the SQL-BackTrack client.

b. Execute the install script.

./install

Are you installing the database extension on this local machine? (y/n)

c. Answer y and follow the prompts for configuration information.

The following prompt will appear.

NetBackup Database Extensions Installation

Found packages to install NetBackup for

SQL-BackTrack

Do you want to install NetBackup for SQL-BackTrack? (y/n) y

d. Type y.

The script extracts NetBackup for SQL-BackTrack from the tar files andruns the installation scripts.

The installation script prompts you for your DTBASE directory.Assuming your $DTBASE directory is /usr/datatools , the scriptplaces the nb_obsi binary in this directory:

/usr/datatools/obsi.nb_obsi/bin/obsi

install_obsi also attempts to create a symbolic link from/usr/datatools/obacktrack/links/obsi.nb_obsi to/usr/datatools/obsi.nb_obsi .

See your SQL-BackTrack Installation Notes for more information on$DTBASE.

e. Go to the Configuration chapter.

6. Installing NetBackup for SQL-BackTrack with ./install on yourNetBackup master server.

a. Execute the following.

./install

The following prompt will appear.




2

Are you installing the database extension on this local machine? (y/n)

b. Answer n.

This will start the install process. The script will display the installationoptions.

Netbackup Database Extension Installation

Installation Options

Installing NetBackup for BACKTRACK

Platform

--------

1) HP

2) RS6000

3) SOLARIS

q To quit platform selection

Enter Platform Type:

c. Select your platform from the list. If you have more than one platform,reselect it.

d. Type q when you are finished selecting platform(s).

e. If the NetBackup master server is also your NetBackup for SQL-BackTrack client then go to Step 9.

f. Use an ftp application to manually transfer the appropriate tar file and/usr/openv/netbackup/dbext/install_btr script into the/usr/openv/netbackup/dbext directory on each client where youwill be backing up databases.

7. Log in as a root user on the client.

8. Meet the following prerequisites:

• NetBackup version 3.2 or later client software is installed andoperational. This also means that the /usr/openv/netbackupdirectory already exists on the client.



Installation 13

2

• Adequate disk space exists. Less than one megabyte of additional diskspace is required in the /usr/openv/netbackup directory. However,more disk space may be necessary at run time.

• Ensure that the /usr/openv/netbackup/dbext directory containsboth the install_btr script and the tar file for NetBackup for SQL-BackTrack.

9. Change your working directory to where the NetBackup for SQL-BackTracksoftware is located.

cd /usr/openv/netbackup/dbext

10. Execute the install script by typing:

./install_btr

The script will:

• Search the current directory for NetBackup for SQL-BackTrack tar files.If the script does not find NetBackup for SQL-BackTrack tar files in thecurrent directory, it prompts you as to where to find them.

• Prompt the user for the packages that you want to install.

NetBackup Database Extensions Installation

Found packages to install NetBackup for

SQL-BackTrack

Do you want to install NetBackup for SQL-BackTrack? (y/n) y

11. Type y.

The script extracts NetBackup for SQL-BackTrack from the tar files andruns the installation scripts.

The installation script prompts you for your DTBASE directory. Assumingyour $DTBASE directory is /usr/datatools , the script places thenb_obsi binary in this directory:

/usr/datatools/obsi.nb_obsi/bin/obsi

install_obsi also attempts to create a symbolic link from/usr/datatools/obacktrack/links/obsi.nb_obsi to/usr/datatools/obsi.nb_obsi .

See your SQL-BackTrack Installation Notes for more information on$DTBASE.




2

▼ Example

Installing NetBackup for SQL-BackTrack...

Extracting files from /usr/openv/netbackup/dbext/BACKTRACK.solaris.tar ...

x ./usr, 0 bytes, 0 tape blocks

x ./usr/openv, 0 bytes, 0 tape blocks

x ./usr/openv/netbackup, 0 bytes, 0 tape blocks

x ./usr/openv/netbackup/bin, 0 bytes, 0 tape blocks

x ./usr/openv/netbackup/bin/nb_obsi, 613940 bytes, 1200 tape blocks

x ./usr/openv/netbackup/bin/install_obsi, 5352 bytes, 11 tape blocks

Do you want to install nb_obsi under DTBASE directory /usr/datatools? (y/n) y

Using DTBASE directory /usr/datatools ...

Installing nb_obsi in /usr/datatools/obsi.nbobsi-3.2/bin/obsi dir ....

Linking /usr/datatools/obsi.nb_obsi to

/usr/datatools/obacktrack/links/obsi.nb_obsi dir ...

NetBackup for SQL-BackTrack installation completed.



15

Configuration 3

Before attempting to configure NetBackup for SQL-BackTrack, complete theinstallation procedure as described in Chapter 2, “Installation."

The following is the configuration procedure.

1. Configure the Media Manager.

2. Add DataTools-SQL-BackTrack Classes to NetBackup.

3. Set Maximum Jobs per Client Global Attribute.

4. Create Directories for Logs.

5. Create Scripts.

6. Configure NetBackup for SQL-BackTrack on the Client.

7. Test NetBackup for SQL-BackTrack Configuration Settings.

This chapter describes each of these steps in detail. This chapter also containsinstructions on “Parallel Backup Streams and Dump Striping” on page 34. Alsolook on page 35 for instructions on “Alternate Client Restore Configuration onthe Client.”




3

Configure the Media ManagerUse the Media Manager to configure tapes or other robotic drives for aNetBackup for SQL-BackTrack configuration.

• Refer to the Media Manager for NetBackup System Administrator’s Guide -UNIX if the NetBackup server is UNIX.

• Refer to the Media Manager for NetBackup System Administrator’s Guide -Windows NT Server if the NetBackup server is Windows NT.

• Refer to online help if the NetBackup server has a Java interface.



Configuration 17

3

Add DataTools-SQL-BackTrack Classes to NetBackupYou must add at least one DataTools-SQL-BackTrack class to NetBackup anddefine appropriate schedules for that class. You should be familiar with theNetBackup class configuration procedures as described in the NetBackup SystemAdministrator’s Guide - UNIX or NetBackup System Administrator’s Guide -Windows NT Server.

This section contains instructions specific to the NetBackup for SQL-BackTrackconfiguration. Most requirements for DataTools-SQL-BackTrack classes are thesame as for file system backups. The differences are defined in the followingsteps.

1. Log onto the master server as root.

2. Start the NetBackup xbpadm administrator interface.

• If you are using mwmand the DISPLAY variable is set, type:

/usr/openv/netbackup/bin/goodies/xbpadm &

• If you are using mwmand the DISPLAY variable is not set, use the -doption:

/usr/openv/netbackup/bin/goodies/xbpadm -d (your_machine_name):0 &

The NetBackup Administration dialog box will open.

3. On the Actions menu, select New, then Classes. The Creating a Class dialogbox will open.

a. In the Class Name box, type the new class name.

b. Under Select one of, select New Class. The Class Type list box will enable.

c. Select the DataTools-SQL-BackTrack class type from the list box.

d. Click OK. The Changing Class dialog box will open.

4. Verify that the Class Type attribute is set to DataTools-SQL-BackTrack.

5. Verify that the Active check box is selected.

6. Select a storage unit under Class Storage Unit.

7. Select a volume pool under Class Volume Pool.

8. Specify the clients in the Client list.




3

a. Click Clients to change the display.

b. Click New to open the Adding Clients dialog box.

c. Select the hardware and operating system from the Hardware and OperatingSystem scroll box.

d. Enter client names in the Client Name(s) pane. This list should include thenames of the clients which:

• Have the database

• Have NetBackup for SQL-BackTrack installed

• Are going to execute the backup or restore scripts

If there is more than one client in the DataTools-SQL-BackTrack class, theSQL-BackTrack scripts are executed on each client.

Note: The Install NetBackup Client Software checkbox will install NetBackupclient software on a remote client. You cannot use this option to installNetBackup for SQL-BackTrack software. Refer to the installation instructions inthis guide to install NetBackup for SQL-BackTrack.

e. Click OK.

9. Configure the Schedules.

The following types of backup are available in the DataTools-SQL-BackTrack class:

• Backup Policy

• Automatic Backup

▼ Backup Policy

A Backup Policy type of backup applies to a special type of user-directedbackup started on the client. At least one Backup Policy type of backup mustbe configured in each DataTools-SQL-BackTrack class. To help satisfy thisrequirement, a schedule named Default-Policy, configured with a BackupPolicy backup type, is automatically created.

The following describes how to configure a Backup Policy backup type inyour own schedule.

a. Click Schedules to change the display.



Configuration 19

3

b. Click New to open the Creating a Schedule dialog box.

c. In the Name of Schedule box, type the new schedule name.

d. Click OK. The Creating a Schedule dialog box will open.

e. Select Backup Policy for Type of Backup.

f. For Retention Period, set to 9 (infinite).

SQL-BackTrack keeps a backup history in its control directories orprofiles. When it is time to expire a backup, SQL-BackTrack sends adelete request to NetBackup. In this way SQL-BackTrack controls theexpiration of the backups.

g. For Schedule Times, set the time of day during which you want thebackup to occur.

A Backup Policy schedule must encompass all of the time periods duringwhich NetBackup for SQL-BackTrack must be able to start backups. Thiswill include:

• Times when user-directed backups can occur.

• Start times and durations of Automatic Backup type of backup (if youhave created any). This is necessary because the Backup Policy type ofbackup starts processes that are required for all NetBackup for SQL-BackTrack backups, including those started automatically.

For example, assume that automatic backups can start between 2200and 0600. In this case, the schedule must include a Backup Policy typeof backup with schedule times from 2200 through 0600.

Hint: Set the time period for the Backup Policy type of backup for 24 hours perday, seven days per week. This will ensure that your NetBackup for SQL-BackTrack operations are never locked out due to the Backup Policy type ofbackup.

▼ Automatic Backup

An Automatic Backup specifies the scheduled dates and times whenNetBackup for SQL-BackTrack will start automatic backups by running theSQL-BackTrack scripts.

Since all the SQL-BackTrack scripts execute during automatic backups, youmay need a separate DataTools-SQL-BackTrack class for each type ofbackup you want to execute automatically on the same database. For




3

example, to perform automatic full backups and partial backups of thesame database, two different SQL-BackTrack scripts are required. If you putboth SQL-BackTrack scripts in the same DataTools-SQL-BackTrack class,NetBackup for SQL-BackTrack will execute both of them during eachAutomatic Backup session for that DataTools-SQL-BackTrack class.

The following describes how to create an Automatic Backup type of schedule.

a. Click Schedules to change the display.

b. Click New to open the Creating a Schedule box.

c. In the Name of Schedule box, type the new schedule name.

d. Click OK. The Creating a Schedule dialog box will open.

e. For Type of Backup, select Automatic Backup.

CAUTION! The settings for Retention Period and Frequency are significantlydifferent for database extensions than they are for other NetBackup class types.Please review the following two steps carefully.

f. For the Retention Period, set a time period which is longer than thefrequency setting for the schedule. For example, if the frequency settingis set to one week, then set the retention period to be more than oneweek. If the frequency is set to 36 weeks, then you will have to set theretention period to 8 (one year).

The retention period for an Automatic Backup type of backup controlshow long NetBackup keeps records of when scheduled backups haveoccurred.

The NetBackup scheduler compares the latest recorded scheduledbackup to the frequency setting to determine whether a backup is due.This means that if you set the retention period to expire the record tooearly, the scheduled backup frequency will be unpredictable. If you setthe retention period to be longer than necessary, the NeBackup databasewill accumulate uncecessary records.

g. For the Frequency, set the time period you want to wait between backups.

h. For the Schedule Times, set the time of day during which you wantbackups to occur.



Configuration 21

3

10. Configure the File list.

A class File list has scripts which define the operations to be performed oneach database. The File list can have multiple scripts and each script canhave multiple SQL-BackTrack commands. When a NetBackup user orschedule starts a backup or restore operation, NetBackup for SQL-BackTrack on the client starts the designated SQL-BackTrack script.

a. Click Files.

b. Click New.

c. Specify an SQL-BackTrack script in the File list if unattended scheduledbackups are going to be performed. Otherwise this step can be skipped.

d. List the SQL-BackTrack scripts that reside on the clients.

Always specify the full path name for an SQL-BackTrack script in the filelist. The scripts will run in the order in which they are listed in the Filelist.

Note: The SQL-BackTrack scripts must be installed on each machine in theclient list.

Refer to “Create Scripts” later in this chapter for details on creating an SQL-BackTrack script.

CAUTION! NetBackup for SQL-BackTrack does not check the type of scriptbeing executed. Therefore, it is important to ensure that persons configuringautomatic backups or starting operations through NetBackup use the correctscript name or the wrong operation could be performed.

11. Click OK.

The Changing Class dialog box will close. The NetBackup Administrationdialog box will remain open.




3

▼ Example DataTools-SQL-BackTrack Class

The following shows attributes and schedules for a typical DataTools-SQL-BackTrack class.

Note that:

• The class type is set to DataTools-SQL-BackTrack.

• The retention level is infinite (DataTools-SQL-BackTrack will control imageexpiration) for Backup Policy backups.

• There are no settings shown for Follow NFS and Cross Mount Pointsbecause, for DataTools-SQL-BackTrack class, NetBackup always sets them toNo.

• The window for the Backup Policy schedule encompasses the window for theAutomatic Backup schedule.

This example shows a disk type storage unit. You may want to use a diskstorage unit as the residence for initial testing because of its simplicity andspeed.



Configuration 23

3

Class Name: sql_bt_1

Class Type: DataTools-SQL-BackTrackActive: yesClass Priority: 0Max Jobs/Class: 99Residence: disk1Volume Pool: NB_duplicates

Client List: SQLSYB10 HP9000-700 HP-UX

File List: backup.sh

Schedule: user_directedType: Backup PolicyMaximum MPX: 2Retention Level: 9 (infinite)Residence: (specific storage unit not required)Volume Pool: (same as class volume pool)Daily Windows:

Sunday 00:00:00 --> Sunday 24:00:00Monday 00:00:00 --> Monday 24:00:00Tuesday 00:00:00 --> Tuesday 24:00:00Wednesday 00:00:00 --> Wednesday 24:00:00Thursday 00:00:00 --> Thursday 24:00:00Friday 00:00:00 --> Friday 24:00:00Saturday 00:00:00 --> Saturday 24:00:00

Schedule: fullType: Automatic BackupFrequency: every 7 daysRetention Level: 3 (one month)Daily Windows:

Sunday 18:00:00 --> Sunday 20:00:00Monday 18:00:00 --> Monday 20:00:00Tuesday 18:00:00 --> Tuesday 20:00:00Wednesday 18:00:00 --> Wednesday 20:00:00Thursday 18:00:00 --> Thursday 20:00:00Friday 18:00:00 --> Friday 20:00:00Saturday 18:00:00 --> Saturday 20:00:00




3

Set Maximum Jobs per Client Global AttributeFrom the NetBackup Administration dialog box, select File, then ChangeNetBackup Configuration. The NetBackup Configuration dialog box willappear.

Use the following rule to figure the Maximum Jobs per Client global attributevalue.

Max Jobs per Client = Number of Streams x Number of Classes

Where:

• Number of Streams is the number of backup streams between the databaseserver and NetBackup server. Each separate stream starts a new backup jobon the client.

• Number of Classes is the number of classes that may back up this client at thesame time. This number can be greater than one. For example, a client maybe in two classes in order to back up two different databases. These backupwindows may overlap.

▼ Example

Assume that a client belongs to two classes and both backup windows areopen at the same time. Also assume that the database backup is configured tostart five parallel backup data streams on the NetBackup client.

Therefore:

Max Jobs per Client = 5 x 2= 10

This setting allows the client to perform ten backup jobs at the same time.



Configuration 25

3

Create Directories for LogsEnable the bphdb log and the nb_obsi log by performing the following steps.

1. Create the following directories on the client:

/usr/openv/netbackup/logs/bphdb/usr/openv/netbackup/logs/ nb_obsi

% cd /usr/openv/netbackup/logs% mkdir bphdb% mkdir nb_obsi

2. Set the access permissions to 777 on these log directories.

% chmod 777 bphdb% chmod 777 nb_obsi




3

Create ScriptsThe SQL-BackTrack script contains SQL-BackTrack commands that controldatabase backup and restore operations. SQL-BackTrack scripts are usedduring unattended scheduled backups, or when a user initiates a backupthrough xbp (bp).

CAUTION! Always specify the correct SQL-BackTrack script when configuringautomatic backups or when starting operations through NetBackup.NetBackup for SQL-BackTrack will not generate an error if a restore SQL-BackTrack script file is used for a backup operation or a backup SQL-BackTrackscript is used for a restore operation.

A separate script is required for each backup or restore operation. For example,you need separate scripts for backups and restores. SQL-BackTrack scripts canbe located anywhere on the same client where NetBackup for SQL-BackTrack isinstalled. The database administrator responsible for configuring databasebackups normally creates the SQL-BackTrack scripts.

You can use SQL-BackTrack to generate the SQL-BackTrack scripts. Beforeusing SQL-BackTrack scripts with NetBackup for SQL-BackTrack, be sure to setthe Oracle or Sybase to superuser by including an su - user (where user isOracle or Sybase).

Note: If you do not include an su - user (user is Sybase or Oracle) in yourSQL-BackTrack scripts, the scripts will not run with the proper permissionsand environmental variables. As a result, you will not be able to performNetBackup operations.

#!/bin/shdate > /tmp/date.out.1su - oracle -c "/usr/datatools/obacktrack/bin/dtobackup /home8/profiles/ora7/IDS_TS"



Configuration 27

3

SQL-BackTrack for Sybase Example

Assume, you log in as user sybase in order to do backups of Sybase serverSQLSYB. This Sybase server has two databases: db1 and db2. The SQL-BackTrack control files for db1 and db2 are:

/home8/obsi_ctrl_dir/SQLSYB/db1

/home8/obsi_ctrl_dir/SQLSYB/db2

You can manually back up database db1 of this server by running thiscommand:

You can manually back up database db2 of this server by running thiscommand:

The host that has the Sybase SQL server SQLSYBand SQL-BackTrack installedis also a NetBackup client. After testing these backups manually, you decide touse NetBackup to automatically execute these two commands every night.

1. Create SQL-BackTrack scripts named script1 and script2 on yourNetBackup client as below.

script1:

script2:

You could also combine script1 and script2 into one SQL-BackTrackscript.

/usr/datatools/sbacktrack/bin/dtsbackup /home8/obsi_ctrl_dir/SQLSYB/db1

/usr/datatools/sbacktrack/bin/dtsbackup /home8/obsi_ctrl_dir/SQLSYB/db2

#!/bin/shdate > /tmp/date.out.1su - sybase -c "/usr/datatools/sbacktrack/bin/dtsbackup /home8/obsi_control_dir/SQLSYB/db1"

#!/bin/shdate > /tmp/date.out.2su - sybase -c "/usr/datatools/sbacktrack/bin/dtsbackup /home8/obsi_control_dir/SQLSYB/db2"




3

2. Perform the following procedure on the NetBackup master server.

a. Create a DataTools-SQL-BackTrack class with a Backup Policy schedule asexplained earlier in this chapter.

b. Create the file list for your DataTools-SQL-BackTrack class as:

/export/home8/sybase/script1

/export/home8/sybase/script2

c. Add a Automatic Backup schedule to your DataTools-SQL-BackTrack classand set the backup window to open at the desired time:

NetBackup will run these SQL-BackTrack scripts (script1 , thenscript2 ) when your Automatic Backup window opens.

3. To enable activity logging create the following directories on the client.

/usr/openv/netbackup/logs/bphdb

/usr/openv/netbackup/logs/nb_obsi

NetBackup will now print useful debugging information to logs in thesedirectories. The log messages will originate from bphdb and nb_obsi .

The filenames for these logs will use the following format:

log. mmddyy

where

mm is the month: 01 through 12

dd is the dat: 01 through 31

yy is the year: 99, 00, 01 and so on

An example of a log would be

log.082799

Standard output and standard error from your SQL-BackTrack scripts willbe written to files with names like bt_stdout.082799 andbt_stderr.082799 respectively in the/usr/openv/netbackup/logs/bphdb directory.



Configuration 29

3

SQL-BackTrack for Oracle Example

The procedure for an Oracle database would be the same as for the Sybaseexample, except for the SQL-BackTrack scripts and path names. The followingis an example of an SQL-BackTrack script for an Oracle database backup.

#!/bin/shdate > /tmp/date.out.1su -oracle -c "/usr/datatools/obacktrack/bin/dtobackup hom e8/profiles/ora7/IDS_TS"




3

Configure NetBackup for SQL-BackTrack on the ClientThere are a number of ways to specify NetBackup attributes for NetBackup forSQL-BackTrack. The class, server, and schedule can be specified throughenvironment variables, SQL-BackTrack Backup Pool Information, a userbp.conf file, or a master bp.conf file. The NetBackup for SQL-BackTrackwill search for CLASS, SERVER, and SCHEDULE in the following order:

1. Environment Variables

2. SQL-BackTrack Backup Pool Information

3. User bp.conf

4. Master bp.conf

If you do not specify the class or schedule by any of the above methods, theNetBackup server uses the first appropriate class and schedule that it finds forthe client.

Environment Variables

Set the following environment variables in your Sybase or Oracle environment.

$BACKTRACK_SERVName of the NetBackup server

$BACKTRACK_CLASSName of the NetBackup class

$BACKTRACK_SCHEDName of the Backup Policy schedule

SQL-BackTrack nb_obsi Backup Pool Configuration

The SQL-BackTrack backup pool stores information about the backup deviceand its options. When you have created the DataTools-SQL-BackTrack class,define an SQL-BackTrack backup pool that uses nb_obsi on the client. Use anSQL-BackTrack program such as obacktrack or sbacktrack when youcreate your Profiles or Control directories. See your SQL-BackTrackdocumentation for details.



Configuration 31

3

---------------------------------------------------------------

DEFINE BACKUP POOL INFORMATION

A backup pool directs backup data to a particular device. Youcan define one or more backup pools in a profile directory. Todefine the backup pool, you enter a name for the pool. (If youdo not enter a name, the name “default” is used.) Then, youchoose the backup device from the list of available OBSIdevices. The device options presented depend on the OBSI deviceyou selected.

Enter backup pool name[return=’default’]: xxxx

Backup pool name is ‘xxxx’

Available OBSI backup devices:

disk, nb_obsi, tape

Enter the OBSI backup device type: nb_obsi

Enter NetBackup class for this pool? sql_bt_1

....

Here, the NetBackup class is the DataTools-SQL-BackTrack class that you havedefined on the NetBackup server.

Modify the SQL-BackTrack Backup Pool Information to add the followingoptions:

class Name of the NetBackup class

sched Name of the Automatic Backup schedule

serv Name of the NetBackup server

For example:

--------------- Backup Pool Information ---------------

begin backup_pool=default

obsi=nb_obsi

class=sql_bt_1

sched=user_direct

serv=venus

end backup_pool

------------ End of Backup Pool Information ------------

Is this correct (y/n/edit)?




3

Configure the bp.conf Files

A NetBackup for SQL-BackTrack user can create bp.conf file in the $HOMEdirectory on the NetBackup for SQL-BackTrack client host. When a NetBackupfor SQL-BackTrack operation is started the Oracle user $HOME/bp.conf file orthe Sybase user $HOME/bp.conf file is searched before the masterconfiguration file (/usr/openv/netbackup/bp.conf ) on the client. Anyoption found at the user level takes precedence over the same option in themaster level configuration.

The following option can be set in the user configuration file or the masterconfiguration file:

BPBACKUP_CLASSThis option specifies the name of the class to use for the SQL-BackTrack backup.

BPBACKUP_SCHEDThis option specifies the name of the schedule to use for the SQL-BackTrack backup.

CLIENT_NAMEThis option specifies the name of the NetBackup for SQL-BackTrackclient

CLIENT_READ_TIMEOUTThis option specifies the number of seconds the NetBackup for SQL-BackTrack client will initially wait for response from the NetBackupserver. The CLIENT_READ_TIMEOUT must be set to a value greaterthan 900 seconds to be used in NetBackup for SQL-BackTrack.Otherwise the default value is 900 seconds.

SERVERThis option specifies the name of NetBackup master server.

VERBOSEThis option causes NetBackup to include more information in itslogs. The larger value between the user and master configuration filewill determine logging information.

See NetBackup System Administrator’s Guide - UNIX for more details and defaultvalues.



Configuration 33

3

Test NetBackup for SQL-BackTrack Configuration SettingsThe following procedure describes how to test configuration settings on aUNIX NetBackup master server.

1. Log onto the master server as root.

2. Start the NetBackup administration interface.

• If you are using mwmand the DISPLAY variable is set, type:

/usr/openv/netbackup/bin/goodies/xbpadm &

• If you are using mwmand the DISPLAY variable is not set, use the -doption:

/usr/openv/netbackup/bin/goodies/xbpadm -d your_machine_name:0 &

The NetBackup Administration dialog box will open.

3. Under Classes, select the DataTools-SQL-BackTrack class you configured.

4. Under Actions, select Manual Backup. The Manual Backup dialog box willappear.

a. Select a schedule in the Schedules pane.

b. Select a client in the Clients pane.

c. Click OK. The Manual Backup dialog box will close.

5. Under File, select Job Monitor. The Job Monitor dialog box will appear. Astatus code will display in the Status column.

Refer to the NetBackup Troubleshooting Guide - UNIX or the NetBackupTroubleshooting Guide - Windows NT Server for a description of status codes.




3

Parallel Backup Streams and Dump StripingNetBackup for SQL-BackTrack supports parallel backup streams for Oracledatabases and dump striping for Sybase databases. Refer to the SQL-BackTrackmanuals for instructions on configuring Profiles for parallel backup streamsand Control directories for dump striping.

The following are some special considerations for dump striping of Sybasebackups.

Note: Dump striping of sybsystemprocs database is not supported in thisrelease.

• A Sybase restriction with multiple streams is that ALL the streams must besimultaneously available before the dump or load can proceed. Also, thenumber of stripes specified during a load must match that of the dump.

• An SQL-BackTrack restriction is that when you recover the databases, youmust use the same stripe devices that you used for the backups. Forexample, if you striped to five devices, you must recover from those samefive devices.

If you are multiplexing striped Sybase database backups, you may require aspecial configuration to restore them. By default, when restoring frommultiplexed backups, Media Manager uses 12 data buffers. This is enoughunless you are using more than 6 stripes.

Each stripe requires at least two data buffers. Therefore, if you are using morethan 6 stripes, you must increase the number of data buffers used by MediaManager. Do this as follows:

1. Create the following file on the NetBackup master or media server that hasthe storage unit:

/usr/openv/netbackup/db/config/NUMBER_DATA_BUFFERS_RESTORE

2. Specify the number of buffers. For example:

20

This number will be the only entry in the file.



Configuration 35

3

Alternate Client Restore Configuration on the ClientIf you want to browse and restore backups that are owned by another client,perform the following:

1. Ensure that the NetBackup server is configured to allow the alternate clientrestore (see the NetBackup System Administrator’s Guide - UNIX or theNetBackup System Administrator’s Guide - Windows NT Server).

2. Specify the client name with the CLIENT_NAME option in the$HOME/bp.conf or /usr/openv/netbackup/bp.conf file on the client.For example, the following command specifies saturn as the client tobrowse:

CLIENT_NAME=saturn




3



37

Using NetBackup for SQL-BackTrack 4

When all installation and configuration is complete, you can use theNetBackup interfaces to perform Oracle or Sybase backups and restores withSQL-BackTrack.

This chapter contains the following sections:

• Performing a Backup

• Performing a Restore

• Performing Other SQL-BackTrack Actions

CAUTION! Always specify the correct SQL-BackTrack script when configuringautomatic backups or when starting operations through NetBackup (see“Configure the File list.” on page 21). NetBackup for SQL-BackTrack will notgenerate an error if a restore SQL-BackTrack script file is used for a backupoperation or a backup SQL-BackTrack script is used for a restore operation.




4

Performing a Backup

Automatic Backup of a DataTools-SQL-BackTrack Class

The most convenient way to back up your database is to set up schedules forautomatic backups. When the NetBackup scheduler invokes a schedule for anautomatic backup, the SQL-BackTrack scripts run:

• In the same order as they appear in the File list

• On all clients that have them (that is, matching path names)

The SQL-BackTrack scripts will start the database backup.

To add a new schedule or change an existing schedule for automatic backups,follow the guidelines in Step 9 “Configure the Schedules.” on page 18.

Manual Backup of a DataTools-SQL-BackTrack Class

The administrator on the master server can use the NetBackup server softwareto manually execute an Automatic Backup schedule for the DataTools-SQL-BackTrack class. See the NetBackup System Administrator’s Guide - UNIX or theNetBackup System Administrator’s Guide - Windows NT Server for detailedinstructions.

User-Directed Backup

If you know the pathname of the SQL-BackTrack script that describes thebackup, you can start a user-directed backup through the NetBackup client-user interface on the client (xbp , bp). After you select the SQL-BackTrack scriptand start the backup, NetBackup executes the SQL-BackTrack script.

For example, to perform a full database backup, the path to the script could be:

$HOME/db_backup.full

NetBackup starts the database backup by executing the shell script file. Thescript file contains SQL-BackTrack commands to execute dtsbackup ordtobackup commands.




4

Using the SQL-BackTrack Interface to Backup

You can start backups directly from the SQL-BackTrack interfaces(obacktrack or sbacktrack ).

Using xbp to Back Up

The following describes how to use xbp to back up your database. Refer to theNetBackup User’s Guide - UNIX for detailed instructions on using xbp .

1. Log in as the Oracle or Sybase administrator or as root.

You cannot back up a database from a remote machine. Be sure to log ontothe machine which you are going to back up.

2. Execute xbp on the client with the database you want to backup. Thefollowing will appear.

3. Type in the path name of the location of the SQL-BackTrack scripts in theDirectory To Search Box box. For example:




4

/db/exb/backtrack/sybase/scripts

4. From the File menu, click Browse File System for SQL-BackTrack BackupScripts.

5. Select the backup script from the Files pane.

6. On the Backup menu, click Backup Database Using Selected Script.

7. Click OK.

A NetBackup process called bphdb will start the SQL-BackTrack script onthe client.

8. View the log file for the NetBackup for SQL-BackTrack operation.

a. Change directories to the nb_obsi log directory.

cd /usr/openv/netbackup/logs/nb_obsi

b. Open the log file with the tail option.

tail -f log.mmddyy

A backup completed SUCCESSFULLY message indicates asuccessfully completed NetBackup operation.




4

Using bp to Back Up

The following describes how to use bp to back up your database. Refer to theNetBackup User’s Guide - UNIX for detailed instructions on using bp to back up.


2. Execute bp on the client machine. The following will appear.

3. Select the B (Backup...) option. The following will appear.




4

4. Select the T (Backup SQL-BackTrack DB...) option from the Backup Menu.The following will appear.

Note: You can return to the Backup Menu at any time, up to starting theoperation, by pressing the Escape key.

a. Check the Path field at the top of the menu. Set the path to the directorywhere you want to start the search for the desired files. At start-up,NetBackup sets Path to your current working directory. For this databasebackup, you need to change the path to:


5. Select the files and directories you want to back up.




4

a. Select the S (Select Scripts...) option from the Backup SQL-BackTrack DBMenu. The following will appear.

b. Use the menu options at the bottom of the screen to move the displayarrow to the line with the script.

c. Choose the <S>elect option to select the backup script. An asterisk (*)will appear to the left of the selected file.

d. Select the <O>k option to return to the Backup SQL-BackTrack DB Menu.

6. Preview the scripts you have selected.

a. Select the E (Edit/View Selected Scripts...) option from the Backup SQL-BackTrack DB Menu. The following will appear.

b. Make sure the backup script appears in the list.

c. Select the <O>k option to return to the Backup SQL-BackTrack DB Menu.

7. Start the backup operation.




4

a. Select the I (Initiate Backup...) option from the Backup SQL-BackTrackDB Menu. The following will appear.

b. Type Y to create a log file and write to this file as the operationprogresses. The following will appear.

If you do not want logging, type N to start the operation.

c. Press Enter to accept the default (shown in parentheses), or type a newpath and press Enter. The operation begins when you press Enter. Thefollowing will appear.

d. Press any key to return to the Backup SQL-BackTrack DB Menu.

8. Select the Q (Quit Menu) option to return to the Main.




4

Performing a RestoreAll restores must be started from the NetBackup for SQL-BackTrack client. Youcannot execute restore operations from the server.

Prior to the execution of a restore, a backup must have been successfullycompleted or an error will occur during the execution.

Restores can be performed by using:

• SQL-BackTrack User InterfaceWe strongly recommend that you use SQL-BackTrack interface to recoveryour database.

• xbp

• bp

Using SQL-BackTrack User Interface to Restore

You can use SQL-BackTrack interfaces (obacktrack or sbacktrack ) toperform the restores.

Using xbp to Restore

The following describes how to use xbp to restore your database. Refer to theNetBackup User’s Guide - UNIX for detailed instructions on using xbp to restore.


You cannot restore a database from a remote machine. Be sure to log ontothe machine to which you are going to restore a backup.




4

2. Execute xbp on the client to which you want to restore a database. Youcannot restore a database to a remote machine. The following will appear.

3. In the Directory to Search Box, type in the path name of the location of theSQL-BackTrack scripts. For example:





4

4. From the File menu, click Browse File System for SQL-BackTrack RestoreScripts.

5. Select the restore script from the Files pane.

6. On the Restore menu, click Restore Database Using Selected Script.

7. Click OK.

A NetBackup process called bphdb starts the SQL-BackTrack script on theclient.

8. View the log file for the NetBackup operation.

a. Change directories to the nb_obsi log directory.

cd /usr/openv/netbackup/logs/nb_obsi

b. Open the log file with the tail option.

tail -f log.mmddyy

A restore completed SUCCESSFULLY message indicates asuccessfully completed NetBackup operation.




4

Using bp to Restore

The following describes how to use bp to restore your database. Refer to theNetBackup User’s Guide - UNIX for detailed instructions on using bp to restore.

NetBackup restores files according to the original file path name. If currentfiles have the same names as backed up files, you can pick whether tooverwrite the current files (file permissions must allow overwriting).


If a different user account is used, change the su- command to the Oracleor Sybase administrator.

2. Execute bp on the client machine. The following will appear.

3. Choose the R (Restore...) option from the Main. The following will appear.




4

4. Select the T (Restore From SQL-BackTrack DB Backups...) option. Thefollowing will appear.

Note: You can return to the Restore Menu at any time, up to starting theoperation, by pressing the Escape key.

Check the Path field at the top of the Restore SQL-BackTrack DB Menu. Setthe path to the directory where you want to start the search. At start-up, thecurrent path is set to the directory from which you start the interfaceprogram. For database restores, you need to change the path to where thedatabase scripts are located. For example:

/usr/openv/netbackup/ext/db_ext/backtrack

5. Select the script file you want to execute.




4

a. Choose the S (Select Scripts...) option from the Restore SQL-BackTrackDB Menu to search for files and directories that belong to the client andmeet the path and date criteria. The following will appear.

b. Use the menu options at the bottom of this screen to move the displayarrow to the line with the restore script.




4

c. Choose the <S>elect option to select the restore script. An asterisk (*) willappear to the left of the selected script.

d. Select the <O>k option to return to the Restore SQL-BackTrack DB Menu.

6. Preview the scripts you have selected.




4

a. Choose the E (Edit/View Selected Scripts...) option from the RestoreSQL-BackTrack DB Menu. The following will appear.

b. Make sure the restore script appears in the list.

c. Select the <O>k option to return to the Restore SQL-BackTrack DB Menu.

7. Select the I (Initiate Restore...) option from the Restore SQL-BackTrack DBMenu.

d. Type Y.

Use progress log? (y/n) (y): will appear.

e. Type Y to create a log file and write to this file as the operationprogresses.

Press any key to continue will appear.

f. Press any key to return to the Restore SQL-BackTrack DB Menu. Therestore operation will begin.




4

Performing Other SQL-BackTrack ActionsTo call SQL-BackTrack scripts for database operations other than backups orrestores, use SQL-BackTrack directly. Do not use NetBackup.




4



55

Troubleshooting 5

NetBackup, NetBackup for SQL-BackTrack, and the SQL-BackTrack all providereports on database operations. These reports are useful for finding errorsassociated with those applications.




5

NetBackup InstallationIf SQL-BackTrack or NetBackup are new to you, it is important to get themworking separately before attempting to combine them. Refer to “Installation”on page 9 for detailed instructions to correctly install the software.

For the Oracle or Sybase version level supported, refer to the readme fileprovided with the distribution package.

NetBackup ReportsThe NetBackup server and client software allow you to set up detailed activitylogs for troubleshooting problems that occur outside of either NetBackup forSQL-BackTrack or the SQL-BackTrack. See the NetBackup Troubleshooting Guide -UNIX or the NetBackup Troubleshooting Guide - Windows NT Server for acomplete description of activity logs. Also see the/usr/openv/netbackup/logs/README.debug file.

Note: These logs do not reveal errors that occur during the execution of theSQL-BackTrack, unless those errors also affect NetBackup for SQL-BackTrack.Your best sources for Oracle or Sybase error information are the logs providedby the Oracle or Sybase.

The /usr/openv/netbackup/logs/nb_obsi directory contains thefollowing execution log.

log. mmddyyThis log contains detailed execution information for the nb_obsiprocess. For example, on a backup you can check that the correctDataTools-SQL-BackTrack class, schedule and server are beingspecified when nb_obsi issues a backup request.

The /usr/openv/netbackup/logs/bphdb directory contains the followingtypes of logs.

bt_stdout .mmddyyNetBackup places SQL-BackTrack script output in this file.

bt_stderr. mmddyyNetBackup places SQL-BackTrack script errors in this file.



Troubleshooting 57

5

log. mmddyybphdb is the NetBackup Hot Database Backup binary. NetBackup forSQL-BackTrack uses the client process for SQL-BackTrack scriptexecution. It is invoked when an Automatic Backup schedule is run,or when xbp , and bp are used for a user directed backup or restore.

NetBackup Client Reports

For a user-directed backup or restore performed through the NetBackup client-user interface, the progress report indicates whether the SQL-BackTrack scriptwas able to complete its part of the operation. You can easily view the progressreport from xbp or a file editor such as vi .

NetBackup Server Reports

NetBackup provides other reports that are useful in isolating problems. Onesuch report is All Logs Entries on the server. See the NetBackup SystemAdministrator’s Guide - UNIX or the NetBackup System Administrator’s Guide -Windows NT Server for a description of this and other reports.




5

Other NetBackup Activity Logs

The NetBackup server and client software allow you to set up detailed activitylogs for troubleshooting problems that occur outside of either NetBackup forSQL-BackTrack or the SQL-BackTrack application.

Enable these NetBackup activity logs by creating the appropriate directoriesunder:

/usr/openv/netbackup/logs

on the server or client. See the NetBackup Troubleshooting Guide - UNIX orNetBackup Troubleshooting Guide - Windows NT Server for a complete descriptionof NetBackup activity logs.

You can also use dtwatch and/or debug flags if you encounter errors during abackup or restore.

dtwatch

Use the dtwatch command to check the status of currently active and recentlycompleted SQL-BackTrack programs. This is also how you determine theultimate success or failure of a database backup or restore. See the SQL-BackTrack User’s Guide for instructions on using dtwatch .

If you see problems with a backup or restore, check the NetBackup logs formore information. You can also re-execute the operation with the debug flags(see “Debug Flags below).

Debug Flags

A good way to get more information about the SQL-BackTrack portion of theoperation is to add the -debug/-DEBUG flags to the dtobackup anddtorecover commands (for Oracle) or dtsbackup and dtsrecover (forSybase). After adding the flags, execute the command (either manually) or inan SQL-BackTrack script and monitor the debug messages. If you modify theSQL-BackTrack scripts that NetBackup uses, be certain to delete the flags whenyou are through troubleshooting.

For information on using these commands, see the SQL-BackTrack User’s Guide.



59

Index

AActivity logs

description, 56, 58Administrator-directed backups

definition, 2feature, 3

Attributeconfiguration, 17

Automatic backupclass, 38schedule

bphdb log, 57configuration, 20manual backup, 38

Automatic-scheduled backupsdefinition, 2executing scripts, 19feature, 3file list, 21

BBackup

automaticusing scripts, 38

Backup Policy scheduleautomatic backups, 19configuration, 18

Backupssee also Automatic backups

user directedwith bp, 41with xbp, 39

bpbackup procedure, 41restore procedure, 48

bphdb log, 56, 57, 58Browse

bp menu options, 43

CClass

attribute, 17Automatic Policy schedule, 19Backup Policy schedule, 18client list, 17example, 22file list, 21type of backup, 19

Clientprogress report, 57

Configurationdatabase class, 17media manager, 16testing, 33troubleshooting logs, 25



60 NetBackup for DataTools SQL-BackTrack System Administrator’s Guide - UNIX

DDefault-Policy schedule

Backup Policy schedule, 18example, 22

Device sharing, 3Directory

bppath field, 42, 49selecting to backup, 43

xbpdirectory to search, 46

EError

information, 56script name, 26

Examplesclass, 22

Execution log, 56

FFile list

configuration, 21Frequency, 20Full backup, 2

retention period, 19

GGraphical user interface, 4

IIncremental backup

automatic-scheduled backups, 2Install

NetBackup client software, 18

LLogs

error, 56troubleshooting, 56, 58

MManual Backup, 38Master server

configure class, 17operations, 3

Media Manager, 16definition, 2features, 3

Menu interface, 4Multiplexing, 3

NNetBackup

definition, 2

PPath

bpchange after a backup is intiated,

44change for a backup, 42change for a restore, 49

xbpto search for backup scripts, 39to search fro restore scripts, 46

Permissionbp file permissions for restore, 48

Progress reports, 57

RReports

database operations, 55Restore



Index 61

user directedwith bp, 48with xbp, 45

Retention PeriodAutomatic Policy schedule, 20

SSchedule

automatic backup, 20, 38Scripts

executing, 19scheduler, 38

Simultaneous operations, 3

TTransparent operations, 3Troubleshooting logs, 56, 58

UUser-directed backup, and restore

definition, 2

Xxbp

backup procedure, 39restore procedure, 45



62 NetBackup for DataTools SQL-BackTrack System Administrator’s Guide - UNIX



Date post:	20-Mar-2018
Category:	Documents
Upload:	lamphuc
View:	225 times
Download:	1 times