Migrating the configuration database, Migrating an autosync source system, On the existing source system – HP NonStop G-Series User Manual
Page 239: On the new source system
Operations and Management
HP AutoSYNC User’s Guide—522580-020
A-17
Migrating the Configuration Database
3. When primary processing has been switched back to \P and \B becomes the
destination system again, re-allow \B to accept synchronizations from \P on \B:.
Migrating the Configuration Database
The AutoSYNC configuration files and tables are described above in paragraph
AutoSYNC Configuration Database
. The information stored in database tables
references local file names, system names and system numbers. As a consequence,
the replication of the configuration database to another system cannot be automated.
This section describes how to migrate the AutoSYNC configuration database to a new
system.
Migrating an AutoSYNC Source System
On the Existing Source System
1. Capture MapDB and Monitor information to use as reference when setting up the
new environment:
2. Capture the global parameter configuration:
3. Capture the syncuser configuration:
4. For each configured syncuser, capture configured syncfilesets:.
On the New Source System
1. Install AutoSYNC as described in
When creating the new MapDB, use the INFO MAPDB output collected in infom as
a reference.
2. Authorize Autosync, using the STATUS MONITOR output collected in infom as a
reference.
FROM \P;
OUT infom;INFO MAPDB,DETAIL;STATUS MONITOR *;
OUT infog;INFO GLOBALS,OBEYFORM;INFO LOCALS,OBEYFORM;
OUT infou;INFO SYNCUSER,OBEYFORM;
OUT inggguux;INFO BATCHID *,USER ggg,uux,OBEYFORM;
OUT inggguuy;INFO BATCHID *,USER ggg,uuy,OBEYFORM;
...
OUT inggguuz;INFO BATCHID *,USER ggg,uuz,OBEYFORM;