none
Cannot Create Checkpoints Manually or During Veeam Backup RRS feed

  • Question

  • We just put up a new Server 2016 Hyper-V host and moved roughly 10 VMs to it from several Server 2012 R2 Hosts.

    We are running Veeam B&R and have had no issues until this point.  We can not successfully create checkpoints manually, and Veeam backups are failing for this same reason.

    Error messages and logs are below.

    Log Name:      Microsoft-Windows-Hyper-V-VMMS-Admin
    Source:        Microsoft-Windows-Hyper-V-VMMS
    Date:          4/18/2018 2:16:20 PM
    Event ID:      18014
    Task Category: None
    Level:         Error
    Keywords:      
    User:          SYSTEM
    Computer:      Server
    Description:
    Checkpoint operation for 'VM' was cancelled. (Virtual machine ID 81998206-704D-4303-88D0-EE956C499142)
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-Hyper-V-VMMS" Guid="{6066F867-ABC-4418-85FD-36E3F9C0600C}" />
        <EventID>18014</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8000000000000000</Keywords>
        <TimeCreated SystemTime="2018-04-18T21:16:20.207168700Z" />
        <EventRecordID>1305</EventRecordID>
        <Correlation />
        <Execution ProcessID="3676" ThreadID="12192" />
        <Channel>Microsoft-Windows-Hyper-V-VMMS-Admin</Channel>
        <Computer>Server</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <UserData>
        <VmlEventLog xmlns="http://www.microsoft.com/Windows/Virtualization/Events">
          <VmName>VM</VmName>
          <VmId>81998206-704D-4303-88D0-EE956C499142</VmId>
        </VmlEventLog>
      </UserData>
    </Event>
    
    
    
    Log Name:      Microsoft-Windows-Hyper-V-VMMS-Admin
    Source:        Microsoft-Windows-Hyper-V-VMMS
    Date:          4/18/2018 2:16:20 PM
    Event ID:      18012
    Task Category: None
    Level:         Error
    Keywords:      
    User:          SYSTEM
    Computer:      Server
    Description:
    Checkpoint operation for 'VM' failed. (Virtual machine ID 81998206-704D-4303-88D0-EE956C499142)
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-Hyper-V-VMMS" Guid="{6066F867-7ABC-4418-85FD-36E3F9C0600C}" />
        <EventID>18012</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8000000000000000</Keywords>
        <TimeCreated SystemTime="2018-04-18T21:16:20.207202300Z" />
        <EventRecordID>1306</EventRecordID>
        <Correlation />
        <Execution ProcessID="3676" ThreadID="12192" />
        <Channel>Microsoft-Windows-Hyper-V-VMMS-Admin</Channel>
        <Computer>Server</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <UserData>
        <VmlEventLog xmlns="http://www.microsoft.com/Windows/Virtualization/Events">
          <VmName>VM</VmName>
          <VmId>81998206-704D-4303-88D0-EE956C499142</VmId>
        </VmlEventLog>
      </UserData>
    </Event>
    
    Log Name:      Microsoft-Windows-Hyper-V-VMMS-Admin
    Source:        Microsoft-Windows-Hyper-V-VMMS
    Date:          4/18/2018 2:16:20 PM
    Event ID:      19100
    Task Category: None
    Level:         Error
    Keywords:      
    User:          SYSTEM
    Computer:      Server
    Description:
    'VM' background disk merge failed to complete: The process cannot access the file because it is being used by another process. (0x80070020). (Virtual machine ID 81998206-704D-4303-88D0-EE956C499142)
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-Hyper-V-VMMS" Guid="{6066F867-7ABC-4418-85FD-36E3F9C0600C}" />
        <EventID>19100</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8000000000000000</Keywords>
        <TimeCreated SystemTime="2018-04-18T21:16:20.232904700Z" />
        <EventRecordID>1308</EventRecordID>
        <Correlation />
        <Execution ProcessID="3676" ThreadID="12192" />
        <Channel>Microsoft-Windows-Hyper-V-VMMS-Admin</Channel>
        <Computer>Server</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <UserData>
        <VmlEventLog xmlns="http://www.microsoft.com/Windows/Virtualization/Events">
          <VmName>VM</VmName>
          <VmId>81998206-704D-4303-88D0-EE956C499142</VmId>
          <ErrorMessage>%%2147942432</ErrorMessage>
          <ErrorCode>0x80070020</ErrorCode>
        </VmlEventLog>
      </UserData>
    </Event>
    


    Brian Modlin

    Thursday, April 19, 2018 1:52 AM

All replies

  • Hi ,

    As the error presented, an .avhdx file was locked.

    Please try to turn off the third party applications and run a test.

    Also check if the following link is helpful:

    Cannot create checkpoint when shared vhdset (.vhds) is used by VM - 'not part of a checkpoint collection' error

    https://social.technet.microsoft.com/Forums/ie/en-US/0d6cddde-3ff3-4a50-a627-6ad7bf7667fd/cannot-create-checkpoint-when-shared-vhdset-vhds-is-used-by-vm-not-part-of-a-checkpoint?forum=winserverClustering

    Best Regards,

    Candy


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com   

    Thursday, April 19, 2018 6:30 AM
  • Brian,

    Do you solve this problem in your environment? I have had the same problem. After reboot the vm the things works well, but it isn't a solution in my understand.

    Thanks


    Rosivaldo Correa


    • Edited by Rosivaldo Thursday, May 23, 2019 7:31 PM
    Thursday, May 23, 2019 7:31 PM
  • same issue as rosivaldo...

    bostjanc

    Wednesday, June 19, 2019 7:19 AM
  • any solution?

    rebooting hyperv host only temporary solves the issue. after 2-3 days the same problem repeats


    BCR

    Saturday, June 22, 2019 3:15 PM
  • Also chiming in with the same issue.

    Rebooting the HyperV host is a band-aid fix. The problem reappears within 2-3 days.

    Using HyperV Server with Veeam Backup & Replication 9.5 U4.

    Tuesday, December 17, 2019 9:39 PM
  • matt. we have figured out that the root of the problem was a bad group policy. someone linked default domain controller gpo to entire domain which messed log on as service, causing veeam backup having issue. with best regards. b

    BCR

    Tuesday, December 17, 2019 9:59 PM
  • do you mind sharing which group policy causes this problem? 

    I am having the same issue but unsure how to fix this from Group Policy.

    Thanks 

    Tuesday, February 18, 2020 6:48 AM
  • Hi ecsw.

    There is a Default Domain Controller group policy Object in GPO and that one was linked to entire domain.
    Default Domain Controller group policy must be linked only to DC's.

    On problematic server where veeam is not working, open command prompt as administrator and run command: gpresult /r

    Check which GPO's are applied to that machine.

    If there is a default domain controller policy lister under applied GPO's make sure to unlink it on GPO.


    BCR

    Thursday, February 20, 2020 9:50 AM
  • We are also facing same issue and same product we are using ( Veem backup server and Windows Server 2016 Hyper V) 

    We are not able to run checkpoint manually

    Post Hyper Restart One Backup will run With out any issue

    We are facing issue in only Hyper 2016 as we are using Hyper V 2012 R2  we are not finding any issue in that HyperV.

    We need support on ASAP as we are not able to take daily backup.

    Saturday, March 21, 2020 6:14 PM