Introduction
SIRP provides robust Disaster Recovery (DR) functionality to ensure the continuity of your security operations with SIRP even in the face of unexpected outages or failures. This article aims to provide a comprehensive overview of how SIRP's DR functionality works, including its configuration, setup, and the two available options: Active-Passive clustering and in-platform backup.
Overview of SIRP's Disaster Recovery Functionality
SIRP's DR functionality is designed to ensure high availability and data integrity, allowing your security operations to continue seamlessly in the event of primary system failures. It operates in an active-passive manner, meaning there are primary and secondary nodes, where the secondary node synchronizes itself from the primary node. Here are the key points to understand about SIRP's DR functionality:
Active-Passive Configuration: SIRP's DR functionality is implemented using an active-passive cluster configuration. In this setup, there are two nodes: the primary and secondary. The primary node handles all processing, while the secondary node is on standby. The secondary node mirrors the primary's data and configurations, ensuring minimal downtime if the primary node becomes unavailable.
Hardware Specs: Ideally, the secondary machine should have the same hardware specifications as the primary machine to ensure smooth and seamless failover. This includes CPU, memory, storage, and network resources.
Connectivity Requirement: To maintain synchronization, there must be continuous network connectivity between the primary and secondary machines.
DR Configuration: The DR utility needs to be configured by the SIRP team upon request. This ensures that the setup aligns with your specific requirements and is properly integrated into your SIRP environment.
No Separate License: It's important to note that there is no need for a separate license for the DR machine, making it a cost-effective solution for ensuring business continuity.
Active-Passive Cluster Configuration
In an Active-Passive cluster configuration, the primary node performs all processing tasks. However, if the primary node becomes unavailable for any reason, the secondary node can be promoted to the primary status, allowing it to take over the IP address and responsibilities of the primary node. This failover mechanism ensures the uninterrupted operation of your security processes.
Key features of Active-Passive Cluster Configuration:
Primary Node: Handles all processing tasks under normal conditions.
Secondary Node: Remains on standby and synchronizes data and configurations from the primary node.
Failover: To be done manually when the primary node becomes unavailable. Apply the IP address of the primary node to the secondary node.
Redundancy: Provides redundancy and high availability while data is being replicated between nodes.
In-Platform Backup and Restore Option
SIRP SOAR also offers an in-platform Backup and Restore option to further enhance data protection and recovery capabilities. This feature allows you to schedule regular backups of core code, uploaded files, and configurations. These backups can be stored either within the SIRP appliance or remotely, providing you with flexibility and control over your data backup strategy.
Key features of the In-Platform Backup Option:
Scheduled Backups: You can schedule regular backups according to your specific requirements.
Backup Locations: Choose between storing backups within the SIRP appliance or uploading them to a remote location.
Data Covered: Backups include core code, customer files, and configurations, ensuring comprehensive protection of your SIRP environment.
Data Recovery: Import the backup files to restore to an older version
In conclusion, SIRP SOAR's Disaster Recovery functionality is a critical component of ensuring the continuity of your security operations. By using an active-passive cluster configuration and the in-platform backup option, you can minimize downtime, protect your data, and maintain high availability even in the face of unexpected disruptions. To set up and configure DR functionality, reach out to the SIRP team for assistance and further details.