Using the gpfs.snap command
This topic describes the usage of gpfs.snap command in IBM Storage Scale.
Running the gpfs.snap command with no options is similar to running the gpfs.snap -a command. It collects data from all nodes in the cluster. This invocation creates a file that is made up of multiple gpfs.snap snapshots. The file that is created includes a master snapshot of the node from which the gpfs.snap command was invoked, and non-master snapshots of each of other nodes in the cluster.
If the node on which the gpfs.snap command is run is not a file system manager node, the gpfs.snap creates a non-master snapshot on the file system manager nodes.
- Data that is always gathered by the gpfs.snap command for master snapshots and non-master snapshots:
- Data that is gathered by the gpfs.snap command in the case of only a master snapshot. For more information, see Data gathered by gpfs.snap for a controller snapshot.
When the gpfs.snap command runs with no options, data is collected for each of the enabled protocols. You can turn off the collection of all protocol data and specify the type of protocol information to be collected using the --protocol option. For more information, see gpfs.snap command.
- Data gathered for SMB on Linux
- Data gathered for NFS on Linux
- Data gathered for S3 on Linux
- Data gathered for Object on Linux
- Data gathered for CES on Linux
- Data gathered for authentication on Linux
- Data gathered for performance on Linux
- Data gathered by gpfs.snap for File audit logging and Watchfolder components