SOP For Disaster Management For Chromatographic Software Data System In Pharma

Table of Contents

SOP for Disaster management for Chromatographic Software Data System

Purpose:

This procedure establishes a disaster management plan for handling any natural disaster or a human-made disaster that destroys hardware, software, or data related to chromatography software.

Scope:

This SOP applies to all backup devices, including hardware, software, and site backup.

Responsibility:

IT Admin/ Designee: Responsible for ensuring disaster management at respective sites is in place.

Accountability:

IT Admin/ Designee: Is responsible for ensuring that this process is implemented.

Abbreviations:

QC: Quality Control
SOP: Standard Operating Procedure
IT: Information Technology
CSDS: Chromatography Software Data System
RAID: Redundant Array of Independent Disk
WAN: Wide Area Network
HOD: Head of The Department
Dept. : Department

Definition:

Disaster Management: Disaster management is the discipline of dealing with and avoiding both natural and man-made disasters. To neutralize or lessen the impact of a disaster, involves preparation, response, and recovery.

Procedure:

Disaster recovery plan for CSDS server in case of hardware failure:

Data should be buffered locally on workstations in case CSDS database server failure occurs, and transferred to the CSDS database server as soon as possible when it comes live.
Hardware disks of the CSDS database server must be protected via RAID levels to ensure the high availability of the server and to avoid data corruption.
There should be a redundant power supply for the server.
There should be daily backups at the site and replication of those backups at an off-site location.
In case of recovery, full backups should be performed daily to avoid dependence on previous backups.
To avoid technical errors and human error on tape backups, tapeless backup solutions should be used.
In case of failure of any network switch, a spare network switch must be available. Also, a network failure protection protocol should be in place through which data should be buffered on local workstations in case of a network failure.
A redundant UPS system should be in place, which could prevent an unexpected shutdown of the database server in case of a power failure.
There should be a performance monitoring SOP and preventive maintenance SOP in place for servers and associated components.
Onsite backup devices are located in different locations from the CSDS database servers within the site.
A contract with the server vendor must be in place with 24×7 support.

Disaster Recovery plan in case of server operating system failure, application failure, and database failure:

At the site, software media for reinstallation should be readily available.
There should be a daily full backup on-site and a replica of the same off-site.
Contracts must be in place with software vendors.
An SOP must be in place for data backup.

A disaster recovery plan in case one of the primary domain controllers fails:

There should be one additional domain controller on each site to fulfill the role of the primary controller.
A contract with the server hardware vendor must be in place.
There should be a performance monitoring SOP and preventive maintenance SOP in place.
There should be a daily full backup on-site and a replica of the same off-site.

Disaster recovery plan for site-level backup failure:

There should be an off-site backup solution in place.
Data must be available on a server that is protected by hardware RAID.
There should be a performance monitoring SOP and preventive maintenance SOP in place.
An additional WAN link should be available in case the primary WAN link fails.