Seeding data to Azure using the Microsoft Azure Import/Export service (4041718)

In replication, the initial transfer of deduplicated base images and incremental snapshots of protected agents, can add up to hundreds or thousands of gigabytes of data. Initial replication can be seeded to the target core using external media, which is useful for large sets of data or sites with slow links.  See Determining your seeding needs and strategy for more information.

When seeding your data to an Azure replication target, use the Microsoft Azure Import/Export service. This service has certain prerequisite and requirements. These are documented on the Azure website, and links to some relevant articles are included below.

Following are some guidelines for seeding to Azure:

• Transfer your repository archives to one or more 3.5-inch Serial Advanced Technology Attachment (SATA) II or SATA III internal hard drives, 8TB or smaller.
• You can transfer a maximum of 80TB of data, based on Microsoft's guidelines. Microsoft charges a nominal fee per drive to seed your data. For current pricing, see the Azure website or contact an Azure representative.
• You must have an existing Azure subscription and one or more Classic storage accounts to use the Azure Import/Export service.
• Due to Azure Storage and File Size Limitations, Page Blob has a limit of 1 TB8TB , while Block Blob has a limit of  195 GB 4.75 TB.
• Since Microsoft can change prerequisites, requirements, costs, and so on, always verify this information.

For more information, including specific articles regarding pricing and procedure for using the Microsoft Azure Import/Export service, see Microsoft Azure documentation.

1. If you have a scheduled archive already configured and running incremental archives on a daily, weekly or monthly basis and you are storing the Archive Data on a Direct Attached Storage or NAS it is going to be faster and pretty straight forward; unless you only want to include an specific time frame for the Recovery Points in order to lower the amount of data that needs to be copied into the seed drive, if the second scenario is your case the Method 2 is going to be more feasible for you.
2. Follow the steps from MS Azure listed below in order to create the import job and ship the external hard drive to a MS Azure Data Center.
3. Use the Azure Import/Export Tool to copy your data from the existing Archive Storage to one or more external hard drives. Make sure to copy the archive into a folder on the drive(s). Do not place the archive data directly on the root of the drive. 
4. Once the process is complete on the Azure Import process explained below and MS has copied the Archive data from the external hard drive(s) to the storage account, you should be ready to import the Archive on the Target Core VM. You will need to add the storage account to the Cloud Accounts page in the core console.
5. Import the Archive Data from the storage account into the Target Core Repository.
6. Configure replication from Source to Target, it should recognize that the Recovery Points are already stored in the Target Repository and should start replicating only the incremental backups.

Method 2: One Time Archive

1. Create a one time Archive using the external hard drive(s), using the Recycle action "do not reuse". Ensure this archive goes to a folder on the drive. Do not send the archive to the root of the drive. 
2. Follow the steps from MS Azure listed below in order to create the import job and ship the external hard drive to a MS Azure Data Center. Make sure that you choose a storage account that is in the same region as your Azure virtual machine. This will ensure there are no additional data egress charges when accessing the storage account from the Azure VM. It will also ensure maximum possible performance when importing the data into Rapid Recovery. 
3. Use the Azure Import/Export Tool to copy your data from the Archive Storage to one or more external hard drives.
4. Once the process is complete on the Azure Import process explained below and MS has copied the Archive data from the external hard drive(s) to the storage account, you should be ready to import the Archive on the Target Core VM. You will need to add the storage account to the Cloud Accounts page in the core console. 
5. Import the Archive Data from the storage account into the Target Core Repository.
6. Configure replication from Source to Target, it should recognize that the Recovery Points are already stored in the Target Repository and should start replicating only the incremental backups.

NOTE: For more details about How to Use the Microsoft Azure Import/Export Service, these are the recommended articles:

• When should I use the Azure Import/Export service?.
• How does the Azure Import/Export service work?.
• How to create an Import Job?.

Other related articles:

• Understanding Block Blobs, Append Blobs, and Page Blobs.
• Azure increases the maximum size and performance of Azure Disks.

NOTE: If you are not able to create a Block Blob larger than 195 GB (previous max size), with the Azure Import Export Tool version that you have, please contact Azure Import Export Support, and they will provide you a version of the Azure Import Export Tool that supports Block Blob up to 4.75 TB (new max size).