http://www.thycotic.com/forums/messages.aspx?TopicID=382 Thycotic Community - Secret Server - Unique DR situation when using clustered front ends - Messages en-us http://blogs.law.harvard.edu/tech/rss Jitbit AspNetForum Thu, 11 Aug 2011 13:42:52 GMT Thu, 11 Aug 2011 13:42:52 GMT http://www.thycotic.com/forums/messages.aspx?TopicID=382
The DB connection reset process only changes the database.config file so copying only that file will be sufficient assuming that the two nodes had identical copies of the production Secret Server web folder before performing the DB connection reset.

The only reason that this wouldn't work is if the DR database was the same server as the primary DR web server and you entered localhost in the database configuration. In that case you would have to go through the process to set the database connection on the secondary node in order to point it to the correct machine.

Kind Regards,

Jacob Stucky
Thycotic Support]]> Thu, 11 Aug 2011 13:42:52 GMT http://www.thycotic.com/forums/messages.aspx?TopicID=382
What we'd like to do is use a standby SecretServer cluster at our DR site. This cluster has been set up in IIS on both nodes, and has had the production SecretServer folder copied over to both DR nodes.

When restoring the production database to our DR site's SQL server, I understand we have to delete the database.config file and then run the installer on the DR site's SecretServer, pointing it at our DR SQL server. The next step is unclear: do we then copy the newly generated database.config file from the primary node to the secondary, and all is good? Or should we be copying the entire contents of the SecretServer folder to the secondary node?

Dustin]]> Thu, 11 Aug 2011 12:46:37 GMT