Pre 6.9.5 New Production Install Upgrade QA

« Return to Notes Listing

Author:Aaron S.
Last Updated:January 06, 2022 4:45 PM

 

Pre-6.9.5: New Production Instance Install

  1. Create a ticket to get internal DNS pointed to host-prod-2:
    [clientid]-prod.titanclient.com 127.0.0.1  
    [clientid]-wkst-prod.titanclient.com 127.0.0.1  
    [clientid]-platform-prod.titanclient.com  
    [clientid]-services-prod.titanclient.com

  2. Update HOSTS file on host-prod-2 with client records:  
    [clientid]-prod.titanclient.com 127.0.0.1  
    [clientid]-wkst-prod.titanclient.com 127.0.0.1  
    [clientid]-platform-prod.titanclient.com  
    [clientid]-services-prod.titanclient.com.
    [clientid]-.titanclient.com 127.0.0.1  
    [clientid]-wkst.titanclient.com 127.0.0.1  
    [clientid]-platform.titanclient.com  
    [clientid]-services.titanclient.com.

    TIP: some clients will have additional entries like translations: [clientid].[mx/de] etc
  3. To allow clients accounts to access the new prod server, request that the -prod domains be made available externally. Be sure to update DomainConfig robots.txt files to Disallow all first.

  4. Sign into HOST-PROD-2

  5. Set up environment in prod by running create instance on host-prod-2 in G:\Scripts Be sure to use -BaseVersion 6.9.0.0 so that the restored db is 6.9 in TPI

    • TIP: the TpiAdmin password will be unique. Make sure to save this and add to keepass! If you don’t save the password you will need get this from the services or platform web.config.

  6. Restore prod database backup over prod database. To do this, you will need to copy your database backup to a local location on HOST-PROD-2, such as C:\TEMP
    • Run "G:\Scripts\RestoreDatabase.ps1"
      ​​​
  7. Run LegacyUpgradeDB script to upgrade to 6.9.0.0. Run this from your PC
    • "M:\_tpi\LegacyUpgrades\DatabaseUpgrade\UpgradeLegacyDB.ps1" to upgrade to 6.9.0.0 (as of 9/22/21 UpgradeLegacyDB.ps1 did not work on HOST-PROD-2 due to missing files)
    • This is only necessary if the instance is less than 6.9.0.0
    • You will need to know the version of Titan that you are upgrading from.  Answer the question posed by the script using the format 6.X.X.X.

Pre-6.9.5: New Production Upgrade

  1. Install client preRelease package, this should have dependencies on any other necessary packages (like Social Media Bookmarks if used). Once this installs successfully, navigate to display and wkst and confirm that everything is working.  
  2. Copy File Pile from Prod using RoboCopy
    EXAMPLE: robocopy \\host-prod-1\Files\Sites\[ClientID]\Titan\Public\FilePile\Pile1 \\host-dev-2\Files\Sites\[ClientID]\Titan\Public\Wkst\FileServer /mir /mt:30
  3. Install Coverage Report package (NWS.Titan.Blocks.CoverageReport and NWS.Titan.Blocks packages)
    1. In Titan Admin, under Content Sites and Blocks, active the Coverage Report Block.
    2. In Off nav, create a Coverage Report page
    3. Add the Coverage Report block to the page, save and publish and refresh

Pre-6.9.5: NWS New Production QA

External Testing is important! If this step is skipped, the upgrade is not guarenteed to go smoothly.

  1. External Team should use the Testing Plan created in the Kick-off Meeting to test the upgraded instance.
  2. Each item in the Testing Plan should be tested. A team member should sign off that each item is working as exptected.
  3. The following testing steps should be followed:
    1. If a bug is found, a ticket should be created as a subtask of the upgrade project. 
    2. A resource should be assigned to fix the issue (BED or FED)
    3. When the resource has fixed the issue, it should be sync to the repo if it is a code change and reassigned to the AD for verification. 
top