Removing sessions

Edit online

How to remove sessions.

About this task

Important: Starting with the 6.3.9.0 release, you can remove sessions while they are in any state. Initiating the Remove Session command during an active session clears the server's memory of any established relationships, yet it leaves the storage system and any connections to z/OS unaffected. Therefore, all relationships, hardware consistency groups, and z/OS HyperSwap configurations remain to run on the storage system or z/OS System.

Complete these steps to remove a session:

Procedure

  1. In the menu bar, click Sessions.
  2. On the Sessions page, select the session that you want to remove.
  3. From the Session Actions list, select Remove Session.
  4. Click Yes to confirm that you want to remove the session.
    Note: For sessions with an active HyperSwap Configuration. For z/OS sessions loaded with HyperSwap or Hardened Freeze configurations, ensure "Manage with HyperSwap" is unchecked in the session properties before deletion. Unchecking this option eliminates the configuration on the z/OS System. If "Manage with HyperSwap" remains checked, HyperSwap stays active and could require a restart of the HyperSwap address space to remove the configuration.
    Note: For sessions with active DS8000 Global Mirror relationships. Upon removing the active session, the Global Mirror session remains on the DS8000 and continues to create consistency groups. To merge an existing Global Mirror session on the hardware into another session, align the Consistency Group name with the session ID on the DS8000. When the new session is started, it sees that the consistency group name matches the hardware and assimilates the relationships.
    Note: For sessions with Safeguarded Copy backups or Safeguarded Snapshots. Upon removing the session, all Safeguarded Copy backup and Safeguarded Snapshots remain on the hardware. For DS8000 Safeguarded Copy backups, the server no longer recognizes any backups and does not process retention times. To clean up the backups, the volumes need to be assimilated into another Copy Services Manager Safeguarded Copy session or by a GDPS configuration.
    Note: For sessions with Spectrum Virtualize / FlashSystems Metro Mirror, Global Mirror or FlashCopy consistency groups. Upon removing the session, all consistency groups remain on the storage system. To assimilate remote copy consistency groups back into a Copy Services Manager session, remove the consistency group on the storage system so that the pairs become stand alone pairs, and then start the Copy Services Manager session which will create a new consistency group on the hardware to manage the pairs. For FlashCopy consistency groups, leave the pairs in the hardware consistency group, create the CSM session with the same name as the consistency group, and then issue the Discover command to discover the existing consistency group and relationships.