Big Wave Dave wrote: > On 1/3/07, Gary V <[EMAIL PROTECTED]> wrote: >> >It finally finished the restore. >> > >> >For the sake of information to help future users.... >> > >> >The "backup" file being used to restore into the new SQL database was >> >99MB and took 17hrs to import on my AMD 1.2Ghz machine with 1GB of >> >RAM. >> > >> >Dave >> >> Could be your database was not expiring. Probably a good idea to do a >> --force-expire prior to a backup. Just curious, If you run --force-expire >> now, what does --dump magic look like? >> >> Gary V >> > > Here are the numbers... > [EMAIL PROTECTED] ~]# sa-learn --dump magic > 0.000 0 3 0 non-token data: bayes db version > 0.000 0 253 0 non-token data: nspam > 0.000 0 580 0 non-token data: nham > 0.000 0 3637103 0 non-token data: ntokens > 0.000 0 1167206400 0 non-token data: oldest atime > 0.000 0 1167890964 0 non-token data: newest atime > 0.000 0 0 0 non-token data: last journal > sync atime > 0.000 0 1167891012 0 non-token data: last expiry atime > 0.000 0 0 0 non-token data: last expire > atime delta > 0.000 0 0 0 non-token data: last expire > reduction count > [EMAIL PROTECTED] ~]# sa-learn --force-expire > [EMAIL PROTECTED] ~]# sa-learn --dump magic > 0.000 0 3 0 non-token data: bayes db version > 0.000 0 253 0 non-token data: nspam > 0.000 0 580 0 non-token data: nham > 0.000 0 3637103 0 non-token data: ntokens > 0.000 0 1167206400 0 non-token data: oldest atime > 0.000 0 1167890964 0 non-token data: newest atime > 0.000 0 0 0 non-token data: last journal > sync atime > 0.000 0 1167891646 0 non-token data: last expiry atime > 0.000 0 0 0 non-token data: last expire > atime delta > 0.000 0 0 0 non-token data: last expire > reduction count > [EMAIL PROTECTED] ~]# > > It would appear to me as if it hasn't changed the number of tokens at all. >
Run with -D, it will probably tell you there wasn't enough difference to run the expire. The SQL import works just like you were learning the tokens, so the atimes are updated accordingly. Over time the atime differences will be enough that you are able to expire. Someone else mentioned it but I'll followup, probably your auto-expire has either been broken (do you use MailScanner of Amavis or something like that?) for some time. Before you backup, you should run sa-learn --force-expire to clear things out. Its obviously too late for that now. Give it a few days to update the database and you'll be able to start expiring out data. It may take a few weeks for you database to get enough diversity in the atimes to get down to the configured 150k token level. Michael
