Storage federation use cases
|Federated workload balancing.|
Powers the non-disruptive movement of entire an application workload between storage systems for more efficient resource utilization, avoiding performance hotspots and bottlenecks, ensuring service levels, and meeting stringent SLAs.
|Federated asset management|
Non-disruptive data movement between existing and new devices (or architectures) for more effective storage asset management. Now technology refreshes and asset re-purposing can be done without time-consuming planning and migration.
|Federated thin provisioning|
Non-disruptively move thinly provisioned virtual volumes between peer systems in order to manage unpredictable growth and maximize capacity utilization.
|Federated high availability|
Establish replication and recovery relationships between systems to ensure business continuity in the event of a disaster and allow server and application maintenance operations to take place non-disruptively.
|Federated data management|
Non-disruptively move across media types and/or storage architectures (primary, backup, and archive) based on factors such as data access frequency and retention policies. Optimize storage resources, reduce storage costs, simplify backup, speed restores, extract more value from that data, meet SLAs, and fulfill governance and compliance requirements.
Allows deduplicated data to move across systems without rehydration to minimize network bandwidth requirements, speed data transfers, ensure replication quality of service, and keep capacity requirements at a minimum.
Link physical capacity from two or more storage resources that are presented as a single logical entity to simplify management, enable scale-out for capacity growth, simplify asset management of underlying hardware, and optimize deduplication.