Plan the snapshot location and interval based on the following:
Try to allocate five times as much space for the database and snapshots combined.
Reconfigure snapshots to run on a separate disk that is tuned to the system's needs.
Having a snapshot interval which is too small will result in a frequent burden to the system and a greater chance that a problem in the database will be copied as a snapshot. Having a snapshot interval too large can create a situation where the database will hold the state it had back when the snapshot was taken.
A snapshot interval of a day is recommended and a week or more of snapshots can be useful if a problem remains on the system for a number of days and you wish to go back to a period prior to point at which the problem existed.
Use configutil parameters to configure the snapshot location and interval, as described in To Specify Message Store Database Snapshot Interval and Location in Sun Java System Messaging Server 6 2005Q4 Administration Guide.