Failed to restore file. Failed to create new binary file

[Vidas]

Veeam Backup&Replication 8.0.0.917

-Restore guest files
--Microsof Windows...
pick nighty Full backup
select some directores in some tree deep
Right click --> Restore --> Overwrite

Show Details:
2015-01-22 07:59:20 File level restore started
2015-01-22 07:59:23 Enabling backup operator privilege
2015-01-22 07:59:24 Interactive mode
2015-01-22 07:59:24 Mounting restore point
2015-01-22 08:01:56 Starting restore
2015-01-22 08:01:56 Folders to restore: 107
2015-01-22 08:01:56 Files to restore: 296
2015-01-22 08:01:56 Total size: 162,1 MB
2015-01-22 08:02:13 VMware Tools are not up to date, some functionality may be affected
2015-01-22 08:02:16 Error Failed to restore file [R:\Dokumentai\Informaciniu_technologiju_skyrius\Sablonai\BRC2013_Paper_Template.dotx]. Failed to create new binary file [\\?\R:\Dokumentai\Informaciniu_technologiju_skyrius\Sablonai\BRC2013_Paper_Template.dotx].
Win32 error:Access is denied.
Code: 5
... same errors ...
2015-01-22 08:02:30 Restored folders: 113
2015-01-22 08:02:30 Restored files: 296
2015-01-22 08:02:30 Total size: 162,1 MB
2015-01-22 08:02:30 Restore successfully: 285
2015-01-22 08:02:30 Error Failed to restore: 11
2015-01-22 08:02:30 Restore completed

Then select these directores in file explorer from C:\VeeamFLR and copy to \\SERVER\SHARE\...\ then OWERWRITE
Files with extensions in lowercase in \\SERVER was owerwrited with files from backup with lowercase extensions to uppercase.

[veremin]

Are VMware Tools inside the given VM up-to-date? It might have happened backup server tried to restore files via VIX due to lack of network connection to the said VM, and it failed, because VMware Tools were outdated. Thanks.

[Vidas]

Thank you. Problem not VMware Tools up-to-date.

Code: Select all

2015-01-23 07:40:03          File level restore started
2015-01-23 07:40:07          Enabling backup operator privilege
2015-01-23 07:40:07          Interactive mode
2015-01-23 07:40:07          Mounting restore point
2015-01-23 07:40:53          Starting restore
2015-01-23 07:40:53          Folders to restore: 108
2015-01-23 07:40:53          Files to restore: 303
2015-01-23 07:40:53          Total size: 163,6 MB
2015-01-23 07:41:16 Error    Failed to restore file [R:\Dokumentai\Informaciniu_technologiju_skyrius\Sablonai\BRC2013_Paper_Template.dotx]. Failed to create new binary file [\\?\R:\Dokumentai\Informaciniu_technologiju_skyrius\Sablonai\BRC2013_Paper_Template.dotx].
                             Win32 error:Access is denied.
                              Code: 5
...
2015-01-23 07:41:40          Restored folders: 114
2015-01-23 07:41:40          Restored files: 303
2015-01-23 07:41:40          Total size: 163,6 MB
2015-01-23 07:41:40          Restore successfully: 292
2015-01-23 07:41:40 Error    Failed to restore: 11
2015-01-23 07:41:40          Restore completed

[veremin]

Then, the best approach would be to open a ticket with our support team, since log investigation seems to be required here. Thanks.

[Vidas]

Is it here: http://www.veeam.com/support.html ?
Do I need paid support if other file level restore options have no problem?

[veremin]

Correct.

Actually, according to our policy, customers with Free or evaluation license are still eligible for support. The answer will be provided based on support availability, though.

Feel free to contact them.

Thanks.

[rm4g00]

Hello,

File level restore windows- I experience the error failed to create new binary file? seems to be random files - i have vmware tools installed.

Anyone experience this? might need to raise a ticket

RM

[rm4g00]

Anyone?

[veremin]

It might happen due to outdated VMware Tools version.

Anyway, the best option would be to reach our support team directly.

Thanks.

[cparker4486]

Same issue. This is ridiculous.

[Mike Resseler]

Chris,

As stated above, did you create a support call? And if you do, please post the support case ID here and the follow-up after investigation with our engineers
Thanks
Mike

[hchabot]

Same issue here... Anyone found a solution yet ?

[Gostev]

Folks, we do need someone to open a support case, so that we can investigate the issue and find the solution. It's been 4 years now and still no one did that... who will finally be our hero?

[M15ter_E]

Not sure if it is the exact same scenario, but we logged a support case (03578191) for a "Failed to create new binary file" error message we had this week when restoring guest OS files (we weren't getting any warnings about VMware Tools). Apparently in our case it was that we were trying to restore to a deduplicated volume on Windows Server 2012 R2 without having the deduplication feature installed on the server that runs Veeam. In hindsight such a simple thing to overlook.

The annoying thing is that the software tried to warn us about this. There was a message displayed when opening a restore job, but I'd seen it so many times when restoring to other (non-deduped) servers without experiencing issues I hadn't associated it with the restore error. In my haste to get the restore job done (so I could get back to deploying Windows 10, re-commissioning a server, the hardware repairs, negotiating 100+ PC relocations and all the other dozens of jobs I'm in the middle of) I ignored the message and as a result wasted more time troubleshooting than it would have taken to read, understand and action the message. In my opinion the message should be reworded to made it easier to understand that action is required - the way it is currently worded, while factually correct, makes it needlessly complicated; which increases the chances that someone in a hurry will dismiss it.

Displayed message text (I had to Google this as our server no longer displays it): "Copying data from deduplicated volumes requires that the console is installed on Windows Server 2012 R2 or later with the data deduplication feature enabled.
Restoring files from deduplicated volumes requires that the mount server associated with the source backup repository uses Windows Server 2012 R2 or later with data deduplication feature enabled."

Suggested message text: "Warning: The data deduplication feature does not appear to be installed on the mount server. To avoid issues with copying/restoring files to deduplicated volumes, please ensure the data deduplication feature is installed (requires Windows Server 2012 R2 or later). See KB?????? for further info." Ideally the KB article would then go on to explain what the mount server is, for the people who didn't know.

Hopefully someone will find this useful one day.

[foggy]

Thanks, Jason. We will consider changing the wording.