Unsolved
This post is more than 5 years old
12 Posts
0
1896
November 21st, 2011 08:00
Cannot get replication to work on a new server
Hi Everyone
We had an old 2003 server source server running repistor 6.2. This worked OK. We have replaced with a new server 2008R2 server. I have loaded replistor V6.4 X64 on. The specifications are all setup the same, and are going to the same target server which is running 2003 with replistor V6.4. However syncronisation just does not appear to do anything at all. The spec says synch needed. I have tried synch with attribute compare only, and also unchecked incremental, (I've tried all the options!) and left it running all night with the different options, but no joy. I have deleted the data directory and tried resynching. Any ideas please?
Many thanks!
No Events found!
yito1
262 Posts
0
November 21st, 2011 17:00
Hi, isoprh
>I have deleted the data directory and tried resynching.
This is the appropriate action.
After doing this, does not synchronize correctly?
If you can not sync correctly, please try to recreate the Specification.
isoprh
12 Posts
0
November 22nd, 2011 03:00
Thanks for the reply
I have tried this, now it doesn't even show the progress bar. I have even tried a small directory (10MB!) and still nothing, still shows synch needed. Kernel log is 0 and cache is 1%, very little in the way of bytes received and bytes sent.
yito1
262 Posts
0
November 22nd, 2011 04:00
Hi,
It is the behavior that is abnormal.
Are there any errors in event log?
It is recommended to reinstall RepliStor.
isoprh
12 Posts
0
November 23rd, 2011 09:00
Thanks for the reply.
I have reinstalled. Same problem. Sites already setup seem OK, it's just any new servers. The first 2 screen shots are errors on the target server. The last one is from the source server. Hope you can view them, they are a bit small. Any ideas?
Thanks
yito1
262 Posts
1
November 23rd, 2011 17:00
Hi,isoprh
Windows-text:10053 shows that could not communicate with the target.
Please resolve it first. Otherwise would not sync.
Events of the VSS and the target will not matter in this SYMPTOMS.
isoprh
12 Posts
0
November 24th, 2011 04:00
Thanks for the pointer. There's usally so much in the logs I don't read them properly! I tracked the issue down to the site properties setting. Usually for domain I just put in the first part of our domain, but I needed to put in the fully qualified domain name! Seems to be OK now.
Thanks again Yoshinobu.