Abstract: A method, a device and a system for asynchronous directory replication is disclosed. The method comprises: configuring an inode identifier of an object stored in a source NAS, the inode identifier of the object having a first inode space identifier and a first local inode identifier, wherein the first inode space identifier indicates that the object is created by the source NAS; copying the object to a target NAS to be stored as a target object, wherein an inode identifier of the target object having a second inode space identifier and a second local inode identifier, wherein the second inode space identifier indicates that the target object is received from the source NAS, and wherein the second local inode identifier is identical to the first local inode identifier, and creating a mapping between the first inode space identifier and the second inode space identifier.

Abstract: Disclosed is a system that will update the metadata index at the consistency point. Accordingly, the metadata index will be updated at the same time that the data blocks and metadata updates are written to disk. Furthermore, the metadata index will be written in the same location as the file system data, and accordingly, when a snapshot is taken of the file system, the metadata index will also be copied and saved with the snapshot. Accordingly, the metadata index will travel with the snapshots of the filesystem, and will be up to date with the latest changes to the file data blocks.

Abstract: A system and method for block-based restarts are described. A data storage system interfaces with one or more nodes of a network file system on which a volume is provided in order to read data stored on the volume on a block-by-block basis. Backup data sets capable of recreating the data on the volume are generated from the data blocks read from the volume. The system can interface with a backup memory resource and write the backup data sets to the backup memory resource in a sequential order. As the backup data sets are generated and written to the backup memory resource, restart checkpoints for the data set are also regularly generated and stored for use in restarting the backup process in the event of a recoverable failure in the transfer.

Abstract: Techniques and components for backing up data are disclosed. A first subset of data units is selected from a plurality of data units of a storage system to create a first partial baseline for backup of the first storage system. The number of data units in the first subset of data units is determined based on a window size parameter n. Data within the storage system that has changed since a previous backup operation are identified. A first backup including the first partial baseline and the first changed data is written to a second storage system. For a data loss event, the techniques include selecting, based on a time of the determined data loss event in combination with n, the first backup and n?1 additional backups, wherein each of the n?1 additional backups include a partial baseline and changed data. The first backup and the n?1 additional backups are written to a third storage system.

Abstract: A backup tool can manage multi-level backup into a cloud and restoration from the cloud. The backup tool can request a data source to stream backup data to the backup tool, and the backup tool can then generate data objects from the data stream for storing into the cloud. The backup tool generates the data objects in accordance with serialization of the data stream. The order of the data objects resulting from the data stream serialization is encoded into the names of the data objects. In addition, the backup tool encodes the backup level into the object names. With sequencing and backup level encoded into the data object names, the data objects can be stored in the cloud for later restoration.

Abstract: Techniques and components for backing up data are disclosed. A first subset of data units is selected from a plurality of data units of a storage system to create a first partial baseline for backup of the first storage system. The number of data units in the first subset of data units is determined based on a window size parameter n. Data within the storage system that has changed since a previous backup operation are identified. A first backup including the first partial baseline and the first changed data is written to a second storage system. For a data loss event, the techniques include selecting, based on a time of the determined data loss event in combination with n, the first backup and n?1 additional backups, wherein each of the n?1 additional backups include a partial baseline and changed data. The first backup and the n?1 additional backups are written to a third storage system.

Abstract: First partial baseline data of a first storage system is identified. First changed data of the first storage system is identified. The first changed data comprises data that has changed since a previous point in time. First backup data is written to a second storage system. The first backup data comprises the first partial baseline data and the first changed data. After writing the first backup data to the second storage system, second partial baseline data of the first storage system is identified. The second partial baseline data does not include the first partial baseline data. Second changed data of the first storage system is identified. The second changed data comprises data that has changed since writing the first backup data. Second backup data is written to the second storage system. The second backup data comprises the second partial baseline data and the second changed data.

Abstract: Disclosed is a system that will update the metadata index at the consistency point. Accordingly, the metadata index will be updated at the same time that the data blocks and metadata updates are written to disk. Furthermore, the metadata index will be written in the same location as the file system data, and accordingly, when a snapshot is taken of the file system, the metadata index will also be copied and saved with the snapshot. Accordingly, the metadata index will travel with the snapshots of the filesystem, and will be up to date with the latest changes to the file data blocks.

Abstract: A system and method for block-based restarts are described. A data storage system interfaces with one or more nodes of a network file system on which a volume is provided in order to read data stored on the volume on a block-by-block basis. Backup data sets capable of recreating the data on the volume are generated from the data blocks read from the volume. The system can interface with a backup memory resource and write the backup data sets to the backup memory resource in a sequential order. As the backup data sets are generated and written to the backup memory resource, restart checkpoints for the data set are also regularly generated and stored for use in restarting the backup process in the event of a recoverable failure in the transfer.

Abstract: A system and method for block-based restarts are described. A data storage system interfaces with one or more nodes of a network file system on which a volume is provided in order to read data stored on the volume on a block-by-block basis. Backup data sets capable of recreating the data on the volume are generated from the data blocks read from the volume. The system can interface with a backup memory resource and write the backup data sets to the backup memory resource in a sequential order. As the backup data sets are generated and written to the backup memory resource, restart checkpoints for the data set are also regularly generated and stored for use in restarting the backup process in the event of a recoverable failure in the transfer.

Abstract: First partial baseline data of a first storage system is identified. First changed data of the first storage system is identified. The first changed data comprises data that has changed since a previous point in time. First backup data is written to a second storage system. The first backup data comprises the first partial baseline data and the first changed data. After writing the first backup data to the second storage system, second partial baseline data of the first storage system is identified. The second partial baseline data does not include the first partial baseline data. Second changed data of the first storage system is identified. The second changed data comprises data that has changed since writing the first backup data. Second backup data is written to the second storage system. The second backup data comprises the second partial baseline data and the second changed data.

Abstract: A backup tool can manage multi-level backup into a cloud and restoration from the cloud. The backup tool can request a data source to stream backup data to the backup tool, and the backup tool can then generate data objects from the data stream for storing into the cloud. The backup tool generates the data objects in accordance with serialization of the data stream. The order of the data objects resulting from the data stream serialization is encoded into the names of the data objects. In addition, the backup tool encodes the backup level into the object names. With sequencing and backup level encoded into the data object names, the data objects can be stored in the cloud for later restoration.

Abstract: A system and method for block-based restarts are described. A data storage system interfaces with one or more nodes of a network file system on which a volume is provided in order to read data stored on the volume on a block-by-block basis. Backup data sets capable of recreating the data on the volume are generated from the data blocks read from the volume. The system can interface with a backup memory resource and write the backup data sets to the backup memory resource in a sequential order. As the backup data sets are generated and written to the backup memory resource, restart checkpoints for the data set are also regularly generated and stored for use in restarting the backup process in the event of a recoverable failure in the transfer.

Abstract: A method of storing data to an aggregate storage system including: receiving data at the aggregate storage system, wherein the aggregate storage system includes a random-access storage component and a sequential-access storage component, and wherein the data includes one or more data portions and one or more metadata portions; identifying each portion of the data as either one of the data portions or one of the metadata portions; in response to determining that one of the metadata portions is identified, writing the metadata portion to the random-access storage component and the sequential-access storage component; and in response to determining that one of the data portions is identified, writing the data portion only to the sequential-access storage component.