Synchronizing the alternate master's NIM database

Edit online

You can synchronize the NIM database for the alternate master using SMIT or from the command line.

In this scenario, master A is configured as a NIM master and has objects, such as clients and resources, defined. Master B is initialized as an alternate master, but its database does not match that of master A. You can use the sync operation to synchronize the NIM database on master B with master A's database. The sync operation backs up master A's database, restores it onto master B, and then ensures that all the object definitions are consistent.

You should consider the following issues when synchronizing the alternate master's NIM database:
  • The resources served by master A are removed from the database when it is restored on master B.
  • Object definitions are reset when the database is restored on master B.
  • After the database is restored on master B, master B does not control any NIM objects until you perform the takeover operation. As a result, master B can not run any NIM operations to any objects in its database.