Java • Python • JavaScript • Dojo • html • css • Apache Tomcat on Linux • Eclipse IDE • ant • make • XML • InstallAnywhere • MVC • Objective C • ActionScript • Flex • SQL • MySQL • C • ksh • shell scripting • tcl/tk • Expect • sed • awk • Linux • AIX • Unix.
Us Patents
Determining Whether Data Written To Source Storage Locations According To A Write Order Is Copied To Corresponding Target Storage Locations In The Write Order
International Business Machines Corporation - Armonk NY
International Classification:
G06F 11/00
US Classification:
707204, 714 54
Abstract:
Provided are a method, system, and article of manufacture for determining whether data written to source storage locations according to a write order is copied to corresponding target storage locations in the write order. Values are written to indicated source storage locations in a write order. The values written to the source storage locations are copied to corresponding target storage locations. The values at the target storage locations are read and a determination is made from the read values whether the values were written to the target storage locations in the write order.
Enhanced Failure Data Collection System Apparatus And Method
William W. Owen - Tucson AZ, US Joshua M. Rhoades - Tucson AZ, US Marina M. Ruíz - Tucson AZ, US
Assignee:
International Business Machines Corporation - Armonk NY
International Classification:
G06F 11/00
US Classification:
714 27
Abstract:
An apparatus for collecting failure data includes a failure data collector that initializes one or more test devices by establishing a secondary interface therewith in response to receiving a test device initialization command from a device tester, communicates one or more failure data collection requests to each test device corresponding to a failure data collection command received from the test device, and receives failure data from the test devices via the secondary interface in response to communicating the failure data collection request. In certain embodiments, the present invention includes a failure data storage repository for storing the collected failure data.
Apparatus And Method To Perform A Version Pre-Check Of A Storage Controller Command
A method to perform a version pre-check of a storage controller command, wherein the method extracts a plurality of objects from a storage controller command, and determines, without querying the storage controller, if each object comprising a method or a method parameter is enabled on that storage controller. If each object comprising a method or a method parameter is enabled on the storage controller, the method indicates success for a version pre-check of the storage controller command.
Evenly Distributing Workload And Providing A Predictable Failover Scenario In A Data Replication System
Paul Anthony Jennas - Tucson AZ, US Jason Lee Peipelman - Tucson AZ, US Joshua Marshall Rhoades - Tucson AZ, US David Montgomery - Tucson AZ, US Philip Matthew Doatmas - Tucson AZ, US Michael Robert Groseclose - Tucson AZ, US Larry Juarez - Tucson AZ, US Todd Charles Sorenson - Tucson AZ, US
Assignee:
International Business Machines Corporation - Armonk NY
International Classification:
G06F 9/46
US Classification:
718104
Abstract:
A method for more effectively distributing the I/O workload in a data replication system is disclosed herein. In selected embodiments, such a method may include generating an I/O request and identifying a storage resource group associated with the I/O request. In the event the I/O request is associated with a first storage resource group, the I/O request may be directed to a first storage device and a copy of the I/O request may be mirrored from the first storage device to a second storage device. Alternatively, in the event the I/O request is associated with a second storage resource group, the I/O request may be directed to a second storage device and a copy of the I/O request may be mirrored from the second storage device to the first storage device. A corresponding system, apparatus, and computer program product are also disclosed and claimed herein.
Jason L. Peipelman - Vail AZ, US Joshua M. Rhoades - Idaho Falls ID, US Matthew J. Ward - Vail AZ, US
Assignee:
International Business Machines Corporation - Armonk NY
International Classification:
G06F 17/00
US Classification:
707649, 707690, 707803
Abstract:
A method for dynamic consistency group formation, in one embodiment, includes creating a snapshot of first data stored on a source storage system with respect to data content and data structure, copying the snapshot to a target storage system, detecting one or more write operations affecting data on the source storage system while copying the first data, detecting one or more collisions affecting the first data on the source storage system, wherein a collision occurs whenever the write operations affect the first data prior to the first data being written, setting a consistency group interval which represents an interval duration between successive snapshot create-and-copy events, and altering the consistency group interval to minimize collisions affecting data on at least one of the storage systems. Other methods for dynamic consistency group formation are also described.
Dynamic Consistency Group Formation And Systems Using The Same
Jason L. Peipelman - Vail AZ, US Joshua M. Rhoades - Idaho Falls ID, US Matthew J. Ward - Vail AZ, US
Assignee:
International Business Machines Corporation - Armonk NY
International Classification:
G06F 17/00
US Classification:
707649, 707690, 707803
Abstract:
In one embodiment, a system, includes logic for creating a snapshot of first data stored on a source storage system, wherein the snapshot is a logical copy of the first data stored on the source storage system with respect to data content and data structure; logic for copying the snapshot to a target storage system; logic for copying the first data represented by the snapshot from the source storage system to the target storage system; logic for detecting one or more write operations affecting data on the source storage system; logic for detecting one or more collisions affecting the first data on the source storage system, logic for setting a consistency group interval; and logic for altering the consistency group interval to minimise collisions affecting data on the source storage system. Other systems and computer program products for dynamic consistency group formation are also described.
Data Migration Methodology For Use With Arrays Of Powered-Down Storage Devices
Dale Howard Anderson - Tucson AZ, US Philip Matthew Doatmas - Flagstaff AZ, US Michael Robert Groseclose - Tuscon AZ, US Larry Juarez - Tucson AZ, US Brian Sean McCain - Mountain View CA, US David Montgomery - Tucson AZ, US Jason Lee Peipelman - Vail AZ, US Joshua Marshall Rhoades - Tucson AZ, US Todd Charles Sorenson - Tucson AZ, US
Assignee:
International Business Machines Corporation - Armonk NY
International Classification:
G06F 12/00
US Classification:
711162, 713320, 711114
Abstract:
A method for managing extents in a data storage system includes monitoring usage statistics for an extent residing on one or more powered-up storage devices. In the event the extent has not been accessed for specified period of time (as determined from the usage statistics), the method automatically compresses the extent and migrates the extent to an intermediate repository. Once the amount of data in the intermediate repository reaches a specified level, the method migrates the extent from the intermediate repository to one or more normally powered-down storage devices. If I/O is received for the extent while it resides in the normally powered-down storage devices or the intermediate repository, the method automatically migrates the extent from the normally powered-down storage devices or the intermediate repository to the normally powered-up storage devices. A corresponding apparatus and computer program product are also disclosed.
Jason L. Peipelman - Vail AZ, US Joshua Marshall Rhoades - Idaho Falls ID, US Matthew J. Ward - Vail AZ, US
Assignee:
International Business Machines Corporation - Armonk NY
International Classification:
G06F 12/16
US Classification:
711162, 711161
Abstract:
In one aspect of the present description, a data preservation function is provided for preserving a set of data on a source storage device at a point in time, and includes identifying as a function of prior update usage, such as input/output usage, of the data to be preserved, a portion of the data which is more likely to be the subject of updates during at least a portion of the data preservation operation as compared to the remaining portion of the data to be preserved, and copies the identified portion of the data to be preserved to a target storage device. In another aspect, the size of the portion of data to be identified is variable. In one embodiment, the size of the portion of data to be identified is a function of a parameter of the command, such that a user can specify the command parameter which affects the size of the portion of data which is prewritten to the target storage device. The parameter may be, for example, a percentage of the data to be preserved, such that a user can specify the percentage of the point-in-time data which is prewritten to the target storage device. Alternatively, the parameter may be, for example, a probability of a collision occurring, such that a user can specify a probability of a collision occurring.
2006 to 2011 Storage Systems CLI Developer and Team LeadIBM
2001 to 2005 Storage Systems Test Tools DeveloperWestinghouse Goose Creek, SC Oct 1998 to Sep 1999 Nuclear Power School Crew Training EngineerPersonal Projects
Additional Experience
Education:
University of Wyoming Laramie, WY May 2001 M.S. in Computer ScienceBrigham Young University Provo, UT Dec 1997 B.S. in Chemical Engineering