Configure Storage not seeing Tape Drives
Long and short of it: Windows 2022 running BE v25 Dell/EMC ML3 Library & ML3e Library expansion - with six(6) LTO-7 drives Drives connected to Dell server using Dell 12Gbps SAS HBAs Issue: All Tape Library entries in Windows device manager are giving a Code 37, though the SCSI tape drives are showing fine. When running Configure Storage -> Tape Storage, only the Hot swap option is present. Below is a basic cable diagram (I did not do the original build out but am now responsible for getting it running - sigh.) I know I must be missing something obvious. Any help would be appreciated. Thanks!What is the retention period for Annual backup
Dear Support, What is the retention period I need to set for my Yearly backup to Tape. (Media set propeties please see the screenshot attached). Retention perid/ overwrite protection period / Append period. Please note this a one time backup only. Backup to Tape drive (LTO6) The purpose of this backup is to keep every year a copy of that year's backup in a seperate LTO Tape. (This is not going to overwrite). This is only for future use in case management needed any files from previous years. I need a proper retention policy to keep for these kind of backups. Thank you.
Backup Exec server cannot access the specified storage device (tape library) in CAS/MBES environment
We have many backup policies in our environment and almost all of them are having the same configuration. It may sound odd but we have one backup for each VM in this environment. All of them are having a weekly job and daily incremental job. As the second stage, each of these jobs is linked to a duplication job which duplicates the correspondent backup set to a DR open storage device. Every first Monday of the month we get the last full backup set and duplicate it to LTO5 tapes and keep them for long retention as monthly backups. The tape library is attached to one of the MBES servers. The problem is that there are a few jobs that cannot see the tape library during monthly tape duplications on each month. The jobs that cannot access the tape library are completely random. So, if one backup policy cannot see the tape library in one month it may work fine next month. Refreshing the Backup Exec services on CAS and two MBESs have not helped in our case. The only way we used to get the full backup sets duplicated to tape was to manually find the backup sets in the deduped OST and duplicated them to the tape library. Just recently, I have found a work around to make the backup policies which have trouble accessing the library to find the device and kick off the monthly duplication. However, after a few jobs, they go to the same state and I have to do the same process again until all of the backup policies are duplicated to tape successfully. We also get "ODBC access error. Possible lost connection to database or unsuccessful access to catalog index in the database" error message on CAS. Apparently, this happens when there is a communication drop out between CAS and one of the MBES servers. I guess this might be causing the monthly duplication issue we are facing in the environment. This is already escalated to Veritas support and is still under investigation. My question is if anybody knows a permanent fix for this issue?
