c5

Revised:  April 07, 2004.



Revised:  April 20, 2004.



2a33


27,230c228,248

Rich set of business continuance solutions

The ESS Model 750 supports a rich set of copy service functions and
management tools that can be used to build solutions to help meet
business continuance requirements.

IBM TotalStorage Resiliency Family

The IBM Total Storage Resiliency Family is comprised of IBM
TotalStorage Resiliency Core Technology, an extensive set
of hardware and software features and products, and IBM
TotalStorage Resiliency Automation, integrated software
and services packages. The IBM TotalStorage Resiliency
Family is designed to help you implement storage
infrastructures to help keep your business running 24
hours a day, 7 days a week.

The following ESS Model 750 functions are key components of
the IBM TotalStorage Resiliency Core Technology:


  • FlashCopy
  • PPRC:

    • PPRC Metro Mirror (Synchronous PPRC)
    • PPRC Global Mirror (Asynchronous PPRC)
    • PPRC Metro/Global Copy (Asynchronous Cascading PPRC)
    • PPRC Global Copy (PPRC Extended Distance)



38c256
with support for the following additional functions:
with the following additional functions:

42a261

  • FlashCopy to a PPRC primary

    65,278c284,296
    volume involved in a FlashCopy relationship. With Incremental FlashCopy,
    the initial relationship between a source and target is maintained. When
    a subsequent FlashCopy establish is initiated, only the data required to
    bring the target current to the source's newly established point-in-time
    is copied. Incremental FlashCopy can help reduce the background copy
    completion time when only a subset of data on either the source or target
    has changed, giving you the option to perform a FlashCopy on a more
    frequent basis.

    The direction of the "refresh" can also be reversed, in which case the
    LUN or volume previously defined as the target becomes the source for the
    LUN or volume previously defined as the source (and is now the target).
    Again, only the data required to bring the target current to the source's
    point-in-time is copied. If no updates were made to the target since the
    last "refresh", the direction change could be used to "restore" the
    volume involved in a FlashCopy relationship. When a subsequent FlashCopy
    establish is initiated, only the data required to bring the target
    current to the source's newly established point-in-time is copied. The
    direction of the "refresh" can also be reversed, in which
    case the LUN or volume previously defined as the target
    becomes the source for the LUN or volume previously defined
    as the source (and is now the target). Incremental
    FlashCopy can help reduce the background copy completion
    time when only a subset of data on either the source or
    target has changed, giving you the option to perform a
    FlashCopy on a more frequent basis. Additionally, if no
    updates were made to the target since the last "refresh",
    the direction change could be used to "restore" the


    79a298,302

    FlashCopy to a PPRC primary lets you establish a
    FlashCopy relationship where the FlashCopy target is also
    a PPRC primary volume. This enables you to create full
    or incremental point-in-time copies at a local site and
    then use PPRC to copy the data to the remote site.


    07,313c330,341

    PPRC is a hardware-based disaster recovery solution
    designed to provide real-time mirroring of logical volumes within an ESS
    or between two ESSs that can be located up to 103 km from each other.
    PPRC is a synchronous copy solution where write operations are completed
    on both copies (primary and secondary ESS) before they are considered to
    be done. PPRC also includes PPRC Extended Distance (PPRC-XD), a
    non-synchronous long-distance copy option for data migration and backup.

    Peer to Peer Remote Copy (PPRC)
    is designed to offer hardware-based remote copy solutions.
    Synchronous PPRC (PPRC Metro Mirro) is designed to provide
    real-time mirroring of logical volumes between two ESSs
    that can be located up to 103 km from each other when
    using ESCON communication links and up to 300 km when
    using Fibre Channel communication links. It is a
    synchronous copy solution where write operations are
    completed on both copies (local and remote site) before
    they are considered to be done. PPRC also includes PPRC
    Extended Distance (PPRC Global Copy), a non-synchronous
    long-distance copy option for data migration and backup.


    15,316c343,344

    PPRC Version 2 further supports business continuance solutions with
    support for the following additional functions:

    PPRC Version 2 further supports business continuance
    solutions with following additional functions:


    19c347,348
  • Asynchronous Cascading PPRC
  • Asynchronous PPRC (PPRC Global Mirror)
  • Asynchronous Cascading PPRC (PPRC Metro/Global Copy)

    32,360c361,413

    Asynchronous Cascading PPRC provides a long-distance remote copy
    solution for zSeries and open systems environments by allowing a PPRC
    secondary volume (involved in a PPRC synchronous relationship) to also
    simultaneously serve as a PPRC primary volume in a PPRC-XD relationship
    to the remote site. This capability enables the creation of three-site
    or two-site Asynchronous Cascading PPRC configurations.

    In a three-site configuration, the synchronous PPRC relationship is
    maintained between an ESS at the local site and an ESS at an intermediate
    site (located within 103 km of the local site). A PPRC-XD relationship
    is simultaneously maintained between the ESS at the intermediate site and
    an ESS at the remote site. The remote site can be located at distances
    well beyond 103 km from the intermediate site -- with the distance
    typically limited only by the capabilities of the network and channel
    extension technologies. When used with specific operational procedures,
    a three-site configuration can be designed to provide a data protection
    solution in the event of an unplanned outage at any one of the three
    sites. Alternatively, operational procedures, including the creation of
    a "safety copy" at the remote site using FlashCopy, can be used to design
    a solution that provides a consistent copy of the data at the remote site
    in the event of a regional outage affecting both the local and
    intermediate site.

    In a two-site configuration, the synchronous PPRC relationship is
    maintained between two ESSs, both of which are located at the local site,
    or within a single ESS. A PPRC-XD relationship is simultaneously
    maintained to an ESS at the remote site, which can be located at long
    distances from the local site. With operational procedures, including
    the creation of a "safety copy" at the remote site using FlashCopy,
    solutions can be designed providing a consistent copy of the data at the
    remote site in the event of an outage at the local site.

    PPRC Global Mirror is designed to provides a long-distance
    remote copy solution across two sites using asynchronous
    technology. It operates over high-speed, Fibre Channel
    communication links and is designed to provide the following:


    • Support for virtually unlimited distance between the
      local and remote sites, with the distance typically limited
      only by the capabilities of the network and channel
      extension technologies. This can better enable you to
      choose your remote site location based on business needs
      and enables site separation to add protection from
      localized disasters.

    • A consistent and restartable copy of the data at the
      remote site, created with minimal impact to applications
      at the local site. Compared to Asynchronous Cascading
      PPRC (PPRC Metro/Global Copy), PPRC Global Mirror eliminates
      the requirement to do a manual and periodic suspend at the
      local site order to create a consistent and restartable copy
      at the remote site.

    • Data currency where, for many environments, the remote
      site lags behind the local site an average of 3 to 5 seconds,
      minimizing the amount of data exposure in the event of an
      unplanned outage. Data currency is also known as the
      recovery point objective (RPO). The actual lag in data
      currency experienced will depend upon a number of factors,
      including specific workload characteristics and bandwidth
      between the local and remote sites.

    • Dynamic selection of the desired RPO based upon business
      requirements and optimization of available bandwidth.

    • Session support whereby data consistency at the remote
      site is internally managed across up to eight ESS machines
      located among the local and remote sites.

    • Efficient synchronization of the local and remote sites
      with support for PPRC failover and failback modes, helping
      to reduce the time required to switch back to the local

    PPRC Metro/Global Copy is designed to provide a
    long-distance remote copy solution across three sites
    using a combination of PPRC Metro Mirror and PPRC Global
    Copy. In a three-site configuration, the PPRC Metro Mirro
    is maintained between an ESS at the local site and an ESS
    at an intermediate site, while a PPRC Global Copy
    relationship is simultaneously maintained between the ESS
    at the intermediate site and an ESS at the remote site.
    When used with specific operational procedures, this can
    be designed to provide a data protection solution in the
    event of an unplanned outage at any one of the three sites.
    Alternatively, operational procedures, including the creation
    of a "safety copy" at the remote site using FlashCopy, can
    be used to design a solution that provides a consistent
    copy of the data at the remote site in the event of a
    regional outage affecting both the local and intermediate
    site.


    65,368d417

    Concurrent Copy offers another method for creating a
    point-in-copy in zSeries and S/390 environments, with the source data
    fully available for access and update after initiation of the copy
    operation.


    90a740,776

    Calculating physical and effective capacity

    Refer to the IBM TotalStorage Enterprise Storage Server
    Introduction and Planning Guide (GC26-7444) for capacity
    calculation guidelines.

    ESS Advanced functions

    Advanced functions are enabled and authorized based upon
    the physical capacity of the ESS:


    • FlashCopy and FlashCopy Version 2

      • Enablement and authorization must be equal to or greater
        than the total physical capacity of the ESS.

    • PPRC and PPRC Version 2

      • Enablement and authorization must be equal to or greater
        than the total physical capacity of the ESS.

    • PAV:

      • Enablement and authorization must be equal to or greater
        than the physical capacity within the ESS that will be
        logically configured as Count Key Data (CKD) volumes for
        use with zSeries and S/390 servers.


    Refer to the IBM TotalStorage Enterprise Storage Server
    Introduction and Planning Guide (GC26-7444) for physical
    capacity calculation guidelines.
    Refer to the IBM TotalStorage Enterprise Storage Server
    Introduction and Planning Guide (GC26-7444) for physical
    capacity calculation guidelines.

    Standby CoD Disk Eight-Packs can be excluded from the
    physical capacity calculation when the Standby CoD
    Indicator (feature number 9510) is present on the machine.

    Refer to "Ordering ESS Advanced Functions" at the end
    of the Special Features section for ordering instructions.


    33a820,882

    PPRC

    PPRC must be purchased for both the primary and secondary
    ESS. In three-machine Asynchronous Cascading PPRC (PPRC
    Metro/Global Copy) configurations, PPRC must also be
    purchased for the intermediate ESS.

    PPRC requires the installation of at least one Fibre
    Channel/FICON or ESCON host adapter on each ESS in the
    PPRC configuration to serve as the PPRC communications
    link. For higher availability, IBM recommends that more
    than one host adapter per ESS be used for the PPRC
    connectivity.

    PPRC is supported with the use of SAN fabric products,
    ESCON directors, Dense Wavelength Division Multiplexing
    (DWDM) products, and channel extenders. A current list
    of supported environments, configurations, networks, and
    products is available at:


    http://www.ibm.com/storage/hardsoft/products/ess/supserver.htm

    Vendors should be consulted regarding hardware and software
    prerequisites when using their products in an ESS PPRC
    configuration. IBM is not responsible for third-party products.

    When using channel extender products with PPRC, the
    channel extender vendor will determine the maximum
    distance supported between the primary and secondary ESS.
    The vendors should be contacted for their distance
    capability, line quality requirements, and WAN attachment
    capabilities.

    PPRC over Fibre Channel: PPRC over Fibre Channel
    communication links has the following additional prerequisites:


    • PPRC Version 2
    • Fibre Channel/FICON Host Adapter (feature #3024 or #3025)

    Asynchronous PPRC (PPRC Global Mirror): PPRC
    Global Mirror has the following additional prerequisites:


    • ESS LIC level 2.4.0, or later
    • PPRC Version 2
    • Fibre Channel communications link
    • FlashCopy Version 2 on the secondary ESS. If PPRC Global

    Mirror will be used during failback from the secondary ESS
    machine(s), FlashCopy Version 2 must also be enabled on the
    primary machine(s).

    In the event of a planned or unplanned outage, recovery
    procedures are required to achieve a consistent and
    restartable copy of the data at the remote site. Scripts
    and software can be used to help automate these procedures.

    PPRC Global Mirror is not supported in Asynchronous
    Cascading PPRC (PPRC Metro/Global Copy) configurations
    as an alternative to the PPRC-XD (PPRC Global Copy)
    relationship to the remote site.

    Asynchronous Cascading PPRC (PPRC Metro/Global
    Copy):
    PPRC Metro/Global Copy has the following
    additional prerequisites:


    • PPRC Version 2

    PPRC Global Mirror is not supported in Asynchronous
    Cascading PPRC (PPRC Metro/Global Copy) configurations
    as an alternative to the PPRC-XD (PPRC Global Copy)
    relationship to the remote site.


    42,743c891
    750. This PTF is planned for availability by May 28, 2004. Refer to the
    IBM TotalStorage Expert V2.1 Fixes entries at:
    750. Refer to the IBM TotalStorage Expert V2.1 Fixes entries at:

    47a896,902

    DFSMS support for the FlashCopy Version 2 and PPRC
    Version 2 enhancements will vary depending upon the
    enhancement. z/OS and OS/390 PTFs are required to provide
    DFSMS support for Data Set FlashCopy, Multiple Relationship
    FlashCopy, and elimination of the LSS constraint. The IBM
    Support Center should be contacted for the current PTF
    information.


    32a1088
    - Standby CoD Indicator 9510

    33a1090
    - Flexible Capacity Indicator 9610

    54a1112
    PPRC Global Mirror Indicator 9912

    163a1322,1359

    (#9510) Standby CoD Indicator


    This feature is used to identify machines participating in
    the ESS Standby CoD program. It is for administrative purposes
    only.

    When this feature is present, advanced function licenses can be
    purchased based upon the machine's physical capacity excluding
    Standby CoD Disk Eight-Pack features (#213x).

    When the machine exits the Standby CoD program, the Standby CoD
    Indicator feature must be replaced with the Flexible Capacity
    Indicator feature (#9610) using the feature removal and add option.
    A machine exits the Standby CoD program when all Standby CoD Disk
    Eight-Pack features (#213x) are converted to Disk Eight-Pack
    features (#212x).

    Current Standby CoD customers that add the Standby CoD Indicator
    feature to the machine are required to sign new versions of the
    agreements if their current agreements are dated prior to April 2004.
    Additional information on requirement agreements is available on the
    following sites (search the site on "Standby CoD"):



    • Minimum: None.
    • Maximum: One.
    • Prerequisites: Standby CoD Flexible Capacity Option (#9500).
    • Corequisites: None.
    • Compatibility Conflicts: Not compatible with Flexible
      Capacity Option (#9600) or Flexible Capacity Indicator (#9610).
    • Limitations: None.
    • Plant Install / Field Install: Both.


    177a1374,1393

    (#9610) Flexible Capacity Indicator


    This feature designates a machine that previously ordered the
    Standby CoD Indicator feature (#9510) and is no longer participating in
    the Standby CoD program. This feature is for administrative and
    tracking purposes only.

    If the machine re-enters the Standby CoD program, the Flexible
    Capacity Indicator feature must be replaced with the Standby CoD
    Indicator feature (#9510) using the feature removal and add option. A
    machine re-enters the Standby CoD program when Standby CoD Disk
    Eight-Pack features (#213x) are ordered.


    • Minimum: None.
    • Maximum: One.
    • Prerequisites: Flexible Capacity Option (#9600).
    • Corequisites: None.
    • Compatibility Conflicts: Not compatible with Standby CoD Flexible
      Capacity Option (#9500) or Standby CoD Indicator (#9510).
    • Limitations: None.
    • Plant Install / Field Install: Both.


    391a1608,1621

    (#9912) PPRC Global Mirror Indicator


    This specify feature must be selected if the ESS will be used in
    a PPRC Global Mirror (Asynchronous PPRC) configuration as either a
    primary or secondary machine. It is for administrative purposes only
    and does not affect the technical capabilities of the ESS.


    • Minimum: None.
    • Maximum: One.
    • Prerequisites: ESS LIC level 2.4.0, or later.
    • Corequisites: PPRC Version 2 (#85xx)
    • Compatibility Conflicts: Not compatible with PPRC (#83xx).
    • Limitations: None.
    • Plant Install / Field Install: Both.