5.1 Manually Creating a Cluster

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\AppData\Local\Temp\vmware-susan\VMwareDnD\852fcc95\Screen Shot 2018-12-11 at 2.19.20 PM.png
Figure 5.2 - Specify information about the new cluster on the Step 1 tab.
Use fields on the Create a New 서버 Cluster dialog to specify information about the new cluster:
Please Note: EDB Ark uses the name specified in the Cluster 이름 field to identify the cluster when performing management functions.
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 서버 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 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.
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 이름 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 instruct EDB Ark to perform a yum update whenever the cluster is provisioned; this option is disabled for clusters that use statically provisioned servers. The yum update command updates all of the outdated packages that reside on the cluster. The update will occur when a cluster is scaled up, scaled down, or during a failover.
When you check the box next to Perform OS and Software update ?, EDB Ark will warn you that enabling this functionality can significantly slow down cluster operations. Updating packages may slow down cluster maintenance operations; an update can easily take 10 minutes or more, and will initiate a reboot of the node. This setting is persistent; if you enable software updates for a cluster, you cannot directly disable software updates for that cluster at a later time.
Use the Notification 이메일 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\d05b78b7\Screen Shot 2018-12-11 at 2.38.52 PM.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.
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\8fa4d3b0\Screen Shot 2018-12-11 at 2.40.35 PM.png
Use the fields on the Step 3 tab to define security rules that allow access to the cluster. By default, the load balancer port is open to any IP address for client connections; you may choose to delete the rule, and specify a more restrictive IP range.
To delete a rule from the list, highlight the entry and click the Delete Rule button; you will be prompted to confirm that you wish to delete the entry before the server removes the rule.
Click the Add Rule button to open the Add Rule dialog (see Figure 5.5) and provide access to a port.
C:\Users\susan\AppData\Local\Temp\vmware-susan\VMwareDnD\c25a4e5c\Screen Shot 2018-12-11 at 2.42.23 PM.png
On the Add Rule dialog:
Use the Port drop-down listbox to select the port that can be accessed from the specified CIDR. A non-administrative user can allow access to ports:
9999 - for client connections and load balancing.
5432 or 5444 - the cluster specific database listener port.
An administrative user can use the Add Rule dialog to add a rule that allows SSH access to Port 22.
Use the CIDR field to specify the address (or address range) that will be allowed access to the server through the selected port.
When you're finished, click Apply to create the security rule.
Then, click Next to continue to the Step 4 tab (see Figure 5.6).
C:\Users\susan\AppData\Local\Temp\vmware-susan\VMwareDnD\d0db7996\Screen Shot 2018-12-11 at 2.43.09 PM.png
Figure 5.6 - Specify backup information on the Step 4명 tab.
Use the fields on the Step 4 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.7); click the X in the upper-right corner of the popup to close the popup.
C:\Users\susan\AppData\Local\Temp\vmware-susan\VMwareDnD\9fade36a\Screen Shot 2018-12-11 at 2.44.08 PM.png
Figure 5.7 - 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