Set up backups for Percona Server for MongoDB

Set up backups for your database infrastructure in your own Kubernetes cluster

읽는 시간 3분

최근 업데이트: 한 달 전

If you have deployed Self-Hosted Deployment in your own cluster through the Bring Your Own Elastic Kubernetes Service (BYO EKS) mode, complete the procedure in this section to set up backups for your database infrastructure using Percona Server for MongoDB (PSMDB).

For backups, PSMDB uses EKS Pod Identity to access the AWS S3 bucket. The procedure sets up these components:

The necessary AWS resources
EKS Pod Identity

참고

This setup procedure is only for the BYO EKS mode. The process for full deployment in a new Kubernetes cluster automatically creates this configuration through the Terraform code.

Requirements

Before you begin, ensure that this setup is complete:

You have performed this installation:
- You have deployed Self-Hosted Deployment in the BYO EKS mode.
- Your installed Unity products, such as Asset Manager, run on your Kubernetes cluster.
- During deployment, you have enabled PSMDB to monitor your database infrastructure, that is, you have set the
```
enable_percona_mongo
```
  setting to true in the Terraform variables file.
These resources are available:
- An EKS cluster with the necessary permissions to create the Identity and Access Management (IAM) roles and policies
- An Amazon S3 bucket for backups

1. Configure EKS Pod Identity to access the S3 bucket

To configure EKS Pod Identity to access the S3 bucket, complete these steps:

Complete the configuration procedure in the Percona Operator for MongoDB documentation.
Authorize the Kubernetes service account
```
psmdb-operator
```
to access the Asset Manager namespace.

참고

The documentation mentions IAM roles for service accounts (IRSA), which is the old implementation of EKS Pod Identity. However, EKS Pod Identity is now supported and is the implementation that Self-Hosted Deployment uses.

2. Test the backup configuration

After you have set up the IAM policy, verify that PSMDB can access the S3 bucket for backups:

To create a test backup operation, apply this YAML file:


apiVersion: psmdb.percona.com/v1kind: PerconaServerMongoDBBackupmetadata:  finalizers:  - percona.com/delete-backup  name: test-psmdb-backupspec:  clusterName: psmdb-db  storageName: s3-primary  type: logical

Check the custom resource PerconaServerMongoDBBackup to ensure that the backup is created. To get the status of the backup, run this command:
```
kubectl get perconaservermongodbbackup test-psmdb-backup -n psmdb-db
```
The status must be ready.
Verify that there are no access errors. To check the PSMDB pod logs, run this command:
```
kubectl logs psmdb-db-rs0-0 -c backup-client
```
Verify that the backup is stored in the S3 bucket.

3. Verify backup storage

To confirm that backups are working correctly, complete these steps:

Check the backup status using the kubectl command that you used to test the backup configuration.
Go to your S3 bucket and verify that backup files are being created.

Verify that the backup process works from end to end. To test restoring from a backup, apply this .yaml file:


apiVersion: psmdb.percona.com/v1kind: PerconaServerMongoDBRestoremetadata:  name: test-psmdb-restorespec:  clusterName: psmdb-db  backupName: test-psmdb-backup

To ensure that the backup copy is restored, check the custom resource
```
PerconaServerMongoDBRestore
```
. To get the restore status, run this command:
```
kubectl get perconaservermongodbrestore test-psmdb-restore -n psmdb-db
```

기술 자료

Development

User Acquisition

Monetization

산업 분야

기술 자료

Development

User Acquisition

Monetization

산업 분야

Self-Hosted Deployment

Amazon Web Services

Microsoft Azure

On premises

vpctl