Endpoint Protection

hi.

i typically install the sep console on xp pro boxes.

is there a docuement the discusses how to backup the sep configurations?

can one transfer this backup to another computer (say the sep console computer is stolen for example) and have it work?

thanks.

Its recommended that SEPM should be installed on machine that have Server OS installed. However it can be installed on XP machines as well.

To backup the database go through the following document.

Best Practices for Disaster Recovery with the Symantec Endpoint Protection Manager

http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007082112135948

How to back up, restore and or move the Symantec Endpoint Protection Manager (SEPM) and embedded Database to another disk or system

http://service1.symantec.com/support/ent-security.nsf/docid/2007102607432048

 

How to change the location of the database backup folder created by Database Backup and Restore Wizard in Symantec Endpoint Protection

http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008010223062548

You can change the default location of the backup and it will be stored on a remote machine.

 In a nutshell, RTFM.

The "installation guide," within the install media on BOTH discs, the very last chapter titled...  Wait for it, wait for it..  "Disaster Recovery."

Step by step on what is needed to backup a SEPM and restore it to re-establish communications from client to server.

You are simply running the JAVA console on the XP machines - NOT the SEM manager. There is NO configuration stored locally.
It's all on the SEM server database. So, you do not need to backup anything specific on your XP boxes since if they got wiped, all you'd do is go back to the SEM server address:9090 and it would reinstall the JAVA console, connect to the management SERVER and off you'd go!
ALL critical data is in the databases, either SQL or the embedded, however you installed and configured it.
So don't sweat the XP machines, you can blow any one or all of them away and SEP and SEM live happily on..............

Now - IF you indeed installed the MANAGEMENT SERVER piece on the XP machine, then follow the database backup instructions. IF you have the MANAGEMENT piece installed on a server and run the CONSOLE from the XP machine,, don't worry about XP.
You didn't specify if you were running the management server on the XP machine as well but simply referred to the console, which you can run on any computer, XP, the SEM server, some other server, Vista, etc., since the CONSOLE is strictly the interface you use to access the Symantec Endpoint Manager.........

Oops.  Should have been more clear on my question :-)

I do run the both console and database on a singe XP box.  Here is my reasoning and if somebody could comment as to good idea, bad idea  that would be really helpful as I have not yet rolled out 11 - only in test mode to this point.

I really hesitated on placing the database/console on the server or servers.  These server machines are already so overloaded that placing another high overhead app concerned me.  Even in cases where I have an additional server or two as well as the domain controller, I hesitate to add yet another database intensive app.

My thinking was to isolate an XP box, give it the RAM and disk space and single IIS site it needed and place the database and console on it.  In these cases, only the SEP software is installed.  So far, things have worked well in the lab.

But i will say that SEP has proven to be VERY sluggish.  Running this app on a P4 with SATA 7200 and 2GB RAM is slow.  The disk at times will chug, chug, chug.  With nobody using this box, not a problem.  But, I'm convinced that if this (the database) was on a server that at certain times where the SEP database is working (policy work/management or updating clients) it would degrade performance on even the best server hardware (quad core, 4GB & striped raid on 15K SCSI).

  

Hi OIStaff,

It's a fair enough solution to put it on an XP box, but obviously if you were to put it on a server with the specs you've mentioned you will get a performance improvement (maybe not the best bang for buck though). 

Another major factor is the amount of clients you have, how you've setup your groups/locations and fine tuned everything.  If you are looking at a large amount of clients then you may well need to consider a seperate SQL server to help spread the load.

If you are going through testing then you are probably contsantly in and out of the console which believe me does exaggerate the pain.

Sorry, I have to disagree big-time. XP and it's overhead are an issue.
The server OS is made to deal with such things, XP is laden down with patch after patch, doesn't deal with databases or high drive subsystem throughput needed.
A server OS with 4gig will make it run MUCH better.
XP is fine for testing, but it's holding you back.
When I put SEP/M on the servers instead of the "test boxes" I was using, things improved and there's been no speed decline seen in our SQL server because of it.
The manager needs DATABASE space - and it's drive intensive. That drive system you have is not going to handle a full load once that database starts going.
XP can only handle 2 gig RAM, and that's the bare minimum I'd run SEM under.
Part of the issue is the slowness of the JAVA console or interface, too. Run the manager on a server, put the data in SQL, and use the console on your XP or Vista or Windows 7 machines, but I'd never judge SEP/SEM based on how it runs on XP.

if you are have a large no of clients it is better to use a sever os instead of windows xp because windows xp having a limitation  of 10 concurrent tcp connections.It is also advisable to keep your database not in os drive because it can affect the performance.As mentioned in the earlier post if you having a large no of clients install sepm and database in different servers because database always will use a high amount of memory and if both are in same machine it can affect the performance...