Enterprise Vault Server Overloaded

Hi,

We have 1 EV Server (EV 2007 SP2) running on a Win2003 (x86) hardware.

We have approx 1500 Exchange Mailboxes which we are archiving. We also have Journal archiving enabled.

SQL Server for EV is local on this same server.

The issue we are currently facing is, when the users try to search their archived emails, the searches are timing out intermittently.(http timeouts)

When I look at the EV Server's load at that time, the CPU is maxing out. (Mailbox archiving task runs during the day).

I am considering the following
  • Moving the SQL Server to a different Server
  • Moving the index volumes to a different server
I am looking for suggestions with regards to improving performance of EV searches. Any help would be greatly appreciated.

Cheers,
1 Solution

Accepted Solutions
Highlighted
Accepted Solution!

document

document http://support.veritas.com/docs/314694

Can the SQL server be located on the same server as Enterprise Vault
Details:
SQL and Enterprise Vault can exist on the same server but is only recommended for pilot or demonstration configurations. In production Enterprise Vault environments it is recommended to install on separate computers.

If installed on the same server there may be performance issues. It is recommended to review the Performance Guide and Installing and Configuring Guide for more information on the hardware requirements. For additional information on the version of SQL that is supported refer to the Compatibility Guide.

Related Documents:

276547: Symantec Enterprise Vault (tm) 6.0, 7.0, 2007 and 8.0 Compatibility List (includes Partner products) - Updated March 31st, 2009
http://support.veritas.com/docs/276547


288395: Symantec Enterprise Vault 2007 - Performance Guide (updated March 2008)
http://support.veritas.com/docs/288395


305429: Symantec Enterprise Vault 2007 - Installing and Configuring Guide
http://support.veritas.com/docs/305429

I think you must consider to move your sql server databases

View solution in original post

9 Replies
Highlighted
Accepted Solution!

document

document http://support.veritas.com/docs/314694

Can the SQL server be located on the same server as Enterprise Vault
Details:
SQL and Enterprise Vault can exist on the same server but is only recommended for pilot or demonstration configurations. In production Enterprise Vault environments it is recommended to install on separate computers.

If installed on the same server there may be performance issues. It is recommended to review the Performance Guide and Installing and Configuring Guide for more information on the hardware requirements. For additional information on the version of SQL that is supported refer to the Compatibility Guide.

Related Documents:

276547: Symantec Enterprise Vault (tm) 6.0, 7.0, 2007 and 8.0 Compatibility List (includes Partner products) - Updated March 31st, 2009
http://support.veritas.com/docs/276547


288395: Symantec Enterprise Vault 2007 - Performance Guide (updated March 2008)
http://support.veritas.com/docs/288395


305429: Symantec Enterprise Vault 2007 - Installing and Configuring Guide
http://support.veritas.com/docs/305429

I think you must consider to move your sql server databases

View solution in original post

Highlighted

Move SQL onto a dedicated

Move SQL onto a dedicated SQL server. You can move indexing but it makes no sense what so ever, technically its possible, but I don't know anyone doing this as it brings no benefit, it will just slow things down as you parsing data over the network, so your bottle neck would be there.

The biggest problem you have is SQL, move that off and you will be fine, I have had up to 20,000 active mailboxes on one Enterprise Vault server, and archiving was not a problem and seeing as you have 1,500 users that's nothing my laptop with a dedicated SQL server would most probably out preform your single server with SQL on it Smiley Happy

--wayne

Highlighted

If it were me I would Move

If it were me I would Move SQL to it's own server

Move Mailbox Archiving to it's own server and leave Journaling on the present hardware

Journaling does not add much load but Mailbox Archiving will and so will SQL so it is best to keep them seperate

Highlighted

If you think this solution is

If you think this solution is ok, don't forget to vote it and mark it as solved
Thanks

Highlighted

huh?

Hi,

Hold on a minute guys.  The guy says he is running mailbox archiving during the day.  that's the key issue I think. 

So why are you doing that?

My thinking is if journalling is using CPU during the day and mailbox archiving during the night then I am not sure I see a problem.


Highlighted

I sorta agree, but believe

I sorta agree boss, but believe the bigger issue is SQL. Its simple enough to test, just move your archiving schedule to out of hours. However I bet you you will be migrating SQL Smiley Happy
Highlighted

Thanks Guys

Thanks for your prompt replies guys. Much appreciated.

I agree with Nicola Rositani's solution. It does make sense and is according to the recommendation from Symantec.

I will give it a go and see.

Thanks Wayne Humphrey, your explanation of why it does not make sense to move indexing to a different server seems reasonable.

Beta dodo, you mentioned a good point but the reason we are running our Mailbox Archiving task during the day is, at night we run the backups which puts EV into read-only mode.

Cheers,

Highlighted

Re: Move SQL onto a dedicated

I realize this is an old thread, but we've already have SQL on a dedicated server and performance is still poor. It's not CPU, I suspect the issue is with IOPS. We're considering separating the indices to a separate server to offload seach activity from the server doing the archiving. Are there guidelines for building our a dedicated search/index server?

Highlighted

Re: Move SQL onto a dedicated

Hello,

You can best open a new thread, describing your question. That would assist better.

Thanks.

Regards. Gertjan