When you add a cluster, a default namespace group (subclient) is automatically created. You can create more namespace groups for data that has different backup requirements.
Before You Begin
-
To configure a YugabyteDB instance, make the following entries while adding a YugabyteDB cluster:
-
Host: Load balancer full name, a public IP address, or a YugabyteDB Anywhere (YBA) host.
-
API token: API token of the user with the following privileges:
-
Admin
-
SuperAdmin
-
BackupAdmin
You can find the API token by logging on to the YugabyteDB Anywhere console.
-
-
Storage configuration : The YugabyteDB storage configuration which will be used for backups and restores.
-
-
Network configuration requirement for YugabyteDB deployed on AWS EC2 or Azure Blob Storage:
If the access node is outside of the YugabyteDB virtual private cloud (VPC), then complete the following steps:
-
Create a peering connection between the access node VPC and the YugabyteDB VPC.
-
For YugabyteDB VPC security group, the port 443 must be open.
-
Both access node and the YugabyteDB Anywhere host must be able to access the S3 bucket or Azure Blob Storage.
-
-
The following keys and tokens for authentication:
-
Amazon S3: IAM or access key and secret key
-
Azure Blob Storage: SAS token
-
Procedure
-
From the Command Center navigation pane, go to Protect > Big data.
The Big data page appears.
-
Click YugabyteDB.
The YugabyteDB page appears.
-
Click Add cluster.
The Configure YugabyteDB Cluster page appears. For further steps, see Configure YugabyteDB Cluster (Step 4 onwards).