Previous Topic

Next Topic

Book Contents

Book Index

Service Integration - Adjusting Maximum File Size for Block Blob File Store

For a MOVEit Transfer deployment that leverages Azure Blob storage, an Azure Blob is conceptually equivalent to a MOVEit Transfer file. However, from the perspective of Azure Storage, it is useful to know that very large files can require adjustments to Blob block size. An Azure Block Blob can have a maximum of 50,000 blocks, but block size is configurable up to 100MB.

Therefore, consider these guidelines to increase the allowed file size when you deploy your MOVEit Transfer file store to Azure Blobs.

Adjusting Maximum File Size (MaxBlockBytes)

When configured to leverage Azure Storage, MOVEit Transfer currently leverages Block Blobs. Blob block size is controlled by the FSAzureBlockBlob registry key set by the MOVEit Transfer installer or the Blob Conversion Assistant.

Background

The following points are helpful when considering the best block size for your instance of MOVEit Transfer:

Adjust the Maximum File Size at the MOVEit Transfer Server

To Adjust Maximum File Size Within Your Azure Blob Storage File Store.

  1. Go to the Windows Server machine running the MOVEit Transfer Server (for web farm deployment patterns, this would be the primary MOVEit Transfer node) and find the following registry key:

    HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Standard Networks\siLock\FSAzureBlockBlob

  2. FSAzureBlockBlob can have an optional REG_DWORD subkey for block size (MaxBlockBytes). If it is not there, you can add it.

    important Important: MaxBlockBytes must be a value between 1048576 (1MB) and 104857600 (100MB), inclusive. An Azure Storage Service block size of 100MB can yield a max Blob of around 4.75TB. Values outside this range can cause exceptions when you start/restart MOVEit Transfer services.