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,33 +1,30 @@ 1 1 2 2 3 +1. Pull newest scripts from repo using D:/ebsphere/devops/setup-scripts/setup-new.ps1 3 3 1. Stop all services including web site for staging on VM 4 4 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 6 +1. Drop Old DB on Azure portal 12 12 11. drop existing connections 13 13 14 -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 15 15 16 -1. Give yourself access to the admin group via the powershell script 11 +1. Give yourself access to the admin group via the powershell script - if needed 17 17 18 18 1. Wait for group policy SQL JOB [roughly 5-10 minutes] to create groups 19 19 20 20 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 21 21 11. [TODO] source passwords from vault 22 22 11. set clearLogins = 2 23 23 11. TODO 24 24 25 25 1. TODO - post restore script db settings etc 22 +11. recreate tblDocuments synonym 23 +11. tblAudit if applicable 26 26 27 27 1. Run dba.dbo.sp_scan_db script for '%[_]Live[_]%' 28 28 11. correct all config found and repoint to Staging 29 -11. TODO automate 30 - 27 +11. TODO automate (some of the config correcting statements can be generated using [dba].[devops].[sp_change_db_env_post_restore]) 31 31 1. Start all services 32 32 11. check logs to make sure no connections issues 33 33