Download as doc, pdf, or txt
Download as doc, pdf, or txt
You are on page 1of 4

Ref. No.

: P/MR/02
Noble Aerospace Pvt. Ltd.
Ref: CL 4.2.4
Quality System Procedure
Rev. No.: 00

Title Rev. Date: 01/10/2013


CONTROL OF RECORDS
Page 1 of 4
Procedure:
This procedure aims to provide evidence of conformity to requirements and the effective
operation of quality management system and to ensure identification, collection, indexing,
storage, filing, maintenance and disposal of records.

The originator is responsible for clarity, completeness and correctness of the generated
records. A separate folder is created against each invoice which in turn has details of
COC and docket details.

Retention period is documented in list of records.

Backup procedure

All files from the director laptop are backed up daily to a Hard Disk. These daily backups
are full backups that include every file from the system.
All office computers are connected to main server which will have one mirror disk which
continuously takes backup.
At the end of the month, one full backup is made on another hard disk and the same is
stored in a director’s home.

Recovery procedure
Potential disasters may vary in scope from isolated outages that impact one or several
critical systems to more extensive outages that compromise many computers or other
devices.

Another key attribute of a disaster is whether the outage is restricted to the loss of
individual files on computers that are still operational, or whether it involves operating
system corruption or hardware damage which renders the computer temporarily or
permanently non-operational.

Prepared by Checked by Approved by


Ref. No.: P/MR/02
Noble Aerospace Pvt. Ltd.
Ref: CL 4.2.4
Quality System Procedure
Rev. No.: 00

Title Rev. Date: 01/10/2013


CONTROL OF RECORDS
Page 2 of 4

In the event of a disaster scenario, Director must assess the impact as quickly as possible
to determine the extent of the impacted systems and to determine whether it involves file
loss, operating system corruption requiring software rebuild, hardware damage or other
infrastructure outage such as communication lines or devices.

If individual computers have suffered file loss or operating system corruption, these
systems should be recovered promptly in the order of their importance to NAPL business
and operations as determined by Director.

In cases where files have been lost but the operating system remains intact, the lost files
should be restored from backup tapes. In cases where the operating system is no longer
functioning, the system must be rebuilt as described below after which any additional files
may be restored from backup if necessary.

File Loss

File loss may result from:

 File system corruption due to software or hardware malfunction, hardware degradation,


abrupt system shutdown, power fluctuation or other damage to the computer
 Accidental deletion of files or directories
 File system damage due to viruses

Recovery from Backup Media

Recovery of lost files from tape should proceed according to the following steps:

1. Identify which files or directories need to be recovered (including server, disk and full
path).
2. Retrieve the most recent full backup for the affected disk partition.
3. If there are a small number of lost files: Using the Retrospect Restore Manager, select
the identified files/directories to be restored. If attempting to recover corrupt data,
restore the files to an alternate location so the restored copies can be compared to the
corrupted originals, and a determination can be made if the restored files are intact.
Prepared by Checked by Approved by
Ref. No.: P/MR/02
Noble Aerospace Pvt. Ltd.
Ref: CL 4.2.4
Quality System Procedure
Rev. No.: 00

Title Rev. Date: 01/10/2013


CONTROL OF RECORDS
Page 3 of 4
4. If there are a large number of files: Using Retrospect Restore Manager, restore the full
backup of the non-system disk partition in part or in its entirety, or restore the most
recent full non-operating system portions of a system disk partition.

Machine Rebuild

Rebuild of a machine’s entire disk is required in the following scenarios:

 Hard disk failure or substantial corruption on the system drive


 Disk corruption which renders the Windows operating system non-operational
 Hard disk failure or corruption, requiring the data drive(s) to be restored
 Catastrophic component failure, rendering the system unusable
 Physical machine loss

The following steps should be followed to rebuild the affected system, including resolving
any hardware issues and recovering the operating system.

1. If there is damaged hardware, identify the failing component and procure a


replacement. If the component is a disk drive, ensure that its replacement is of the
same capacity or larger.
2. Replace and/or re-install the component. When replacing hardware, use the same
type of controller, driver, and SCSI ID as used prior to the disaster.
3. Recreate the disk partitions on the new system to be the same size or larger, format
each of them with the same format as previously (i.e. FAT, NTFS, etc), and assign the
same drive letters as before.
4. Boot the machine and restore the image of that disk partition
a. If the machine is a critical data center server
i. Reboot the machine
ii. Run the Retrospect Backup Client Agent and Restore
Manager software to restore files from the most recent full backup.
b. Otherwise, restore any other disk partitions from their current
image on the network share

Prepared by Checked by Approved by


Ref. No.: P/MR/02
Noble Aerospace Pvt. Ltd.
Ref: CL 4.2.4
Quality System Procedure
Rev. No.: 00

Title Rev. Date: 01/10/2013


CONTROL OF RECORDS
Page 4 of 4

Theft of Data

To prevent the theft of Data the following policies have been applied

1. Source codes are not allowed to send by Email


2. FTP file transfer should be secured with encryption and password.
3. Request for burning the data’s in to the CD/DVD media need to be approved
by the director.

Documented Reference:

 List of records L/MR/02

Prepared by Checked by Approved by

You might also like