Re: More on daily backups..

On Wed, 2003-12-31 at 11:45, James Treworgy wrote:

> Two odd things are happening. The huge log files are still being
> backed up (e.g. they were in the 12-31 daily backup) even though their
> last update date was 12-29. I would have expected them to get backed
> up once more after I switched to a rotating log cycle but then never
> again in an incremental. Why would these files keep getting archived?
> For that matter - why would ANY file with a date stamp more than 24
> hours before the previous daily backup get archived in the daily?

The daily contains all files changed /since the last weekly dump/ - not
just since yesterday.  This avoids needing to access more than one daily
dump in order to do a full restore, and makes it safe to delete daily
dumps that are older than you need.

If you make a large number of changes one day - bulk renames or
additions of large files - it is most efficient to force a weekly or
monthly update immediately afterward.  You may be able to do that by
deleting the etc/inclist.weekly or etc/inclist.monthly files (at least
that works with my crontab and configuration).

> 
> Also - every single file from the mysql snapshot is getting archived.
> In many cases, these tables are relatively static and some have not
> been updated in months. The snapshot generated by mysqlhotcopy
> maintains the date stamp of the actual table, so the daily archive
> reflects lots of files with very old date stamps.

I used to have a few files that got archived every night, it turned out
the date stamps were wrong (in the far future).  I don't think there
should be any reason that old files should show up anywhere but in the
full monthly dump, unless you've changed your include/exclude settings
since the monthly was run.

Bng
--
Boris Goldowsky