Changes for page MI Restore to Staging From Live
Last modified by Phillip Swanepoel on 2026/06/09 12:46
Change comment:
(Autosaved)
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. phillips1 +XWiki.rudim - Content
-
... ... @@ -1,30 +1,25 @@ 1 1 2 2 3 -1. Pull newest scripts from repo using D:/ebsphere/devops/setup-new.ps1 4 - 5 5 1. Stop all services including web site for staging on VM 6 6 7 -1. Drop Old DB on Azure portal 5 +1. Backup Old DB to storage account 6 +11. disable encryption if enabled 7 +11. container for client 8 + 9 +1. Drop Old DB 8 8 11. drop existing connections 9 9 10 -1. Restore DB from Live from last PITR or latest Full backup if DB age is not important12 +1. Restore DB from Live from last PITR 11 11 12 -1. Give yourself access to the admin group via the powershell script - if needed 13 - 14 -1. Wait for group policy SQL JOB [roughly 5-10 minutes] to create groups 15 - 16 -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]] 14 +1. Run post restore access script sqlmi_accesss_SKL.sql 17 17 11. [TODO] source passwords from vault 18 -11. set clearLogins = 216 +11. set clearLogins = 1 19 19 11. TODO 20 20 21 -1. TODO - post restore script db settings etc 22 -11. recreate tblDocuments synonym 23 -11. tblAudit if applicable 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]) 21 +11. TODO automate 22 + 28 28 1. Start all services 29 29 11. check logs to make sure no connections issues 30 30