Merge pull request #264317 from AbhishekMallick-MS/Jan-26-2024-Freshness

Freshness - Offline-seeding

Author: prmerger-automator[bot]

articles/backup/backup-azure-backup-import-export.md

@@ -3,7 +3,7 @@ title: Offline seeding workflow for MARS using customer-owned disks with Azure I
 description: Learn how you can use Azure Backup to send data off the network by using the Azure Import/Export service. This article explains the offline seeding of the initial backup data by using the Azure Import/Export service.
 ms.reviewer: saurse
 ms.topic: how-to
-ms.date: 12/05/2022
+ms.date: 01/26/2024
 author: AbhishekMallick-MS
 ms.author: v-abhmallick
 ---
@@ -14,31 +14,22 @@ This article describes how to send the initial full backup data from MARS to Azu
 
 Azure Backup has several built-in efficiencies that save network and storage costs during the initial full backups of data to Azure. Initial full backups typically transfer large amounts of data and require more network bandwidth when compared to subsequent backups that transfer only the deltas/incrementals. Through the process of offline seeding, Azure Backup can use disks to upload the offline backup data to Azure.
 
-In this article, you'll learn about:
+## Offline-seeding flow
 
-> [!div class="checklist"]
-> - Offline-seeding process
-> - Supported configurations
-> - Prerequisites
-> - Workflow
-> - How to initiate offline backup
-> - How to prepare SATA drives and ship to Azure
-> - How to update the tracking and shipping details on the Azure import job
+The Azure Backup offline-seeding process is tightly integrated with the [Azure Import/Export service](../import-export/storage-import-export-service.md). You can use this service to transfer initial backup data to Azure by using disks. If you have terabytes (TBs) of initial backup data that need to be transferred over a high-latency and low-bandwidth network, you can use the offline-seeding workflow to ship the initial backup copy, on one or more hard drives to an Azure datacenter. 
 
-## Offline-seeding process
-
-The Azure Backup offline-seeding process is tightly integrated with the [Azure Import/Export service](../import-export/storage-import-export-service.md). You can use this service to transfer initial backup data to Azure by using disks. If you have terabytes (TBs) of initial backup data that need to be transferred over a high-latency and low-bandwidth network, you can use the offline-seeding workflow to ship the initial backup copy, on one or more hard drives to an Azure datacenter. The following image provides an overview of the steps in the workflow.
-
-  :::image type="content" source="./media/backup-azure-backup-import-export/offlinebackupworkflowoverview.png" alt-text="Screenshot shows the overview of offline import workflow process.":::
-
-The offline backup process involves these steps:
+To perform the offline backup:
 
 1. Instead of sending the backup data over the network, write the backup data to a staging location.
 1. Use the *AzureOfflineBackupDiskPrep* utility to write the data in the staging location to one or more SATA disks.
 1. As part of the preparatory work, the *AzureOfflineBackupDiskPrep* utility creates an Azure import job. Send the SATA drives to the nearest Azure datacenter, and reference the import job to connect the activities.
 1. At the Azure datacenter, the data on the disks is copied to an Azure storage account.
 1. Azure Backup copies the backup data from the storage account to the Recovery Services vault, and incremental backups are scheduled.
 
+The following diagram provides an overview of the offline-seeding flow:
+
+  :::image type="content" source="./media/backup-azure-backup-import-export/offlinebackupworkflowoverview.png" alt-text="Diagram shows the overview of offline import workflow process.":::
+
 >[!Note]
 >Ensure that you use the latest MARS agent (version 2.0.9250.0 or higher) before following the below sections. [Learn more](backup-azure-mars-troubleshoot.md#mars-offline-seeding-using-customer-owned-disks-importexport-is-not-working).