Setting Up Swarm as an Object Store to Veeam as a Backup Repository

Follow the below steps to add Swarm as an object store to Veeam as a backup repository:

1. Navigate to the Backup Repository tab and click on Add Repository. The alternative is to right-click on Backup Repositories in the Backup Infrastructure panel.

   Open

   

    

2. Select Object storage, then select S3 Compatible.
   
   

   Open

   

    

3. Enter a Name. This is the name that is displayed as a Capacity Extent option in other Veeam menus.

    

4. Uncheck the Limit concurrent tasks option and click Next.

5. Fill in the Service point and prefix it with "https://“. The “Service point” is the Swarm Domain endpoint specified when configuring Swarm. This example uses https://veeam-cert.cloud.datacore.com.

6. The Region is not utilized, and you can leave the default setting “us-east-1”.

7. Click Add to enter in the Access/Secret key credentials corresponding to the token generated for the Swarm Domain being used as the target, then click OK to continue. The Access key is the Token ID.
   
   

   
   
   

    

8. Click Next to specify the bucket. If Veeam can connect to your Swarm Domain successfully, click on Browse to select the bucket you created earlier to use as the target.

    

9. Click on New Folder to define the folder prefix Veeam adds to your backups. Any prefix you define is fine. Veeam creates a folder using this prefix to segregate Veeam backup from other data that may also be in that bucket.
   
   

    

10. For Veeam backup with immutability, select the number of days you want to make backups immutable for. Click Apply to proceed. Veeam applies a minimum of 10-days backup immutability to protect dependent incremental even if you choose fewer days.
    
    

     

11. On the Summary, click Finish to complete the backup repository creation. If everything works properly, a summary screen displays and the Swarm-based Capacity Tier is now available.
    
    

Now, the list of backup repositories includes the Swarm object storage.

By utilizing the process above you can create multiple buckets with various erasure coding policies and S3 tokens valid for different periods of time.