[gpfsug-discuss] gpfs snapshots

[Jez Tucker]

Hey Yuri,

   Perhaps an RFE here, but could I suggest there is much value in 
adding a -c <comment> option to mmcrsnapshot?

Use cases:

mmcrsnapshot myfsname @GMT-2016.09.13-10.00.00 -j myfilesetname -c 
"Before phase 2"

and

mmcrsnapshot myfsname @GMT-2016.09.13-10.00.00 -j myfilesetname -c 
"expire:GMT-2017.04.21-16.00.00"

Ideally also: mmcrsnapshot fs1 
fset1:snapA:expirestr,fset2:snapB:expirestr,fset3:snapC:expirestr

Then it's easy to iterate over snapshots and subsequently mmdelsnapshot 
snaps which are no longer required.
There are lots of methods to achieve this, but without external 
databases / suchlike, this is rather simple and effective for end users.

Alternatively a second comment like -expire flag as user metadata may be 
preferential.

Thoughts?

Jez


On 13/09/16 05:32, Valdis.Kletnieks at vt.edu wrote:
> On Tue, 13 Sep 2016 00:30:19 +0200, Lukas Hejtmanek said:
>> I guess we could reach snapid 100,000.
> It probably stores the snap ID as a 32 or 64 bit int, so 100K is peanuts.
>
> What you *do* want to do is make the snap *name* meaningful, using
> a timestamp or something to keep your sanity.
>
> mmcrsnapshot fs923 `date +%y%m%d-%H%M`   or similar.
> _______________________________________________
> gpfsug-discuss mailing list
> gpfsug-discuss at spectrumscale.org
> http://gpfsug.org/mailman/listinfo/gpfsug-discuss


-- 
Jez Tucker
Head of Research & Product Development
Pixit Media
www.pixitmedia.com <http://www.pixitmedia.com>

-- 

This email is confidential in that it is intended for the exclusive 
attention of the addressee(s) indicated. If you are not the intended 
recipient, this email should not be read or disclosed to any other person. 
Please notify the sender immediately and delete this email from your 
computer system. Any opinions expressed are not necessarily those of the 
company from which this email was sent and, whilst to the best of our 
knowledge no viruses or defects exist, no responsibility can be accepted 
for any loss or damage arising from its receipt or subsequent use of this 
email.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20160913/f148a878/attachment-0002.htm>