Re: export | import taking a really, really long time

Am 07.08.2012 16:22, schrieb Larry D'Anna:
> I'm trying to migrate a spam probe database over from an old machine.  The
> spamprobe version hasn't changed, (v1.4d is what it reports), but the version of
> the database lib has changed, so I can't directly use the old library.  The
> problem is that spamprobe export is generating what appears to be an unbounded
> amount of output.   It got up to 50G (for a 345M database) before I killed it.
> Now I'm running "spamprobe_old export | spamprobe_new import" so it doesn't fill
> up my whole disk, but it's been running all night and the new database is only
> 33M.   It doesn't appear to have grown at all since I checked it before going to
> sleep.
>
> Any ideas?
>
> Thanks.
>
>

How did you run the initial export that generated 50 GB of data? Using 
the new spamprobe with the old database file?

This sounds as if you were using non-hash DB before and are now using a 
fixed-size hash DB with a size of 32 MB. If the database lib has changed 
(potentially making the DB files incompatible), your only option is 
indeed to run an export using the old spamprobe with the old database 
file and an import using the new spamprobe with a new database file. But 
you need to make sure that spamprobe is compiled with the correct 
database (PBL, Berkeley DB, ...) and that you choose the correct mode 
for your new spamprobe database file (see the "-d" option).


Cheers,
Thomas.


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/