You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/storage-mover/release-notes.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -90,8 +90,8 @@ Refresh release notes for:
90
90
- Improved network connectivity testing: The Storage Mover agent now utilizes the Azure ARC CLI tool (azcmagent) and a curl GET command to verify the ARC and Storage Mover endpoints with the 'Test Network Connectivity' option in the agent console.
91
91
- A new option, 'Test Network Connectivity Verbosely' can help diagnose local network problems more easily.
92
92
- Improved user experience to error conditions during agent registration and unregistration processes.
93
-
- Since Storage Mover depends on Azure ARC and an Entra ID Managed Identity, additional safeguards are added that ensure seamless registration: The ARC *Hybrid Compute* resource is now created in the same region as the storage mover resource, anas well as the Azure Arc Private Link Scope (if applicable) is in the same Azure region.
94
-
- Improved instructions during agent registration when leveraging private networking.
93
+
- Since Storage Mover depends on Azure ARC and an Entra ID Managed Identity, extra safeguards are added that ensure seamless registration: The ARC *Hybrid Compute* resource is now created in the same region as the storage mover resource, anas well as the Azure Arc Private Link Scope (if applicable) is in the same Azure region.
94
+
- Improved instructions during agent registration when using private networking.
95
95
- Security improvements and bug fixes.
96
96
97
97
## 2023 December 1
@@ -119,13 +119,13 @@ Major refresh release notes for:
119
119
- Agent version: 2.0.358
120
120
121
121
### Migration scenarios
122
-
- Migrating your SMB shares to Azure file shares has become generally available.
122
+
- Migrating your SMB shares to Azure file shares became generally available.
123
123
- The Storage Mover agent is now supported on VMware ESXi 6.7 hypervisors, as a public preview.
124
124
- Migrating NFS shares to Azure Data Lake Gen2 storage is now available as a public preview.
125
125
126
126
### Service
127
127
128
-
- Migrations from NFS shares to Azure storage accounts with the hierarchical namespace service feature (HNS) enabled, are now supported and automatically leverage the ADLS Gen2 REST APIs for migration. This allows the migration of files and folders in a Data Lake compliant way. Full fidelity is preserved in just the same way as with the previously existing blob container migration path.
128
+
- Migrations from NFS shares to Azure storage accounts with the hierarchical namespace service feature (HNS) enabled, are now supported and automatically apply the ADLS Gen2 REST APIs for migration. This API allows the migration of files and folders in a Data Lake compliant way. Full fidelity is preserved in just the same way as with the previously existing blob container migration path.
129
129
-[Error codes and messages](status-code.md) have been improved.
130
130
131
131
### Agent
@@ -255,5 +255,5 @@ To access copy logs on the agent:
1. A list of jobs that have run on the agent is shown. Copy the ID in the format `Job definition id: Job run id` that represents the job you want to retrieve the copy logs for. You can confirm you've selected the right job by looking at the details of your selected job by pasting it into menu option `3) Job details`
258
+
1. A list of jobs that previously ran on the agent is shown. Copy the ID in the format `Job definition id: Job run id` that represents the job you want to retrieve the copy logs for. You can confirm the selection of the correct job by looking at the details of your selected job by pasting it into menu option `3) Job details`
259
259
1. Retrieve the copy logs by selecting option `4) Job copylogs` and providing the same ID from the previous step.
0 commit comments