Your organization may require the implementation of disaster recovery for your Posit infrastructure.
*The following information is applicable to Posit Workbench, Posit Connect, and Posit Package Manager. It should be seen as a framework to build on, as opposed to a strict guide on how to setup a disaster recovery mechanism. Each organization has different requirements, so it's best to consult your infrastructure engineering teams for further advice.
Depending on your organizations use case, a high availability configuration will also assist in ensuring that your services remain available.
It's usually best to consult your Infrastructure team for such a request as this is formally outside of Posit's support agreement. That said, the following information may prove helpful:
It helps that you have your server utilizing a separate database, as opposed to the default Sqlite3 database. In addition, hosting your infrastructure using a shared NFS/CIFS storage medium is ideal. Whilst a separate database and storage mechanism helps, it certainly is not a requirement. When your database is separate you can take a snapshot of the database and your shared storage to use with the recovery nodes. Depending on your RTO & RPO objectives, you can have the DR nodes in a warm standby by backing up & restoring your servers across the current infrastructure and letting it co-exist with the current production environment. Information on backup and restoration can be found here:
It's also worth considering licensing. You can use our license deactivation tool here to deactivate your licenses from the failed nodes:
This will force deactivate the licenses on your troubled nodes so that you can apply them to the recovery nodes.