Case ID 01755522 Backup Copy can not generate .vbm file ...

[Zedification]

Hi,

case ID : 01755522

After upgrading to v9 u1, I have a Backup Copy job failed with the error message :
Failed to preprocess target Error: One or more errors occurred.
Unable to create target storage, processing will be retried ...


In the job log file :

Code: Select all

Saving backup meta to '\\server\share\Backup Copy Altavault\Backup Copy Altavault.vbm'
[06.04.2016 12:35:32] <17> Info           [OLSRVBKP01.domacme.com] [FC] Saving file content [<?xml version="1.0" encoding="UTF-8"?><BackupMeta Version="673" OriginalBackupId="babe700e-143f-4e4f-b933-75e201748b38"><VmObjects><VmId><string>ecbd4703-b669-49e0-94c4-073ae7619586</string><string>5402195f-d799-487b-b117-50a2e5c790bb</string><string>33e12143-6f10-4f87-ae3d-f98267b97171</string><string>35152289-d60f-4c94-b0aa-c4afbd8e167a</string><string>fde6731b-6407-4456-a8ad-bcb35d7a3513</string><string>8ce00e27-ad67-42b1-b525-4228a7447743</string><string>b94093fe-35
[06.04.2016 12:35:33] <17> Info     [OLSRVBKP01.domacme.com] [FC] Renaming remote file from [\\server\share\Backup Copy Altavault\Backup Copy Altavault.vbm_3_tmp] to [\\server\share\Backup Copy Altavault\Backup Copy Altavault.vbm]
[06.04.2016 12:35:33] <07> Error    [BackupMetaUpdater] Failed to generate backup meta
[06.04.2016 12:35:33] <07> Error    [OLSRVBKP01.domacme.com] Failed to get item info for \\server\share\Backup Copy Altavault\Backup Copy Altavault.vbm (System.Exception)
[06.04.2016 12:35:33] <07> Error       at Veeam.Backup.ProxyProvider.CProxyFileCommander.GetFsItemInfo(String itemPath)
[06.04.2016 12:35:33] <07> Error       at Veeam.Backup.Core.CRemoteWinFileCommander.GetItem(String link)
[06.04.2016 12:35:33] <07> Error       at Veeam.Backup.Core.CBackupMetaEx.<>c__DisplayClassb.<GenerateAndSaveLocally>b__8(Tuple`2 tuple)
[06.04.2016 12:35:33] <07> Error       at System.Threading.Tasks.Parallel.<>c__DisplayClassf`1.<ForWorker>b__c()
[06.04.2016 12:35:33] <07> Error       at System.Threading.Tasks.Task.InnerInvokeWithArg(Task childTask)
[06.04.2016 12:35:33] <07> Error       at System.Threading.Tasks.Task.<>c__DisplayClass11.<ExecuteSelfReplicating>b__10(Object param0)
[06.04.2016 12:35:33] <07> Error    File not found. File name: \\server\share\Backup Copy Altavault\Backup Copy Altavault.vbm (Veeam.Backup.Common.CAppException)
[06.04.2016 12:35:33] <07> Error       at Veeam.Backup.ProxyProvider.CProxyFileCommander.GetFsItemInfo(String itemPath)
[06.04.2016 12:35:33] <07> Error       at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
[06.04.2016 12:35:33] <07> Error       at System.Threading.Tasks.Task.Wait()
[06.04.2016 12:35:33] <07> Error       at System.Threading.Tasks.Parallel.ForWorker[TLocal](Int32 fromInclusive, Int32 toExclusive, ParallelOptions parallelOptions, Action`1 body, Action`2 bodyWithState, Func`4 bodyWithLocal, Func`1 localInit, Action`1 localFinally)
[06.04.2016 12:35:33] <07> Error       at System.Threading.Tasks.Parallel.ForEachWorker[TSource,TLocal](IEnumerable`1 source, ParallelOptions parallelOptions, Action`1 body, Action`2 bodyWithState, Action`3 bodyWithStateAndIndex, Func`4 bodyWithStateAndLocal, Func`5 bodyWithEverything, Func`1 localInit, Action`1 localFinally)
[06.04.2016 12:35:33] <07> Error       at System.Threading.Tasks.Parallel.ForEach[TSource](IEnumerable`1 source, Action`1 body)
[06.04.2016 12:35:33] <07> Error       at Veeam.Backup.Core.CBackupMetaEx.GenerateAndSaveLocally(IStorageCommander storageCommander, IMetaCommander metaCommander, IEnumerable`1 fcAndPathes, CBackupInfo backupInfo)
[06.04.2016 12:35:33] <07> Error       at Veeam.Backup.Core.CLocalStorageCommander.GenerateAndSaveMetaFile(CBackupInfo backupInfo)
[06.04.2016 12:35:33] <07> Error       at Veeam.Backup.Core.CThreadedBackupMetaUpdater.GenerateMetaSafe(CBackupMetaUpdateRequest[] requests)
[06.04.2016 12:35:33] <01> Error    Error: One or more errors occurred.

The destination Backup Repository is a CIFS type with full right for the credentials set in the job.

I ran some tests, and I can not create any file with the .vbm extention in the repository (ex : touch.vbm)

Thanks for your help.

Edit : The job work with a local Backup Repository. I tryed to recreate the job and the CIFS Backup Repository but no change ...

[foggy]

Am I understanding right, you've tried to manually create a file on repository? Were you able to create a file with any other extension? What kind of storage this CIFS repository is located on?

[Zedification]

Yes, I can create any other extension, but not .vbm. It's a NetApp appliance called Altavault.
it worked before the upgrade.

Edit : When I try to change the extension to .vbm, error : "The file or folder does not exist"

[foggy]

That sounds really strange, let our engineer examine the appliance settings.

[Staring07]

I have this issue as well (Case ID 01755919). It seems that with v9 the process that renames temporary meta data files has changed to one that uses the .vbm extension. As you have noted this isn't permitted on the NetApp appliance as it conflicts with it's data pinning operations.

NetApp will apparently be releasing a fix for this in version 4.2 of AltaVault due around the end of the week.

[Zedification]

OK, thanks for the reply !

I opened a case to the NetApp support this is the answer :

There is a known compatibility issue between Altavault and Veeam version 9.
We currently recommend to continue to use Veeam version 8 until version 9 is qualified and appears on the Interoperability Matrix. http://mysupport.netapp.com/matrix/

We are in contact with Altavault Product Management making them aware of all Customers who desire to use Veeam version 9 so that engineering resources can be assigned accordingly.

Right now i still can’t give an outline on when we will support Veeam 9 but we have a Tracking BURT 982969 which you can subscribe to if you want to get Update on this

See http://mysupport.netapp.com/NOW/cgi-bin ... lay=982969

Hope the version 4.1 will be release soon !

Thanks.

[Zedification]

The Altavault 4.2 version is out. I tested and it work !!! The issues was not in the Veeam side.

Hope this can help ...

[cjbifchor]

Issues after upgrade to 9.0-Copy Job (Case#01808034)



Since the in-place upgrade to 9.0 Copy Jobs to our AltaVault appliance fails with "Unable to create target storage"-"Failed to preprocess target error: One or more errors occured". I try to Populate the repository and I get the "Failed to get disk free space".

Code: Select all

24.05.2016 14:08:53 :: Failed to preprocess target Error: Invalid Signature.
--tr:Error code: 0x80090006
Cannot create folder. Folder path: [\\AltaVault appliance \CIFS\XYZ_CopyJob].
 
--tr:FC: Failed to create directory. Directory path: [\\AltaVault appliance \CIFS\XYZ_CopyJob].
 
--tr:Failed to call DoRpc. CmdName: [FcCreateDir].
Invalid Signature.
Cannot create folder. Folder path: [\\AltaVault appliance \CIFS\XYZ_CopyJob].

[PTide]

Hi,

I believe that the error you've mentioned is related to AltaVault verison. Please check this thread.

Thanks

[cjbifchor]

Case # 0180803

Confirmed, NetApp AltaVault 4.1 is not compatible with Veeam 9.0. Upgrade to 4.2.