Emc IP Holding Company LLC

Martin Feeney

Douglas Eric LeCrone

Larry W McCloskey

Jeffrey L Jones

Richard Goodwill

Writing new data to a tape volume of a tape emulation unit includes determining if the new data is an update to data that was previously written, writing the new data to a new section of the tape emulation unit in response to the new data not updating data that was previously written, deleting the data that was previously written and writing the new data to a new section in response to the new data updating data that was previously written, the new data being larger than the data that was previously written, and the underlying file system not supporting variable size records/blocks, and overwriting the data that was previously written in response to the new data updating data that was previously written and either the new data not being larger than the data that was previously written or the underlying file system supporting variable size records/blocks.

Concurrent tape modification

Migrating data from a first storage device to a second storage device includes coupling a host computer to the storage devices, causing the host computer to transition from performing I/O operations with the first storage device to performing I/O operations with the second storage device by modifying metadata used for I/O operations to change a mapping of logical devices to physical devices, migrating data from the first storage device to the second storage device independently of any I/O operations by the host, and acknowledging a data write operation from the host only after the data has been successfully written to both the first storage device and the second storage device. Modifying metadata may include changing control block information in device drivers. The data may be written by the host to the second storage device only and the data may be copied from the second storage device to the first storage device.

Data migration with write back to source

Systems and procedures are provided to enable large size fixed block architecture (FBA) device support over FICON. The FBA devices may have a size greater than 2 terabytes. For example, in known storage systems, an FBA device size may be 64 terabytes and an architecture provided for 512-terabyte devices, and the described system supports such large, or even larger, FBA devices. The system may be used with existing fixed block command sets.

Large size fixed block architecture device support over FICON channel connections

Systems and procedures are provided to enable fixed block architecture (FBA) device support over fiber connections using transport mode protocol. The FBA devices may have a size greater than 2 terabytes. The system may be used with existing fixed block command sets according to the transport mode protocol. The existing fixed block command sets may be extended to permit addressing of greater than 2 terabytes. The transport mode protocol may be based on a high performance protocol implementation that facilitates processing of I/O requests.

Growing community of inventors

Medway, MA, United States of America

Martin Feeney