Does this event as well cause backup jobs to fail and if so what is the error there?
You mention CAS (physical) and MBES (Virtual).
Do both BE server connect to this NAS and do both report this event or just the one server and if so which one?
Did this ever work, meaning when did the issue of these event start?
I'm getting this also.
BE21.3
BE server is on Windows Server 2019
Remote server being backed up is 2012r2 and hosts the DAS the backup is going to. (yes its odd, changing soon)
Backup is B2D being processed on the remote server. I did not have this issue until we were required to upgrade from 20.6 to 21.3. Tech support required us to upgrade before they would provide support to fix a database entry issue.
Now the database is working but I'm constantly getting these errors.
All servers are Dell 520 and 540's. All are updated with the most current SUU. All Windows and BE udpates are in place.
The backup this weekend was my first successful backup in nearly a month due to this and I still got 20 BE errors.
All errors are 33808, 'An error occurred while processing a B2D command. Drive: OpenPosMTF() CreateFile failed, retrying(...file location.bkf). Error=32
This is followed about 15 seconds later by an error saying it succeeded after 1 retry Error=0
Do you have one B2D folder on the DAS or do you have multiple B2D folder on the DAS?
What is the concurrency you have specified for the B2D device(s)
How many jobs do run in parallel?
Maybe you want to reduce the concurrency specified for the device and/or schedule some jobs earlier /later so that there are less jobs running at the same time and see if that makes any difference.
Do you have one B2D folder on the DAS or do you have multiple B2D folder on the DAS?
- The DAS only contains the .BKF files and all are written directly to the DAS without being contained in a folder so essentially being treated as being in 1 folder. I've been considering changing this so each server has it's own folder on the DAS but would that help?
What is the concurrency you have specified for the B2D device(s)
- Concurrent write sessions: 3
How many jobs do run in parallel?
- A maximum of 2. They are all spaced out so they shouldn't overlap too much. Most are very small backups in the 200GB realm and finish in a few hours. The main one at around 2TB takes about 2.5 days typically for B2D only and another 12 hrs for duplication to tape.
Maybe you want to reduce the concurrency specified for the device and/or schedule some jobs earlier /later so that there are less jobs running at the same time and see if that makes any difference.
- My current challenge is in the B2D transfer rate. None of them break 700MB/min and the worst is about 350-450MB/minute on a 6GB SAS connection. When it duplicates DAS to Tape it runs at around 1.7GB/min.
- Also, just received a predictive drive failure this morning for the DAS. I'm curious to see if this issue remediates itself with the replacement of the drive.
