We're here to help!

Standby FAQ's - Version 8.0

Follow
Description

Below are some of the Frequently Asked Questions by customers , while installing the new standby version 8.0, which is quite different from the previous versions of standby , with loads of improvements and features being made available in the new version. The commands have also changed in version 8.0, so its always a Best Practice to view the version specific user guide to avoid issues.

FAQ's

1.     The  version 7 installation was requiring a database schema/user to store some management stuff. The version 8 does not seem to need it anymore? So can we drop the database user for version 7?

Standby V8 uses an external data store for its repository therefore after you have upgraded to Standby V8 you can drop the Oracle repository owner from the database (ie. dbvisit7). See Link for additional Information.

https://dbvisit.atlassian.net/wiki/display/DS8QSG/Installing+Dbvisit+Standby#InstallingDbvisitStandby-3.1.TheDbvisitStandbyRepositoryOverview

2.     Inside the dbvserver web GUI we can see the ACTIVE TASK LIST. Is it intentional that only those jobs are reported there, which have been started from the web GUI? The scheduled jobs from primary and standby to transfer and apply the archived logs do not show up there in our setup.?

Please see the below link for additional information on this topic.

https://dbvisit.atlassian.net/wiki/display/DS8QSG/Central+Console%3A+Tasks+and+Task+Tracking

3.        The documentation states that we can run a “dbvisit daemon” on my primary and standby. But we do not get for what purpose. The management GUI runs on a third and separate machine and archivelog transfer and apply are scheduled jobs on the primary and standby server. Can you explain what the purpose and benefit is to run the “dbvisit daemon” on both standby and primary?

The shipment & apply logs can either be scheduled as they were in Standby V7.  Optionally you can ship / apply them via a background/daemon process instead of the scheduled process.You would choose one or the other not both. See linked page for additional information

https://dbvisit.atlassian.net/wiki/display/DS8QSG/Dbvisit+Standby+Scheduling#DbvisitStandbyScheduling-4.RunningDbvisitStandbyintheBackground

4. How to Apply License for my standby version 8.0 

The steps to apply license for the standby version 8.0 is provided in the link below. The standby 8.0 has completely different command sets compared to the previous versions, so its best always to refer the user guide.

https://dbvisit.atlassian.net/wiki/display/DS8QSG/Dbvisit+Standby+License

5. What are the unique features of the standby product ? 

NEW Dbvisit Standby Version 8 Features: 

  • New Central Console - easily manage one or multiple configurations from one web based interface
  • Support for Cascading Standby Database (Create standby from Standby)
  • New Dbvnet network component - enhanced encryption and compression
  • New Oracle RAC support with the option to create a RAC enabled Standby Database.

http://www.dbvisit.com/products/dbvisit_standby_database_for_oracle_disaster_recovery/

6. How is the RPO and RTO while deploy DBvisit Standby ?

When scheduling Dbvisit Standby there are a few key factors to consider

such as the Recovery Time Objective (RTO) and Recovery Point Objective (RPO) of your environment. This is a business decision, but certain factors play a key role.

These are:

  • Speed of the network
  • Activity on the database
  • Speed of the disks
  • Compression method chosen and CPU power to compress and uncompress archive log files.

 The schedules can be customized based on requirements. There is continuous monitoring which can set up to get notified for any delay. The daemon process automatically detects the archivelog in the primary and forces a logswitch in primary when it does not see a new archivelog for a certain period, by doing this it makes sure that the delay between Primary and Standby are minimum.

7. What is the required bandwidth between primary and secondary site, how to estimate?

To estimate the bandwidth, we might need to understand from the database perspective

  • Size of the redologs.
  • Number of archivelogs generated in a day and size.
  • What is the application environment (OLTP/DWH)?

We should also test network speed under these circumstances.

8. Does the DBvisit synchronize the archive log or redo log to DR site DB server? , if its archivelog will there will be a delay ?

Archivelogs are used to synchronise the Standby, there is a legitimate delay in any DR solutions, since the archivelog from the primary must be sent to the Standby site and applied, but this will also be based on the other factors explained in the Question 2.

 But rest assured in case of any disaster scenarios, activating a standby site is very straight forward and easy process using Dbvisit product and can be done

using a single Command Line or by using a GUI interface.

Have more questions? Submit a request

Comments