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
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. Thanks
Troubleshooting 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,
Discovering Devices - Never Completes!! Help PLS!
Hello Everyone, I have a DLT 8000 drive connected via scsi 2940 running win server 2016 x64 std. Vanilla stand alone server install with base service packs/patches. No other SW is installed. Device manager has no errors. Im using the latest backup exec v25. In the Storage Tab of Backup Exec, Discovering devices simply refuses to complete. I've left it running for hours. It just constantly runs marking both tape drive and disk storage as online and offline every five or so minutes. I've tried pausing the devices...discovering devices just cycles marking them offline and then online.. I've tried deleting the tape drive....it is found within a minute and then same discovering devices cycle of marking offline and online. I've tried restarting the server. Same result. Discovering devices just refuses to complete. I've had the same endless discovering device issue with backup exec versions 16, 20 and 21. I've restored the server via image prebackup exec install between each version. I've been messing with this issue for three weeks Please kindly assist!! Thank you to all!
Adding files which are missing
Hi all Maybe someone has an idea how to achieve this: I started full backup of some folders that are on another server (so via network). That server was restarted and backup job stopped. Is there a way i can set up another job, so backup exec checks where it stopped and it will add files that are missing? So like it will check already written files to the tapes and continue where it was interrupted? Thank you
Can not backup synology nas to Tape
Backup EXEC 24.0 Synology DSM 7.0.0 We are trying to backup SMB Share on Synology NAS to Tape. We added NAS to File server in Backup EXEC and enabled backup user share. But Backup Exec try to backup SMB share by NDMP Protocol. Why Backup exec do that? [3816] 2025-02-13T13:47:59.967 [ndmp\ndmpcomm] - Could not resolve the "bews-ndmp" or the "ndmp" service, error code: 10109, using port 10000 [3816] 2025-02-13T13:47:59.967 [ndmp\ndmpcomm] - ndmpConnectEx: Querying the neighbour advertisement cache to discover information on 'synology_FQDN' ... [3816] 2025-02-13T13:48:01.970 [ndmp\ndmpcomm] - ndmpEstablishConnectionUsingNoSpecificAdapter: Could not connect to remote address Synology_IP and port 10000 Errorno : 10061 [3816] 2025-02-13T13:48:01.970 [ndmp\ndmpcomm] - ndmpConnectEx: unable to connect using NetworkOptions to synology_FQDN [3816] 2025-02-13T13:48:03.974 [ndmp\ndmpcomm] - ndmpConnectEx: All attempts to connect to 'synology_FQDN' failed [3816] 2025-02-13T13:48:03.974 [ndmp\ndmpcomm] - ndmpConnectEx: failed to connect to 'synology_FQDN'
