Migration steps for an autosync destination system, On the existing destination system, On the new destination system – HP NonStop G-Series User Manual
Page 225
Operations and Management
HP AutoSYNC User’s Guide—522580-015
A-17
Migration Steps for an AutoSYNC Destination
System
•
Validate the new configuration using the INFO GLOBAL, INFO SYNCUSER
and INFO SYNCFILESET commands.
•
Proceed with your usual testing suites, using one time syncs, the REPORT
command and activating syncfilesets progressively.
Migration Steps for an AutoSYNC Destination System
On the Existing Source System
Moving a destination system requires updates to the syncfileset definitions on the
source system.
1. Capture the syncfileset configuration information for each syncuser as described in
Steps 4 described in paragraph
above.
2. From the captured output, create ALTER SYNCFILESET command files to make
the necessary updates to the syncfileset configurations:
•
To retarget the synchronizations to the new system and file names.
•
If synchronization is done over a TCP/IP connection, to update the host name
or IP address of the destination.
On the Existing Destination System
1. If triggers on the source system invoke or reference macros, scripts or programs
on the existing destination system, move the files to the new system. See
examples
and
on page 6-3 for cases where on the
destination system are used in the execution of a trigger.
2. If a private copy of RESTORE is used by the destination sync process, move the
private copy of RESTORE to the appropriate location on the new destination
system.
3. Move mapnames files that reside on the existing destination system to the new
destination system, in the correct location and update their content to reflect the
new mappings between source and destination.
On the New Destination System
1. Perform Step 1, Step 2 and Step 3 described in paragraph
2. Test the new installation:
From the source system, use one-time syncs, the REPORT command and activate
your syncfilesets progressively.