Hi everybody!
I need to shutdown sym server with a master node and start it on the other server.
Is there a way to accomplish this task with minimum settings and don't lose any replication data?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Shutting SymmetricDS down will not cause any loss of capture. Since it is trigger based the changes will continue to capture into sym_data.
You will want to copy the following items from the old server to the new server
- The security folder in SymmetricDS
- The engine file(s)
- The sync.url property in the master server engine file to represent the new server name
- The sync url column in the master servers database sym_node table to represent the new server name
- You may need to update the registration.url properties on all nodes that register against this node to have the new url for the master if they ever lost registration and needed to register.
- You could delete the entry in sym_node_host for the master so that it only contains the new entry. This is for informational purposes but would keep the information up to date.
- The property in the conf/sym_service conf that contains the keystore password
Also, bin/setenv and conf/sym_service.conf have a password to security/keystore that has the encryption keys for db properties in engines/x.properties files, so those files are all related and need copied together.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi everybody!
I need to shutdown sym server with a master node and start it on the other server.
Is there a way to accomplish this task with minimum settings and don't lose any replication data?
Shutting SymmetricDS down will not cause any loss of capture. Since it is trigger based the changes will continue to capture into sym_data.
You will want to copy the following items from the old server to the new server
- The security folder in SymmetricDS
- The engine file(s)
- The sync.url property in the master server engine file to represent the new server name
- The sync url column in the master servers database sym_node table to represent the new server name
- You may need to update the registration.url properties on all nodes that register against this node to have the new url for the master if they ever lost registration and needed to register.
- You could delete the entry in sym_node_host for the master so that it only contains the new entry. This is for informational purposes but would keep the information up to date.
- The property in the conf/sym_service conf that contains the keystore password
Also, bin/setenv and conf/sym_service.conf have a password to security/keystore that has the encryption keys for db properties in engines/x.properties files, so those files are all related and need copied together.