NIB Information Management System Backup and Restore

Transcription

1 SOP Reference: IT 02 Standard Operating Procedure for: NIB Information Management System Backup and Restore Version: Date Created: Date of first review: Date of next review: Name of Author: Eamonn O Hagan Signature of Author: Authorised by: Peter Hamilton Signature:

2 1. INTRODUCTION This SOP defines the procedures to be followed for the Northern Ireland Biobank (NIB) to backup and restore all system and data files. It outlines what is backed up, the frequency of backups and the scripts used in the backup. This procedure is to be used NIB. For security the data backups are copied nightly to a secondary off-site backup server. The location and specification of the servers are listed in Appendix 1. Periodically the backup data is restored and data integrity checks are performed to ensure no data is lost and all files are up to date. This procedure ensures that a secure and reliable backup of all data is copied to the NIB secondary server, where it can be restored, in the event of the primary server failing. 2. RESPONSIBILITY 2.1 It will be the responsibility of the NIB Scientific Director to ensure all suitably qualified persons adhere to this SOP. 2.2 The current suitably qualified persons are listed in Appendix Personnel who have been trained to backup, restore and perform integrity checks for all data and files associated with the NIB server must be approved by the NIB Scientific Director. 3. HEALTH AND SAFETY The NIB server must not be situated near heat sources or products that produce heat. Ventilation should not be switched off, covered or blocked to ensure reliable operation and prevent overheating. If the server is exposed to moisture contact PathXL to backup the server and DO NOT touch the machine. To avoid electric shock DO NOT expose the server to liquids of any description. 4. PROCEDURE 4.1 Backup Procedure The NIB primary server is backed up to the D: drive of the secondary server ( ) Data is backed up on a daily basis as follows: Website files are backed up once daily at hours using script C:\backupscript\SiteFiles.cmd. SQL database is backed up once daily at hours using script C:\NIBExpressBak\nibtest.BAT. Mongo clinical data is backed up once daily at hours using script C:\backups\Mongo\(day)\MongoDumpScript.BAT. Off-site sweep occurs once daily at hours using scripts: C:\backupscript\NIBBACKUP.cmd C:\backupscript\MongoBackup.cmd

3 4.2 Retention of Data Website files incur a daily up-date and overwrite. SQL data has an unlimited retention Mongo files are retained for seven days Monday to Friday. 5. WEBSITE FILES The NIBiobank website files are located on the primary server at C:\inetpub\wwwroot\tissuebank; The website backup files are located on the backup server in the folder D:\SiteFiles\. This folder can be accessed on the primary server by mapping a network drive to \\ \BackupVolume. To restore the website files: 5.1 On the primary server navigate to C:\inetpub\wwwroot\tissuebank. 5.2 Delete all files and folders. 5.3 In Windows Explorer click on Tools and Map Network Drive. Set Drive: to Z: and Folder to \\ \BackupVolume and click Finish 5.4 Copy and paste all files from Z:\SiteFiles\ to C:\inetpub\wwwroot\tissuebank 5.5 The backup of website files is now restored. 6. SQL DATABASE The NI Biobank SQL database is located at C:\Program Files\Microsoft SQL Server\MSSQL11.NIBIOBANK\MSSQL\DATA\pxlEngine.mdf 6.1 To restore the SQL database copy the relevant PxlEngine.bak from the backup location on the backup server (D:\nibdb\pxlEgine\) to the default SQL server directory: C:\ProgramFiles\MicrosoftSQLServer\MSSQL10_50.BIOBANK\MSSQL\BACKUP 6.2 Select the SQL Management Studio from the drop down list Figure Log on to the SQL server using the default username and password and select connect Figure In the left hand browser window, delete the current pxlengine database by right clicking on pxlengine db and select delete Figure Select the tick boxes for delete backup and restore history information for database and close existing connections Figure Select ok to confirm the deletion of the database Figure Within the left hand browser window select Database and right click Restore Database Figure Select File and click Add Figure Select pxlengine.bak from the left hand browser window, previously copied, and select ok Figure Within the Specify Backup Box select Ok Figure From the database drop down menu select pxle and tick the restore box. Select Ok to complete the database restore Figure Database is now restored Figure From the left hand browser window, select the Security Directory and Users Figure Right click on pathxl2 form the drop down menu and select delete to remove from the pxlengine database Figure Select Security and Logins from the browser window. Right click on pathxl2 and select properties Figure 12

4 6.16 Select User Mapping from the menu on the left hand side of the screen Figure Within the window Users Mapped to this Login select the tick box pxlengine Figure Select the tick box db_owner and public from the window marked Database role membership for pxlengine Figure Select ok to fully restore the database with the correct permissions Figure 13 Mongo Dump 6.20 To restore the Mongo Dump select the search bar from the start menu and type in services or select Start, Administrative Tools and Services Select the Mongo DB service, do a right mouse click and select Stop to stop the service Figure In Windows Explorer navigate to the folder C:\data and delete all files From the backup server copy the relevant Mongo Dump folder (D:\mongo\(Day)\ to the C:\mongoBin location From windows start menu select command prompt and type cd C:\mongoBin Enter the command mongorestore directoryperdb dbpath C:\data 6.26 Create the folder C:\data\logs Select start the service to fully restore the mongo databases Figure Setup the connection strings. On nthe backup server double click the file D:\PXLConfiguration.exe Type in the database password: Bar3nt567, populate the fields as shown Figure Within the Pathxl configuration window populate the data as shown and select next Figure The restore of all files and data is now fully complete. 7. DATA INTEGRITY CHECKS 7.1 To ensure that data has been correctly backed up and that no information has been lost or tampered with, data integrity checks are performed on a monthly and annual basis. 7.2 The monthly integrity check involves matching the total numbers of records on primary and backup servers as per NIB-F-015. In addition a selected check for five donors is randomly selected using the HTA Audit Report on the NIB IMS. The completed audit form will be maintained in the central file as per normal practice (see Admin 06 Audit & Quality Control SOP) 7.3 The annual integrity check involves an in depth comparison of stored data from 10 individual records between the primary and secondary server. This will ensure data within the Biobank Information Management System including reports, applications, donors, cases and protocols are accurate and up to date.

5 8. DISASTER RECOVERY PLAN The primary and back up servers are located in separate buildings. Thus the backup procedure will ensure recovery of all data and files.

6 NIB server specifications NIB Primary Server APPENDIX 1 Location Specification Rm LG05 Health Sciences Building Dell PowerEdge T310 Bios: Intel Xeon X Ghz (Quad Core) 8.0 GB Ram Dell Perc S100/S3000 Disk Space: Available 1.4TB (Used 80 GB) Broadcom BCM5716C NetExtreme II GigE Card x 2 Support QUB Inventory No: Dell Serial No: DPVF05J Date of Purchase: 09/03/2011 Dell Warranty Expiry: 09/03/2014 Network Installed Software Installed Windows Roles Backups Computer Name : NIBIOBANK Workgroup: WORKGROUP IP Address: Windows 2008 R2 Enterprise SP1 (64-bit) LogMeIn Microsoft SQL Server 2008 Microsoft SQL Server 2012 MongoVUE VMware Player Symantec Endpoint Protection Application Server File Services Web Server (IIS) 1) Mongo (Mon Sun) Daily backup of Mongo database at using mongodump command to c:\backups\mongo\<day> folder 2) NIB Database Backup Run daily at Uses Expressmaint to backup NIB database (NIBIOBANK\NIBIOBANK) to C:\backups\SQL folder. With report log copied to c:\reports 3) NIB Sweep Backup Run daily at Using Robocopy copies Mongo and NIB backup folders to backup server 4) SiteFilesSweep Run daily at Using Robocopy copies www server files (\wwwroot\tissuebank) to backup server

7 Users Web Server Administrator biobankbackup (member of Users) Physical Path: C:\inetpub\wwwroot\tissuebank Security certificate expires : 12 / 1/ 2015 NIB Backup Server Location Specification Support Network Installed Software Installed Windows Roles Backups Users Web Server Rm 0B.005 Molecular Pathology CCRCB Dell PowerEdge T310 Bios: Intel Xeon X Ghz (Quad Core) 8.0 GB Ram Dell Perc S100/S3000 Disk Space: Available 1.4TB (Used 85 GB) Broadcom BCM5716C NetExtreme II GigE Card x 2 (only one configured) QUB Inventory No: Dell Serial No: Date of Purchase: Dell Warranty Expiry: Computer Name : CCRCB Workgroup: WORKGROUP IP Address: Windows 2008 R2 Enterprise SP1 (64-bit) Microsoft SQL Server 2008 Microsoft SQL Server 2012 Symantec Endpoint Protection File Services Web Server (IIS) Daily backups of NIBioBank databases copied to D:\Mongo folder; NIBioBank www server files copied to D:\SiteFiles Administrator biobank (member of Administrators) NIBBackup (member of Administrators) Physical Path: C:\inetpub\wwwroot\SiteFiles

8 APPENDIX 2 Staff with access rights to the NI Biobank servers. NIB Scientific Director MDBS IT NIB Digital Pathology Technician PathXL Administrator Dr Jacqueline James Eamonn O Hagan Steve Stewart Anne Carson Stephen Johnston NOTES 1 Records of data integrity checks performed on a yearly and monthly basis are located on the NIB Shared drive.

9 Figure 1 SQL Management Studio Figure 2 SQL Server Login

10 Figure 1 SQL Management Studio Figure 2 SQL Server Login Figure 3 Delete pxlengine database Figure 4 Delete backup and restore history information for database

11 Figure 5 Restore database Figure 6 Restore database

12 Figure 7 Specify backup Figure 8 Restore database

13 Figure 9 Database restore complete Figure 10 Security directory

14 Figure 11 Delete pxlengine database Figure 12 pathxl2

15 Figure 13 Complete database restore with correct permissions Figure 14 Start and stop Mongo Dump

16 Figure 15 Set up Connection Strings Figure 16 Complete Connection Strings