Abstract: A test automation system is provided that implements a DataTap service to capture underlying communications in a test environment or on a test platform. In some embodiments, the DataTap service can be configured as a passive data capture element. In various embodiments, passive data capture allows the system to record/mirror all data traffic flows associated with test execution without affecting the operation or execution of the tests. Some alternatives include functions to modify test traffic. In some examples, the system is configured to replay tests, modify test execution, modify test parameters, among other options. Various embodiments of the system allow new and updated feature sets to be integrated into existing test platforms without any changes in code, tests, or operation. Further, updates to test services become simple plug-in based features that, for example, provide assurance of zero impact on existing implementation.

Abstract: A test automation system is provided that implements a DataTap service to capture underlying communications in a test environment or on a test platform. In some embodiments, the DataTap service can be configured as a passive data capture element. In various embodiments, passive data capture allows the system to record/mirror all data traffic flows associated with test execution without affecting the operation or execution of the tests. Some alternatives include functions to modify test traffic. In some examples, the system is configured to replay tests, modify test execution, modify test parameters, among other options. Various embodiments of the system allow new and updated feature sets to be integrated into existing test platforms without any changes in code, tests, or operation. Further, updates to test services become simple plug-in based features that, for example, provide assurance of zero impact on existing implementation.

Abstract: A test automation system is provided that enables “codeless” code test generation and execution. Various embodiments allow users to create automation tests, sets variables in test scripts, set validation criteria, etc. all without having to write code for the operation being tested. In some examples, the system is configured to provide access to mobile device emulation based on selection of or from any number of mobile devices. By automatically defining a suite of tests that can be run on a mobile device population, automated testing can improve validation of any developed software, functionality, and identification of test failures over many existing approaches. Once the codeless tests are created on the system, they can be scheduled to run repeatedly, periodically, a-periodically, all without supervision. Any errors can be communicated to the user, with recommendations to resolve, re-test, among other options.

Abstract: A test automation system is provided that enables “codeless” code test generation and execution. Various embodiments allow users to create automation tests, sets variables in test scripts, set validation criteria, etc. all without having to write code for the operation being tested. In some examples, the system is configured to provide access to mobile device emulation based on selection of or from any number of mobile devices. By automatically defining a suite of tests that can be run on a mobile device population, automated testing can improve validation of any developed software, functionality, and identification of test failures over many existing approaches. Once the codeless tests are created on the system, they can be scheduled to run repeatedly, periodically, a-periodically, all without supervision. Any errors can be communicated to the user, with recommendations to resolve, re-test, among other options.

Abstract: A test automation system is provided that implements a DataTap service to capture underlying communications in a test environment or on a test platform. In some embodiments, the DataTap service can be configured as a passive data capture element. In various embodiments, passive data capture allows the system to record/mirror all data traffic flows associated with test execution without affecting the operation or execution of the tests. Some alternatives include functions to modify test traffic. In some examples, the system is configured to replay tests, modify test execution, modify test parameters, among other options. Various embodiments of the system allow new and updated feature sets to be integrated into existing test platforms without any changes in code, tests, or operation. Further, updates to test services become simple plug-in based features that, for example, provide assurance of zero impact on existing implementation.

Abstract: A test automation system is provided that enables “codeless” code test generation and execution. Various embodiments allow users to create automation tests, sets variables in test scripts, set validation criteria, etc. all without having to write code for the operation being tested. In some examples, the system is configured to provide access to mobile device emulation based on selection of or from any number of mobile devices. By automatically defining a suite of tests that can be run on a mobile device population, automated testing can improve validation of any developed software, functionality, and identification of test failures over many existing approaches. Once the codeless tests are created on the system, they can be scheduled to run repeatedly, periodically, a-periodically, all without supervision. Any errors can be communicated to the user, with recommendations to resolve, re-test, among other options.

Abstract: An archival storage cluster of preferably symmetric nodes includes a data protection management system that periodically organizes the then-available nodes into one or more protection sets, with each set comprising a set of n nodes, where “n” refers to a configurable “data protection level” (DPL). At the time of its creation, a given protection set is closed in the sense that each then available node is a member of one, and only one, protection set. When an object is to be stored within the archive, the data protection management system stores the object in a given node of a given protection set and then constrains the distribution of copies of that object to other nodes within the given protection set. As a consequence, all DPL copies of an object are all stored within the same protection set, and only that protection set. This scheme significantly improves MTDL for the cluster as a whole, as the data can only be lost if multiple failures occur within nodes of a given protection set.

Abstract: An archival storage cluster of preferably symmetric nodes includes a data protection management system that periodically organizes the then-available nodes into one or more protection sets, with each set comprising a set of n nodes, where “n” refers to a configurable “data protection level” (DPL). At the time of its creation, a given protection set is closed in the sense that each then available node is a member of one, and only one, protection set. When an object is to be stored within the archive, the data protection management system stores the object in a given node of a given protection set and then constrains the distribution of copies of that object to other nodes within the given protection set. As a consequence, all DPL copies of an object are all stored within the same protection set, and only that protection set. This scheme significantly improves MTDL for the cluster as a whole, as the data can only be lost if multiple failures occur within nodes of a given protection set.

Abstract: An interface between a local file system and a data store (e.g., a “write-once”store) generates and exports to the data store a “versioned” file system. The state of the local file system at a given point in time can be determined using the versioned file system. The versioned file system comprises a set of structured data representations that comprise metadata associated with actual file system data. The interface creates and exports to the data store structured data representations, which correspond to versions of the local file system, as well as the actual file system data that these structured data representations represent. A cache associated with the interface stores recently used data and metadata, as well as write data and metadata waiting to be transferred to the data store. Prior to transfer, data transformations, such as compression, encryption, and de-duplication, may be applied to the data and metadata.

Abstract: A computer system and method for dynamic pricing is described. The system includes at least one dynamic calculator, which performs calculations based upon conditional rules.

Abstract: An interface between an existing local file system and a data store (e.g., a “write-once” store) generates and exports to the data store a “versioned” file system. The state of the local file system at a given point in time can be determined using the versioned file system. Preferably, the versioned file system comprises a set of structured data representations (such as XML) that comprise metadata associated with the actual file system data. In operation, the interface creates and exports to the data store structured data representations, which correspond to versions of the local file system, as well as the actual file system data that these structured data representations represent. A cache associated with the interface stores recently used data and metadata, as well as all write data and metadata waiting to be transferred to the data store. Prior to transfer, one or more data transformations, such as compression, encryption, de-duplication and the like, may be applied to the data and metadata.

Abstract: An archival storage cluster of preferably symmetric nodes includes a data protection management system that periodically organizes the then-available nodes into one or more protection sets, with each set comprising a set of n nodes, where “n” refers to a configurable “data protection level” (DPL). At the time of its creation, a given protection set is closed in the sense that each then available node is a member of one, and only one, protection set. When an object is to be stored within the archive, the data protection management system stores the object in a given node of a given protection set and then constrains the distribution of copies of that object to other nodes within the given protection set. As a consequence, all DPL copies of an object are all stored within the same protection set, and only that protection set. This scheme significantly improves MTDL for the cluster as a whole, as the data can only be lost if multiple failures occur within nodes of a given protection set.

Abstract: A memory storage device has a file storage operating system that uses inodes to access file segments. Each inode has a plurality of rows. A portion of the rows can store extents pointing, directly or indirectly, to data blocks. Each extent has a field to indicate whether the extent is an indirect extent or a direct extent.

Abstract: A hierarchical, probability-based look-up method and apparatus for selection of an operation for job generation. Bitmaps are set based on the priority class of pending operation requests. The bitmap values are used to select a priority class and an operation for the selected priority class in a two-step, probability-based table look-up.

Abstract: A memory storage device has a file storage operating system which uses an inode to record and find segments of each data file. The inode includes a plurality of rows. A portion of the rows are written with direct extents pointing to data blocks storing portions of file segments. At least two of the extents point to data blocks having addresses in different logical volumes.

Abstract: An apparatus and method implemented in embedded software that transparently redirects local hard drive requests to a Network Attached Storage (NAS) subsystem is provided. The apparatus, contains a large front end cache used to intercept local hard disk I/O requests at the lowest level before forwarding to an external network attached NAS subsystem, providing a transparent high performance centrally managed storage solution.

Abstract: An apparatus and method implemented in embedded software that provides instant startup functionality to host computers. The apparatus consists of an embedded controller with microprocessor and interface logic and a large amount of cache memory that is battery protected. The method detects data requested by the host during boot sequences, and saves that and associated meta-data in non-volatile memory. The boot process optimizer can then use this information on subsequent starts to provide the data from the faster cache memory instead of a relatively slower mechanically spinning hard disk drives or other mass memory devices. By utilizing locked in memory indicators, the boot data stored in cache memory will be preserved during subsequent accesses by post-boot operations of the host.

Abstract: A storage manager platform for a data processing system. The storage manager platform, located within the same housing as a host central processing unit, is connected to receive data from both the processor and a mass storage unit such as a disk drive. The storage manager provides a programming environment that is independent of the host operating system, to permit implementation of storage management functions such as performance, data protection and other functions. Commands destined for the storage manager platform are provided as in-band messages that pass as normal I/O requests, through the disk storage interface, in a manner that is independent of any host system bus in configuration. In certain disclosed embodiments of the invention the application performance enhancement functions can include caching, boot enhancement, Redundant Array of Independent Disk (RAID) processing and the like.

Abstract: A technique that provides faster startup functionality for personal computers (PCs) and servers. Data requested by a host processor from a mass storage device, such as a disk drive, during a boot or start-up sequences is detected. Meta-data that describes the requested data including Logical Block Addresses and Logical Block Counts are stored as an extent list in non-volatile memory. This extent list information is then used on subsequent start-ups to pre-stage the data from the mass storage device into fast memory before it is requested by the host. This technique thereby reduces access times and improves boot performance. The extent list can be merged and manipulated in other ways to ensure that efficient use is made of limited non-volatile memory space.

Abstract: A method for adaptively selecting an optimal pre-fetch policy between a first pre-fetch policy, in which a request for desired data from a data-set is satisfied by reading the desired data, and a second pre-fetch policy, in which a request for desired data from a data-set is satisfied by reading the data-set. The method includes collecting statistics on a number of avoidable read-misses. On the basis of the statistics, a first threshold value is defined and frequently updated. Upon detection of an unavoidable read-miss, a random number is generated and the optimal pre-fetch policy is selected on the basis of a sign of a difference between the threshold value and the random number.