Administering CN - CN Replication

Metacat Replication

Metacat Replication is used to copy objects that have been copied to |CN|s during the synchronization process. Currently (Version 1 and 2 ofthe infrastructure), this is limited to objects of type METADATA and RESOURCE.

It will sometimes be necessary to trigger Metacat Replication when it is noticed that content on a Coordinating Node is not present.

To trigger Metacat Replication, visit the Coordinating Node at the admin URL:

/metacat/admin

then click on “Reconfigure Now” for “Replication Configuration”. This should open the page:

/metacat/admin?configureType=replication
../../_images/mc_replication.png

Click on the “Get All” button to initiate Metacat Replication. The only acknowledgement is a message “‘Get All’ Done” in the frame at the bottom of the page. In order to actually see what’s going on it is necessary to take a look at the Metacat log on the respective CN.

DataONE Replication

This is a CN service that manages MN to MN replication.

LDAP Replication

TBD

Postgres Replication

TBD

Hazelcast Replication

TBD

This material is based upon work supported by the National Science Foundation under Grant Numbers 083094 and 1430508.

Any opinions, findings, and conclusions or recommendations expressed in this material are those of the author(s) and do not necessarily reflect the views of the National Science Foundation.