more than 10 months and I haven't posted anything! I've been extremely busy, to say the least. Family life and ramping up work projects take their toll on free time, hobbies and blogging. My family sees me rarely enough so I don't want to deprive them of these rare and precious moments, especially with my 1 year old boy!
As the title says above, I've come across an interesting issue experienced in Windows 2008 R2 while running the 64-Bit DoubleTake 184.108.40.2061 agent (also known as HP Storage Mirroring Recover). The situation was that after running almost normally for 2-3 weeks, DoubleTake would start leaking memory, consuming up all the available memory thus forcing system to swap to disk. In this case, the virtual machine (a file server) had 4 GB RAM and once this was committed, the swap file increased to 16 GB. At the same time, because the folder used for replication was located on the C: drive, and was using up some space as well, the server ended up with less than 100 MB available on the disk. This of course is very bad news. The system became totally unresponsive and had to be reset.
An incident was raised with HP and they acknowledged that the 220.127.116.111 version has known problems and needs to be upgraded to 18.104.22.1685.6, which we did promptly. At the same time, I reconfigured our source and target servers to use a dedicated folder on a larger disk (to avoid exhaustion of free space on disk C). Hopefully this should fix the issue for good.
I hope this post will give something to chew for those who follow it and who lost faith in ever seeing something new published on it!
Let's be honest, I am posting because I wanted to share some information of interest before cutting off all ties with the civilized world as I prepare for my core leave… 2 weeks in the French Riviera, at my parents, with the whole family. Needless to say, I'm very much looking forward! I will put Active Directory and Virtualization books aside for 2 weeks, and enjoy a suntan a some swimming!
Have all fun and enjoy your holidays 🙂