Table of Contents Previous Next


5 Creating a Server Cluster : 5.1 Manually Creating a Cluster

Before you can connect to Postgres from a client application, you must create a server cluster. Use the Launch DB Instance button (located in the upper left panel of the Dashboard Tab) or click the Add Server button on the Clusters tab to open the Create a New Server Cluster dialog, as shown in Figure 5.2.
C:\Users\susan\Desktop\new_cluster.png
Figure 5.2 - Specify information about the new cluster on the Step 1 tab.
Use fields on the Create a New Server Cluster dialog to specify information about the new cluster:
Please Note: EDB Ark uses the name specified in the Cluster Name field to identify the cluster when performing management functions. The cluster name is also part of the Instance Name on the OpenStack console; you must not modify the name in the OpenStack management console. Changing the cluster name in the OpenStack console can break key EDB Ark features (i.e. failover).
Use the drop-down listbox in the Engine Version field to select the version of the Postgres engine that you wish to use.
Use the drop-down listbox in the Server Class field to specify the size of each cluster node. The server class determines the size and type (compute power and RAM) of each node within the cluster.
You can adjust the amount of storage used by the cluster, or number of replicas in the cluster as your resource demands change. For example, you can start with a m1.small instance, and later, easily upgrade to a more capable c1.medium instance as your performance requirements dictate.
If your cluster resides on an OpenStack host, use the drop-down listbox in the Virtual Network field to specify the identity of the network in which the cluster should reside.
If your cluster resides on an Amazon host, you can check the box to the left of Use Private IP addresses to display addresses that are in your private network in the VPC field.
If your cluster resides on an Amazon host, use the drop-down listbox in the VPC field to specify the identity of the network in which the cluster should reside.
If your cluster resides on an OpenStack host, use the drop-down listbox in the Floating IP Pool field to select the address pool in which the cluster should reside.
Use the drop-down listbox in the Number of nodes field to specify the number of server nodes that you wish to create. The name specified in the Cluster Name field will apply to the master node; each additional node will act as a replication server for the master node.
Use the Storage GB field to specify the initial size of the data space (in Gigabytes).
Check the box next to Encrypted to indicate that the cluster should be encrypted. EDB Ark uses the aes-xts-plain (512-bit) cipher suite to provide an encryption environment that is both secure and transparent to connecting clients. When encryption is enabled, everything residing on the cluster is encrypted except for the root filesystem.
If your cluster resides on an AWS host, check the box next to EBS Optimized to specify that your cluster should use an Amazon EBS-optimized instance and provisioned IOPS to guarantee a level of I/O performance.
The IOPS field is enabled for those clusters that will reside on an EBS-optimized instance. If applicable, use the field to specify the level of I/O performance that will be maintained for the cluster by automatic scaling. The maximum value is 30 times the size of your cluster; for example, if you have a 4 Gigabyte cluster, you can specify a maximum value of 120.
Check the box next to Perform OS and Software ? update to specify that a software update should be performed whenever the cluster is provisioned. Please note: this option is disabled if the cluster uses a statically provisioned server.
Use the Notification Email field to provide the email address that will receive notices about changes to the cluster status.
If applicable on your host system, click the Next button to continue to the Step 2 tab (shown in Figure 5.3).
C:\Users\susan\AppData\Local\Temp\vmware-susan\VMwareDnD\e996229e\Screen Shot 2018-03-20 at 9.39.08 AM.png
Figure 5.3 - The Step 2 tab.
Use the fields on the Step 2 tab to specify additional database information:
Use the AVAILABILITY ZONE drop-down listbox to the right of each node to select the availability zone in which the node will reside.
Use the SUBNET drop-down listbox to the right of each node to select the subnet that the node will use. Please note that if you manually specify a subnet, you must select a subnet that resides on your private network.
If applicable on your host system, click the Next button to continue to the Step 3 tab (shown in Figure 5.4).
C:\Users\susan\AppData\Local\Temp\vmware-susan\VMwareDnD\f915135a\Screen Shot 2018-03-20 at 9.40.40 AM.png
Figure 5.4 - Specify backup information on the Step 3 tab.
Use the fields on the Step 3 tab to specify additional database information:
Use the # of automatic backups to retain field to specify the number of server backups stored. When the specified number of server backups is reached, EDB Ark will delete the oldest backup to make room for a new backup.
When point-in-time recovery (PITR) is enabled, the value specified in the # of automatic backups to retain setting determines the duration of the PITR backup window. For example, if you specify a value of 7, the PITR backup window will be 7 calendar days long.
Use the Backup Window field to specify a time that it is convenient to backup the server (you may wish to schedule backups to occur when the CPU load is the lightest).
Check the box next to Continuous Archiving (Point-in-Time Recovery) to enable point-in-time recovery for the cluster. When enabled, a base backup is automatically performed that can to be used to restore to a specific point in time. All subsequent automatic scheduled backups will also support point-in-time recovery. Note that if you deselect this option, the cluster (and subsequent automatic backups) will be re-configured to not include support for point-in-time recovery.
Use the Previous button or select a tab to return to a tab to review or update information; when you have completed the Create a New Server dialog, click Launch to create the database cluster.
A popup dialog confirms that EDB Ark is creating a new cluster (see Figure 5.5); click the X in the upper-right corner of the popup to close the popup.
Screen shot 2012-01-13 at 6
Figure 5.5 - A popup confirms that the new cluster is being created.
Navigate to the Clusters tab of the Ark console to monitor the creation of the cluster.

5 Creating a Server Cluster : 5.1 Manually Creating a Cluster

Table of Contents Previous Next