Loading patent…
AssigneeInternational Business Machines Corporation
InventorsJustin Paul Eastman, Jeffrey Richard Suarez, Andrew Nelson Wilt
Estimating the term…
An apparatus, system, and method are disclosed for copying data. The present invention includes a data storage subsystem that supports fast replication and a host system that communicates a fast replication request to the data storage subsystem, estimates an expected wait time for a pending fast replication operation if the fast replication request is not granted, awaits the expiration of the wait time, communicates an additional fast replication request to the data storage subsystem, and records the data as moved if the additional fast replication is granted. In certain embodiments, the host system moves the data via conventional I/O operations if the expected wait time exceeds an expected duration for the conventional I/O operations.
A system for copying data, the system comprising:
An apparatus for copying data, the apparatus comprising:
A computer readable storage medium tangibly embodying a program of machine-readable instructions executable by a digital processing apparatus to perform operations for copying data, the operations comprising:
A method for copying data, the method comprising:
Dependencies are inferred from the claim text.
Drawings are temporarily unavailable. Open the PDF at USPTO
From the US filing history. Foreign family members aren’t listed.
In which an application is distributed across nodes in the network: replication or mirroring of data, e.g. scheduling or transport for data…
Improving I/O performance: in relation to throughput
Horizontal data movement in storage systems, i.e. moving data in between storage devices or systems: replication mechanisms
Vertical data movement, i.e. input-output transfer; data movement between one or more hosts and one or more storage devices: command handling…
About 2 months of term left · ends 20 Dec 2026 (estimated)
1. Field of the Invention
This invention relates to systems, apparatus, and methods for managing data and more particularly relates to systems, apparatus, and methods for copying data.
2. Description of the Related Art
In order that the advantages of the invention will be readily understood, a more particular description of the invention briefly described above will be rendered by reference to specific embodiments that are illustrated in the appended drawings. Understanding that these drawings depict only typical embodiments of the invention and are not therefore to be considered to be limiting of its scope, the invention will be described and explained with additional specificity and detail through the use of the accompanying drawings, in which:
FIG. 1 is a schematic block diagram of one embodiment of data copy system in accordance with the present invention;
FIG. 2 is a schematic block diagram of one embodiment of a host system in accordance with the present invention;
Many of the functional units described in this specification have been labeled as modules, in order to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom very large scale integration (VLSI) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.
Modules may also be implemented in software for execution by various types of processors. An identified module of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the module and achieve the stated purpose for the module.
Indeed, a module of executable code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, among different processors, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network.