In some ways the USP works like a standard storage subsystem. The virtualisation mapping is effectively in the controller, but the USP does not introduce a new file space, it simply directs IOs to the correct place in the storage it manages. The big difference between the USP and other subsystems is that while it has an internal capacity of up to 332TB, it can also attach external storage devices, including non-HDS devices, giving a total internal and external capacity up to 32PB aggregated into a single virtual storage pool.
At present, the internal storage is all considered 'top-tier' while the external storage can be grouped into lower tiers. Later this year it will be possible to install SATA disk inside the subsystem. This storage can be configured as up to 16,384 LUNs
All the storage is treated equally as far as migration, copying and mirroring operations are concerned. The USP uses HDS Shadowimage for instant copy, and copy can take place between different storage tier devices. Remote mirroring must be between The USP controllers, but the data can be directed to any physical storage at the back end.
The USP manual states 'The HDS strategy is to provide automatic policy based data movement over time in line with access and retention value considerations'. This implies that the USP does not have HSM functionality yet.
The USP does have an optional facility for e-mail archiving and e-mail fixed content storage.
The USP supports a full range of operating systems including z/OS mainframe data. Specifically, mainframe data can be mapped to external SATA disks.
In storage hardware terms it supports IBM, EMC, SUN, ESS and DS4000, EMC symmetrix 8000, DMX series and Clariion CX Series.
Open Systems servers can be attached directly, or connected to the USP via a SAN, mainframe servers are attached through ESCON of FICON ports. A USP can be split into up to 32 virtual subsystems, each of which is isolated from the others and so resilient.