Block Generation

When you configure immutability, keep in mind that an additional period of up to 10 (by default) days will be automatically added to the immutability expiration date. This period is called Block Generation. For example, if you set your immutability period to 30 days, 10 days will be added, and total immutability period will be up to 40 days.  

Block Generation works in the following way. When the first data block (a full backup) arrives, its immutability period is set to 30 + 10 = 40 days. The first full backup starts its generation, that will be appended with the incremental backups. All the incremental backups within the generation (i.e. within the 10-days period) will have the same immutability expiration date as the full backup. For instance, a data block that was offloaded on day 9 will have the same immutability expiration date as a data block offloaded on day 1. Thus we ensure that the immutability period for all the data blocks within a generation is no less than 30 days.

Consider this example: within one forward incremental backup chain, a full backup file can not be removed before an incremental backup file. On the other hand, an incremental backup file makes no sense without relevant full backup file. So the immutability period is extended for all data blocks in the backup chain.

The Block Generation period was introduced in order to reduce the number of requests to the capacity tier, thereby saving traffic and reducing costs that might be incurred by your storage provider. With 10 days of immutability automatically added, it means there is no need to extend the immutability period for the incremental backups in forward chain and for the unchanged blocks of current full backups in reverse chain offloaded within those 10 days. On the 11th day, though, the immutability period will have to be extended (in order to ensure that the immutability period for all the data blocks within a generation is no less than 30 days).

The immutable blocks of data may be reused during the offload. Veeam Backup & Replication continues to keep reused or dependent blocks of data locked by continuously assigning them to new generations, thereby extending their immutability expiration period. This is valid both for forward and reverse incremental backup chains.

The extension of immutability works differently in different cases, as follows:

Forward incremental backup chain

  • New full backup file in the new generation:
  • Immutability is extended for the data blocks that are being reused from the old backup chain,
  • Immutability is set anew for the new blocks of the new full backup file.
  • New incremental backup file in the new generation:
  • Immutability is extended for all the data blocks from the current backup chain,
  • Immutability is set anew for the new blocks of the latest incremental backup file.

Reverse incremental backup chain

  • New full backup file in the new generation:
  • Immutability is extended for the data blocks that are being reused from the previous full backup file,
  • Immutability is set anew for the new blocks of the new full backup file.
  • Current full backup file in the new generation:
  • Immutability is extended for all the data blocks of this full backup file that are already stored in the capacity tier,
  • Immutability is set anew for the new blocks of this full backup file.

Related Topics

I want to report a typo

There is a misspelling right here:

 

I want to let the Veeam Documentation Team know about that.