cancel
Showing results for 
Search instead for 
Did you mean: 

Storage Archive runs for about 1 minute and then stops processing.

plslakewood
Level 4
Partner Accredited Certified

Running EV 9.0.3 on Windows 2003 SP2 with Exchange 2003 SP2 servers. EV in MS Cluster.

 

We upgraded from 8.0.5 to 9.0.3 and this issue started.

 

The Storage Archive process will run for about 1 minute after it is restarted. A _com_error is displayed in the dtrace of Storage Archive and that is the only message seen. There are no Events displayed. Once we restart the SA resource (service) it continues processing what is in the storage archive queue.

1 ACCEPTED SOLUTION

Accepted Solutions

plslakewood
Level 4
Partner Accredited Certified

We are working with Symantec right now so will close this thread.

View solution in original post

4 REPLIES 4

JesusWept3
Level 6
Partner Accredited Certified

really need more detail than that to be honest.
You say that there is a COM error in the dtrace, what is the actual error then?
And when you restart the resource, it then continues on fine? or does it just run for a minute more and then stop again?

Does this happen on both nodes of the cluster?
Was this also in a cluster and working fine before the upgrade or did you convert to cluster after you upgraded?

What kind of item is it processing in the storage archive queue? does the queue ever move or is it just failing on the same item over and over again?

Is there any errors in the application or system logs of the event viewer?
 

https://www.linkedin.com/in/alex-allen-turl-07370146

plslakewood
Level 4
Partner Accredited Certified

We are working with Symantec right now so will close this thread.

JesusWept3
Level 6
Partner Accredited Certified

When you get it resolved, could you update the thread with the com error and what was done to fix it so that if anyone else runs in to issues they know what the resolution is?

Then i will update that post as the solution and you can get the full points for it too

https://www.linkedin.com/in/alex-allen-turl-07370146

plslakewood
Level 4
Partner Accredited Certified

The problem was caused by heavily fragmented SQL databases. 

 

The following technote discussed how to defrag the SQL databases:

 

http://www.symantec.com/docs/TECH74666