Windows 2019 failover cluster - move virtual machine storage - problems

Slawomir 21 Reputation points
2021-07-15T22:23:44.853+00:00

Hello,

I have a problem with move virtual machine storage in failover cluster manager (Windows 2019 server Datacenter edition). In the left corner I should have seen my cluster storage volume folders...I see only word "Loading". Here are print screens. Can you help me ?115140-klaster-1.jpg

115201-klaster-2.jpg

Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,480 questions
Hyper-V
Hyper-V
A Windows technology providing a hypervisor-based virtualization solution enabling customers to consolidate workloads onto a single server.
2,560 questions
Windows Server Clustering
Windows Server Clustering
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Clustering: The grouping of multiple servers in a way that allows them to appear to be a single unit to client computers on a network. Clustering is a means of increasing network capacity, providing live backup in case one of the servers fails, and improving data security.
962 questions
0 comments

5 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. JiayaoZhu 3,911 Reputation points
    2021-07-16T07:30:35.623+00:00

    Hi,

    Thanks for posting on our forum!

    Based on your error message, it seems that your access to the cluster storage path is denied and I would like to firstly learn more about your cluster environment so that I can better help you troubleshoot the possible cause:

    1. How did you move your VM storage, from one CSV to another, or within the same CSV?
    2. Check if your nodes and cluster service are working properly
    3. are you using ESET or MPIO in your cluster?
    4. Try to remove the disk you attached to the cluster, and then re-add it. THEN add to CSV, to see if it works
    5. Restart cluster service if you can endure downtime

    Besides, I also found a bold which had a similar issue with yours, you can take a look at:
    https://social.technet.microsoft.com/Forums/en-US/d7dacf9f-4d48-4242-94bc-8730278478f9/hyperv-virtual-machine-move-fails-to-another-csv-general-access-denied-error-0x80070005?forum=winserverClustering

    Finally, apart from this event information, did you find any other logs stamped on the time when you encountered this issue, you can also post them on this blog if you can find them.

    Thanks for your support!

    BR,
    Joan

    If the Answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments
  2. Slawomir 21 Reputation points
    2021-07-17T23:16:57.2+00:00

    Hi,

    Below are my answers to your question.

    1) How did you move your VM storage, from one CSV to another, or within the same CSV? --> I can move storage by using Hyper-v Manager. But first I must remove vm from cluster, and then I can move vm storage by using Hyper-v Manager.....
    2) Check if your nodes and cluster service are working properly -- > I see that all nodes and services are online.
    3) are you using ESET or MPIO in your cluster? --> Im using MPIO 4) Try to remove the disk you attached to the cluster, and then re-add it. THEN add to CSV, to see if it works --> Do I have to shut down all my vms to remove discs from cluster ? Or even when I will remove disc and re-add them, all my guests vm`s will be online ?

    115558-klaster-3.jpg
    5) Restart cluster service if you can endure downtime --> Unfortunatelly I cant restart my cluster service because then all our VMs will go offline in one time and that is impossible...

    0 comments
  3. JiayaoZhu 3,911 Reputation points
    2021-07-19T02:47:42.53+00:00

    Hi,

    Thanks for your reply!

    1) Try to remove the disk you attached to the cluster, and then re-add it. THEN add to CSV, to see if it works——Yes, you need to offline your VMs

    2) Based on your description, I think you can check if you have assigned full permission to your CSV from all of your VMs, you need to check if your MPIO is configured properly. Besides, have you tried the method that mentioned in the blog? That is, to create a folder with the name of the VM on the CSV and migrated the file to that folder instead of trying to put the file on the root of the CSV. "C:\ClusterStorage\Volume5\VM-NAME\" instead of "C:\ClusterStorage\Volume5\". If you have tried, then what is the output?

    3) I would appreciate it if you could try to find other relevant logs stamped on the time when you encountered this issue. The more information you can offer us, the more we can do for you.

    Besides, if you are in a hurry to solve the issue, I will recommend you to contact Microsoft Customer Support and Services where professional log analysis and real-time remote troubleshooting for your issue can be done. In addition, if the issue has been proved as system flaw, the consulting fee would be refund. You may find phone number for your region accordingly from the link below.

    Global Customer Service phone numbers:
    https://support.microsoft.com/en-us/help/13948/global-customer-service-phone-numbers

    Thanks for your support!

    BR,
    Joan

    If the Answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

  4. Slawomir 21 Reputation points
    2022-09-18T06:32:34.803+00:00

    I have solved my problem...... I was changing the cluster name to name with 14 digits (before my cluster name had 16 digits....), and now the option Move Virtual Storage works :).

    0 comments
  5. Jeferson Sophiatti 0 Reputation points
    2024-01-13T00:31:40.5633333+00:00

    Hello, I know that this thread is old, but can help others with same problem. In my case the problema was that the IP and cluster name was misconfigured and offline. Correcting cluster name and putting online all things works!

    0 comments