Discrepancy in Charged TB in NetBackup Deployment Utility
Hi Veritas Support, I am encountering a discrepancy in the charged TB for my 7-day Capacity Licensing Report (22nd May,2024 - 29th May,2024) generated by the NetBackup Deployment Utility. The 7-day report shows a significantly higher TB charged compared to the 35-day report(24th April, 2024 - 29th May, 2024). We perform one full backup per week and six incremental backups per week. After investigating, I found the following: 1. I checked the itemization tab and compared columns - Client Name, Policy Name, Policy Type, and Backup Image - to identify any duplicate rows with the same values across these columns, which could lead to overlapping and increased TB size. No exact duplicates were found. 2. Despite this, the discrepancy still persists, and I need assistance in understanding why the 7-day report shows such a high TB charged and how to accurately adjust for potential overlaps or other issues. Thank you for your support. Best regards, Pruthvi Patel(CEP-17234) Support Experience User Research
Interaction Date: June 28 – July 2, 2021 Interaction Type: Support Experience User Research Our Customer Support Technology Solution team is looking at enhancing the customer support portal and accompanying documentation to help enhance and simplify your experience on the support portal. If you are interested in participating in this or other exciting interactions, and are not currently a member of our CPEP program, you can register here: https://cpep.veritas.com then contact us at customer.engagement@veritas.com.
Veritas Backup 16 - Service Crashing
I have a critical issue with BE. The service beserver.exe is crashing randomly. We tried with the BE support without success. This server crash at the Windows 2016 server, so we reinstall the BE at a Win 2012 R2, but the service crashes too. If you leave the server without any job running, the services crashes too. We tried to repair, remove the .Net framework, but without success. Its the log: A process crash has been detected. Faulting application: BackupExec.exe 16.0.1142.0 Faulting module: KERNELBASE.dll 6.3.9600.18666 Fault offset 0x95fc Exception code 0xe0434352. Any suggestions ?
Backup Exec Technical Support - Partner Newsletter - 1st Edition - Nov 2016
Hi Partners, Welcome to the first newsletter from the Backup Exec Support Team. With your feedback we hope to make this a regular update that provides you with everything you need to know about all things Technical Support and show you how your feedback is helping to drive service and product improvements.
Backup Exec 16 - Temporary VMware folders are not cleaned from the Backup Exec data directory
HI All, So we started with Backup Exec 14 few years back and I've updated to BE 16 last week with latest patch due to following issue when Symantec could not resolve it. Issue: When backup up VM's, there are lot of Temporary folders been created in folder C:\Program Files\Symantec\Backup Exec\Data. (Folders name include VM's name and date ), and number of folders been created keep growing everyday. Troubleshoot done: I've logged a call with Symantec and for a week they did troubleshooting and today an Advanced tech called me and advised that this is a known issue and only work-around is to delete these folders manually ? Now I have had the same above issue while we were on BE 15, with all the patches installed, hence why I quickly upgraded to BE 16 to see if that resolve the issue. Symantec advance support tech directed me to this article ( https://www.veritas.com/support/en_US/article.000023219 ) which is according to the article was an issue on BE 2014. So I don't believe that Backup Exec 16 will have this now, will it ? And I can't accept an answer been deleting these folder manually every day as a solution. Does anyone experienced this kind of issue ? Cheers
