How to Refresh a Non Production Munis Database

Owned by Knowledge Assistant
Last updated: Sept 10, 2024
2 min read



Description of Issue

  • How can I bring data over from a Munis Production database to a Non-Production database?

  • Request to Refresh Train, Test, Verif, Impl or other Non-Live Munis databases from Live Production Database

  • Need to use Live data in a safe database for testing

  • Data problem in secondary database that is not occurring in Live.



Context

  • Data

  • Refresh

  • Munis

  • OnPrem

  • Munis refresh

  • Munis database refresh



Cause

Need up to date data in a Non-Production environment



Resolution

Prerequisites

  • The target environment MUST be on an equivalent or higher code level as Production. You CANNOT refresh from a higher version to a lower one.

    • Ex: Prod is on 2019.1.21 and Test is on 2019.1.22. This is supported.

    • Ex: Prod is on 2019.1.22 and Test is on 2019.1.20. This is NOT supported.

  • Refreshing from an older Munis release to a newer release is supported, such as Prod 11.3 to Test 2019.1

    • The code level/service pack MUST be equivalent or higher in the target environment

    • Example: 11.3.25 is compatible to refresh to 2019.1.22, but is not supported if the 2019.1 environment is on a lower service pack, such as 2019.1.21

  • The best way to ensure version refresh compatibility is to apply any outstanding updates to the target environment before running a refresh 

  • For AWS Hosted sites you MUST login to a NonProd environment first to ensure that the systems are available for a refresh


  1. Before running the refresh, it is a good idea to check DIA conditions in the Production environment by applying a filter for the applicable target version: DIA Condition Filter

    1. If any DIA conditions are corrected, a new backup of Prod will needed: On Demand Backup For On-Premise Munis Clients

    2. This step is not required, but can help prevent a refresh failure due to invalid DIA conditions

  2. Log into the Application server as tylerservice (or equivalent)

    1. It is very important that you use this account due to required permissions

    2. If there are split Prod and Non-Prod application servers, log into the Non-Prod application server

  3. Launch the refresh script

    1. Option #1

      1. Open File Explorer and navigate to <mundrv>:\cmd (Ex: D:\cmd)

      2. Here you will find the refresh scripts, such as refreshtest.cmd or refreshtrain.cmd

      3. Right click on the desired target environment's script and click Run as administrator

    2. Option #2

      1. Open Command Prompt as administrator

      2. Shift + right click > Run as administrator

      3. Type in refresh<env>, replacing <env> with the desired environment name and press Enter

        1. Ex: refreshtest or refreshtrain

  4. For each prompt, verify you would like to proceed by typing Y and press Enter

  5. The script should begin to run. Please note this process can take some time, depending on how much data is being refreshed. It is important to let the refresh script to run until it is finished.



Additional Information