Expired Backup Sets unable to delete on Backup Exec 16
Hi, I need some helps how to delete expired Backup Sets on Backup Exec 16. [Done] - "Allow Backup Exec to delete all expired backup sets" is ticked. - Backup Sets I want to delete is "Expired". - "DeleteLastRecoverySetsOnceExpired" registry value is 1. - Backup Exex 16 is the latest as of Jan 2018. However it is not deleting after hours unfortunately. I went through topics here in the past, but nothing worked so far. If you have any tips I can try next, please let me know. Thank you!
VSR 16: Service Pack 1 - available now!
Service Pack 1 for Veritas System Recovery (VSR) 16 is now available. What's new? 32TB volume support Microsoft Surface Pro 4 support Support for the following Linux versions: Red Hat 6.6, 6.7 & 6.8 SLES 11.4 CentOS 6.6, 6.7 & 6.8 Windows 2016 Server support (as a managed client with the Veritas System Recovery Management Solution) Release notes: http://www.veritas.com/docs/000125903 Patch download: http://www.veritas.com/docs/000125892 (NOTE: SP1 is also available via LiveUpdate) Updated compatibility list: http://www.veritas.com/docs/000114479 For more details about VSR, please visit https://www.veritas.com/product/backup-and-recovery/system-recovery To download a trialware copy of VSR, please visit https://www.veritas.com/trial/en/us/system-recovery-16.html Please use this thread for any questions that are specific to SP1.
V-79-57344-38264 - Unable to copy the virtual machine disk using the VMware VixDiskLib
Hi, we've been having issues with failing Backups of VMs in our VMware infrastructure lately. The error get is this: V-79-57344-38264 - Unable to copy the virtual machine disk using the VMware VixDiskLib VixDiskLib_Read() reported the error: Memory allocation failed. Out of memory. We run Backup Exec 16. I recently installed FP2. We had the issue before FP2, but only maybe 1 Backup per day, that failed. Now its rather 3-4 per day. Both incremental and Full Backups. The "out of memory" Error doesn't make much sense to me. The Media Server runs Windows Server 2012R2 with 32GB of RAM. According to monitoring it never dips below 70% free RAM. Our ESX Hosts also have multiple hundred GB RAM free at any time. The VMs themselves also don't show any RAM usage issues. The vSphere Appliance has 16GB RAM, usually at less than 2GB used. VMware vSphere & ESX Version: 6.5 with latest updates Backed-Up VMs run Windows Server 2012R2 / 2016, some LinuxBe2016 fails on Ex2016 - error V-79-57344-759
Hi Folks, I had seen reference to this error in earlier posts, but as you see below, I tried and it didn't help. Hoping a new posting might gather some new insight? :-) I am on BE2016, now with Exchange 2016... I was getting 100% success rates with Exhange 2010, but now that we have migrated to Ex2016, I am also getting this old error. I have tried the DWORD mentioned in the other article (which I assume is NOT a typo in that there is a space in the DWORD name)... rebooted, ran another incremental, and the same error popped up. (please advise if I should now remove the DWORD, or if it's safe to leave with BE2016/Ex2016) Any thoughts? Or something I am missing? Here is the exact text of the error: October 25, 2017 12:23:48 AM - V-79-57344-759 - The backup selection '\\Crom.aquilonia.orb\Microsoft Information Store\Mailbox Database xxxx2' was not successfully processed for Granular Recovery Technology (GRT). The Database Recovery failed with Error '*Null*'. You will not be able to restore individual items for this backup selection Job Completion Status Job ended: October 25, 2017 at 12:23:49 AM Completed status: Failed Final error: 0xe00002f7 - Cannot extract mailbox messages from the Exchange backup. Review the job log for more information. Final error category: Resource Errors For additional information regarding this error refer to link V-79-57344-759 Thanks!
Can't install Agent on Windows server 2003R2
When mounting the agents from the server console the process does it correctly but then on the machine with windows 2003, the service is not started and therefore does not contact the console properly. The same happens to the three servers with w2003. Thank you