Privilege Manager Disaster Recovery
Any disaster recovery plan needs to include contingency plans for the event when a company's data center goes down. as such, it should always include storing backups of the latest web application and database offsite, potentially at multiple locations.
For Privilege Manager web application backups, Delinea recommends creating a copy following any install/upgrade. For the database backups, SQL database backup recommendations should be followed.
Maintaining Privilege Manager in a Disaster
With Privilege Manager environments three types of Disaster recovery strategies can be implemented. The framework of a solid Privilege Manager Disaster Recovery Plan should follow these methods of maintaining operations:
- manual backups to restore (restoring/rebuilding from backup)
- passive failover (built and ready, but with a few manual switches)
- active fail-over via High Availability setup. Privilege Managers licensing allows for full clustering.
As a best practice for Privilege Manager databases, we recommend asynchronous replication. There are a lot of transactions - too many transactions for synchronous replication in most enterprise environments. Asynchronous replication works with a manual failover.
Simple Installation and Architecture
Privilege Manager operates on typical modern servers On-Premises, in the Cloud, and in virtual environments.
By design, Privilege Manager's installation is a quick and easy process. Keeping this process as quick and easy to install was a goal from the outset. This serves as a viable fallback option should redundancy plans fail. In a worst-case scenario where the host server fails, a cluster/mirror fails, and the other backup plans fail, Privilege Manager can be installed from scratch quickly and data imported from various methods.
Administrators familiar with Microsoft SQL and IIS can typically install Privilege Manager in about 30 minutes on a prepared server.
Refer to the following installation topics:
Restoring from Backup
Delinea recommends to make a back-up copy of your Privilege Manager web application folder after installation or following an upgrade. This back-up copy is used during disaster recover to restore the instance. Microsoft SQL database restores are simple as well, but require several steps, depending on the backup scenario. Refer to vendor details, such as Back Up and Restore of SQL Server Databases.
Start by preparing servers for installation. When the servers are prepared, restore the Privilege Manager application on one and the database on the other. Some specific web configurations may be needed to match the previous IIS settings.
Restoring Privilege Manager from a Backup
When restoring from backup in the single-server configurations, be certain to make copies of the backup files on a different device or media.
Follow instructions as detailed under Installing as a Virtual Directory.
High Availability
A Privilege Manager implementation based on a high availability setup plays well with any disaster recovery plan.
With HA clustering, there are more than one front-end web servers, and more than one active node. Allowing users to use Privilege Manager through more than one active node simultaneously requires enabling clustering within the application. Only one server handles background processes, meaning that one of the active nodes will be designated as the Primary Node at any given time (this can be changed manually, if necessary, in the application). In the event that the Primary Node becomes unavailable, the "Primary" status will be transferred to one of the other active nodes and users can continue using the application without interruption. There can be more than one active and passive server nodes (no limit), depending on the needs of the organization.
A Disaster Recovery Plan for High Availability consists of failover for Web Server or Microsoft SQL Server issues. If the failover members were to themselves fail, then Web Application Backups and Automated Application Database Backups can be used to restore functionality. If these Servers are virtualized, leveraging strategies such as making scheduled Snapshots or having a hot/cold Site may add additional layers of redundancy.
Refer to Privilege Manager High Availability Setup.
Summary & Additional Support Resources
The integration of Privilege Manager into Business Continuity Planning should not present any unique challenges beyond normal server and database recovery. If your organization already has disaster recovery plans for servers and databases, Privilege Manager and its Microsoft SQL database should fit within your organization's current framework. Using server virtualization to assist with Business Continuity and Disaster Recovery in terms of snapshots, replication, and other 3rd party features are recommended where applicable.