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
Catalog Job behaviour after reboot ? resume possible ?
Hi , we have an older BE instance V 20.4 long story short - we lost the catalog after a Server crash (no catalog Backups :-( )- and so we have to rescan (catalog) the jobs details from a Dell Datadomain Storage. The job runs about a few days now - trillions of mini files deduplicated on a Datadomain - make this whole process a pain in the A** My question is : I have to reboot the Backup Exec Server now. what happens if i stop the catalog job and start a new one after the reboot ? Does the catalog start at the point where it ended ? or does it start the whole catalog process from the beginning ? Thank you!
Backup Exec 21.4 - change SQL version, unable to create SDR iso
Backup exec 21.4 runs on SQL 2014 express 32bit. Server 2025. Is there a way to create a new database on SQL express 64bit? I installed SQL express 2022 64bit but I think the database is still on SQL 2014 express 32bit. ADK is installed but Backup exec doesn't see it so I am unable to create a SDR iso. Thanks
Running into exceptions on one server
Since a few weeks Backup Exec backups on a non virtualized server are finishing with exceptions, pointing to various files in Sophos folders in C:\ProgramData\Sophos\Management Communications System\Endpoint\Cache and after excluding this folder a few days later in C:\ProgramData\Sophos\Management Communications System\Endpoint\Trail due to the files being in use. Is there any known documentation which folders to exclude from Backup Exec (latest version) on a server (Windows Server 2022) with Sophos Central Server Protection to avoid this kind of conflict and how to keep an SDR compatible backup as result? Best greetings from Germany OlafA user was added to or removed from a group while a backup job was running
I use Backup Exec for backup jobs, but I noticed that a user was added or removed from a group during the backup process. Since I run backups daily, this occurs almost every day at a specific time. Is this a normal occurrence?Recovering encryption key from Backup Exec 14.1 SQL database
So... I have to recover some data from a Backup Exec LTO. The desired backup set is encrypted, and, naturally, no one remembers the keyname/passphrase. So I can't recreate it. However... one of the other backup sets on the tape is the Backup Exec SQL database (BKUPEXEC), and it is not encrypted. My understanding is that the database can be restored, and it will contain the magic key... but it's not at all clear to me how I go about restoring the database. I am using BE 15 (14.2) and have bumbled about trying to restore BKUPEXEC (starting with the master, as recommended by the restore dialog hints) to the same installation, and to an installation on a different machine, but all I get is messages like: Completed status: Failed Final error: 0xe00084a4 - The SQL Server system databases (master, model, msdb) and the Backup Exec database (bedb) cannot be directly restored on the active Backup Exec SQL Server instance. It can be accomplished with a remote media server. Please consult documentation for instructions on how to accomplish this task. Final error category: Job Errors For additional information regarding this error refer to link V-79-57344-33956 the V-79-57344-33956 link is dead. I've tried to find other references but only found this, here: https://vox.veritas.com/discussions/backup-exec/the-active-backup-exec-sql-server-instance-cannot-have-its-master-database/115808 which seems to be implying you can only restore a database (using BEUtil.exe) from backup files on disc... but that doesn't make any sense, why would they allow you to back the databases onto tape if you can't restore them somehow?? Any pointers would be very welcome!How to use a disk-based-storage with different credentials?
Backup Exec server ver 21.4 Windows server 2019 with domain (AD) Backup Exec installed with a domain account and it's services are also started with a domain account. We are backing up a few server within the domain. Everything works! We have a NAS which we have joined to the domain. We share a folder at the NAS with AD privilegiers and Backup Exec are able to create a disk-based-storage to //192.168.100.100/sharedfoldername, since the service account for BE have the rights to that folder. Simple and understandable. BUT. In case of virus/malware entering the system and getting access to the AD, the virus could easily infect even the backup folder at the NAS. To make it more difficult, we would like to remove the AD join from the NAS, setting up a local account at the NAS and let BE using theese credentials for the local user at the NAS to connect the disk folder. I that even possible? How do I tell BE to use different name/password for a disk folder? Any workaround? Thanks in advance Best regards Martin
Backup jobs failing that were not failing before.
Hi, New to BackupExec. We have a Backupexec server that runs on a Windows 2016 server that was backing up an SQL database running on a Windows 2012R2 server that had been running fine. Recently, the backups have started failing with the following error in the logs: The job failed with the following error: A communications failure has occurred with a SQL Server resource. The backup credentials test fine when looking at the backup job. Looking deeper into things, when this error occurs, the event logs on the Windows 2012 server where the SQL database resides shows the following error in it's event logs: The server-side authentication level policy does not allow the user "Administrator" from address (backupexec server's address) to activate DCOM server. Please raise the activation authentication level to at least to RPC_C-AUTHN_LEVEL_PKT_INTEGRITY From what I can see, it has something to do with a Windows patch, but there haven't been any recent patches ran on either server. Any ideas are greatly appreciated. BackupExec is version 20.6Backup failed for a Hyper-V guest of a Linux Virtual Appliance
I tried to backup a Hyper-V guest of a Linux Virtual Appliance. However, a error "E0009757 - A Backup Exec server cannot back itself up when it is installed on a virtual machine" occurred. But the Backup Exec server is installed on a physical server. Anyone know how to fix it? Thanks,
Error with Instant Cloud Recovery Configuration setup
I am trying to setup Instant Cloud Recovery but after I sign into Azure/Powershell then choose my Subscription from the drop down list and click next, I get error: Operation returned an invalid status code 'BadRequest'. I have 3 subscriptions with existing Azure resources, it errors on all of them. The azure account is the subscription owner and a global admin. I am running Backup Exec 22.2 1193.1626 Any help please.
