Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Method and System for Facilitating Availability of Deleted Data Blocks using Secured Fast Replication Mechanism

IP.com Disclosure Number: IPCOM000244144D
Publication Date: 2015-Nov-13
Document File: 8 page(s) / 309K

Publishing Venue

The IP.com Prior Art Database

Abstract

A method and system is disclosed for facilitating availability of deleted data blocks using secured fast replication mechanism.

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

Page 01 of 8

Method and System for Facilitating Availability of Deleted Data Blocks using Secured Fast Replication Mechanism

A data set without scratch on erase process (overwriting the used data blocks with zeroes), after deleting sensitive information from a volume, makes the data still accessible on free space tracks. If a user performs print block/track of the free space, the sensitive data can also be read by an unauthorized user. A subsequent allocation of a data set may

contain the blocks/tracks assigned for user data. A print of the blocks/tracks before the user writes to the newly allocated blocks results in vulnerability of the data in the blocks/tracks.

Disclosed is a method and system for facilitating availability of deleted data blocks using secured fast replication mechanism. The method and system provide data security at the track/block level without compromising performance.

In accordance with the method and system, as shown in figure 1 and figure 2, when a data set is deleted, the extents of deleted data set are established and the track/block list is maintained / tracked in a side file in cache storage using flash copy technology. A single image track/block is simultaneously maintained that contains zeroed out records. Subsequently, when the extents are established, the deleted extents are free to be returned to the free space extents list for the volume. Any subsequent READ from a track/block that is established for a marked deletion (track/block list maintained in cache storage) is presented as the zeroed-out image rather than on-disk track/block. Further, while a

WRITE occurs to a track/block that is marked for deletion list in the side file, that track/block's entry is removed from the track list since the write overwrites previously marked track/block with sensitive information. The solution allows the extents to be made quickly available for allocation without having to ze...