Compact takes forever to run

We are running a scheduled compact task (compact -B) on mail servers overnight which takes over 24 hours to run on approx 3000 databases (average size 150MB). Is this reasonable or not?

Subject: Compact takes forever to run

Depending on your hardware, yes this is reasonable. You might not want to run “-B” option except once a weekend. “-b” is better to run at night and you might want to add “-S 10” to only compact databases over 10% unused space.

We have found on our pseries with SAN, that running 8 compactor tasks over 5 processors reduces the total time significantly vs 1 compactor. If you have the disk speed to handle this load. We have 1.5 TB of mail files so instead of weeks running, it now takes only days.

Subject: just to add: the nightly “-b” option will reduce the work done by the weekly “-B”

Subject: RE: Compact takes forever to run

We have Transactional Logging running so -S 10 no longer works. I’ll try -b and see how it goes.

Thanks

Subject: RE: Compact takes forever to run

The compact -b took about 6 hours less than the -B but one of the reasons for running -B is to reduce the size of the mail files that are backed up. Has anyone any ideas whether it is possible to achieve this?

Subject: Yes, but how much quicker are the -B backups when you’re doing nightly -b backups?

Subject: Not much difference

Thanks for the thought but sadly it only took 7 minutes less this weekend than last - still about 18 hours.