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

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

2. Purge the RDF control subvolume and then issue an INITIALIZE RDF command of the
following form on the primary system:
INITIALIZE RDF, BACKUPSYSTEM \system, SYNCHDBTIME ddmmmyyyy hh:mm
For the timestamp, follow the guidelines for the INITTIME option.
3. Configure RDF and then issue a START RDF, UPDATE OFF command on the primary
system.
4. Make a copy of your table using one of the following two methods:
•
Method 1
Create the entire duplicate table on your backup system with a temporary name at a
temporary location (such as \BACKUP.$DATA.DUP.PART).
The alternative is to create the duplicate table on the primary system at a temporary
location (such as \PRIMARY.$DATA.DUP.PART).
If the table whose primary partition needs to be synchronized has indexes, do not create
indexes for the duplicate table.
Use the SQLCI LOAD command with the SHARED option to load the entire table.
Again, with relative tables, you must load the entire table.
• Method 2
Take on online dump of the specific partition that you to resynchronize, and then
perform a TMF FRNL operation to put that copy on a different volume. In this example,
use MAP NAMES to recover it as $DATA.DUP.PART.
5. When you have completed Step 4, issue the RDFCOM STOP SYNCH command.
6. When the load has completed, issue the RDFCOM STOP SYNCH command.
7. If you created the duplicate table on the primary system, then use the BACKUP utility to
put the entire duplicate table with all partitions onto tape.
If you created the duplicate table directly on the backup system, skip this step.
8. If you created the duplicate table on the primary system, then use the RESTORE utility to
put the entire duplicate table with all its partitions onto disk on the backup system. You
must use MAP NAMES to correct the system name. $DATA.DUP.PART is now on the
backup system.
If you created the duplicate table directly on the backup system, skip this step.
9. Rename the original table on the backup system whose primary partition is being
synchronized to a temporary name using the SQLCI ALTER TABLE command
($DATA.TEST.PART becomes $DATA.TEMP.PART).
10. Rename the duplicate table on the backup system to the name of the original table whose
partition is being synchronized using the SQLCI ALTER TABLE command
($DATA.DUP.PART becomes $DATA.TEST.PART).
11. Use the BACKUP utility with the PARTONLY option to back up just the partition you need
synchronized to tape (the primary partition, in this example). Remember that the duplicate
table now has the name of the original table. Thus, you now have on tape the loaded partition
that you need to synchronize. Because it has the correct name, you will not need to use MAP
NAMES when you eventually restore it.
12. Rename the duplicate table back to its original duplicate table name ($DATA. TEST.PART
becomes $DATA.DUP.PART).
13. Use SQLCI to drop the duplicate table. By renaming the duplicate table back to its original
name before dropping it, you can preserve whatever indexes exist on the backup system
that are associated with the table being synchronized.
182 Online Database Synchronization