Migration software
Komprise Elastic Data Migration
Suggested in one of our migration playbooks, mainly for Servers and cloud. Here is what it handles, how it treats key settings, and other tools for the same jobs.
What it handles
The limits of the built-in tools that Komprise Elastic Data Migration gets around, as covered in our playbooks.
NAS to Azure Files migration
- Size shares and accounts for the limits, then clean upKomprise analytics show data type, ownership, usage, age and growth per share to decide what goes to Azure Files, Azure Blob Storage or Azure NetApp Files, and it then runs the NAS migration.
- Azure Files has size limits per share, and with Azure File Sync one Windows Server can sync at most 30 shares.Analyses data type, ownership, usage, age and growth per share to decide what goes where, then runs the NAS migration.
How it handles key settings
From the settings checklists in our playbooks: what Komprise Elastic Data Migration carries across.
| Setting | How it handles it | Playbook |
|---|---|---|
| Local NAS users and groups | Not stated in Komprise's documentation: test it in your pilot. | NAS to Azure Files migration |
| File size and share size | Analyses data type, ownership, usage, age and growth per share to decide what goes where. | NAS to Azure Files migration |
Tools for the same jobs
Other tools our playbooks suggest for the same migrations.
We write these notes from the vendor documentation cited in each playbook. Tools cannot pay to be included or to change them. Check the vendor's current documentation and terms before you buy.