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 />

Options<br />

NONE<br />

If you do not want traverse the file system’s root to access the snapshot, a more convenient<br />

mechanism that enables a connection in each directory of the active file system can be enabled<br />

with the -a option of the mmsnapdir comm<strong>and</strong>.<br />

Exit status<br />

0 Successful completion.<br />

nonzero A failure has occurred.<br />

Security<br />

You must have root authority to run the mmcrsnapshot comm<strong>and</strong>.<br />

You may issue the mmcrsnapshot comm<strong>and</strong> from any node in the <strong>GPFS</strong> cluster.<br />

When using the rcp <strong>and</strong> rsh comm<strong>and</strong>s for remote communication, a properly configured .rhosts file must<br />

exist in the root user’s home directory on each node in the <strong>GPFS</strong> cluster. If you have designated the use<br />

of a different remote communication program on either the mmcrcluster or the mmchcluster comm<strong>and</strong>,<br />

you must ensure:<br />

1. Proper authorization is granted to all nodes in the <strong>GPFS</strong> cluster.<br />

2. The nodes in the <strong>GPFS</strong> cluster can communicate without the use of a password, <strong>and</strong> without any<br />

extraneous messages.<br />

Examples<br />

To create a snapshot snap1, for the file system fs1, issue this comm<strong>and</strong>:<br />

mmcrsnapshot fs1 snap1<br />

The output is similar to this:<br />

Writing dirty data to disk<br />

Quiescing all file system operations<br />

Writing dirty data to disk again<br />

Creating snapshot.<br />

Resuming operations.<br />

Before issuing the comm<strong>and</strong>, the directory structure would appear similar to:<br />

/fs1/file1<br />

/fs1/userA/file2<br />

/fs1/userA/file3<br />

After the comm<strong>and</strong> has been issued, the directory structure would appear similar to:<br />

/fs1/file1<br />

/fs1/userA/file2<br />

/fs1/userA/file3<br />

/fs1/.snapshots/snap1/file1<br />

/fs1/.snapshots/snap1/userA/file2<br />

/fs1/.snapshots/snap1/userA/file3<br />

If a second snapshot were to be created at a later time, the first snapshot would remain as is. Snapshots<br />

are made only of active file systems, not existing snapshots. For example:<br />

mmcrsnapshot fs1 snap2<br />

132 <strong>GPFS</strong>: <strong>Administration</strong> <strong>and</strong> <strong>Programming</strong> <strong>Reference</strong>

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

Saved successfully!

Ooh no, something went wrong!