E07 only Default Yes or no JB in E06 format and  JB/JC/JK in E07 format E07 JB/JC/JK in E07 format E06 JB in E06 format E06 only Default Yes or no JA/JJ/JB in E05/E06 format E05 only Default Yes or no JA/JJ in J1A format and  JA/JJ/JB in E05 format J1A only Default Yes or no JA/JJ in J1A format Installed tape  drives Export format of  copy export pool LMTDBPVL  enabled? Exportable physical volumes 13.1.4 Copy Export grid considerations Copy Export is supported in grid and stand-alone environments. In this section, we review  several considerations that are unique to the grid environment. Performing Copy Export The first consideration relates to performing Copy Export. In a grid configuration, a Copy  Export operation is performed against an individual TS7700, not across all TS7700 clusters.  Set up Copy Export in a grid plan that is based on the following guidelines: GLYPH<SM590000> Decide which TS7700 in a grid configuration is going to be used to export a specific set of  data. Although you can set up more than one TS7700 to export data, only the data from a  single source TS7700 can be used in the recovery process. A service offering called Copy  Export Merge is available, but you cannot merge copy-exported volumes from more than  one source TS7700 in the recovery TS7700. GLYPH<SM590000> Define an MC name for each specific set of data to export. On the TS7700 that is used to  export that data, define a secondary physical volume pool for that MC name and ensure  that you indicate that it is an export pool. Although you must define the MC name on all  TS7700s in the grid configuration, specify only the secondary physical volume pool on the  one TS7700 that is to perform the export operation.  Specifying it on the other TS7700s in the grid configuration does not interfere with the  Copy Export operation, but it is a waste of physical volumes. The exceptional useful case  of this approach is if you want one of the TS7700s in the grid configuration to include a  secondary copy of the data in case the primary copies on other TS7700s are inaccessible. GLYPH<SM590000> While you are defining the MC name for the data, ensure that the TS7700 to perform the  Copy Export operation includes a copy policy that specifies that it is to have a copy. GLYPH<SM590000> If a logical volume is to be copied to the TS7700 that is performing the Copy Export  operation and that copy did not yet complete when the export is started, it is not included  in the current export operation. GLYPH<SM590000> When the Copy Export operation is run, the export list volume must be valid on only the  TS7700 that is performing the operation. You must define a unique MC name to be used  for the export list volume. For that MC name, you must define its copy policy so that a copy  is on only the TS7700 that is to perform the export operation. If the VOLSER that is  specified for the export list volume when the export operation is started is on more than  one TS7700, the Copy Export operation fails. Chapter 13. Copy Export  743