Migration via external interposition
Shadow filesystem semantics during migration
Snapshots of shadow filesystems
Replicating shadow filesystems
Migration of local filesystems
Testing potential shadow migration
Migrating data from an active NFS server
Filesystem and project settings
Protocol access to mountpoints
Non-blocking mandatory locking
Remote Replication Introduction
Project-level vs Share-level Replication
Modes: Manual, Scheduled, or Continuous
Including Intermediate Snapshots
Sending and Cancelling Updates
Cancelling Replication Updates
Cloning a Package or Individual Shares
Exporting Replicated Filesystems
Reversing the Direction of Replication
Destroying a Replication Package
Snapshots and Data Consistency
Replicating iSCSI Configuration
Upgrading From 2009.Q3 and Earlier
Snapshots are read only copies of a filesystem at a given point of time. For more information on snapshots and how they work, see the concepts page. Projects snapshots consist of snapshots of every filesystem and LUN in the project, all with identical names. Shares can delete the snapshots individually, and creating a snapshot with the same name as a project snapshot, while supported, can result in undefined behavior as the snapshot will be considered part of the project snapshot with the same name.
The behavior of this property is identical to its behavior at the share level.
Project level snapshots are administered in the same way as share level snapshots. The following actions are documented under the shares section.
Project snapshots do not support rollback or clone operations.
To access the snapshots for a project, navigate to the project and run the snapshots command.
clownfish:> shares select default clownfish:shares default> snapshots clownfish:shares default snapshots>
From this point, snapshots are administered in the same way as share level snapshots. The following actions are documented under the shares section.
Project snapshots do not support rollback or clone operations.