Uber22 Posted August 10, 2019 Posted August 10, 2019 Hey does anyone issues with server 2016 backups since about a week ago or two i have been getting checkpoint error, veeam support cant help as its a microsoft issue and microsoft want a one off fee to look at the issue. if i reboot my host the back will work for a day or two. thanks
jonnykewell1 Posted August 10, 2019 Posted August 10, 2019 I had an issue with veeam backups for server 2016 and was given these instructions by Veeam support. n order to resolve it, I would like to ask you to perform the following: 0. Make sure that no jobs are running. 1. Download the hotfix: https://storage.veeam.com/Fix_164032_8ae0a13785.zip 2. On each and every Hyper-V host (that are added to Veeam) and on the main Veeam Backup & Replication server stop service named "Veeam Data Mover service" manually, then find and kill process "VeeamPSDirectCtrl_X64.exe" if present. 3. Open [C:\Program Files (x86)\Veeam\Backup Transport\GuestInteraction\VSS\] folder on the Hyper-V host and rename original [VeeamPSDirectLib_x64.dll] to [VeeamPSDirectLib_x64.dll_orig]. 4. Copy DLL from the provided FTP location and replace DLL you have just renamed. 5. Run service "Veeam Data Mover service" manually. After that, please re-try the job(s) and let me know the results. I will be waiting for your answer.
Uber22 Posted August 10, 2019 Author Posted August 10, 2019 (edited) still getting the same error does need need to be done on the host,vm and backup sever ? ailed to create VM recovery checkpoint (mode: Crash consistent) Details: Job failed ('Checkpoint operation for 'sever' failed. (Virtual machine ID 70941E2B-25F9-441A-9DF1-84355126FFA5) Checkpoint operation for 'PASS' was cancelled. (Virtual machine ID 70941E2B-25F9-441A-9DF1-84355126FFA5) 'server' could not initiate a checkpoint operation: The process cannot access the file because it is being used by another process. (0x80070020). (Virtual machine ID 70941E2B-25F9-441A-9DF1-84355126FFA5) 'PASS' could not Retrying snapshot creation attempt (Failed to create production checkpoint.)Task has been rescheduledQueued for processing at 10/08/2019 10:27:13Unable to allocate processing resources. Error: Job failed ('Checkpoint operation for 'server failed. (Virtual machine ID 70941E2B-25F9-441A-9DF1-84355126FFA5) Checkpoint operation for 'SERVER' was cancelled. (Virtual machine ID 70941E2B-25F9-441A-9DF1-84355126FFA5) 'server' could not initiate a checkpoint operation: The process cannot access the file because it is being used by another process. (0x80070020). (Virtual machine ID 70941E2B-25F9-441A-9DF1-84355126FFA5) 'ailed to create VM recovery checkpoint (mode: Crash consistent) Details: Job failed ('Checkpoint operation for 'server' failed. (Virtual machine ID 70941E2B-25F9-441A-9DF1-84355126FFA5) Checkpoint operation for 'server' was cancelled. (Virtual machine ID 70941E2B-25F9-441A-9DF1-84355126FFA5) 'server' could not initiate a checkpoint operation: The process cannot access the file because it is being used by another process. (0x80070020). (Virtual machine ID 70941E2B-25F9-441A-9DF1-84355126FFA5) 'server' could not Retrying snapshot creation attempt (Failed to create production checkpoint.)Task has been rescheduledQueued for processing at 10/08/2019 10:27:13Unable to allocate processing resources. Error: Job failed ('Checkpoint operation for 'server' failed. (Virtual machine ID 70941E2B-25F9-441A-9DF1-84355126FFA5) Checkpoint operation for 'server' was cancelled. (Virtual machine ID 70941E2B-25F9-441A-9DF1-84355126FFA5) 'server' could not initiate a checkpoint operation: The process cannot access the file because it is being used by another process. (0x80070020). (Virtual machine ID 70941E2B-25F9-441A-9DF1-84355126FFA5) 'server' could not create auto virtual hard d' could not create auto virtual hard d Edited August 10, 2019 by Uber22
jonnykewell1 Posted August 10, 2019 Posted August 10, 2019 Might be a different problem but it was known to affect server 2016 vms. Needs to be applied on the hyper v hosts only.
jvanstee Posted September 21, 2020 Posted September 21, 2020 I have had the same issues with both Back up Exec and now VEEAM. Did the above instructions fix the issue for you ?
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now