Abstract:
A system for object-based archival data storage includes an object-based storage subsystem having respective data storage devices, at least one file presentation interface that interfaces to client platforms, an administration interface having graphical user interface (GUI) and a command line interface (CLI), a meta data subsystem for storing meta data about files, and includes a virtual file subsystem having a virtual file server (VFS), a policy subsystem, and a scalar e interconnect to couple the object-based storage subsystem, the at least one file presentation interface, the administration interface, the meta data subsystem, and the policy subsystem, wherein the policy subsystem provides system rules predetermined by a user for at least one of hash based integrity checking, read-only/write-ability/erase-ability control, and duplicate data treatment corresponding to files and file objects.
Abstract:
A system for object-based archival data storage includes an object-based storage subsystem having respective data storage devices, at least one file presentation interface that interfaces to client platforms, an administration interface having graphical user interface (GUI) and a command line interface (CLI), a meta data subsystem for storing meta data about files, and includes a virtual file subsystem having a virtual file server (VFS), a policy subsystem, and a scalar e interconnect to couple the object-based storage subsystem, the at least one file presentation interface, the administration interface, the meta data subsystem, and the policy subsystem, wherein the policy subsystem provides system rules predetermined by a user for at least one of hash based integrity checking, read-only/write-ability/erase-ability control, and duplicate data treatment corresponding to files and file objects.
Abstract:
A data backup system for use with a server running a storage application such as a file system or database management system that writes and reads data blocks to and from a volume. The data backup system includes a self archiving log structured volume for copying blocks from the active volume while the storage application is running without contending with the storage application for access to data blocks. The self archiving log structured volume records the result of every write event in a new location in primary storage, forming a chronological log of the state changes the volume undergoes. The self archiving log structured volume is operable to record in the log the points in time (synch events) when the blocks of the self archiving log structured volume are in a consistent state with respect to the storage application. The data backup system further includes backing storage operable with the self archiving log structured volume to store the archived data blocks and synch events of the self archiving log structured volume. The self archiving log structured volume is operable to migrate inactive segments of its log to the backing storage. The self archiving log structured volume is further operable to ensure that a volume can be reconstructed from a fixed number of log segments.