Symantec Netbackup™ For Informix Administrator'S Guide: For Unix and Linux
Symantec Netbackup™ For Informix Administrator'S Guide: For Unix and Linux
Informix Administrator's
Guide
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.
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.
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:
Index .................................................................................................................... 65
Chapter 1
Introduction to NetBackup
for Informix
This chapter includes the following topics:
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
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.
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:
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.
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
Term Meaning
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.
Network (TCP/IP)
NetBackup software:
– NetBackup master server or media server
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.
/usr/openv/netbackup/logs/infbsa
■ Verifying the operating system and platform compatibility for NetBackup for
Informix
Step 1 Verify the installation prerequisites. See “Verifying the operating system and platform
compatibility for NetBackup for Informix” on page 16.
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.
■ 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.
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.
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:
■ About permissions for NetBackup for Informix log files (UNIX and Linux)
Step 2 Configure NetBackup for Informix See “About NetBackup for Informix
scripts. scripts” on page 33.
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.
■ 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.
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.
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.
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.
■ 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
Retention 2 weeks
00:08:00 - 22:00:00
Table 3-4 Example settings for NetBackup for Informix automatic backup
schedules
Table 3-4 Example settings for NetBackup for Informix automatic backup
schedules (continued)
18:00:00 - 22:00:00
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.
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
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.
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.
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
/backup_scripts/db/cold_backup.sh
3 Add a schedule.
Provide the following information.
Retention Set the time period that is needed to retain two full backups
of your database.
Start Window Set the time of day when you want backup operations to be
available to the user.
/usr/openv/netbackup/ext/db_ext/informix/scripts
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
vi informix_onbar_backup_of_rootdbs
Configuring NetBackup for Informix 35
About NetBackup for Informix scripts
#!/bin/sh
# Replace xxxxx below with the extention used for your onconfig file.
ONCONFIG=onconfig.xxxxx
# 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
export ONCONFIG
echo "exported ONCONFIG"
export INFORMIXDIR
echo "exported INFORMIXDIR"
export INFORMIXSERVER
echo "exported INFORMIXSERVER"
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
fi
exit $RETURN_STATUS
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:
/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
informix policy The name of the Informix-ON-Bar policy that was configured in the
backup policy.
NetBackup uses the bp.conf file in the Informix user’s home directory only for
backups and restores initiated by this Informix user.
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.
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 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.
onbar -l -s
cd $INFORMIXDIR/etc
Performing backups and restores of Informix 47
Redirecting an Informix restore to a different client
/usr/openv/netbackup/bin/jbpSA &
4 Use onbar to logically restore the dbspaces that you physically restored.
For example:
onbar -r -l
/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
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
onbar -r -p
onbar -r -l
■ DBSERVERNAME is srcdb
■ DBSERVERNAME is destdb
export INFXBSA_SERVER=lion
■ sqlhosts
■ onconfig
■ oncfg_srcdb.6
■ You salvaged the logical logs on camel by using the following command:
onbar -l -s
/usr/openv/netbackup/db/altnames/giraffe
■ ixbar.0
■ sqlhosts
■ onconfig
■ oncfg_destdb.0
export INFORMIXSERVER=srcdb
export INFXBSA_CLIENT=camel
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
onbar -r -p
echo $?
onbar -r -l
echo $?
■ Minimizing loading and unloading of tapes for database backups (UNIX and
Linux)
■ 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
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.
/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.
/usr/openv/netbackup/logs/user_ops/dbext/logs/6749.0.1115233002
■ 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
This output tells you that the communication progress file’s name is
6749.0.1115233002.
/usr/openv/netbackup/logs/README.debug file
60 Troubleshooting
NetBackup debug logs and reports
/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:
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.
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.
This log contains debugging information and execution status for the
NetBackup for Informix client process.
VERBOSE = X
/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
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