Amazon AWS EC2 -> Amazon AWS EC2
- 1 1. Introduction
- 2 2. Initial Setup and Configuration
- 3 3. Install, Configure and Run the Standby software
1. Introduction
The purpose of this Deployment guide is to demonstrate the way in which Dbvisit Standby 8.0 software can be installed on an Amazon AWS EC2 instance. In this guide, we focus on both the Primary and Standby databases being in AWS. In another document, we focus on 'On-Premise Primary' to Standby in AWS. A link that document can be found here
The setup will be from Single Instance Primary Database to Single Instance Standby Database with Datafiles stored on standard filesystems on a Linux Platform. However, the options for configuring Dbvisit Standby are in no way limited to this.
2. Initial Setup and Configuration
2.1 Provisioning the Severs
The primary server dbvaws01 has been provisioned in the equivalent section of the guide "On-Premise Primary" to AWS EC2. This documentation will reference the same server. This section will focus on the provisioning of the 2nd server: dbvaws02 which will be launched from the snapshot taken of dbvaws01 after the Oracle environment had been prepared and the Dbvisit Standby binaries had been copied to the server. The AMI ID is ami-cdcb5cb5
From the AMI menu select this AMI and click 'Launch'
For Step 2 "Choose an Instance Type": The allows you to select from a range of Amazon Instance Types. The "learn more" link directs you to more information about the instance types and how they might suit your computing needs. For the purpose of this guide only, we have chosen t2.small.
Step 3: Configure the Instance Details. Here we choose the defaults,
Step 4 "Add Storage". We also accept the defaults here as a 30GB disk is more than enough for the demo purposes.
Throughout this guide, no mention is made to the licensing implications of running Oracle software on Amazon AWS. The setup we have here has been built for demonstration purposes/ Further information regarding Oracle Licenses in the cloud can be found here. Also Licensing Oracle Software in the Cloud Computing Environment.
Step 5 "Add Tags". Create a Tag with Key = "Name" and Value = "dbvaws02"
Step 6 "Configure Security Group". Here, we've chosen an existing security group with ports 22 (SSH), 4433 (dbvserver), 7890 (dbvnet) and 7891 (dbvagent) enabled within the INBOUND security rules.
The final step is to review and Launch the new instance making sure that if the 'Choose an existing key pair' option is selected that the .pem file is accessible by yourself.
I have access to the dbvAWS.pem file so I clicked the tick box and then proceeded with "Launch Instance"
Within a few minutes, the new instance is up and running.
A test connection can then be made to the new host using the dbvAWS key pair.
Lorraines-MBP:Downloads landers$ ssh -i dbvAWS.pem ec2-user@34.217.129.95
Last login: Thu Mar 8 18:29:09 2018 from 222.154.244.15
[ec2-user@ip-172-31-30-113 ~]$
Summary Details of the 2 VMs are as follows :
Primary Server Details | Standby Server Details |
|---|---|
Name: dbvaws01 Hosted: Amazon AWS EC2 vCPUs : 1 OS: Oracle Linux EL7 Memory : 2G Storage : 30G Version: 11.2.0.4 Edition: Enterprise Edition Database : XE Dbvisit Base: /usr/dbvisit/standby Standby Version: 8.0.20 | Name: dbvaws02 Hosted: Amazon AWS EC2 vCPUs : 1 OS: Oracle Linux EL7 Memory : 2G Storage : 30G Version: 11.2.0.4 Edition: Enterprise Edition Database : XE Dbvisit Base: /usr/dbvisit/standby Standby Version: 8.0.20 |
2.2 Preparing the Servers: dbvaws01 and dbvaws02
The binaries were copied and the /usr/dbvisit directory was in place as part of the image, so we can proceed directly to the installation. The server dbvaws01 will be reconfigured in this guide to be a primary server and server dbvaws02 will be configured to be the standby server with the GUI binaries installed.
3. Install, Configure and Run the Standby software
3.1 Installing and Configuring the Software
3.1.1 dbvaws01 (hostname : ip-172-31-13-235)
This server, dbvaws01, will be the primary server so install the core components. Here is the link to the full installation guide. It is summarized below. Navigate to where the unpacked files are
[oracle@ip-172-31-13-235 tmp]$ cd dbvisit
[oracle@ip-172-31-13-235 dbvisit]$ ls -lrt
total 20
drwxr-x---. 10 oracle oinstall 4096 Mar 7 19:41 standby
drwxr-x---. 5 oracle oinstall 4096 Mar 7 19:41 dbvserver
drwxr-x---. 5 oracle oinstall 4096 Mar 7 19:41 dbvnet
drwxr-x---. 6 oracle oinstall 4096 Mar 7 19:41 dbvagent
drwxr-xr-x. 2 oracle oinstall 4096 Mar 7 19:41 installer
[oracle@ip-172-31-13-235 dbvisit]$ cd installer
[oracle@ip-172-31-13-235 installer]$ ls -lrt
total 2772
-rwxr-x---. 1 oracle oinstall 2835196 Mar 7 19:41 install-dbvisit
[oracle@ip-172-31-13-235 installer]$ ./install-dbvisitAccept the defaults for the dbvnet configuration and choose ip-172-31-30-113 as the remote host.
Dbvnet Summary Configuration.
Dbvagent Summary configuration on the Standby Server
The summary information for this node :
The processes can be started on dbvaws01 (2 small batch scripts dbv_start/dbv_stop have been copied to the /home/oracle directory to quickly stop/start the processes)
[oracle@ip-172-31-13-235 ~]$ cat dbv_start
#!/bin/bash
cd /usr/dbvisit/dbvnet
./dbvnet -d start
cd ../dbvagent
./dbvagent -d start
ps -ef|grep -i dbv
[oracle@ip-172-31-13-235 ~]$ ./dbv_start
dbvnet process started with pid: 11548
dbvagent process started with pid: 11550
oracle 11546 11242 0 19:29 pts/1 00:00:00 /bin/bash ./dbv_start
oracle 11548 1 0 19:29 ? 00:00:00 ./dbvnet -d start
oracle 11550 1 0 19:29 pts/1 00:00:00 ./dbvagent -d start
oracle 11552 11546 0 19:29 pts/1 00:00:00 grep -i dbv3.1.2 dbvaws02 (hostname : ip-172-31-30-113)
This server will be configured to be the Standby Server. As both of these servers are launched within the same VPC and Security Group. The hostnames ip-172-31-30-113 and ip-172-31-13-235 should be resolvable from each other without the need to update the local host's files.
With the processes started on the primary host, we can test this with a quick telnet on one of the dbvisit ports.
[oracle@ip-172-31-30-113 ~]$ telnet ip-172-31-13-235 7891
Trying 172.31.13.235...
Connected to ip-172-31-13-235.
Escape character is '^]'.