Fujitsu ETERNUS DX S5 Series Design Manual page 118

2. Basic Functions
Backup (Advanced Copy)
¡: Possible, ´: Not possible
*1: This combination is supported only if the copy size in both the copy source volume and the copy destination volume is less than
2TB.
If the copy size is 2TB or larger, perform the following operations instead.
• When performing a temporary recovery
Use a Cascade Copy of QuickOPC (copy session 1) and OPC (copy session 2).
• When backing up two generations
Use a multi-copy that is configured with QuickOPC and QuickOPC.
*2: When copy session 1 uses the REC Consistency mode, the data transmission sequence of copy session 1 is guaranteed, but the data
transmission sequence of copy session 2 is not guaranteed.
Caution
• A Cascade Copy can be performed when the copy type for copy session 1 is XCOPY or ODX. The copy
destination area for XCOPY or ODX and the copy source area for copy session 2 do not have to be
completely identical. For example, a Cascade Copy can be performed when the copy source area for
copy session 2 is only part of the copy destination area for copy session 1.
XCOPY or ODX cannot be set as the copy type for copy session 2 in a Cascade Copy.
• For more details on XCOPY and ODX, refer to
• To acquire valid backup data in the copy destination for copy session 2, a physical copy must be
completed or suspended in all of the copy sessions that configure the Cascade Copy. Check the copy
status for copy sessions 1 and 2 when using the backup data.
However, if a Cascade Copy performs session 1 before session 2, and copy session 1 is an OPC or
QuickOPC session and copy session 2 is an OPC, QuickOPC, SnapOPC, or SnapOPC+ session, the data
in the copy destination for copy session 2 is available even during a physical copy.
• If copy session 1 is an EC or REC session and copy session 2 is an OPC, QuickOPC, SnapOPC, or
SnapOPC+ session, setting copy session 2 after setting copy session 1 to an equivalent or suspended
state is recommended.
• When stopping an OPC or QuickOPC session for copy session 1 during a physical copy, stop copy
session 2 in advance if copy session 2 is an OPC, QuickOPC, SnapOPC, or SnapOPC+ session.
• If copy session 2 is an EC or REC session, copy session 2 does not transition to an equivalent state
until the physical copy for copy session 1 is complete. For an EC session, a copy session cannot be
suspended until the session transitions to an equivalent state.
"Server Linkage Functions" (page
118
149).
Design Guide