Description:
When trying to start a EMSA instance, the server may fail with the message, "ERROR: Store '$sys.meta' on the active server has a different file name than on the standby server".


Symptoms:
When trying to start a EMSA instance, the server may fail with the message,  "ERROR: Store '$sys.meta' on the active server has a different file name than on the standby server".
Cause:
This can be caused by the addition of a new appliance unit to a an existing appliance setup with parameter values out of sync with the other appliance units. In this case, the new box uses an old template. (It defaults to the standard appliance model). For reference, it is worthwhile checking tibemsd.json on all instances for comparison.

EMSA

To resolve the issue what is needed is to export the tibemsd.json config from the working unit to the new unit. It is important that the JSON being imported is the one from the working peer.

On Working peer instance:

     export 0 config
     export 1 config

SFTP the tibemsd.json from the old machine ~tibfile  instance-0 and instance-1 directories to the new machine.

On the Peer being repaired:

Need to stop the server/servers before attempting to change the config.

EMS CLI > stop local

Apply changes (Accessed via support-enable menu)
    import-config 0 tibemsd.json -force
    import-config 1 tibemsd.json -force

Adding the -force option skips all preprocessing since it should be identical to its peer.

 EMS CLI >   start local

IMPORTANT NOTE: This procedure is for importing a JSON configuration to a standby server that is identical to the one already running on the active instance’s server.  Attempting to import a modified JSON on the standby using this procedure will not behave as expected.

EMSA instance start up failure, "ERROR: Store '$sys.meta' on the active server has a different file name than on the standby server".