Refresh Dev from Prod

Refresh Dev From Prod

The following steps are designed to ensure that the refresh process goes smoothly and does not slow prod or leave incorrect values on dev. While some steps may be unneccessary much of the time, if they are missed when needed they can cause difficult to track errors.

1. Store the dev values for the following global params somewhere (there is space for them in the attached testing template). These values will need to be replaced once dev is refreshed from prod. Some may already be correct after the refresh but at the time of writing this documation, all of them need to be checked and occasionally replaced. Some will always need to be reset.
   • Environment
     • BackgroundMailerWkstDns
     • ContactBlockWkstUrl
     • MailHostName
     • NetSQLConnAppControl
     • NetSQLConnCMS
   • Extensibility
     • MailProvidersConfig
   • Request Handling
     • DomainConfig
   • Site Search
     • CenterContentWebAppPath
     • DisplayWebAppPath
     • DTIndexBaseDirectory
     • WkstWebAppPath
2. Store the dev values for the following:
   • Upload Path for File Piles
   • Download Path for File Piles
   • Primary Display DNS for each Content Sites
   • Search Index Types -> dtSearch -> External Assembly Location
   • If there are datasites with Site-specific Detail Pages, save the values there.
3. Create and Copy Only back up of the dev database and store it in "\\sql-dev-1\DatabaseRefresh".
   • Connect to SQL-DEV-1\TITANCLIENTS via SSMS. Connection information should be in keepass.
   • Find the database you wish to backup and right click.
     • Select "Tasks" -> "Back Up..."
       • In the modal select the checkbox for Copy-only Backup.
       • Select "Disk" in the destination dropdown.
       • Click "Add..." 
       • Under "File Name" enter: "Q:\DatabaseRefresh\[ClientID]_Titan_Public_Dev_[Date].bak" and click OK
       • Click OK in the main modal to begin the backup.
4. Create a copy of the Prod database and transfer it to the dev server.
   • Remote out to the production server that your database is on and create a backup as instructed in step 2 with the exception of the File Name which should be: "H:\SQLBackups\[ClientID]_Titan_Public_For_Refresh_[Date].bak
   • Open Microsoft Edge and login to your one drive acount.
   • Open File Explorer and navigate to your .bak 
     • Generally speaking, if the bak file is more than 1,000,000 KB it is best to zip it in pieces so that the transfer does not impact prod speeds.
       • Right click on your bak file, go to "7-Zip" and select "Add to archive..."
       • Set up the modal as seen below. The "Memory usage for Compressing" and "Split to volumes, bytes" are likely to need altering from the defaults.
         • 
         • Click OK to begin the zip.
       • Make a note of the file size for the .bak in order to compare once the transfer is complete.
   • Return to your one drive account and upload the resulting zip files or the original .bak if small enough to no need zipping.
     • Make sure to upload files somewhere they will be easy to find.
     • On your computer it is recommened to pause syncing of your one drive account though this is not actually neccessary.
   • At this time you may close everything on prod and log off.
5. Using Microsoft Edge, open your one drive account on your local computer.
   • Download the backup of prod.
     • If it is multiple zips, it is recommended that you download one at a time. This can increase the amount of time that it takes but it has a lower chance of corrupted or failed downloads.
   • Open File Explorer and locate your downloaded backup.
     • Using File Explorer transfer the backup (.bak or zips) to "Q:\DatabaseRefresh"
     • If your backup is zipped, right click on the first in the series, got to 7-Zip and selected "Extract Here".
     • Compare the size of the unzipped bak file with that of the one on prod. If they are the same your transfer was successful.
6. Run the Restore Database script.
   • Open powershell and navigate to "M:\_tpi\Scripts"
   • run "./RestoreDatabase.ps1"
     • Follow the promts to run the script. Review the screenshot below for an example.
       • Your server will need to be changed to "sql-dev-1\titanclients".
       • If your prod is on host-prod-3 make sure to change it from the default of host-prod-2.
       • To get the correct path for your backup, right click on the .bak file in File Explorer and select "Copy as path"
         • change "\\sql-dev-1" to "Q:" before entering it into the powershell script.
     • 
7. Once the script has completed you will need to reset the dev values that you saved off.
   • First you will need to reset the password.
     • Login to the workstation with the prod password.
     • On the Admin side, go to Account Configuration and make sure that the checkbox for password complexity is unchecked.
     • Logout
     • On the login screen, click "Change Password and Login"
     • Reset the dev password to "titancms"
   • Reset all the Global Parameters that you saved.
   • Reset the other dev values saved.
   • Once all values are reset it is recommended that you restart all sites via TPI in case values are cached.
8. Run the following Background jobs:
   • dtSearch Disk Refresh
   • dtSearch Create Index jobs
   • Refresh Display Nav
   • DocMgmt File Sweeper
9. Use the SmokeTestTempate to make sure you test impacted areas.