Browse Prior Art Database

Version-based Storage Device with Backup Support

IP.com Disclosure Number: IPCOM000246956D
Publication Date: 2016-Jul-18
Document File: 5 page(s) / 226K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a version-based storage device is able to backup logical blocks' state and to allow for users to roll back state of files, file systems, or entire block devices on version basis. Such storage device is able to rollback to any version of block's state (file's state), to provide natural support for tracking changes in files, and to provide easy way for recovering information in the case of malicious or erroneous a user or software activity.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 47% of the total text.

Page 01 of 5

Version-based Storage Device with Backup Support

ABSTRACT. Disclosed is a version-based storage device is able to backup logical blocks' state and to allow for users to roll back state of files, file systems, or entire block devices on version basis. Such storage device is able to rollback to any version of block's state (file's state), to provide natural support for tracking changes in files, and to provide easy way for recovering information in the case of malicious or erroneous a user or software activity.

Traditionally, one needs to use backup specific software on a host to initiate a backup archive. This means that the backup software (Figure 1): (1) reads the contents of a file system volume 103 or partition, or any other logical construct that the software is aware of; (2) prepares a backup archive 104 on the host 101; (3) stores the backup archive 104 into some persistent storage 105.

 

In the case of I/O errors or logical construct corruption (Figure 2) on a volume 203, backup software needs to have access to backup archive 206. The backup software reads the backup archive 206 on the host 201 and writes recovered information into the corrupted volume 203.

Figure 1 Traditional Backup Operation 


Page 02 of 5

 

Usually, the target use-case of traditional backup/restore approach is complete or partial malfunctioning of storage device. The expectation of storage device's malfunctioning is the key reason of necessity to use two independent storage devices (one contains file system volume, another one stores backup archive). Such approach has as advantages as drawbacks but, finally, the traditional backup/restore approach is unable to guarantee the successful user data recovering.

First of all, huge amount of end users' issues with data storage take place because of:
(1) file system bugs, (2) OS crashes, (3) end users mistakes, or (4) malicious activity but not because of storage device malfunctioning. Capacity of modern storage devices is growing significantly without adding any new features. As a result, available data storage device's free space cannot be used efficiently. Moreover, amount of "unrecovered read errors" issues are growing substantially and modern file systems are not ready to process such issue efficiently. Even backup/restore approach is unable to guarantee the absence of data loss in such environment. Backup activity takes place from time to time or with some timeout and, finally, available backup archive could contain not actual state of user data. Also backup operation needs in file system volume's freezing or in very sophisticated approaches of file system volume's changes tracking with significant memory footprint and CPU usage. Finally, user data is unavailable and it's needed to be recovered for the case of corrupted file system volume but well-functioning data storage device.

Every file system volume (Figure 3) is a sequence of logical blocks 301. Modification of the file system 302 occurs when...