DellEMC just released Unity 4.1. Listed below are the release notes on the New Features of Unity in the release of 126.96.36.19959731.
Data-in-Place conversions are a procedure by which a storage processor assembly can be upgraded, while keeping all data and configurations in place. This procedure is offline, meaning data will be unavailable during the upgrade.
Reduced number of restarts when adding I/O modules
The system now restarts fewer times after adding I/O modules.
Reset and hold
A new state has been added, hold-and-reset, which allows for easier I/O module replacement. The system no longer needs to be completely powered down or placed in service mode.
Direct Current (DC) 15-slot DAE
A new 15-slot direct current disk array enclosure is now supported on Unity.
1Gbe SFP support
Unity now supports 1Gbe connections with a new Small Form-factor Pluggable (SFP)[for CNA].
Long distance, single mode 16Gb FC SFP support
Unity now supports long distance, single mode 16Gb connections with a new Fibre Channel SFP.
Storage efficiency enhancements
This release introduces compression for thin LUNs in all-Flash pools. New data is compressed on the initial write from the host. Compression stops for new writes when sufficient resources are not available, and resumes automatically once enough resources are available. Data that cannot be compressed is detected, and is written uncompressed.
When you enable compression, only new data is compressed, not data that already exists on the LUN. In order to compress existing data, you must move the LUN’s data to a destination LUN that has compression enabled. Use the new Compress Now feature to move the data. In Unisphere, navigate to Block > LUNs, select the relevant LUN, and then select More Actions > Compress Now.
If you need to convert a pool to a hybrid pool (consisting of both Flash and non-Flash drives), any LUNs that use compression must be deleted or moved. Hybrid pools cannot have compression enabled, and you cannot create a compression-enabled LUN in a hybrid pool. An all-Flash pool can contain both compression-enabled and non-compression enabled LUNs.
This release introduces the capability to move a LUN. The LUN move session feature lets you move existing LUNs in the system:
- To a pool with faster drives.
- Between pools for load balancing.
- To take advantage of newly purchased spindles.
- To enable compression (for either newly-written data or both newly-written data and existing data) on a thin LUN in an all-Flash pool. Note that if you choose to compress existing data, the LUN data is moved within the same pool.
You can move a member LUN in a Consistency Group. If it has associated snapshots, they will be deleted once the move completes successfully. You can also move a VMFS LUN. A maximum of 100 move sessions are allowed, with a maximum of 16 allowed to be in progress simultaneously. Any additional sessions are queued, up to the 100 maximum limit. While a LUN is being moved, you can view the status from the LUN Summary and LUN Properties windows. Once completed, the LUN move status can be viewed for up to 3 days from the same two windows.
Flash drive enhancements
- Support for SAS Flash 4 drives in all Flash pools. SAS Flash 4 drives are one-write-per-day drives.
- Support for a mixture of SAS Flash 2, SAS Flash 3, and SAS Flash 4 drives in the same Extreme Performance tier.
- Support for SAS Flash 3 drives in a hybrid pool. (A hybrid pool consists of both Flash and non-Flash drives).
This release supports IP multi-tenancy (separate IP namespaces), which provides the ability to assign isolated, file-based storage partitions for NAS servers on a storage processor. Tenants are used to enable the cost-effective management of available resources, while at the same time ensuring that tenant visibility and management is restricted to assigned resources only. Each tenant will have their own VLAN domain, routing table, IP firewall, Domain Name Service (DNS), and network namespace.
Multiple IPs per NAS server and advanced static routing
You can now associate multiple IP addresses with each NAS server in the storage system. This enables you to connect the same NFS or SMB/CIFS share to different IP networks for different purposes. For example, you could use one IP network for testing and another IP network for replication sessions.
To support having multiple IPs per NAS server, Unity now offers advanced static routing. Earlier versions of Unity handled communication from a NAS server to external services, such as LDAP and DNS, through a default gateway. Now, you can configure specific routes between NAS servers and external services to support more complex network topologies.
Events Publishing allows third-party applications to register to receive event notification and context from the storage system (NAS servers) when accessing file systems by using the SMB/CIFS or NFS protocols. The Events Publishing agent delivers to the application both event notification and associated context in one message. Context may consist of file metadata or directory metadata that is needed to decide business policy.
IP Packet Reflect
IP Packet Reflect functionality for NAS servers ensures that outbound (reply) packets always exit through the next hop gateway through which inbound (request) packets entered. Because the majority of network traffic on a NAS server (including all file system I/O) is client-initiated, the NAS server can use IP packet reflect to reply to client requests. IP packet reflect is disabled by default.
Multiprotocol now supports range locking, directory renaming, and local file support as an alternative to NIS or LDAP for UDS. Minimum allocated size for a thin file systems You can now set a minimum size for a file system. This will prevent a thin file system from shrinking below this size if auto-shrink is enabled.
Cloud Tiering Appliance (CTA) support through DHSM
CTA 11 now supports archiving from a source Unity system to CTA Cloud destinations for NFS and SMB clients using Distributed Hierarchical Storage Management (DHSM) offline file support over HTTP.
Protection and mobility enhancements
The Data Import feature allows you to a migrate data from an existing VNX (source VNX1 or VNX2) storage system to a Unity (target) storage system. This feature provides a built-in capability for file-based imports with minimal or no disruption to clients. It also provides a built-in capability for block-based imports, but cutting over of a block import session will be disruptive.
You can manually import a virtual data mover (VDM) (including all its associated filebased storage, network, and configuration information) from a VNX storage system to a Unity storage system. For a VDM import, ensure that the VNX1 OE is 188.8.131.52 or later or the VNX2 OE is 8.1.x or later.
You can manually import block LUNs, or a Consistency Group (CG) of LUNs, from a VNX storage system to a Unity system. Block import leverages the SANCopy feature on the VNX storage system to push data to the Unity system. For a LUN or CG of LUNs import, ensure that the VNX1 Block OE is 5.32.x or later or the VNX2 Block OE is 5.33.x or later.
The source and target systems involved in a data import use different file system types (UFS32 and UFS64). After an import completes successfully it is expected that the target system’s file system and related directory sizes may be different than those of the source.
Snapshots enhancements for LUNs
You can attach multiple snapshots of a LUN or LUN group to a host or group of hosts simultaneously. At the attach time, you define the set of hosts which should have access to the snapshot. When attaching a snapshot and specifying the list of hosts for I/O, you can define a read-only or read-write access type for each host. A snapshot refresh operation updates the snapshot to the current state of its base LUN or consistency group.
Block and file replication are supported between Unity 4.0 and Unity 4.1 versions. A VDM can be migrated between a 4.1.x and 4.0.1 system, but cannot be migrated to a 4.0.0 system. Note that if some 4.1 file-related features are in use on the source system, replication to a 4.0 destination system is not allowed. After replication is configured between a Unity 4.0 destination and Unity 4.1 source system, some 4.1 features cannot be enabled on the source system. These features include support for CTA 11.0, Events Publishing, Multi-protocol enhancements, and IP Multi-tenancy.
This release supports the collection and analysis of real-time metrics for system resources, LUNs, file systems, Fibre Channel ports, Ethernet ports, iSCSI interfaces, and drives. Real-time metrics display data collected during the current session, over a maximum time range of 15 minutes.
With real-time metrics charts, you can compare changes in performance across multiple metrics, such as network traffic, bandwidth, and throughput. You can also analyze data at the aggregated level using line charts, to quickly determine whether there are any performance issues.
Quality of Service Enhancements
Several enhancements have been made to host I/O limits (as known as quality of service) settings.
- Individual host I/O limit policies can be paused and resumed separately from the system-level setting, which applies to all policies globally.
- Density-based I/O limits scale with the amount of storage that is allocated to the storage resources they are applied to.
- An I/O limit policy can be configured to use burst control settings. This option allows traffic to exceed the base policy limit by a percentage of the base limit. User specified parameters determine the amount, duration, and frequency of the traffic burst.
- Historical data for a shared I/O limits policy can be exported for external processing or analysis.
CloudIQ Link and Launch
This release adds a CloudIQ button in Unity Unisphere that automatically launches the CloudIQ dashboard.