Retry Only Failed Resources in Backup Job with Backup Exec™ 20.3
Administrators usually have SLAs to protect all the important resources and have a restore point in time ready. Backup job can be configured to backup several resources in the same job. When such job is successful for some of the resources and fails for some, the latest recovery point is available only for the resources for which job succeeded. For example, a job backed up 10 out of 12 virtual machines and failed for 2 virtual machines. In such scenario, the administrator has the following options: Rerun the entire failed job: This takes a lot of unnecessary time and space since resources already backed up are backed up again. Create a new job only for failed resources Job creation, configuration takes a lot of time. Introducing 'Retry Only Failed Resources' option Backup Exec™ 20.3 introduces a new option to ‘Retry Only Failed Resources’, which addresses this problem by giving you an option to run a failed job for only the failed resources. When this option is selected, the job will run for only the resources which failed in the previous run of the job. This option can be selected by doing right-click and select ‘Retry only failed resources’ in the Backup Exec console. The option is available in all places where ‘Run now’ option is present. This option is available for backup jobs. This option is enabled only when the most recent run of the job has failed. Backup Exec checks the latest run of the job, whether full backup or incremental / differential backup for failure and the option is enabled. Job logs provides information about the resources which are skipped in the job. These resources were successful in the previous run of the job. Simplified Disaster Recovery’ / ‘System State Protection’ Enabled Jobs If System State Protection is enabled for a backup job, the ‘Retry Only Failed Resources’ option considers all the critical resources. It does not skip the critical resources even if they were successfully backed up in the job which failed for some other resources. This allows Simplified Disaster Recovery at the point in time for the retried job. This option is not designed to work as a replacement for the ‘Check Point Restart’ feature. Check Point Restart allows to restart from the point of the failure, at a file level granularity. For example, if NTFS volume E: had 100 files, and backup failed after backing up 50 files, Check Point Restart allows the next run of the job to start backing up from the failed file, that is the 50th file. If a job had D: and E:, and the backup failed for E: but was successful for D:, then ‘Retry only failed resources’ would backup E: entirely (depending on the backup method of the job) but skip D:. Inside the failed resource, ‘Retry only failed resources’ job does not start from the failed file. ‘Retry Only Failed Resources’ is a perfect example of our customer focus and commitment, because this option was requested by customers. If you are not a current Backup Exec customer, we invite you to learn more about the solution at the following link: www.backupexec.com
Exchange 2016: The Database Recovery failed with Error '*Null*'
We're trying to backing up our new exchange envirement with BE 20.3. We often get the error message: Backup V-79-57344-759 - The backup selection '<Database>' 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 ended: <date> 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 This happens during full backup and incremental backup. The next backup, full or inc, runs (often) fine. I don't know why the next backup runs successfully, I didn't change anything. The backup selection '<Database>' has been successfully processed for Granular Recovery Technology (GRT) I have already tried the following Reading the administration guide twice (appendix F: Backup Exec Agent for Microsoft Exchange Server) Reinstall the "BE-Agent" Restart servers (BE and Exchange) https://www.veritas.com/support/en_US/article.100043312 Recreate the backup job Any help is appreciated! BE-Server: Backup Exec 20.3 Rev 1188 Windows Server 2016 Exchange Server: Windows Server 2016 Exchange Server 2016 CU12 Version 15.1 (Build 1713.5) Edition: Standard
Backup 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.
