Windows Server service not started
Initial Backup Exec installation When running the "Backup Exec Environment Check 2.0" from the install media, one of the results include a section called Windows Server Service Check - FAILED. "The Windows Server service was not started. Sart this service before continuing with the installation of Backup Exec." What Windows Server service is this referring to? The host is a clean Server 2016 installation in a domain, with alldefault services started.Solved20KViews0likes3CommentsBackup Exec 20.3 now available to modernize your Data Protection
Backup Exec 20.3 is now available with Day 1 support for Microsoft Windows Server 2019 and Microsoft Exchange Server 2019, new GDPR Guard capability for compliance enforcement, support for Alibaba Cloud, support for VMware vSphere 6.7 Update 1, Granular VMware VM-disk backups, enhanced job logic persistence and more.17KViews3likes4CommentsBackup Exec console crashes after installing .NET Framework 4.8
Backup Exec 20.x and 16 are affected by the following issue: "Backup Exec console crashes after installing .NET Framework 4.8"https://www.veritas.com/support/en_US/article.100045500.html. UPDATE: Backup Exec 20.x : This issue has been addressed in Backup Exec20.5, which is now available in the Download Center, please go tosupport.veritas.comto obtain this update. Backup Exec 16 FP2:This issue has been addressed inBackup Exec 16 FP2 Hotfix 506023 which is now available in the Download Center, please go tosupport.veritas.comto obtain this update. Veritas recommends, where possible, to upgrade to the latest available version of Backup Exec. To aid customers with upgrading, the following resources can be used: Software Compatibility List: https://www.veritas.com/content/support/en_US/doc/BE_20_SCL Licensing Guide: https://www.veritas.com/content/support/en_US/doc/BE204_Licensing_Guide Admin Guide: https://www.veritas.com/content/support/en_US/doc/59226269-135381838-0/index Upgrades – Best Practices and available support: https://www.veritas.com/support/en_US/article.100044375.html Trialware: https://www.veritas.com/form/trialware/backup-exec Please use this thread for any questions on this issue with .NET 4.8.13KViews2likes6CommentsBackup Exec cannot create a recovery checkpoint for the virtual machine
I ask for help from the community. run into a problem when backing up a virtual machine, a search (on vox/ google) did not yield results. Backup Exec Server: BE version=20.0.1188, OS Windows 2016 ver 1607 (14393.3204) Hyper-V host: OS Windows 2016 ver 1607 (14393.3204)with roleHyper-V, Agent VBE 20.0.11.2496 VM: OSWindows 2008R2 + MSQL 2012 SP2 GRT - OFF/ Instant Recovery - OFF I get the following error: V-79-40960-38691 - Backup Exec cannot create a recovery checkpoint for the 'SQL' virtual machine. Refer to the Windows Event Log on the Hyper-V host for more details or retry the backup job. Job Completion Status Job ended: 17/11/2019 . at 13:01:30 Completed status: Failed Final error: 0xa0009723 - Backup Exec cannot create a recovery checkpoint for the virtual machine. Refer to the Windows Event Log on the Hyper-V host for more details or retry the backup job. Final error category: Resource Errors For additional information regarding this error refer to link V-79-40960-38691 Errors Click an error below to locate it in the job log Backup- hvc-cluster V-79-40960-38691 - Backup Exec cannot create a recovery checkpoint for the 'SQL' virtual machine. Refer to the Windows Event Log on the Hyper-V host for more details or retry the backup job.Solved9.4KViews0likes9CommentsBackup Exec 20.5 Technical Preview program registrations are now open
We are currently recruiting customers who are interested in participating in upcoming Backup Exec 20.5 Technical Preview program. The Technical Preview Program for the upcoming release of Backup Exec contains some new features which continue to position our product as the leader in Backup and Recovery solutions for mid-market organizations. These include: Unified reports with SaaS Backup (Backup Exec and Veritas SaaS Backup integration) AWS Glacier and Deep Archive support Please visit the below link and register in this program. Join this Technical Preview Program We are opening registration early to allow enough time to process applications before the Technical Preview build is available for download. So, if you are Veritas partner/reseller, please have your clients sign up early. All applications will be screened for US legal compliance a week or two prior to Technical Preview program start date, which is currently expected to be sometime in first half of June 2019. If you have any queries, please contact us at bnrbeta@veritas.com. To joinVeritas Customer and Partner Engagement Program, please visithttp://cpep.veritas.com/. We look forward to your interest and participation. Best regards, Backup Exec Team Forward-looking Statements Any information regarding pre-release Veritas offerings, future updates or other planned modifications is subject to ongoing evaluation by Veritas and therefore subject to change. This information is provided without warranty of any kind, express or implied. Customers who purchase Veritas offerings should make their purchase decision based upon features that are currently available.Solved8.4KViews0likes16CommentsThe path appears to be an invalid path. Please ensure the server name and share name are correct.
I have downloaded a trial version of Backup Exec version 20.2 rev 1188, but I can't add my storage. The error I get is "The path appears to be an invalid path. Please ensure the server name and share name are correct." I've found this document: https://www.veritas.com/support/en_US/article.100028740, but it still doesn't work. The storage device is in DNS, and it's pingable from the BE server. The user also has full read/write to it. I'm trying to add it as disk storage. Also, I can map the drive through Windows, but I can't see it as a local disk from the drop down.Solved8.4KViews0likes6CommentsUnable to connect to AWS S3 Storage BEMSDK Failure code E0009B3F
so trying to connect to S3 using the "aws_access_key_id" for the username and "aws_secret_access_key" and the password i am recieving the following error. It cant seem to be able to find the buckets to select from which should be the next step. this is what i could get from the debug monitorSolved7.5KViews0likes19CommentsBackup Exec 20.2 Error Code=4
Hello All, We recently installedBackup Exec 20 (updatingto 20.2). Ever since the installation we have received a daily active alert with a category of "Veritas Update Error" and a message stating "The query for available updates failed, error code=4". The installation of Backup Exec 20.2 does not have any outstanding updates. I cannot find any reference to the text "The query for available updates failed, error code=4". Has anyone seen a similar error code, if so, how did you clear the error? Thank you AG_16.4KViews0likes9CommentsSQL Server Express upgrade instance BKUPEXEC - what version is supported?
Hi I've recently finally finished upgrading from BE 16 to 20.3, so far so good, SQL Server 2014 remains the default version that BE 20 relies on for the BKUPEXEC instance. I'm doing overall upgrade planning on our infrastructure and saw SQL Server 2014 SP3 will get out of mainstream support in july 2019 identified which systems still run this version, Backup Exec server being one of them. Even if the extended maintenance support continues, MS will definitely limit their efforts for 2014 in favour of 2016 and newer. Thus I'd like to get all our DB instances upgraded in time - where possible to the same versions on the whole infastructure so that we have to keep an eye on less software version to keep patched and maintained. The BE 20.3 admin guide mentions SQL Server 2014 Express SP2 as minmum requirement, however I haven't found an indication what newer versions of SQL Server (Express) are supported for the BKUPEXEC instance. Ideally I'd like to upgrade to SQL Server 2017, then again if Veritas doesn't support new SQL Server for the BKUPEXEC instance it wouldn't be worth the effort. Hence my question about what versions are actually supported by Veritas in this case - and where I can find about.Solved6.1KViews0likes6CommentsBEDATA Folder Files Unable to Delete Manually
BE 20.5 Unable to manually delete any files or folders from the B2D Disk BEDATA folder I have full privileges (administrator) to the system and drive I created a new B2D and have the same problem The prompt I get is :"You need permission to perform this action" "You require permission from Administators to make changes to this folder" I have no problems accessing / deleting files in the BEControl folder or any other folders I create on the B2D drive - Just cannot do anything in the BEDATA folder5.8KViews0likes1Comment