#1 2019-12-12 18:01:01

Registered: 2019-12-12
Posts: 3

Backup completes with errors, no mail is sent

Job completes but no mail is sent when the below errors are reported. I have tested when running with VMs that do not cause any errors and mail does get sent, so issue is not with the mail configuration. It just seems to get to the end and decide not to send email when there are errors with the task.

We are using NFSv3 in this case, VMware server has Broadcom nics and storage is off FreeNAS system (sync=standard) with Intel nics.

Is there any way to force the mail to get sent?

With NFSv3 and FreeNAS we currently use the default sync=standard, not sure if we should try with sync=always or sync=disabled.

Thank you for any pointers.

Error logs included below:

2019-12-12T01:38:34 | Error code 456 at file dedup-in.c, line 456
Error description: can't rename temp block: /vmfs/volumes/BACKUPS/vmware/data/116790670784987052.tmp, Input/output error
2019-12-12T12:06:58 | Error code 1127 at file common.c, line 1127
Error description: file does not exist: /vmfs/volumes/storage/vmware/20191211164731/hostXX/hostXX.vmx.tmp.map
2019-12-12T12:06:58 | Error code 2416 at file xsibackup.c, line 2416
Error description: could not rename .vmx.tmp file: /vmfs/volumes/storage/vmware/20191211164731/hostXX/hostXX.vmx.tmp.map
2019-12-12T12:07:12 | Error code 2506 at file xsibackup.c, line 2506
Error description: some error was raised while backing up: VMs(RUNNING), error count is: 3
Removed /tmp/xsi dir     OK
Unlocked backup          OK
Removed PID              OK


#2 2019-12-12 19:16:11

Registered: 2017-04-21
Posts: 1,366

Re: Backup completes with errors, no mail is sent

We put our design efforts in trying to comunicate any error through the e-mail report, nevertheless there may be errors or exceptions that can't be reported by e-mail.

In your case you are suffering from an NFS protocol issue which is denoted by the message Input/output error. (c)XSIBackup is somewhat NFS Async safe, as it "waits" until the block is available in the remote FS. In any case using Sync NFS won't hurt performance inside a LAN so you should always use Sync NFS, which is safer. Async should work seamlessly inside a LAN too though.

The sync=xxxxx options you comment aren't NFS options but seem to be volume sync options instead. Try to create a simple volume on a single disk and backup there, your NFS errors might be related to some layer underneath it which is not keeping up with NFS transfer rate.


Board footer