Skip to content

Commit d2f4846

Browse files
authored
Merge pull request #18136 from ronhogue/ronh-2025-06-06-auto-export
add auto-export page
2 parents 158e5ae + e662837 commit d2f4846

File tree

5 files changed

+174
-2
lines changed

5 files changed

+174
-2
lines changed

azure-managed-lustre/TOC.yml

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,8 +20,10 @@
2020
href: blob-integration.md
2121
- name: Import data using import jobs
2222
href: create-import-job.md
23-
- name: Export data using export jobs
23+
- name: Export data using manual export jobs
2424
href: export-with-archive-jobs.md
25+
- name: Export data using auto-export jobs
26+
href: auto-export.md
2527
- name: Access a file system
2628
items:
2729
- name: Install Lustre client

azure-managed-lustre/auto-export.md

Lines changed: 168 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,168 @@
1+
---
2+
title: Use Azure Managed Lustre Auto-Export (Preview)
3+
description: How to use auto-export job to copy data from your Azure Managed Lustre file system to long-term storage in Azure Blob Storage.
4+
ms.topic: how-to
5+
ms.date: 06/06/2024
6+
author: pauljewellmsft
7+
ms.author: brlepore
8+
ms.reviewer: brianl
9+
10+
# Intent: As an IT Pro, I need to be able to auto-export files from my Azure Managed Lustre file system to long-term Azure Blob Storage.
11+
# Keyword:
12+
---
13+
# Azure Managed Lustre Auto-Export (Preview)
14+
15+
The Auto-Export feature for Azure Managed Lustre is a capability that automatically synchronizes changes in your Azure Managed Lustre file system with a linked Azure Blob Storage Container. This feature ensures that new and modified files in the file system are reflected in the associated Blob Storage Container without manual intervention. This streamlines data management and improves synchronization for long-term storage.
16+
17+
## How auto-export works
18+
19+
Auto-Export operates by continuously monitoring changes in the Azure Managed Lustre file system. Based on the configured export policy, it updates the contents of the associated Blob Storage Container to reflect these changes. This feature provides users with a seamless and automated data replication process.
20+
21+
### Configuration
22+
23+
Auto-Export is enabled on an existing Azure Managed Lustre file system that has an associated Blob Storage Container configured. Auto-Export is configured in the Blob Integration settings in the Azure portal.
24+
25+
To create a new Auto-Export job, follow these steps:
26+
27+
1. In the Azure portal, open your Azure Managed Lustre file system and select the **Blob integration** pane under **Settings**.
28+
1. Select **+ Create new job**.
29+
1. In the **Job Type** dropdown, select **Auto-Export**.
30+
1. In the **File system path** field, you can enter a string to specify a directory path. All new or changed files in the file system under this path (prefix) are continually exported. Files are written to the blob container with the same file path (or prefix) that they have in the Lustre system. To avoid overwriting existing files in the blob container, ensure that the path of the file in your Lustre system doesn't overlap with the existing path of the file in the blob container unless your Lustre file was imported from that path in the Blob Container.
31+
32+
:::image type="content" source="media/auto-export/auto-export-create-job.png" alt-text="Screenshot of the Blob integration page for Azure Managed Lustre showing Create import/export job." lightbox="media/auto-export/auto-export-create-job.png":::
33+
34+
### Auto-Export Behavior
35+
36+
Auto-Export handles different types of changes as follows:
37+
38+
- **New File Creation, New Directory, and File Content Changes**: Blob Integration identifies new files and directories and changed data and starts an export job automatically. Auto-Export ensures that the latest version of the file is transferred to Blob Storage.
39+
- **Metadata Changes**: Changes such as renames, ownership updates, or permission adjustments are **not synchronized** currently.
40+
- **Deletion**: When files, directories, or symlinks are deleted in the file system, they are **not removed** from the Blob Storage Container.
41+
42+
No more than one Blob Integration job (Manual Export, Auto Export, Import) can be run at a time.
43+
Auto-Export is implemented as continuous export iterations. Upon completion of an iteration, Blob Integration scans the filesystem for any new files, directories, or content changes and starts a new iteration of an export job.
44+
Logs created in your configured Logging container can help identify synchronization issues and understand the reasons behind failed operations.
45+
46+
## Monitoring and Managing Auto-Export
47+
48+
You can monitor Auto-Export activities and manage configurations using the Azure portal:
49+
50+
The Blob Integration pane displays details of export activities in the **Recent jobs** section, including the status of recent jobs and metrics related to automatic synchronization.
51+
52+
To cancel the job that's in progress, select the **Cancel** link for that job in the **Recent jobs** table. The **Cancel** link is only available for the current auto-export.
53+
54+
To view the metrics of an Auto-Export job, click on the **Name** of the job, and the **Metrics blade** appears on the side panel in the Portal.
55+
56+
:::image type="content" source="media/auto-export/auto-export-job-details.png" alt-text="Screenshot of the Blob integration page for Azure Managed Lustre showing Job details." lightbox="media/auto-export/auto-export-job-details.png":::
57+
58+
### Auto-Export Job Monitoring
59+
60+
The Blob Integration pane displays details of export activities in the **Recent jobs** section, including the status of recent jobs and metrics related to automatic synchronization.
61+
To cancel the job that's in progress, select the **Cancel** link for that job in the **Recent jobs** table. The **Cancel** link is only available for the current auto-export.
62+
To view the metrics of an Auto-Export job, click on the **Name** of the job, and the **Metrics blade** appears on the side panel in the Portal.
63+
64+
### Metrics
65+
66+
Metrics are grouped into two main categories, *Overall* and *Current Iteration*.
67+
68+
:::row:::
69+
:::column span="":::
70+
**Overall Statistics**
71+
:::column-end:::
72+
:::column span="2":::
73+
**Statistics since enabling Auto-Export**
74+
:::column-end:::
75+
:::row-end:::
76+
:::row:::
77+
:::column span="":::
78+
Total Files Exported
79+
:::column-end:::
80+
:::column span="2":::
81+
Count of files successfully copied to the associated Blob Container since enabling Auto-Export
82+
:::column-end:::
83+
:::row-end:::
84+
:::row:::
85+
:::column span="":::
86+
Total MiB Exported
87+
:::column-end:::
88+
:::column span="2":::
89+
Aggregate file size (in MiB) successfully copied to the associated Blob Container since enabling Auto-Export
90+
:::column-end:::
91+
:::row-end:::
92+
:::row:::
93+
:::column span="":::
94+
Iterations Completed
95+
:::column-end:::
96+
:::column span="2":::
97+
Count of times Blob Integration has identified new or changed data and initiated a new Export job
98+
:::column-end:::
99+
:::row-end:::
100+
:::row:::
101+
:::column span="":::
102+
Last Successful Iteration
103+
:::column-end:::
104+
:::column span="2":::
105+
Finish timestamp of the last iteration that successfully exported all data to the associated Blob Container at the time
106+
:::column-end:::
107+
:::row-end:::
108+
109+
:::row:::
110+
:::column span="":::
111+
**Current Iteration Statistics**
112+
:::column-end:::
113+
:::column span="2":::
114+
**Statistics about the current activity**
115+
:::column-end:::
116+
:::row-end:::
117+
:::row:::
118+
:::column span="":::
119+
Files Discovered
120+
:::column-end:::
121+
:::column span="2":::
122+
Count of files that the Export job is currently exporting, including files already successfully copied to the associated Blob Container in this Iteration*
123+
:::column-end:::
124+
:::row-end:::
125+
:::row:::
126+
:::column span="":::
127+
MiB Discovered
128+
:::column-end:::
129+
:::column span="2":::
130+
Aggregate file size (in MiB) that the Export job is currently exporting, including files already successfully copied to the associated Blob Container in this Iteration*
131+
:::column-end:::
132+
:::row-end:::
133+
:::row:::
134+
:::column span="":::
135+
Files Exported
136+
:::column-end:::
137+
:::column span="2":::
138+
Count of files of new and changed data successfully copied to the associated Blob Container
139+
:::column-end:::
140+
:::row-end:::
141+
:::row:::
142+
:::column span="":::
143+
MiB Exported
144+
:::column-end:::
145+
:::column span="2":::
146+
Aggregate file size (in MiB) of new and changed data successfully copied to the associated Blob Container
147+
:::column-end:::
148+
:::row-end:::
149+
:::row:::
150+
:::column span="":::
151+
Files Failed
152+
:::column-end:::
153+
:::column span="2":::
154+
Total number of files that failed to copy during the current iteration. Click on this link to be taken to the Logging Container page to view the logs associated with this Auto-Export job.
155+
:::column-end:::
156+
:::row-end:::
157+
\* The metrics for the current ongoing iteration should be read as “so far.” For example, Files Discovered is the number of the files discovered for exporting at the moment of reporting. The next stats reporting cycle may show that more files are discovered.
158+
159+
## Considerations and Best Practices
160+
161+
While using Auto-Export, consider the following best practices to ensure smooth operation:
162+
163+
- **Conflict Management**: If a file is modified in both the file system and Blob Storage, there is a risk of overwrite. Use application-level coordination to prevent conflicting edits.
164+
- **Disable Auto-Export Before Deletion**: Before deleting a file system or its Blob Integration, ensure that all queued updates are synchronized. Verify that the **Last Successful Iteration Time** is recent and the **Files Failed** metric is zero to avoid data loss. Then, disable Auto-Export.
165+
166+
## Next step
167+
168+
- Learn more about [Azure Blob Storage integration with Azure Managed Lustre file systems](blob-integration.md).

azure-managed-lustre/index.yml

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,8 +42,10 @@ landingContent:
4242
links:
4343
- text: Import data using import jobs
4444
url: create-import-job.md
45-
- text: Export data using export jobs
45+
- text: Export data using manual export jobs
4646
url: export-with-archive-jobs.md
47+
- text: Export data using auto-export jobs
48+
url: auto-export.md
4749
- title: Access a file system
4850
linkLists:
4951
- linkListType: how-to-guide
141 KB
Loading
249 KB
Loading

0 commit comments

Comments
 (0)