A volume copy is different from a snapshot because a snapshot creates a point in time copy'
that is a child device of the original source volume, whereas a volume copy is a point in time
copy that is independent of its source volume. This effectively makes it similar to a traditional
volume copy, but combined with the sophisticated use of metadata that is found in XIV.
Volume copy’s main advantage over a snapshot is that it is independent and is not at risk of
being automatically deleted if pool space becomes constrained. A volume copy target can
also be in a different pool than the source. However, for temporary copies of data with low
change rates, a volume copy will most likely be less capacity efficient than using the XIV
snapshot function. This is because it effectively duplicates all the data from the source volume
at the time it is created.
IBM storage, flash system, 5000: low, 7000 medium, 9000 high end to replace old V5000, V7000 (virtualized, software-defined storage system designed to consolidate workloads into a single storage system )
Admin SAN: spectrum control on-premise(charge), can manage a lot of SAN.
how about 3 x Site with HA and DR solution for Oralce, DB2, sybase using SAN ?
more on topology and architecture design point of view, quick start.
usally what a person will ask you if he/she want to hire you as SAN administrator is welcome.