- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks both. I changed the HA policy to reserve 20% as failover spare capacity, then set the 'reserve all guest memory' on the vm, which completed successfully.
After reading through more discussions I am now beginning to suspect this issue might have started after changing the pagefile recently. It was set to 12GB + 10MB as per Microsoft's recommendation. Due to space constraints on the C: drive, this was lowered to 'system managed size' (5119MB). I have now extended the C drive so can restore the pagefile back to my previous Microsoft recommended figure. I'll do this out of hours tonight as it'll require a reboot.
If correct, then my vm is paging to memory, which is not ideal. I'll bump up the memory to 16GB to see if that helps.
I can report that putting the vm into the newly created resource pool, which had a memory reservation of over 12GB did nothing to stop the Information Store errors mentioned in my first post.
I'll update again tomorrow after the reboot.