BE 2012 & DataDomain DDBoost OST problem tape full error condition & read / write error
We have a weird problem on one of my customer's site.
I just migrated their backup infrastructure to BE 2012.
I installed Backup Exec 2012 from scratch on a new system Win 2008 R2.
And yes, I installed the dedup option :)
BE 2012 SP3 : 14.0 Rev 1798.1300 (64 bit)
DD OST : 18.104.22.168-3
DD OS : 22.214.171.124-404909
I have created new DDBoost repositories, with a clean DDBoost user which i entered in Backup Exec.
Created my OST DDBoost devices which he proposes alone once I entered the DD hostname.
Concurrent Ops : 4
Split Data stream every : 50 GB
Data Stream Size : 256 KB
Stream handler : Disabled
CLient side dedup : Disabled
Disk space reserve for non BE operations : 1 GB
We have many backups going well, but as we have many servers to backup, Exchange Cluster, Evault, NetApps, Win servers, we have also many problems :
First Problem :
Robotic library destination element full error.
The robotic library has reported a destination element full error condition. This is typically caused by trying to mount media into a drive that already contains media. The drive state has been set to offline. Please attend to this condition.
Second Problem :
xxxx-Full Daily -- The job failed with the following error: A backup storage read/write error has occurred.
If the storage is tape based, this is usually caused by dirty read/write heads in the tape drive. Clean the tape drive, and then try the job again. If the problem persists, try a different tape. You may also need to check for problems with cables, termination, or other hardware issues.
If the storage is disk based, check that the storage subsystem is functioning properly. Review any system logs or vendor specific logs associated with the storage to help determine the source of the problem. You may also want to check any vendor specific documentation for troubleshooting recommendations.
We have tried to update our DDBoost OST, the DDos, and BE was at lasted patches.
We scheduled all jobs to launch separately.
We updated all agents, rebooted all servers, checked our fiber / network connections.
Now we are stuck .. any thoughts, ideas or leads ?