Backup 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 20.3 Beta registrations are now open!
We are pleased to inform you that registrations for Backup Exec 20.3 Beta program are now open. This NEW Beta program for upcoming release of Backup Exec contain some new features such as support for Windows Server 2019 and Exchange Server 2019, Retry backup for only failed resources, Backup virtual machine disks selectively - VMware, Support for new cloud storage and overall improvements in meeting your recovery time objectives. Please visit the below link and register in this program. Join this BetaProgram Please click on above “Join this BetaProgram" link to successfully register for this program. You will receive an email notification from us upon successful registration. We are opening up registration early to allow enough time to process applications before the Beta 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 Beta program start date which is currently expected to be sometime in second-half of August2018. If you have any queries, please contact us at bnrbeta@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.2KViews2likes3CommentsBackup 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. Thanks410Views1like0CommentsBackup 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.3KViews1like3CommentsBackup Exec Support KB Articles are in desperate need of improvement...
Hi Guys, Your KB articles are getting more and more out of control and need to have some work done on them, desperately, to improve things. Here is a case in point: KB Article: How to troubleshoot Backup Exec Deduplication Storage Folder Location: https://www.veritas.com/support/en_US/article.100038756.html Issue: (and this is the problem across a significant number of your KB documents): The way in which your articles identify the products the article refer to is woefully inadequate. In this example this is what you say: "Product(s): Backup Exec, Appliances". The article then goes on to state "Note:Backup Exec version 2014, 15, 16 utilize PostgreSQL as the backend database in deduplication storage folder. Backup Exec 20 does not use PostgreSQL, so some commands that are suited for Backup Exec version 2014, 15, 16 may not apply to Backup Exec version 20 deduplication storage." Now, this is really not much help to people who are troubleshooting their deduplication store. How are we supposed to know which commands are or aren't "suited" to the multiple versions you have given. I know, for a fact that post 2012 and pre v20, some fairly big changes were made to the deduplication subsystem and then with v20 probably some of the biggest changes you have ever made (in fact arguably the biggest changes Veritas, specifically, have ever made to the product, since the spin-off from Symantec) were made to the deduplication systems. However, you are inadequately updating your KB articles to cater for these changes. This article has been changed very little since, pre 2012 versions and you have simply inserted the lines of vague exemptions, as identified above, rather than properly seperating out this article to cover the three most recent major evolutionary changes of the dedupliaction subsystem. We are talking about changes made over the last 10 years, so we're not talking about an awful lot of work for you guys to get this right. Generally, your KB articles should clearly indentify the specific product major versions the article is relevant to, in tabular format, somewhere standard, in the document. Normally the top for other vendors whose documentation is on top of this kind of thing. Not managing this better exposes your customers to unnecessary risk. If someone who is not particularly familiar with the deduplicaion subsystem reads this current article, how are they to know whether the commands they are using are "suited" to the version they are using or not? Regards, David988Views1like1CommentBackup Exec not delete old jobs expired from NAS
Hi, I used Backup Exec 20.4 for backup my server (Hypervisor + 2 VMs to Windows 2016 Server). My storage location is a NAS Synology. I had 2 tasks for my job : 1 complete job first sunday of the month with 5 days storage 1 incremential daily backup with 3 days storage My NAS system had 4 To HDD, and the gross size of my system is 1,25 To. But despite the expiry of my old jobs, files are not deleted from the nas! Unfortunately my new backups are crashing. What is going on? Regards, Luc1KViews1like1Comment0xe000fed1 - A failure occurred querying the Writer status
We are facing VSS issues in multiple servers, while taking backup of windows 2016 remote server (Virtual Machine in VMWare \Hyper-V environment) through Veritas Backup Exec 20.3. Need to find out the root cause of this issue. Details are provided below: Media server Dc-001 OS: Microsoft windows server 2012 R2 standard Veritas Backup Exec Version: 20.3 Rev. 1188 (64 bit) *** Remote server DC-008 OS: Microsoft windows server 2016 *** Remote server DC-006 OS: Microsoft windows server 2016 Observation: In both the server “Microsoft visual C++ 2010 x64 redistributable 10.0.40219” patch\hotfix is updated (KB2565063). Final error: 0xe000fed1 - A failure occurred querying the Writer status. See the job log for details about the error. Job Log of DC-008 (OS: Server 2016) -------------------------- V-79-57344-65233 - Snapshot Technology: Initialization failure on: "\\DC-008.XYZ.ABC\System?State". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS). Snapshot technology error (0xE000FED1): A failure occurred querying the Writer status. See the job log for details about the error. Check the Windows Event Viewer for details. Writer Name: Automated System Recovery, Writer ID: {BE000CBE-11FE-4426-9C58-531AA6355FC4}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during freeze operation (9). Writer Name: COM+ Class Registration Database, Writer ID: {542DA46900-D3E1-473C-9F4F-7847F01FC64F}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during freeze operation (9). Writer Name: Internet Information Services, Writer ID: {059B1F000CF-90EF-465F-9609-6CA8B2938366}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during freeze operation (9). Writer Name: Internet Information Services, Writer ID: {0FCA-4AA8-A654-1F8C654603F6}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during freeze operation (9). Writer Name: Network Policy Server, Writer ID: {01-13E1-48DB-97FC-D5BC721BB18A}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during freeze operation (9). Writer Name: Registry, Writer ID: {00000B4A2-367D-4D15-A586-71DBB18F8485}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during thaw operation (10). Writer Name: System Files, Writer ID: {E0008132975-6F93-4464-A53E-1050253AE220}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during freeze operation (9). Writer Name: Terminal Server Licensing, Writer ID: {00009}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during freeze operation (9). Writer Name: Terminal Services Gateway, Writer ID: {00009XXXX}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during freeze operation (9). Writer Name: Windows Management Instrumentation, Writer ID: {XXXXxF0}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during freeze operation (9).1.3KViews1like1Comment