Last modified by Phillip Swanepoel on 2026/06/09 12:46

<
From version < 15.1
edited by Phillip Swanepoel
on 2026/06/09 12:46
To version < 11.1 >
edited by Phillip Swanepoel
on 2025/07/09 14:19
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -22,15 +22,12 @@
22 22  11. recreate tblDocuments synonym
23 23  11. tblAudit if applicable
24 24  
25 -1. Run  dba.dbo.sp_scan_db script for '%[_]Live[_]%' (exec dba.[dbo].[sp_scan_db] @includestr = '%DBC[_]Live%', @databasename = 'DBC_Live_Everest')
25 +1. Run  dba.dbo.sp_scan_db script for '%[_]Live[_]%'
26 26  11. correct all config found and repoint to Staging
27 27  11. TODO automate (some of the config correcting statements can be generated using [dba].[devops].[sp_change_db_env_post_restore])
28 28  11. exec dba.[devops].[sp_change_db_env_post_restore] @dbname = 'ENV_Staging_Everest', @ClientCode ='ENV', @Sourceenv = 'Live', @TargetEnv = 'Staging',
29 29  @domainRev = 'com.site', @domain = 'site.com',@svcUserPass = 'xxx.xxx.xxx.xxx#xx'
30 -11. After executing the output of the dba.devops.sp_change_db_env_post_restore rerun this SP and make sure there is no objects that hasn't changed
31 -11. Use [[doc_central.sql - Repos>>url:https://dev.azure.com/ebsphere/ebsphere/_git/devops?version=GBmaster&path=%2Fsetup-scripts%2Fdoc_central.sql]] to update staging documents when restoring from live.
32 32  1. Start all services
33 33  11. check logs to make sure no connections issues
34 -1. Log into the new DB with Everest and do a happyline test -> search for a member -> view member details -> upload a document -> download a document
35 35  
36 36  

Need help?

If you need help with XWiki you can contact: