Troubleshooting the content sync issue across instances

Syncing of the content containing sensitive data across multiple TrueSight Network Automation instances fails. For example, you cannot push the content containing sensitive data from one instance to another using Multi-Server Administration, or you cannot export content from one instance to another.

This issues occurs when the instances in use have different encryption keys. Each TrueSight Network Automation instance has its own encryption key. For the sync to be successful, the keys across instances need to be the same.

Fix

If you have done a fresh installation of version 20.02 on both the instances, do the following:

1. Log on to one of the TrueSight Network Automation instances.
2. Navigate to the BCA-Networks-Data directory and copy the keystore.jceks file.
3. Log on to the second instance.
4. Navigate to the BCA-Networks-Data directory and overwrite the keystore.jceks file.
5. Run the installation program again on the second instance.

If you have upgraded one instance to version 20.02 and yet to upgrade the second instance, do the following:

1. Log on to TrueSight Network Automation instance that you have upgraded.
2. Navigate to the BCA-Networks-Data directory and copy the keystore.jceks file.
3. Log on to the second instance.
4. Navigate to the BCA-Networks-Data directory and paste the keystore.jceks file.
5. Upgrade the second instance.