Backup Exec 25 Administrator's Guide
- Introducing Backup Exec
- Installation
- Methods for installing the Agent for Windows
- Using a command prompt to install the Agent for Windows on a remote computer
- Using a command script to install the Agent for Windows
- Installing the Remote Administrator
- Installing Backup Exec using the command line (silent mode)
- About updates to Backup Exec using Arctera Update
- Backup Exec license contract information
- About upgrading to Backup Exec
- Getting Started
- Configuring the Home tab
- Backups
- Recommendations for when to use virtual-based backup and agent-based backup
- Backing up data
- Restores
- How Backup Exec catalogs work
- Job management and monitoring
- About the Job Monitor
- About the Job History
- Viewing the job log
- Error-handling rules for failed or canceled jobs
- Alerts and notifications
- Enabling active alerts and alert history to display on the Home tab
- Adding a recipient group for alert notifications
- Sending a notification when a job completes
- SNMP traps for Backup Exec alerts
- Disk-based and network-based storage
- Configuring disk storage
- Configuring disk cartridge storage
- Backup sets
- Cloud-based storage devices
- Amazon S3 cloud-based storage
- Google cloud-based storage
- Microsoft Azure cloud-based storage
- Private cloud-based storage
- About S3-Compatible Cloud Storage
- Cloud deduplication storage device
- Requirements for configuring a cloud deduplication storage device
- About the Backup Exec™ CloudConnect Optimizer
- Generic S3 Configurator
- OpenStorage devices
- Microsoft 365
- OneDrive plugin: Performance and throttling configuration
- Exchange plugin: Performance and throttling configuration
- SharePoint plugin: Performance and throttling configuration
- Teams plugin: Performance and throttling configuration
- Tape storage
- Robotic libraries in Backup Exec
- Creating robotic library partitions
- Managing tapes
- Creating media sets for tapes
- Labeling tape media
- Default media vaults
- Storage device pools
- Storage operations
- Conversion to virtual machines
- Configuration and settings
- Configuring role-based access settings
- Configuring parallel streams and job settings for Microsoft 365
- Changing network and security options for Backup Exec
- Using Backup Exec with firewalls
- Deleting DBA-initiated job templates
- Backup Exec logon accounts
- Reports
- Creating a custom report
- List of Backup Exec standard reports
- Instant Cloud Recovery
- Preconfigurations to be completed in the Azure portal
- GDPR Guard
- Troubleshooting Backup Exec
- Troubleshooting failed components in the SAN
- Generating a diagnostic file for troubleshooting Backup Exec
- Simplified Disaster Recovery
- Setting or changing the alternate location for the disaster recovery information file
- Creating a Simplified Disaster Recovery disk image
- Preparing to recover from a disaster by using Simplified Disaster Recovery
- Recovering a computer with Simplified Disaster Recovery
- Performing manual disaster recovery
- Forever Incremental Backup
- Appendix A. Backup Exec Agent for Windows
- About the Backup Exec Agent Utility for Windows
- Appendix B. Backup Exec Deduplication Feature
- Creating or importing deduplication disk storage
- Selecting storage devices for direct access sharing
- Appendix C. Backup Exec Agent for VMware
- About establishing trust for a vCenter/ESX(i) server
- Backing up VMware virtual machines
- About instant recovery of a VMware virtual machine
- About Recovery Ready for VMware virtual machines
- Appendix D. Backup Exec Agent for Microsoft Hyper-V
- Backing up Microsoft Hyper-V virtual machines
- About instant recovery of a Hyper-V virtual machine
- About Recovery Ready for Hyper-V virtual machines
- Appendix E. Backup Exec Agent for Microsoft SQL Server
- Backing up SQL databases and transaction logs
- Restoring SQL databases and transaction logs
- Disaster recovery of a SQL Server
- About SQL Server Always On availability groups
- Appendix F. Backup Exec Agent for Microsoft Exchange Server
- Backing up Exchange data
- Appendix G. Backup Exec Agent for Microsoft SharePoint
- Backing up Microsoft SharePoint data
- Appendix H. Backup Exec Agent for Oracle on Windows or Linux Servers
- Configuring the Oracle Agent on Windows computers and Linux servers
- Configuring an Oracle instance on Windows computers
- Viewing an Oracle instance on Windows computers
- About authentication credentials on the Backup Exec server
- About backing up Oracle databases
- About restoring Oracle resources
- Appendix I. Backup Exec Agent for Enterprise Vault
- About backup methods for Enterprise Vault backup jobs
- Restoring Enterprise Vault
- About the Backup Exec Migrator for Enterprise Vault
- Configuring the Backup Exec Migrator
- About retrieving migrated Enterprise Vault data
- About the Partition Recovery Utility
- Appendix J. Backup Exec Agent for Microsoft Active Directory
- Appendix K. Backup Exec Central Admin Server Feature
- About installing the Central Admin Server feature
- What happens when CAS communication thresholds are reached
- About job delegation in CAS
- How to use Backup Exec server pools in CAS
- How centralized restore works in CAS
- Appendix L. Backup Exec Advanced Disk-based Backup Feature
- Appendix M. Backup Exec NDMP Feature
- About restoring and redirecting restore data for NDMP servers
- Viewing the properties of an NDMP server
- Viewing storage properties for an NDMP server
- Appendix N. Backup Exec File Servers
- Appendix O. Backup Exec Agent for Linux and Unix
- About installing the Agent for Linux and Unix
- About establishing trust for a remote Linux and Unix computer in the Backup Exec list of servers
- Editing configuration options for Linux and Unix computers
- About backing up a Linux and Unix computer by using the Agent for Linux and Unix
- About restoring data to Linux and Unix computers
- Editing the default backup job options for Linux and Unix computers
- Uninstalling the Agent for Linux and Unix
Retrying only failed resources from the Job History
You can retry a job that failed from the job history for only the resources that failed during the immediate previous run of that backup job. This option is available only for a failed or cancelled backup job. If a backup job is successful, this option is grayed-out.
For example, if you have a VMware backup job that is backing up 5 virtual machines. During backup, only 3 virtual machines are successfully backed up and for 2 virtual machines the backup failed. You can refer to the job log to know the reason for the failure, correct the issue, and then use the
option to run the job again. This time only the 2 virtual machines that failed during the immediate previous run of that backup job are backed up.. The 3 virtual machines that were backed up successfully are not backed up again.If a backup job is enabled for Simplified Disaster Recovery and failure occurs in one or more of the critical resources, then when you retry the failed backup job, all the critical resources are backed up again. Even the critical resources that may have backed up successfully in the immediate previous run of that backup job.
In a CAS-MMS environment, for jobs delegated from the CAS server, the option to run retry failed backup is only available from the CAS user interface. The option is disabled for the delegated jobs on the MMS user interface.
To retry only failed resources from the Job History
- Do one of the following:
To retry the failed resource from the Job Monitor tab
On the Job Monitor tab, locate the job in the Job Histories pane.
To retry the failed resource from the Backup and Restore tab or the Storage tab
Do the following:
On the Backup and Restore tab or the Storage tab, double-click the server or the storage device where the job ran.
In the left pane, click Job History.
- Do one of the following:
Right-click the failed job that you want to retry, and then click Retry Only Failed Resources.
On the Job Monitor tab, select the failed job that you want to retry, and then click Retry Only Failed Resources.
A dialog box is displayed stating that the job will run immediately and also run as per the defined schedule.
- Click Yes.
The job starts and only the resource that failed during the immediate previous run of the job is backed up.