SB Connectivity Veeam - S3 Capacity Tier

Installation and Connectors Installation and electrical connection as well as network connection are to be done as described in the manual Installation

Network Adjustments The network settings are to be adjusted as described in the manual Installation

The settings of this volume differ from settings for a Backup to disk repository which uses Large File Optimization and probably no Audit.

Create a new Volume of type 'SNAS' with a parity of 3 or 2

Compression is recommended for the capacity tier

Disable Large File Optimization

For higher redundancy a parity level of 3 is recommended

In your volume navigate to the Shares section

Choose "Add S3 Share"

Enter a Share Name

Enter credentials for accessing the S3 layer

The Port will be automatically increased for each new S3 instance

Write down the Access Point URL.

Right-Click on the S3 Share and choose "Manage Buckets"

Create a new Bucket for use with Veeam

Since S3 communicates via HTTPs, certificates are being used. In order to update the SSL certificate of the Silent Brick System proceed as follows:

Navigate to Settings -> Network

Select "Edit" for "Custom SSL Certificate" and upload your own certificates.

Certificates may be generated manually or via services like Lets Encrypt

Supported certificate types are SSL certificates including the private key and the signing certificate authority.

Certificates with passphrase are not supported.

Add a new repository of type 'Object Storage' - 'S3 Compatible'

Enter the Service Point URL previously noted

Enter the credentials as defined for the S3 Share

Select the previously created bucket

Add a folder to the bucket

Edit your existing Scale-Out Backup repository and add the new Object Store as capacity tier.

You Object Store on a Brick is now being used in your Veeam SOBR.

Retention for data in the capacity tier depends on the Backup Job Retention

Choose "Copy" to create instant redundancy of your data

Choose "Move" to free up disk space in the performance tier by moving data to the capacity tier after time.

Both is combinable

If you want to archive data in the capacity tier use "Move" in the SOBR and the GFS setting along with a proper retention in your backup job configuration.

Per Default VEEAM write quite small objects which can influence the performance especially on spinning disks. Therefor increasing the Object Size can result in a higher Performance.

Increasing the Object size will result in bigger incremental backups

To make this option visible, create the UIShowLegacyBlockSize (DWORD, 1) registry value under the 'HKLM\SOFTWARE\Veeam\Veeam Backup and Replication' key on the backup server. Keep in mind that this option significantly increases incremental backups size and requires an active full backup to be activated.

Modify your Backup Job to use Extra Large Object Sizes

Run an active full backup

Per Default VEEAM write quite small objects which can influence the performance especially on spinning disks. Therefor increasing the Object Size can result in a higher Performance.

Increasing the Object size will result in bigger incremental backups

Modify your Backup Job to use Local Target ( Large Blocks)

Run an active full backup