Dbvserver
Starting Dbvserver on Linux/Unix
Dbvserver can be started on Linux/Unix as follows. Dbvserver will start in the background and the session can be exited.
/usr/local/dbvisit> dbvserverd
/usr/local/dbvisit> exit
Some erroneous messages may appear on the console if the session is not exited. This is normal.
Stopping Dbvserver on Linux/Unix
Dbvserver can be stopped on Linux/Unix by killing the dbvserverd processes or by running the following command:
/usr/local/dbvisit> dbvserverd stop
Starting and stopping Dbvserver on Windows
Dbvserver on Windows is a Windows service, which can be started, and stopped as a regular Windows service.
The Dbvserver service logs on as the Oracle windows account user.
Managing the Dbvserver service on Windows
The Dbvserver service can be managed using the dbvisit_install_win32 executable. Start the Dbvisit Standby Command Console and change directory to the Dbvserver\bin directory.
To delete or remove the service
C:\Program Files (x86)\Dbvisit\Dbvserver\bin> dbvisit_install_win32 delete
To create the service, the path to the dbvserverd.exe is required, also the Oracle account owner and the password.
C:\Program Files (x86)\Dbvisit\Dbvserver\bin> dbvisit_install_win32 create "c:\program files (x86)\dbvisit" oracle passwd
To show service
C:\Program Files (x86)\Dbvisit\Dbvserver\bin> dbvisit_install_win32 show
For help
C:\Program Files (x86)\Dbvisit\Dbvserver\bin> dbvisit_install_win32
Dbvserver directories
Dbvserver includes the following directories under the main dbvserver directory
- log. This contains the log files for:
- Dbvserver log files.
- Scheduler log files.
- Http access log files.
- Optional debug log files.
- etc. This contains the following files:
- dbvserver.conf, which is the configuration file for Dbvserver.
- scheduler.conf, which is the configuration file for the scheduler.
- init.d directory, which contains the init.d templates to auto start Dbvserver at boot time.
- tmp. Temporary directory used by Dbvserver.
Backing up Dbvserver configuration files
A backup of the Dbvserver configuration files can be made by backing up the /etc folder. This will ensure there is a backup of the
- dbvserver.conf, which is the configuration file for Dbvserver.
- scheduler.conf, which is the configuration file for the scheduler.
- init.d directory, which contains the init.d templates to auto start Dbvserver at boot time.
Dbvserver scheduler
Dbvisit Standby needs to be scheduled on the primary server and the standby server. Please see Scheduling with Dbvserver scheduler
Auto start Dbvserver at boot
If Dbvserver is used, then it is recommended to auto start the Dbvserver process at boot.
On Windows, this can be done by setting the Startup Type on the Dbvserver service to automatic:
On Unix/Linux this can be done by creating an init.d script to auto start Dbvserver at boot time. Example template init.d files can be found in:
/usr/local/dbvisit/dbvserver/etc/init.d
An example init.d script for redhat is:
# Source function library.
. /etc/init.d/functions
DBVISIT=/usr/local/dbvisit
DBVSERVERD=$DBVISIT/dbvserverd
PIDFILE=$DBVISIT/dbvserver/tmp/dbvserverd.pid
PATH=/usr/bin:/bin:/usr/sbin:/sbin
RETVAL=0
prog="dbvserverd"
start() {
# Check if already running
echo -n $"Starting $prog: "
sudo -u oracle $DBVSERVERD
RETVAL=$?
echo return $RETVAL
}
stop() {
echo -n $"Stopping $prog: "
if [ -f "$PIDFILE" ]; then
killproc $DBVSERVERD
fi
RETVAL=$?
echo
return $RETVAL
}
restart() {
stop
start
} case "$1" in
start)
start
;;
stop)
stop
;;
restart)
restart
;;
*)
echo $"Usage: $0 {start|stop|restart}"
exit 1
esac
exit $? e
xit $RETVAL
Dbvserver configuration
The Dbvserver configuration is determined by the settings in the dbvserver.conf file which is located in the etc or conf directory.
This configuration file can be edited manually or updated through the web-based interface by going to the Settings page. The settings page should also be used to update the default password.
Whenever a change is made in the configuration, Dbvserver has to be restarted to read the new config file.
Parameters can be turned off by commenting them out.
The important parameters are as follows:
Parameter | Value | Description |
---|---|---|
servers | https | Turn on https support |
servers | http | Turn on http support |
servers | scheduler | Turn on the scheduler to schedule Dbvisit Standby |
bind_port | 8081 | Http or https port |
bind_port_alternatives | 8082 | If bind_port is not available, then use this port |
proc_minimum | 2 | How many minimum server processes to start. The more processes the more concurrent users can log on to the web service. |
proc_maximum | 2 | How many maximum server processes to start. The more processes the more concurrent users can log on to the web service. |
date_time_zone | Pacific/Auckland | Time zone for the time displayed in the web interface. Please see here for all valid timezones: http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/timezone.html |
date_time_format | %d %b %Y, %H:%M:%S | Date format |
username | admin | Username to login to the web front end |
password | Encrypted password | |
daemon_log_file | log/scheduler | Log file for the scheduler |
standby_delay_minutes | 0 | The lag between the primary server and standby server scheduler. |
logger_file | log/dbvserver | Dbvserver log file |
Dbvserver debugging
Dbvserver debugging can be turned on by setting debug = 1 in the dbvserver.conf file.
The debug information will be written to the dbvserver file on the log directory.