Browse Prior Art Database

Piggybacked Command Monitoring

IP.com Disclosure Number: IPCOM000249320D
Publication Date: 2017-Feb-16
Document File: 1 page(s) / 66K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a method to use a separate command that piggybacks on the current initiating task to enable a user to monitor an active long lasting task from a separate window.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 57% of the total text.

1

Piggybacked Command Monitoring

A Disaster Recovery (DR) solution using a controller system (KSYS) node involves a number of actions including:

1. Discovery - where all the Logical Partitions (LPARs) aka Virtual Machines (VMs), Virtual Input/Output Servers (VIOSes), Hosts(aka CECs), Hardware Management consoles (HMCs), and the storage are discovered for both the primary and backup sites

2. Verification - where the data captured during discovery is validated to ensure the user has correct access, right storage in the backup site, etc.

3. Move - where the VMs from the primary site move to the backup site, and 4. Recovery - in case of errors encountered during a move; hence, the need to

perform error handling and recovery

The four above actions are long lasting actions (LLA); execution can take anywhere from several minutes to hours based on the configuration. The command that usually initiates the action can report the progress and the completion with either success or failure. This command usually communicates with the KSYS daemon to initiate the action and determine the progress. However, if this command is killed, then there is no easy way for the user to know the status, progress, or completion of the issued command. In addition, a user might need to monitor the disaster recovery action from a separate computer after telneting to the KSYS node in a separate window.

This disclosure proposes a mechanism wherein a separate command piggybacks the monitoring of an active long...