Discussions specific to the Microsoft Hyper-V hypervisor
Post Reply
headond
Novice
Posts: 3
Liked: never
Joined: Nov 02, 2018 2:09 pm
Contact:

Failed to finalize guest processing. Error: Cannot copy file

Post by headond » Nov 05, 2018 8:27 am

Case #03270218

Failed to finalize guest processing. Error: Cannot copy file. Source file: [\192.168.16.202ADMIN$VeeamVssSupportmetadataVSSBackupComponents.xml]. Target file: [C:WindowsTEMP9a739a7-1cdf-4819-b10b-e813b0f9058dBackupComponents.xml].
CopyFile() failed.
Win32 error:The system cannot find the file specified.
Code: 2

Server 2008 R2

Dima P.
Product Manager
Posts: 10305
Liked: 834 times
Joined: Feb 04, 2013 2:07 pm
Full Name: Dmitry Popov
Location: Prague
Contact:

Re: Failed to finalize guest processing. Error: Cannot copy file

Post by Dima P. » Nov 05, 2018 10:34 am

Hello headond,

Kindly keep working with our support team, thank you!

P.S. Please do not forget to include a brief description of your issue whenever you are posting about technical issues - otherwise we cannot advise. Thank you for understanding.

headond
Novice
Posts: 3
Liked: never
Joined: Nov 02, 2018 2:09 pm
Contact:

Re: Failed to finalize guest processing. Error: Cannot copy file

Post by headond » Nov 05, 2018 2:25 pm

The below response worked for me as a temp measure:

You also might temporary disable AAP for the isued VMs. The backup will not be transaction-consistent, but you'll still get successful restore point of the machines in crash-consistent state.

Please find the instruction below:

Right-click the issued job in the "Jobs" section;
Click "Edit…";
Go to the "Guest Processing" tab;
Press the "Applications…" button;
Mark the issued VM and press "Edit…";
Choose "Disable application processing" in the General tab.

Dima P.
Product Manager
Posts: 10305
Liked: 834 times
Joined: Feb 04, 2013 2:07 pm
Full Name: Dmitry Popov
Location: Prague
Contact:

Re: Failed to finalize guest processing. Error: Cannot copy file

Post by Dima P. » Nov 05, 2018 4:13 pm

Hi headond.

Thanks for the heads up. That sounds like a workaround but I suggest to keep working with our support team to tack down the root cause. Cheers!

Post Reply

Who is online

Users browsing this forum: No registered users and 15 guests