BE16 crashing after .NET 4.8 update but no access to entitlement information to download fix
Frustrating issue because we find ourselves between a rock and a hard place: We inherited our client from their previous IT provider who upped and disappeared overnight, without contact. We've managed via whatever written records they had on hand, with minimal issues so far. However a recent Exchange update required .NET Framework 4.8 be installed and as a result the Backup Exec console now crashes on startup whenever we attempt to load it. I did some quick digging online and found this is a known issue with a known hotfix. Unfortunately the hotfix cannot be downloaded without logging into our Veritas account with entitlements, and there's the rub: we don't have one. We located an account that had been setup, but it has no products attached to it. And we have no other records that we can locate. Our assumption is this may have been tied to the previous IT provider's own accounts instead. I called Veritas support, but they couldn't find record of the client's company name. They attempted to get information from the server, but to do so they have to open the Console, which is the entire reason we're in this mess. They have no solutions other than to come here and ask for advice. And so I do. Is there any way to pull our entitlement information from a file on the system so we can get the support we need to download this hotfix? Or any other workarounds we could consider? Thank you.4.4KViews0likes39CommentsShadow copy component backup failing with error code 13
Performed a multi-stream backup and it indicated shadow copy component failed with file read failed (error code 13). Rest of the drives able to backup. Is it possible to delete the shadow copy component in the client itself or there is a solution to rectify this issue? Thanks.402Views0likes5CommentsWhy is my backup-to-disk-folder offline?
We are using a backup-to-disk-storage on a NAS-share which has been working since a long time A couple of days ago this storage went offline and is still offline. Whenever I try to online it, it takes a couple of minutes, then an error message comes which is not helping me. - I can access the CIFS-share with the account BackupExec is using - I can read files and make new files. The error message says the typical reason is that the B2D-folder was deleted, o r the share is no more available. I think I tested this and there is no problem. Alos, my attempts to import this share in a new storage fail. The error message says there is no B2D-folder which can be imported. Can some one help?370Views0likes2CommentsQuantum Superloader 3 w/ LTO7 HH and BackupExec 20.6
Just installed a Quantum Superloader 3 with an LTO7 HH drive connected to a Windows 2016 server via SAS. I am running fully patched BUEX 20.6. BUEX has been installed and running jobs to networked storage for a few years. I am able to see the library and drive in BUEX. I can inventory and scan the slots of the unit. There is currently 2 blank and 1 cleaning tapes loaded in the unit (slots 3 4 and 2). When I run a job I am getting a message to "Please instert overwritable media into the robotic library using the import command". Any help would be appriciated.Solved435Views0likes4CommentsBackupexec always does 'verify' step even when disabled...
I have disabled 'verify' for the job defaults of every type. When starting a job I also double-check that the 'verify' step is disabled. We are writing to an AWS Tape Gateway appliance, so Backupexec sees it as any other tape drive, but we do not need this step. What am I missing?337Views0likes2Commentshow to configure alerts in opscenter for queued jobs
Hello everybody! sporadically we have a problem with a SAP log backups filling the queue on a dedicated netbackup domain. I am looking for information about configuring an alert in opscenter to monitor the number of queued jobs and send an email if that number is more then a configured value. I did not find something relevant in the opscenter admin guide so I hope that somebody having experience with similar alert would step in and share. thank you in advance!1.8KViews0likes10CommentsBackup Admin died. Need to know how to gather useful information for support.
We have 2 Backup systems running. a 9.1.0 and a 8.3.0 systems. The 8.3.0 was backing up some of our legacy Unix server using clients 7.0 for most of them. We cannot login to the 8.3 system to see if the 7.0 clients will work on the 9.1.0 server (where we want to go). The 8.3 system cannot login to the interface due to error unable to login status 537 connection to the netbackup database was not successful (although the service is running, and yes, we tried to restart the service). 1) how to transfer the profiles (or a profile) from the 8.3.0 system to the 9.1? 2) how to resize the tables if I cannot login to the GUI interface on the 8.3.0 system (plenty of disk space available, like 2.5TB) https://www.veritas.com/support/en_US/article.100051777 https://www.veritas.com/support/en_US/article.100051777 Also, when we get this running, what do we need to gather to have record of for better support when needed?511Views0likes1CommentInaccurate disk storage
Hi All, Anyone can help me figure out or resolve the issue? We have network storage (10TB free/50TB) after deleting the old backup with that we can at least have the space available. but in the BE console shows (46.5TB used/50TB). and that is not accurate to our original capacity which is (10TB free/50TB). It might also cause a failed backup and it turns out to offline status because it is already full. Is there any resolution that might help us to resolve this? Thank you in advance.245Views0likes0Comments