1. Introduction
The section of the user guide explains installing Dbvisit Standby MP on AWS EC2 instances. In this guide, we focus on both primary and standby on the AWS. The setup will be a single instance primary database and a single instance standby database on Linux Platform. The data files are stored on a standard filesystem. This is just an example, and it does not limit the possibility of storing the data files on an ASM, using the Windows operating system, or using any supported Oracle platforms that are available on AWS.
2. Initial Setup and Configuration
2.1 Provisioning servers
We will be provisioning two servers, both with the same Linux version and release. We are using community AMIs with Linux 7.9. Click on “Launch Instance with AMI” to move to next step
Below image shows the Instance type choses (t2.medium) and also the key pair to login. We are using the existing key pair to connect to these machines (SydneySC), but a new key can be created by clicking on “Create new key pair”
The next important step is to configure network and firewall which we will see details in the next section.
Adding additional storage for Oracle installation and database files. In this example we have added just one EBS volume with 75Gig. The Root volume is already added as part of the AMI but you can choose to increase the size.
2.2 Network and Firewall
The details of the VPC created is shown below.
Security group for Inbound and Outbound rules. ( 1 ) for Nats Port for agentmanager (5533) communication and also for PostgreSQL cluster ( 2 ) Webserver port for GUI ( 3 ) Dbvnet communication port range , the main port required for this is 7890. ( 4 ) The port for ssh and also for RDP incase of windows. A specific IAM profile is also created that has required permissions and policies assigned to it.
Once this is completed and added. Click on “Launch Instance” to start the instance. There are also options to have reserved public IP to ensure that the IPAddresses do not change after every server restart. These can be used for machines that are created for permanent production use. For this use case we have not enabled them as these machines are used only for temporary purposes. The machine name has also been set to desired one using the tags.
