[DGD] Primary vs secondary snapshot

[Raymond Jennings]

I noticed that DGD only even tries to open the secondary (full) snapshot if
the first one is marked as partial.  Which isn't even always the case if
you cold boot and do nothing but incremental snapshots.

So I've had my script just see if both exist, and then use both, and trust
dgd to simply ignore the second snapshot if it doesn't need it, since the
first one is current and has the flags needed to tell dgd if it needs the
full one.

Is this correct?

On Tue, Nov 10, 2015 at 2:59 PM, Raymond Jennings <shentino at gmail.com>
wrote:

> To all reading:
>
> I learned this the hard way when DGD aborted after running out of disk
> space.
>
> Also, fresh fix related, pull latest from dworkins' github for dgd
>
> On Tue, Nov 10, 2015 at 1:46 PM, Felix A. Croes <felix at dworkin.nl> wrote:
>
>> Raymond Jennings <shentino at gmail.com> wrote:
>>
>> > I noticed that during creation of an incremental snapshot, the full
>> > snapshot is moved to blah.old, and the swapfile is moved to blah and
>> > further swapping goes to blah as the incremental snapshot, while the
>> full
>> > snapshot remains at blah.old
>> >
>> > Is this correct?
>> >
>> > Second question:
>> >
>> > If so, is there any way to distinguish a full blah and a stale blah.old
>> > from a full blah.old and an incremental blah without having the mudlib
>> > posting a file somewhere for external scripts to read?
>>
>> Correct, and the only way to tell is to start DGD with the latest
>> snapshot.  If it's incomplete and the old snapshot is also needed, DGD
>> will tell you.
>>
>> It's a good idea to keep around the latest full snapshot for backup
>> purposes.  It is also a good idea not to create too many incremental
>> snapshots, as they tend to bloat the snapshot size.
>>
>> Regards,
>> Felix Croes
>> ____________________________________________
>> https://mail.dworkin.nl/mailman/listinfo/dgd
>
>
>