My setup is a notebook with 2 drives, with 2 partitions in a DP file-replication pool, windows 8.1 with Hyper-V.
I remember reading in another post somewhere that for always-on VMs, DP's balancing algorithm will choke up (or something will happen), if we don't turn off the VM prior to the running of the balancer.
And I think that's exactly what happened this morning at 6am when the balancer was scheduled to run on a pool with a running VM. I have not tested turning the VM off to see if the error shows up at balancing, I will try this next.
What do you suggest I do for 24/7 VM's. Does anyone has a best practices tips for running virtual machines in a DP pool.
ps. I think you've got something special here and I've purchased DP anyway even though I'm only 1 day in my trial. Keep up the good work.
Question
aprib
My setup is a notebook with 2 drives, with 2 partitions in a DP file-replication pool, windows 8.1 with Hyper-V.
I remember reading in another post somewhere that for always-on VMs, DP's balancing algorithm will choke up (or something will happen), if we don't turn off the VM prior to the running of the balancer.
And I think that's exactly what happened this morning at 6am when the balancer was scheduled to run on a pool with a running VM. I have not tested turning the VM off to see if the error shows up at balancing, I will try this next.
What do you suggest I do for 24/7 VM's. Does anyone has a best practices tips for running virtual machines in a DP pool.
ps. I think you've got something special here and I've purchased DP anyway even though I'm only 1 day in my trial. Keep up the good work.
Link to comment
Share on other sites
4 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.