Hi @kousik.roy
Thanks for your question!
It looks like you already have Octopus set-up in your DR environment which is excellent! In case it’s useful, I wrote up a Knowledgebase article about that very topic here:
Adding your production servers as deployment targets to your DR Octopus will depend on how you have your DR Octopus configured in terms of replicating data from your production Octopus instance.
If it’s standalone and not connected in any way to your existing production octopus database (by way of database replication techniques such as Log Shipping) then you can add the production servers to the DR Octopus instance - either manually in the DR Octopus web portal, or by using the REST API and adding the machines in programmatically.
Having no connectivity to the production servers from your DR Octopus instance in the DR Site themselves isn’t an issue. To prevent Octopus from trying to connect to them in the DR site, you have a couple of options:
- Mark the machines as Disabled in the DR Octopus instance. This means they won’t be connected to and fail any machine policy health checks. The downside of this is that you will need to re-enable them when DR is invoked.
- Configure the machines to have a machine policy with machine Connectivity set to Unavailable deployment targets will not cause health checks to fail.
If you do add your production servers to your DR Octopus instance, be sure to remember the Tentacles to trust both your Production and DR Octopus instances, since they may have different Server Thumbprints. In addition for any software which is deployed to them, ensure they have the matching target roles, environments and tenanted setup if applicable.
I hope that helps!