Weird Failed jobs and Backup job details

[zadrian]

I am using Veeam 9.5.4.2615 (update 4) Enterprise Plus for VMware. Backing up VMs on VMware Std 6.7u1 (11675023 ).
The backup repository is a Synology RS2416RP+ with RAID 10 12x 10TB SATA
- Limit max concurrent task to 8
- (ticked) Align backup file data blocks
- (unticked) Decompress backup data blocks before storing
- (ticked) Use per-VM backup files
- Enabled vPower NFS

Job settings (most jobs, especially for weekend jobs that include all VMs)
- Retention points to keep : 5
- Reverse Increment
- Active Full backup (Saturday) *Note that 1st 6 jobs on Saturdays and next 6 jobs on Sunday*
- Storage-level corruption guard (Weekly on Saturdays) *Note that 1st 6 jobs on Saturdays and next 6 jobs on Sunday*
- Data Reduction (ticked all recommended ones)
- CBT enabled
- retry failed items 5 times, wait 100 minutes before next attempt

I have several jobs, but mostly only 1 VM per job. Only 4 jobs have 2 or 4 jobs (smaller VMs) per job.
I can have a few failed jobs (last 24 hours).

ERROR or FAILED reason
- Processing Svr02 (Web App Svr Development) Error: The user name or password is incorrect.
Failed to open storage for read/write access. Storage: [\\NAS_IP_ADDRESS\Veeam\Weekly-10\Svr02.vm-136_478DD2019-03-24T123534.vbk].

Weird thing....
1. The retry runs at a later time and succeed
2. It still shows as fail in the "last 24 hour tab"
3. It sends email of job failure (3 jobs succeed, 1 job fail)
4. It send email of job failure (Email header is pink, but text shows 1 job retry succeed)
5. In the "jobs tab" backup job, only details of the retry job is shown, other 3 jobs is now shown.

[Andreas Neufert]

In the end it means that the Synology do not accept the Veeam connection at this point in time.
Please check your settings on the Synolgy side if you can optimize how many connections you can open to it.
As well please check processor/RAM load on the Synlology.


If it happens after the optimization, please open a support ticket and let our support check your logs.

[zadrian]

I do not mind the error....as I mentioned, the retry at a later time succeeds but the reporting is very weird...

[foggy]

Will the 'Suppress notifications until the last retry' check box address at least some weirdness for you?

[zadrian]

Thats only for email notifications....but there are a few points...

1. In GUI only shows status of the retry job
2. Email notification shows failure but text says success

[foggy]

If in p.1 you mean the job session log, then you can review previous job runs with the help of arrow keys.

[zadrian]

Ok...thanks....