Configuring S3 backup settings for fresh install of the Management subsystem
You can configure backups for your management subsystem in your Kubernetes environment.
Before you begin
If you have a two data center disaster recovery deployment, before you
configure S3 backup settings you must first disable 2DCDR on both sites. Follow
these steps:
- Remove the
multiSiteHA
section from thespec
section of the management CRs on both data centers. Take note of which data center is the active and which is the warm-standby. Keep a copy of themultiSiteHA
sections that you remove. - Configure your S3 backup settings. You must specify different backup locations for each data center, see Backup and restore requirements for a two data center deployment.
- Add the
multiSiteHA
sections back to the management CRs in both data centers, ensuring that your original active is set to be the active again.
About this task
If you haven't already, configure your management subsystem custom
resource
with the databaseBackup
subsection.
Note: S3Provider
supports custom
S3 solutions in 10.0.2.0 and
greater. The support includes new backup parameters backupCerts
and
backups3URIStyle
.
Important: For S3 backups of the management subsystem, do not use
retention features provided by Cloud-based S3 storage providers. Use of such features can result in
periodic deletion of archived backups, which can cause backup corruptions that can cause database
restores to fail.
Warning:
When configuring a new management subsystem for S3 backup, the content of the S3 bucket path must
be empty. If you want to configure a management subsystem to use the content of an S3 bucket path
already used by another management subsystem, you have two options:
- Shutdown the postgres database on the existing management subsystem that points to the S3 bucket path before you start the new management subsystem.
- In a disaster recovery scenario where you want to restore from the backup of an existing installation: Create a new S3 path and use S3 tools to copy the backup content from the existing management subsystem S3 bucket path, to the new bucket path.