Welcome to your hub for Data Compliance, InfoScale, and Backup Exec discussions. Learn more about recent changes to the VOX Community here.
Forum Widgets
Recent Discussions
Backup Exec does not backup files and subfolders selected, without any error
Dear comunity A customer has an Win2019 Server (DC and fileshae), we were back up with backup exec 23. But in some folders on a disk it does not backup any informations in some subfolders (Simplified Disaster Recovery: on). Lucky to see all public and privatefolders were backed up, and lucky me windows shadowcopy funtion safed us from data loss... If I select a file or subfolder in extra backupjob (eg. 774MB see attachment) the backup runs without any error,with in seconds, but the file(s) selected are not in the backup. The same problem exitsts with v21.4 and now v23. I dit not tried to update to v24 or 25. We use the backup agent, because the customer runs it server under vCenter 5.5 essentials... Yes we know it is out of date... Any idea is welcome. Cheers Daniel
Oracle Backup fails with 0xe0001403 login account could not be authenticated
I am not able to run a succesful Oracle backup. The log file on the Oracle Server from BEUTility looks as if the ORACLE-part runs fine (message logon succesful), but something else goes wrong. Whatever I do , the jobs end with error 0xe0001403. The message text asks me to update logon credentials on "the list of authentication resources" on the BE Server (sorry, my system is in german). The only point I can think of is "Login accounts administration" Can someone give me a hint? EDIT: Oracle Server and Backup Exec Server are in a Workgroup "PRAXIS" - not a Windows Domain
recover old data from other backup exec versions
How can I recover backups made on an external HD via Backup Exec from 2017 to the end of 2020, considering that there have been version updates? At the moment, the only way to recover would be to install the most recent Backup Exec and hope to be able to inventory, catalog and restore? Should that work? From what I've seen in other cases where attempts to recover old backups were always on tape, and this seems to make it more complex than just a USB HD. Thank you in advance for your attention
outdated powershell modules and little functionality
Already more than 10 years ago there were requests to control Backup Exec by Powershell. I get the impression that Veritas makes no effort to optimize BMECLI. Even simple functions are still not implemented, the module is from 2021. New functions are constantly being added to the application, but much remains the same. Bugs that were already included in 2022 are present in 2023 and 2024. Duplication of backup sets from a given time-range is not possible by GUI, powershell or other way. It seems to me that we are riding a dead horse but haven't realized it yet.
BackupExec 23.0 not loading tapes to another drive
We are using BackupExec 23.0 and a IBM Tape Library with 2 drives. It works fine with one drive, but tapes are not loading to another drive now. It worked before. We can find bother drive in BackupExec 23.0, and the status of the drive not loading tapes is Active. Both drives are in the Windows Device Manager. The drive status in GUI of the IBM Tape Library are good too. What the issue could be?
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!The Backup Exec installer is blocked by Windows Security Policies. 100013381
Hi, i have trouble installing the Agent Updates BE 25 1193.1011. The installation of the Agent 1193.000 was fine, on a few machines i needed to unblock the ZIP/ISO File first. But i am not able to upgrade the agents, even a complete uninstall of the agent reboot the server install agent 1193.0000 was fine, but update fails. Even a remote push installation fails. I tried this article https://www.veritas.com/support/de_DE/article.100013381 But this doesn´t help at all. I tried to disable all Defender Options but this fails. Is there any solution?
