How to deploy Backup Exec via the AWS Marketplace
How to deploy Veritas Backup Exec on AWS Marketplace. Veritas Backup Exec provides simple, rapid, and secure offsite backup to AWS for your in-house virtual and physical environments and protects cloud-based workloads in AWS. Veritas Backup Exec helps customers recover quickly from critical data loss situations, and easily meet data regulatory requirements. By leveraging Veritas Backup Exec in the cloud as well as on-premises, you gain a unified and efficient data protection experience. Deploying Veritas Backup Exec via marketplace frees businesses from purchasing and managing IT infrastructure and enables them tomove to a more cost-efficient operational expense (OpEx) model. To learn “What’s New” with Backup Exec, visit the Veritas Backup Exec webpage. Steps to deploy the Veritas Backup Exec in AWS Marketplace: Through the AWS Marketplace, you can easily and quickly deploy the Veritas Backup Exec. 1. Visit AWS Marketplace and click on “Continue to Subscribe” to use Veritas Backup Exec. Note: This is the Veritas Backup Exec for AWS BYOL. 2. Click “Continue” to take you to the AWS portal. Log in to the AWS portal and click “Continue to Configuration”. 3. Set the Delivery Method to “Backup Exec Base Instance”, Software Version to the latest version of Veritas Backup Exec available, and Region to your desired region, then click on “Continue to Launch”. 4. Select Choose Action as “Launch CloudFormation” and Click on “Launch”. 5. On the CloudFormation screen, the default template will be selected in “Specify template”, to create a stack, click on “Next” 6. Specify stack details such as instance type, username, password, key name and CIDR block, etc. Click on “Next”. 7. Provide an appropriate option in the “Configure stack options” screen and click on “Next 8. Review details on the “Review” screen and click on “create stack” 9. The Marketplace “Stack Creation Progress” screen will appear. 10. Once stack creation is completed successfully, select the instance from AWS Instances Services and click on connect and download the RDP file to connect to the Virtual Machine. 11. Your Veritas Backup Exec server is now running and you are ready to use Veritas Backup Exec 60 days trial Version. About License: Contact Veritas Technologies LLC to get a license. Veritas Backup Exec support contact3.4KViews3likes0CommentsHow to deploy Backup Exec via the Azure Marketplace
How to deploy Veritas Backup Exec on Azure Marketplace. Veritas Backup Exec provides simple, rapid, and secure offsite backup to Azure for your on-premises environments and protects cloud-based workloads in Azure. Veritas Backup Exec helps customers recover quickly from critical data loss situations, and easily meet data regulatory requirements. By leveraging Veritas Backup Exec in the cloud as well as on-premises, you gain a unified and efficient data protection experience. Deploying Veritas Backup Exec via marketplace frees businesses from purchasing and managing IT infrastructure and enables them tomove to a more cost-efficient operational expense (OpEx) model. To learn “What’s New” with Backup Exec, visit the Veritas Backup Exec webpage. Steps to deploy the Veritas Backup Exec in Azure Marketplace: Through the Azure Marketplace, you can easily and quickly deploy the Veritas Backup Exec 1. Visit Azure Marketplace and click on “GET IT NOW” to use Veritas Backup Exec Note: This is the Veritas Backup Exec for Azure BYOL. 2. Click on “Continue” to take you to the Azure portal. Log in to the Azure portal and click on “continue”. 3. On the Azure Portal click on “Create” 4. Provide required details in “Basics”, “Network and Storage Settings”, “Backup Exec server IP address assignment” tabs and click on “Review + Create”. 5. The “Validation Passed” message will appear on the screen. Click on “Create.” 6. Once you click on create, it will show you “deployment is in progress” 7. Once deployment is completed, click on “Go to Resource Group”. 8. Select the BE server virtual machine. 9. Click on “Start” Virtual Machine, click on “Connect” and select “RDP”. 10. Click on “Download RDP file” and Connect to VM once the RDP file is downloaded. 11. Your Veritas Backup Exec server is now running and you are ready to use Veritas Backup Exec 60 days trial Version. About Licensing: Contact Veritas Technologies LLC to get a license. Veritas Backup Exec support contact3.7KViews3likes0CommentsBE 21.4 randomly hangs but then is ok during backup operations
Hello. We are running BE 21.4 on Windows Server 2022 and at random times during backup operations, the console just hangs and shows not responding but then after several minutes, is all good again. This isn't a huge issue as it doesn't seem to affect backup operations just more of an annoyance. Any suggestions are greatly appreciated.797Views1like3CommentsBackup-Recovery from Exchange 2013 into an *.PST File failed - Final error: 0xe000fe2d Solved
We had the problem, that Backup Exec 22 got us the followign error, every time we want to recover selected mailboxes from an Exchange 2013 Backup into an *.pst file. ******************* Auftrag beendet am Donnerstag, 25. August 2022 um 16:21:34 Abschlussstatus: Fehlgeschlagen Endgültiger Fehler: 0xe000fe2d - Während des Backups konnten ein oder mehrere Elemente nicht ordnungsgemäß gelesen werden. Das kann folgende Ursachen haben: Beschädigung des Dateisystems, Controllers, Laufwerks oder teilweise gesperrte Datei. Überprüfen Sie die Windows-Ereignisprotokolle, führen Sie das entsprechende Windows-Diagnoseprogramm und danach erneut das Backup durch. Endgültige Fehlerkategorie: Ressourcenfehler Zusätzliche Informationen zu diesem Fehler finden Sie unter der Verknüpfung V-79-57344-65069 or in english: Final error: 0xe000fe2d - During the backup, one or more items could not be read properly. This can be caused by: file system, controller, drive, or partially locked file corruption. Check the Windows event logs, run the appropriate Windows diagnostic program, and then run the backup again. Final Error Category: Resource Errors See link V-79-57344-65069 for additional information on this error ******************* So we thougt it was an file error, corrupted file or something else (that is what the message sounds like) But after we installed MS Office 2016 (MS Office 2010 was installed before) on the Backup Exec Server, without Office, you cant recover into an *.pst, the error was gone and all works fine. And, with Backup Exec 21, we had no problems to recover into an *.pst with MS Office 2010. This cost us many ours of troubleshooting, so maybe we can help you out...790Views1like1CommentBE system state backup stuck
Hello, we have a BE server which backups 4 MS Hyper-V servers and a lot of Windows and Linux VM's on these servers. Normally this works just fine, but every few weeks the backup of some of the Hyper-V hosts just get stuck at the backup system state. There is no longer any progress in the backed up files/sizes and the througput of the back just drop and drops. Attached an example of today, where the backup just stuck at 7GB in the system state, the job is already running for 9:33 hours and nothing happens any longer. And the same for the second Hyper-V server, already running for 9:03 hours, 2.75GB backed up and also stuck Also a stop of the backup does not work. We use BE 21.0 1200.2536 and the latest windows 2019 updates. We have seen this many times over the last 2-3 years.1.1KViews1like2CommentsExchange 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.8KViews1like5Comments