IBM XIV Storage System Copy Services and Migration

The XIV firmware version can also be displayed by using an XCLI command as shown inExample 8-2, where the example machine is on XIV firmware Version 10.0.1.b.Example 8-2 Displaying the XIV firmware versionxcli -m 10.0.0.1 -u admin -p adminadmin version_getVersion10.0.1.bNote that an upgrade from XIV 10.0.x.x code levels to 10.1.x.x code levels is not concurrent(meaning that the XIV is unavailable for I/O during the upgrade).8.2.2 Copy functionsThe XIV has many advanced copy and remote mirror capabilities, but for XIV volumes beingused as SVC MDisks (including image mode VDisk/MDisks), none of these functions can beused. If copy and mirror functions are needed, they should be performed using the equivalentfunctional capabilities in the SVC (such as SVC FlashCopy and SVC Metro and GlobalMirror). This is because XIV copy functions are not aware of un-destaged write cache dataresident in the SVC cache. Whereas it is possible to disable SVC write-cache (when creatingVDisks), this method is not supported by IBM for VDisks resident on XIV.8.2.3 TPC with XIV and SVCXIV code levels 10.1.0.a and later support the use of Tivoli Storage Productivity Center (TPC)via an embedded SMI-S agent in the XIV. Subsequently, if you want to use TPC in conjunctionwith XIV then you your XIV must be code level 10.1.0.a (or later). TPC itself must be Version4.1 (or later). Refer to the “Recommended Software Levels for SAN Volume Controller”documentation for your SVC code level to identify the latest recommended TPC for Disksoftware version via the following Web site:http://www.ibm.com/storage/support/21458.3 Zoning setupOne of the first tasks when implementing XIV is to add the XIV to the SAN fabric so that theSVC cluster can communicate with the XIV over the Fibre Channel. The XIV can have up to24 Fibre Channel host ports. Each XIV reports a single World Wide Node Name (WWNN)that is the same for every XIV Fibre Channel host port. Each port also has a unique andpersistent World Wide Port Name (WWPN), which means that we can potentially zone 24unique WWPNS from an XIV to an SVC cluster. However, the current SVC firmware has arequirement that one SVC cluster cannot detect more than 16 WWPNs per WWNN, so at thistime there is no value in zoning more than 16 ports to the SVC. Because the XIV can have upto six interface modules with four ports per module, it is better to use just two ports on eachmodule (allowing up to 12 ports total).Chapter 8. SVC migration with XIV 245