How to enable replication In sepm
Replication and considerations
Symantec Endpoint Protection Manager Replication Workflow
How to add "Replication Partners" and Schedule Replication
Thanks In Advance
Best Practice for setting replication frequency
Check this video
Check this article.
Help Link: http://www.symantec.com/business/support/overview.jsp?pid=54619
Replication enables data to be duplicated between databases one separate sites so that both databases contain the same information. If one database fails, you can manage the entire site by using the information on the database from another site.
A partner is a management server on another site with a different database and management servers. A site may have as many partners as needed. Each partner, or remote site, connects to the main site or local site, which is the site that you are logged on to. All sites that are set up as partners are considered to be on the same site farm.
Each site you replicate data with is either a replication partner or a site partner. Both replication partners and site partners use multiple servers, but the database they use and the way they communicate is different:
Note: If you wish to move SEPM from one machine to another with the help of replication, Replication is an option, decide whether to go or not.Beacuse if you do replication and remove the old server that is the Primary SEPM , in future if you want to do replication you will not be able to do so.
How replication works
Managing sites and replication
Adding a replication partner
Forum Article: Replication & Consideration
Sr.Technical Support Engineer, Endpoint Security
Enterprise Technical Support
CCNA | CCNP | MCSE | SCTS |
Don't forget to mark your thread as 'SOLVED' with the answer that best helps you.<
Thanks all of you .
Kindly provide more information..
Difference Beetween Failover and replication ?
How to configure 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.
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.
Symantec Endpoint Protection Manager configures and controls this replication. This replication is not native SQL Server replication.
1) About failover and load balancing
2) About Load Balancing and Failover Clustering in Symantec Endpoint Protection 11.0
3) About installing and configuring the Symantec Endpoint Protection Manager for failover or load balancing
4) Installing a management server for failover or load balancing
Check this Thread: