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

++ VM on second Hyper-V Cluster Node not backing up - Failed to find VM ++

Hello,
we are using NetVault 12.1 to backup all virtual machines from our hyper-v 2012R2 cluster.
vms01 (node1) vms01 (node2) vmscl (cluster). Ping, nslookup/ptr, check access, firewall test is running successfully.

For some weeks we see the following messages in the backup log.

Job Message    2018/10/29     18:00:02  71        Data Plugin       VMS01 Number of VMs selected for backup: 20

Error         2018/10/29     18:00:05          71        Data Plugin       VMS01 VM [BI01]: Failed to find VM on cluster 'VMSCL'
Error         2018/10/29     18:00:06          71        Data Plugin       VMS01 VM [BI01]: Backup failed
Error         2018/10/29     18:00:10          71        Data Plugin       VMS01 VM [CLOUD]: Failed to find VM on cluster 'VMSCL'
Error         2018/10/29     18:00:10          71        Data Plugin       VMS01 VM [CLOUD]: Backup failed

Here is what I did to get it running again:
- Removed all agents on vms02, restart
- Deleted virutal client
- Created new virtual client with the cluster name "vmscl" (agents are installed on vms02 successfully)
- Restarted
- Hyper-V Cluster license is looking good
- Running the following commands

Import-Module FailoverClusters
Import-Module ServerManager

Remove-ClusterNode -Cluster vmscl vms02
Restarted vms02
Add-ClusterNode -Cluster vmscl vms02

Get-ClusterNode -Cluster vmscl
Name            ID    State
----                 --    -----
VMS01          2     Up
VMS02          1     Up

Virtual machines running on vms02 are still not backing up / shown in the create backup selection section.

Parents
  • Hi is it 2012 r2 core? what hyper v plugin are you using? can you check the configuration in change settings -> client settings -> vms02 -> Network Manager you should have in preferred ip the ip for the host only and in barred ip addresses any other if you have iscsi, etc (cluster ip should be nowhere in this configuration on none of vms02 or vms01)

    After all this steps that you have done have you tried to delete virtual client, remove hyper-v plugin from both hosts, recreate the virtual client and retry?

    Looking forward

    Regards,

  • Hi,

    it is Server 2012 R2 with GUI, using Hyper-V plug-in version 12.0.0.7.
    NetVault doesn't care about preferred ip address entered or not. Result is the same.


    Now I did:
    - Remove all agents on vms01 + vms02, restart

    - Deleted virutal client
    - Created new virtual client with the cluster name "vmscl" (agents are installed on vms01 + vms02 successfully)
    - Restarted

    No change.

  • It was working before? if yes, what has changed?

    Can you try to browse the vm's under the hyper-v plugin using the host instead of the virtual client?

    Run in powershell in both hosts:

    Get-Cluster from both hosts

    Get-vm from both hosts

    Does that give you the correct info?

  • Good morning,
    sure, it was working for years. I guess I installed some windows updates.

    VMS01:
    PS C:\> Get-Cluster
    Name
    ----
    VMSCL


    PS C:\> get-vm

    Name State CPUUsage(%) MemoryAssigned(M) Uptime Status
    ---- ----- ----------- ----------------- ------ ------
    AP1 Running 0 20480 4.13:12:10 Normaler Betrieb
    AR1 Running 0 8096 4.10:14:41 Normaler Betrieb
    CLD Running 0 2048 6.00:25:16 Normaler Betrieb
    CI Off 0 0 00:00:00 Normaler Betrieb
    C Running 0 512 5.05:02:59 Normaler Betrieb
    D1 Running 0 6144 4.15:25:49 Normaler Betrieb
    D1 Running 0 6144 5.05:56:42 Normaler Betrieb
    FI1 Running 0 12228 3.08:35:31 Normaler Betrieb
    R1 Running 0 8096 4.16:18:15 Normaler Betrieb
    R01 Running 4 24576 3.02:24:44 Normaler Betrieb
    R02 Running 4 24576 3.02:01:31 Normaler Betrieb
    TIC Running 0 4096 5.21:26:38 Normaler Betrieb

    VMS02:
    PS C:\> Get-Cluster
    Name
    ----
    VMSCL

    PS C:\> get-vm

    Name State CPUUsage(%) MemoryAssigned(M) Uptime Status
    ---- ----- ----------- ----------------- ------ ------
    B1 Running 0 16384 3.01:15:26 Normaler Betrieb
    C01 Running 0 6144 2.12:01:59 Normaler Betrieb
    D01 Off 0 0 00:00:00 Normaler Betrieb
    GET Running 0 4096 2.15:45:47 Normaler Betrieb
    M01 Running 3 24576 2.15:44:23 Normaler Betrieb
    NP Running 0 6144 2.15:47:51 Normaler Betrieb
    R3 Running 3 24576 2.15:48:18 Normaler Betrieb
    R1 Running 0 8192 2.15:47:56 Normaler Betrieb
    TE Running 0 4096 2.15:45:07 Normaler Betrieb
    Wer Off 0 0 00:00:00 Normaler Betrieb
    WS Running 0 6144 3.01:14:33 Normaler Betrieb

     
    The results are correct!

Reply
  • Good morning,
    sure, it was working for years. I guess I installed some windows updates.

    VMS01:
    PS C:\> Get-Cluster
    Name
    ----
    VMSCL


    PS C:\> get-vm

    Name State CPUUsage(%) MemoryAssigned(M) Uptime Status
    ---- ----- ----------- ----------------- ------ ------
    AP1 Running 0 20480 4.13:12:10 Normaler Betrieb
    AR1 Running 0 8096 4.10:14:41 Normaler Betrieb
    CLD Running 0 2048 6.00:25:16 Normaler Betrieb
    CI Off 0 0 00:00:00 Normaler Betrieb
    C Running 0 512 5.05:02:59 Normaler Betrieb
    D1 Running 0 6144 4.15:25:49 Normaler Betrieb
    D1 Running 0 6144 5.05:56:42 Normaler Betrieb
    FI1 Running 0 12228 3.08:35:31 Normaler Betrieb
    R1 Running 0 8096 4.16:18:15 Normaler Betrieb
    R01 Running 4 24576 3.02:24:44 Normaler Betrieb
    R02 Running 4 24576 3.02:01:31 Normaler Betrieb
    TIC Running 0 4096 5.21:26:38 Normaler Betrieb

    VMS02:
    PS C:\> Get-Cluster
    Name
    ----
    VMSCL

    PS C:\> get-vm

    Name State CPUUsage(%) MemoryAssigned(M) Uptime Status
    ---- ----- ----------- ----------------- ------ ------
    B1 Running 0 16384 3.01:15:26 Normaler Betrieb
    C01 Running 0 6144 2.12:01:59 Normaler Betrieb
    D01 Off 0 0 00:00:00 Normaler Betrieb
    GET Running 0 4096 2.15:45:47 Normaler Betrieb
    M01 Running 3 24576 2.15:44:23 Normaler Betrieb
    NP Running 0 6144 2.15:47:51 Normaler Betrieb
    R3 Running 3 24576 2.15:48:18 Normaler Betrieb
    R1 Running 0 8192 2.15:47:56 Normaler Betrieb
    TE Running 0 4096 2.15:45:07 Normaler Betrieb
    Wer Off 0 0 00:00:00 Normaler Betrieb
    WS Running 0 6144 3.01:14:33 Normaler Betrieb

     
    The results are correct!

Children