You can customize your backup and restore settings.

MinIO gateway mode

The backup and restore operator and MinIO are deployed with the default settings. The MinIO can be deployed as a statefulset or it can be deployed as a proxy (gateway) to the external datastore. The default behavior is to deploy the MinIO as the statefulset.
Note: When the MinIO is deployed as the statefulset the backup are stored in MinIO Persistent Volumes (PV), and the backups are not externalized. Which means when the Kubernetes cluster or the MinIO PV is deleted the backups will be erased. To avoid this, you must deploy MinIO as a gateway.
Procedure to deploy MinIO as gateway, using Deployment Container:
  1. To deploy MinIO as a gateway, you can override the Helm MinIO chart by adding:
    --set appSpecs.minio.helmOverrides.minio.gateway.enabled=true --set appSpecs.minio.helmOverrides.minio.gateway.auth.s3.accessKey=${AWS_ACCESS_KEY_ID} --set appSpecs.minio.helmOverrides.minio.gateway.auth.s3.secretKey=${AWS_SECRET_ACCESS_KEY}
    

    The PRODUCT_SPECIFIC_HELM_OVERRIDES is available in deploy.settings file.

    Note: You can add MinIO and custom bucket configuration in a single command.
  2. Export the access keys using command:
    export AWS_ACCESS_KEY_ID=<access id>
    export AWS_SECRET_ACCESS_KEY=<access key>
  3. Set the DEPLOYMENT_ACTION to deploy-all in the deploy.settings file.
  4. Run the tcx_app_deployment.sh script in the Deployment Container, which triggers the Helm upgrade and restarts the br-operator pod.
Procedure to deploy MinIO as gateway, using VMware Telco Cloud Automation:
  1. For deploying MinIO as a gateway, see Steps to Reconfigure VMware Telco Cloud Service Assurance through VMware Telco Cloud Automation UI.
    Note: Ensure that you update only the parameters specified in step 2.
  2. Update the values for gateway.enabled=true, accesskey, secretkey in the values.yaml file as shown in the following screenshot:

    Note: The backups taken on the previous statefulset MinIO are not available in the updated MinIO as a gateway.

Changing the backup bucket

The backup and restore operator is deployed with a default bucket vmware-tcsa-backup.

Procedure to override the bucket name, using Deployment Container:
  1. To change the bucket you can override the br-operator helm chart by adding:
    --set appSpecs.brOperator.helmOverrides.minio.backupBucketName=<your bucket>

    The PRODUCT_SPECIFIC_HELM_OVERRIDES is available in deploy.settings file.

  2. Set the DEPLOYMENT_ACTION to deploy-all in the deploy.settings file and run the tcx_app_deployment script, which triggers the Helm upgrade and restarts the MinIO.
  3. Manually start the br operator by using the following command:
    kubectl delete pod -l app.kubernetes.io/name=br-operator
Procedure to override the bucket name, using VMware Telco Cloud Automation:
  1. To override the bucket name in MinIO gateway mode, see Steps to Reconfigure VMware Telco Cloud Service Assurance through VMware Telco Cloud Automation UI.
    Note: Ensure that you update only the parameters specified in step 2.
  2. Update the bucket name in the values.yaml file as shown in the following screenshot:

  3. Manually start the br operator by using the following command:
    kubectl delete pod -l app.kubernetes.io/name=br-operator
Note: The backups taken on the previous bucket, will not be available in the new bucket.