How much memory and disk space does a SEPM server need?
As part of our antivirus upgrade process, I've install SEP Manager on a virtual server with 2GB of RAM and about 30 GB of disk space. I've created a site, with an embedded database and moved 4 client so far to that site (our target configuration, presumably on a larger production server, will manage up to 3500 clients).
Now that the manager is active, I've been seeing a constrant stream of "Server Health Notification" messages, which are evidently triggered by a shortage of disk space. Right now, for example, the server has about 298MB of free disk space. There were about 10GB of free space available after I installed SEPM a few days ago, so the space is getting consumed pretty quickly.
I can't figure out how much space I really need (if it's like this for four clients, what will happen when we have thousands?) and in general I don't know what configuration changes I could make that would reduce the demand for space.
Can anyone give me advice? Is there documentation anywhere that might help answer my questions?
Comments
How many content revisions
How many content revisions are you having your SEPM store in it's database. Our best practice guide suggest 42 content revisions so the SEPM can be out of date for 2 weeks before it has to download a full virus definition instead of the delta updates. The downside to this is that the 42 content revisions are about 10 gigs in size. So you would see these content revisions starting to appear after you start up the SEPM. Maybe this is the problem? For more info on the best practice guide that suggest the 42 revisions visit this link: http://service1.symantec.com/support/ent-security....
Hope this helps,
Grant
Please don't forget to mark your thread solved with whatever answer helped you : )
How can I tell how many
How can I tell how many revisions are being stored, and how much space they're taking?
Is there a file name I can search for?
I do know that I've left the number at the default value of 30.
Would it help to un-check the "store client packages unzipped..." option?
Ideally, you would put the
Ideally, you would put the database on a different volume! This way you can grow it as needed.
Oh and at 3500 users, you are at the cusp of where SQL would be something to look into. While the embedded can support up to 5000 clients... It doesnt mean you should. Kind of like where MS says Vista only needs a Gb of RAM?!
There is an online portal, save yourself the long hold times. Create ticket online, then call in with ticket # in hand :-) http://mysupport.symantec.com "We backup data to restore, we don't backup data just to back it up."
Can you move an embedded
Can you move an embedded database to a new drive? What is involved in doing this?
If managemement agrees, I
If managemement agrees, I think I'll try reinstalling SEPM, this time with SQL Server. If we have these problems now, with only four clients, I can only imagine what space nightmares we'll have when we go to production with 3500 clients. SQL Server might not eliminate the space issues, but it will offload them to another group that is better equipped to deal with them.
Thanks to everybody for useful suggestions.
How much space on C drive and SQL
I've noticed that when you load SEPM on a server, the C drive requires about 8-12 Gig of disk space just for the SEPM piece regardless of whether you do an embedded or SQL database.
I've been trying to replicate, thinking that the database would take care of my sizeable data growth. When you replicate, the C drive seems to require at least 10-15 Gig.
Why is this and how much will it grow - given that I will use a SQL database on the Primary and the replication partner???
thanks
Would you like to reply?
Login or Register to post your comment.