Note:  Data that is collected during this operation is not automatically forwarded to IBM. The user must contact IBM and open a problem management report (PMR) to move manually the collected data off the system. 

When the data collection process is started, a message is displayed that contains a button that links to the Tasks window. The user can click this button to view the progress of data collection. 

Important:  If data collection is started on a cluster that is in service mode, the user might not be able to check the progress of data collection. The Tasks window is not available for clusters in service mode; therefore, no link to it is included in the message. 

GLYPH<SM590000> Data Collection Limit Reached: This window opens if the maximum number of System Snapshot or TS7700 Log Collection files exists. The user can save a maximum number of 24 System Snapshot files or two TS7700 Log Collection files. If the user attempted to save more than the maximum of either type, the user is prompted to delete the oldest existing version before continuing. The name of any file to be deleted is displayed. 

Click Continue to delete the oldest files and proceed. Click Cancel  to abandon the data collection operation. 

GLYPH<SM590000> Problem Description (optional): Enter in this field a detailed description of the conditions or problem that was experienced before any data collection was started. Include symptoms and any information that can assist IBM Support in the analysis process, including the description of the preceding operation, VOLSER ID, device ID, any host error codes, any preceding messages or events, time and time zone of incident, and any PMR number (if available). The number of characters in this description cannot exceed 1000. 

## Copy Export Recovery window 

Use this window to test a Copy Export recovery, or to run an actual Copy Export recovery on the TS7700 cluster. 

Tip:  This window is visible only in a single tape-attach cluster. 

Copy Export enables the export of all virtual volumes and the virtual volume database to physical volumes, which can then be ejected and saved as part of a data retention policy for disaster recovery. The user can also use this function to test system recovery. 

For more information about the Copy Export function, see Chapter 13, “Copy Export” on page 737. Also, see IBM TS7700 Series Copy Export Function User’s Guide , WP101092. 

Reminder: The recovery cluster needs tape drives that are compatible with the exported media. Also, access to the EKs must be provided if encrypted tapes are used for export. 

Before the user attempts a Copy Export, ensure that all physical media that is used in the recovery is inserted. During a Copy Export recovery, all current virtual and physical volumes are erased from the database and virtual volumes are erased from the cache. Do not attempt a Copy Export operation on a cluster where current data is to be saved. 

