Professional Documents
Culture Documents
Veritas Netbackup For Informix Administrator'S Guide
Veritas Netbackup For Informix Administrator'S Guide
Administrators Guide
for UNIX
Release 6.5
Veritas NetBackup for Informix
System Administrators Guide
Copyright 2007 Symantec Corporation. All rights reserved.
NetBackup 6.5
Symantec, the Symantec logo, and NetBackup are trademarks or registered trademarks of
Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be
trademarks of their respective owners.
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.
The product described in this document is distributed under licenses restricting its use,
copying, distribution, and decompilation/reverse engineering. No part of this document
may be reproduced in any form by any means without prior written authorization of
Symantec Corporation and its licensors, if any.
Symantec Corporation
Cupertino, CA 95014
www.symantec.com
Technical support
For technical assistance, visit http://entsupport.symantec.com and select phone
or email support. Use the Knowledge Base search feature to access resources
such as TechNotes, product alerts, software downloads, hardware compatibility
lists, and our customer email notification service.
Contents
Chapter 1 Introduction
NetBackup for Informix features ........................................................................ 7
Chapter 3 Configuration
User interface terminology notes .....................................................................27
Chapter 5 Troubleshooting
Troubleshooting tips ........................................................................................... 55
Index 63
Chapter 1
Introduction
This chapter contains the following topics:
NetBackup for Informix features on page 7
NetBackup for Informix terminology on page 9
NetBackup for Informix overview on page 9
Sequence of operation on page 11
NetBackup for Informix integrates the database backup and recovery
capabilities of the Informix ON-Bar utility with the backup and recovery
management capabilities of NetBackup and its media manager.
This chapter introduces NetBackup for Informix, and it explains how NetBackup
for Informix relates to both the Informix ON-Bar utility and to NetBackup.
Feature Description
Media and device All devices supported by Media Manager are available to
management NetBackup for Informix.
8 Introduction
NetBackup for Informix features
Feature Description
Scheduling facilities NetBackup scheduling facilities on the master server can be used
to schedule automatic and unattended Informix backups.
This also lets you choose the times when these operations can
occur. For example, to prevent interference with normal daytime
operations, you can schedule your database backups to occur only
at night.
Multiplexed backups NetBackup for Informix lets you take advantage of NetBackups
and restores multiplexing capabilities. Multiplexing directs multiple data
streams to one backup device, thereby reducing the time necessary
to complete the operation.
Sharing the same It is possible to share the same devices and media used for other
storage units used backups or to give Informix exclusive use of certain devices and
for other file media. NetBackup for Informix can use Media Manager, disk, and
backups PureDisk storage units.
Centralized and From the NetBackup master server, you can schedule database
networked backup backups or start them manually for any client. The Informix
operations databases can also reside on hosts that are different from the
devices on which NetBackup stores the backups.
Graphical user NetBackup provides the following graphical user interfaces for
interfaces client users and administrators:
NetBackup administration console for Java
NetBackup administration console for Windows
A database administrator or NetBackup administrator can start
backup or restore operations for Informix from the NetBackup
graphical user interface on the master server.
Parallel backup and NetBackup for Informix supports the parallel backup and restore
restore operations capabilities of the Informix ON-Bar utility. For example, this
permits the user to run more than one tape device at a time for a
single Informix backup or restore, thereby reducing the time
necessary to complete the operation.
Introduction 9
NetBackup for Informix terminology
Feature Description
Term Meaning
Informix ON-Bar utility The Informix ON-Bar utility allows database administrators to back up and
restore Informix databases on UNIX systems. This utility, however, does not
directly manage storage devices and media. The Informix ON-Bar utility
must be integrated with a media management system that can access
devices and keep information about the media used in Informix database
backups. NetBackup for Informix provides this media-management
capability by integrating the utility with NetBackup.
onbar The onbar command starts a backup or restore with the Informix ON-Bar
utility. This command is described in the IBM Informix Backup and Restore
Guide.
onsmsync The onsmsync utility is an Informix version XPS 8.x, IDS 9.x, and later
feature that synchronizes the NetBackup catalog with the Informix backup
catalog. The onsmsync utility deletes images from both Informix backup
catalogs and NetBackup catalogs. For more information, see your IBM
Informix documentation.
be a NetBackup client, and it must have NetBackup for Informix and the
Informix ON-Bar utility installed.
Network (TCP/IP)
NetBackup software:
NetBackup Master Server
NetBackup Media Server
(if system is a media server)
The onbar command is documented in the IBM Informix Backup and Restore
Guide.
Sequence of operation
You can run an ON-Bar script in one of the following ways:
Automatically, from the NetBackup scheduler
From the NetBackup administration interface on the NetBackup master
server
From the command line on the NetBackup client
With the exception of the command line method, a NetBackup process named
To verify compatibility
2 From the Product Lookup list, choose NetBackup Enterprise Server and
click on the > button.
3 From the list on the right, click on Compatibility List.
4 In the list of documents, click Veritas NetBackup Enterprise Server (tm) x.x/
NetBackup Server x.x Database Agent Compatibility (Updated date).
For x.x, look for the current release. For date, look for the most recent date.
For information on supported cluster environments for NetBackup for
Informix, see NetBackup (tm) x.x Cluster Compatibility (updated date).
14 Installing the agent
Verifying the installation prerequisites
5 Click the link for the PDF document, which is a downloadable file that
enables you to view the supported database spreadsheet for this release.
6 Read the document and verify that the software in your environment is
compatible with the NetBackup and the database agent.
NetBackup software
Verify that the following requirements are met for the NetBackup server and
client software:
The NetBackup server software is installed and operational on the
NetBackup server.
The NetBackup server platform can be any that NetBackup supports. For
installation information, see the NetBackup Installation Guide.
The NetBackup client software is installed on the client that has the
databases you want to back up.
The version of the NetBackup client and the version of the database agent
you want to install must be the same (for example, 6.5).
There must be adequate disk space on each machine upon which you want to
install the database agent. Less than two megabytes of additional disk space
is required in the /usr/openv/netbackup directory. However, more disk
space might be needed at run time.
Make sure that you configure any backup media that the storage unit uses.
The amount of backup media that is required depends on the devices that
are used, the sizes of the databases that you want to back up, the amount of
data that you want to archive, the size of your backups, and the frequency of
backups or archives.
For information on using Media Manager, see the NetBackup
Administrators Guide, Volume I.
Database software
Verify the following regarding the database software on the NetBackup client:
Informix vendor software must be installed and operational.
One or more Informix instances must exist.
Cluster software
Verify the following requirements if you are installing the database agent
software on a NetBackup server configured in a NetBackup cluster:
Installing the agent 15
Installing NetBackup for Informix
procedure.
4 Verify that a registered and valid license key for NetBackup for Informix
resides on the master server.
You can obtain master server license information from either the master
server or the media server. To view or add license keys, perform one of the
following actions:
From the master server or media server, run the following command:
/usr/openv/netbackup/bin/admincmd/get_license_key
When the system prompts you, type the host name of the NetBackup
master server.
Open the NetBackup administration console and choose Help > License
Keys.
If the NetBackup master server is part of a NetBackup cluster, the license
key must be registered on each node.
5 Mount the CD-ROM.
For more information on how to mount a CD-ROM, see the NetBackup
Installation Guide.
6 Change the working directory to the CD-ROM directory.
For example:
cd /CD_mount_point
b Type n.
c Select the NetBackup for Informix option.
d Type q to quit selecting options.
e Type y.
The install script identifies the types of client software that is loaded
during the installation of the NetBackup server. By default, any
matching NetBackup for Informix software is automatically loaded. If
there are more platforms available, the script displays a menu that
gives you the opportunity to add more client types to the default list.
After the list is complete, the installation script copies the database
agent version files and the install_dbext script to directory
/usr/openv/netbackup/dbext. (These files are tar(1) files
compressed with gzip(1).)
8 (Conditional) Select another node upon which to install the software.
Perform this step under the following circumstances:
If you want to install the NetBackup for Informix software on a server
that is part of a NetBackup cluster.
and
If you have any nodes that still need the software installed.
If there are any inactive nodes that do not yet have the software installed,
select one of these inactive nodes. Then repeat step 3 through step 8 for
that node.
If you installed the software on all the inactive nodes, select the active node
10 Decide how you want to distribute the NetBackup for Informix software to
the clients.
Use one of the following methods whether you want to upgrade clients in an
existing environment or you want to perform a new installation:
Distribute to all clients currently specified in the database policy. This
method distributes the NetBackup for Informix software to all clients
that are currently included in the database policy. You can use this
method only if you want to push from a master server.
For information on this method, see Pushing the software to all
clients on page 18.
Distribute to selected clients. This method distributes the NetBackup
for Informix software to selected clients only. If you want to perform a
new installation and you plan to add clients to a database policy after
you install the software. You can install the software on such clients
now and configure the policy later. This method also allows you to skip
any clients that you do not want to upgrade to 6.5 at this time. You can
use this method whether you want to push from a master server or
from a media server.
For information on this method, seePushing the software to new or
selected clients on page 21.
Note: Make sure that the NetBackup for Informix version is the same version as
the NetBackup client software.
Note: If you want to push the database agent software from a server that is part
of a NetBackup cluster, type all commands in this procedure from the active
NetBackup node.
Note: If you want to push the database agent software from a server that is part
of a NetBackup cluster to an inactive node in the cluster, you need to force the
installation to the inactive node.
Installing the agent 19
Installing NetBackup for Informix
The database agent software for that client type was not loaded
onto the server. (In the procedure To load the database agent files
on a UNIX server on page 16.)
The client does not belong to the database policy type.
The skipped client list is in $TMPDIR/skipped_clients.PID,
where PID is the process identifier. The TMPDIR environment
variable is defined as /tmp. If no file is present, no clients were
skipped.
3 (Conditional) Specify the number of simultaneous client updates.
If you want to update more than one client, the installation software
displays the number of updates that are required to distribute the software
to the clients. If the software detects the need to update more than one
client, it displays the following prompt:
Enter the number of simultaneous updates you wish to take place.
max The maximum number of simultaneous updates that is allowed. The value
that is displayed ranges from 1 to 30.
dflt The number the program uses if you press Enter without specifying a
number. The value that is displayed ranges from 1 to 15.
Note: If you want to push the NetBackup for Informix software from a server
that is part of a NetBackup cluster, type all commands in this procedure from
the active NetBackup node.
Note: If you want to push the database agent software from a server that is part
of a NetBackup cluster to an inactive node in the cluster, you need to force the
installation to the inactive node.
1 On the master server, type the following command to ensure that the bpdbm
daemon is running:
/usr/openv/netbackup/bin/bpps
If the output shows that the bpdbm daemon is not running, type the
following command to start the daemon:
/usr/openv/netbackup/bin/initbpdbm
The options for this command depend on whether you want to install from a
If you want to perform the install from the master server, type the
following command:
./admincmd/bpplclients -allunique -noheader > file
If you want to perform the install from a media server, type the
following command:
./admincmd/bpplclients -allunique -noheader -M ms_name > file
file Name of the file to contain the list of unique clients. If no clients have
been configured in the NetBackup database, file is empty. Create
file using the same format as that generated by bpplclients.
hardware The hardware name. For examples, type the ls(1) command in
directory /usr/openv/netbackup/client.
op_system The operating system name. For examples, type the ls(1) command
in directory /usr/openv/netbackup/client/hardware.
For example:
Note: You do not need to run the cluster_config script after you install the
database agent on a server that is part of a NetBackup cluster.
If you are already logged in, but are not the root user, run the following
command.
su - root
You can obtain master server license information from either the master
server or the media server. To view or add license keys, perform one of the
following actions:
From the master server or media server, type the following command:
/usr/openv/netbackup/bin/admincmd/get_license_key
When the system prompts you, type the host name of the NetBackup
master server.
Open the NetBackup administration console and choose Help > License
Keys.
If the NetBackup master server is part of a NetBackup cluster, the license
key must be registered on each node.
6 (Conditional) Log out of the media server or master server and return to the
local client.
Perform this step if you logged into a media server or the master server in
step 4 to verify the license.
7 Mount the CD-ROM.
For more information on how to mount a CD-ROM, see the NetBackup
Installation Guide.
8 Change the working directory to the CD-ROM directory.
For example:
cd /CD_mount_point
Note: Make sure that the NetBackup for Informix version is the same version as
the NetBackup client software.
b Type y.
A menu of all database agents available on the CD-ROM appears.
c Select the NetBackup for Informix option.
d Type q to quit if you do not want to select other options.
A prompt appears that asks if the list is correct.
e Type y.
The following actions occur:
The script writes the version file, a tar(1) file compressed with
gzip(1), and the install_dbext script to directory
/usr/openv/netbackup/dbext.
The install script automatically runs the install_dbext script.
If install_dbext completes successfully, it writes a version file
in directory /usr/openv/share that contains the version of
NetBackup for Informix that was installed.
f Type q to quit from the script.
Note: You do not need to run the cluster_config script after you install
NetBackup for Informix on a server that is part of a NetBackup cluster.
If there are any inactive nodes that do not yet have the software installed,
select one of these inactive nodes. Then repeat step 3 through step 10 for
that node.
If you installed the software on all the inactive nodes, select the active node
and repeat step 3 through step 10 for that node.
After you install NetBackup for Informix, use the procedure in this section to
provide additional information about your Informix environment.
3 Supply the appropriate name for the Informix instance home path.
The command finishes, and the set-up step is complete.
4 Verify the Informix ON-Bar configuration.
This script creates the following entry in the Informix instance home paths
etc/sm_versions file for each client.
1|1.1.0|Veritas-NetBackup|1
All Informix versions later than 7.31 UC4 dynamically read the appropriate
information from the sm_versions file every time a backup or restore is
performed. If you are using a release at this level, you do not need to edit
any files.
If you are using Informix version 7.31 UC4 and earlier, perform step 5.
5 (Conditional) Update the bar_version table in the sysutils database.
Perform this step if you are using Informix version 7.31 UC4 and earlier.
Insert the following lines into the bar_version table in the sysutils
database:
bar_version bsa_version bar_sm sm_version
1 1.1.0 Veritas-NetBackup 1
The following procedure shows how to set the Maximum jobs per client
attribute.
number_of_policies The number of policies of any type that can back up this
client at the same time. This number can be greater than
one. For example, a client can be in two policies in order
to back up two different databases. These backup
windows can overlap.
Tip: Enter a large enough value for the Maximum jobs per client attribute to
meet the number of jobs that Informix runs. You might need to experiment with
different values at your site.
Standard policy with a User Backup schedule type to back up these files.
Most requirements for database policies are the same as for file system backups.
In addition to the policy attributes for this database agent, other attributes are
3 If your site has more than one master server, choose the one on which you
want to add the policy.
4 From the Windows interface: In the left pane, right-click Policies and choose
New Policy.
From the Java interface: In the left pane, click Policies. In the All Policies
5 In the Add a New Policy dialog box, in the Policy name field, type a unique
name for the new policy.
6 Click OK.
7 In the Add a New Policy or Change Policy dialog box, in the Policy type list,
select the Informix-ON-Bar policy type.
The database agent policy type does not appear in the drop-down list unless
your master server has a license key for the database agent.
8 Complete the entries on the Attributes tab.
For more information, see Description of attributes, which follows this
procedure.
9 Add other policy information.
30 Configuration
Configuring a backup policy for a database
Description of attributes
With a few exceptions, NetBackup manages a database backup like a file system
backup. Table 3-3 shows the policy attributes that are different for Informix
Other policy attributes vary according to your specific backup strategy and
system configuration.
Guide, Volume I.
Attribute Description
Policy type Determines the types of clients that can be in the policy. In some
cases the policy type determines the types of backups that
NetBackup can perform on those clients. To use the database
agent, you must define at least one policy of type that is
Informix-ON-Bar.
Keyword phrase For NetBackup for Informix, the Keyword phrase entry is ignored.
Adding schedules
Each policy has its own set of schedules. These schedules initiate automatic
backups and specify when a user can initiate operations. A database backup has
two types of schedules: Application Backup and Automatic Backup.
Backup Window The time during which a NetBackup Sunday through Saturday
operation can be initiated.
00:08:00 - 22:00:00
Note: (Optional) Specify the Application Backup schedule name in the bp.conf
file on the client. See Configuring an additional bp.conf file on page 42 for
details.
32 Configuration
Configuring a backup policy for a database
Automatic Full Retention The length of time to store the record of a 2 weeks
Backup backup, which NetBackup uses to
determine if the schedule needs to be run.
6 If this schedule is the last schedule, click OK. To add other schedules, repeat
step 1 through step 6.
Configuration 33
Configuring a backup policy for a database
Application Backup The Application Backup schedule enables user-controlled NetBackup operations from
the client. These operations include those initiated from the client and those initiated
by an automatic schedule on the master server. NetBackup uses the Application Backup
schedule when the user starts a backup manually. Configure at least one Application
Backup schedule for each database policy. The Default-Application-Backup schedule is
configured automatically as an Application Backup schedule.
Automatic Full Backup An Automatic Full Backup copies all blocks into the backup set. It skips only the data file
blocks that have never been used. Note that a full backup is not the same as a whole
database backup; full is an indicator that the backup is not incremental.
This type of backup corresponds to an Informix Level-0 backup, which is a baseline
backup.
Automatic Incremental An Automatic Incremental Backup is a backup of only those blocks that have changed
Backup since the last Automatic Full (baseline) backup. This kind of backup takes less time and
space than a full backup because the Automatic Incremental Backup contains only the
changed data.
This type of backup corresponds to an Informix Level-1 backup.
Schedule properties
Some of the schedule properties have a different meaning for database backups
than for a regular file system backup. Table 3-7 explains the schedule
properties.
Property Description
Type of backup Specifies the type of backup that this schedule controls. The
selection list shows only the backup types that apply to the policy
you want to configure.
For more information, see Types of backup schedules on page 33.
34 Configuration
Configuring a backup policy for a database
Property Description
Frequency This setting is used only for scheduled backups and not for
user-directed backups. Frequency specifies the period of time that
can elapse until the next backup or archive operation begins on this
schedule. For example, assume that the frequency is seven days and
a successful backup occurs on Wednesday. The next full backup does
not occur until the following Wednesday. Typically, incremental
backups have a shorter frequency than full backups.
Calendar This setting is used only for scheduled backups. It is not used for
user-directed backups. The Calendar option allows you to schedule
backup operations that are based on specific dates, recurring week
days, or recurring days of the month.
Multiple copies If you want to specify multiple copies of a backup for the policy,
configure Multiple copies on the Application Backup schedule.
Other schedule properties vary according to your specific backup strategy and
system configuration. For more information on schedule properties, consult the
NetBackup Administrators Guide, Volume I.
Configuration 35
Configuring a backup policy for a database
Adding clients
The client list is the list of clients on which your ON-Bar scripts are run during
an automatic backup. A NetBackup client must be in at least one policy but can
be in more than one.
For a database policy, clients you want to add must have the following software
installed:
Informix
NetBackup client or server
NetBackup for Informix
The backup or restore ON-Bar script(s)
list contains files and directories to be backed up. In a database policy, you
specify scripts to be run.
Caution: Be sure to specify the correct script names in the backup selections list
to prevent an error or possibly a wrong operation. Make sure that the script
resides on the client before you try to add it to the backup selections list.
To add scripts to the backup selections list from the Java interface
1 Open the Policy dialog box.
To access the Policy dialog box, double-click the policy name in the Policies
list in the NetBackup administration console.
2 Click the Backup Selections tab.
3 Click New.
4 Specify the names of the scripts that you want NetBackup to use.
a In the Script: box, type the full path name of a script on the client.
Configuration 37
Configuring a backup policy for a database
For example:
/backup_scripts/db/cold_backup.sh
To add scripts to the backup selections list from the Windows interface
1 In the Policy dialog box, click the Backup Selections tab.
To access the Policy dialog box, double-click the policy name in the Policies
list in the NetBackup administration console.
2 Click New.
3 Specify the names of the scripts you want NetBackup to use.
Use one of the following methods:
Type the full path name of the script on the client.
For example:
/backup_scripts/db/cold_backup.sh
Note: The name of the policy must be specified in the backup scripts you modify
on the client.
d In the Start Window section of the Schedules dialog, set the time of day
when you want backup operations to be available to the user.
Set this window to the same time periods as the Application Backup
schedule in the Informix-ON-Bar policy.
Note: You do not need to configure a file list for this policy because it will be a
User Backup type schedule.
Creating scripts
The NetBackup for Informix installation software includes the following
example scripts:
informix_dbspace_list
informix_logical_log_backup
informix_onbar_backup_of_dbspace1
informix_onbar_backup_of_rootdbs
informix_onbar_backup_of_rootdbs_and_dbspace1
informix_onbar_backup_using_file_list
informix_onbar_restore_dbspace1
informix_onbar_restore_rootdbs
infx_remove_expired_backup
The installation software writes these scripts to the following directory:
/usr/openv/netbackup/ext/db_ext/informix/scripts
Configuration 39
Creating scripts
Although each script can perform multiple ON-Bar operations, each type of
operation requires a separate script. For example, you need separate scripts for
Caution: Always specify the correct script when configuring automatic backups
or when starting operations through NetBackup. NetBackup for Informix does
not generate an error if a restore script is used for a backup operation or a
backup script is used for a restore operation.
#!/bin/sh
# Replace xxxxx below with the extention used for your onconfig file.
ONCONFIG=onconfig.xxxxx
INFORMIXDIR=/yyyyy/informix
INFORMIXSERVER=zzzzz
# Replace informix_etc below with the name of the NetBackup server policy
INFX_ETC_POLICY=informix_etc
export ONCONFIG
export INFORMIXDIR
export INFORMIXSERVER
RETURN_STATUS=0
if [ "${INFXBSA_INCR}" = "1" ]
then
$INFORMIXDIR/bin/onbar -b -L 1 rootdbs
RETURN_STATUS=$?
else
$INFORMIXDIR/bin/onbar -b -L 0 rootdbs
RETURN_STATUS=$?
fi
then
Configuration 41
Creating scripts
BPBACKUP_STATUS=$?
then
echo ""
fi
fi
echo ""
exit $RETURN_STATUS
Environment variables
When a schedule runs, NetBackup sets environment variables for the local shell
scripts to use when performing the backup. The echo lines are used to show
what Informix environment variables are available.
You can use the Informix environment variables in the following lists to
perform conditional functions inside the scripts. These variables are local to the
Informix shell script.
NetBackup sets the following variables:
The Informix user can set the following variables either in the script or
manually from the command line in the same environment from which onbar is
issued:
BPBACKUP_SCHED=informix_sched
SERVER=server_name
CLIENT_READ_TIMEOUT=1800
Configuration 43
Testing configuration settings
NetBackup uses the bp.conf file in the Informix users home directory only for
backups and restores initiated by this Informix user.
Caution: Always specify the correct ON-Bar script when configuring automatic
backups or when starting operations through NetBackup. NetBackup for
Informix does not generate an error if a restore ON-Bar script file is used for a
backup operation or a backup ON-Bar script is used for a restore operation.
Performing a backup
The Informix ON-Bar utility supports four different types of backups. Table 4-8
on page 45 describes each backup type briefly.
Level 0 backup (Full) An Informix level 0 backup is a full backup. It includes all the
records in the selected dbspaces. This is the only type of backup
that allows a complete restore without performing any recovery
steps.
46 Using NetBackup for Informix
Performing a backup
Level 2 backup An Informix level 2 backup backs up records that have changed
since the last Level 1 Backup in the selected dbspaces. NetBackup
does not support this type of backup with an equivalent automatic
schedule. You can perform level 2 backups by writing a script and
by keeping track of the previous backup type with the ON-Bar
script.
Logical-log backup An Informix logical-log backup backs up the logical logs that have
filled. By using the Informix ALARMPROGRAM configuration
option, these backups can be started on demand when the logical
logs fill.
Backup strategy
The backup strategy in the following example is for a database that requires
frequent backups in order to provide protection against disk failure. This
strategy is as follows:
1 Perform an Informix full backup (level 0) every Friday night.
This backs up the selected dbspaces.
2 Perform an Informix incremental backup (level 1) each night.
3 Back up the $INFORMIXDIR/etc directory once a day.
The sample scripts that NetBackup for Informix installs by default include
parameters to back up the $INFORMIXDIR/etc directory after each full or
incremental backup.
4 Configure the Informix ALARMPROGRAM to start a logical-log backup as the
logs fill.
If you do not want to wait for log files to fill, you can set up a separate
often as necessary.
follow the guidelines in Configuring a backup policy for a database on page 28.
Browsing backups
Use the bplist command to browse the Informix backup history on the master
server. The result is the list of dump file names. The following example assumes
that the root user issued the bplist(1M) command from the NetBackup master
server in order to search all Informix backups for a client named cabbage:
bplist -C cabbage -t 6 -R /legohead
/legohead/0/18
/legohead/0/17
/legohead/0/17
/legohead/rootdbs/0
/legohead/0/17
/legohead/0/17
/legohead/0/17
/legohead/0/16
/legohead/rootdbs/0
Performing a restore
The following procedure explains how to restore your database to the level of
your last full or partial backup plus all transactions through the last
incremental. It includes steps for recovering all of your files.
To perform a restore
1 Salvage the logical-log files before replacing any disks that have failed.
Use the following command:
onbar -l -s
cd $INFORMIXDIR/etc
/usr/openv/netbackup/bin/jbpSA &
4 Use onbar to logically restore the dbspaces that you physically restored.
For example:
onbar -r -l
A logical log contains records of all the database activity that occurs
between backups. These records contain all the database transactions
that have taken place after the last backup.
Log into the source client as Informix ownerId and issue the following
command:
onbar -b -l
b If the source client database server is down, salvage the logical logs.
This command backs up any logical logs that have not yet been backed
up and are not corrupted or destroyed.
Log into the source client as Informix ownerId and issue the following
command:
onbar -l -s
3 Shut down the Informix database server on both the source client and the
destination client.
Issue one of the following commands:
For Informix Dynamic Server:
onmode -ky
4 On the NetBackup for Informix destination client, back up the files that
reside in the $INFORMIXDIR/etc directory to preserve the original
configuration. The following steps overwrite files in this directory.
5 Copy configuration and informational files in the $INFORMIXDIR/etc
directory from the NetBackup for Informix source client to the
$INFORMIXDIR/etc directory on the NetBackup for Informix destination
client.
You can use ftp(1) to copy files from the source client to the destination
client.
a Copy the emergency or backup boot files.
For the Informix Dynamic Server, the emergency boot file is
$INFORMIXDIR/etc/ixbar.servernum.
For the Extended Parallel Server, the backup boot file is
$INFORMIXDIR/etc/Bixbar_hostname.servernum.
For servernum, specify the value of the SERVERNUM configuration
parameter specified in the $INFORMIXDIR/etc/$ONCONFIG file.
b Copy the connectivity information file,
$INFORMIXDIR/etc/sqlhosts, that specifies how the client
application finds and connects to an Informix Database Server.
Using NetBackup for Informix 51
Performing a restore
Perform this step if the NetBackup master server used for the source
client backup is different than the server specified in the bp.conf file
on the destination.
You salvaged the logical logs on camel by using the following command:
onbar -l -s
onconfig
oncfg_destdb.0
This step is needed only if the first server specified in the bp.conf file on
giraffe is not lion.
8 Browse the file system backups from camel and restore the following files
to $INFORMIXDIR/etc on giraffe:
ixbar.6
54 Using NetBackup for Informix
Performing a restore
sqlhosts
onconfig
oncfg_destdb.6
9 Perform the redirected restore to giraffe.
a Perform the physical restore:
onbar -r -p
Troubleshooting tips
Refer to this section and to your Informix documentation when you
troubleshoot NetBackup for Informix. The following sections describe things
you should verify when you encounter problems.
commands:
onmode -uky
oninit
xctl -C oninit
4 Make sure the table bar_version in the sysutils database has the
correct value for the bar_version column. It should be 1.1.0 for
Informix 7.3 or later.
5 (Optional) Verify that you are using the correct library.
Perform this step if you are using NetBackup for Informix on an IBM AIX
platform.
Depending on your release of IBM AIX, verify the following:
Informix 7.3 and later releases require file infxbsa.so instead of
infxbsa.a.
Informix 7.2 uses infxbsa.a.
You can use the ar(1) command to extract infxbsa.so from infxbsa.a if
necessary.
/usr/openv/netbackup/logs/infxbsa
backup and restore session. NetBackup writes the other log files on a daily
basis. Log files in the log directories have the naming convention of
For example, the bprd log file shows if a backup or restore request from
as client name, policy type, client type, and backup file name.
NetBackup server and the NetBackup client during backups and restores.
/usr/openv/netbackup/logs/user_ops/dbext/logs/6749.0.1115233002
/usr/openv/netbackup/logs/infxbsa directory.
58 Troubleshooting
NetBackup reports
</usr/openv/netbackup/logs/user_ops/dbext/logs/6749.0.1115233002>
NetBackup reports
The NetBackup server and client software allow you to enable detailed
debugging logs. The information in these log files can help you troubleshoot
problems that occur outside of either the database agent or the Informix ON-Bar
utility.
Note the following with regard to these logs:
These logs do not reveal errors that occur when Informix ON-Bar utility is
running unless those errors also affect NetBackup. Informix might (or might
not) write to the NetBackup logs for errors in the application. Your best
sources for Informix error information are the logs provided by Informix.
Generally, each debug log corresponds to a NetBackup process and
executable.
For information about the debugging log files, see the NetBackup
Troubleshooting Guide and the
/usr/openv/netbackup/logs/README.debug file.
Enabling logging
To enable the database agent logs
/usr/openv/netbackup/logs/bpbackup
/usr/openv/netbackup/logs/bpbkar
/usr/openv/netbackup/logs/bphdb
/usr/openv/netbackup/logs/bprestore
/usr/openv/netbackup/logs/tar
/usr/openv/netbackup/logs/infxbsa
Troubleshooting 59
NetBackup reports
For example:
cd /usr/openv/netbackup/logs
mkdir bphdb
3 Enable logging for the nbpem, nbjm, and nbrb scheduling processes, which
use unified logging.
NetBackup writes unified logs to /usr/openv/logs. You do not need to
create log directories for processes that use unified logging. For
information on using logs and reports, see the NetBackup Troubleshooting
Guide.
When this script runs, it creates files in the /tmp directory. These files are not
removed. Later, they can be used to diagnose any problems that occur.
62 Troubleshooting
Deleting expired backups from the Informix backup database
Index
A log 59
bplist command 47
backup window 31
configuring 31
browsing backups 47
environment variables 41
overview 31, 33
retention 31
C
automatic backup
client list
create scripts 39
for installation 19
manual backup 47
client read timeout property 60
policy 47
cluster software prerequisites 14
schedules, configuring 32
cluster_config script 15, 23, 25
bpplclients 15, 22
B get_license_key 16, 24
initbpdbm 21
install_dbext 21, 25
adding selections 36
overview 35
onmsync 9
backups
compatibility information 13
configuration
logical log 46
manual 43
Media Manager 14
ON-Bar types 45
BAR_DEBUG variable 56
accessing 59
BAR_DEBUG_LOG variable 56
enabling 58
BAR_RETRY parameter 26
in /usr/openv/netbackup/logs 57, 58
bar_version table 26
troubleshooting with log files 58
bp.conf
debugging level 60
administrator 61
client 42
overview 42
E
bpdbm daemon 21
environment variables 41
bphdb
error
64
script name 39
overview 8
multi-streamed backups 61
G
get_license_key command 16, 24
N
nbjm scheduling process 59
I
nbpem scheduling process 59
INFORMIXDIR/etc directory 37
O
infxbsa library 26
ON-Bar
initbpdbm command 21
also see onbar command
installation
overview 10
local 23
utility
platform compatibility 13
overview 9, 10
prerequisites 13
script 9
prerequisites in a cluster 14
onbar command
remote 15
overview 9, 10
performing restore 48
sequence of operation 11
Java interface 27
OnBAR debug log 57
L onsmsync utility 9, 61
log files
attributes 30
BAR_ACT_LOG 11
for databases 29
enabling 58
Informix-On-BAR 29
logs
schedules 30
OnBAR 57
Standard 37
testing 43
M processes
manual backups 47
bpdbm 21
Media Manager
scheduling (nbpem, nbjm, nbrb) 59
65
redirected 49
user directed 48
retention period
for frequency-based schedules 34
robust logging 59
S
schedules
adding 30
automatic backup 47
frequency 34
properties 33
retention 34
types of schedules 30
scripts
cautions regarding usage 39
cluster_config 15, 23, 25
examples 38
install 17, 24
modifying 39
ON-Bar 9
scheduler 47
type of operation 39
skipped clients 19
sysutils database 26
T
testing policy configuration 43
timeout failures, minimizing 60
U
unified logging 59
update_dbclients command 15, 19, 22, 23
W
Windows interface 27
66