Table of Contents | ||||
---|---|---|---|---|
|
...
1. Dbvisit Standby MultiPlatform Components
Noteinfo |
---|
Dbvisit Standby MultiPlatform refers to the product "Dbvisit Standby" and does not refer to the Standby database, Standby server or platform. |
...
There are two main components for Dbvisit Standby MultiPlatform.:
dbvagentmanager (Dbvisit Agent)(Explanation by Alex) | 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) | (Explanation by Alex) |
...
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) | |||||||
---|---|---|---|---|---|---|---|---|
|
|
Unix Based Systems(dbvcontrol) | Windows Based Systems(dbvcontrol) | ||||
---|---|---|---|---|---|
|
|
...
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.
...