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
@@ -27,36 +29,36 @@ Azure Storage Mover facilitates the migration of unstructured data into Azure. T
27
29
28
30
## Billing components
29
31
30
-
In a migration to Azure, there are several components involved that can affect on your bill:
32
+
In a migration to Azure, there are several components involved that can affect your bill:
31
33
32
34
1. Storage Mover service usage
33
35
1. Target storage usage
34
36
1. Network usage
35
37
36
38
### 1. Storage Mover service usage
37
39
38
-
All current features of the Azure Storage Mover service are provided free of charge during the public preview. However, service enhancements and other features may be included in future releases. It's possible that the use of these features may incur a charge.
40
+
All current features of the Azure Storage Mover service are provided free of charge. However, service enhancements and other features may be included in future releases. It's possible that the use of these features may incur a charge.
39
41
40
42
### 2. Target Azure storage usage
41
43
42
-
As you begin your migration into Azure, the service will copy your files and folders into your target Azure Storage locations. Depending on the configuration of these storage targets, usage charges may apply.
44
+
As you begin your migration into Azure, the service copies your files and folders into your target Azure Storage locations. Depending on the configuration of these storage targets, usage charges may apply.
43
45
44
-
Any storage usage charges incurred will be the result of the following factors:
46
+
Any storage usage charges incurred are the result of the following factors:
45
47
46
48
- Storage transactions
47
49
- Billed capacity
48
50
49
-
The billing model for each Azure Storage target will determine how these charges apply. There are two different billing models in Azure Storage:
51
+
The billing model for each Azure Storage target determines how these charges apply. There are two different billing models in Azure Storage:
* Storage transactions caused by the Storage Mover service will be billed. Review your specific storage product's pricing pages for details on transaction charges. The [estimating storage transaction charges](#estimating-storage-transaction-charges) section of this article explains why it can be difficult to estimate a migration’s effect on your storage transaction charges.
54
-
* One advantage of the consumption-based model is that capacity charges are progressively applied. Charges are incurred only as files are migrated and increasingly more storage capacity is consumed. This model helps prevent storage pre-provisioning or over-provisioning ahead of a migration.
55
+
* Storage transactions caused by the Storage Mover service are billed. Review your specific storage product's pricing pages for details on transaction charges. The [estimating storage transaction charges](#estimating-storage-transaction-charges) section of this article explains why it can be difficult to estimate a migration’s effect on your storage transaction charges.
56
+
* One advantage of the consumption-based model is that capacity charges are progressively applied. Charges are incurred only as files are migrated and increasingly more storage capacity is consumed. This model helps prevent storage preprovisioning or over-provisioning ahead of a migration.
55
57
56
58
#### [Provisioned billing](#tab/provisioned)
57
59
58
60
* Storage transaction charges typically don't apply to targets covered by this billing model. Review your specific storage product's pricing pages for details and to confirm the previous statement actually applies to your product.
59
-
* The capacity of your Azure target storage is pre-provisioned and is billed regardless of utilization. The progress of your cloud migration doesn't affect your bill.
61
+
* The capacity of your Azure target storage is preprovisioned and is billed regardless of utilization. The progress of your cloud migration doesn't affect your bill.
60
62
61
63
> [!CAUTION]
62
64
> Always ensure that there is enough provisioned capacity to store all your source content. Copy jobs will fail if your target lacks sufficient storage capacity.
@@ -71,18 +73,18 @@ Storage transactions aren't billable for every Azure Storage type. Review the pr
71
73
72
74
If you've determined that your Azure storage product charges for transactions, it may be difficult to estimate the number generated by your migration.
73
75
74
-
- It's not possible to estimate the number of transactions based on the utilized storage capacity of the source. The number of transactions scales with the number of namespace items (files and folder) and their properties that are migrated, not their size. For example, more transactions are required to migrate one GiB of small files than one GiB of larger files.
75
-
- An empty Azure target requires fewer resources than a target which already contains items. To comply with your migration's settings, the Storage Mover agent will often need to enumerate a target's existing namespace. This enumeration increases the number of transactions.
76
+
- It's not possible to estimate the number of transactions based on the utilized storage capacity of the source. The number of transactions scales with the number of namespace items (files and folder) and their properties that are migrated, not their size. For example, more transactions are required to migrate 1 GiB of small files than 1 GiB of larger files.
77
+
- An empty Azure target requires fewer resources than a target that already contains items. To comply with your migration's settings, the Storage Mover agent often needs to enumerate a target's existing namespace. This enumeration increases the number of transactions.
76
78
- In order to minimize downtime, you may need to run copy operations several times between a source and its target. All source and target items are processed during each copy operation, though subsequent runs finish faster. After the initial operations, only the differences introduced between copy runs are transported over the network. It's important to understand that although less data is being transported, the number of transactions required may remain the same.
77
79
- Copying the same file twice might not result in the same number of transactions. Processing an item migrated in a previous copy run may result in only a few read transactions. In contrast, changes to metadata or content between copy runs may require a larger number of transactions to update the target. Each file in your namespace may have unique requirements, resulting in a different number of transactions.
78
80
79
81
### 3. Network usage
80
82
81
-
Upload bandwidth is another factor that could affect overall cost. The bandwidth utilized by your migration carries the same charge as any other Azure-bound traffic. There's no Storage Mover-specific premium. Your specific network connection and provider agreements will determine whether upload charges are incurred.
83
+
Upload bandwidth is another factor that could affect overall cost. The bandwidth utilized by your migration carries the same charge as any other Azure-bound traffic. There's no Storage Mover-specific premium. Your specific network connection and provider agreements determine whether upload charges are incurred.
82
84
83
85
## Next steps
84
86
85
-
After understanding the billing implications of your cloud migration, it's a good idea to get more familiar with the Storage Mover service. Select an article below to learn more.
87
+
After understanding the billing implications of your cloud migration, it's a good idea to get more familiar with the Storage Mover service. Select an article to learn more.
86
88
87
89
-[Understand file and folder cloud migration basics](migration-basics.md)
88
90
-[Learn about the Azure Storage Mover resource hierarchy](resource-hierarchy.md)
0 commit comments