Troubleshoot Content Replication

When an object's content is stored in a filestore and is replicated to another filestore either by surrogate_get, manually, or scheduled content replication then prior to the replication, a dump of the content object must show the storage_id as being the distributed store. A dump of the dmi_replica_record will just show one component id for this content object.

After replication, a dump of the dmi_replica_record for this content object (data_ticket of content object is the same as the r_object_id_i of the dmi_replica_record) will show multiple component_ids (ids of the filestores) that it is stored in.
All the filestores, which are part of the distributed store will be listed as component_ids for the distributed store.


Useful information to obtain:

1. Get server.ini files from all locations

2. dump serverconfig objects
DQL: select r_object_id, r_object_id, object_name from dm_server_config
API> dump,c, for each serverconfig object

3. dump distributed store object

DQL: select r_object_id from dm_distributedstore
API> dump,c,

4. dump filestores in distributed store (component_ids from above output)

API> dump,c,

5. dump example object

API> dump,c,09001c808002ca6e

6. dump content of example object

API> dump,c,06001c808000af7a

7. Determine how many component IDs are associated with a replica - dump replica object for the replicated content object. Get the data_ticket from content object (previous dump) (data_ticket is -2147477618 in example below)

API> retrieve,c,dmi_replica_record where r_object_id_i = '-2147477618'
...
2d001c808000178e

API> dump,c,2d001c808000178e

After doing this you should be able to determine if the job is running successfully and if you are configured correctly. If it is not successfull then you need to look at the content replication job that is failing.

a) make sure content replication jobs were installed through the toolset.ebs
a) make sure user and password is on same line under arguments (for connect info to docbases).
b) trace job (10)
c) trace method