Unsolved
This post is more than 5 years old
8 Posts
0
403
August 2nd, 2007 12:00
Replistor 6.2 problem
I'm having some major issues with my installation of Replistor. We finally got it working and mirroring files in one direction to our secondary server, but it keeps failing, and now more recently, another problem has cropped up.
The primary server allows us to see the control panel with two sites - the primary site itself, and the secondary site.
The primary site icon (stoplight) is all grey, and will not attach or show any information about status or specifications. However, the secondary site shows as a green light.
Files are moving over - we tested it, but I don't know why the servers can't connect to themselves. The secondary server is having the same issue - it can see the primary but not itself. Also, it keeps mentioning something about a router.cfg file being corrupt or not available. Please help. I've searched for that file but cannot find it
Message was edited by:
SECUSA
The primary server allows us to see the control panel with two sites - the primary site itself, and the secondary site.
The primary site icon (stoplight) is all grey, and will not attach or show any information about status or specifications. However, the secondary site shows as a green light.
Files are moving over - we tested it, but I don't know why the servers can't connect to themselves. The secondary server is having the same issue - it can see the primary but not itself. Also, it keeps mentioning something about a router.cfg file being corrupt or not available. Please help. I've searched for that file but cannot find it
Message was edited by:
SECUSA
No Events found!
dramjass
151 Posts
0
August 9th, 2007 12:00
1. Virtual Memory. Ensure the Virtual Memory for the Windows box has at least 1.5 times the physcial.
Are you able to gracefully restart the ReplIStor Server service? If not, this may indicate a memory issue with the box.
2. Do you see any rep_srv.DMP files int he Data Directory? If so, this may indicate an issue with the product and EMC RepliStor Engineering may need to review these.
3. Check the Data Directory for a large amount of Kernel Log (OC$.rdf) files. Perhaps the GUI is taking a long time to repond b/c of all the files it needs to read to provide an update.