Upgrading from v9 or v10
1. Considerations
Dbvisit v11 uses different ports than v9 and v10
Before doing an upgrade, make sure that necessary ports are allowed as per the system requirements https://dbvisit.atlassian.net/wiki/spaces/DSMP/pages/3238264943/System+Requirements#6.--Network-Requirements
V11 uses different processes
Processes are replaced as follows:
v10 dbvnet and dbvagent and dbvctl daemons are merged into v11 dbvagentmanager
v10 dbvserver and observer are merged into v11 dbvcontrol
In case you have automated startup implemented or if you have RAC or Oracle SEHA you will have to modify existing cluster resources. Example how to create cluster resources for v11 is for instance on this page: https://dbvisit.atlassian.net/wiki/spaces/DSMP/pages/3500081153
2. Introduction
The upgrade process from the older version to multiplatform is simple and straightforward. The versions from which you can upgrade to multiplatform are Version 9.0.x and Version 10.x. Most of the old ports are retained with Multiplatform except Once. The below table will show the difference in the ports between old versions and Multiplatform.
A separate license is required for both Oracle and Microsoft SQL Server. if you don’t have a permanent license key , contact renewals@dbvisit.com
Default Ports | Dbvisit Standby Version 9.0.x and 10.x | Dbvisit Multiplatform |
|---|---|---|
7890 | Dbvnet | Dbvisit File transfer port |
7891 | Dbvagent | Not used in Multiplatform |
4433 | Dbvserver | Control center |
10853 | Observer | Not used in Multiplatform |
5533 | Not used in earlier versions | Multiplatform agentmanager port |
From the above table, you can see that ports 7891 and 10853 is no longer used and the new port used for agent manager is 5533.
Note that the upgrade process will pickup the ports from your v9/v10 configuration if non-default ports were used there.
If your current configuration is using an alternative copy and remote shell methods like SCP and SSH instead of Dbvnet then you need to switch back to Dbvnet before upgrading. Dbvisit Standby MP does not support these methods anymore.
Before starting the upgrade process set the following in your DDC file:
RSH= <leave blank>CP= <leave blank>NETPORT=7890NETPORT_DR=7890
2.1 Snapshot considerations
If the current v9 or v10 configuration utilize the Snapshot functionality the following steps need to be performed prior to upgrading to version 11:
Using GUI delete all Single snapshots instances presented.
For all the Snapshot Groups use the trash bin button to stop the snapshot generation and to delete all snapshots within the given Snapshot group. Optionally, you can delete the snapshot groups themselves. All of them will need to be created manually again after the upgrade is finished.
3. Linux - Example of the Upgrade process
3.1 Considerations
It is recommended to be on the latest update of Dbvisit Standby version 9 or 10 prior to upgrading to Multiplatform.
The upgrade process consists of two key steps:
Upgrade (install) the new version 11 software.
Upgrade the DDC files and repository to reflect the latest release.
When upgrading from version 9.0.x or 10.0.x, the process is easy and should only take a few minutes.
The high level recommended steps are:
Stop your Dbvisit Schedules if you have any running.
Stop or wait for any Dbvisit processes that might still be executing.
Backup the Dbvisit Base location where your software is installed.
Download the latest version from www.dbvisit.com
Extract the install files into a temporary folder, example /home/oracle/MP
Start the Installer and select to install the required components.
Once the update is complete, you can remove the temporary install folder where the installer was extracted.
Apply the new version 11 license key.
It is recommended to run a manual send/apply of logs once an upgrade is complete.
Enable the automatic standby update for scheduling the send and apply.
The section below will show you a detailed example of the upgrade process.
3.2 Prerequisite Steps
Stop all schedules if used - on Unix systems if schedules are used it would be via the UNIX "CRON" schedule. You can use the "crontab -l" command to list any schedules and if you want to edit them use "crontab -e"
Stop the Dbvisit components. Check the processes by running “ps -ef |grep dbv” which would list out processes that are running . Below is the example for stopping the Dbvisit components from both primary and standby. We have our dbvserver installed in the standby server in this example.
Primary: dbvel71. Standby: dbvel72
Stopping Components in Primary
[oracle@dbvel71 standby]$ ps -ef |grep dbv
oracle 2682 1 2 12:00 ? 00:00:02 ./dbvctl -d orcl21c -D start
oracle 2829 3974 0 12:02 pts/0 00:00:00 grep --color=auto dbv
oracle 30150 1 0 11:03 ? 00:00:23 ./dbvnet -d start
oracle 30158 1 0 11:03 ? 00:00:03 ./dbvagent -d start
[oracle@dbvel71 standby]$ ./dbvctl -d orcl21c -D stop
Stopping Dbvisit Daemon...
Successfully stopped.
[oracle@dbvel71 standby]$ cd ../dbvnet/
[oracle@dbvel71 dbvnet]$ ./dbvnet -d stop
Stop signal has been sent to pid: 30150
[oracle@dbvel71 dbvnet]$ cd ../dbvagent/
[oracle@dbvel71 dbvagent]$ ./dbvagent -d stop
Stop signal has been sent to pid: 30158
[oracle@dbvel71 dbvagent]$ ps -ef |grep dbv
oracle 2886 3974 0 12:03 pts/0 00:00:00 grep --color=auto dbv
[oracle@dbvel71 dbvagent]$
Stopping Components in Standby
[oracle@dbvel72 standby]$ ps -ef |grep dbv
oracle 405 1 0 11:04 ? 00:00:01 ./dbvnet -d start
oracle 413 1 0 11:04 ? 00:00:05 ./dbvagent -d start
oracle 420 1 0 11:04 ? 00:00:16 ./dbvserver -d start
oracle 5841 1 1 12:00 ? 00:00:02 ./dbvctl -d orcl21c -D start
oracle 6066 4048 0 12:03 pts/0 00:00:00 grep --color=auto dbv
[oracle@dbvel72 standby]$ ./dbvctl -d orcl21c -D stop
Stopping Dbvisit Daemon...
Successfully stopped.
[oracle@dbvel72 standby]$ cd ../dbvnet/
[oracle@dbvel72 dbvnet]$ ./dbvnet -d stop
Stop signal has been sent to pid: 405
[oracle@dbvel72 dbvnet]$ cd ../dbvagent/
[oracle@dbvel72 dbvagent]$ ./dbvagent -d stop
Stop signal has been sent to pid: 413
[oracle@dbvel72 dbvagent]$ cd ../dbvserver/
[oracle@dbvel72 dbvserver]$ ./dbvserver -d stop
Stop signal has been sent to pid: 420
[oracle@dbvel72 dbvserver]$ ps -ef |grep dbv
oracle 6110 4048 0 12:04 pts/0 00:00:00 grep --color=auto dbv
[oracle@dbvel72 dbvserver]$Backup the Dbvisit Standby installation directory (optional - but recommended)
In this example, we will backup the /usr/dbvisit directory using the "tar" command to create a backup in a backup folder called /home/oracle/backup. You can use the "du -sh" command to confirm the /usr/dbvisit directory size prior to backup. The "tar" command used in this case will use the -z option to enable compression.
[oracle@dbvel72 dbvisit]$ pwd
/usr/dbvisit
[oracle@dbvel72 dbvisit]$ du -sh .
453M .
[oracle@dbvel72 dbvisit]$ tar czf /home/oracle/backup/dbvisit_backup_31Dec2021.tar.gz .
[oracle@dbvel72 dbvisit]$ ls -lrt /home/oracle/backup/dbvisit_backup_31Dec2021.tar.gz
-rw-r--r--. 1 oracle oinstall 83521643 Dec 31 11:36 /home/oracle/backup/dbvisit_backup_31Dec2021.tar.gz
[oracle@dbvel72 dbvisit]$3.3 Agentmanager installation
[oracle@dbvel71 ~]$ cd MP/
[oracle@dbvel71 MP]$ ls -lrt
total 303208
-rwxr-xr-x. 1 oracle oinstall 28322375 Dec 28 12:54 install-control-v11.0.0RC3-1-g2c6a9646
-rwxr-xr-x. 1 oracle oinstall 126913353 Dec 28 12:55 install-agent-v11.0.0RC3-1-g2c6a9646
-rw-------. 1 oracle oinstall 5767 Dec 28 17:15 setup.log
[oracle@dbvel71 MP]$ ./install-agent-v11.0.0RC3-1-g2c6a9646
+----------------------------------------------------------------------+
| ____ _ _ _ __ __ ____ |
| / ___|| |_ __ _ _ __ __| | |__ _ _| \/ | _ \ |
| \___ \| __/ _' | '_ \ / _' | '_ \| | | | |\/| | |_) | |
| ___) | || (_| | | | | (_| | |_) | |_| | | | | __/ |
| |____/ \__\__,_|_| |_|\__,_|_.__/ \__, |_| |_|_| |
| Copyright 2021 |___/ By Dbvisit |
+----------------------------------------------------------------------+
Welcome to Dbvisit StandbyMP setup version v11.0.0RC3-1-g2c6a9646.
? Which directory should the software be installed into? /usr/dbvisit
? Upgrade Dbvisit Standby from: 10.1.0_0_gba3a9e08 to v11.0.0RC3-1-g2c6a9646? Yes
- - - You are now configuring the Dbvisit StandbyMP Agent - - -
The Agent will listen on the following discovered addresses:
- 127.0.0.1
- 10.0.2.9
- 192.168.56.9
? Agent File Transfer Port: 7890
? Fully Qualified Domain Name for this host: dbvel71
? Fully Qualified Domain Name for the Control Center: 192.168.56.10
? Agent Communications Port: 5533
Each Dbvisit StandbyMP Agent and the Dbvisit StandbyMP Control Center must
be configured with the same passphrase. This is how we know that they are all
intended to be part of the same system. Please specify a strong passphrase - we
suggest at least 12 characters, containing at least 2 numbers and 2 symbols.
? Passphrase: *******
? Confirm Passphrase: *******
- - - Dbvisit StandbyMP Agent configuration finished - - -
- - - Ready to perform installation - - -
? Do you wish to proceed with the setup using the supplied configuration options? Proceed with setup
- - - Performing installation - - -
Copying software files to '/usr/dbvisit'...
Writing Agent configuration file '/usr/dbvisit/standbymp/conf/dbvagentmanager.ini'...
- - - Installation successful! - - -
To enable the installed Dbvisit StandbyMP components to run as system services, you will need to execute some commands as the "root" user in order to complete the setup.
To install the system service(s), you can run, substituting the name of the user to run as if it is different from the current user:
sudo /usr/dbvisit/standbymp/bin/dbvagentmanager service install --user oracle
To start the system service(s), you can run:
sudo /usr/dbvisit/standbymp/bin/dbvagentmanager service start
- - - Configuration Summary - - -
Install Directory: /usr/dbvisit
Fully Qualified Domain Name for this host: dbvel71
Fully Qualified Domain Name for the Control Center: 192.168.56.10
Agent Communications Port: 5533
Agent File Transfer Port: 7890
- - - Installation Summary - - -
The following actions have been performed:
- Backed up files for components being upgraded to: /usr/dbvisit/upgradeBackup
- Installed Dbvisit StandbyMP Agent software into: /usr/dbvisit/standbymp
- Agent settings are available in the configuration file: /usr/dbvisit/standbymp/conf/dbvagentmanager.ini
- Imported DDCs from previous version
- Generated new security certificates in: /usr/dbvisit/standbymp/certificates
- - - UPGRADE SUCCESSFUL - - -Start the agent manager in primary
Run the same process on the standby server to install the agent manager.
Start the components
3.4 Install the Control Center
The control center must be installed only on one server. This must be either a separate server or on the standby server. In this example we are installing the control center in standby server.
Start the control center
3.5 Upgrade the DDC from the control center and License
3.5.1 Login to control center
3.5.2 Import the DDC’s
Unlike the earlier versions where the DDC’s appear in the Managed configurations page, for the Standby MultiPlatform, the primary host needs to be selected and then the DDC has to be imported. Go to New configurations and click on Start with Oracle ( 1 )
Select the Primary database server host. In the example the primary database host is dbvel71
This will list the configuration that has been upgraded from the previous version and then click on Import Configuration ( 1 )
3.5.3 Update The licence key
After the configuration is imported. Click on UPDATE to install the new license key for Dbvisit Standby MultiPlatform
Enter the new license key ( 1 ) and click on Update ( 2 ) to install the new key.
The New license key is updated and shows the expiration date for the license.
4. Windows - Example of the Upgrade process
4.1 Considerations
It is recommended to be on the latest update of Dbvisit Standby version 9 or 10 prior to upgrading to Multiplatform.
The upgrade process consists of two key steps:
Upgrade (install) the new version 11 software.
Upgrade the DDC files and repository to reflect the latest release.
When upgrading from version 9.0.x or 10.0.x, the process is easy and should only take a few minutes.
The high level recommended steps are:
Stop your Dbvisit Schedules and all services if you have any running.
Stop or wait for any Dbvisit processes that might still be executing.
Backup the Dbvisit Base location where your software is installed.
Download the latest version from www.dbvisit.com
Extract the install files into a temporary folder, example C:\Temp\MP
Start the Installer and follow the steps
Once the update is complete, you can remove the temporary install folder where the installer was extracted.
Apply the new version 11 license key.
It is recommended to run a manual send/apply of logs once an upgrade is complete.
Enable the automatic standby update for scheduling the send and apply.
The section below will show you a detailed example of the upgrade process.
4.2 Prerequisite Steps
On primary and standby server stop all dbvisit services and Windows scheduler jobs (if used instead of dbvctl daemon processes). All services must be visible as stopped, like so:
2. On primary and standby, backup the Dbvisit Standby installation directory (optional - but recommended). Before backup, you can remove standby\trace folder to save time and space. Copy & paste the installation directory:
4.3 Agentmanager installation
On primary and standby server install dbvagentmanager - run the installer and follow the prompts. Click next, accept licence agreement and then choose upgrade:
Next, proceed to fill in detailed settings for dbvagentmanager:
Specify local hostname and hostname for control center host - controlcenter host is the server where you have your dbvserver installation. Note that you don’t have to use FQDNs. You only need to be consistent with hostnames (FQDN, or on-FQDN) which you used in your v10 or v9 DDC configuration.
Fill in username & password - those are credentials used to run dbvagentmanager service
Next, set passphrase to generate certificates for secure communication. It is not relevant to any password used in v10 or v9 configuration, choose any random string. You will use the same string for all servers where Dbvisit is running:
As last step choose where to install dbvisit standbymp (you can leave the default value):
On last screen click “Install” to finish and start the installation.
After instllation is finished, verify that old services were removed and dbvagentmanager service was successfully started:
If there are any old services remaining you can use commands “sc delete dbvagent”, “sc delete dbvnet”, “sc delete dbvobserver”, “sc delete dbvserver” to manually remove the services, they are no longer needed.
4.4 Control Center installation
The control center upgrade is to be run one server only - were your dbvserver was installed. Start the controlcenter installer and choose upgrade option:
There’s usually no need to change any ports, proceed with further steps:
On next screen, set passphrase to generate certificates for secure communication. This is the same string you used for all servers where you upgraded dbvagentmanager:
Modify install directory if needed, click Next and the click on Install to start the installation:
Once the installation is finished, verify that dbvcontrol service is running correctly:
4.5 Upgrade the DDC from the control center and License
Upgrading the DDC file steps and also updating the licence steps are completely the same for Windows and Linux Operating system (as they are performed from GUI only). Refer to chapter “4.5 Upgrade the DDC from the control center and License” for Linux to finalize the Windows upgrade process.