SQL/MX 2.x Installation and Management Guide (G06.24+, H06.03+)

Planning Database Security and Recovery
HP NonStop SQL/MX Installation and Management Guide—523723-004
5-30
Frequency of Backups
Frequency of Backups
Although you cannot know with certainty whether you will ever need to use your
backup tapes, you should schedule backups regularly as a general precaution. In
addition, you should back up affected volumes or possibly the entire system when
special events take place, such as equipment changes, configuration changes, and
major software changes.
OSS program
executable file or
user module
Does not automatically back up
program executables or user
modules. You back up program
files or executables by
specifying OSS backup objects.
See Backing Up and Restoring
Program Executables and User
Modules on page 5-35.
Use OSS backup objects to
restore program executables or
user modules in one or more sets
of OSS directories and
subdirectories.
Trigger A trigger is automatically
backed up when you back up
the associated catalog,
schema, or table.
A trigger cannot be restored with
Backup and Restore 2. To restore
a trigger, run the OBEY command
file for the trigger generated by
the RESTORE SHOWDDL ON
command. See Using the
RESTORE SHOWDDL ON
Option to Re-Create Objects on
page 5-36.
View A view is automatically backed
up when you back up the
associated catalog or schema.
A view cannot be restored with
Backup and Restore 2. To restore
a view, run the OBEY command
file for the view generated by the
RESTORE SHOWDDL ON
command. See Using the
RESTORE SHOWDDL ON
Option to Re-Create Objects on
page 5-36.
Note. You can use the BRCOM BACKUP command to back up all supported SQL/MX objects
(all catalogs and all subordinate objects) on your system with the “CAT[ALOG] *” SQL/MX
object specification.
Table 5-2. Backup and Restore of SQL/MX and OSS Objects (page 3 of 3)
SQL/MX or OSS
Object BACKUP Command RESTORE Command