HP NonStop RDF, Руководство по управлению

Страница: 71 / 478

The backup system should also have copies of the following files in case an RDF takeover
operation is necessary:
• OBEY command files and TACL scripts containing NonStop SQL/MP or NonStop SQL/MX
DDL commands that define the database
• SQLCI or MXCI report definitions
To make it easy to compare catalogs on the primary and backup systems, it is strongly
recommended that you register objects protected by RDF in separate catalogs from objects not
protected by RDF. Either all the tables in a catalog should be protected or none of the tables
should be protected.
Every NonStop SQL object maintained on the backup system must be registered in a catalog,
even if the object is not protected by RDF.
Synchronizing the Primary and Backup Databases
For databases to be synchronized in an RDF environment, the database on the backup system
must be logically identical to the database on the primary system. There are two ways to
synchronize your databases: offline and online. This topic covers offline database synchronization.
For a description of online database synchronization, see
Chapter 7 (page 167) .
To ensure consistency between the primary and backup databases, you should copy the primary
database to the backup system before RDF updating starts. The most effective way to synchronize
the databases follows:
1. Stop TMF auditing on the primary system by turning off the applications and stopping TMF.
2. Create a copy of the primary database on the backup system.
The tools for synchronizing databases on NonStop systems are:
• The TACL OBEY command enables you to create the same database structures on the primary
system and the backup system by using commands in an EDIT file to create reusable TACL
macros and routines.
• The SQLCI or MXCI CREATE CATALOG command can re-create NonStop SQL/MP or
NonStop SQL/MX catalogs on the backup system.
• The SQLCI or MXCI DUP utility can copy NonStop SQL/MP or NonStop SQL/MX objects
and Enscribe files from one system to another.
• The BACKUP and RESTORE utilities can copy NonStop SQL/MP or NonStop SQL/MX
objects and Enscribe files to and from tape.
• The FUP DUP command can copy Enscribe files from one system to another.
• The NonStop Autosync product can replicate all application programs and files other than
your RDF database.
Backing up partitioned files requires some extra planning, as explained in “Synchronizing
Partitioned Files” (page 74) .
For a complete discussion of synchronized versus unsynchronized databases and their
ramifications, see
“Understanding Database States” (page 157) .
Re-Creating an Empty Database With an OBEY Command
If a database on the primary system does not contain any data yet, use either an OBEY command
file or a TACL macro to re-create the database on the backup system.
To create logically identical database structures on the primary and backup systems, first do the
following at the primary system:
1. Place the database creation commands in either an EDIT (command) file or TACL macro
or routine. See the TACL Reference Manual for more information.
2. Through the TACL command interpreter, issue an OBEY
filename
command or run the
macro to create the primary database.
Preparing the Backup System 71