Video Screencast Help

Installing an Additional Site as a replication partner

Created: 19 Nov 2009 • Updated: 26 Jul 2010 | 15 comments

We have two servers that act as replication partners in SEP .

One of the servers ran out of disk space so we increased the disk sizes but had to get rid of the old disks (system disk stayed) , so I broke the replication between the SEP servers before the disks were replaced & then re-installed on the new disks.

Now I can't seem to get replication to work anymore. It doesn't even connect to secars ( I'm using port 8443 ) . I've uninstalled IIS & the SEPM & re-installed them but still I can't connect. We have no firewall on our servers so the port should be open.

Anyone have any idea's ?

Comments 15 CommentsJump to latest comment

pete_4u2002's picture

is the server added as an additional site?

Does the replication starts and gives the status as failed? if yes, post the scm-server-0.log from the tomcat\logs folder.

Vikram Kumar-SAV to SEP's picture

 While re-installing did you re-install it as replication partner or you restored the old database ?

Vikram Kumar

Symantec Consultant

The most helpful part of entire Symantec connect is the Search use it.

sandeep_sali's picture

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 only set up data replication during the initial installation of another Symantec Endpoint Protection Manager (SEPM) site.  Multiple sites are called a site farm when they are set up as replication partners.  You can add any site on the site farm as a replication partner to another already present site and you can also re-add a replication partner that was previously deleted (for example, prior to an upgrade).
Before you begin, you need to have the IP address or host name of the Symantec Endpoint Protection Manager for which you want to make a replication partner.

Follow the steps below to add a replication partner

Install Symantec Endpoint Protection Manager.
In the Management Server Configuration Wizard panel, click Advanced.
Select the number of clients you expect the server to manage, and then click Next.

This panel is displayed only when installing the Symantec Endpoint Protection Manager on the computer for the first time.
Check Install an additional site, and then click Next.
In the Server Information panel, accept or change the default values, and then click Next.
Accept or change the name in the Site Name box, and then click Next.
In the Replication Information panel, type values in the following boxes:

    Replication Server Name    The name or IP address of the remote Symantec Endpoint Protection Manager
    Replication Server Port        The default value is 8443
    Administrator Name        The account name that is used to log on to the console with administrator user rights
    Password            Provide a password that is associated with the Administrator Name that is specified

Click Next.
In the Certificate Warning dialog box, click Yes.
In the Database Server Choice panel, choose on of the following and click Next

Embedded Database
Microsoft SQL Server

If you chose Embedded Database in the above step, then continue with these steps, if you chose Microsoft SQL Server, move to step 14.
In the admin user panel, provide and confirm a password for the admin account. Optionally, provide an administrator email address.
Move to step 19
Do one of the following:

If the database does not exist, check Create a new database (recommended).
If the database exists, check Use an existing database.

An existing database must define file groups PRIMARY, FG_CONTENT, FG_LOGINFO, FG_RPTINFO, and FG_INDEX. The user account for database access must have privileges db_ddladmin, db_datareader, and db_datawriter.

If these requirements are not met, your installation fails. A best practice is to define a new database.

Click Next
In the Microsoft SQL Server Information panel, type your values for the following boxes:

    Database server        

        If you created a new instance, the format is servername_or_IPaddress\instance_name.    

    SQL server port    
    Database name     
    Confirm password (only when creating a new database)    
    SQL Client folder    
    DBA user (only when creating a new database)    
    DBA password (only when creating a new database)    
    Database data folder

Click Next
Provide and confirm a password for the admin account. Optionally, provide an administrator email address.
Click Next

    Configuring the Symantec Endpoint Protection Manager for replication

You use the Symantec Endpoint Protection Manager Console to configure servers for replication. The administrator logon credentials are the credentials that are used at the first site that you specify for replication.

To configure the Symantec Endpoint Protection Manager for replication

On the computer on which you installed the Symantec Endpoint Protection Manager as an additional site, log on to the Symantec Endpoint Protection Manager console.
In the console, click Admin, and then click Servers.
Under View Server, expand Local Site, expand Replication Partner, right-click Site <remote_host>, and then click Edit Properties.
In the Replication Partner Properties dialog box, set the options that you want for logs, packages, and replication frequency, and then click OK.

Refer to context-sensitive Help and the Administration Guide for Symantec Endpoint Protection and Symantec Network Access Control for details about these settings.

Right-click Site <remote_host>, and then click Replicate Now.
Click Yes.
Click OK.

To add a replication partner when a site has already been replicated using the above steps
Launch the Symantec Endpoint Protection Manager console.
Click the Admin tab. Under "View Servers", select a site.
Under "Tasks", click Add Replication Partner. The Add Replication Partner wizard appears.
Click Next on the "Welcome panel", and then enter the <IP Address> or <Host name> of the server that you wish to add as a replication partner.
Enter the <port number> and the administrator's user name and password for the remote server on which you installed the SEPM.
Note: The default setting for the remote server port is 8443.

Click Next to invoke the "Schedule Replication" dialog box
Disable "Autoreplicate" to set up a custom schedule for replication:
Select the hourly, daily, or weekly Replication Frequency.
Select the specific day during which you want replication to occur in the Day of Week list to set up a weekly schedule.

Click Next when the replication schedule is configured as desired.
Click Yes or No depending on whether or not you want to replicate logs.
Note: The default setting is No.

Click Next and then click Finish. The replication partner site is added under Replication Partners on the Admin page.

Thanks & Regards

Sandeep C Sali

AravindKM's picture

After reinstalling SEPM configure with defalut options
Then restore the database copy the old server server.xml  to \Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\conf and kesore.jaks file to Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\etc  .Then reconfigre your server and try..

If your DB is backuped after deleting the replication partner add that replication partner from admin tab...

Please don't forget to mark your thread solved with whatever answer helped you : ) Thanks & Regards Aravind

brav's picture

It's at first setup , just after installing the latest version of SEPM. We've had disk space issues on that server for 2 months , because we had no space and the business dragged their feet on authorizing more disk space I disabled the management server on the site & broke replication. So they were out of sync for 2 months before we upgraded the disks.

Because of this I thought it best to completely uninstall the second site & re-install the latest version of SEPM , so it's a new database replica.... however it fails half way through starting the replication just after install.

I'm using an embedded database for the replication partner ( the master site is using an SQL database )

Also, Sandip_Sali : I know you're trying to help ( thankyou ) but a link to the document would have been more appropriate than spamming the thread if I did actually need that information, however, I did say that I already had replication partners established and working previously to this problem.......


Vikram Kumar-SAV to SEP's picture

 Does the replication fail after 4 hours or so...If yes then you will have to increase Database idle timeout in ODBC...
what error do you get when it fails ?

Vikram Kumar

Symantec Consultant

The most helpful part of entire Symantec connect is the Search use it.

brav's picture

It's usually a java error , I did have it written down but seem to have mislaid that paper sorry!.

The thing that I can't seem to get round though is that I cannot telnet to port 8443 on the server but can telnet to the master server. Secars fails with : The website cannot display the page ; most likely causes : The website is under maintenance , The website has a programming error .

This worked previously , all I did was uninstall the SEPM and then re-install....


Vikram Kumar-SAV to SEP's picture

Is the SEPM version same on both the ends?
Was there any network change within this time?
Hope you are using default 8443 on sepm and havent change it.

scm-server0.log should be helpful. 

Vikram Kumar

Symantec Consultant

The most helpful part of entire Symantec connect is the Search use it.

brav's picture

The SEPM is the same on both ends
There haven't been any network changes for quite some time.
The port is 8443

There is no scm-server0.log on the replication partner


AravindKM's picture

Reinstall IIS
Repair your SEPM and try.... 

Please don't forget to mark your thread solved with whatever answer helped you : ) Thanks & Regards Aravind

brav's picture

Tried that & I receive a Java error :

Synchronization to the remote site failed:
JZ006: Caught IOException:
com.sybase.jdbc2.jdbc.SybConnectionDeadException: JZ0C0:
Connection is already closed.


AravindKM's picture

I think you are facing some network issues
You can bring the remote sever to the Lan which the main server situates..
  Give one local IP and do a replication
After this you can Bring the server to original location and reconfigure it..


After installing SEPM as a replicated site in a local machine take backup and restore in remote server and reconfigure the server...

Please don't forget to mark your thread solved with whatever answer helped you : ) Thanks & Regards Aravind

shp's picture

Can you try replication with  local server for test purpose... 
You can also follow the offline replication method suggested by aravind...

Srinivas H.P.
HCL Infosystems Ltd

Stefan Wilski's picture

We faced the same replication timeout wit a remote site where the bandwith was tight.
Here are the settings we used :

- from the remote site, we targeted another "parent" server on the master site. That server was less loaded.
- we started replication in the evening (bandwith available  - 2Mbps link to Internet, VPN between sites)
- in the ODBC settings, in the network tab, we checked "compress network packets". We could not change the 240 minutes "idle timeout", as that setting was greyed out.
- in the ODBC setting, in the database tab, we un-checked the "Stop database after last diisconnect".

We did replicate +/- 3 Gb within 5 hours (... more than 240 minutes ...)

I don't know which of the above setting did the trick...

We still have to reconfigure the remote site to synchronize with the correct "parent" server.