Skip to content

Commit 2af838e

Browse files
committed
Fixing formatting.
1 parent 55f4592 commit 2af838e

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

articles/storage/elastic-san/elastic-san-snapshots.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -147,7 +147,11 @@ az elastic-san volume snapshot delete -g "resourceGroupName" -e "san_name" -v "v
147147

148148
## Export volume snapshot
149149

150-
Elastic SAN volume snapshots are automatically deleted when the volume is deleted. If you need your snapshot's data to persist beyond deletion, export them to managed disk snapshots. The export process will take time and will depend on the size of the snapshot. You can check how much is left before completion by checking the CompletionPercentage property of the managed disk snapshot. Once you export an elastic SAN snapshot to a managed disk snapshot, the managed disk snapshot begins to incur billing charges. Elastic SAN snapshots don't have any extra billing associated with them, they only consume your elastic SAN's capacity.
150+
Elastic SAN volume snapshots are automatically deleted when the volume is deleted. For your snapshot's data to persist beyond deletion, export them to managed disk snapshots. Exporting a volume snapshot to a managed disk snapshot takes time, how much time it takes depend on the size of the snapshot. You can check how much is left before completion by checking the `CompletionPercentage` property of the managed disk snapshot.
151+
152+
### Billing implications
153+
154+
Elastic SAN snapshots don't have any extra billing associated with them, they only consume your elastic SAN's capacity. Once you export an elastic SAN snapshot to a managed disk snapshot, the managed disk snapshot begins to incur billing charges.
151155

152156
# [Portal](#tab/azure-portal)
153157

0 commit comments

Comments
 (0)