Before planning a real backup of files and folders from my customer's on-premises Windows Server 2012 with offline seeding, I have set up and performed afake offline backup from on-premises W10 Pro Client. As this attempt was just a test I won't send the disk to Microsoft, therefore I'm going to cancel this import job process, successfully created and visible inside the Classic Portal.
Everything worked well following the available documentation through these steps:
- New ARM backup vault
- New Storage account with CLASSIC deployment, although created from new portal
- Download latest agent with credentials, agent installed and registered
- Backup configured (folders, schedule and retention)
- Backup performed on local transient folder, Disk generated using new utility AzureOfflineBackupDiskPrep
So far so good. Now I have some doubts about what exactly would happen at the time Microsoft would import Disk data into my classic Storage account/container.
Here I read from a user question answered by the staff:
Q:Since the ARM storage accounts are not supported yet for the Import/Export Service, can I import the data to a Classic (ASM) storage account and then have the Azure backup agent copy the data to the Azure Backup vault that was created in ARM?
A:Yes, you can import the data to a Classic (ASM) storage account and have it seed your initial backup data using Offline seeding. The Agent would copy the data from the storage account to the Azure Backup vault created in ARM (a.k.a Recovery Services Vault), once the data is available on the storage-account
Will the agent automatically transfer data from Classic storage to ARM Backup vault blob storage?
After, the agent will start the first incremental online backup automatically?
Marco