Panchayat:Repo18/vol2-page0677

GOVERNMENT ORDERS 677


(ii) Archival-The saving of old or unused files onto magnetic tape or other offline mass storage media for the purpose of releasing on-line storage room.


(iii) Restore-The process of bringing offline storage data back from the offline media and putting it on an online storage system.


(iv) Storage replication-Storage replication is a service in which stored or archived data is duplicated in real time over a storage area network. Storage replication service provides an extra measure of redundancy that can be invaluable if the main storage backup system fails. Storage replication may be done in the same storage array, different storage arrayfs in the same location or a storage array in a remote location. Immediate access to the replicated dataminimizes downtime and its associated costs. The service, if properly implemented,can streamline disaster recovery processes by generating duplicate copies of allbacked-up files on a continuous basis. It can also speed up and simplify recovery from a natural or human-caused disaster such as a fire, flood,burricane, virus, or worm.

(v) Disaster Recovery - The process, policies and procedures related to preparing for recovery or continuation of technology infrastructure critical to an organization after anatural or human induced disaster. Disaster recovery planning is a subset of a larger process known as business Continuity planning and should include planning for resumption of applications, data, hardware, Communications (such as networking) and other IT infrastructure. A business continuity plan (BCP) includes planning for non-IT related aspects such as key personnel, facilities, Crisis communication and reputation protection, and should refer to the disaster recovery plan (DRP) for Trelated infrastructure recovery/continuity

4. Scope

This policy applies only to backup and restore of data for all Computers and storage equipment in the eGovernance Date Centre, owned and operated by Kerala Government Departments. This does not include the policies for archival, storage replication and disaster recovery.

5. Backup Timing

Fullbackups are to be scheduled nightly on Monday,Tuesday, Wednesday, Thursday, Friday, Saturday and Sunday. All tapes are to be tested on Sunday during daytime. Removal of tapes to be kept in safe locker shall be performed after testing of tapes are completed. Loading new tapes shall also be performed during this time.

6. Tape Storage

There shall be separate set of tapes for each daily backup. There shall be additional set of tapes for each Saturday of the month such as Saturday 1, Saturday 2, Saturday 3, Saturday 4 etc. Backups performed on Saturday on the additional setshall be kept for one month in safe locker and used again the next month on the applicable Saturday. Backups performed on Monday through Friday shall be kept for one week and used again the following appropriate day of the week. All tapes shall be properly labelled. In addition, differential back up should be taken midday, preferably between 1.00 PM 2.00 PM on all days including Sunday and holidays. Transaction Log Back up should be done additionally and copied to a remote location every half an hour/one hour depending on system equiements The remote Transaction Log Backup need not be retained once the next differential/fullbackup is taken.

7. Tape Drive Cleaning

Tape drives shall be cleaned weekly and the cleaning tape shall be changed monthly.

8. Monthly Backups

Every month two sets of monthly backup shall be made. One set shall be kept in the tape drive and the otherset in the safe locker.

9. Age of tapes

The date each tape was put into service shall be recorded on the tape. Tapes that have been used longer than six months shall be discarded and replaced with new tapes,

10. Responsibility

The System Administrator or IT manager of each department or his delegate from the IT cell of the department shall performallbackup related activities. He/She shall develop a procedure for testing backups