Changes for page MI Restore to Staging From Live
Last modified by Phillip Swanepoel on 2026/06/09 12:46
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,19 +1,24 @@ 1 1 2 2 3 -1. Pull newest scripts from repo using D:/ebsphere/devops/setup- scripts/setup-new.ps13 +1. Pull newest scripts from repo using D:/ebsphere/devops/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 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 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 important15 +1. Restore DB from Live from last PITR 10 10 11 -1. Give yourself access to the admin group via the powershell script - if needed17 +1. Give yourself access to the admin group via the powershell script 12 12 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 ... ... @@ -24,7 +24,8 @@ 24 24 25 25 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]) 32 +11. TODO automate 33 + 28 28 1. Start all services 29 29 11. check logs to make sure no connections issues 30 30