Restore job failed Error: Cannot complete file creation operation.

Hey guys

We’re doing some VeeamZIPs and directly restore VMs them to a backup-NAS which is added in Veeam via SMB. Since beginning of the year (or even before. The last restore was made on the 30th November 2023) we’re not able to do this operation anymore. We’re getting the following error message: “Restore job failed Error: Cannot complete file creation operation.”

The logs show the following:

>05.01.2024 11:16:02.757] <01> Error        Restore job has been failed
f05.01.2024 11:16:02.757] <01> Error        Make datastore directory failed, datacenter ref = datacenter-2, directory name = "obackupnas] backup20240103-xxx" (System.Exception)
p05.01.2024 11:16:02.757] <01> Error           bei Veeam.Backup.ViSoap.CSoapConnection.CreateDatastoreDirectory(String datacenterRef, String dirName)
r05.01.2024 11:16:02.757] <01> Error           bei Veeam.Backup.ViSoap.CSoapDatastore25.CreateDirectory(CSoapDatastoreDirectory parent, String relativePath)
e05.01.2024 11:16:02.757] <01> Error           bei Veeam.Backup.Core.CNfcFileCommander.CreateSoapDirectory(CSoapPath soapPath)
p05.01.2024 11:16:02.757] <01> Error           bei Veeam.Backup.Core.CViVmRestoreTarget.PrepareDatastoreDir(Boolean allowedToCreateDir, CSoapPath preferredPath)
d05.01.2024 11:16:02.757] <01> Error           bei Veeam.Backup.Core.CViVmRestoreTarget.PrepareTargetDir(Boolean needCreateDir, CSoapPath preferredTargetDirPath)
r05.01.2024 11:16:02.757] <01> Error           bei Veeam.Backup.Core.CViVmRestoreTarget.PrepareTargetDir(CSoapPath preferredTargetDirPath)
r05.01.2024 11:16:02.757] <01> Error           bei Veeam.Backup.Core.CViVmRestorerImpl.RestoreConfig(CSoapPath targetVmDirPath, CViVmRestoreTarget restoreTarget, IViVmRestoreSource restoreSource, COibSummary summary)
m05.01.2024 11:16:02.757] <01> Error           bei Veeam.Backup.Core.CViVmRestorerImpl.RestoreImpl(ITask task, IClientContainer sourceClientContainer, CViVmRestoreTarget restoreTarget, IViVmRestoreSource source, COibSummary summary)
m05.01.2024 11:16:02.757] <01> Error           bei Veeam.Backup.Core.CViVmRestoreProcessor.RestoreImpl(CRestoreTask task, IViVmRestoreSource restoreSource, COib oib, CStoragei] restoreStorages)
r05.01.2024 11:16:02.757] <01> Error           bei Veeam.Backup.Core.CViVmRestoreProcessor.Restore(CViVmRestoreSourceProvider restoreSource, COib oib, CStoragei] restoreStorages)
r05.01.2024 11:16:02.757] <01> Error           bei Veeam.Backup.Core.CViVmRestorer.DoRestore(IStopSessionSync sync, IStorageAccessor accessor)
e05.01.2024 11:16:02.757] <01> Error           bei Veeam.Backup.Core.CVmRestorer.Restore(CBackup localBackup)
a05.01.2024 11:16:02.757] <01> Error           bei Veeam.Backup.Core.CVmRestorer.Restore(CRestoreSession jobSess, CBackup localBackup, IVmRestorer vmRestorer, IStopSessionSync sync)
 05.01.2024 11:16:02.757] <01> Error           bei Veeam.Backup.Core.CVmRestoreExecutor.ExecuteRestore(IRestoreOibSpec spec, CStopSessionControl sync)
 05.01.2024 11:16:02.757] <01> Error           bei Veeam.Backup.Core.CLocalRetryableMethod`1.Execute()
c05.01.2024 11:16:02.757] <01> Error           bei Veeam.Backup.Core.CRetryableRestore`1.Execute(Boolean executeOibPrepare)
e05.01.2024 11:16:02.757] <01> Error           bei Veeam.Backup.Core.CVmRestoreExecutor.Execute()
c05.01.2024 11:16:02.757] <01> Error        Fault "CannotCreateFileFault", detail "<CannotCreateFileFault xmlns="urn:vim25" xsi:type="CannotCreateFile"

However, we can still create backups as usual on the backup-NAS and we can restore the backups to our local productive storage, but not the backup-NAS. We’re using the community edition.

Did someone already encountered this error and has a fix for that? Would be much appreachiated.

BR Marcel

Page 1 / 1

Based on the logs you posted it seems that it cannot create the datastore for the VM on the NAS. If this is just for backups using SMB that could be the issue. Also it might be a limitation of the CE edition of the software as well. Need to check that. Worse case you could open a case with support.

Hey Chris

Thanks for your response.
We’re doing the restores like describe above for a few months now and it just stopped working. I also checked the permissions on the NAS, of course, which are OK. Additionally the backups could be written when running a backup job. This is kind of crazy.

BR Marcel

Ok thanks for the details. What version of Veeam are you running? If an older version maybe try upgrading to the latest 12.1 and see if that resolves the issue or the latest patch for the version you are using.

Good point, thanks! Currently we’re on 12.0.0.1420 P20230718. Let me quickly check the release notes of the latest version.

That is definitely the latest patch for v12. If you want 12.1 details check here - KB4510: Release History for Veeam Backup & Replication 12.1

If this is SMB it's not an issue with long file names / special characters is it?

Yeah, I’m not super familiar with this log, but it says the target directory name is “ backupnas] backup20240103-xxx” but I’m not sure if the brackets are in the actual directory name or are to denote the repository name or the name of the actual NAS or what….

My guess is the backup NAS hostname listed in the log isn’t the actual name given by the poster (though would need them to confirm) as part of the path name, but rather just the display of the name given by Veeam, like vSphere does with datastores ( (datastore-name] ) for various cmd line tasks, or even when adding advanced parameters for a Host (e.g. syslog config).

That being said, if it’s possible to change the path name, or at least create a different path to test on with 1. a shorter name, and 2. if there are characters in the path name, one without characters… that would eliminate those 2 potential causes.

Hey guys

Thanks for all the answers. I was infected by a virus, so I could not answer in time.

Unfortunately the update to 12.0.1 did not fix the issue.

>backupnas] is the datastore name, also the hostname and the backup repository in veeam. So that’s a bit confusing. Anyhow, found that the issue is ibackupnas] (datastore) on vcenter and no user can create folders on that datastore. It’s now cleary that it’s not a veeam problem and I have to look into vcenter. Nothing changed from me side, so the digging begins now.

Thanks again to all! It’s good to know that you’re there to help. Really appreciated!

Best regards
Marcel

Sorry to hear about the virus issue. Hopefully you got that all sorted.

Thank you also for the update...glad you were able to narrow down the issue was not on the Veeam side but vCenter side.

To clarify, the virus was a medical issues. Not an IT one

Hey guys

Thanks for all the answers. I was infected by a virus, so I could not answer in time.

Unfortunately the update to 12.0.1 did not fix the issue.

Thanks again to all! It’s good to know that you’re there to help. Really appreciated!

Best regards
Marcel

Glad to hear you figured out the NAS issue and hopefully get that addressed. Sorry to hear about the virus infection not a nice thing to hear.

To clarify, the virus was a medical issues. Not an IT one

Oh LOL

To clarify, the virus was a medical issues. Not an IT one

Gotcha

Hey @marcel123456 -

Just wanted to follow-up on your post and confirm you found out the resolution on your own was the datastore/nas in vCenter and not Veeam? I would recommend selecting your comment there above as what “resolved” your issue to benefit others who may experience the same issue.

Thanks!

Hey @coolsport00

Thanks for the reminder. I selected my last on-topic message as the solution for this issue.

BR Marcel

Hey @coolsport00

Thanks for the reminder. I selected my last on-topic message as the solution for this issue.

BR Marcel

Great to see you were able to get an answer to your issue.

Comment

Sign up

Login to the community

Scanning file for viruses.

This file cannot be downloaded