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 12virtual 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
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.Protect Windows Server 2016 with Veritas Backup Exec 16!
So what does that really mean? If I install the released bits of Windows 2016 server, could I then install Veritas Backup Exec 16 on it and start using it immediately? Well, the answer is “Yes” ! Additionally, you can use Windows 2016 server to install Backup Exec Server and Agent, as well as options and components such as: Protection for remote Windows 2016 Server computers. Simplified Disaster Recovery (SDR), which recovers the entire windows 2016 server from a bare metal state. Backup and recovery of the latest Microsoft Hyper-V 2016 platform. Protection for resilient file system (ReFS) & Dedupe Volumes. Support for the current versions of Microsoft applications like SQL Server, Microsoft Exchange, and SharePoint Active directory for application item level GRT on Windows 2016. How did we go about supporting Windows 2016? Deploy Windows 2016 today, without waiting for backup to catch up! There is no need to take the old approach of waiting until late in the game to start implementing a new server OS. You can immediately start protecting Windows Server 2016 with Veritas Backup Exec 16. We have been actively working with Windows 2016 builds for quite some time now. We tested technical preview releases and prepared ourselves to support the final release. Testing on Windows 2016 Server began almost 10 months ago with validation of pre-release builds. We executed manual as well as automation test suites on each pre-release build. We executed over 1000 test cases (500 automated and over 500 manual) spread across features such as core Backup and Restore, Simplified Disaster Recovery, Hyper-V, and Microsoft applications such as Exchange, SharePoint, Active directory, and SQL server. We have qualified over 20 Windows 2016 Server pre-release builds with different configurations, such as Windows 2016 failover cluster, storage pools, and ReFS. Backup Exec 16 has been tested with all versions of Windows 2016 Server, such as Datacenter, Essentials, Standard, Storage Server and Hyper-V Edition. Automation helped us in a big way to qualify the pre-release builds. In addition, our manual test lab consists of over 30 test servers, on which every new build of Windows Server was installed and manual test cases were executed. How did automation help testing Backup Exec 16 on Window 2016? Providing support to new offering coming in market in a short time span is a challenging job. Without automation, repeating the test cycles on frequent early-access builds of an upcoming OS or application, is very difficult. To address this problem and provide maximum coverage, we utilize the automation labs of Backup Exec. We deployed Windows 2016 drops on an automation environment consisting of more than 100 virtual machines. We refreshed of the Windows 2016 build on at a one-week cadence on our setups, with a two-week cadence on the more complex setups Over 500 test cases have been running daily on Windows 2016 builds right since April 2016 till Windows RTM. We were not only able to catch potential issues in our product but also were able to identify and worked with Microsoft to resolve Windows issues. All builds with fixes were re-tested again by automation. We were successfully able to provide automation for various features of Backup Exec 16 mentioned below: Feature Names: Install, Migration ,Licensing and Upgrade Base functionality of Backup and Restore and BEMCLI support Disaster Recovery Hyper-V Exchange SQL MSFT-Active Directory Various supported Storage types AVVI CAS General UI
Forecast: Backup Exec with Increasing Cloudiness
A weather report that includes "cloudy" can bum you out, and IT designers may feel the same way when the term is applied to evolving infrastructure. Let’s lift the fog around Cloud and highlight how Backup Exec can help you today and in the near future.
