Last modified by Phillip Swanepoel on 2026/06/09 12:46
Show last authors
1
2
3 1. Pull newest scripts from repo using D:/ebsphere/devops/setup-scripts/setup-new.ps1
4 1. Stop all services including web site for staging on VM
5
6 1. Drop Old DB on Azure portal
7 11. drop existing connections
8
9 1. Restore DB from Live from last PITR or latest Full backup if DB age is not important
10 - [[image:image-20250411144502-1.png||height="150" width="284"]]
11 1. Give yourself access to the admin group via the powershell script - if needed
12
13 1. Wait for group policy SQL JOB [roughly 5-10 minutes] to create groups
14
15 1. Run post restore access script [[SKL_sqlmi_accesss.sql - Repos (azure.com)>>url:https://dev.azure.com/ebsphere/ebsphere/_git/dbs?version=GBmaster&path=/src/setup_scripts/SKL_sqlmi_accesss.sql]]
16 11. This has to be run using SQLCMD mode on the script
17 11. [TODO] source passwords from vault
18 11. set clearLogins = 2
19 11. TODO
20
21 1. TODO - post restore script db settings etc
22 11. recreate tblDocuments synonym
23 11. tblAudit if applicable
24
25 1. Run  dba.dbo.sp_scan_db script for '%[_]Live[_]%' (exec dba.[dbo].[sp_scan_db] @includestr = '%DBC[_]Live%', @databasename = 'DBC_Live_Everest')
26 11. correct all config found and repoint to Staging
27 11. TODO automate (some of the config correcting statements can be generated using [dba].[devops].[sp_change_db_env_post_restore])
28 11. exec dba.[devops].[sp_change_db_env_post_restore] @dbname = 'ENV_Staging_Everest', @ClientCode ='ENV', @Sourceenv = 'Live', @TargetEnv = 'Staging',
29 @domainRev = 'com.site', @domain = 'site.com',@svcUserPass = 'xxx.xxx.xxx.xxx#xx'
30 11. After executing the output of the dba.devops.sp_change_db_env_post_restore rerun this SP and make sure there is no objects that hasn't changed
31 11. Use [[doc_central.sql - Repos>>url:https://dev.azure.com/ebsphere/ebsphere/_git/devops?version=GBmaster&path=%2Fsetup-scripts%2Fdoc_central.sql]] to update staging documents when restoring from live.
32 1. Start all services
33 11. check logs to make sure no connections issues
34 1. Log into the new DB with Everest and do a happyline test -> search for a member -> view member details -> upload a document -> download a document
35
36