Functional requirement for Disaster Recovery Management Software

Disaster Recovery Management Software enables operational automation of the entire life cycle of the IT DR process, while masking the heterogeneous technology complexity.

The scope of the Disaster Recovery Management Software will be for the entire DR infrastructure that will be covered under this RFP.

The following features must be supported by Disaster Recovery Management software that will be used for Monitoring, DR Drills, Failover, SLA Reporting and Replication management for various applications that would be hosted in SDC.

“DR location for Punjab SDC will be (NIC Data Centre location to be confirmed at the later stage) who would be facilitating the DR activities in their Data Centre. The DR will be a Storage based replication from DC to DR., The replicator which will be positioned in the DR and will have the capacity to virtulize the backend storage on which NIC is giving 25TB initially. In future State may go beyond 25 TB space.

S

No Description

Compliance

1

Real time monitoring of Recovery Point Objective at database and application level.

DR solution health – real time monitoring of primary & DR subsystem health and alerts on DR solution

Provide alerts on event threshold conditions such as RPO deviation and replication log space full at application level and support policy based actions for these alerts

DR Manager dashboard – single dashboard to track DR readiness status of all applications under DR

2

Central console to start, stop & track recovery workflows for each application.

Report on number of steps and estimate of time for failover recovery for each application.

Automated failover of each application to the DR site with single click. A ready to use library of recovery automation actions for third party databases and replication products. This must significantly reduce custom development of scripts and speed deployment of DR solutions.

3

Central console to start, stop & track DR drill related workflows for each application.

Readymade, single click based automated switch-over and switch-back workflows for industry popular databases and replication products

Pre-flight check DR workflows to ensure conditions are met to ensure a successful drill

Automated drill reports with evidence of control and granular timing of each step.

4

Readymade reports on RPO deviation, RTO deviation, Datalag, Application DR readiness status, WAN utilization

Ability to create UI based custom reports. Data can be exported to popular reporting engines.

5

Built-in file replication that is not tied to a specific platform or OS for application environment protection with the following features:

 Replication from multiple sources to multiple destination files/folders and nested files & folders

 Preserves file attributes & option to skip or copy open files

 Maintain primary & DR equivalence. Files deleted on the primary will be deleted on DR

 Provides log of replicated file names, pending files and number of files to be replicated and statistics on throughput

 Support replication for Unix symbolic links

 Restart replication after a break from last successful replicated point

 Replicate only portions of the file that have changed  On the fly compression for reduced bandwidth

 Ability to provide alerts when specific files change on production systems

Notification using SMS and email and support for notification lists to handle groups of users at a time

The software must be able to integrate any application into its DR management framework in the field, for application environment and configuration monitoring

The software must provide GUI based application component dependency map across primary and DR sites so that failure identification is quick and easy

The software must provide monitoring and management capability for remote management.

The software must have the capabilities to be integrated with the major EMS systems.

The software must provide infrastructure/application based and role based access control to users to support large environments securely.

The software should provide single integrated management interface to meet all the disaster recovery management functionality

5 Support

The software must support major platforms including Linux, Windows, Solaris, HPUX, and AIX.

The software must have inbuilt support for several popular databases including Oracle, MSSQL and DB2.

The software must have inbuilt support for several replication products including Oracle Dataguard, MSSQL Native Replciation, HDS TrueCopy and HUR, EMC SRDF, HP Continuous Access among other. .

The software must support physical and virtual servers across primary and DR sites without any restrictions.

6

Management Console Server

The solution must provide with DR Management Console Servers with the required licenses and future scalability

Roles & Responsibility for DR

The primary role of DCO within the Disaster Recovery is to create &maintain a Disaster Recovery Plan to support a timely and effective resumption and recovery of all interrupted state services running from state data center.

The scope of disaster recovery plan shall include but not limited to:

1. Gathering need of services running from SDC.

2.Understanding policies, impact, and risk of services running from SDC. 3. Define Key Assets, Threats and Scenarios.

4. Define Recovery window.

5. Define Recovery solutions for data and services

6. Communication plan including escalation, notification, and declaration plans for each service running from state data centre.

7. Roles and responsibilities of teams working during disaster.

8. Exercising the plans, either to test and improve the plans, or to actually recover from a disaster situation that affects Service Delivery.

9. Updating, maintaining, managing, testing, and implementing any portion of the Disaster Recovery plans and activities that relate to the continued provisioning of the Services

10. DCO will be the primary point of contact that will communicate to PSEGS, affected services delivery manages about the disaster and recovery windows and procedure’s.

11. It is the complete responsibility of the DCO to meet all defined SLAs with PSEGS or any other State Department / State PSUs in event of Disaster.

12. “DR location for Punjab SDC will be (NIC Data Centre location to be confirmed at the later stage) who would be facilitating the DR activities in their Data Centre. The DR will be a Storage based replication from DC to DR., The replicator which will be positioned in the DR and will have the capacity to virtulize the backend storage on which NIC is giving 25TB initially. In future State may go beyond 25 TB space.