Step 4: Running the Dbvisit Installer
The next step in the process is to start the Dbvisit Standby installer. Once you have extracted the tar archive, you will notice a new "dbvisit" directory, which contains all the install files. In this directory you will find a sub directory called "installer" which contains the installation script to be executed. Before executing this script you need to make it "executable". This can be done as follows:
oracle@dbvlin101[/home/oracle/7.0]: ls -l total 109848 drwxr-xr-x 6 oracle oinstall 4096 Aug 21 10:50 dbvisit -rw-r--r-- 1 oracle oinstall 45089534 Aug 21 10:40 dbvisit-standby7.0.01_linux.zip -rw-rw-rw- 1 oracle oinstall 67165696 Aug 19 18:10 dbvisit-standby7.0.01.tar -rw-rw-rw- 1 oracle oinstall 393 Jul 10 23:21 online_user_guide_reference.txt -rw-rw-rw- 1 oracle oinstall 87875 Aug 19 14:17 README.txt oracle@dbvlin101[/home/oracle/7.0]: cd dbvisit oracle@dbvlin101[/home/oracle/7.0/dbvisit]: ls dbvnet dbvserver installer standby oracle@dbvlin101[/home/oracle/7.0/dbvisit]: cd installer oracle@dbvlin101[/home/oracle/7.0/dbvisit/installer]: ls -l total 2648 -rw-r--r-- 1 oracle oinstall 2707057 Aug 19 18:10 install-dbvisit oracle@dbvlin101[/home/oracle/7.0/dbvisit/installer]: chmod u+x install-dbvisit oracle@dbvlin101[/home/oracle/7.0/dbvisit/installer]: ls -l total 2648 -rwxr--r-- 1 oracle oinstall 2707057 Aug 19 18:10 install-dbvisit
Now that the install-dbvisit script has the correct permissions, you may execute this script to start the installer.
The example upgrade below is being performed on a Dbvisit Version 6.0.50 installation that was located in /usr/local/dbvisit
(Dbvisit Base directory).
If you were updating an existing version 7 installation you can follow the same procedure. The key is to make sure you select the correct Dbvisit Base directory where Dbvisit Standby was already installed.
In most cases just accepting the default values should be sufficient:
Start the installer using - ./install-dbvisit command
Provide the DBVISIT_BASE directory where Dbvisit Standby is already installed - /usr/local/dbvisit
Confirm the Oracle Database software owner name - oracle (default)
Specify the dbvnet port number - 7890 (default)
Specify the dbvnet password used for secure communication between nodes - admin (default)
Confirm if you want to auto start dbvnet after installation - yes (default)
Specify the Dbvserver (GUI) protocol (http or https) - https (default)
Confirm the default port number for Dbvserver (GUI) - 8443 (default for https)
Specify the Dbvserver administrator user name - admin (default)
Specify the Dbvserver administrator user password - admin (default)
Confirm if you want to auto start Dbvserver after installation - yes (default)
Do you want to allow error notification (bug tracking Dbvserver) - yes (default)
Confirm bug tracking email address (bug tracking Dbvserver) - bugtrack700@dbvisit.com (default)
Below is an example installation process. At the end of this process the Dbvnet and Dbvserver background processes will be started automatically.
oracle@dbvlin101[/home/oracle/7.0/dbvisit/installer]: ./install-dbvisit ------------------------------------------------------------------------------- Welcome. Your Dbvisit product is going to be installed in a moment. It will be required by you to enter some configuration parameters during installation. ------------------------------------------------------------------------------- It is recommended to make a backup of our current Dbvisit software location for rollback purposes. >>> INSTALLATION DIRECTORY Please specify the Dbvisit main installation directory. The default directory is "/usr/dbvisit". Note: the various Dbvisit products and components - such as Standby, Replicate, Dbvnet, and Dbvserver - will be installed in the appropriate subdirectories of this path. Enter a custom value or press ENTER to accept default [/usr/dbvisit]:
Specify location of current Dbvisit Standby Installation to be upgraded:
Enter a custom value or press ENTER to accept default [/usr/dbvisit]: > /usr/local/dbvisit ------------------------------------------------------------------------------- ABOUT TO CONFIGURE: DBVISIT STANDBY ------------------------------------------------------------------------------- Dbvisit Standby is Dbvisit's disaster recovery software for your Oracle database. >>> ORACLE USER NAME Please specify the Oracle user name on this server. The default user name is "oracle". Note: you must be logged in as the Oracle user to run Dbvisit installer. Custom value or ENTER for default [oracle]: > oracle ------------------------------------------------------------------------------- ABOUT TO CONFIGURE: DBVISIT DBVNET ------------------------------------------------------------------------------- Dbvisit Dbvnet is Dbvisit's network transportation software which provides network connectivity for all Dbvisit products. Dbvnet is a persistent daemon software that must be running on both the primary and standby servers at all times. >>> DBVNET PORT NUMBER Please specify the listening port number for Dbvnet on this server. The default port number used by Dbvnet is 7890. You may choose any value between 1024 and 65535. Note: if you can not access this port after the installation has finished, then please double-check your server's firewall settings to ensure the selected port is open. Custom value or ENTER for default [7890]: > 7890 >>> DBVNET PASSWORD Please specify a password to encrypt all network data transmissions between servers in your network on which Dbvisit software is running. The default password is "admin". Custom value or ENTER for default [admin]: > admin >>> DBVNET START AFTER INSTALLATION Please specify whether or not Dbvnet should be started when the installer has finished. The default setting is "yes". Custom value or ENTER for default [yes]: > yes ------------------------------------------------------------------------------- ABOUT TO CONFIGURE: DBVISIT DBVSERVER ------------------------------------------------------------------------------- Dbvisit Dbvserver is Dbvisit's web server software that provides a web interface for all Dbvisit products. Dbverver is a also a daemon that must be running on both servers if you wish to use its built-in command scheduler or control Dbvisit software through your web browser. >>> DBVSERVER WEB PROTOCOL Please specify the web protocol to be used by Dbvserver on this server. Dbvserver supports both the HTTP and HTTPS web protocols. HTTP sends plain text messages across the network and should therefore be used on local networks only. The default web protocol is "https". If unsure, select HTTPS which safely encrypts all network transmissions. Custom value or ENTER for default [https]: > https >>> DBVSERVER PORT NUMBER Please specify the listening port number for Dbvserver on this server. The default port number used by Dbvserver is 8081 for HTTP and 8443 for HTTPS. You may choose any value between 1024 and 65535. Note: if you can not access this port after the installation has finished, then please double-check your server's firewall settings to ensure the selected port is open. Custom value or ENTER for default [8443]: > 8443 >>> DBVSERVER USER Please specify a user name to be used to access Dbvserver through your web browser later on. Note: this is a virtual user name, i.e. there is no corresponding system user account required. The default user name is "admin". Custom value or ENTER for default [admin]: > admin >>> DBVSERVER PASSWORD Please specify a login password for the user name you just entered. The default password is "admin". Custom value or ENTER for default [admin]: > admin >>> DBVSERVER START AFTER INSTALLATION Please specify whether or not Dbvserver should be started when the installer has finished. The default setting is "yes". Custom value or ENTER for default [yes]: > yes >>> AUTOMATIC ERROR NOTIFICATION In order to improve both the Dbvisit web interface and the network transport layer, an automatic email can be sent to Dbvisit support when a run-time issue is detected by Dbvserver or Dbvnet. Note: information pertaining to Dbvserver and Dbvnet is sent only, and the information is solely used to improve our software. The default setting is "yes". Custom value or ENTER for default [yes]: > yes >>> AUTOMATIC ERROR EMAIL ADDRESS What email address should be used to send automatic error notifications to? Usually, they are sent to a special Dbvisit error collection address. However, you may use your own support email address to receive error notifications first, and then forward them to Dbvisit support later in case there is a serious issue. Note: the Dbvisit notification address below can not be used for support enquiries. Manual email sent to this address will be ignored. Please open a support ticket on the support desk (http://www.dbvisit.com/servicedesk) if you are facing any difficulties. The default email address is "bugtrack700@dbvisit.com". Custom value or ENTER for default [bugtrack700@dbvisit.com]: > ------------------------------------------------------------------------------- Thank you. Configuration is complete. Installation will commence now. ------------------------------------------------------------------------------- >>> Installing Standby - the Dbvisit disaster recovery software... Installing product files...
Existing DDC files Upgrade running:
Installing product files... Updating and migrating existing DDC files in /usr/local/dbvisit... > Removing old DDC files with appended timestamps Updating and migrating existing DDC files in /usr/local/dbvisit/standby... > Migrating DDC file /usr/local/dbvisit/standby/dbv_testdb.env to /usr/local/dbvisit/standby/conf/dbv_testdb.env > Renaming old DDC file /usr/local/dbvisit/standby/dbv_testdb.env to /usr/local/dbvisit/standby/conf/dbv_testdb.env.v6 > Removing old DDC files with appended timestamps Removing old product files... Dbvisit Standby installation complete. >>> Installing Dbvnet - the Dbvisit network layer... >>> Adjusting init script templates for product dbvnet... Please find some init script templates in the following directory: /usr/local/dbvisit/dbvnet/conf/init.d These templates will allow your Systems Administrator to automatically start Dbvserver after a database server reboot. Templates are available for Sun Solaris, IBM AIX, and the Linux flavours OpenSuSE, RedHat/Centos/Fedora & Debian/Ubuntu. >>> Starting Dbvnet daemon, please wait... Dbvnet is up and running on the following ip address and port: niop://172.16.1.111:7890 >>> Installing Dbvserver - the Dbvisit web interface... >>> Adjusting init script templates for product dbvserver... Please find some init script templates in the following directory: /usr/local/dbvisit/dbvserver/conf/init.d These templates will allow your Systems Administrator to automatically start Dbvserver after a database server reboot. Templates are available for Sun Solaris, IBM AIX, and the Linux flavours OpenSuSE, RedHat/Centos/Fedora & Debian/Ubuntu. >>> Starting Dbvserver daemon, please wait... Dbvserver is up and running. Please point your browser to the following URL to log in to the Dbvisit web interface: https://172.16.1.111:8443 Login user name is 'admin' (password 'admin') >>> Dbvisit product and component installation is now complete. >>> NEXT STEPS: CONFIGURE DBVISIT STANDBY VIA COMMAND LINE INTERFACE (CLI): cd /usr/local/dbvisit/standby ./dbvisit_setup Note: Dbvisit can also be configured and run through a (GUI) web browser. Dbvserver (dbvserverd) must be installed and started for this. >>> IMPORTANT - PLEASE NOTE THE FOLLOWING REQUIREMENTS BEFORE CONTINUING: > The Dbvisit Standby, Dbvnet, and Dbvserver software must be installed on both the primary and standby servers. > For network communication between the primary and standby server via Dbvnet port number 7890 must not be blocked by your firewalls. > Dbvnet must be up and running on both the primary and standby servers at all times. > If you wish to use Dbvserver, the Dbvisit web interface, then please ensure port 8443 is open on your servers' firewalls, as well. >>> Thank you for using Dbvisit software!
One key area to review from the above output are these lines indicating an upgrade from version 6 to version 7.
... >>> Installing Standby - the Dbvisit disaster recovery software... Installing product files... Updating and migrating existing DDC files in /usr/local/dbvisit... > Removing old DDC files with appended timestamps Updating and migrating existing DDC files in /usr/local/dbvisit/standby... > Migrating DDC file /usr/local/dbvisit/standby/dbv_testdb.env to /usr/local/dbvisit/standby/conf/dbv_testdb.env > Renaming old DDC file /usr/local/dbvisit/standby/dbv_testdb.env to /usr/local/dbvisit/standby/conf/dbv_testdb.env.v6 > Removing old DDC files with appended timestamps Removing old product files... ..
Regarding the upgrade of existing DDC files
As you can see from the above the installation process picked up that there are version 6 Dbvisit Configuration files (DDC) located in:
/usr/local/dbvisit/standby/dbv_testdb.env
This file is then converted to a version 7 configuration (DDC) file and moved into:
/usr/local/dbvisit/standby/conf/
The original version 6 configuration file is renamed to dbv_testdb.env.v6 and moved also moved to:
/usr/local/dbvisit/standby/conf
Once the installation and upgrade is complete you will end up with the following files in:
/usr/local/dbvisit/standby/conf
Any old backup DDC files with date timestamps as extensions (dbv_SID.dbv.yyyymmdd) will be removed from:
/usr/local/dbvisit/standby
At this stage you should now have the Dbvisit Standby version 7 software installed and if you upgraded from version 5.3.x or 6.0.x your DDC files would have been upgraded as part of the installation process. If you selected to auto-start Dbvnet (Dbvisit Networking) and Dbvserver (GUI) you will have a number of background processes running. Below is example output listing these processes:
oracle@dbvlin101[/home/oracle]: ps -ef|grep dbvisit |grep -v grep oracle 6410 1 0 Aug21 ? 00:00:01 /usr/dbvisit/dbvnet/dbvnetd oracle 6411 6410 0 Aug21 ? 00:00:00 /usr/dbvisit/dbvnet/dbvnetd oracle 6414 6410 0 Aug21 ? 00:00:00 /usr/dbvisit/dbvnet/dbvnetd oracle 6415 6410 0 Aug21 ? 00:00:00 /usr/dbvisit/dbvnet/dbvnetd oracle 6416 6410 0 Aug21 ? 00:00:00 /usr/dbvisit/dbvnet/dbvnetd oracle 6431 1 0 Aug21 ? 00:00:01 /usr/dbvisit/dbvserver/dbvserverd oracle 6432 6431 0 Aug21 ? 00:00:00 /usr/dbvisit/dbvserver/dbvserverd oracle 6434 6431 0 Aug21 ? 00:00:01 /usr/dbvisit/dbvserver/dbvserverd oracle 6436 6431 0 Aug21 ? 00:00:00 /usr/dbvisit/dbvserver/dbvserverd