To demonstrate the snapshot capabilities and cover the use cases, a test setup is configured as shown in the following figure:
Figure 18. Test setup for snapshot/restore use cases using cloned YugabyteDB cluster
This test setup shows seven VM instances, each configured with minimum 4 CPU and 16 GB memory.
- One instance for the client machine to log in to the database and run operations.
- Three instances of source database nodes each configured with
- Operating system root (/) volume - 50 GB
- PowerFlex volume for YugabyteDB software mounted on /opt - 30 GB
- PowerFlex volume for YugabyteDB database mounted on /ydb - 1 TB
- Operating system: RHEL 8.x
- The remaining three instances are the cloned database nodes.
- In this test environment, the IP addresses, and hostnames for the above VMs are configured as mentioned in the following table.
Table 6. Test environment - node IP and hostname details
Machine Name | IP address | Hostname |
Source database node VM-1 | 172.16.105.101 | ydb-node1.ydb.com |
Source database node VM-2 | 172.16.105.102 | ydb-node2.ydb.com |
Source database node VM-3 | 172.16.105.103 | ydb-node3.ydb.com |
Cloned database node VM-1 | 172.16.105.104 | ydb-node1-clone.ydb.com |
Cloned database node VM-2 | 172.16.105.105 | ydb-node2-clone.ydb.com |
Cloned database node VM-3 | 172.16.105.106 | ydb-node3-clone.ydb.com |
Client VM-1 | 172.16.105.111 | ydb-client1.ydb.com |
- The IP addresses and hostnames are recorded in the DNS server. For example, ydb-node1 to ydb-node3 represent the 3-node production YugabyteDB cluster, while the ydb-node1-clone to ydb-node3-clone represent the hosts to which a PowerFlex snapshot of the production YugabyteDB database is mounted and started as a database copy. The /etc/hosts file in each of the database nodes should be updated with the appropriate hostname and IP address for its purpose (for example, ydb-node1 for production cluster node 1).