Increase in API Calls when Performing Backups Directly to Immutable Object Storage
Challenge
Cause
Solution
There are two ways to reduce the overall quantity of API calls needed to maintain immutability. These may be combined or used independently.
Option 1: Reduce the Quantity of Blocks by Increasing Block Size
To decrease the number of API calls, consider increasing the block size of the backup files generated by jobs that perform direct backups to immutable object storage. By increasing the block size, the number of blocks involved in the immutability extension process will be reduced. Keep in mind that changing the block size in a backup job will only take effect during the next Active Full backup session. Additionally, if backup copy jobs target the immutable object storage, the block size change must be implemented in the source backup jobs first, followed by forcing an Active Full backup in both the source backup and backup copy jobs.
Option 2: Adjust the Immutability Extension Frequency
The immutability extension frequency, which affects the number of API calls, can be reduced by adjusting the Block Generation interval. By increasing this interval, the occurrence of immutability extensions within a given time frame can be minimized while maintaining the same overall immutability duration.
To adjust the Block Generation interval, configure the following registry value on the Veeam Backup Server:
Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication
Value Name: ObjectStorageImmutabilityGenerationDays
Value Type: DWORD (32-bit) Value
Value Data (Dec): Adjust the value based on specific requirements.
It is crucial to note that when extending the Block Generation length, the immutability setting at the repository level should be reduced in order to maintain the same overall immutability duration.
As detailed in the How Block Generation Works user guide section, the Block Generation value is added to the configured immutability. This ensures that the overall immutability duration is maintained while adjusting the frequency of immutability extensions.
For example, with the default Block Generation interval of 10 days and an immutability configuration of 11 days, objects remain immutable for up to 21 days, with immutability extensions occurring every 10 days. However, if you change the Block Generation interval to 20 days and set the immutability to 1 day, objects will still maintain immutability for up to 21 days, but immutability extensions will only be required every 20 days.
In both scenarios, the overall block immutability duration remains the same (21 days). However, by extending the Block Generation interval, the number of immutability extensions decreases. For instance, over 2 months, only 3 immutability extensions would occur instead of 6.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.