search

Marxsal / polly

Batch file system to restore TiddlyWiki files from download directory to their original home directory
9 stars 1 forks source link

Maintenance of backup dirs #19

Open Marxsal opened 5 years ago

Marxsal commented 5 years ago

The backup dirs may become untidy. I'm thinking a menu item that will trim the directory to one file a week. But I regard this as a useful enhancement, not as a must-have. Also, there is the liability that occurs whenever files are deleted.

TiddlyTweeter commented 5 years ago

IF user has auto-download on in wiki/browser; edits things a lot; auto-monitors in seconds ... that could spawn large numbers of backups very quickly. I do think pruning will be needed in some situations.

However, I get nervous deleting things. The trouble is we can do the backups easy now, but managing backups, retained or deleted, is another story. Spacing? How many, etc?

Maybe this should be for a semi-separate specialised tool later?

TiddlyTweeter commented 5 years ago

Just FYI: Both PMario and Riz implemented "Towers Of Hanoi" well in their backup plugins. I looked for a PS library that can do it but haven't found one yet.

TBH I'd be nervous about any arbitrary cut-off date. I'd think spread is better, if you know what I mean.

Marxsal commented 5 years ago

I believe the way PMario (don't know about Riz) did TOH was to actually label the backups as they occurred, like myfile (A), myfile(B)...

The thing about TOH, is it assumes that your need for a file is geometric over time. That is, there are 8 backups, then there will be 8 backups whether your data set consists of everything you did this week, or everything you did over 3 years. I'm thinking that a more realistic approach might be to keep all backups from the past week, one backup each week for one month, and then one monthly backup a month forever.

Of course, both approaches are misnomers, since they don't actually backup anything. A true backup needs to send files off to another device or cloud. But I digress.

TiddlyTweeter commented 5 years ago

@Marxsal ... both approaches are misnomers, since they don't actually backup anything. A true backup needs to send files off to another device or cloud.

Actually I agree. And its a not a digression in the sense that: Is it better to emphasise proper replication to another device first, over smart pruning. TBH I think fundamental of backup to separate device matters most.

Marxsal commented 5 years ago

Re backups, per your other comments, it should be possible to upload genuine backups to cloud sites? It's apparently possible to install git on powershell, so you could even push backups to your own GH repository. Definitely gilding the lily, or something.

TiddlyTweeter commented 5 years ago

@Marxsal ... realistic approach might be to keep all backups from the past week, one backup each week for one month, and then one monthly backup a month forever.

I slept on this. Actually, when I think about actual usage of backups for TW my single most common case is in the last 24 hours Why? Because TW has no "Undo" function. I have, quite often, used TW backups as a surrogate "undo".

So there is me thinking again ... Wondering IF we might be able to do sequential restores from backups via the Polly interface?

This tool is frightening! :-)