...
Dbvisit uses very similar concept for standby database synchronization for Oracle, SQL Server and Postgres.
Oracle concept:
| Info |
|---|
Oracle Standby database is always in MOUNT status during synchroniation. It can be opened READ-ONLY, but in this state, apply of archivedlogs is paused |
SQL Server concept:
...
| Info |
|---|
Similar to Oracle, SQL Server Standby database is always in RESTORING status during synchroniation. It can be opened READ-ONLY, but in this state, apply of archivedlogs is paused |
Postgres Streaming concept:
...
| Info |
|---|
Dbvisit StandbyMP allows to create Postgres Standby cluster in HOT mode (read-only access is possible during synchronization) or WARM mode (read-only access can’t be obtained). |
...
3. Considerations for users running Dbvisit Standby version 11
Dbvisit StandbyMP Version 12 shares the same code base with version 11 and if you are on version 11, there’s no immediate need for you to upgrade to version 12. Version 11 will remain supported for sufficient amount of time in the future. More details on:
https://support.dbvisit.com/hc/en-us/articles/8117254640911-Dbvisit-Standby-Version-Support-Matrix
The notable differences from version 11 and reasons for upgrade to version 12 are :
version 12 contains public API API which help users with integrating the product with existing monitoring systems or deployment flows
version 12 contains new command line interface CLI which enables users to perform complete configuration and deployment without need of interaction with GUI.
| Info |
|---|
It is still needed and necessary to install and maintain dbvcontrol as it is integral part of NATS messaging system which is necessary for proper functionality of the product |
version 12 will be prioritized for receiving new features and updates over version 11
4. Considerations for users running Dbvisit Standby versions 8,9 or 10
...