The minimum version is Veeam 11a CP4 (11.0.1.126120220302,) which brings an important special fix when using Object Lock.
In May 2024, we started to introduce regions with contract-owned buckets, providing enhanced performance and resilience. Contract-owned buckets are available in the eu-central-3 region or in the us-central-1 region. This new bucket type creates an easier opportunity for user management, since the bucket list is visible for all users of the contract, and the contract owner or administrators can assign permissions to view bucket contents. For more information, see Bucket Types and Endpoints.
This setting is available during the addition of the new Object Storage repository. For more information, see Configure repository details in Create Object Storage as an object repository in Veeam.
You can also update the concurrent tasks limit for an existing Object Storage repository by following these steps:
Go to the Backup Infrastructure tab.
Click Backup Repositories.
Right-click on your Object Storage repository and choose Properties.
Select the checkbox Limit concurrent tasks to and set the value as follows:
Up to 10—for eu-south-2 region.
Up to 20—for all other regions.
Veeam Backup & Replication allows you to configure block sizes for each backup job, which can significantly impact deduplication efficiency and incremental backup size. By default, blocks are compressed, typically achieving a compression ratio of about 50%.
Smaller blocks can enhance deduplication; they increase the number of calls to the object storage, potentially affecting performance.
Larger blocks reduce the number of storage calls and can increase throughput to and from IONOS Object Storage, improving overall backup performance.
For optimal performance with IONOS Object Storage, we recommend using 8 MB blocks. These blocks are unavailable in the interface by default and must be enabled via a registry key by following these steps:
1. Open the Registry Editor.
2. Navigate to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication.
3. Add a new DWORD (32-bit) value named UIShowLegacyBlockSize.
4. Set the value of UIShowLegacyBlockSize to 1.
Result: The 8 MB blocks are now available in the Veeam interface.
To change the storage optimization setting, follow these steps:
1. Click the Backup section under Jobs.
2. Select the required backup job, right-click on it, and choose Edit in the menu.
3. Click Storage > Advanced and change the tab to Storage.
4. In the Storage optimization drop-down list, choose 8 MB marked as "not recommended”. Disregard this mark as it is the correct choice. This option must be there if you modify the registry setting as described in the previous section. Do not use a block size less than 4 MB.
5. Click Save as default at the bottom of the Advanced Settings screen.
Result: The new storage configuration is saved as the default setting. This will ensure the settings are automatically used for any new backup jobs created.
The immutability retention period of the Object Storage Repository must be less or equal to the backup retention period of the backup job.
To check the immutability retention period, follow these steps:
1. Go to the Backup Infrastructure tab.
2. Click Backup Repositories.
3. Right-click Object Storage Repository and choose Properties.
4. Click Next upon seeing the Name setting and Account setting.
5. Set the number to 30 to Make recent backups immutable for setting.
Result: The immutable retention period is successfully set.
To check the backup retention period, follow these steps:
1. Click the Backup section under Jobs.
2. Select the required backup job, right-click on it, and choose Edit in the menu. You will see the Job Mode screen.
3. Click Storage in the left menu and check the number in the Retention policy setting.
Note: The immutability retention period from the previous check (30) is lower than the retention policy listed here (31), and this is the correct setting.
Create a bucket for every 100 virtual machines or 200 TB of data to be backed up; Performance or Capacity Tier, depending on the use case.
