- Is there a way to immediately deploy the cluster so that backups are made in s3 and archives are saved in s3. Those in the local storage did not get anything so that?
I want to do it as described by crunchy here Crunchy Data PostgreSQL Operator Documentation
pgo create cluster mycluster --pgbackrest-storage-type=s3 -n pgouser1
Now all archives for the cluster will be pushed to S3 storage only, and local storage will not be utilized for storing archives (nor can local storage be utilized for backups and restores).
The question is how to achieve this?
We set up backups to s3, but what is done by jobs is done sequentially locally and after to s3, and the archives are similarly saved locally and in s3
When you make a switchover by patronictl, a backup is made, but it is only done in the local repository and not in c3, is it somehow configured?