Abstract: Implementations are provided herein for incremental backup using a change tree. A change tree is a database file for tracking file system changes of a specific dataset, such as a directory of a file system. A backup process can create and/or initiate a change tree when creating a backup snapshot of a dataset. After the change tree is created, all file system changes inside the dataset can be tracked. The next incremental backup can then take advantage of the change tree to backup changes without traversing the entire dataset. Thus, incremental backups can be more efficient and are better able to keep up with tape streaming speed.

Abstract: The subject disclosure is directed towards the parallel backing up of a file system. A file system tree structure is walked by parallel workers that write file system data to data storage devices in parallel streams. Work assigned to one worker may be split to an idle worker to provide parallel operation. Relationship data that maintains relationships between the streams is persisted (e.g., via reference data inserted into the streams) so that a restore mechanism is able to stitch the streams together back into the file system data. Also persisted is location data that maintains storage locations of the streams. A file's data also may be written into parallel streams.

Abstract: A method of providing shared objects and node-specific objects in a cluster file system is described and provided. The method includes providing to a particular shared object an attribute, whereas the particular shared object can be a container-type shared object. The attribute indicates any object created in the particular shared object (including its sub-divisions or sub-containers) from this point in time will be designated as node-specific. Furthermore, when a node causes a file system operation that is node-specific to be performed by accessing the particular shared object, the file system operation is performed in an alternate directory corresponding to the node. The alternate directory supports a node-specific object. The shared objects and the node-specific objects can be directories. Additionally, the shared objects and the node-specific objects can be files.

Abstract: Approaches are disclosed for reconfiguring nodes in a cluster file system after new nodes are added to the cluster file system or when node configuration data is changed. According to one aspect of the invention, counters and node configuration data is stored on a volume in a cluster file system. Nodes periodically inspect the counters, and, if it is determined that a node has been added to the cluster file system, or, if the node determines that node configuration data for a node has changed, the node (and other nodes) may dynamically reconfigure itself.

Abstract: A method of providing shared objects and node-specific objects in a cluster file system is described and provided. The method includes providing to a particular shared object an attribute, whereas the particular shared object can be a container-type shared object. The attribute indicates any object created in the particular shared object (including its sub-divisions or sub-containers) from this point in time will be designated as node-specific. Furthermore, when a node causes a file system operation that is node-specific to be performed by accessing the particular shared object, the file system operation is performed in an alternate directory corresponding to the node. The alternate directory supports a node-specific object. The shared objects and the node-specific objects can be directories. Additionally, the shared objects and the node-specific objects can be files.

Abstract: Approaches are disclosed for reconfiguring nodes in a cluster file system after new nodes are added to the cluster file system or when node configuration data is changed. According to one aspect of the invention, counters and node configuration data is stored on a volume in a cluster file system. Nodes periodically inspect the counters, and, if it is determined that a node has been added to the cluster file system, or, if the node determines that node configuration data for a node has changed, the node (and other nodes) may dynamically reconfigure itself.