If this is Windows 2003, you may want to look at a few things: 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.
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.