Abstract: Name caching can be used external to a distributed file system (DFS), such as a network file system (NFS), to reduce the complexity of facilitating a file operation at the DFS. A system that can use the name caching and request the file operation of the DFS can comprise a processor and a memory that stores executable instructions that, when executed by the processor, facilitate performance of operations. The operations can comprise, in response to a lookup operation or a file operation performed by a DFS, storing, using the processor, a name cache entry for each directory element accessed during the lookup operation or the file operation. The operations further can comprise sending, to the DFS, a single request that comprises a compound command comprising requests for a set of lookup operations and for a file operation.

Abstract: Described herein is a system that provides data service failover in shared storage clusters. An example shared storage cluster can include multiple data node devices equipped to access to a shared storage location. Each of the data node devices can host multiple network attached storage (NAS) servers. For each NAS server at a data node device, a different data node device in the shared storage cluster can be designated as a backup node. The designated backup nodes for NAS servers at any one data node device in the shared storage cluster can be distributed across multiple other data node devices in the shared storage cluster, thereby sharing the burden of data node device failure across multiple other data node devices.

Abstract: Described herein is a system that performs cluster controller selection in a shared storage cluster. A shared storage cluster can include multiple data node devices equipped to access to a shared storage location. The data node devices can be managed by a cluster controller. Furthermore, multiple of the data node devices can be equipped to serve as the cluster controller if necessary. To ensure ongoing operation of a cluster controller, each data node device, including the current cluster controller, can periodically update the shared storage location to indicate the data node device is operational. Each data node device can furthermore perform a cluster controller selection process, and can record its cluster controller selection in the shared storage location. If the current cluster controller fails to periodically update the shared storage location, the cluster controller selection processes at the other data node devices can select a new cluster controller.

Abstract: Described herein is a system that provides data service failover in shared storage clusters. An example shared storage cluster can include multiple data node devices equipped to access to a shared storage location. Each of the data node devices can host multiple network attached storage (NAS) servers. For each NAS server at a data node device, a different data node device in the shared storage cluster can be designated as a backup node. The designated backup nodes for NAS servers at any one data node device in the shared storage cluster can be distributed across multiple other data node devices in the shared storage cluster, thereby sharing the burden of data node device failure across multiple other data node devices.

Abstract: Described herein is a system that performs cluster controller selection in a shared storage cluster. A shared storage cluster can include multiple data node devices equipped to access to a shared storage location. The data node devices can be managed by a cluster controller. Furthermore, multiple of the data node devices can be equipped to serve as the cluster controller if necessary. To ensure ongoing operation of a cluster controller, each data node device, including the current cluster controller, can periodically update the shared storage location to indicate the data node device is operational. Each data node device can furthermore perform a cluster controller selection process, and can record its cluster controller selection in the shared storage location. If the current cluster controller fails to periodically update the shared storage location, the cluster controller selection processes at the other data node devices can select a new cluster controller.

Abstract: A data management method and system for migrating a data volume from a source array to a destination array includes receiving an indication of a source volume to migrate from the source array to the destination array wherein the source volume comprises a clustered volume associated with a plurality of cluster hosts. A path-flip is performed by the host multipath module, to switch the paths between source and destination array. This switch is done in a seamless manner, without disrupting host I/O. The path-flip includes transferring associated metadata from source to destination and can be performed even in clustered and/or multi-host environments. Sanity timers are built-in to ensure that the path-flip completes within a stipulated time-frame and, if not, the path-flip process is aborted and I/O is resumed without any disruption.

Abstract: A method may include establishing, by a MPIO driver of a host information handling system, an I/O path between the host information handling system and the source storage array as an active I/O path and a path between the host and the target storage array as a passive I/O path. The method may also include performing a snapshot-based iterative replication between the source storage array and the target storage array, wherein successive iterations of the snapshot-based iterative replication comprise I/O to the source storage array occurring during an immediately previous iteration of the snapshot-based iterative replication. The method may further include, upon completion of the snapshot-based iterative replication, establishing, by the MPIO, the I/O path between the host and the source storage array as a passive I/O path and the path between the host and the target storage array as the active I/O path.

Abstract: A method and system perform a background copy of a source volume to a migration volume. The source volume has an asynchronous replication relationship with a disaster recovery (DR) volume. A migration volume snapshot may be obtained and host I/O to the source volume may be disabled. A post-copy replication of the source volume is performed to synchronize the source volume and the DR volume. A replication snapshot, comprising a snapshot of the DR volume, is obtained and an identifier of the replication snapshot is modified in accordance with an identifier of the migration snapshot. For example, the identifier of the migration snapshot may be copied to the replication snapshot. Thereafter, an existing replication relationship between the source volume and the DR volume may be disabled and a post-migration replication relationship between the migration volume and the DR volume established such that subsequent replication are incremental or delta replications.

Abstract: A data management method and system for migrating a data volume from a source array to a destination array includes receiving an indication of a source volume to migrate from the source array to the destination array wherein the source volume comprises a clustered volume associated with a plurality of cluster hosts. A path-flip is performed by the host multipath module, to switch the paths between source and destination array. This switch is done in a seamless manner, without disrupting host I/O. The path-flip includes transferring associated metadata from source to destination and can be performed even in clustered and/or multi-host environments. Sanity timers are built-in to ensure that the path-flip completes within a stipulated time-frame and, if not, the path-flip process is aborted and I/O is resumed without any disruption.

Abstract: A method may include establishing, by a MPIO driver of a host information handling system, an I/O path between the host information handling system and the source storage array as an active I/O path and a path between the host and the target storage array as a passive I/O path. The method may also include performing a snapshot-based iterative replication between the source storage array and the target storage array, wherein successive iterations of the snapshot-based iterative replication comprise I/O to the source storage array occurring during an immediately previous iteration of the snapshot-based iterative replication. The method may further include, upon completion of the snapshot-based iterative replication, establishing, by the MPIO, the I/O path between the host and the source storage array as a passive I/O path and the path between the host and the target storage array as the active I/O path.

Abstract: A method and system self encrypts a disk storage device. Given a plurality of data storage devices, the system establishes an encryption key for the plurality of data storage devices. The system locally stores the encryption key in a piecewise manner throughout the plurality of data storage devices such that the encryption key is rendered undeterminable with less than a threshold subset of the plurality of data storage devices. This results in the plurality of data storage devices being self encrypting. Upon an increase or decrease in the plurality, the system resplits the encryption key and locally stores the resulting pieces throughout the changed (increased/decreased) plurality of data storage devices. This renders the encryption key undeterminable with less than a new or revised threshold each time the plurality is changed.

Abstract: The invention pertains to a method and apparatus for writing data to an array of Shingled Magnetic Recording (SMR) devices. In an embodiment of the invention a parity band configured to allow random access writes is provided. Next, data is appended sequentially to a stripe on an array of SMR devices. Then the parity band is updated to contain parity data consistent with the data appended to the stripe. In another embodiment of the invention, a shingled parity band is provided. Data is then appended sequentially to a stripe on an array of SMR devices without the user being required to write an entire stripe of data. The provided parity band is then updated to contain parity data consistent with the data that was appended to the stripe. In such an embodiment it is not always necessary to delete all of the parity data in the parity band when updating the parity band.

Abstract: Embodiments of the present invention provide various polymeric matrices that may be used as a binder matrix for polymer solder hybrid thermal interface materials. In alternative embodiments the binder matrix material may be phophozene, perfluoro ether, polyether, or urethane. For one embodiment, the binder matrix is selected to provide improved adhesion to a variety of interfaces. For an alternative embodiment the binder matrix is selected to provide low contact resistance. In alternative embodiments, polymeric materials containing fusible and non-fusible particles may be used in application where heat removal is desired and is not restricted to thermal interface materials for microelectronic devices.

Abstract: The invention pertains to a method and apparatus for writing data to an array of Shingled Magnetic Recording (SMR) devices. In an embodiment of the invention a parity band configured to allow random access writes is provided. Next, data is appended sequentially to a stripe on an array of SMR devices. Then the parity band is updated to contain parity data consistent with the data appended to the stripe. In another embodiment of the invention, a shingled parity band is provided. Data is then appended sequentially to a stripe on an array of SMR devices without the user being required to write an entire stripe of data. The provided parity band is then updated to contain parity data consistent with the data that was appended to the stripe. In such an embodiment it is not always necessary to delete all of the parity data in the parity band when updating the parity band.

Abstract: Systems and methods for providing an efficient partitioned resource server are disclosed. The partitioned resource server includes a plurality of individual servers, and the individual servers support a storage service. The systems and methods provide archiving processes for partitioned resources. To this end, the systems and process include a snapshot process operating on a server and capable of coordinating with other snapshot processes operating on the other servers for generating state information representative of the state of the partitioned resources.

Abstract: A method and system self encrypts a disk storage device. Given a plurality of data storage devices, the system establishes an encryption key for the plurality of data storage devices. The system locally stores the encryption key in a piecewise manner throughout the plurality of data storage devices such that the encryption key is rendered undeterminable with less than a threshold subset of the plurality of data storage devices. This results in the plurality of data storage devices being self encrypting. Upon an increase or decrease in the plurality, the system resplits the encryption key and locally stores the resulting pieces throughout the changed (increased/decreased) plurality of data storage devices. This renders the encryption key undeterminable with less than a new or revised threshold each time the plurality is changed.

Abstract: Embodiments of the present invention provide various polymeric matrices that may be used as a binder matrix for polymer solder hybrid thermal interface materials. In alternative embodiments the binder matrix material may be phophozene, perfluoro ether, polyether, or urethane. For one embodiment, the binder matrix is selected to provide improved adhesion to a variety of interfaces. For an alternative embodiment the binder matrix is selected to provide low contact resistance. In alternative embodiments, polymeric materials containing fusible and non-fusible particles may be used in application where heat removal is desired and is not restricted to thermal interface materials for microelectronic devices.