Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

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

Content

...	...	@@ -1,24 +1,30 @@
1	1
2	2
3		-1. Backup Old DB to storage account
4		-11. container for client
5		-
	3	+1. Pull newest scripts from repo using D:/ebsphere/devops/setup-scripts/setup-new.ps1
6	6	1. Stop all services including web site for staging on VM
7	7
8		-1. Drop Old DB
	6	+1. Drop Old DB on Azure portal
9	9	11. drop existing connections
10	10
11		-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
12	12
13		-1. Run post restore access script sqlmi_accesss_SKL.sql
14		-11. source passwords from vault
15		-11. set clearLogins = 1
16		-11. TODO
	11	+1. Give yourself access to the admin group via the powershell script - if needed
17	17
	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	+
18	18	1. Run  dba.dbo.sp_scan_db script for '%[_]Live[_]%'
19	19	11. correct all config found and repoint to Staging
20		-11. TODO automate
21		-
	27	+11. TODO automate (some of the config correcting statements can be generated using [dba].[devops].[sp_change_db_env_post_restore])
22	22	1. Start all services
23	23	11. check logs to make sure no connections issues
24	24