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