Azure Storage Mover
Managed migration service that copies on-premises shares and S3 buckets into Azure Storage.
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| accelerator | enum | none | gpu | asic | no | none | inherited |
| concurrency | integer | — | no | — | inherited |
| fanoutStrategy | enum | none | push | pull | hybrid | no | none | inherited |
| fanoutThreshold | integer | — | no | — | inherited |
| idempotent | boolean | — | no | false | inherited |
| instances | integer | — | no | — | inherited |
| managed | boolean | — | no | false | ▸ true |
| migrationMode | enum | agent-based | agentless | no | agent-based | inherited |
| rateControl | enum | none | fixed | aimd | no | none | inherited |
| schedule | string | — | no | — | inherited |
| sourceProtocol | enum | smb | nfs | s3 | azure-blob | no | — | inherited |
| targetType | enum | blob-container | file-share | no | — | inherited |
| trigger | enum | queue | stream | schedule | batch | manual | yes | — | ▸ manual |
Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.
Pure push fan-out over a social graph is brutal at the tail: one post from an account with millions of followers becomes millions of cache writes. A follower threshold above which readers merge at read time bounds that write amplification.
- — all of these hold:
- — the node's `fanoutStrategy` is "push"
- — the node's `fanoutThreshold` has no value
- — the design contains a node of kind graph-database
One worker pool consuming several queues lets a slow or poisoned queue starve the others. That is precisely what the design's per-queue isolation requirement forbids.
- — all of these hold:
- — the node has more than 1 incoming edge from a queue
- — the design requirement `isolation.perQueue` is true
A stateful compute node pinned to exactly one availability zone disappears with that zone, and its state goes with it. Nodes inside a cell are exempt, because there the cell is deliberately single-zone and redundancy comes from the other cells.
- — all of these hold:
- — the node's `stateless` is false
- — the node sits inside exactly 1 availability-zone group
- — this does not hold:
- — the node sits inside at least one cell group
nodes:
- { id: "storage-mover", component: "azure-storage-mover" }# yaml-language-server: $schema=../../schema/component.schema.json # Azure Storage Mover: managed migration service that copies file shares and buckets into Azure # Storage. Migrations start when you start them, so jobs are on demand, and a copy runs either # through an agent VM deployed near the source or agentless ("Introduction to Azure Storage # Mover"). schemaVersion: "1" type: "component" id: "azure-storage-mover" kind: "worker" provider: "azure" docs: "https://learn.microsoft.com/en-us/azure/storage-mover/service-overview" defaults: trigger: "manual" managed: true properties: migrationMode: type: "enum" values: ["agent-based", "agentless"] default: "agent-based" sourceProtocol: type: "enum" values: ["smb", "nfs", "s3", "azure-blob"] targetType: type: "enum" values: ["blob-container", "file-share"]