Upgrading from version 11 is fully automated, the only manual step required is to enter new version 12 licence key after the upgrade, because version 11 keys will not be valid after upgrade. This upgrade guide is valid for all database platforms.
In general, the upgrade consists of three main steps. These steps must be done on all servers in one go.
Stop all version 11 Dbvisit StandbyMP components on all servers
Upgrade: run version 12 Installer choosing the existing version 11 installation directory on each server (order doesn’t matter)
Start all version 12 Dbvisit StandbyMP components on all servers
Upgrade must be performed on dbvcontrol and all dbvagentmanagers connected to that specific dbvcontrol. It is not supported to mix versions.
There is no specific required sequence to upgrade dbvagentmanagers and dbvcontrol. For example it doesn’t matter if you upgrade first dbvcontrol, or if you first upgrade primary dbvagentmanager.
You can choose any sequence which suits you best. We recommend to start with dbvcontrol upgrade, continue to standby dbvagentmanager upgrade and as final step primary dbvagentmanager upgrade.
1. Prerequisites
Before upgrading to version 12 you need to make sure that:
you have valid version 12 Dbvisit StandbyMP key
The existing version 11 key will become invalid after upgrade and you must apply version 12 key in order for synchronization to continue after upgrade.
your standby database should be in sync with primary. In the dashboard you should see that your standby database is lagging only few minutes behind, for example:
If your standby database is out of sync or has any other issues, we recommend to perform fresh v12 installation instead of upgrade and setup standby database from the scratch.
you have downloaded version 12 installer files to all servers where you want to upgrade Dbvisit. The latest available version can be downloaded from the Dbvisit web site https://www.dbvisit.com. Create temporary directory on the server to which you download the version 12 installer files
Determine existing DBVISIT_BASE and user running dbvisit components.
On Linux you can do this by checking existing dbvagentmanager and dbvcontrol process:
$ ps -ef | grep dbv oracle 895913 1 0 09:25 pts/0 00:00:05 /usr/dbvisit/standbymp/bin/dbvcontrol service run oracle 895914 1 0 09:25 pts/0 00:00:01 /usr/dbvisit/standbymp/bin/dbvagentmanager service run
In this example the DBVISIT_BASE is “/usr/dbvisit” and user is “oracle”.
On Windows, right click on dbvagentmanager service and choose properties. Refer to “Path to executable”:
In this example the DBVISIT_BASE is C:\Program Files\Dbvisit. On the “Log On” tab view and remember the user which runs the service:
In this example oracle user.
2. Linux Upgrade
The upgrade consists of four main steps: stop & backup, run v12 installer, startup v12, update licence key. You must perform all upgrade steps as user who run dbvisit components. Do not use root user except for stopping and starting dbvisit components.
You will need to upgrade all dbvagentmanagers and also dbvcontrol to complete the upgrade.
2.1 Prepare installer files for upgrade
Go to the temporary directory to which you downloaded the version 12 installer files. Make sure the ownership of the file is set to the same user who owns Dbvisit Base and extract the file:
chown oracle:oinstall standby-v12.1.0.tar.gz tar -xzf standby-v12.1.0.tar.gz
Verify you can now see two installer files:
-rwxr-xr-x. 1 oracle oinstall 197778472 Mar 27 23:03 install-agent-v12.1.0 -rwxr-xr-x. 1 oracle oinstall 66786142 Mar 27 23:01 install-control-v12.1.0
2.2 Stop dbvisit components and backup existing DBVISIT_BASE directory
Stop all components running on the server as per: Starting and Stopping Standby Multiplatform . We recommend to stop all dbvisit components on other servers which will be part of the upgrade at this point as well.
If you’re using Dbvisit StandbyMP for oracle platform, cleanup existing directories in DBVISIT_BASE: standbymp/oracle/trace, standbymp/oracle/tmp, standbymp/oracle/gs. You can remove all files in those directories, as they are temporary only.
Backup existing DBVISIT_BASE directory, for example:
sudo su - oracle mkdir /home/oracle/v11backup cd /usr/dbvisit cp -avr standbymp /home/oracle/v11backup
make sure to create the backup, you will need to refer to it during upgrade
2.3 Run version 12 installer to upgrade the dbvagentmanager
Perform this step on all primary and standby servers. Run the version 12 installer from the temporary directory:
$ ./install-agent-v12.1.0
You will need to respond to following prompts during installation:
Prompt |
Example Value |
Comment |
|---|---|---|
Please carefully read the end-user license agreement at https://dbvisit.com/eula. Do you agree to the terms of this agreement? |
Yes |
Installation will proceed only with response “Yes” |
Which directory should the software be installed into? |
/usr/dbvisit |
Dbvisit Base directory you have identified during Prerequisites step |
Upgrade Dbvisit StandbyMP Agent Manager from: v11.6.3 to v12.1.0? Yes |
Yes |
Answer yes to perform upgrade on existing v11 DBVISIT_BASE . Your current Dbvisit version will be displayed. |
Agent File Transfer Port: (7890) |
|
Refer to backup dbvagentmanager configuration file, in this example: /home/oracle/v11backup/standbymp/conf/dbvagentmanager.ini enter the same value as in line “FileTransferListenPort” |
Fully Qualified Domain Name for this host: [? for help] (czlin0231) |
czlin0231 |
Refer to backup dbvagentmanager configuration file, in this example: /home/oracle/v11backup/standbymp/conf/dbvagentmanager.ini enter the same value as in line “HostAddress” |
Fully Qualified Domain Name for the Control Center: |
czlin0232 |
Refer to backup dbvagentmanager configuration file, in this example: /home/oracle/v11backup/standbymp/conf/dbvagentmanager.ini enter the same value as in line “NatsAddress” |
Agent Communications Port:(5533) |
Refer to backup dbvagentmanager configuration file, in this example: /home/oracle/v11backup/standbymp/conf/dbvagentmanager.ini enter the same value as in line “NatsPort” |
Example complete output of dbvagentmanager upgrade:
You can now proceed to upgrading next dbvagentmanager or dbvcontrol.
2.4 Run version 12 installer to upgrade the dbvcontrol
Perform this step only on host where dbvcontrol is installed. Run the version 12 installer from the temporary directory:
$ ./install-control-v12.1.0
You will need to respond to following prompts during installation:
Prompt |
Example Value |
Comment |
|---|---|---|
Please carefully read the end-user license agreement at https://dbvisit.com/eula. Do you agree to the terms of this agreement? |
Yes |
Installation will proceed only with response “Yes” |
Which directory should the software be installed into? |
/usr/dbvisit |
Dbvisit Base directory you have identified during Prerequisites step |
Upgrade Dbvisit StandbyMP Control Center from: v11.6.3 to v12.1.0? Yes |
Yes |
Answer yes to perform upgrade on existing v11 DBVISIT_BASE . Your current Dbvisit version will be displayed. |
Control Center Web Server Port: (4433) |
Refer to backup dbvcontrol configuration file, in this example: /home/oracle/v11backup/standbymp/conf/dbvcontrol.ini enter the same value as in line “Gui.WebListenPort” |
|
Agent Communications Port: (5533) |
|
Refer to backup dbvcontrol configuration file, in this example: /home/oracle/v11backup/standbymp/conf/dbvcontrol.ini enter the same value as in line “Nats.NatsListenPort” |
Example complete output of dbvcontrol upgrade:
2.5 Start dbvisit components
Once all dbvagentmanagers and dbvcontrol components are upgraded, you can start all components on all servers as per: Starting and Stopping Dbvisit StandbyMP
2.6 Update licence key
Licence keys for all your configurations (for all database platforms) will now be invalid as shown on this example:
You will need to update the licence key with version 12 licence key that you have as per: Licence Information
This is the final step of the upgrade process on Linux. Let the synchronization run for few days and if there are no issues, delete the backup you created previously.
3. Windows Upgrade
Similar to Linux, the upgrade consists of four main steps: stop & backup, run v12 msi installer, startup v12 and update licence key. During upgrade on Windows, the product is firsst deinstalled (preserving some files) and then installed again.
3.1 Stop dbvisit components and backup existing DBVISIT_BASE directory
Stop all components running on the server by stopping individual services as per: Starting and Stopping Standby Multiplatform . We recommend to stop all dbvisit components on other servers which will be part of the upgrade at this point as well.
Once all dbvisit services are stopped, proceed to create the backup.
If you’re using Dbvisit StandbyMP for oracle platform, cleanup existing directories in DBVISIT_BASE: standbymp/oracle/trace, standbymp/oracle/tmp, standbymp/oracle/gs. You can remove all files in those directories, as they are temporary only.
Afterwards backup existing DBVISIT_BASE (by default C:\Program Files\Dbvisit) directory by copy+paste into backup directory of your choice.
3.2 Run version 12 installer to upgrade the dbvagentmanager
Perform this step on all primary and standby servers. Run the version 12 agent installer from the temporary directory:
Click Next in the very first step:
You must accept EULA (1) in order for upgrade to proceed (2):
On the next screen, you should see Upgrade button (1). If not, it means the registry entries are not correct on the server and the .msi installer wasn’t able to retreive the information about existing v11 installation:
The next screen will show you existing configuration of v11 dbvagentmanager. Dbvagentmanager hostname (in this example CZWIN0191), control center hostname (in this example CZWIN0192) and ports are taken from existing v11 DBVISIT BASE and you’re not required to change those. You must take care only to change the dbvagentmanager service username password and domain (1) according to the user who runs the dbvagentmanager service - which you obtained during prerequisite steps:
Click on next to advance to next step where you should click again Next to confirm current hostname (do not change the hostname):
Confirm DBVISIT BASE folder on next screen, do not change it and click next:
On the final screen click on Install to start the upgrade, or go back to review your settings:
After the upgrade is finished, you will be able to close the installer(1):
You will also see the installer log file location (2).
3.3 Run version 12 installer to upgrade the dbvcontrol
Perform this step only on host where dbvcontrol is installed. Run the version 12 dbvcontrol installer from the temporary directory:
On the frist screen click on Next:
You must accept EULA (1) in order for installation to proceed (2):
On the next screen, you should see Upgrade button (1). If not, it means the registry entries are not correct on the server and the .msi installer wasn’t able to retreive the information about existing v11 installation:
All port information on the next screen are pulled from existing v11 installation, you need only to click on Next:
Confirm DBVISIT BASE folder on next screen, do not change it and click next:
On the final screen click on Install to start the upgrade, or go back to review your settings:
Once the upgrade completes, you will be able to close the installer(1):
You will also see the installer log file location (2).
3.4 Start dbvisit components
Dbvisit v12 components are automatically started during the installation, you will not have to start them manually after the upgrade.
3.5 Update licence key
Licence keys for all your configurations (for all database platforms) will now be invalid as shown on this example:
You will need to update the licence key with version 12 licence key that you have as per: Licence Information
This is the final step of the upgrade process on Linux. Let the synchronization run for few days and if there are no issues, delete the backup you created previously.
4. Rollback Upgrade
If for any reason the upgrade wasn’t successful, you can easily revert to previously installed version. The steps in this section are valid for Windows and Linux
You will need to perform following steps:
4.1 Stop the existing dbvisit processes or services
refer to Starting and Stopping Dbvisit StandbyMP on how to stop existing dbvisit processes or services. If upgrade failed during installation and no processes are running, you can skip this step.
4.2 Restore the backup you created before the upgrade
Delete all files created by failed upgrade from DBVISIT BASE. Fully restore the backup of the DBVISIT BASE folder you created into the original location. Use this folder location as a reference example where restored folders should be placed:
Default directory structure for bin folder on Linux:
/usr/dbvisit/standbymp/bin
Default directory structure for bin folder on Windows:
C:\Program Files\Dbvisit\standbymp\bin
4.3 Start dbvisit processes or services
Refer to Starting and Stopping Dbvisit StandbyMP on how to start existing dbvisit processes or services.
You don’t have to modify or recreate in any way Windows services if they exist when you decide to perform rollback
Windows only:
If failed upgrade left you in state where the dbvisit services were deleted from the system services, you can create them manually after you restore the backed up folder.
Create dbvagentmanager service:
sc create dbvagentmanager binPath="\"C:\Program Files\Dbvisit\standbymp\bin\dbvagentmanager.exe\" service run" start=delayed-auto displayname="Dbvisit StandbyMP Agent"
Add a description to the service:
sc description dbvagentmanager "The Dbvisit StandbyMP Agent provides connectivity to databases on this computer."
Create dbvcontrol service:
sc create dbvcontrol binPath="\"C:\Program Files\Dbvisit\standbymp\bin\dbvcontrol.exe\" service run" start=delayed-auto displayname="Dbvisit StandbyMP Control Center"
Add a description to the service:
C:\Users\Administrator>sc description dbvcontrol "The Dbvisit StandbyMP Control Center provides centralized coordination for Dbvisit StandbyMP Agent operations, as well as the GUI management console."
You can change user running the service and its startup type easily after creation by running services.msc and modifying service properties.
Start the newly created services to finish the rollback.
Comments