Introduction
1. Dbvisit Standby MultiPlatform Components
Dbvisit Standby MultiPlatform refers to the product "Dbvisit Standby" and does not refer to the Standby database, Standby server or platform.
The Dbvisit standby has two main components:
It is important to note that the user running Dbvisit on Unix-based systems MUST be the same user used to install and run the Oracle/SQLServer Database software. But, the services are stopped and started using the root user.
On Windows-based systems
The installation for Oracle-based systems does not have to be the same user as the Oracle Home Owner, but MUST be in the ORA_DBA and Local Administrators group with "Log on as a service" permission.
For SQL Server, the installation must be done as the Administrator and the services must run as an Administrator or as a user which has access to the user databases and not as Local System User (This is mainly when then SQL Server instance runs on Windows Authentication Mode). If you are using mixed-mode you should be able to proceed with the configuration by using SQL Authentication (sa user/password)
There are two main components for Dbvisit Standby MultiPlatform:
dbvagentmanager (Dbvisit Agent) | This component should be installed once on each database server. The Dbvisit Agent is responsible for connecting to the Oracle and/or SQL Server databases, and communicating with the Dbvisit Control Center. |
dbvcontrol (Dbvisit Control center/GUI) | This component should be installed once only, ideally on a 3rd server separate from either the primary or standby database server. It is also possible to install this on the standby server. The Dbvisit Control Center contains the communication hub, logic center, the user interface, and the Observer. In simple terms, the Control Center is the brains behind the operation - it is through the Control Center that you will interact with the product the vast majority of the time. |
2. Dbvisit Standby MultiPlatform Directory Structure.
The following are the directory structure for Dbvisit Standby Multiplatform. The default location for Unix based system is /usr/dbvisit and for Windows, it's c:\Program Files\Dbvisit. It is however recommended to install the dbvcontol or the Control Center to be installed on a separate machine and not on the database servers.
Unix Based Systems (Dbvagentmanager) | Windows Based Systems(Dbvagentmanager) |
|---|---|
/usr/dbvisit/standbymp
├── backup
├── bin
├── certificates
├── conf
├── db
├── dbvnet
│ ├── conf
│ └── log
├── log
└── oracle
├── backup
├── conf
├── doc
├── gs
├── lib
├── log
├── meta
├── pid
├── snap
├── support
├── tmp
└── trace | C:\Program Files\Dbvisit\standbymp>tree
├───backup
├───bin
├───certificates
├───conf
├───db
├───dbvnet
│ ├───conf
│ └───log
├───log
└───oracle
├───backup
├───conf
├───doc
├───gs
├───log
├───meta
├───pid
├───snap
├───support
└───tmp |
Unix Based Systems(dbvcontrol) | Windows Based Systems(dbvcontrol) |
|---|---|
/usr/dbvisit
├── standbymp
│ ├── backup
│ ├── bin
│ ├── certificates
│ ├── conf
│ ├── db
│ └── log
└── upgradeBak |
3. Using Dbvisit Standby
After the installation of the Dbvisit Standby MultiPlatform, you are recommended to use the central console for creating configurations for Oracle/SQLServer. Once the configuration is created you should be able to set your DR databases.
Please ensure you have reviewed the Release notes as well as system requirements and pre-requisites.