CASO Communication stalled in BE2016
I am getting problems with communication stalled on CAS BE16 running on Windows Server 2016. No matter what I tried (patching MMS and CASO, aligned the agents with proper certificates, database repaired or created a fresh one) gave any success. The servers are having sudden bursts of communication and going back to stalled which prevents any monitoring of target servers. I've also run CAS on 2010 and 2015 versions and they do not have such a problem with communication and basically allow live monitoring of the target MMS. All CAS servers are running in exactly same enviroment with necessary ports opened however only BE2016 CAS has this kind of problem. Is there any specific thing I can try to change with BE 2016 to enable communication proper communication between CAS and MMS servers ?Unable to add a Managed Media Server
Hi folks, IHAC with a CAS 20.1 on Windows Server 2016 and a (prospective) MMS also with BE 20.1 on Windows Server 2016. Problem: when rerunning the installation on the MMS with "Managed Media Server" box ticked I can progress until the name of the CAS is entered. After that a message appears that (paraphrased because the messages are in German) asks to enter the credentials for the account on the CAS having authorization to do the connection. The account identified is the default service account used both on the CAS and the MMS, but the ensuing message says "not authorized", and there is no way I can circumvent that. Any ideas or solutions? Regards, Bert
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?
