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
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?
Moving a current install to a new server with a twist
I am currently running BE 22.2 Rev. 1193. This is running on an old Server 2012 R2 installation. I am tasked with moving to a new server 2022 installation. I am going to install the latest BE 25 and then I have to migrate the catalog to that new installation. There is a twist, however. New security requirements say that I must not have the SQL database running on the same server as BE. Meaning I have to install the new BE connected to an enterprise SQL installation on another server. My plan is to install BE 25 using the custom install feature in order to tell it the new SQL server to use and then use BEUtility to move the database from the old server to the new server. My question is: Is this going to work or do I have to jump through other hoops in order to get this done in the constraints that I now have? Thanks in advance. Mike
Arctera Backup Exec 25.0 1193 (64-bit)
Hello everybody, yesterday we tried to install the initial release of the latest Arctera Backup Exec 25.0 1193 (64-bit) without Hotfix. This was done on a fresh installation of Windows 2016 v1607 server with Net Framework 4.0 installed (both with Cumulative Updates from March 2025). Unfortunately we were not able to install Arctera Backup Exec 25.0 1193 (64-bit) and we remember similar experiences with older versions. The installation wizard was not able to install SQL Express 2017 and installation was cancelled. Installing this SQL Express 2017 version from the Backup Exec 25.0 1193 (64-bit) package manually works very well, but that's not how we intend to finally install Arctera Backup Exec in our environment. Has anybody an idea, why SQL Express 2017 installation is broken in Arctera Backup 25.0 1193 (64-bit) or has anybody similar experiences and knows how to fix it? We will have further tests in virtual environments to get an idea, what's wrong! We really hope, this will be fixed by Arctera. Also, we could not find an information what Outlook versions are supported to create PST-file-exports. We would appreciate an improvement in the Exchange restore wizard regarding PST-file export, as it's always confusing how to use it correctly and there are no examples available in the offline help, so it's always guessing, if you don't do this on a regular basis. ThanksTroubleshooting Persistent Reappearing Meetings in Exchange + Arctera Integration
We've been running into a really annoying issue lately in our Exchange environment, which is integrated with Arctera, and I'm hoping someone here might have seen something similar or have some insights. The problem is that some users are experiencing old or deleted calendar meetings reappearing in their Outlook calendars. They decline them, delete them properly (even emptying Deleted Items), but days or weeks later, the same meeting invite can pop back up. It's causing significant calendar clutter and confusion. Initially, we were looking into potential sync issues related specifically to the Exchange-Arctera integration, wondering if maybe updates weren't propagating correctly or if there was some conflict in how shared calendar resources are handled between the two systems. We're still investigating that angle. However, while digging deeper into the Exchange side of things, I stumbled across a pretty comprehensive article that outlines several Exchange-specific reasons why this might happen, independent of any integration. It covers things like: Lingering invites in different mail folders. Corrupt recurring meeting series. Issues with calendar delegation permissions. The Calendar Repair Assistant (CRA) potentially misbehaving. Outdated clients or mobile device sync problems. Here's the article if anyone's interested: How to Stop Exchange Server from Recreating Meetings? It has some useful steps for both end-users and admins (like PowerShell commands to check/disable CRA or repair mailboxes). My question for this group is: Has anyone using an Exchange + Arctera setup encountered this specific "ghost meeting" issue? If you did, did you find the root cause was purely within Exchange (like one of the points in the article), or did you discover an interaction or configuration nuance related to the Arctera integration that was contributing to it? We're particularly curious if certain sync settings or how delegate access is managed across both platforms might play a role. Any shared experiences or troubleshooting tips specifically within the Exchange/Arctera context would be hugely appreciated! Thanks in advance,
