[gpfsug-discuss] gpfs snapshots

[Jez Tucker]

Hi

   I still think I'm coming down on the side of simplistic ease of use:

Example:

[jtucker at pixstor ~]# mmlssnapshot mmfs1
Snapshots in file system mmfs1:
Directory                SnapId    Status  Created                   Fileset	Comment
@GMT-2016.09.13-23.00.14 551       Valid   Wed Sep 14 00:00:02 2016  myproject	Prior to phase 1
@GMT-2016.09.14-05.00.14 552       Valid   Wed Sep 14 06:00:01 2016  myproject  Added this and that
@GMT-2016.09.14-11.00.14 553       Valid   Wed Sep 14 12:00:01 2016  myproject  Merged project2
@GMT-2016.09.14-17.00.14 554       Valid   Wed Sep 14 18:00:02 2016  myproject  Before clean of .xmp
@GMT-2016.09.14-17.05.30 555       Valid   Wed Sep 14 18:05:03 2016  myproject  Archival


Jez



On 14/09/16 19:10, service at metamodul.com wrote:
> Why not use a GPFS user extented attribut for that ?
> In a certain way i see GPFS as a database. ^_^
> Hajo
>
>
>
> Von Samsung Mobile gesendet
>
>
> -------- Ursprüngliche Nachricht --------
> Von: Jez Tucker
> Datum:2016.09.13 11:10 (GMT+01:00)
> An: gpfsug-discuss at spectrumscale.org
> Betreff: Re: [gpfsug-discuss] gpfs snapshots
>
> 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>
>


-- 
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/20160914/568022b8/attachment-0002.htm>