193 results about "File migration" patented technology

A read-write snapshot copy facility is constructed from a hierarchical storage management facility. The read-write snapshot copy file system initially comprises stub files pointing to the files in a read-only snapshot copy file system. When an application writes to a file in the read-write snapshot copy, the read-write snapshot copy facility migrates a copy of the file to replace the stub file, and then writes to the migrated file. Because the read-write snapshot copy facility references the files in the read-only snapshot file system in a network namespace using standard protocols such as NFS or CIFS, the read-write snapshot copy facility permits referencing of distributed read-only snapshot file systems in an open (heterogeneous) network environment, and the read-write snapshot copy is scalable by linking the read-write snapshot copy facility to multiple file servers containing read-only snapshot file systems.

A namespace server translates client requests for access to files referenced by pathnames in a client-server namespace into requests for access to files referenced by pathnames in a backend NAS network namespace. The namespace server also translates between different file access protocols. The namespace server may change the translation of a client-server network pathname from an old backend NAS network pathname to a new backend NAS network pathname for file migration without disruption to client access during file migration for load balancing or for a more appropriate service level. Client access can also be routed automatically and transparently to replicas in case of server or site failures. The namespace server may create the appearance of a virtual file system that contains multiple physical servers, a virtual share that contains physical shares from different servers, directories that contain files on different servers, and files that contain data from files on different servers.

System and method for partial file migration in file systems by Hierarchical Storage Management (HSM) applications. Embodiments may provide an automated mechanism for HSM applications to partially migrate files by migrating the inactive parts of the files to offline storage while leaving the active parts of the files on disk and active in the file system. In embodiments, access information including timestamps may be recorded and maintained at the subfile level to enable detection of inactivity at the subfile level and hence partial file migration by migrating only the inactive parts of files. The parts of files may be extents, blocks, or ranges. The access information may be recorded and maintained in-memory only, in a separate file on disk, or in extent descriptors for the files.

The invention discloses a storage method and a storage device of a distributive-type file system. The method comprises following steps of determining access times for the same file within a preset period of time; and migrating the file into a storage device with higher performance than the current storage device according to the access times. Through the storage method and the storage device, files inside the distributive-type file system are graded to be stored according to the file access heat of the file, i.e. the file with high access frequencies in the preset period of time is migrated into the storage device with high performance, the correlation of the file slice storage position and the file slice access heat is realized through the differential storage, so that input output operations per second (IOPS) pressure among the storage devices is balanced, and the overall performance is enhanced.

File system independent techniques and mechanisms for replicating files on multiple devices are provided, migrating files from one device to another (for purposes of reliability, increased bandwidth, load balancing, capacity expansion, or reduced cost), and propagating updates from a master copy to remote replicas. The mechanisms involve work queues and asynchronous file migration daemons that operate independently from and in parallel with the primary client-server and network protocol to on-disk storage data paths.

The system of the present invention curbs an unnecessary inter-tier file migration and provides an inter-tier file migration that conforms to the utilization state. The hierarchical storage management system respectively migrates a frequently accessed file to the upper Tier, and an infrequently accessed file to the lower Tier. This system carries out inter-tier file migration in conformance with the utilization state. This system provides functions for anchoring a Tier for storage for a specified file, and for not permitting an inter-tier file migration.

A high availability cluster and method of storage medium management in such high availability cluster. A number k of nodes belonging to the cluster, where k≧2 and includes a master node, are provisioned with high-access-rate and low-access-rate storage media. A file is written to the high-access-rate medium of a serving node selected from among k-1 nodes excluding the master node. The file is also written to low-access-rate medium of each of k-2 nodes excluding the master node and the serving node. A distributed storage medium management protocol supervises file migration from the, low-access-rate medium of a back-up node to the high-access-rate medium of the back-up node upon disruption of file availability on the serving node. File rebalancing relies on parameters including popularity, write- and read-requests, capacity, processing load or cost.

A system and method are provided for migrating data files from a source file volume to a target file volume, wherein a target file volume is generated on a target storage device, and a target directory is created based on a directory in the source file volume. In addition, for each file stored in the source file volume, a corresponding stub file is created in the target file volume. The target file volume is mounted to enable a host to access data stored in the target file volume. Files are then copied from the source file volume to the target file volume. In one embodiment, a data processing request is received from the host specifying a stub file stored in the target file volume, a file in the source file volume is identified that corresponds to the specified stub file, and the file is copied from the source file volume to the target file volume. Requested data is retrieved from the copied file and provided to the host.

Systems and methods to customize a namespace using a synthetic namespace. A NAS switch provides file migrations in a NAS storage network that are transparent to the clients. The NAS switch file handles are used to customize a namespace. More specifically, a synthetic namespace is generated from one or more file location tables that map the switch file handles to NAS file handles. The NAS file handles are independent of a physical export containing the objects referred to by the NAS file handles. In one example, the synthetic namespace presents a home directory corresponding to a location of a user.

A data migration system is provided for migrating data between an existing file server apparatus and a new file server apparatus in a computer system that includes a plurality of host computers and a plurality of file server apparatuses that are mutually connected to one another. The data migration system on the new file server apparatus copies file attributes unique to the network attached storage (NFS) and file attributes unique to the common internet file system (CIFS) from the existing file server apparatus, and stores the file attributes without changing the file attributes in the new file server apparatus. Then actual data is moved from the existing file server to the new file server. When a file access to data is made from a host computer during the file migration process, and if the data has not been migrated from the existing file server to the new file server, the data is read out from the existing file server onto the new file server, and the file access is processed by the new file server as if the existing file server were processing the file access.

A non-distruptive migration of a native volume from a source server to a destination server performed by a file switch involves converting the source native volume to a native with metadata volume. The native with metadata volume is converted to a mirrored native with metadata volume including the source server and the destination server. The destination server includes a mirror copy of the native with metadata volume. The source server is removed from the mirrored native with metadata volume. The mirror copy of the native with metadata volume on the destination server is converted to a destination native volume on the destination server.

A read-write snapshot copy facility is constructed from a hierarchical storage management facility. The read-write snapshot copy file system initially comprises stub files pointing to the files in a read-only snapshot copy file system. When an application writes to a file in the read-write snapshot copy, the read-write snapshot copy facility migrates a copy of the file to replace the stub file, and then writes to the migrated file. Because the read-write snapshot copy facility references the files in the read-only snapshot file system in a network namespace using standard protocols such as NFS or CIFS, the read-write snapshot copy facility permits referencing of distributed read-only snapshot file systems in an open (heterogeneous) network environment, and the read-write snapshot copy is scalable by linking the read-write snapshot copy facility to multiple file servers containing read-only snapshot file systems.

A NAS switch provides file migrations in a NAS storage network that are transparent to the clients. A source file server exports an original NAS file handles indicative of object locations on the source file server to the NAS switch. The NAS switch modifies the original NAS file handles to an internal file system and maps the original NAS file handles to a switch file handles independent of location. The NAS switch exports the switch file handles to a client. The client looks-up objects and makes NAS requests to the source file server using switch file handles. The NAS switch performs file migration by first replicating the namespace containing data to be migrated from source file server to a destination file server. Separately, the NAS replicates data which is a relatively longer process than the namespace replication. During data replication, namespace access requests for objects are directed to the replicated namespace. After data replication, file object requests for migrated objects are redirected to the destination file server in a process that is transparent to the client.

The embodiment of the invention discloses a data searching method and device. The method comprises the following steps that a data searching request is received; two data sheets needing splitting in a hashing mode are determined; information of the data sheets is sent to each slave node; corresponding relations, between hashed values and sheet fragmentation files, sent by the slave nodes are received; fragmentation is conducted on the hashed values to acquire hashed value fragments, and the slave nodes corresponding to the hashed value fragments are respectively determined; according to the relations between the hashed values and the sheet fragmentation files, all the nodes are controlled to transfer the sheet fragmentation files; connecting results, corresponding to each hashed value, sent by each slave node are received, and the data search request result is determined according to the connecting result. The data searching method and device can be used for acquiring the correct left outer join or right outer join result and further acquiring the correct data searching result when left outer join or right outer join is used for achieving data searching processing in an MPP distributed type data base system.