COPY BACKUP FILE
1. Log on to RCP-DC-1 server as ctac (or another server with enough free space to create the file)
- The Reason RCP-NOC-DC-1 is recommended is that you need enough free space on the C:\ drive for windows to create the zip file, to do this it needs roughly the same free space as the file being zipped takes up. So if the .bak is 130GB than you have to find a computer with 130GB of free space on the C: drive to create the file, even if the file is located in another position or server.
2. Browse to \\RCP-SQL\m$\Backup 3. Select the .bak file (i.e P21_backup_2016_02_01_000001_4391421)
(Use 10PM file from last day of the previous month located in \\RCP-SQL\m$\Backup\P21\ if 12AM Fails, or restore the end of month nights backup of the Live P21 Database from UDP if required as a tertiary option)
4. Right click on the file and select send to à Compressed (zipped) folder
5. Once the file is zipped, copy the zip file to \\rcp-fs\P21_monthly_backup in the correct year folder and create a new folder that matches the current structure. (i.e. for the file above the correct location would be \\RCP-fs\P21 2016\P21_January_2016\
6. Please note the file is created as a backup of the previous month on the first of each month, so a file showing 2017_01_01 would be the backup of December 2016 and would be placed in the folder P:\P21 2016\P21_December_2016\
MONTH END DATABASE RESTORE
7. Open Microsoft SQL Management studio on RCP-SQL.
8. Login to Microsoft SQL Management studio (windows authentication as RCP_ServDesk)
9. Left click on “Databases” + symbol
10. Right click on the correct database that matches the file you are restoring based on the policy below:
· Please note the file is created as a backup of the previous month on the first of each month, so a file showing 2017_01_01 would be the backup of December 2016 and would be restored to MEDB4 not MEDB1. Based on the month of the backup, use the corresponding DB below.
(In the example screenshot below-we are restoring a DB from the month of July-so we use MEDB3)
11. January, May, September – MEDB1
12. February, June, October – MEDB2
13. March, July, November – MEDB3
14. April, August, December – MEDB4
15. Select “Task” / “Restore” / “Database”
16. On the “General” page select the option “From Device” then click the browse icon
17.
18. On the “Specify Backup” window select “File” (default). Click on the “Add” tab
19.
20. Browse to the M:\backup folder and locate the .bak file (previously identified in the Copy Backup Instructions at start of this doc)
21.
22. 1-Click check box under restore
23. 2-Browse to the “Options” page and select the box “Overwrite the Existing database (WITH REPLACE)”
24.
25. Check to ensure the restore location on “Files” page is also set to the correct month database as you are restoring to, not the database the file came from. In the example below, it shows the restore will go to E\Data\P21.mdf-THIS IS INCORRECT DB, you must change it to the correct MEDB for both Seed 16_data and seed 16_log.
(THIS IS IMPORTANT!)
26.
27. Location under “Restore As” should match the file path of the MEDB database from the J drive.
· For example, if you are restoring to MEDB1 than the file path should be set to J:\MEDB1\MEDB1.mdf and J:\MEDB1\MEDB1_log.ldf
28. Once you’ve verified the restore is pointed to the correct “Restore As” location. Click on “Options”.
29. Check “overwrite the existing Database (With Replace)”
30. Uncheck “Take tail-log backup before restore”
· If this is check it will lock the DB, and cause the Restore to fail.
31.
32. Lastly, verify a time that the “Restore as” location shows the correct MEDBx and click on “OK”
33. Once the restore is 100%, which can take about an hour or two, call Ed Marsh to have him confirm the DB restore is good.
34. Once you make sure you copied the zip file created in the first section above to the RCP-fs server-this is the first step you should have done in this document, you can delete the monthly backup file off the M:\ drive
35. This completes the process.