This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Core memory usage in Hyper-V VMs making VMs unresponsive

We run most of our Rapid Recovery Cores in Hyper-V VMs. Since upgrading from Appassure 5.4 to Rapid Recovery we've had problems with the Core service gradually using up more and more memory until it eventually uses up all the available memory recourses. At the point the VM will become unresponsive and eventually crash. This first started happening with Rapid Recovery 6.0, and has continued to happen with all the subsequent releases. Most of our Core VMs are running Windows Server 2012r2, a few are also on 2012 or 2008r2, and the problem seems to happen with all of them. We don't see this problem happening with Core that are running bare metal however.

Are there any known issues with Rapid Recovery running on Hyper-V VMs, or workarounds for this problem?

Parents
  • I've made the changes you suggested to one of the Cores in our test environment, and left a similar core unchanged. I restarted the core service on both to compare how the memory behaves.
Reply
  • I've made the changes you suggested to one of the Cores in our test environment, and left a similar core unchanged. I restarted the core service on both to compare how the memory behaves.
Children
No Data