🚀 go-pugleaf

> If you want DECnsr to make a full backup of your 160GB every week, and
> wants that users can browse into the indexes for the last 4 years, you
> will surely have a big amount of indexes !

No, what I meant is that we have 160 Gb on our backup tapes - that's
the total size of the full saves, weeklies and dailies.  Some of those
full saves date back almost a year at this point.  What I'm wondering
is what's the ratio between the number of files backed up (or the size
of the backups) and the amount of space that the online index takes up
- I'm trying to estimate how large an index would be in our case for
all of our existing backups, and how useful a partial index would be
given N Mb of disk space to play with (eg, how far back would the
index reach and still fit within N mb).

If someone could give me a number like "10% of the amount backed up"
or "15kb per file backed up" or something, I could make reasonable
and useful estimates.

> So in your current environment, I propose you to make a full backup every
> month (or 2 or 3), and incremental backups every day (or week).
> In addition, I propose you to keep a one-year on-line indexes, no more.

We do full saves once a month, level 2's once a week and level 9's
twice a day, 12 hours apart (so the most we should lose "at most" 12
hours of work).  If the 10% figure is correct, then we're talking
about 16Gb worth of indices for the last 8 months of backups, which is
what I'm calling absurd - I don't have that much disk space to burn at
the moment.  I'm glad to hear that you could trim the online index,
though - I imagine one could work out a happy medium, since having
such an index would be very nice, especially for the recent backups
which are used more frequently.

--- Steve