Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Error while adding replication partner

Created: 25 Dec 2007 • Updated: 22 May 2010 | 8 comments

Hi All
While adding replication partner i have such error:

------------------->
The site you want to add as a partner does not belong to
the same system as this site
it cannot be added as a partner
<------------------

Comments 8 CommentsJump to latest comment

Shubhojit's picture
Hi,
Even I got the exact same error message. I m trying to replicate two SEPMs at seperate locations. Could not find anything in the knowledgebase. Any help?
 
Regards,
 
Shubhojit.
Stickan's picture
Hi,
 
I also have the same issue, haven't found anything about it.
 
/Stickan
Paul Murgatroyd's picture
you can't add replication partners through the console - you must add them using the Server Configuration Wizard - the GUI option is available re-add a replica if it has been removed.

Paul Murgatroyd
Principal Product Manager, Symantec Endpoint Protection
Endpoint twitter feed: http://twitter.com/symc_endpoint

Tony Mannino's picture

Paul,

 

I am receiving the same error when I try to use the replication wizard in Endpoint Manager.  So I tried to use the Server configuration wizard that you recommended and it destroyed my database.  Thank goodness I had a backup and was able to restore it successfully. 

 

So my question is:  what are the EXACT steps to do it with the configuration wizard?  (Obviously, I did not do it correctly.)

 

Any help you could give me would be greatly appreciated!  Thanks.

 

Tony

Govardhan Gunnala's picture

It seems to be a very common issue, really needs Symantec assitence in fixing this. Symantec could one of you explain why wee receive this error and what's the resolution?

 

-Govardhan 

Govardhan

Security Engineer

D. E. Shaw & Co.,

Tony Mannino's picture

I actually did get it to work successfully but it replicates the ENTIRE database! If you have just one site to replicate to, it's not a big deal. But I have several remote sites, so it's not an option for me. I hear that they are releasing another maintenance release (MR3 in September) that will fix this replication issue.

If you still want to use replication, Symantec has a tech support team (called the Complex Installation team or something like that) JUST for replication because of the complexity of it. Just call Symantec tech support and ask for the team that handles replication.

Hope this helps!

Tony

Govardhan Gunnala's picture

Thanks for sharing your success and knowledge in this regard.

 

I have contacted Symantec and we are working on this.

 

-Govardhan 

Govardhan

Security Engineer

D. E. Shaw & Co.,

Wiley  Winter's picture

Well, this blows!  MR3 obviously didn't fix it.

I've added the server name in question to a new management server list on the primary but I get the same error. 

If you "install an additional site", it will wipe out your existing database on your primary.

 

Time for a bottle of red, a bottle of white

 

Wiley Winter

Memphis, TN