Exchange restore fails - old server no longer exists as part of DAG
Hi, I am attempting to restore an Exchange 2016 database and log files to an alternate location as flat files. I have previously done this without issue, and tested with another database successfully today, however the server where this mailbox database was backed up from no longer exists and is no longer part of the DAG. The backup fails with the following error: V-79-57344-65072 - Connection to the restore target has been lost. Operation canceled. It seems like the restore job is trying to connect to or check for the original server which was a member of the DAG at the time of the backup that no longer exists as I get the exception in the job log below: The Backup Exec server was unable to connect to the Remote Agent on machine (Machine name removed by me) Any ideas on why this is happening?877Views1like2CommentsBeServer Service crash at 4:00 am
Someone updated to BE 21.2? I did from 21.1 to 21.2 on Monday because Support suggested it to solve an other problem. After that the beserver service crashes at 4:00 am daily. This seems to be smilar to this:https://www.veritas.com/support/en_US/article.100008398 Eventlog shows (sorry it is a german system): event 259 BEDBG A process crash has been detected. Faulting application: beserver.exe 21.0.1200.1899 Faulting module: beserver.exe 21.0.1200.1899 Fault offset 0x456457 Exception code 0xc0000005 event 1026 .NET_Runtime Anwendung: beserver.exe Frameworkversion: v4.0.30319 Beschreibung: Der Prozess wurde aufgrund einer unbehandelten Ausnahme beendet. Ausnahmeinformationen: Ausnahmecode c0000005, Ausnahmeadresse 0000000140456457 event 1000 Application_Error Name der fehlerhaften Anwendung: beserver.exe, Version: 21.0.1200.1899, Zeitstempel: 0x602d14f0 Name des fehlerhaften Moduls: beserver.exe, Version: 21.0.1200.1899, Zeitstempel: 0x602d14f0 Ausnahmecode: 0xc0000005 Fehleroffset: 0x0000000000456457 ID des fehlerhaften Prozesses: 0xec Startzeit der fehlerhaften Anwendung: 0x01d70f2d68b66f79 Pfad der fehlerhaften Anwendung: C:Program FilesSymantecBackup Execbeserver.exe Pfad des fehlerhaften Moduls: C:Program FilesSymantecBackup Execbeserver.exe Berichtskennung: e24257dc-7bcc-11eb-80ef-b02628b8e15b anyone else with this?1.8KViews1like5CommentsBackup exec 20.5 job active status queued forever
Hello, I have just set up a new BE 20.5 server and trying to backup another server using a remote agent. The job stays active : Queued forever. The server is able to start creating 0 byte bkf files on the disk storage. I have tried creating a new storage pool and running the database repair. The test run completes successfully and so do the credential tests. I have applied all of the possible updates for BE and Windows. I have also re-installed BE. Any suggestions on what to try next would be greatly appreciated. Thanks411Views1like0CommentsBackup Exec Services Manager shows server status "Server unavailable" but jobs run fine
We installed a new BE Server in an environment that already had one but it was deactivated because the server was old and weak. The servers to be backed up already had agents installed, but I ran push-update jobs so they would be up to date with the new server. The version of the new BE Server is 20.5. Everything was working fine, the backup tests worked as expected but a day later I opened the Backup Exec Services Manager and realized all the servers show server status "server is unavailable". I can't see nor interact with the services running on the remote servers even though the jobs are running just fine. I've found this: https://www.veritas.com/support/en_US/article.100009920, but WMI seems to be OK(I'm not sure how to test it properly, but the General tab says it connected to the local computer succesfully) Any suggestions?1.4KViews1like3CommentsSDR - You do not have Backup Privilege to run this wizard.
Trying to run the Create an SDR disk wizard and I am getting the error. You do not have Backup Privilege to run this wizard. Contact your system administrator. My login is from a trusted domain. I am in the machine administrator's group. I also tried adding my login to the machine's Backup Operators group. I also tried running Backup Exec as administrator. I can do other functions within BE --- such as backup and restore. Just can run the wizard to create an SDR disk.958Views1like3CommentsDuplicate to tape job automatically gets skipped if the source job fails
This is a feature request. This is the scenario; If a backup to disk job fails for any reason whatsoever, even if it's only missing one file or directory, it automatically causes a duplicate to tape job to get skipped and then it requires creating a manual duplicate to tape job for that backup set just to get your data backed up. If you're backing up multi-terabytes worth of information and a backup fails for a single missing directory, I still want/need that data to be duplicated to tape regardless! The software needs to be smart enough to do this because I can't babysit backup jobs that sometimes take four or five days to complete by themselves, not including verification. Even if the job failed entirely, I would still want whatever data that actually was backed up to be duplicated to tape.698Views1like0CommentsVSR 16 replication restore on different unit
Good Day! I was wondering if it's possible to restore my VSR16 Server in different computer unit ( only application itselfand the configurationwill bethe same ). I've come up with this scenario because what if, one day my VSR server will blown up? And i need to restore my VSR16 Server's configuration and the application itself to a different unit and continue serving my deployed Agents. How is it possible? Any speculation or thoughtful ideas? I was thinking also about Bare Metal Restore but i do only need the application and configuration restoration only. Thank you have a nice day!1.3KViews1like5CommentsStrange Email Notification Messages
Hello all, After a recent install of Veritas SR 16, my email notification messages are nothing short of cryptic. Example below: Description: Result (0x6c8f043d 39 VPRO_INFO_COUNT_EXCEEDED_BACKUP_DELETED Args [1] Arg (0xbab000d 54 \\nas\backup\Server1\SERVER01_D_Drive128_i003.iv2i);)<9 1.0-*-*-* > Anyone have any ideas what this means and how I can get the software to send a readable message? Many thanks in advance.1.3KViews1like2Comments