Summary

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

Details

Page properties

Author

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

Content

...	...	@@ -1,24 +1,19 @@
1	1
2	2
3		-1. Pull newest scripts from repo using D:/ebsphere/devops/setup-new.ps1
	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. Backup Old DB to storage account
7		-11. disable encryption if enabled, delete encryption key for DB
8		-111. TODO move to self managed keys
9		-11. enable compression!
10		-11. container for client
11		-
12		-1. Drop Old DB
	6	+1. Drop Old DB on Azure portal
13	13	11. drop existing connections
14	14
15		-1. Restore DB from Live from last PITR
	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
16	16
17		-1. Give yourself access to the admin group via the powershell script
18		-
19	19	1. Wait for group policy SQL JOB [roughly 5-10 minutes] to create groups
20	20
21	21	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
22	22	11. [TODO] source passwords from vault
23	23	11. set clearLogins = 2
24	24	11. TODO
...	...	@@ -27,10 +27,14 @@
27	27	11. recreate tblDocuments synonym
28	28	11. tblAudit if applicable
29	29
30		-1. Run  dba.dbo.sp_scan_db script for '%[_]Live[_]%'
	25	+1. Run  dba.dbo.sp_scan_db script for '%[_]Live[_]%' (exec dba.[dbo].[sp_scan_db] @includestr = '%DBC[_]Live%', @databasename = 'DBC_Live_Everest')
31	31	11. correct all config found and repoint to Staging
32	32	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
33	33	1. Start all services
34	34	11. check logs to make sure no connections issues
	33	+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,0 +1,1 @@
	1	+XWiki.nikhils

Size

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

Content