Disaster Recovery 101: Part 2
So you’ve taken measures to protect and preserve your information – now how do you restore it in a disaster? Part 2 of our Disaster Recovery series explains how you can quickly restore a working copy of Secret Server in the case that your primary instance of Secret Server fails.
Note that the following steps assume you have copies of:
- Your application files directory
- Your SQL database (.bak file)
For a quick review of backups and other Disaster Recovery tips we’ve covered so far, see Disaster Recovery Part 1.
Configure your Backup Server
The application files you backed up will need to run in IIS on your backup server. If you’ve already configured this on your backup server in advance, you can skip to the Restore your Backups section, below. Otherwise, refer to our Installation Guide to follow instructions for enabling IIS in Windows.
Ensure that you also have .NET Framework 4.5.1 or 4.5.2 installed if you are using Secret Server 8.5 or higher. See Installing the .NET Framework 4.5.1 for installation instructions and a link to the installer.
SQL Server will be required if you are also setting up your database on this server. The alternative is to put your database on another server and point the Secret Server application on your backup server to that existing database. See our Installation Guide for detailed information about installing and configuring SQL Server.
Restore your Backups
- Application Files: If your application files are zipped, unzip them first. The default file location is C:inetpubwwwroot, but you can place the folder anywhere you like on your backup server. Add your site back to IIS using the instructions in the Manual Installation section of our Installation Guide. This is where it’s important to know how your primary environment was configured, including which account was running the application pool and whether Secret Server was a website or virtual directory.
- Database: In SQL Server, restore your .bak file by right-clicking the Databases folder and selecting Restore. Once the database has been restored, ensure that the account you used to access the database in your primary environment also has the ability to access this SQL Server instance. For details on how to do this, see the SQL Server section of our Installation Guide.
Test the Website
Browse to the Secret Server website, which should now be running on your backup server, and confirm you can log in. You will be required to activate your licenses, which can be done by navigating to Licenses from the Administration menu in Secret Server. If you run into any errors during activation, please contact our Technical Support team for assistance.
Another common error encountered during backup restoration is a message stating that the current node is not “primary.” To resolve this, select Server Nodes from the Administration menu and then click “Make current node primary.”
Share your feedback
Have you run into unusual Disaster Recovery scenarios, have questions about a specific case in your environment, or just want to provide some feedback? Share your ideas in our Forums, suggestions at our Customer Feedback page, or submit a ticket with our Support team.
Latest posts by Thycotic Team (see all)
- Top 4 Password Blunders And How Thycotic Can Help - January 24, 2017
- Top 3 New Features in Secret Server 10.1 - January 18, 2017
- Security Metrics Must Tell a Story That is Relevant to Your Business - September 6, 2016