Video Screencast Help

Difference between Replication and Failover

Created: 06 Jan 2012 • Updated: 06 Jan 2012 | 5 comments
Rao's picture
This issue has been solved. See solution.

Hello,

Could someone please explain the difference between Replication and Failover

Comments 5 CommentsJump to latest comment

Mithun Sanghavi's picture

Hello,

These are 2 different Concept.

To explain, I would suggest you to check these Articles below:

For  Failover and Load Balancing

1) About failover and load balancing

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

2) About Load Balancing and Failover Clustering in Symantec Endpoint Protection 11.0

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

3) About installing and configuring the Symantec Endpoint Protection Manager for failover or load balancing

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

4) Installing a management server for failover or load balancing

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

Check this Thread:

https://www-secure.symantec.com/connect/forums/failover-concept

 

REPLICATION

1) About installing and configuring Symantec Endpoint Protection Manager for replication

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

2) Installing Symantec Endpoint Protection Manager for replication
 
 
3) What is Management Server List and how to configure Failover between replication partners using embedded database.
 
 
 

Mithun Sanghavi
Senior Consultant
MIM | MCSA | MCTS | STS | SSE | SSE+ | ITIL v3

Don't forget to mark your thread as 'SOLVED' with the answer that best helped you.

Rao's picture

Mithun,

Please make it simpler.

Thanks and Regards,

S.Rao

Mithun Sanghavi's picture

Hello,

To Explain:

1) Failover

In a failover configuration, all clients send traffic to and receive traffic from server 1. If server 1 goes offline, all clients send traffic to and receive traffic from server 2 until server 1 comes back online.

Load balancing occurs between the servers assigned to Priority 1 in a Management Server list. If more than one server is assigned to Priority 1, the clients randomly choose one of the servers and establish communication with it. If all Priority 1 servers fail, clients connect with the server assigned to Priority 2

Failover configurations are used to maintain communication when clients are unable to communicate with a Symantec Endpoint Protection Manager. When all management servers at a higher priority level become unavailable, clients switch to failover servers, which are defined by their lower priority level in the Management Server List. At every heartbeat, clients check to see whether there is a higher priority server available. If there is, the clients switch to it immediately.

Whenever possible, failover servers should be at the same site as the management servers that they back up. All management servers at the same site share one database, so that data consistency is guaranteed. It is possible to configure management servers that are replication partners as failover servers, but there is a risk of data inconsistency between replication partners because replication does not always take place frequently enough.

Failover and load balancing installations are supported only when the original Symantec Endpoint Protection Manager uses Microsoft SQL Server. The SQL Server Native Client files also must be installed on the computer on which you install a site for failover or load balancing.

You do not install servers for failover or load balancing when the first Symantec Endpoint Protection Manager site is configured to use the embedded database.

Reference:

https://www-secure.symantec.com/connect/forums/failover-concept

 

2) Replication:

Replication configurations are supported with both embedded and Microsoft SQL Server databases. Replication configurations are used for redundancy. Data from one database is replicated (duplicated) on another database. If one database fails, you can still manage and control all clients because the other database contains the client information.

Installing and configuring servers for replication is a two-part process. In an existing installation site, you first install a new Symantec Endpoint Protection Manager and database for replication with an existing manager. Second, you log on to the Symantec Endpoint Protection Manager and select and schedule the items to replicate.

When you select the items to replicate, you can choose logs and packages. Packages also include the updates to virus definitions, client components, and client software. The size of packages and updates can grow to several gigabytes of information if you download updates in multiple languages. You must consider the amount of data you replicate when you select these options, along with the bandwidth consumption. One client package is generally 180 MB in size when compressed.

You can install and configure both the embedded database server and Microsoft SQL Server for replication. Replication configuration causes data to be duplicated between databases so that both databases contain the same information, preferably on different database servers on different computers. If one database server crashes, you can continue to manage the entire site by using the information on the database server that did not crash.

Note: 
Symantec Endpoint Protection Manager configures and controls this replication. This replication is not native SQL Server replication.

 

 

Reference: http://www.symantec.com/docs/HOWTO26797

 

Hope that helps!!

Mithun Sanghavi
Senior Consultant
MIM | MCSA | MCTS | STS | SSE | SSE+ | ITIL v3

Don't forget to mark your thread as 'SOLVED' with the answer that best helped you.

SOLUTION
pete_4u2002's picture

Thumbs up to Mithun's clear explaination!

Replication can be across any database supported for SEPM. Failover it is mandatory to have SQL.

Is your question related to replication , and set MSL within SEPM's. The clients will still failover?

Rao's picture

Too good

Thank you Mithun and pete

My company is looking forward to add a server and I am trying to understand 2 different concepts in symantec. so that i can take the correct decisions.

Thank you again.

Thanks and Regards,

S.Rao