7.3 Restoring a Cluster from Backup

Table of Contents Previous Next


7 Managing Backups and Recovery : 7.3 Restoring a Cluster from Backup

You can use a template or manually provide cluster properties when restoring a cluster from a backup. To restore a backup into a new cluster, navigate to the Backups tab and highlight the name of a backup. Then, click the Recover Backup icon, located in the left margin.
C:\Users\susan\AppData\Local\Temp\vmware-susan\VMwareDnD\0e3d5154\Screen Shot 2018-12-11 at 4.16.53 PM.png
If you are a Template Only user or select the Restore From Template option on the recovery method dialog, a dialog opens that allows you to use a pre-defined template for the cluster configuration; for detailed information about using a template to clone a cluster, see Section 7.3.1.
If you select Manually Restore A Backup, the dialog shown in Figure 7.4 opens.
C:\Users\susan\AppData\Local\Temp\vmware-susan\VMwareDnD\43cbcc20\Screen Shot 2018-12-11 at 4.17.55 PM.png
When the Recover Data from a Backup dialog (shown in Figure 7.4) opens:
If applicable, use the calendar selector in the Recovery Point field to specify the recovery target (the date and time that the database was in the state in which you wish the new cluster to start). The Recovery Point field is only displayed for backups that were taken with point-in-time recovery implemented; you cannot perform a point-in-time recovery with a backup unless point-in-time recovery is enabled for the cluster when the backup was taken.
Specify a name for the new cluster in the Cluster 이름 field.
Check the box next to Encryption to specify that the new cluster should reside in an encrypted cluster. Please note that you can restore a non-encrypted backup into an encrypted cluster.
Check the box next to Perform OS and Software update to instruct EDB Ark to perform a yum update whenever the cluster is provisioned. Please note: this option is disabled if the database engine is statically provisioned.
If applicable, check the box to the left of Use Private IP addresses to restore the backup into a private IP address.
If your cluster resides on an Amazon host, use the VPC drop-down listbox to select a VPC on which the cluster will reside.
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.
Use the 서버 Class drop-down listbox to specify the server class of the new cluster.
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.
Note that you can increase the IOPS value of your cluster by recovering the cluster from a snapshot into a cluster with a higher value or cloning your database into a cluster with a higher IOPS value.
Check the box next to Continuous Archiving (Point-In-Time Recovery) to indicate that the new cluster should implement point-in-time recovery. Please note that to restore into a cluster with point-in-time recovery enabled, the backup from which you are restoring must have had point-in-time recovery implemented when the backup was taken. The checkbox will not be available if point-in-time recovery was not implemented when the backup was taken.
Use the Add Rule button to open a dialog that allows you to open a port for connections from a specified CIDR formatted address.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 and continue.
Highlight a rule and click the Delete Rule button to remove a security rule.
Click the Recover button to continue, or the Cancel button to exit without starting the recovery process. A popup confirms that the cluster is being restored (see Figure 7.5); close the popup and navigate to the Clusters tab to monitor the restoration process.
C:\Users\susan\AppData\Local\Temp\vmware-susan\VMwareDnD\9f3de216\Screen Shot 2018-12-11 at 4.23.10 PM.png
Please note: when restoring a cluster from backup, you may need to modify parameters in the postgresql.conf file on the restored cluster to reflect the available memory of the new instance if the server class has changed from the original setting (the default value in the 서버 Class field). After modifying the server configuration, restart the server for the changes to take effect.

7 Managing Backups and Recovery : 7.3 Restoring a Cluster from Backup

Table of Contents Previous Next