Browse Prior Art Database

Emergency Failsafe Shutdown and Data Preservation

IP.com Disclosure Number: IPCOM000015788D
Original Publication Date: 2002-Mar-31
Included in the Prior Art Database: 2003-Jun-21
Document File: 1 page(s) / 39K

Publishing Venue

IBM

Abstract

During an emergency situation a network interrupt would be generated externally by the safety system. This interrupt would cause a message to be broadcast to all terminals and storage systems in the affected building(s). The terminals would assume a locked state, to prevent further input, and a message would be posted to the screen stating, "Evacuate the Building in an Orderly Manner" or other suitable message alerting both users and operators. In addition, the message to the storage system would invoke either (a) JCL (Job Control Language) or (b) a backup macro, resulting in a remote copy type of job to be initiated for those files changed since the last backup. This remote copy could be a synchronous Peer-to-Peer Remote Copy (PPRC) or an asynchronous Extended Remote Copy (XRC). Either way, by locking input to the PC and preventing further input, there will be no further changes to the material being backed-up. In view of the fact that an emergency has been declared, time is of the essence and it is essential to perform the backup as quickly as possible. Thus, by preventing further input by the user, the user is evacuated safely and the backup proceeds at the fastest speed possible because the backup process is not encumbered by ongoing changes to the material. By locking all terminals, the full bandwidth of the fibre-channel or local area network is available for backup. The primary purpose of this backup is to backup data files, not the applications which generated those data files. The applications can always be obtained from the manufacturer. However, the data files are what is key to restoring the business. After a time of T seconds, power hungry CRT (Cathode Ray Tube) screens and other screens such as LCDs (Liquid Crystal Displays) would be turned off. This would conserve battery backup power for the PCs and servers. Once a PC and/or server had been fully backed up, that PC/server would be shut down. This would preserver whatever remaining power there was for the remaining systems to finish the backup process.

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

Page 1 of 1

Emergency Failsafe Shutdown and Data Preservation

    During an emergency situation a network interrupt would be generated externally by the safety system. This interrupt would cause a message to be broadcast to all terminals and storage systems in the affected building(s). The terminals would assume a locked state, to prevent further input, and a message would be posted to the screen stating, "Evacuate the Building in an Orderly Manner" or other suitable message alerting both users and operators. In addition, the message to the storage system would invoke either (a) JCL (Job Control Language) or (b) a backup macro, resulting in a remote copy type of job to be initiated for those files changed since the last backup.

This remote copy could be a synchronous Peer-to-Peer Remote Copy (PPRC) or an asynchronous Extended Remote Copy (XRC). Either way, by locking input to the PC and preventing further input, there will be no further changes to the material being backed-up. In view of the fact that an emergency has been declared, time is of the essence and it is essential to perform the backup as quickly as possible. Thus, by preventing further input by the user, the user is evacuated safely and the backup proceeds at the fastest speed possible because the backup process is not encumbered by ongoing changes to the material. By locking all terminals, the full bandwidth of the fibre-channel or local area network is available for backup.

The primary purpose of this backup is to...