Meta-volume performance and availability requirements
Performance is not critical for meta-volumes. The minimum performance that is allowed is 40 MB/sec and 100 4 K IOP/second.
For non-flash arrays, the physical spindles for meta-volumes should be isolated from application workloads.
The following is recommended for meta-volumes:
Read caching must be enabled
A hot spare meta-volume must be pre-configured in case of a catastrophic failure of the active metavolume.
If possible, do not use devices on LUN0. Paths to LUN0 are removed and added whenever its array goes through discovery. This behavior is because LUN0 can be either a default LUN or a real LUN backed by real storage."
Availability is critical for meta-volumes. The meta-volume is essential for system recovery. The best practice is to mirror the meta-volume across two or more back-end arrays to eliminate the possibility of data loss. Choose the arrays that mirror the meta-volume so that they are not required to migrate simultaneously.
WARNING:Do not create meta-volume using volumes from a single storage array. Single array meta-volumes are not a high availability configuration and are a single point of failure.
If metro node temporarily loses access to all meta-volumes, the current metadata in cache is automatically written to the meta-volumes when access is restored.
If metro node permanently loses access to both meta-volumes, it continues to operate based on the metadata in memory. Configuration changes are suspended until a new meta-volume is created.
NOTE:If the metro node loses access to all meta-volumes, and all directors either fail or restart, changes made to the metadata (the metro node configuration) after access was lost cannot be recovered. System volumes are supported on thinly provisioned LUNs, but these volumes must have thin storage pool resources available, at maximum capacity. System volumes must not compete for this space with user-data volumes in the same pool.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\