| Table of Contents |
|---|
1. Introduction
The purpose of this Deployment guide is to demonstrate the way in which Dbvisit Standby 8.0 software can be used within the Azure Cloud Hosting Space. In this guide, we focus on both the Primary and Standby databases being hosted on MS Azure Windows 2016 Virtual Machines. In another document, we focus on 'On-Premise Primary' to Standby in the Azure Cloud. A link that document can be found here
...
| Info |
|---|
| The setup will be from Single Instance Primary Database to Single Instance Standby Database with Datafiles stored on standard filesystems on a Windows Platform. However, the options for configuring Dbvisit Standby are in no way limited to this. |
2. Initial Setup and Configuration
2.1 Provisioning the Servers
Connect to Azure Portal and Select 'Compute' from the options for 'New'
...
| Primary Server Details | Standby Server Details |
|---|---|
Name: dbvwin2016 vCPUs: 2 OS: Windows 2016 Datacenter Memory: 14G Storage: 28G Version: 12.1.0.2 Edition: Enterprise Edition Database: LAA Dbvisit Base: C:\Program Files\Dbvisit Standby Version: 8.0.14.19191 | Name: dbvwin2016DR vCPUs: 2 OS: Windows 2016 Datacenter Memory: 14G Storage: 28G Version: 12.1.0.2 Edition: Enterprise Edition Database: LAA Dbvisit Base: C:\Program Files\Dbvisit Standby Version: 8.0.14.19191 |
2.2 Preparing the Servers
Connect to each of the servers using the Microsoft Remote Desktop details provided earlier and copy and then unzip the required binaries for the Oracle and Dbvisit Installations from the local mapped drive.
...
At this stage, the servers are ready for the next stage of installing the Dbvisit Standby software.
3. Install, Configure and Run the Standby software
3.1 Installing and Configuring the Software
Unzip installer following the instructions in the dbvisit installation guide as an admin user (in this guide: user oracle).
...
As part of the installation of Dbvisit Standby on Windows. The services for each component are created and automatically started (e.g. from DR Server)
| Note |
|---|
Version 8.0.20 has a new parameter, that of DBVSERVER_PUBLIC_HOST (parameter public_address in dbvserver.conf) Rather than accepting the default hostname prompt here, the public-facing IPv4 address of the Cloud Host should be used. Public-facing IPv4 address that will be supplied to the Agents (Dbvagent) to be used for pushing information back to the Central Console. This is the externally resolvable address supplied to dbvagent, not an additional listener address on dbvserver itself. |
3.2 Start the GUI and Create the DDC
| Info |
|---|
The following browsers are supported when using the Dbvisit Standby Web Based interface (latest versions recommended)
Future support for the following browsers are planned:
|
...
The configuration can be viewed and edited from the 'Manage Configurations' Tab.
3.3 Create the Standby Database
3.3.1 Creating the Standby with the GUI
Choose the Create Standby Database Tab from the Home Screen.
...
Click Submit. The progress can be monitored from the resulting icon in the status bar.
3.3.2 Creating the Standby with the CLI
To Create the Standby database with the command line is shown below
| Code Block |
|---|
C:\Program Files\Dbvisit\Standby>dbvctl -d DBV1 --csd
>>> Running pre-checks please wait... done
What would you like to do:
1 - Create standby database (and optionally save settings in template)
2 - Help
3 - Terminate processing
Please enter your choice [1]: 1
-------------------------------------------------------------------------------
Answer Yes to transfer the datafiles directly to the standby server (not
recommended for large database or slow networks)
Note tablespaces will be placed in backup mode for direct copy.
Answer No (recommended) to create an RMAN backup of primary datafiles in a
temporary location and transfer the backup to the standby server
=>Do you want to copy database files directly to the standby server? [N]:
Your input: N
Is this correct? <Yes/No> [Yes]:
-------------------------------------------------------------------------------
=>Do you want to use TRANSPORTABLE MEDIA to transfer the database backup to the
standby server? Transportable media is an external device such as a USB drive
that is first plugged into the primary server and then manually transferred to
the standby site and plugged into the standby server to continue the process.
It can be used for large databases or slow networks.
Specifying No means the network will be used to transfer the database backup.
[N]:
Your input: N
Is this correct? <Yes/No> [Yes]:
-------------------------------------------------------------------------------
A temporary location must be specified on DBVWIN2016 where the database will be
backed up to first.
This location must be big enough to hold RMAN backup of the whole database
(1.29GB).
=>Specify the location on this server: [C:\windows\temp]:
Your input: C:\windows\temp
Is this correct? <Yes/No> [Yes]:
-------------------------------------------------------------------------------
A temporary location must be specified on DBVWIN2016DR where the database
backup will be copied to before moving to specified locations.
=>Specify location on remote server: [C:\windows\temp]:
Your input: C:\windows\temp
Is this correct? <Yes/No> [Yes]:
-------------------------------------------------------------------------------
Oracle Home User login might be required to create the Oracle Windows service
Leave empty if Oracle Home User is Windows built-in account
=>Specify Oracle Home User: []: oracle
Your input: oracle
Is this correct? <Yes/No> [Yes]:
=>Specify Oracle Home User password: []: *********
Your input: *********
Is this correct? <Yes/No> [Yes]:
-------------------------------------------------------------------------------
=>Do you want to use an existing standby spfile rather than create a new one
from scratch? [N]:
Your input: N
Is this correct? <Yes/No> [Yes]:
-------------------------------------------------------------------------------
=>Do you want to register a newly created standby database with Oracle Restart?
[N]: N
Your input: N
Is this correct? <Yes/No> [Yes]:
The following oracle database parameters will be set in the standby database pfile or spfile:
-------------------------------------------------------------------------------
SID NAME VALUE
* audit_file_dest C:\app\oracle\admin\LAA\adump
* compatible 12.1.0.2.0
* control_files C:\APP\ORACLE\ORADATA\LAA\CONTROL01.CTL,C:\APP\ORACLE\FLASH_RECOVERY_AREA\LAA\CONTROL02.CTL
* db_block_size 8192
* db_domain
* db_name LAA
* db_recovery_file_dest C:\app\oracle\flash_recovery_area
* db_recovery_file_dest_size 4102029312
* db_unique_name LAA
* diagnostic_dest C:\app\oracle
* dispatchers (PROTOCOL=TCP) (SERVICE=LAAXDB)
* log_archive_format ARC%S_%R%T.arc
* memory_target 2113929216
* open_cursors 300
* processes 150
* remote_login_passwordfile EXCLUSIVE
* spfile OS default
* undo_tablespace UNDOTBS1
-------------------------------------------------------------------------------
What would you like to do:
1 - Proceed with creating the standby database
2 - Edit oracle database parameters for the standby database pfile/spfile
3 - Terminate processing
Please enter your choice [1]:
Validating oracle database parameters... please wait
=>SUCCEEDED
-------------------------------------------------------------------------------
=>Create standby database template for DBV1 using provided answers? [Y]:
Your input: 1
Is this correct? <Yes/No> [Yes]:
-------------------------------------------------------------------------------
=>Continue with creating a standby database? (If No processing will terminate,
the saved template will be available for future use) [Y]:
Your input: 1
Is this correct? <Yes/No> [Yes]:
>>> dbvctl will now run a pre-flight check for standby database creation. An attempt will
be made to create a standby (s)pfile using oracle standby database parameters, followed
by trying to start the standby instance. If this step fails, then please double-check
the following items before re-running dbvctl again:
1) Review the standby database parameters you have supplied and provide valid values
unless a template is used.
2) Recreate the template to provide valid values for standby database parameters if a
template is used.
>>> Running pre-flight check for standby creation, please wait... done
>>> Total database size for LAA is 3.35GB
>>> Backing up primary database...
Backing up datafile 1... done
Backing up datafile 3... done
Backing up datafile 4... done
Backing up datafile 5... done
Backing up datafile 6... done
Backing up datafile 7... done
Backing up datafile 8... done
Backing up datafile 9... done
>>> Creating standby control file... done
>>> Transferring backup from DBVWIN2016 to DBVWIN2016DR...
Transferring C:\windows\temp\DBV_DBV1_CSD_DBF_1_3ESDNA8M_1_1.RMAN... done
Transferring C:\windows\temp\DBV_DBV1_CSD_DBF_1_3FSDNA9F_1_1.RMAN... done
Transferring C:\windows\temp\DBV_DBV1_CSD_DBF_2_3GSDNA9I_1_1.RMAN... done
Transferring C:\windows\temp\DBV_DBV1_CSD_DBF_3_3HSDNAA2_1_1.RMAN... done
Transferring C:\windows\temp\DBV_DBV1_CSD_DBF_4_3ISDNAA4_1_1.RMAN... done
Transferring C:\windows\temp\DBV_DBV1_CSD_DBF_5_3JSDNAAG_1_1.RMAN... done
Transferring C:\windows\temp\DBV_DBV1_CSD_DBF_6_3KSDNAA3_1_1.RMAN... done
Transferring C:\windows\temp\DBV_DBV1_CSD_DBF_7_3LSDNAA1_1_1.RMAN... done
Transferring C:\windows\temp\DBV_DBV1_CSD_DBF_8_3MSSAAA3_1_1.RMAN... done
Transferring C:\windows\temp\DBV_DBV1_CSD_DBF_9_3NSOKUA1_1_1.RMAN... done
>>> Restoring standby control files... done
>>> Starting standby database LAA on DBVWIN2016DR mount... done
>>> Restoring datafiles on DBVWIN2016DR...
Restoring datafile 1... done
Restoring datafile 2... done
Restoring datafile 3... done
Restoring datafile 4... done
Restoring datafile 5... done
Restoring datafile 6... done
Restoring datafile 7... done
Restoring datafile 8... done
Restoring datafile 9... done
>>> Renaming standby redo logs and tempfiles on DBVWIN2016DR... done
>>> Performing checkpoint and archiving logs... done
>>> Completing standby database creation... done
>>> Standby database created.
To complete creating standby database please run dbvctl on the primary server first,
then on the standby server, to ensure the standby database is in sync with the primary
database.
PID:3816
TRACE:3816_dbvctl_csd_DBV1_201709051722.trc |
3.4 Performing Basic Tasks
Some examples of basic tasks are outlined below. Please refer to the online documentation for more details on each command.
3.4.1 Log Gap Report
Run a log gap report from the Primary Site
| Code Block |
|---|
C:\Program Files\Dbvisit\Standby>dbvctl -d DBV1 -i ============================================================= Dbvisit Standby Database Technology (8.0.14.19191) (pid 3808) dbvctl started on DBVWIN2016: Tue Sep 5 17:53:15 2017 ============================================================= Dbvisit Standby log gap report for DBV1 thread 1 at 201709051753: ------------------------------------------------------------- Destination database on DBVWIN2016DR is at sequence: 360. Source database on DBVWIN2016 is at log sequence: 362. Source database on DBVWIN2016 is at archived log sequence: 361. Dbvisit Standby last transfer log sequence: 360. Dbvisit Standby last transfer at: 2017-09-05 17:44:59. Archive log gap for LAA: 1. Transfer log gap for LAA: 1. Standby database time lag (DAYS-HH:MI:SS): +00:08:14. ============================================================= dbvctl ended on DBVWIN2016: Tue Sep 5 17:53:17 2017 ============================================================= C:\Program Files\Dbvisit\Standby> |
Also from the GUI
3.4.2 Log Transfer
Sending the logs from the Primary via the CLI
...
Apply Logs at the Standby Site via the GUI
3.4.3 Daemon Status
Start the Daemons for automatic send/apply from the GUI Database Actions Tab.
...
https://dbvisit.atlassian.net/wiki/display/DS8QSG/Dbvisit+Standby+Scheduling
3.4.4 Starting Standby Database in Readonly Mode
From the Database Actions Tab choose the Database Icon. This allows the user to perform database actions on each node.
...
Now the Standby is back in recovery mode and the logs can be applied as normal.
3.5 Performing Graceful Switchover
The following screenshots show a Graceful Switchover from one Cloud Standby to the other using the GUI. A first pre-requisite is to ensure that the daemons started earlier are not running whilst the switchover is in progress.
3.5.1 Check the Status of the Daemons
If the daemons have been started in the previous step, they need to be stopped before performing a graceful switchover.
3.5.2 Graceful Switchover Icon GUI
3.5.3 Check Log Gap is Zero and Click Submit
3.5.4 Locate the Task on the Task Bar
3.5.5 Monitor the Activity
3.5.6 Verify the New Roles within each of the Databases
Verify the new database roles within the database
| Code Block |
|---|
C:\Program Files\Dbvisit\Standby>hostname dbvwin2016 C:\Program Files\Dbvisit\Standby> sqlplus / as sysdba SQL*Plus: Release 12.1.0.2.0 Production on Thu Jun 1 00:38:14 2017 Copyright (c) 1982, 2014, Oracle. All rights reserved. Connected to: Oracle Database 12c Standard Edition Release 12.1.0.2.0 - 64bit Production SQL> select name, database_role from v$database; NAME DATABASE_ROLE --------- ---------------- LAA PHYSICAL STANDBY C:\Program Files\Dbvisit\Standby>hostname dbvwin2016DR C:\Program Files\Dbvisit\Standby> sqlplus / as sysdba SQL*Plus: Release 12.1.0.2.0 Production on Thu Jun 1 00:38:14 2017 Copyright (c) 1982, 2014, Oracle. All rights reserved. Connected to: Oracle Database 12c Standard Edition Release 12.1.0.2.0 - 64bit Production SQL> select name, database_role from v$database; NAME DATABASE_ROLE --------- ---------------- LAA PRIMARY |
3.6 Activate the Standby Database
It is possible to activate the Standby Database and make it become the new Primary. This is also called failover to the standby database.
...
From the Central Console/GUI Choose the "Activate Standby Database Command"
3.6.1 Choose the Activate Standby Database
3.6.2 Select the Configuration
3.6.3 Monitor the Task from The Task Bar
3.6.4 Verify the Status within the Database
| Code Block |
|---|
C:\Program Files\Dbvisit\Standby>hostname dbvwin2016 C:\Program Files\Dbvisit\Standby> sqlplus / as sysdba SQL*Plus: Release 12.1.0.2.0 Production on Thu Jun 1 00:38:14 2017 Copyright (c) 1982, 2014, Oracle. All rights reserved. Connected to: Oracle Database 12c Standard Edition Release 12.1.0.2.0 - 64bit Production SQL> select name, database_role from v$database; NAME DATABASE_ROLE --------- ---------------- LAA PRIMARY |
3.6.5 Manage Configurations Tab Implications
Now the Manage Configurations Tab has the option to choose the hosts. This allows you to either accept the current configuration with the new Primary (old Standby site) or start again with the original Primary site and depends on the circumstances of the Activation.
...