Topic
If a disaster recovery for RPA LE Central is desired where the plan is to fail over the server for RPA Central to a DR location along with the SQL server that houses the RPACentralKeys and RPACentralWeb databases.
While performing a test of this Disaster Recovery process, please note, the Nintex RPA Central service should not be turned off if any instances are running when testing. Instead, wait for the running instances to complete before performing the test.
Instructions
Normally creating a backup of the RPA Central databases and also creating regular backups of your botflows by bulk exporting from the Bot is an easy way to preserve your botflows and other information. Please see link below for more information.
If SQL Server is used, to perform a Disaster Recovery like mentioned above, here are some things to keep in mind:
First back up the RPAC database files after turning off the Nintex RPA Central service.
For Disaster Recovery, if the backup machine is an exact clone of the machine such that it's already activated on the DR machine with the same key, then the RPAC machine can just be completely shut down.
Then boot up the DR backup machine and it should just work.
If the backup machine is a different machine, then please reach out to Support@Nintex.com so that we can deactivate the license key (assuming this is a simulation of an unexpected crash of the RPAC server in which case deactivating the key by uninstalling it from the RPAC Server would not be possible).Then restore the backed up RPAC DB files, activate the licenses on the new machine. Then bind it to a security certificate so remote bots can connect to the new RPAC Server.
Additional Information
Please see the link below for more information:
