Using WAN optimization gizmos eg Riverbed is


  1. VMware vSphere Virtual Amounts (vVols) commonly supported in the a good DRP;
  2. A quantity into the a beneficial DRP can’t be shrunk;
  3. No volume disperse anywhere between I/O organizations if the volume inside the a DRP (explore FlashCopy otherwise Town Mirror/Around the globe Echo as an alternative);
  4. No split up away from a volume mirror to reproduce for the another I/O group;
  5. Real/used/free/free/tier potential commonly said for each and every frequency – simply each pond.

RAID and you can Marketed RAID FlashSystem 7200 systems support DRAID1, DRAID5, DRAID6, TRAID0, TRAID1 and TRAID10. For compressed drives only DRAID1, DRAID5 and DRAID6 are supported.

DRAID Remove Proportions For candidate drives, with a capacity greater than 4TB, a strip size of 128 cannot be specified for either RAID-5 or RAID-6 DRAID arrays. For these drives a strip size of 256 should be used.

Non-Disruptive Regularity Disperse (NDVM) The following Fibre Channel attached host types are supported for non-disruptively moving a volume between I/O groups (control enclosures):

Whenever swinging an amount that’s mapped in order to an environment class then you definitely have to rescan disk pathways towards all of the server group nodes to ensure the brand new paths were identified in advance of removing availability from the brand-new I/O group.


Clustered Assistance A FlashSystem 7200 system requires native Fibre Channel SAN or alternatively 16Gbps/32Gbps Direct Attach Fibre Channel connectivity for communication between all nodes in the local cluster. Clustering can also be accomplished with 25Gbps Ethernet, for standard topologies. For HyperSwap topologies a SCORE request will be required. Please contact your IBM representative to raise a SCORE request.

Partnerships anywhere between possibilities to own Metro Echo or Around the world Mirror replication is be taken having each other Fiber Route and Native Ethernet associations. Ranges higher than 300 yards are merely offered while using an FCIP hook up or Fibre Station between supply and target.

Clear Cloud Tiering Transparent cloud tiering on the system is defined by configuration limitations and rules. Please see the IBM Documentation maximum limits page for details.

  1. Whenever an affect account is generated, it must continue to use an equivalent security form of, on longevity of the content where cloud membership – even if the affect account object is removed and remade on the computer, the latest encoding kind of for this affect account may possibly not be altered while back up data for that system is present about cloud seller.
  2. When performing lso are-secret surgery to the a system who’s a security enabled cloud membership, carry out the to visit procedure once brand new ready yourself operation. Ensure that you take care of the past program master key (into the USB or perhaps in Keyserver) because this secret might still be needed in order to recover their affect content study when doing a Miami, FL in USA women T4 recuperation otherwise a significance.
  3. Restore_uid choice really should not be used whenever duplicate is imported in order to an alternative group.
  4. Import off TCT info is simply supported out-of possibilities whoever backup data was made during the v7.8.0.step one.
  5. Transparent affect tiering spends Sig V2, when hooking up so you can Amazon countries, and won’t currently service nations which need Sig V4.

Security and you may TCT There is an extremely small possibility that, on a system using both Encryption and Transparent Cloud Tiering, the system can enter a state where an encryption re-key operation is stuck in ‘prepared’ or ‘prepare_failed’ state, and a cloud account is stuck in ‘offline’ state. The user will be unable to cancel or commit the encryption rekey, because the cloud account is offline. The user will be unable to remove the cloud account because an encryption rekey is in progress. The system can only be recovered from this state using a T4 Recovery procedure. It is also possible that SAS-attached storage arrays go offline. There are two possible scenarios where this can happen: