How to do This ?

Bijay.Swain's picture
I have a SEPM server running with 1000 clients connecting to it. Now I have a spare server with me which I want to use it as a backup server for the main SEPM server.
 
I am using embedded database on my primary SEPM server. How can I setup my spare server as a backup server so that incase my 1st sepm server fails all the clients will transfer to the backup server and get updates from that server and also with the same policy.
Swaminathan's picture

Hi Bijay, If you were running

Hi Bijay,

If you were running SEP with a SQL DB then you could just configure failover.

In your scenario with Embedded BD you have to configure replication to accomplish your task.

Check the following links,

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

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

pete_4u2002's picture

failover is only supported

failover is only supported only if you are using the SQL DB.

If embedded DB, you may manually need to copy the server certificates and other configuration files.

Bijay.Swain's picture

I want to all  my clients to

I want to all  my clients to connect to the 1st sepm server only but if it fails/crashes then only clients should move to the backup sepm server.

can this be done with replication.

Rafeeq's picture

Hi

I did not read that you have embedded, this article should help you out, you need to add the ;management server list... to get the priority, clients try to communicate based on priority if they fail they switch to next server in the MSL 

What is Management Server List and how to configure Failover between replication partners using embedded database

https://www-secure.symantec.com/connect/articles/what-management-server-list-and-how-configure-failover-between-replication-partners-using-e

 Failover configuration causes one server to pick up the client communications load if another server becomes unavailable. Load balancing configuration causes servers to share the client communications load and automatically implements failover if one of the servers goes offline.

Rafeeq

aulia's picture

Replication partners is good

Replication partners is good if we have huge bandwidth. First time Installing SEP, have 9 SEPM server and over 7500 client, I have problem with that. So I decide to split them by region..

Bijay.Swain's picture

first time replication fails

first time replication fails because of insufficient disk space on the primary sepm server(site).the C:\Program Files\Symantec\Symantec Endpoint Protection Manager\data\replication on primary site increases its size while replication starts to more that 6 GB . how much space is needed on first site for replication .

Vikram Kumar-SAV to SEP's picture

 The database size will be

 The database size will be replicated so whatever size of SEM5 you see on your main sepm expect the same on replication partner.

Celebrating 2 years as a community member....

ben_cSEPticons_secured's picture

even if you dont have an SQL

even if you dont have an SQL Server and will setup a replication partner atleast you have a backup... Just follow mr. rafeeq given links...