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-31
Backup Objects Hierarchy
Daily Backups
To provide a high degree of protection, you can use Backup and Restore 2 to perform
daily backups. Then the maximum amount of data lost from a failure never exceeds
one working day.
A daily backup should either be a full backup of all database objects or a limited
backup of specific objects. If you use limited daily backups, you should also perform
periodic full backups, as explained in Periodic Full Backups.
Periodic Full Backups
A full backup performed periodically might be adequate for protecting your database.
The time between periodic backups should not exceed the maximum amount of work
that would be acceptable to lose or redo if a catastrophic failure occurred.
This command performs a full backup on all database objects:
BR> BACKUP $tape-drive, (MX(CATALOG*));
Daily Timestamp Backups
For large databases, a full backup can be inefficient. For some applications, the
amount of change to database files is uneven. Some files might change frequently,
while other files seldom change from day to day.
BACKUP provides a mechanism to perform a partial backup automatically on only
those files that have changed since the last backup date. You can filter certain objects,
such as files with a specified user ID, files created or modified within a certain
timestamp expression, or files with a certain file code. By using the WHERE
expression, you can back up only SQL/MX files that have been modified from a certain
date.
If you perform partial backups, you must perform a full backup periodically to ensure
that all files have been saved.
This example uses a qualified file set list to restrict the backup to files that were
modified since the date of the last full backup:
BR> BACKUP $tape-drive, (MX((CATALOG*) WHERE (MODTIME AFTER 10
JAN 2004)));
Backup Objects Hierarchy
For detailed information about the SQL/MX object hierarchy supported by Backup and
Restore 2, see the Backup and Restore 2 Manual.