For SQL backup strategies and options, including guidelines for performing daily and periodic
backups, and using the FROM CATALOG, PARTONLY, and INDEXES options, see the SQL/MP
Installation and Management Guide.
CAUTION:
BACKUP is normally used as a secondary recovery method for SQL objects; TMF
recovery operations are used as the primary method. An SQL object recovered with RESTORE
might be inconsistent with the current catalog description of the object.
•
When a base table is backed up with PARTONLY OFF and INDEXES IMPLICIT:
Any SQL protection views defined on the table are backed up automatically. You should
not explicitly name protection views in the backup files.
◦
◦
Constraints and comments associated with the table are backed up automatically.
◦
An SQL shorthand view is not backed up unless it is explicitly named in
backup-files.
•
You must use BACKUP to archive nonaudited SQL tables.
NOTE:
SQL tables can be backed up only if the program file from BACKUP is licensed.
Licensing occurs automatically if you use the DSM/SCM to install BACKUP. If you do not use
DSM/SCM, you can use the FUP LICENSE command to license the program file.
•
By default, BACKUP and RESTORE do not back up and restore SQL catalogs. Use the
SQLCATALOGS ON option to back up and restore catalogs. (An SQL catalog is a set of
tables containing the descriptions of SQL objects.)
Always use BACKUP to back up SQL objects, but only use the SQLCATALOGS ON option to
dump all SQL catalogs when reporting a problem to HP support.
•
BACKUP and RESTORE do not work with remote SQL tables if SQL is not installed on the local
node.
•
To provide a create-like function for multiple partition SQL objects, use the BACKUP
NOSQLDATA option followed by RESTORE MAP NAMES. The resulting SQL object is an
empty copy of the original.
•
In case of disk failure, use the VOLUMEMODE option of BACKUP and RESTORE to replace
any volumes containing SQL catalogs, if possible. Use this option to restore SQL files only if
the SQL objects have not changed since they were backed up.
CAUTION:
Under normal conditions, to ensure that BACKUP and RESTORE handle all related
objects together and avoid inconsistencies, use BACKUP with the default options PARTONLY OFF
and INDEXES IMPLICIT.
When necessary, use the PARTONLY and INDEXES EXPLICIT options to back up or restore individual
SQL components of a set of related objects (files), such as the individual partitions of a partitioned
table or indexes of SQL tables. Use these options carefully:
•
The consistency checking that BACKUP and RESTORE perform to validate the data during
these procedures does not ensure the data consistency of SQL objects.
•
If you use options from BACKUP and RESTORE incorrectly, you can cause the primary data
to be inconsistent with the alternate indexes. For example, a base table can be inconsistent
with its indexes and left invalid after a RESTORE process when PARTONLY ON or INDEXES
EXPLICIT is specified. Use these options with extreme care.
BACKUP Guidelines and Examples
75