Back Up Policy

Revision History

Ver. / Date / Description of Change / Authored / Revised By / Reviewed By / Approved By
0.1 / 25th Feb, 2009 / Draft / Abhishek Rautela / Ausaf / Sudhir Saxena
1.0 / 30th Feb, 2009 / Initial Version / Abhishek Rautela / Ausaf / Sudhir Saxena
2.0 / 12th Oct, 2009 / Updated the tasks section .Mentioned that the back up would be taken on the tape drives. / Abhishek Rautela / Ausaf / Sudhir Saxena
2.1 / 19th May, 2010 / Reviewed / Abhishek Rautela / Ausaf / Sudhir Saxena
2.2 / 5th Jan, 2011 / Reviewed and Formatting / Abhishek Rautela / Ausaf / Sudhir Saxena
3.0 / 22nd Aug, 2011 / Update section 2 & 5 / Abhishek Rautela / Ausaf / Dhananjay
3.1 / 21st May 2012 / Storage Device / Ajeet / Saket Madan / Dhananjay
3.2 / 10th March 2014 / Update section 3 & 4 / Saket Madan / Dhananjay Kumar / Ajay Kumar Zalpuri

Table of Content

Back Up Policy

Table of Content

1. Introduction

2. Scope of Backup Policy

2.1 a) In Scope:

2.2 Out of Scope:

3. Responsibility

4. Frequency of the back up

1. Introduction

NST recognizes that the importance of the timely backup and restore .The regular backups and restore is not only important from project point of view but is also useful for organizational growth and productivity. Therefore, this backup and restore policy highlights the areas that are in scope of the backup and restore

2. Scope of Backup Policy

2.1 a)In Scope:

  • VSS
  • MS Exchange (NST)
  • Configuration Image of Domain Controller
  • Configuration Image of Project Servers
  • TFS Server
  • Accounts/ Tally
  • Virtual Machines
  • DENTSPLY Server
  • QMS
  • Camera
  • Artcore
  • Sonic Wall VM Server
  • Sonic Wall Demo Server
  • Share Point Server
  • Data of department head

2.1 b) Added the NAS: as Central Backup storage with capacity 5TB

2.2 Out of Scope:

The backup of the individual machines are out of scope of the policy but we have added the NAS storage device and added all users with them. Individual are advised to store or backup within.

3. Responsibility

Infrastructure team: The infrastructure team is responsible for carrying out regular backups and restore

  • Maintain Backup logs
  • Maintain demo Restore log

Stakeholders: The relevant project/support team will verify the restore data at first time and as and when restoring is required.

4. Frequency of the back up

NST would be liable for the backup of the server mentioned in the Scope of the policy.

The frequency of the backup of the servers is on daily incremental and weekly full basis.

Backup:

The full backup of the MS-Exchange Servers is scheduled for Saturday, and TFS every day.Diskdrives would be used for taking the back up the TFSand Exchange server.

  • Backup Media (disk drives External Mass storage) shall be stored safely so as to protect them against theft and unauthorized access.
  • Rejected Media Backup shall be disposed after safe removal data by various erasing processes.
  • Offsite backup copy is available at an authorized location on weekly basis.
  • Incremental backup will be uploaded via FTP on to the authorized location on daily basis.
  • The Exchange backup is carried using Symantec backup exec software.
  • Clustered email mail box replication in real time.

The configuration image of Domain Controller and project servers are backed up when the configuration is set up and approved the first time.The backup of the configuration image is taken on the shared drive accessible to only infrastructure team.

The infrastructure team shall be notified in case of any issues against the servers mentioned in section 2.

Restore:

  • The backup media shall be regularly tested to ensure the reliability of backup information.
  • The demo restore is performed randomly on weekly basis. A demo restore log is maintained.

Page 1 of 5

Backup Policy ~NST Internal