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
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!18Views0likes1CommentCan't append despite infinite append and free space
Hi, collecting logs to submit a ticket but figured I'd post here as well in case there's something easily/silly I'm missing. Backup servers to Tape media. Job A - fails because of shenanigans on our end. Some servers were done, others failed. Job B - Added the failed servers, trying to append to the same tape. Media Properties: Media set: Infinite overwrite and append (a set I created specifically for this purpose) Overwrite protected: Infinite - Do not overwrite Appendable until: Infinite - Allow append Media "Available capacity": 7.48 TB Job Details: Storage > Media Set > "When this job begins" - Append to media, overwrite if no appendable media is available." I tried the "append, cancel job if no appendable is available" but it would instantly cancel. Changed to the above and now instantly does "You cannot use the available media in the drive for this job because it is not overwritable" Anyone know why it's just refusing to append? A setting or something I'm missing maybe? Tried restarting the server, removing/pushing the tape back in, not really sure what else I can do.Solved65Views0likes7CommentsLinux 5.14.0-522.el9.x86_64 not supported by RALUS
I'm trying to install Backup Exec Agent for Linux and Unix Servers 25.0.1193-0 on CentOS Stream 9. I get an error: Checking system communication: Checking OS version on v1btx1 ............. Linux 5.14.0-522.el9.x86_64 Checking system support for v1btx1 ... Linux 5.14.0-522.el9.x86_64 not supported by RALUS Why is this happening? CentOS 9 supports Backup Exec 25 - Software Compatibility List 25.x (SCL)Solved30Views0likes2CommentsUnable open Veritas backup Exec Console
We are unable to open veritas backup console on windows servers 2012. The moment we open the console it automatically disappears. Current version Veritas Backup Exec is 20.0.1137, Kindly help to resolve this problemdineshbhandare23 days agoLevel 224Views0likes2CommentsAdding 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 youDamjanL29 days agoLevel 219Views0likes2CommentsCan 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'35Views0likes2Comments- Girishrox2 months agoModerator54Views1like0Comments
Any BE22 support for OES 2024.4 with SLES 15 SP4?
Hi, I need to migrate an OES 2018 environment that is being backed up with BE22 to one that is running OES 2024.4 which runs on SLES 15 SP4. There are various constrainsts meaning I will have to run and backup the OES2028 and OES 2024.4 systems at the same time. The latest BE22 RALUS and patches (up to ralus1193.1626HF311011 installs in OES 2024.4/SLES 15 SP4 but when I add try to add the Linux server to BackupExec the ralus program crashes and exists during the last stage. Is it possible to run BE23 and backup OES2018 servers running the BE22 ralus? Any thoughts about what I can do?Guy_Dawson2 months agoLevel 333Views0likes2CommentsDelete old backups after reinstalling veritas backup exec
Hi, Some background: I had an trial version of veritas backup installed that a backup job running for some months. The backup job eventually began to fail becuase the trial period ran out. Therefore i was tasked with licensing the software. In doing so i tried to upgrade the software to version 24 but i was unable to do so because the trial version had some components installed that i was unsuccessful in trying to remove. Therefore i decided to uninstall the old version of veritas backup entirely and then install veritas backup 24. The problem: I'm trying to delete some old backup files inside of a "trashbox" folder that are picking up space on my NAS. These backup files were created from the trial version of veritas backup that i had installed. When I try to delete the files it says I need permission from Unix User\Nobody to remove the files. I assume this is because i needed to delete these files with the old version of veritas backup before I uninstalled it. Is there any way to fix this? as I need to free up the space in order to make room for the new backup jobs that i have configured and are already running.Solvedkadmin102 months agoLevel 288Views0likes4Comments