Stored utility

There is no need to run any of the stored commands manually under normal circumstances.

To understand better what the commands do, please look at the documentation. I'm going to assume you're running 6.2, though you've not said. Here's a link to the various commands:

http://docs.sun.com/app/docs/doc/819-2651/6n4u5ce7b?a=view#acmes

running a simple

stored -v should give you exactly the same results as running

stored

by itself, just more screen data.

And, running "stored" by itself is not one of the flags that's documented. I wouldn't do that. . . . . . .

What the output you show tells me, is that it's doing an expire run. Similar to "imexpire". If you have message expiration rules, then they're being applied.

If your system is "under stress" at peak load, then I would not run extra commands, unless you're prepared for your system to be under even more stress. Stress is defined as high load average, long i/o wait times, and such. A system under stress will run slower, may build up transaction logs, and eventually may crash.

If your system is not under stress at peak load, then it's no problem. Running any store-wide command will add disk load to the system. you need to understand that.

jay_plesset at 2007-7-7 3:47:42 >

Hi,

The only time you should need to run stored from the command line is if you are trying to debug some kind of problem and have been instructed to by Sun Support. Even then you would only want to run the command outside business hours to reduce risk and I/O load on the system.

With older versions you used to run stored to check the output of expiration rules, but this functionality was replaced by imexpire.

>> 1. whether i can stop the stored utility within a minute after checking

outputs?

This should be OK, but why are you running the command at all?

>> 2. After this migration i have to provide dat to day maintenance support

>> to this messaging server? so can you tell me at which situation i have

>> to run this stored utility (whether once in a week or if i encountered any

problem )?

As above. In 4 years of running 4 servers for 100,000+ accounts, I never had to run the stored utility manually.

Regards,

Shane.

shane_hjorth at 2007-7-7 3:47:42 >

> Hi JAY,

>

>

> --

> last pid: 14135; load avg: 0.44, 0.44, 0.39;

> up 17+22:20:53

>

> 1:44:56

> 105 processes: 102 sleeping, 1 zombie, 2 on cpu

> CPU states: 77.9% idle, 15.3% user, 3.4% kernel,

> 3.3% iowait, 0.0% swap

> emory: 8192M phys mem, 5395M free mem, 31G swap, 31G

> free swap

>

Was this taken at peak usage, or a quiet time? If at a quiet time, it's not of much use to our discussion.

> This is our new setup for 750000 users and rightnow

> it is migration

> so only less number of users are in this server and

> i'm new to

> messaging so i'm eager to run this stored utlity and

> check the out puts ?

What is it you're trying to get? The stored utility isn't really for "checking outputs", it's more of a utility to be used when you need it.

> Now i think there will not be any problem in running

> stored utility on this server because it has less

> load average and it just remove the

> temporary files and sync database ?

Why do you think you need to do that?

>

> Now my question is

>

> 1. whether i can stop the stored utility within a

> minute after checking

>outputs?

I personally would not be messing with the stored utility, unless you have an indication that you truly need it.

I also would be CAREFUL stopping any utility that updates the database. If it dies without removing locks, you will have to restart your Messaging Server.

Again, what end result are you looking for? Why do you believe you need to run the stored utility?

> maintenance support

> to this messaging server? so can you tell me at

> which situation i have

> to run this stored utility (whether once in a

> week or if i encountered any

>problem )?

I run a small server myself. In 3 years, I have NEVER run the stored utility.

I have run the imexpire utility in "test" mode, while I was setting up expiration rules, but once that was done, I let the automatic system run it nightly.

After I had a power failure, and my system went down, hard, after fsck on the disks, I ran reconstruct -m

and

reconstruct -r

though likely, I didn't need to.

I run

sa-learn to pick up spam I missed (that my users have placed in a spam-to-be-learned folder. This is SpamAssassin, not Messaging Server.

imsbackup to back my mail store up.

that's all.

You will need to monitor disk use, and make sure you don't run out of disk.

You need to monitor the size of the

mail.log

file, as Messaging Server will allow this file to grow without limit. It's up to you to trim it.

>

jay_plesset at 2007-7-7 3:47:42 >