9 results about "Sparse file" patented technology

Embodiments are provided for mirroring an operating system by creating a new OS image from a copy of an installer operating system (OS) image maintained in persistent storage. During operating system mirroring, only a portion of the operating system files in the installer image are fully copied to the new operating system image. Placeholder files are created for other files that were not included in the initial subset of OS files, which are determined to be critical to the booting of the OS and / or a minimum set of OS functions. Placeholder files are different from sparse files, which are not accurately displayed by the file system as complete copies of the underlying installer OS image. The data of the placeholder files is copied only when requested, on demand, and / or when there is available / unused processing bandwidth, which is subsequently identified after the computing system is rebooted using the new OS image.

This application discloses a hard disk testing method and electronic device, relating to the field of hardware testing technology. The method uses a master control script to determine the target hard disk to be tested, assesses whether the target hard disk is mounted, and obtains the target hard disk's device parameters. A data filling model is used to automatically calculate the capacity to be filled based on the device parameters, eliminating the need for manual control. By creating a sparse file, when the data filling volume is too large, the test capacity of the target hard disk is quickly expanded using the sparse file's byte expansion characteristic. After expanding to the test capacity, a dirty disk test is performed on the expanded hard disk. This solves the technical problem of excessively long data filling time when the data filling volume is too large, thus improving testing efficiency.

A method for recovering files from a filesystem stored across sparse files in a cloud environment is described. According to the method, a data management system may receive a request to read the files. The data management system may identify one or more target address ranges corresponding to the files indicated via the request. The data management system may read index information for the sparse files in the cloud environment. The index information may indicate respective address ranges for data blocks within the sparse files. The data management system may identify one or more data blocks within one or more sparse files as corresponding to address ranges that overlap with the one or more target address ranges based on the index information. The data management system may transmit, to the cloud environment, one or more read requests for the identified one or more data blocks.

A computer-implemented method for providing a process with access to data stored in a file comprises receiving a request, from a process, to access at least a portion of the data, creating an empty sparse file and associated metadata; creating a memory-mapped sparse file in a virtual memory of the process and allocating memory for the process using a pointer to a starting position of the memory-mapped sparse file; copying in the at least a portion of the data into the sparse file; and providing the process with access to the data based upon the based upon the memory-mapped sparse file. The zero content of the memory-mapped sparse file is mapped to a system zero page. By using the memory-mapped sparse file as a container for the data and the system zero page, data may be more efficiently allocated by the computer system.

The application provides a node setting method, a data storage method, an electronic device and a storage medium. Each storage node is respectively provided with a corresponding sparse file, each virtual storage address in the sparse file corresponds to each physical storage address in the corresponding storage node in one-to-one correspondence, and the method comprises the following steps: acquiring a data storage instruction, the data storage instruction comprising a data storage address and to-be-stored data; writing the to-be-stored data into each sparse file according to the data storage instruction, the virtual storage address indicated by the data storage address; and writing the to-be-stored data written in the virtual storage address indicated by the data storage address in each sparse file into the corresponding storage node respectively, the physical storage address corresponding to the virtual storage address. Therefore, compared with the backup mode of the primary node and the standby node in the prior art, the data is not easy to be lost due to the absence of the time difference between the primary node and the standby node.

This invention discloses a remote backup method and system suitable for narrow bandwidth environments, relating to the field of data backup and recovery technology. The method includes the following steps: deploying a cache server to build a centralized relay architecture; receiving backup instructions and determining the backup type; if it is an incremental backup, entering incremental caching mode; if it is the first or full backup, entering full pass-through mode; performing sparse file, bitmap, and metadata collaborative capture for incremental backup; performing pass-through forwarding mode for full backup; and using QoS-based intelligent bandwidth utilization and transmission priority scheduling. This invention accurately captures incremental data through a dual-file mechanism of sparse files and bitmaps, avoiding storage resource waste. Combined with a dual QoS strategy of snapshot pre-transmission and dynamic priority scheduling, it maximizes narrow bandwidth resource utilization, balances fairness in multi-client backup with core business priority, and efficiently adapts to narrow bandwidth, high latency cross-data center backup scenarios.

The application provides a method, device and storage medium for realizing sparse file migration, which comprises the following steps: S1, reading a source file of a sparse file by using a driver, and mapping a data area of the source file into a virtual target sparse file according to metadata of the source file; S2, listening to reading and / or writing operations on the target sparse file by using the driver, and mapping the reading and / or writing operations on the target sparse file to reading and / or writing operations on the source file; and S3, keeping listening to the reading and / or writing operations on the target sparse file by the driver until an exit signal is received, removing the mapping, and updating the source file according to the mapped reading and / or writing operations on the source file. By using the above technical scheme, the sparse file can be migrated arbitrarily without losing the sparse characteristic.

A method for recovering files from a filesystem stored across sparse files in a cloud environment is described. According to the method, a data management system may receive a request to read the files. The data management system may identify one or more target address ranges corresponding to the files indicated via the request. The data management system may read index information for the sparse files in the cloud environment. The index information may indicate respective address ranges for data blocks within the sparse files. The data management system may identify one or more data blocks within one or more sparse files as corresponding to address ranges that overlap with the one or more target address ranges based on the index information. The data management system may transmit, to the cloud environment, one or more read requests for the identified one or more data blocks.

A system may parse, during a current filesystem check, a sparse file stream comprising a plurality of Update Sequence Numbers (USNs). A system may access a checkpoint USN that is locally stored apart from the sparse file stream and serves as a checkpoint of a prior USN that was accessed during a prior filesystem check. A system may identify a next byte offset for a next USN of a file in the sparse file stream after the checkpoint USN based on the byte offset of the checkpoint USN. A system may update the checkpoint USN with the next USN. A system may identify a file event from the sparse file stream based on the next USN without polling files or directories on the filesystem. A system may pass the file event to a downstream system.