Upgrading to Standby v10

Upgrading to Standby ™️

When reviewing the upgrade process for Standby™️ with customers, users are always surprised by how quick and easy it is.  So what better way to introduce the process, and allay any upgrade doubts than a quick blog and video tutorial? 

Upgrading is also a perfect time to evaluate the implementation of some of Standby’s more advanced features, so I have included a couple for you to consider during our upgrade planning.  

Many Reasons to Upgrade

Standby™️ v10 builds on our Gold Standard Disaster Recovery by adding four key features that deliver greater protection, value, and performance to maximise utilisation of your  Oracle infrastructure: (1) Multi-tenancy support; (2) Reporting Replicas and Test/Dev Snapshots; (3) GUI improvements; and (4) A new and upgraded network utility. Read more on our Standby™️ product page.

Please note that v10 is available for Linux and Windows OS only. For other operating systems we recommend upgrading to our latest Standby™️ v9.

Things to do Before Upgrading

• You do not need to recreate the standby database if your standby database already exists and is in sync with the primary.
• Confirm you are running a supported operating system and version of Oracle. Windows or Linux with Oracle version 10.2.0.5 or above. See the compatibility matrix. 
• Download the latest version on the download page and request your new license at sales@dbvisit.com. 

Steps to Upgrade from Standby™️ v9 to v10

1. Prepare your existing v9 environment – Standby™️ v9 to v10
2. Install Standby™️ v10 
3. Login to the Central Console.  Update the DDC configuration.  Apply the v10 License Key. Send and Apply Logs,  and Run the Log Gap report.

Detailed Installation Video:

Post-upgrade steps:

1. Scheduling - Start the Daemon process
2. Enable Email Notifications
3. Configure Dbvisit Archive Log Management Module (AMM)
4. Configure Log and Trace Management

Maximise Standby™️ by utilizing these features:

Standby™️ includes many features that can enhance the speed, resilience, and value of your Oracle infrastructure.  Why not investigate implementing some value add features, including:

• Standby™️ Reporting Replicas and Dev/Test Snapshots
• Refresh a Standby PDB from Primary

We hope you found this blog and associated resources helpful, let us know if you have any questions.