Increase in API Calls when Performing Backups Directly to Immutable Object Storage

KB ID: 4470
Product: Veeam Backup & Replication | 12
Published: 2023-07-11
Last Modified: 2023-07-18
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

Challenge

When backing up directly to Object Storage that has immutability enabled, an increase in API callsspecifically PutObjectLockRetention to the Object Storage is noticed. This behavior is observed when using either a simple Object Storage Repository or when targeting a Scale-Out Backup Repository that uses an Object Storage Repository as its Performance Tier. The spike in API calls occurs at regular intervals, typically around every 10 days.

Cause

This situation is caused by the way in which backup file immutability is maintained when using Immutable Object Storage as a primary backup destination. As explained in the "How Block Generation Works" section, Veeam Backup & Replication utilizes Block Generations to extend the immutability of groups of backup files in 10-day intervals. This approach is implemented to reduce I/O operations with the storage over time.

Solution

Expected Behavior
The immutability extension API calls occurring on a periodic interval are an expected outcome of the Block Generation and immutability extension design.

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 (Storage Optimization) of the backup files generated by jobs that perform direct backups to immutable object storage. Increasing the block size used when creating the backup files will reduce the number of blocks involved in the immutability extension process, but will increase the size of the incremental restore points (on average twice as large).

Keep in mind that changing the block size (Storage Optimization) 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 submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.