mirror of
https://github.com/pgsty/minio.git
synced 2026-08-09 15:53:28 +03:00
docs: migrate Silo resources to unified portal
Co-authored-by: ChatGPT <noreply@openai.com> Co-authored-by: Claude <noreply@anthropic.com>
This commit is contained in:
@@ -5,10 +5,10 @@ When using Veeam Backup and Replication, you can use S3 compatible object storag
|
||||
## Prerequisites
|
||||
|
||||
- One or both of Veeam Backup and Replication with support for S3 compatible object store (e.g. 9.5.4) and Veeam Backup for Office365 (VBO)
|
||||
- MinIO object storage set up per <https://silo.pigsty.io/index.html>
|
||||
- Veeam requires TLS connections to the object storage. This can be configured per <https://silo.pigsty.io/operations/network-encryption.html>
|
||||
- MinIO object storage set up per <https://silo.pgsty.com/docs/>
|
||||
- Veeam requires TLS connections to the object storage. This can be configured per <https://silo.pgsty.com/operations/network-encryption/>
|
||||
- The S3 bucket, Access Key and Secret Key have to be created before and outside of Veeam.
|
||||
- Configure the minio client for the Veeam MinIO endpoint - <https://silo.pigsty.io/operations/deployments/baremetal-deploy-minio-on-redhat-linux.html>
|
||||
- Configure the minio client for the Veeam MinIO endpoint - <https://silo.pgsty.com/operations/deployments/baremetal-deploy-minio-on-redhat-linux/>
|
||||
|
||||
## Setting up an S3 compatible object store for Veeam Backup and Replication
|
||||
|
||||
@@ -26,7 +26,7 @@ mc mb myminio/veeambackup
|
||||
mc mb -l myminio/veeambackup
|
||||
```
|
||||
|
||||
> Object locking requires erasure coding enabled on the minio server. For more information see <https://silo.pigsty.io/operations/concepts/erasure-coding.html>.
|
||||
> Object locking requires erasure coding enabled on the minio server. For more information see <https://silo.pgsty.com/operations/concepts/erasure-coding/>.
|
||||
|
||||
### Add MinIO as an object store for Veeam
|
||||
|
||||
|
||||
Reference in New Issue
Block a user