29.01.2013 Views

GPFS: Administration and Programming Reference - IRA Home

GPFS: Administration and Programming Reference - IRA Home

GPFS: Administration and Programming Reference - IRA Home

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

mmcrsnapshot Comm<strong>and</strong><br />

Name<br />

mmcrsnapshot – Creates a snapshot of an entire <strong>GPFS</strong> file system at a single point in time.<br />

Synopsis<br />

mmcrsnapshot Device Directory<br />

Description<br />

Use the mmcrsnapshot comm<strong>and</strong> to create a snapshot of an entire <strong>GPFS</strong> file system at a single point in<br />

time.<br />

A snapshot is a copy of the changed user data in the file system. System data <strong>and</strong> existing snapshots are<br />

not copied. The snapshot function allows a backup or mirror program to run concurrently with user updates<br />

<strong>and</strong> still obtain a consistent copy of the file system as of the time the copy was created. Snapshots are<br />

exact copies of changed data in the active files <strong>and</strong> directories of a file system. Snapshots of a file system<br />

are read-only <strong>and</strong> they appear in a .snapshots directory located in the file system root directory. The files<br />

<strong>and</strong> attributes of the file system may be changed only in the active copy.<br />

There is a maximum limit of 31 snapshots per file system. Snapshots may be deleted only by issuing the<br />

mmdelsnapshot comm<strong>and</strong>. The .snapshots directory cannot be deleted, though it can be renamed with<br />

the mmsnapdir comm<strong>and</strong> using the -s option.<br />

If the mmcrsnapshot comm<strong>and</strong> is issued while a conflicting comm<strong>and</strong> is running, the mmcrsnapshot<br />

comm<strong>and</strong> waits for that comm<strong>and</strong> to complete. If the mmcrsnapshot comm<strong>and</strong> is running while a<br />

conflicting comm<strong>and</strong> is issued, the conflicting comm<strong>and</strong> waits for the mmcrsnapshot comm<strong>and</strong> to<br />

complete. Conflicting operations include:<br />

1. Other snapshot comm<strong>and</strong>s<br />

2. Adding, deleting, replacing disks in the file system<br />

3. Rebalancing, repairing, reducing disk fragmentation in a file system<br />

If quorum is lost before the mmcrsnapshot comm<strong>and</strong> completes, the snapshot is considered partial <strong>and</strong><br />

will be deleted when quorum is achieved again.<br />

Because snapshots are not full, independent copies of the entire file system, they should not be used as<br />

protection against media failures. For protection against media failures, see General Parallel File System:<br />

Concepts, Planning, <strong>and</strong> Installation Guide <strong>and</strong> search on recoverability considerations.<br />

For more information on snapshots, see Creating <strong>and</strong> maintaining snapshots of <strong>GPFS</strong> file systems in<br />

General Parallel File System: Advanced <strong>Administration</strong> Guide.<br />

Parameters<br />

Device<br />

The device name of the file system for which the snapshot is to be created. File system names<br />

need not be fully-qualified. fs0 is just as acceptable as /dev/fs0.<br />

This must be the first parameter.<br />

Directory<br />

Specifies the name given to the snapshot. The name appears as a subdirectory of the .snapshots<br />

directory in the file system root. Each snapshot must have a unique name.<br />

Chapter 8. <strong>GPFS</strong> comm<strong>and</strong>s 131

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!