Abstract: A system can migrate a source file system on a first computer to a destination file system on a second computer. The system can receive, at the second computer, a request from a client computer that indicates a file system operation, and that references a source file handle of the source file system that comprises an identifier of the source file system. The system can identify the destination file system based on the identifier of the source file system. The system can determine, from a source inode number of the source file handle, a source inode number segment. The system can determine, from the source inode number segment, a destination inode number segment. The system can determine, from the destination inode number segment, a destination inode number. The system can perform the file system operation on the destination file system using the destination inode number and the identifier of the destination file system.

Abstract: A system can determine that a first destination inode number of a first destination inode of destination inodes is equal to a first source inode number of a file. The system can create a second file on the source file system, wherein the second file is stored in a second source inode of the source inodes having a second source inode number of the source inode numbers. The system can determine that the destination file system lacks an inode that has the second source inode number. The system can move a third file stored in the first destination inode to a second destination inode of the destination inodes that has a second destination inode number of the destination inode numbers. The system can migrate the first file to the destination file system, wherein the destination file system stores the first file with the first destination inode number.

Abstract: A system can perform a migration. The system can, in response to receiving a request to perform a file system operation on a destination file system, wherein the request identifies a first source file handle, direct, by a second computer and to a first computer, to perform the file system operation on a source file system with the first source file handle, to produce a second source file handle, convert the first and second source file handles to corresponding first and second components of a destination file handle, perform the file system operation on the destination file system with the first and second components of a destination file handle, respond to the client computer with the second source file handle. The system can re-assign a network address when rolling back the migration, wherein a client is configured to use the second source file handle with the source file system.

Abstract: A system can determine that a first destination inode number of a first destination inode of destination inodes is equal to a first source inode number of a file. The system can create a second file on the source file system, wherein the second file is stored in a second source inode of the source inodes having a second source inode number of the source inode numbers. The system can determine that the destination file system lacks an inode that has the second source inode number. The system can move a third file stored in the first destination inode to a second destination inode of the destination inodes that has a second destination inode number of the destination inode numbers. The system can migrate the first file to the destination file system, wherein the destination file system stores the first file with the first destination inode number.

Abstract: A system can migrate a source file system on a first computer to a destination file system on a second computer. The system can receive, at the second computer, a request from a client computer that indicates a file system operation, and that references a source file handle of the source file system that comprises an identifier of the source file system. The system can identify the destination file system based on the identifier of the source file system. The system can determine, from a source inode number of the source file handle, a source inode number segment. The system can determine, from the source inode number segment, a destination inode number segment. The system can determine, from the destination inode number segment, a destination inode number. The system can perform the file system operation on the destination file system using the destination inode number and the identifier of the destination file system.

Abstract: A target data storage system performing a migration operation also responds to client requests by creating and maintaining a metadata cache for caching attributes of a user file as obtained from a source data storage system. A read-type client request is processed by (1) determining whether the metadata cache stores current attribute values, (2) if so, then satisfying the client request using the current values in the metadata cache, and (3) otherwise obtaining current attribute values from the source data storage system and satisfying the client request using the obtained current attribute values, and storing the current values in the metadata cache to be available for use in processing subsequent read-type client requests. A write-type client request is processed forwarding modified attribute values from the client request to the source data storage system for storage therein.

Abstract: A user I/O operation is processed in a file system of a target data storage system (DSS) performing a file system migration. The target DSS assesses a migration state of a user file of the user I/O operation, including (1) determining whether a metadata file storing migration state data for the user file has an already recovered record indicating the migration state of the file, (2) if so, then using the already recovered record to assess the migration state of the user file, and (3) otherwise (a) initiating an on-demand recovery to obtain an on-demand record for the user file, and (b) using the on-demand recovered record to assess the migration state. If the migration state indicates that the file has not yet been migrated, then the user I/O operation is redirected to a separate source DSS, and otherwise the user I/O operation is completed locally at the target DSS.

Abstract: A system and method provides for querying and setting file attributes between Network File System and Common Internet File System network attached storage systems. Aspects of the present invention may be performed by a storage virtualization system that acts as an intermediary between one or more network attached storage systems. By querying and setting file attributes, files may be migrated between network attached storage systems while keeping the file attributes and primary location of the file contents intact. In addition, the present invention provides an additional aspect of ensuring that file names of multi-protocol files are compatible across every protocol.

Abstract: Electronic commerce transaction messages are processed over a network between a client and a server in a highly reliable fashion by establishing a secure or un-secure communications connection between the network client and the network server at an electronic transaction assurance (eTA) system, which is located in a communication path between the network client and the network server. The transaction type is identified in the message and the progress of the transaction is tracked using transaction models. Any failure in the back-end server system or in the network connections is detected and the failure is recovered from using an outcome determination technique. The failure of a node within the eTA system is masked from the network client by formulating an appropriate response and sending it back to the client such that the network client and network server that were using the selected node do not see any interruption in their communications.

Abstract: Electronic commerce transaction messages are processed over a network between a client and a server in a highly reliable fashion by establishing a secure or un-secure communications connection between the network client and the network server at an electronic transaction assurance (eTA) system, which is located in a communication path between the network client and the network server. The transaction type is identified in the message and the progress of the transaction is tracked using transaction models. Any failure in the back-end server system or in the network connections is detected and the failure is recovered from using an outcome determination technique. The failure of a node within the eTA system is masked from the network client by formulating an appropriate response and sending it back to the client such that the network client and network server that were using the selected node do not see any interruption in their communications.