Question

How do I promote my environment from pre-production to production?

Environment

HVR

Answer

This article provides the procedural steps for an HVR Administrator to export their lower pre-production environment and import it into their upper production environment.

Applies to

The steps in this document apply to promoting to a production environment from or to Windows or Linux/UNIX platforms. Instructions for upgrading an HVR instance in place can be found in the online documentation pages.

• This article applies to version v5.7

• This article does not address generating or using new SSL certificate information

• This article does not address any AgentPlugIn Actions that references a custom file path or any other environment variable that may reference a custom file path

• This article does not apply to moving maintenance tasks, instead they should be recreated.

• This article assumes that the upper production environment is already installed. If not, please refer to our installation guide: https://www.hvr-software.com/docs/installing-and-upgrading-hvr

Scenario

If you have configured your pre-production environment to work as you would like, you have the option to export these replication objects from your pre-production environment and import them into your production environment.

To promote from the pre-production to the production environment, first separately export locations before importing them to the upper environment. The physical locations can then be edited for the upper environment. Once this is complete, export the channel definitions (without locations). Lastly, import and then initialize.

The result is HVR replication services are now running on your production environment.

Prerequisites

1. Make sure you read the compatibility section of the HVR Release Notes to ensure that HVR is compatible with the server you selected to be the HVR Hub for your upper environment.

2. Make sure you download the HVR installation distribution from the HVR product download site for your specific operating system in advance of performing any steps.

3. Make sure you have already installed the database that will serve as the upper HVR repository and created a schema/database/user that has the same name as the lower HVR repository.

Overview

1. Verify your upper environment is installed and ready

2. Export location properties from lower and import to the upper environment

3. Change the physical properties of the location to match the upper environment

4. Export channel definition (except for locations) and import to the upper environment

5. Initialize channel to create the runtime objects and create stateful information

6. Start jobs

Instructions

1. Start the HVR Remote Listener on the upper server

   Ref: https://www.hvr-software.com/docs/Hvrremotelistener

2. Register the Hub

   – Launch the HVR User Interface

   – Navigate to Register Hub using the menu: File > Register Hub

   

   – Enter the details that are specific to connect to your HVR Hub server, which includes:

   – HVR Remote Listener server node, port, and login information

   – Repository Class

   – Database Connection

3. Export Catalogs from the lower HVR Hub to upper HVR Hub

   – Export your Location Definitions by right-clicking on your old Hub, and select Export Catalogs…

   

   • In the Catalog group box, only check Locations.

   – Use the Browse button to choose a folder and name the file to store the output.

   

   – Click OK

   Note: Ensure that the exported files are transferred to the server in the upper environment

4. Import and edit the new locations

   • Change the location properties to point to the new upper environment.

   – Ensure the HVR agent information the database server information is included.

5. Test Connection for all Locations on the upper HVR Hub

   

   – Repeat this step for all connections until all connection tests are successful.

6. Promote the remaining Catalog definitions from the lower HVR Hub to upper HVR Hub

   – Export your Channel Definitions by right-clicking on your lower Hub, and select Export Catalogs…

   

   – In the Catalog group box, uncheck Locations and check Channel Definitions Group Membership, and Configuration Actions for All Channels

   – Use the Browse button to choose a folder and name the file to store the output.

   

   – Click OK

   Note: Ensure that the exported files are transferred to the server in the upper environment

   – Import your HVR Catalog Definitions by right-clicking on your upper Hub, and select Import Catalogs…

   – Select the XML file which you saved the exported catalog definitions

   – Click Open to complete the import

   – Verify that your entire HVR Catalog has been imported to the upper HVR Hub server

   Deploy and start upper HVR Hub

7. Launch the HVR User Interface and connect to the upper HVR Hub repository

   For all channels, you must run HVR Initialize to deploy local runtime objects including Scripts and Jobs

   – Right-click on the channel definition, and select HVR Initialize

   

   – Check Create or Replace Objects

   Note: The first time the channel is deployed in this environment, you will need to select all objects and run Initialize for with all objects selected.

   If you are promoting to. channel that already exists and has already been running, you only need to select Scripts and Jobs while leaving all other object unchecked

   – Click Initialize

   

8. Start all Jobs System

   – Right-click on the Scheduler and select All Jobs in System > Start