Summary

• Page properties (2 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 1 removed)
  • image-20250411144502-1.png

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.phillips
	1	+XWiki.rudim

Content

...	...	@@ -1,19 +1,23 @@
1	1
2	2
3		-1. Pull newest scripts from repo using D:/ebsphere/devops/setup-scripts/setup-new.ps1
4	4	1. Stop all services including web site for staging on VM
5	5
6		-1. Drop Old DB on Azure portal
	5	+1. Backup Old DB to storage account
	6	+11. disable encryption if enabled, delete encryption key for DB
	7	+111. TODO move to self managed keys
	8	+11. enable compression!
	9	+11. container for client
	10	+
	11	+1. Drop Old DB
7	7	11. drop existing connections
8	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
	14	+1. Restore DB from Live from last PITR
12	12
	16	+1. Give yourself access to the admin group via the powershell script
	17	+
13	13	1. Wait for group policy SQL JOB [roughly 5-10 minutes] to create groups
14	14
15	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	17	11. [TODO] source passwords from vault
18	18	11. set clearLogins = 2
19	19	11. TODO
...	...	@@ -20,17 +20,12 @@
20	20
21	21	1. TODO - post restore script db settings etc
22	22	11. recreate tblDocuments synonym
23		-11. tblAudit if applicable
24	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')
	28	+1. Run  dba.dbo.sp_scan_db script for '%[_]Live[_]%'
26	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.
	30	+11. TODO automate
	31	+
32	32	1. Start all services
33	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	35
36	36

image-20250411144502-1.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.nikhils

Size

...	...	@@ -1,1 +1,0 @@
1		-67.7 KB

Content