Mark S. wrote:
>
> I'm working on the new timestamp and subdirectories routines.
>
> I think adding zips to a single archive would be inadvisable since as it
> increases in size it will take
> longer and longer for the backup to process. Eventually it will probably
> crash.
>
Okay. Understood.
> An ambitious enhancement would be to delete all but the last x number of
> backups. Of course, it's
> always a little worrying to be deleting things.
>
I agree that it will eventually need some kind of ("periodic"??, once a
session?) backup management. If a user fully went Polly with a bunch of
wiki especially, with auto-save on, running in auto-mode at 60 secs, the
numbers of backups could get very high quickly.
FWIW, I had a quick look around at .ps1 backup related scripts that manage
"spread" of "preserved" backups (i.e. schemas like 1 a day, 1 a week, 1 a
month etc) based on date matching. I didn't find one that fitted our use
case perfectly but there may be one that could handle the problem?
Another approach might be, rather than delete, to move all files that would
be deleted into zip-archive (in this case I think possible failure on zip
would be lower as its performed once) in a different directory? The user
then manually decides to delete them??
Thoughts
TT
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/22e7ff5e-91e1-46f6-aa06-843b105a7c1f%40googlegroups.com.
