Backup Exec 2014 - Error code 57 - The parameter is incorrect

[CDRossi]

Hello

I recieved this error whlle doing a full mailbox backup of Exchange 2010. Backup Exec 2014 is installed on a Windows Server 2008 R2 Enterprise SP1 64 bit.

The backup is to Disk and the job has run successfully in the past. The event ID in the Server logs is 34113 - Cannot extract mailbox messages from the Exchange backup.

The version of Backup Exec 2014 is 14.1 Rev 1786(64 bit).

I'm looking to understand this issue and to find a solution.

Thank you.

[pkh]

Check your job properties to see where the staging for the backup takes place. By default, this is C:\temp. Make sure the disk has sufficient space to hold the entire Information Store

[CDRossi]

It does. The backup is going to a storage server locally on our network . The available space is 1.25 Terabytes and the job typically needs 90 Gigabytes. There are other jobs that go to the same backup location that have run successfully after this job that amounted to more than 90 Gigabytes. Is there anythinig else that may cause this issue?

[pkh]

It is not the final backup destination that I am talking about. It is the staging destination that you should check. These two are not the same

[VJware]

This is a very generic error. Usually, there is another line at the end of this error message, pls post the same.

Pls check, verify, perform the following steps:-

1) If AOFO is enabled for the Exchange backup, turn it off.

2) Do ensure the BE account has the necessary prerequisites as per this KB - https://support.symantec.com/en_US/article.TECH184449.html

3) Error 57 translates to - A Network Adapter Hardware error occured

Do ensure the Network settings in the job such as IPv4 or IPv6, subnet etc are chosen properly. As the error says, focus on the network settings.

4) Lastly, if the above do not help, then create the following keys on the BE media server (as you are backing up to disk):-

Key : HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VirtFile
Value: VFF Extended Timeout
Type: DWORD
Set value (Decimal) to 600.

Key : HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VirtFile
Value: Detach Timeout
Type: DWORD
Set value (Decimal) to 10000

Key : HKLM\SOFTWARE\Symantec\Backup Exec For Windows\Backup Exec\Engine\Exchange
Value: OnHostTemp
Type: String
Set value (String) to C:\Temp or any other NTFS, local volume on the BE server which has plenty of free space to stage the entire Information Store

Restart all the Backup Exec Services for the changes to take effect.

[CDRossi]

Hi, thanks for the response. AOFO is not enabled for this job and the BE account does have the proper permissions. The job will often run without issues, but once in a while it will fail, sometimes repeatedly.

What seems to be happening is that the backup will write anywhere from 10-30 GB of the mailbox database EDB file into the B2D destination image folder on the NAS, then BackupExec will log the following:

Error writing file data.

V-79-57344-33935 - The backup-to-disk folder that was specified for this job ran out of disk space. ...

Both the NAS and the media server have more than enough disk space.

What sort of network hardware error did you mean? We have made your registry edits, without success. What else could we try?

Thanks.

[VJware]

Is the option "pre-allocate disk space...." enabled on the Disk Storage's properties ? If yes, disable it.

Also do ensure, compression and disk quotas are not enabled at the target storage end.

If the above doesn't help, try recreating the disk storage.

[CDRossi]

Thanks. No pre-allocate disk space, compression or disk quotas. I did, however, drop the number of concurrent write operations down to 1, and set "auto detect settings" back to enabled (had been enabling buffered reads and writes).

Short of recreating the entire disk store, I deleted Changer.cfg, Folder.cfg, and last_pdi.bin and ran an inventory.

Will let you know if the above has improved the situation.