0% found this document useful (0 votes)
55 views

Symantec Netbackup™ For Informix Administrator'S Guide: For Unix and Linux

Uploaded by

Dmitriy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
55 views

Symantec Netbackup™ For Informix Administrator'S Guide: For Unix and Linux

Uploaded by

Dmitriy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 67

Symantec NetBackup™ for

Informix Administrator's
Guide

for UNIX and Linux

Release 7.5
Symantec NetBackup™ for Informix Administrator's
Guide
The software described in this book is furnished under a license agreement and may be used
only in accordance with the terms of the agreement.

Documentation version: 7.5

Legal Notice
Copyright © 2012 Symantec Corporation. All rights reserved.

Symantec, Veritas, NetBackup and the Symantec Logo 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.

This Symantec product may contain third party software for which Symantec is required
to provide attribution to the third party (“Third Party Programs”). Some of the Third Party
Programs are available under open source or free software licenses. The License Agreement
accompanying the Software does not alter any rights or obligations you may have under
those open source or free software licenses. Please see the Third Party Legal Notice Appendix
to this Documentation or TPIP ReadMe File accompanying this Symantec product for more
information on the Third Party Programs.

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.

THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS,
REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT,
ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO
BE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL
OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING,
PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED
IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.

The Licensed Software and Documentation are deemed to be commercial computer software
as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19
"Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights in
Commercial Computer Software or Commercial Computer Software Documentation", as
applicable, and any successor regulations. Any use, modification, reproduction release,
performance, display or disclosure of the Licensed Software and Documentation by the U.S.
Government shall be solely in accordance with the terms of this Agreement.
Symantec Corporation
350 Ellis Street
Mountain View, CA 94043

http://www.symantec.com
Technical Support
Symantec Technical Support maintains support centers globally. Technical
Support’s primary role is to respond to specific queries about product features
and functionality. The Technical Support group also creates content for our online
Knowledge Base. The Technical Support group works collaboratively with the
other functional areas within Symantec to answer your questions in a timely
fashion. For example, the Technical Support group works with Product Engineering
and Symantec Security Response to provide alerting services and virus definition
updates.
Symantec’s support offerings include the following:
■ A range of support options that give you the flexibility to select the right
amount of service for any size organization
■ Telephone and/or Web-based support that provides rapid response and
up-to-the-minute information
■ Upgrade assurance that delivers software upgrades
■ Global support purchased on a regional business hours or 24 hours a day, 7
days a week basis
■ Premium service offerings that include Account Management Services
For information about Symantec’s support offerings, you can visit our Web site
at the following URL:
www.symantec.com/business/support/
All support services will be delivered in accordance with your support agreement
and the then-current enterprise technical support policy.

Contacting Technical Support


Customers with a current support agreement may access Technical Support
information at the following URL:
www.symantec.com/business/support/
Before contacting Technical Support, make sure you have satisfied the system
requirements that are listed in your product documentation. Also, you should be
at the computer on which the problem occurred, in case it is necessary to replicate
the problem.
When you contact Technical Support, please have the following information
available:
■ Product release level
■ Hardware information
■ Available memory, disk space, and NIC information
■ Operating system
■ Version and patch level
■ Network topology
■ Router, gateway, and IP address information
■ Problem description:
■ Error messages and log files
■ Troubleshooting that was performed before contacting Symantec
■ Recent software configuration changes and network changes

Licensing and registration


If your Symantec product requires registration or a license key, access our technical
support Web page at the following URL:
www.symantec.com/business/support/

Customer service
Customer service information is available at the following URL:
www.symantec.com/business/support/
Customer Service is available to assist with non-technical questions, such as the
following types of issues:
■ Questions regarding product licensing or serialization
■ Product registration updates, such as address or name changes
■ General product information (features, language availability, local dealers)
■ Latest information about product updates and upgrades
■ Information about upgrade assurance and support contracts
■ Information about the Symantec Buying Programs
■ Advice about Symantec's technical support options
■ Nontechnical presales questions
■ Issues that are related to CD-ROMs, DVDs, or manuals
Support agreement resources
If you want to contact Symantec regarding an existing support agreement, please
contact the support agreement administration team for your region as follows:

Asia-Pacific and Japan [email protected]

Europe, Middle-East, and Africa [email protected]

North America and Latin America [email protected]


Contents

Technical Support ............................................................................................... 4


Chapter 1 Introduction to NetBackup for Informix ........................... 9
Features of NetBackup for Informix .................................................. 9
About NetBackup for Informix ........................................................ 11
About NetBackup for Informix terms ............................................... 11
Example NetBackup for Informix configuration ................................. 12
About the Informix ON-bar utility and library ................................... 13
How NetBackup for Informix works ................................................. 14

Chapter 2 Installing NetBackup for Informix ................................... 15


Planning the installation of NetBackup for Informix .......................... 15
Verifying the operating system and platform compatibility for
NetBackup for Informix ........................................................... 16
NetBackup server and client requirements for NetBackup for
Informix ............................................................................... 16
Informix server software requirements for NetBackup for
Informix ............................................................................... 17
Adding license keys for NetBackup for Informix backups ..................... 17
Specifying the Informix home path (UNIX and Linux) ......................... 18
Adding new Informix instances ...................................................... 19

Chapter 3 Configuring NetBackup for Informix ............................... 21


About configuring NetBackup for Informix ....................................... 21
About user interface terminology .................................................... 22
About configuring a backup policy for an Informix database ................ 22
Adding a new NetBackup for Informix policy ............................... 23
About policy attributes for NetBackup for Informix ...................... 24
About adding schedules to a NetBackup for Informix policy ........... 25
Adding clients to a NetBackup for Informix policy ........................ 29
About backup selections for an Informix client ............................ 30
Configuring a Standard policy .................................................. 32
About NetBackup for Informix scripts .............................................. 33
Modifying NetBackup for Informix scripts .................................. 33
8 Contents

About NetBackup for Informix environment variables .................. 37


Configuring an additional bp.conf file .............................................. 38
About permissions for NetBackup for Informix log files (UNIX and
Linux) .................................................................................. 39
Configuring the Maximum jobs per client ......................................... 39
Testing configuration settings for NetBackup for Informix .................. 40

Chapter 4 Performing backups and restores of Informix .............. 43


About using NetBackup for Informix ............................................... 43
About Informix ON-Bar backup types ............................................... 44
Example Informix backup strategy .................................................. 44
Automatic backup policy for Informix .............................................. 45
Manual backup policy for Informix .................................................. 45
Using the onbar command to perform a user-directed backup .............. 45
About browsing Informix backups ................................................... 45
Restoring files to the original client ................................................. 46
Redirecting an Informix restore to a different client ........................... 47
Example of procedure for restoring an Informix database .................... 50

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

Verifying the NetBackup for Informix configuration ........................... 55


Verifying NetBackup for Informix log files ........................................ 56
NetBackup debug logs and reports ................................................... 59
Enabling the NetBackup for Informix logs .................................. 60
About the NetBackup for Informix log files ................................. 60
About NetBackup server reports ............................................... 61
About Informix ON-Bar utility logs ............................................ 61
Setting the debug level on a UNIX or Linux client ............................... 62
Minimizing timeout failures on large database restores ....................... 62
Minimizing loading and unloading of tapes for database backups
(UNIX and Linux) ................................................................... 63
About deleting expired backups from the Informix backup
database ............................................................................... 63
Informix versions XPS 8.x and IDS 9.x ....................................... 63
Informix version IDS 7.x .......................................................... 63

Index .................................................................................................................... 65
Chapter 1
Introduction to NetBackup
for Informix
This chapter includes the following topics:

■ Features of NetBackup for Informix

■ About NetBackup for Informix

■ About NetBackup for Informix terms

■ Example NetBackup for Informix configuration

■ About the Informix ON-bar utility and library

■ How NetBackup for Informix works

Features of NetBackup for Informix


Table 1-1 shows NetBackup for Informix’s main features and introduces some
terms used in this documentation.

Table 1-1 NetBackup for Informix features and descriptions

Feature Description

Media and device All devices supported by Media Manager are available to
management NetBackup for Informix.
10 Introduction to NetBackup for Informix
Features of NetBackup for Informix

Table 1-1 NetBackup for Informix features and descriptions (continued)

Feature Description

Scheduling facilities NetBackup scheduling facilities on the master server can be used
to schedule automatic and unattended Informix backups.

This feature 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 NetBackup’s
and restores multiplexing capabilities. Multiplexing directs multiple data
streams to one backup device, thereby reducing the time necessary
to complete the operation.

Transparent Informix All backups and restores run simultaneously and transparently
and regular file system without any action from the NetBackup administrator.
backup and restore
The database administrator can run database backup and restore
operations
operations through NetBackup. An administrator or any other
authorized user can use NetBackup to run database backups and
restores.

Alternatively, you can use the Informix ON-Bar utility as if


NetBackup were not present.

Sharing the same It is possible to share the same devices and media used for other
storage units used for backups or to give Informix exclusive use of certain devices and
other file backups media. NetBackup for Informix can use Media Manager, disk, and
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.
Introduction to NetBackup for Informix 11
About NetBackup for Informix

Table 1-1 NetBackup for Informix features and descriptions (continued)

Feature Description

Parallel backup and NetBackup for Informix supports the parallel backup and restore
restore operations capabilities of Informix ON-Bar. 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.

Compression Compression increases backup performance over the network and


reduces the size of the backup image that NetBackup writes to the
storage unit.

For more information on general NetBackup terminology, see the NetBackup


Administrator’s Guide, Volume I.

About NetBackup for Informix


NetBackup for Informix integrates the database backup and recovery capabilities
of the Informix ON-Bar utility with the backup and the recovery management
capabilities of NetBackup and its media manager.
This topic introduces NetBackup for Informix, and it explains how this agent
relates both to the Informix ON-Bar utility and NetBackup.

About NetBackup for Informix terms


Table 1-2 lists the terms that may be new to an Informix database administrator
or a NetBackup administrator.

Table 1-2 Terminology

Term Meaning

Informix ON-Bar The Informix ON-Bar utility lets database administrators back up
utility and restore Informix databases on UNIX systems. However, this
utility 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.
12 Introduction to NetBackup for Informix
Example NetBackup for Informix configuration

Table 1-2 Terminology (continued)

Term Meaning

onbar More information about this command is available. The onbar


command starts a backup or restore with the Informix ON-Bar
utility.

See the IBM Informix Backup and Restore Guide.

ON-Bar scripts A Bourne-shell script that contains onbar commands.

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.

Example NetBackup for Informix configuration


The server that hosts the Informix database must be a NetBackup client. It must
have NetBackup for Informix and the Informix ON-Bar utility installed.
Figure 1-1 shows the major components in a NetBackup for Informix configuration.
Introduction to NetBackup for Informix 13
About the Informix ON-bar utility and library

Figure 1-1 Major components in a NetBackup for Informix configuration


System hosting the Informix database

NetBackup for Informix supplies:

– Vendor I/O library


– Sample configuration program
Informix database – Sample script files

Additional NetBackup software:


Informix database software supplies:
– NetBackup client (required)
– Informix ON-Bar Utility

Network (TCP/IP)

NetBackup master server


or remote media server Storage unit

NetBackup software:
– NetBackup master server or media server

About the Informix ON-bar utility and library


During a backup or restore, the Informix ON-Bar utility provides the interface to
the databases and performs the actual extraction and insertion of data.
To start a database backup or restore, the database administrator runs a command
called onbar. This command, which is part of the Informix ON-Bar utility, can be
executed from the command line, from an ON-Bar script, or from an application
such as NetBackup. An ON-Bar script includes the onbar command to be executed
and defines the database objects to be backed up or restored.
During a backup or restore, the Informix ON-Bar utility controls the data streams
going into or out of a database. To access the storage devices, this utility must be
integrated with a media-management system such as the one provided by
NetBackup and its Media Manager.
The onbar command is documented in the IBM Informix Backup and Restore Guide.
Instructions are available for how to find the supported Informix version level.
14 Introduction to NetBackup for Informix
How NetBackup for Informix works

See “Verifying the operating system and platform compatibility for NetBackup
for Informix” on page 16.
NetBackup for Informix has a special library that contains the functions necessary
for the Informix ON-Bar utility to use NetBackup.

How NetBackup for Informix works


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
bphdb starts the ON-Bar script on the client.

The following events occur for a backup:


■ The onbar command starts the requested operation on the databases.
■ If the process requires media to store backup data, onbar starts a user-directed
backup by issuing a backup request.
■ The NetBackup media server connects to ON-Bar through the NetBackup
library on the client and transfers the database data to secondary storage.
A restore works in essentially the same manner except that onbar issues a restore
request. This action causes NetBackup to retrieve the data from secondary storage
and send it to NetBackup for Informix on the client.
The status for an ON-Bar operation is logged in the Informix BAR_ACT_LOG. A
database administrator can use this log to determine if a backup or restore was
successful.
NetBackup also logs status, but only for its own part of the operation. This debug
log is located in the following directory:

/usr/openv/netbackup/logs/infbsa

A database administrator cannot use NetBackup status to determine whether


ON-Bar was successful because errors can occur in ON-Bar that do not affect
NetBackup and are not recorded in its logs.
See “About NetBackup for Informix scripts” on page 33.
Chapter 2
Installing NetBackup for
Informix
This chapter includes the following topics:

■ Planning the installation of NetBackup for Informix

■ Verifying the operating system and platform compatibility for NetBackup for
Informix

■ NetBackup server and client requirements for NetBackup for Informix

■ Informix server software requirements for NetBackup for Informix

■ Adding license keys for NetBackup for Informix backups

■ Specifying the Informix home path (UNIX and Linux)

■ Adding new Informix instances

Planning the installation of NetBackup for Informix


Table 2-1 shows the major installation steps needed to run NetBackup for Informix.
Each step contains one or more links to pertinent procedures and concepts.
16 Installing NetBackup for Informix
Verifying the operating system and platform compatibility for NetBackup for Informix

Table 2-1 Installation steps for NetBackup for Informix

Step Action Description

Step 1 Verify the installation prerequisites. See “Verifying the operating system and platform
compatibility for NetBackup for Informix” on page 16.

See “NetBackup server and client requirements for


NetBackup for Informix” on page 16.

See “Informix server software requirements for NetBackup


for Informix” on page 17.

Step 2 Add the license key for NetBackup for See “Adding license keys for NetBackup for Informix
Informix. backups” on page 17.

Step 3 Specify the Informix home path. See “Specifying the Informix home path (UNIX and Linux)”
on page 18.

Step 4 Add a new database instance. See “Adding new Informix instances” on page 19.

Verifying the operating system and platform


compatibility for NetBackup for Informix
Verify that the NetBackup for Informix agent is supported on your operating
system or platform.
To verify operating system and compatibility
1 Go to the Symantec Support Web page:
http://www.symantec.com/business/support/index.jsp
2 Click on the link for NetBackup Enterprise Server.
3 In the list of documents, click on the following document:
NetBackup Database Agent Compatibility List

NetBackup server and client requirements for


NetBackup for Informix
Verify that the following requirements are met for the NetBackup server:
■ The NetBackup server software is installed and operational on the NetBackup
server. The NetBackup server platform can be any that NetBackup supports.
See the NetBackup Installation Guide.
Installing NetBackup for Informix 17
Informix server software requirements for NetBackup for Informix

■ Make sure that you configure any backup media that the storage unit uses.
The number of media volumes that are required depends on several things:
■ The devices 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
■ The frequency of backups or archives
See the NetBackup Administrator’s Guide, Volume I.

Verify that the following requirements are met for the NetBackup clients:
■ The NetBackup client software is installed on the computer that has the
databases you want to back up.

Informix server software requirements for NetBackup


for Informix
Verify the following regarding the Informix server software on the NetBackup
server or client:
■ Informix server software must be installed and operational.
■ One or more Informix instances must exist.

Adding license keys for NetBackup for Informix


backups
To use NetBackup for Informix, add a valid license key for it on the master server.
More information is available on how to add license keys.
See the NetBackup Administrator’s Guide, Volume I.
To add a NetBackup for Informix license key in the NetBackup Administration
Console
1 On the master server, open the NetBackup Administration Console.
2 Choose Help > License Keys.
3 Click the New icon.
4 Type the license key and click Add.
18 Installing NetBackup for Informix
Specifying the Informix home path (UNIX and Linux)

On UNIX and Linux, you can also add a license key by using the get_license_key
command.
To add a NetBackup for Informix license key with the get_license_key command
1 From the master server server, run the following command:
/usr/openv/netbackup/bin/admincmd/get_license_key

2 When the system prompts you, type the host name of the NetBackup master
server.

Specifying the Informix home path (UNIX and Linux)


After you add the license key for NetBackup for Informix, run this script on the
computer where the Informix vendor software is installed. With this script,
NetBackup can gather additional information about your Informix environment.
Complete this procedure at the following times:
■ If you licensed NetBackup for Informix for the first time.
To specify the Informix home path
1 Change to the following directory:
/usr/openv/netbackup/bin

2 Run the following script:


./informix_config

3 Supply the home path for the database instance.


4 Verify the Informix ON-Bar configuration.
This script creates the following entry in the Informix instance home path’s
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 use a release at this level, you do not need to edit any files.
5 If you use Informix version 7.31 UC4 and earlier, continue with the next step.
Installing NetBackup for Informix 19
Adding new Informix instances

6 (Conditional) Perform this step if you use Informix version 7.31 UC4 and
earlier. Update the bar_version table in the sysutils database.
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

7 Make sure $BAR_BSALIB_PATH is correctly linked to NetBackup's


infxbsa.[so,sl,a].

See “Verifying the NetBackup for Informix configuration” on page 55.


8 Set the BAR_RETRY configuration parameter to 5.
The configuration parameter BAR_RETRY is used in the
$INFORMIXDIR/etc/$ONCONFIG file. This parameter specifies the number of
times ON-Bar attempts to back up or restore the storage space or logical log
if the first attempt fails. Informix recommends setting BAR_RETRY to 5.

Adding new Informix instances


If you install a new Informix instance after you install NetBackup, you need to
add this new instance to the NetBackup configuration. This action ensures that
all new Informix instances are included in backup operations.
See “Specifying the Informix home path (UNIX and Linux)” on page 18.
20 Installing NetBackup for Informix
Adding new Informix instances
Chapter 3
Configuring NetBackup for
Informix
This chapter includes the following topics:

■ About configuring NetBackup for Informix

■ About user interface terminology

■ About configuring a backup policy for an Informix database

■ About NetBackup for Informix scripts

■ Configuring an additional bp.conf file

■ About permissions for NetBackup for Informix log files (UNIX and Linux)

■ Configuring the Maximum jobs per client

■ Testing configuration settings for NetBackup for Informix

About configuring NetBackup for Informix


Before you configure NetBackup for Informix, complete the installation procedure.
After you complete the installation procedure, complete the procedures in
Table 3-1 to configure your environment.

Table 3-1 Steps to configure NetBackup for Informix

Step Action Description

Step 1 Configure a backup policy. See “About configuring a backup


policy for an Informix database”
on page 22.
22 Configuring NetBackup for Informix
About user interface terminology

Table 3-1 Steps to configure NetBackup for Informix (continued)

Step Action Description

Step 2 Configure NetBackup for Informix See “About NetBackup for Informix
scripts. scripts” on page 33.

Step 3 Configure an additional bp.conf file. See “Configuring an additional


bp.conf file” on page 38.

Step 4 Configure permissions for log files See “About permissions for
on UNIX and Linux systems NetBackup for Informix log files
(UNIX and Linux)” on page 39.

Step 5 Configure the Maximum jobs per See “Configuring the Maximum jobs
client. per client” on page 39.

Step 6 Test the configuration settings. See “Testing configuration settings


for NetBackup for Informix”
on page 40.

About user interface terminology


You perform many configuration steps from the NetBackup Administration
Console on the master server. The type of console available depends on your
master server platform. NetBackup supports a Java interface for both Windows
and UNIX master servers. In addition, NetBackup supports a Windows interface
for Windows master servers.
The Java and Windows interfaces are nearly identical. If interface differences
exist in the configuration procedures, the term “Windows” or “Java” appears in
the procedure to differentiate between the two interfaces.

About configuring a backup policy for an Informix


database
A backup policy for a database defines the backup criteria for a specific group of
one or more clients.
These criteria include the following:
■ Storage unit and media to use
■ Policy attributes
■ Backup schedules
Configuring NetBackup for Informix 23
About configuring a backup policy for an Informix database

■ Clients to be backed up
■ The script files to run on the clients
To back up the database environment, define at least one Informix-ON-Bar policy
with the appropriate schedules. A configuration can have a single policy that
includes all clients, or there can be many policies, some of which include only one
client.
In addition to the Informix-ON-Bar policy, back up the $INFORMIXDIR/etc files
that are specified in the backup scripts. Define a 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
available that you should consider.
See the NetBackup Administrator’s Guide, Volume I.
To add and configure a policy, see the following topics:
■ See “Adding a new NetBackup for Informix policy” on page 23.
■ See “About policy attributes for NetBackup for Informix” on page 24.
■ See “About adding schedules to a NetBackup for Informix policy” on page 25.
■ See “Adding clients to a NetBackup for Informix policy” on page 29.

Adding a new NetBackup for Informix policy


This topic describes how to add a new backup policy for a database.
To add a new NetBackup for Informix policy
1 Log on to the master server as administrator (Windows) or root (UNIX).
2 Start the NetBackup Administration Console.
3 If your site has more than one master server, choose the one on which you
want to add the policy.
4 Do one of the following:
■ Windows: In the left pane, right-click Policies and choose New Policy.
■ Java interface: In the left pane, click Policies. In the All Policies pane,
right-click the master server, and click New Policy.

5 In the Add a New Policy dialog box, in the Policy name box, type a unique
name for the new policy.
6 Click OK.
24 Configuring NetBackup for Informix
About configuring a backup policy for an Informix database

7 In the Add New Policy dialog box, in the Policy type list, select
Informix-ON-Bar.
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.
See “About policy attributes for NetBackup for Informix” on page 24.
9 Add other policy information as follows:
■ Add schedules.
See “About adding schedules to a NetBackup for Informix policy”
on page 25.
■ Add clients.
See “Adding clients to a NetBackup for Informix policy” on page 29.
■ Add scripts to the backup selections list.
See “About backup selections for an Informix client” on page 30.

10 When you have added all the schedules, clients, and backup selections you
need, click OK.

About policy attributes for NetBackup for Informix


With a few exceptions, NetBackup manages a database backup like a file system
backup. Other policy attributes vary according to your specific backup strategy
and system configuration.
For more information on policy attributes, see the NetBackup Administrator’s
Guide, Volume I.

Table 3-2 Policy attribute descriptions for NetBackup for Informix policies

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
Informix 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. However, it can be set
using the environment variable INFXBSA_KEYWORD.

See “About NetBackup for Informix environment variables” on page 37.


Configuring NetBackup for Informix 25
About configuring a backup policy for an Informix database

About adding schedules to a NetBackup for Informix policy


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
these types of schedules: application backup and automatic backup.

Configuring a NetBackup for Informix application backup


schedule
A database backup requires an application backup schedule. You cannot perform
backups if this type of schedule is not included in the policy. The NetBackup for
Informix agent automatically creates this schedule and names it
Default-Application-Backup.
The backup window for an application backup schedule must encompass the time
period during which all scheduled jobs and unscheduled jobs can occur. This
window is necessary because the application backup schedule starts the processes
that are required for all database backups, including those started automatically.
You can choose to set the window for the application backup schedule for 24 hours
per day, seven days per week. This window ensures that your operations are never
locked out due to the application backup schedule.
To configure an application backup schedule
1 In the Policy dialog box, click the Schedules tab.
To access the Policy dialog box, double-click the policy name in the Policies
list in the NetBackup Administration Console .
2 Double-click the schedule that is named Default-Application-Backup.
3 Specify the other properties for the schedule.
See “About NetBackup for Informix schedule properties” on page 28.

Example application backup schedule for NetBackup for


Informix

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 38.

Assume the following:


■ Users perform database backup operations during business hours, 08:00 to
13:00.
26 Configuring NetBackup for Informix
About configuring a backup policy for an Informix database

■ The automatic backups that use this policy start between 18:00 and 22:00.
In this scenario, the application backup schedule must have a start time of 0800
and a duration of 14 hours.

Table 3-3 Example settings for a NetBackup for Informix application backup
schedule

Schedule option Setting

Retention 2 weeks

Backup window Sunday through Saturday

00:08:00 - 22:00:00

Configuring NetBackup for Informix automatic backup


schedules
If you plan to have NetBackup perform automatic scheduled backups, you need
one or more automatic backup schedules.
To configure an automatic backup schedule
1 On the Policy dialog box, click the Schedules tab.
2 Click New.
3 Specify a unique name for the schedule.
4 Select the Type of backup.
See “About the NetBackup for Informix backup types” on page 27.
5 Specify the other properties for the schedule.
See “About NetBackup for Informix schedule properties” on page 28.
6 Click OK.

Example automatic backup schedule for NetBackup for Informix


Table 3-4 shows example settings for automatic backup schedules.

Table 3-4 Example settings for NetBackup for Informix automatic backup
schedules

Type of backup Schedule property Setting

Automatic Full Backup Retention (proxy backup 2 weeks


only)
Configuring NetBackup for Informix 27
About configuring a backup policy for an Informix database

Table 3-4 Example settings for NetBackup for Informix automatic backup
schedules (continued)

Type of backup Schedule property Setting

Frequency Every week

Backup window Sunday, 18:00:00 - 22:00:00

Automatic Incremental Retention (proxy backup 1 week


Backup only)

Frequency Every day

Backup window Sunday through Saturday

18:00:00 - 22:00:00

About the NetBackup for Informix backup types


Table 3-5 shows the backup schedules you can specify.

Table 3-5 Informix backup types

Backup type Description

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


Backup that have changed 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.


28 Configuring NetBackup for Informix
About configuring a backup policy for an Informix database

About NetBackup for Informix schedule properties


This topic describes the schedule properties that have a different meaning for
database backups than for file system backups. Other schedule properties vary
according to your specific backup strategy and system configuration. Additional
information about other schedule properties is available.
See the NetBackup Administrator’s Guide, Volume I.

Table 3-6 Description of 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.

See “About the NetBackup for Informix backup types” on page 27.

Schedule type You can schedule a backup in one of the following ways:

■ Frequency
This setting is used only for scheduled backups. It is not used 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.
Configuring NetBackup for Informix 29
About configuring a backup policy for an Informix database

Table 3-6 Description of schedule properties (continued)

Property Description

Retention The retention period for an application backup schedule refers to the length of time that
NetBackup keeps backup images (stream-based backups). The retention period for an
automatic schedule controls how long NetBackup keeps records of when scheduled backups
occurred (proxy backups). For example, if your database is backed up once every Sunday
morning, you should select a retention period of at least 2 weeks.
The retention period is affected by the type of schedule you select, as follows:

■ Frequency-based scheduling
Set a retention period that is longer than the frequency setting for the schedule. For
example, if the frequency setting is set to one week, set the retention period to be more
than one week. The NetBackup scheduler compares the latest record of the automatic
backup schedule to the frequency of that automatic backup schedule to determine
whether a backup is due. This means that if you set the retention period to expire the
record too early, the scheduled backup frequency is unpredictable. However, if you set
the retention period to be longer than necessary, the NetBackup catalog accumulates
unnecessary records.
■ Calendar-based scheduling
The retention period setting is not significant for calendar-based scheduling.

Multiple copies If you want to specify multiple copies of a backup for the policy, configure Multiple copies
on the application backup schedule.

Adding clients to a NetBackup for Informix policy


The client list contains a list of the clients on which your 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 NetBackup for Informix policy, clients you want to add must have the
following software installed:
■ Informix
■ NetBackup client or server
■ The backup or restore script(s)
To add clients to a NetBackup for Informix policy
1 In the Policy dialog box, click the Clients tab.
To access the Policy dialog box, double-click the policy name in the Policies
list in the NetBackup Administration Console.
2 Click New.
30 Configuring NetBackup for Informix
About configuring a backup policy for an Informix database

3 Type the name of the client and press Enter (Windows) or click Add (Java).
If Informix is installed in a NetBackup cluster, specify the virtual Informix
name as the client name.
4 (Windows) To add another client, repeat step 2 and step 3.
5 (Java) To add another client, repeat step 3.
6 If this client is the last client you want to add, click OK.
7 (Java) In the Policy dialog box, click Close.

About backup selections for an Informix client


The backup selections list in a database policy is different from the list in
non-database policies. For example, in a Standard or MS-Windows policy, the list
contains files and directories to be backed up. In a database policy, you specify
scripts to be run.

About NetBackup for Informix scripts rules


Observe the following when you use scripts:
■ Make sure the scripts reside on each client in the client list. Scripts can reside
in any location. Make sure that NetBackup can access the location you choose
and that NetBackup can run the scripts.
■ NetBackup installs sample scripts when you install the software; you can
modify these scripts for your own use. Write the scripts to a location outside
of the original installation location. This ensures that future NetBackup
installations do not overwrite your site’s scripts.
■ If you use NetBackup for Informix in a NetBackup server cluster, make sure
that the scripts reside in a location that is available after a failover.
Add scripts to the backup selections list only if you want to set up a policy for
automatic backups. These scripts are run for manual backups and for automatic
backup schedules as specified under the Schedules tab. NetBackup runs the scripts
in the order that the scripts appear in the backup selections list.
See “About NetBackup for Informix scripts” on page 33.

Adding NetBackup for Informix scripts to the backup selections


list
The following procedures describe how to add scripts to the backup selections list
by with the Java interface and the Windows interface. Review the information on
backup scripts if necessary.
Configuring NetBackup for Informix 31
About configuring a backup policy for an Informix database

Note: 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 NetBackup for Informix 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 In the Script box, type the full path name of a script on the client.
For example:

/backup_scripts/db/cold_backup.sh

5 Click Add to add the script to the list.


6 Click OK.
To add NetBackup for Informix 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

■ Click the Remote Folder button.

4 Navigate to and select the script file, then click OK.


5 Click OK.
32 Configuring NetBackup for Informix
About configuring a backup policy for an Informix database

Configuring a Standard policy


In addition to the Informix policy, you also must configure a Standard type policy.
A Standard policy enables the backup of the $INFORMIXDIR/etc files that is
specified in the scripts.
Note the following:
■ You must specify the name of the policy in the backup scripts that you modify
on the client.
■ You do not need to configure a file list for this policy because the policy uses
a User Backup type schedule.
To configure a Standard policy
1 Add a new policy.
See "Configuring a NetBackup Policy."
2 Specify the general attributes for the policy.
■ Select Standard for the policy type.
■ Specify other attributes as desired.

3 Add a schedule.
Provide the following information.

Name Type the name of your schedule.

Type of Backup Select User Backup.

A User Backup schedule enables user controlled NetBackup


operations performed on the client.

Retention Set the time period that is needed to retain two full backups
of your database.

For example, if your database is backed up once every Sunday


morning, select a retention period of at least two weeks.

Start Window 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.

4 Specify the clients to be backed up.


The client must have both Informix and NetBackup for Informix installed.
5 Click OK.
Configuring NetBackup for Informix 33
About NetBackup for Informix scripts

About NetBackup for Informix scripts


The NetBackup installation software writes Informix scripts to the following
directory:

/usr/openv/netbackup/ext/db_ext/informix/scripts

For more information on ON-Bar scripts, see your Informix documentation.


Be sure to modify these scripts for your environment. Although each script can
perform multiple ON-Bar operations, each type of operation requires a separate
script. For example, you need separate scripts for backups and restores.

Note: Always specify the correct script when you configure automatic backups or
when you start 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.

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

Modifying NetBackup for Informix scripts


The following procedure shows how to modify a script. Repeat this procedure for
each script that you modify.
34 Configuring NetBackup for Informix
About NetBackup for Informix scripts

To modify NetBackup for Informix scripts


1 Copy the example scripts from
/usr/openv/netbackup/ext/db_ext/informix/scripts to a different location
on your client.
The Informix scripts can reside anywhere on the client. Do not store your
scripts in the sample directory because your modifications are lost if you
upgrade or reinstall. Always relocate your scripts to a safe location. In a
NetBackup cluster, the script must be available after a failover.
2 Enable proper permissions on the script files so NetBackup can access the
script files.
Set the access permissions of the scripts to 775. For example:

chmod 775 script_name

3 Open the script file with a text editor.


For example, use the following command to modify the
informix_onbar_backup_of_rootdbs script:

vi informix_onbar_backup_of_rootdbs
Configuring NetBackup for Informix 35
About NetBackup for Informix scripts

4 Modify the script according to the instructions in the file.


Customize the scripts to reflect your Informix installation. Refer to the
comments in the scripts that indicate "Replace ....". The scripts need to be
modified to have the correct Informix home path and Informix server name.
The scripts also must include the policy that you want to use to back up the
files and the name of the Informix configuration file.
For example, the informix_onbar_backup_of_rootdbs script contains the
following lines:

#!/bin/sh

# Replace xxxxx below with the extention used for your onconfig file.
ONCONFIG=onconfig.xxxxx

# Replace yyyyy below with the Informix home path.


INFORMIXDIR=/yyyyy/informix

# Replace zzzzz below with the name of the Informix server.


INFORMIXSERVER=zzzzz

# Replace informix_etc below with the name of the NetBackup server policy
# to be used to back up the $INFORMIXDIR/etc directory.
INFX_ETC_POLICY=informix_etc

echo "Started ‘date’"

export ONCONFIG
echo "exported ONCONFIG"

export INFORMIXDIR
echo "exported INFORMIXDIR"

export INFORMIXSERVER
echo "exported INFORMIXSERVER"

echo "INFXBSA_SERVER = $INFXBSA_SERVER"


echo "INFXBSA_SCHEDULED = $INFXBSA_SCHEDULED"
echo "INFXBSA_USER_INITIATED = $INFXBSA_USER_INITIATED"
echo "INFXBSA_FULL = $INFXBSA_FULL"
echo "INFXBSA_INCR = $INFXBSA_INCR"
echo "INFXBSA_POLICY = $INFXBSA_POLICY"
36 Configuring NetBackup for Informix
About NetBackup for Informix scripts

RETURN_STATUS=0

if [ "${INFXBSA_INCR}" = "1" ]
then
# Netbackup has started an incremental backup.
echo "$INFORMIXDIR/bin/onbar -b -L 1 rootdbs"
$INFORMIXDIR/bin/onbar -b -L 1 rootdbs
RETURN_STATUS=$?
else

echo "$INFORMIXDIR/bin/onbar -b -L 0 rootdbs"


$INFORMIXDIR/bin/onbar -b -L 0 rootdbs
RETURN_STATUS=$?

fi

if [ "$RETURN_STATUS" -eq "0" ]


then

# Initiate a backup of the directory that contains the onconfig,


# sqlhosts, oncfg_$INFORMIXSERVER.SERVERNUM, and ixbar.SERVERNUM
# files after doing the backup.

echo "bpbackup -p $INFX_ETC_POLICY -w 0 $INFORMIXDIR/etc"


/usr/openv/netbackup/bin/bpbackup -p $INFX_ETC_POLICY -w 0 $INFORMIXDIR/etc
BPBACKUP_STATUS=$?

if [ "$BPBACKUP_STATUS" -ne "0" ]


then
echo ""
echo "bpbackup of $INFORMIXDIR/etc returned $BPBACKUP_STATUS"
fi
fi

echo "Finished ‘date’"

echo "exit $RETURN_STATUS"


echo ""
Configuring NetBackup for Informix 37
About NetBackup for Informix scripts

exit $RETURN_STATUS

5 Test the scripts that you created.


More information is available on how to test your configuration.
See “Testing configuration settings for NetBackup for Informix” on page 40.

About NetBackup for Informix environment variables


When a schedule runs, NetBackup sets environment variables for the local shell
scripts to use when it performs 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:

INFXBSA FULL Set to 1 if this backup is a full backup (Automatic


Full Backup).

INFXBSA_INCR Set to 1 if this backup is an incremental backup


(Automatic Incremental Backup).

INFXBSA_SCHEDULED Set to 1 if this backup is a scheduled backup


(Automatic Full Backup or Automatic Incremental
Backup).

INFXBSA_USER_INITIATED Set to 1 if this backup is a user-initiated backup


(Application Backup backup).

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:

INFXBSA_SERVER Name of the NetBackup server.

INFXBSA_LOGICAL_POLICY Name of the policy to be used for a logical logs


backup. If this variable is set, NetBackup backs
up the logical logs with this policy.

INFXBSA_LOGICAL_SCHED Name of the schedule to be used for a logical logs


backup. If this variable is set, NetBackup
distinguishes and backs up logical logs with this
schedule.
38 Configuring NetBackup for Informix
Configuring an additional bp.conf file

INFXBSA_POLICY Name of the Informix-ON-Bar policy. If this


variable is set, NetBackup backs up Informix
databases with this policy.

INFXBSA_SCHED Name of the Application Backup schedule. If this


variable is set, NetBackup backs up Informix
databases with this schedule.

INFXBSA_KEYWORD The keyword phrase you want to associate with


a backup image.

Configuring an additional bp.conf file


The administrator can add options to the NetBackup bp.conf file on the NetBackup
master server. The administrator can create an additional bp.conf file in the
home directory of the Informix user’s account used for the backup or restore.
Before you use NetBackup for Informix, you can create a bp.conf file in the home
directory of the Informix user’s account used for the backup on the NetBackup
client. The path to this directory can be equal to the value of the $INFORMIXDIR
variable.
For example, if the home directory is /informix, the path is as follows:

/informix/bp.conf

After you create a bp.conf file in the Informix home directory, add the following
options to the file and replace the italicized text with the information that pertains
to the client:

BPBACKUP_POLICY=informix_policy
BPBACKUP_SCHED=informix_sched
SERVER=server_name
CLIENT_READ_TIMEOUT=1800

The variables are as follows:

informix policy The name of the Informix-ON-Bar policy that was configured in the
backup policy.

See “About configuring a backup policy for an Informix database”


on page 22.

informix_sched The schedule name for the informix_policy. By default, it is


Default-Application-Backup.

server_name The name of the NetBackup master server.


Configuring NetBackup for Informix 39
About permissions for NetBackup for Informix log files (UNIX and Linux)

NetBackup uses the bp.conf file in the Informix user’s home directory only for
backups and restores initiated by this Informix user.

About permissions for NetBackup for Informix log


files (UNIX and Linux)
NetBackup uses the /usr/openv/netbackup/logs directory tree not only for the
recording of troubleshooting information, but for progress and communication
updates to users and other NetBackup applications. Restrictive permissions on
these directories can not only disable the collection of troubleshooting data, but
also prevent the application itself from functioning correctly.
Backup and restore operations fail when permissions are too restrictive. We
recommend that you make all of the usr/openv/netbackup/logs directories and
subdirectories readable and writeable by all users (777 permissions). However,
security requirements may prohibit global read-write access. If so, you can restrict
permissions of specific directories to a single group or user if the following is true:
Processes that run as members of that group or as that user initiate all backup
and restore operations that are related to that directory.
Check that the /usr/openv/netbackup/logs/user_ops directory tree has 777
permissions. The items in this directory need to be accessible for the applications
to operate correctly.
If you restrict permissions on the other directories that are located in
/usr/openv/netbackup/logs, backup and restore operations are not affected.
However, troubleshooting efforts may be hindered when processes do not have
the appropriate permissions to update the debug logs therein.

Configuring the Maximum jobs per client


The following procedure shows how to set the Maximum jobs per client attribute.
To configure the maximum jobs per client
1 In the left pane of the NetBackup Administration Console, expand NetBackup
Management > Host Properties.
2 Select Master Server.
3 In the right pane, double-click the server icon.
40 Configuring NetBackup for Informix
Testing configuration settings for NetBackup for Informix

4 Click Global Attributes.


5 Change the Maximum jobs per client value to 99.
The Maximum jobs per client specifies the maximum number of concurrent
backups that are allowed per client. The default is 1.
You can use the following formula to calculate a smaller value for the Maximum
jobs per client setting:
Maximum jobs per client = number_of_streams X number_of_policies
Refer to the following definitions:

number_of_streams The number of backup streams between the database server and
NetBackup. Each separate stream starts a new backup job on the client.

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 to back up two different databases. These backup
windows can overlap.

Note: Enter a large enough value for the Maximum jobs per client attribute to
meet the number of jobs that Informix runs. You may need to experiment with
different values at your site.

Testing configuration settings for NetBackup for


Informix
After you configure the master server for NetBackup for Informix, test the
configuration settings. Perform a manual backup (or backups) with the automatic
backup schedules you created. A description of status codes and other
troubleshooting information is available.
See the NetBackup Status Codes Reference Guide.
See the NetBackup Troubleshooting Guide.
To test the configuration settings
1 Log onto the master server as administrator (Windows) or root (UNIX).
2 Start the NetBackup Administration Console.
3 In the left pane, click Policies.
4 Click the policy you want to test.
Configuring NetBackup for Informix 41
Testing configuration settings for NetBackup for Informix

5 Select Actions > Manual Backup.


The Schedules pane contains the name of an automatic schedule (or schedules)
configured for the policy that you want to test. The Clients pane contains the
name of the client(s) listed in the policy that you want to test.
6 Follow the directions in the Manual Backup dialog box.
7 To check the status of the backup, click Activity Monitor in the NetBackup
Administration Console.
The Activity Monitor and the script output indicate the status of the backup
operation.
For more information, see the Troubleshooting chapter.
42 Configuring NetBackup for Informix
Testing configuration settings for NetBackup for Informix
Chapter 4
Performing backups and
restores of Informix
This chapter includes the following topics:

■ About using NetBackup for Informix

■ About Informix ON-Bar backup types

■ Example Informix backup strategy

■ Automatic backup policy for Informix

■ Manual backup policy for Informix

■ Using the onbar command to perform a user-directed backup

■ About browsing Informix backups

■ Restoring files to the original client

■ Redirecting an Informix restore to a different client

■ Example of procedure for restoring an Informix database

About using NetBackup for Informix


When all installation and configuration are complete, you can start Informix
backups and restores through NetBackup or run the onbar command directly.
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.
44 Performing backups and restores of Informix
About Informix ON-Bar backup types

About Informix ON-Bar backup types


The Informix ON-Bar utility supports different types of backups.
Table 4-1 describes each backup type.

Table 4-1 Informix ON-Bar backup types

Backup type Description

Level 0 backup (Full) An Informix level 0 backup is a full backup. It includes all the
records in the selected dbspaces and is the only type of backup
that allows a complete restore without performing any recovery
steps.

Level 1 backup An Informix level 1 backup is an incremental backup. It backs up


(Incremental) the records that changed since the last level 0 backup in the
selected dbspaces.

Level 2 backup An Informix level 2 backup backs up the records that changed
since the last Level 1 Backup in the selected dbspaces. NetBackup
does not support this type of backup with an equivalent automatic
schedule. To perform level 2 backups write a script and by keep
track of the previous backup type with the ON-Bar script.

Logical-log backup An Informix logical-log backup backs up the filled logical logs. By
using the Informix ALARMPROGRAM configuration option, these
backups can be started on demand when the logical logs fill.

For more information, see your Informix documentation.

Example Informix backup strategy


The backup strategy in the following example is for a database that requires
frequent backups to provide protection against disk failure.
This strategy is as follows:
■ Perform an Informix full backup (level 0) every Friday night.
This backs up the selected dbspaces.
■ Perform an Informix incremental backup (level 1) each night.
■ 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 each
incremental backup.
Performing backups and restores of Informix 45
Automatic backup policy for Informix

■ 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
NetBackup policy and then schedule a full logical-log backup to occur as often
as necessary. Have a good strategy for backing up logical-log files because they
are needed for database recovery.

Automatic backup policy for Informix


The most convenient way to back up your database is to set up schedules for
automatic backups.
When the NetBackup scheduler invokes a schedule for an automatic backup, the
ON-Bar scripts run as follows:
■ In the same order as they appear in the file list
■ On all clients that have them (that is, matching path names)
The ON-Bar scripts start the database backup.
Instructions for how to add a new schedule or change an existing schedule for
automatic backups are available.

Manual backup policy for Informix


The administrator on the master server can use the NetBackup server software
to manually execute an Automatic Backup schedule for the Informix-ON-Bar
policy.

Using the onbar command to perform a user-directed


backup
You can run the onbar command from the UNIX command line on the client to
start a backup.

About browsing Informix 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 to search all Informix backups for a client named cabbage:
46 Performing backups and restores of Informix
Restoring files to the original client

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

The -t 6 on this command specifies the Informix backups (dumps). Alternatively,


you can specify -t 0 to browse the backups of files in the $INFORMIXDIR/etc files.
For more information on this command, see the bplist(1M) man page.

Restoring files to the original client


Start all restores from the NetBackup for Informix client. A backup must have
completed successfully before a restore is started. Otherwise, an error message
is generated.
To perform a user-directed restore, use the onbar command from the UNIX
command line on the client.

Note: You cannot run restore operations from the server.

To restore files to the original client


1 Before you replace any disks that have failed, salvage the logical-log files.
Use the following command:

onbar -l -s

2 (Conditional) Determine whether you need to restore the $ONCONFIG file,


sqlhosts file, emergency boot file, or the oncfg_$INFORMIXSERVER.SERVERNUM
file.
If you need to restore these files, use the NetBackup Administration Console
, as follows:
■ Change to the $INFORMIXDIR/etc directory.
Use the following command:

cd $INFORMIXDIR/etc
Performing backups and restores of Informix 47
Redirecting an Informix restore to a different client

■ Start the Java interface:


Use the following command:

/usr/openv/netbackup/bin/jbpSA &

■ Select the files to restore and start the restore.

3 Use onbar to physically restore the damaged dbspaces.


For example:

onbar -r -p dbspace1 dbspace2

4 Use onbar to logically restore the dbspaces that you physically restored.
For example:

onbar -r -l

Redirecting an Informix restore to a different client


You have the option to restore an Informix database to a client other than the one
that originally supplied the backup. This process of restoring data to a different
client is called a redirected restore.
To perform a redirected restore, the following conditions must be present:
■ The source and the destination clients must have identical operating system
versions and bit levels.
■ The source and the destination clients must have identical Informix database
versions.
■ The Informix ownerId, Informix groupId, and Informix home must be identical
on the source and on the destination clients.
For more information on redirected restores, see the NetBackup Administrator’s
Guide, Volume 1.
To redirect an Informix restore to a different client
1 Configure the NetBackup server to allow redirected restores. You must be
the NetBackup administrator to perform these tasks.
Create one of the following files:
■ To remove restrictions for all clients, create the following file on the
NetBackup master server:

/usr/openv/netbackup/db/altnames/No.Restrictions
48 Performing backups and restores of Informix
Redirecting an Informix restore to a different client

Take care when using the No.Restrictions file. This file permits the root
user of any client to browse and restore backups from any other client.
■ To restrict clients to restore only from certain other clients, create the
following file on the NetBackup master server:

/usr/openv/netbackup/db/altnames/client_name

For client_name, specify the name of the client that is allowed to perform
the redirected restore. Add the name of the NetBackup for Informix source
client to that file.

2 Back up the logical logs on the NetBackup for Informix source client.
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

3 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

4 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

■ For Extended Parallel Server:

xctl onmode -ky

5 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.
Performing backups and restores of Informix 49
Redirecting an Informix restore to a different client

6 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.
■ Copy the emergency or the 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
that is specified in the $INFORMIXDIR/etc/$ONCONFIG file.
■ Copy the connectivity information file, $INFORMIXDIR/etc/sqlhosts,
which specifies how the client application finds and connects to an
Informix database server .
■ Copy the database configuration file that is specified by the environment
variable ONCONFIG. This file is located in the $INFORMIXDIR/etc directory.
■ Copy the files that are created and updated by the Informix database server
every time a dbspace, blobspace, logical-log file, or chunk is added or
deleted.
For Informix Dynamic Server, this file is
$INFORMIXDIR/etc/oncfg_servername.servernum
For Extended Parallel Server, for each coserver, this file is
$INFORMIXDIR/etc/oncfg_servername.servernum.coserverid
The variables are as follows:

servernum The value of the SERVERNUM configuration.

servername The value of the DBSERVERNAME configuration.

coserverid The ID of the coserver.

■ (Conditional) Copy file xcfg_servername.servernum.


Perform this step if you use the Extended Parallel Server. File
xcfg_servername.servernum contains information about coserver location
and dbslice definition.
In the file name, the variables are as follows:

servernum The value of the SERVERNUM configuration.


50 Performing backups and restores of Informix
Example of procedure for restoring an Informix database

servername The value of the DBSERVERNAME configuration.

7 Configure the NetBackup for Informix destination client.


■ Set the INFXBSA_CLIENT environment variable to the host name of the
source client.
■ (Conditional) Set the INFXBSA_SERVER environment variable to the
NetBackup master server that is used for the source client backup.
Perform this step if the NetBackup master server that is used for the
source client backup is different than the server that is specified in the
bp.conf file on the destination.

8 Perform the redirected restore.


■ Log onto the NetBackup for Informix destination client as Informix
ownerId.
■ Perform a physical restore.
Use the following command to restore storage spaces to their most recent
backed-up state:

onbar -r -p

■ Perform a logical restore.


Use the following command to update the most recent backed-up version
of the storage spaces with later transactions:

onbar -r -l

Example of procedure for restoring an Informix


database
This example shows the procedure for restoring an Informix database from the
original source computer, camel, to the destination computer, giraffe. For this
example, the redirected restore is necessary because the original computer, camel,
failed. You also can use a redirected restore to duplicate your Informix database
in a development or in a test environment.
This example assumes the following:
■ Source client camel is a Solaris computer that is running Informix.
■ SERVERNUM is 6
Performing backups and restores of Informix 51
Example of procedure for restoring an Informix database

■ DBSERVERNAME is srcdb

■ Host name is camel

■ Destination client giraffe is a Solaris computer that is running Informix.


■ SERVERNUM is 0

■ DBSERVERNAME is destdb

■ Host name is giraffe

■ NetBackup master server is lion. The bp.conf on camel includes SERVER=lion.


If SERVER=lion were not the first server in the bp.conf file, then the
environment variable INFXBSA_SERVER on camel you would set to lion, as
follows:

export INFXBSA_SERVER=lion

■ Previously you performed the onbar -b Informix database backup on camel.


■ Previously you performed a file system backup of $INFORMIXDIR/etc on camel,
which effectively backed up the following:
■ ixbar.6

■ sqlhosts

■ onconfig

■ oncfg_srcdb.6

■ You salvaged the logical logs on camel by using the following command:

onbar -l -s

To redirect an Informix restore (Example)


1 As the NetBackup administrator, create the following file on the NetBackup
server, lion:

/usr/openv/netbackup/db/altnames/giraffe

2 Add the name camel to the file.


3 Log into giraffe as Informix ownerId and ensure that the Informix database
server is shut down.
4 Perform a manual file system backup of $INFORMIXDIR/etc on giraffe.
Including the following files:
52 Performing backups and restores of Informix
Example of procedure for restoring an Informix database

■ ixbar.0

■ sqlhosts

■ onconfig

■ oncfg_destdb.0

Note that this step is a precautionary measure. It is performed in case these


configuration files are needed to recreate the environment on giraffe. This
backup is not used for the redirected restore.
5 On giraffe, change the Informix server environment variable to match the
variable on camel.
Use the following command:

export INFORMIXSERVER=srcdb

6 On giraffe, change the INFXBSA_CLIENT environment variable to camel.


For example:

export INFXBSA_CLIENT=camel

This causes giraffe to browse backups from camel.


7 (Conditional) On giraffe, set the INFXBSA_SERVER environment variable to
lion.

For example:

export INFXBSA_SERVER=lion

This step is needed only if the first server that is specified in the bp.conf file
on giraffe is not lion.
8 Browse the file system backups from camel and restore to $INFORMIXDIR/etc
on giraffe.
Restore the following files:
■ ixbar.6

■ sqlhosts

■ onconfig

■ oncfg_destdb.6

9 Perform the redirected restore to giraffe.


Complete the following steps:
Performing backups and restores of Informix 53
Example of procedure for restoring an Informix database

■ To perform the physical restore, run the following command:

onbar -r -p

■ Verify the return status by using the following command:

echo $?

If the restore was successful, the return status is 0.


■ To perform the logical restore run the following command

onbar -r -l

■ Verify the return status by using the following command:

echo $?

If the restore was successful, the return status is 0.

10 On the destination client (giraffe), start the database.


54 Performing backups and restores of Informix
Example of procedure for restoring an Informix database
Chapter 5
Troubleshooting
This chapter includes the following topics:

■ Verifying the NetBackup for Informix configuration

■ Verifying NetBackup for Informix log files

■ NetBackup debug logs and reports

■ Setting the debug level on a UNIX or Linux client

■ Minimizing timeout failures on large database restores

■ Minimizing loading and unloading of tapes for database backups (UNIX and
Linux)

■ About deleting expired backups from the Informix backup database

Verifying the NetBackup for Informix configuration


Use the following procedure to verify that environment variables, paths, and other
settings are correct for your installation.
To verify the configuration
1 Verify the existence of $BAR_BSALIB_PATH, which is defined in the Informix
$CONFIG file. This path should point to NetBackup's
/usr/openv/netbackup/bin/infxbsa.[so,sl,a] library. Ensure that the
permissions are set to 755.
2 Verify that the Informix policy and schedule are properly created.
See “About configuring a backup policy for an Informix database” on page 22.
3 Set the following variables in the Informix $INFORMIXDIR/etc/$ONCONFIG
configuration file:
56 Troubleshooting
Verifying NetBackup for Informix log files

■ BAR_DEBUG. This variable sets the level of detail to be gathered about the
backup. The range is 0-9, with 9 providing the most detail. The Informix
instance uses the value that is specified in this variable, and it provides
debugging information according to the level specified.
■ BAR_DEBUG_LOG. This variable sets the location of the file to collect the
log. This should be the same location specified by MSGPATH in the Informix
configuration file, $ONCONFIG.
To set these variables, stop and restart the Informix instance, as follows:
■ For Informix version 7.X and 9.X, run the following Informix commands:

onmode -uky
oninit

■ For Informix version 8.X, run the following commands:

xctl onmode -uky


xctl -C oninit

4 Make sure the table bar_version in the sysutils database has the correct
value for the bar_version column. The value 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 use NetBackup for Informix on an IBM AIX platform.
Informix 7.3 and later releases require file infxbsa.so instead of infxbsa.a.
You can use the ar(1) command to extract infxbsa.so from infxbsa.a if
necessary.

Verifying NetBackup for Informix log files


Use the following procedure to verify that the log files are configured correctly.
Troubleshooting 57
Verifying NetBackup for Informix log files

To verify the NetBackup for Informix log files


1 Check the Informix instance log specified by MSGPATH in the Informix
configuration file $ONCONFIG.
2 Verify the existence of the following log directories:

/usr/openv/netbackup/logs/user_ops/dbext/logs
/usr/openv/netbackup/logs/infxbsa

The user_ops and infxbsa directories and any subdirectories should have
777 permissions. They must exist and be accessible for the applications to
operate correctly.
3 Examine the client logs in the following order:
■ The Informix server log. This path is specified in ONCONFIG.
■ OnBAR debug log. This path is specified in ONCONFIG.

■ The NetBackup for Informix debug log directory,


/usr/openv/netbackup/logs/infxbsa.If this directory was created
properly and no log is present, then stop. The absence of a file in a properly
created directory indicates a problem with the communication from
ON-Bar to NetBackup for Informix. This file is the starting point of
communication with NetBackup. Its absence indicates there are no further
NetBackup activities on either the server or client.
58 Troubleshooting
Verifying NetBackup for Informix log files

4 Examine other log files.


The following log files reside in the /usr/openv/netbackup/logs directories
on the servers indicated:

Master server bpcd, bpdbm, bprd

Media server bpbrm, bpcd, bpdm, bptm

Client /user_ops/dbext/logs, bpcd, bphdb, infxbsa

NetBackup writes a log file to


/usr/openv/netbackup/logs/user_ops/dbext/logs for each 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 log.mmddyy. or
mmddyy_nnnnn.log (if robust logging is enabled). These files may offer
additional debug information.
For example, the bprd log file shows if a backup or restore request from
bpbackup or bprestore was received. Examine the request’s details such as
client name, policy type, client type, and backup file name.
5 Examine the communication progress file.
The communication progress file logs communication between the NetBackup
server and the NetBackup client during backups and restores. This file is the
key file in the debugging process.
The following is an example of a progress file name:

/usr/openv/netbackup/logs/user_ops/dbext/logs/6749.0.1115233002

Perform the following steps to determine the communication progress file’s


name:
■ Use the cd(1) command to change to the
/usr/openv/netbackup/logs/infxbsa directory.

■ Use an editor to open the file in that directory.The following are examples
of file names: log.103105, 103105.00001.log.
■ Use an editor to open the log file and search for the communication
progress file’s name.
For example, search for the string openProgressFile.
The search flags the following lines in the file:
Troubleshooting 59
NetBackup debug logs and reports

13:56:42.905 [6749] <4> openProgressFile: entering openProgressFile.


13:56:42.905 [6749] <4> openProgressFile: commFull = </usr/openv/
netbackup/logs/user_ops/dbext/logs/6749.0.1115233002>

This output tells you that the communication progress file’s name is
6749.0.1115233002.

NetBackup debug logs and reports


The NetBackup server and client software let you enable detailed debugging logs.
The information in these log files can help you troubleshoot the problems that
occur outside of either the database agent or Informix ON-Bar.
Note the following with regard to these logs:
■ These logs do not reveal the errors that occur when Informix ON-Bar is running
unless those errors also affect NetBackup. Informix may (or may not) write
errors in the application to the NetBackup logs. Your best sources for Informix
error information are the logs provided by Informix.
■ Generally, each debug log corresponds to a NetBackup process and executable.
Information about the debugging log files is available.
See the NetBackup Troubleshooting Guide.
Also refer to the following file:

/usr/openv/netbackup/logs/README.debug file
60 Troubleshooting
NetBackup debug logs and reports

Enabling the NetBackup for Informix logs


Enabling the NetBackup for Informix database agent logs manually (UNIX)
1 Create the following directories on the client:

/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
chmod 777 /usr/openv/netbackup/logs/infxbsa

For example:

cd /usr/openv/netbackup/logs
mkdir bphdb

2 The user_ops, each of the log directories, and any subdirectories should have
777 permissions. They must exist and be accessible for the applications to
operate correctly.
For example:

chmod 777 bphdb

See “About permissions for NetBackup for Informix log files (UNIX and Linux)”
on page 39.
3 Enable logging for the nbpem, nbjm, and nbrb scheduling processes that 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.
Information on how to use logs and reports is available.
See the NetBackup Troubleshooting Guide.

About the NetBackup for Informix log files


The following topics describe the logs that are created when you create the log
directories. Use a text editor to view the contents of the logs.
See “ About the bphdb directory on the UNIX database client” on page 61.
Troubleshooting 61
NetBackup debug logs and reports

About the bphdb directory on the UNIX database client


The /usr/openv/netbackup/logs/bphdb directory contains logs.
The following types of logs exist:
■ onbar_stdout.mmddyy

Unless it is redirected elsewhere, NetBackup writes ON-Bar script output to


this file.
■ onbar_stderr.mmddyy

Unless it is redirected elsewhere, NetBackup writes ON-Bar script errors to


this file.
■ log.mmddyy

This log contains debugging information for the bphdb process. bphdb is the
NetBackup database backup binary. It is invoked when an automatic backup
schedule is run. NetBackup for Informix uses this client process for ON-Bar
script execution.

About the infxbsa directory on the NetBackup for Informix


client
The /usr/openv/netbackup/logs/infxbsa directory contains execution logs.
The following execution log exists:
■ log.mmddyy

This log contains debugging information and execution status for the
NetBackup for Informix client process.

About NetBackup server reports


NetBackup provides other reports that are useful in isolating problems. One such
report is All Logs Entries on the server. Information on server reports is available.
See the NetBackup Administrator’s Guide.

About Informix ON-Bar utility logs


The Informix ON-Bar utility performs its own error logging and tracing in the file
specified by BAR_ACT_LOG in the $INFORMIXDIR/etc/ONCONFIG file. Database
administrators can use this log file to determine what happened during ON-Bar
execution.
62 Troubleshooting
Setting the debug level on a UNIX or Linux client

Setting the debug level on a UNIX or Linux client


To control the amount of information that is written to the debug logs, change
the “Database” debug level. Typically, the default value of 0 is sufficient. However,
Technical Support may ask you to set the value higher to analyze a problem.
The debug logs are located in /user/openv/netbackup/logs.
To set the debug level on a UNIX or Linux client
◆ Enter the following line in the bp.conf file.

VERBOSE = X

Where X is the debug level you want.

Minimizing timeout failures on large database


restores
Large database restores sometimes fail when multiple restore sessions compete
for resources. In this situation, a restore session can be delayed while waiting for
media or device access. If the delay is too long, the restore session times out. Use
the following procedure to minimize session timeouts and to allow the restores
to complete successfully.
To minimize timeout failures on large database restores
1 In the NetBackup Administration Console, expand NetBackup Management
> Host Properties > Clients
2 Set the Client read timeout property to a large value.
The default for the Client read timeout setting is 300 seconds (5 minutes).
For database agent clients, increase the value significantly from the
recommended value.
See the NetBackup Administrator’s Guide, Volume 1.
For example, change this setting to 30-60 minutes to minimize timeout errors.
3 Click OK for each client.
Troubleshooting 63
Minimizing loading and unloading of tapes for database backups (UNIX and Linux)

Minimizing loading and unloading of tapes for


database backups (UNIX and Linux)
You can minimize excessive unloading and reloading of tapes between
multistreamed database backups by making changes on the NetBackup media
server.
To minimize loading and unloading of tapes
◆ In the /usr/openv/netbackup/bp.conf file on the NetBackup media server,
add the following options:
■ MEDIA_UNMOUNT_DELAY.

■ MEDIA_REQUEST_DELAY. Use this variable only with non-robotic drives,


such as tape stackers.

About deleting expired backups from the Informix


backup database
The following topics describe how to delete expired backup images.

Informix versions XPS 8.x and IDS 9.x


onsmsync is an Informix version XPS 8.x, IDS 9.x utility that synchronizes the
NetBackup catalog with the Informix backup catalog. Use the onsmsync utility to
delete images from both Informix backup catalogs and NetBackup catalogs. For
information on the onsmsync utility, see your Informix documentation.

Informix version IDS 7.x


Informix version IDS 7.x does not have a mechanism for deleting records of expired
backups from its backup database. NetBackup for Informix provides a script that
can delete these records from the Informix backup database if the NetBackup
image database has expired the backups. Run execute the following command as
user informix or the Informix Administrator.

/usr/openv/netbackup/ext/db_ext/informix/scripts/infx_remove_expired_images

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.
64 Troubleshooting
About deleting expired backups from the Informix backup database
Index

A bp.conf
Application Backup schedule administrator 63
environment variables 37 client 38
overview 27 overview 38
application backup schedule bphdb
configuring 25 log 61
overview 25 process
retention 26 sequence of operation 14
automatic backup bplist command 45
create scripts 33 browsing backups 45
manual backup 45
policy 45 C
automatic backup schedule client read timeout property 62
configuring 26 clients list, for backup policies 29
Automatic Full Backup schedule 26–27 commands
Automatic Incremental Backup schedule 27 bplist 45
onbar 12–14, 45–47
B onmsync 11–12
backup media required 16 communication progress file 58
Backup Selections list compatibility information 16
adding selections 30–31
overview 30 D
backups daemons
automatic see processes 60
configuring scripts 33 debug logs
automatic using scripts 45 accessing 60
expired enabling 59
deleting from Informix 63 in /usr/openv/netbackup/logs 58, 60
logical log 44 troubleshooting with log files 59
ON-Bar types 44
performing database backups 44
strategy 44
E
backups, automatic environment variables 37
running manually 40 error
BAR_ACT_LOG log file 14 script name 33
BAR_BSALIB_PATH variable 19, 55
BAR_DEBUG variable 56 I
BAR_DEBUG_LOG variable 56 Informix home path 18
BAR_RETRY parameter 19 Informix ON-Bar utility
bar_version table 19 overview 11
INFORMIXDIR/etc directory 32
66 Index

infxbsa library 19 onbar command (continued)


installation performing backup 45
adding a license key 17 performing restore 46
requirements for NetBackup clients 17 physical restore 47
requirements for NetBackup servers 16 sequence of operation 14
instances, adding 19 OnBAR debug log 57
ONCONFIG 19, 55, 57
J onsmsync utility 11–12, 63
Java interface 22
P
L policy configuration
adding clients 29
level 0 (full) backup 44
attributes 24
level 1 (incremental) backup 44
backup selections list 30
level 2 backup 44
for databases 23
license keys, adding 17
Informix-On-BAR 23
log files
overview 22
also see debug logs 58
schedules 25
BAR_ACT_LOG 14
Standard 32
logical log backups 44
testing 40
logs
processes
OnBAR 57
log files for NetBackup processes 60
scheduling (nbpem
M nbjm. See nbrb
manual backups 45
maximum jobs per client 39
multi-streamed backups 63
R
remote folder button 31
multiple copies feature 29
reports 59
multiplexing
See also log files
overview 10
All Log Entries report 61
NetBackup server reports 61
N restoring
nbjm scheduling process 60 redirected 47
nbpem scheduling process 60 user directed 46
nbrb scheduling process 60 robust logging 60

O S
ON-Bar schedules
also see onbar command 13 adding 25
backup types supported 44 automatic backup 45
script frequency 28
overview 13 properties 28
used in backing up 45 types of schedules 25
utility scripts
overview 11, 13 cautions regarding usage 33
script 12 examples 33
onbar command modifying 34
overview 12–13 ON-Bar 12
Index 67

scripts (continued)
scheduler 45
type of operation 33
sysutils database 19

T
testing policy configuration 40
timeout failures
minimizing 62

U
unified logging 60

W
Windows interface 22

You might also like