Re: More on daily backups..

[On 21 Jan, @00:02, James wrote in "Re[2]: [hdup-user] More on dai ..."]
> Hi - Been looking into this a bit more. It's maybe a bit tricky. The
> files are technically 'created' each day. They "mysqlhotcopy" program
> copies every single table file to a temporary area, which I back up.
> However, the copy retains the date stamp of the original table, most
> of which rarely change so these dates are often at least several weeks
> in the past.

which datestamp? You have: (from 'man 2 stat')

time_t        st_atime;    /* time of last access */
time_t        st_mtime;    /* time of last modification */
time_t        st_ctime;    /* time of last status change */

> \backup\toarchive\mysql\databasename\table.MYI

btw, what kind of filesystem is this? And what timestamps are
supported on that?

> gets created daily in my hdup prerun script, then deleted in the
> postrun script. But it should be identical in every respect, and the

tar (which ofcourse does the actual backup) doesn't use a file contents
nor does it use hashes to compare files and to decide what to backup

> date stamp certainly looks identical to the untrained eye. Is there
> some other bit of information that's causing HDUP to realize it hasn't

It has been too long for me, but in the tar source you should be able to
see what tar is using to decide what to backup.

> just been sitting there for a day or week? If so, how else could I
> avoid having these files re-backed up every day. It's making my daily
> files about 70 megabytes bigger than needed.

make the prerun script a lot smarter? :) maybe using 'stat' yourself on
the dumped database file?

grtz Miek