One of the biggest hurdles of integrating public cloud storage, such as Microsoft Azure, into a modern data workflow is actually moving data to the cloud.
Ingress fees can stack up quickly for datasets with millions of objects, and high latencies can impact end users while data is flowing from primary systems to the cloud. Additionally, moving this data can be cumbersome and time consuming for IT just to initiate and monitor the data movement, and keep track of where the data winds up for retrieval.
Igneous’ policy-driven data movement allows for replication to Microsoft Azure, simplifying the process. This data is moved first to Igneous for regular backup using latency-aware data movement, then to the cloud, meaning end users won’t see any impact either during the initial backup or when data is moved to Azure. Igneous replicates data to the cloud in efficient format, grouping many objects into blobs and dramatically reducing ingress fees. Finally, metadata for any data moved to the cloud is collected and stored in Igneous’ universal metadata index, making retrieval simple.
For more information about Igneous’ integration with Microsoft Azure, check out these resources:
- Igneous Integration with Microsoft Azure
- Announcing Easy Tiering and Replication to Microsoft Azure Archive Blob Storage with Igneous
- 3 Questions to Ask to Decide What to Tier to Microsoft Azure
- Learn how Igneous enables NAS Backup to Cloud
- View DataProtect on the Azure Marketplace
- View DataDiscover on the Azure Marketplace