Backup Exec 20.2 Administrator's Guide
- Introducing Backup Exec
- 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)
- Backup Exec license contract information
- About upgrading to Backup Exec
- Getting Started
- Backing up data
- 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
- About the Backup Exec™ CloudConnect Optimizer
- Legacy backup-to-disk folders
- Legacy backup-to-disk folders
- Legacy backup-to-disk folders
- 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
- Using Backup Exec with firewalls
- Deleting DBA-initiated job templates
- Backup Exec logon accounts
- Creating a custom report
- List of Backup Exec standard reports
- Instant Cloud Recovery
- Preconfigurations to be completed in the Azure portal
- Troubleshooting Backup Exec
- Troubleshooting failed components in the SAN
- Generating a diagnostic file for troubleshooting Backup Exec
- Using Backup Exec in cluster environments
- Configurations for Backup Exec and Microsoft Cluster Servers
- Disaster recovery of a cluster
- 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
- Integration with Veritas™ Information Map
- 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
- 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
- Configuring Enterprise Vault collections
- Configuring the Backup Exec Migrator to communicate with Enterprise Vault
- About retrieving migrated Enterprise Vault data
- About the Partition Recovery Utility
- Appendix J. Backup Exec Agent for Microsoft Active Directory
- About backing up Active Directory and ADAM/AD LDS
- 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 Agent for Linux
- About installing the Agent for Linux
- About establishing trust for a remote Linux computer in the Backup Exec list of servers
- Editing configuration options for Linux computers
- About backing up a Linux computer by using the Agent for Linux
- About restoring data to Linux computers
- Editing the default backup job options for Linux computers
- Uninstalling the Agent for Linux
- Appendix O. Backup Exec Remote Media Agent for Linux
- About installing the Remote Media Agent for Linux
- About establishing trust for a Remote Media Agent for Linux computer in the Backup Exec list of servers
- About the Backup Exec operators (beoper) group for the Remote Media Agent for Linux
- About adding a Linux server as a Remote Media Agent for Linux
- Editing properties for the Remote Media Agent for Linux
- Creating a simulated tape library
- Viewing simulated tape libraries properties
- Appendix P. Accessibility and Backup Exec
- About keyboard shortcuts in Backup Exec
- Backup and Restore tab keyboard shortcuts
- Storage tab keyboard shortcuts
Configuring checkpoint restart
Checkpoint restart is a backup job setting that enables Backup Exec to automatically restart a job that is interrupted. The job restarts from the point where it was interrupted instead of starting over at the beginning. Backup Exec waits two minutes after the job stops and then attempts to restart the interrupted job. If the job cannot be restarted automatically or if checkpoint restart is disabled, you must restart it manually. A manual restart starts the job at the beginning instead of at the point where the job was interrupted.
Checkpoint restart cannot restart a backup job until it has backed up at least 32 MB of data. If a backup job fails before it has backed up at least that much data, you must run it again manually.
You can enable checkpoint restart for any jobs that are configured with the storage option Overwrite media. However, if there is no available media to overwrite and the job is interrupted, it may be placed on hold until overwritable media is available. When the media is available, the job restarts from where it was interrupted.
Backup Exec automatically cancels any jobs that run for too long according to the schedule settings that you selected when you created the job. If Backup Exec automatically cancels a job, it is not eligible to be restarted. If you manually cancel a job, Backup Exec does not automatically try to restart it.
If you use the Central Admin Server feature (CAS), any jobs that are restarted run on the same managed Backup Exec server on which the job failed. If the original Backup Exec server is not available, Backup Exec selects a different Backup Exec server on which to run the restarted job.
You can enable or disable checkpoint restart in the Advanced Open File options when you create backup jobs or in the backup job defaults.
This topic includes the following information:
Checkpoint restart is only supported for NTFS volumes. The only type of snapshot technology that is supported for checkpoint restart is VSS.
Checkpoint restart is not supported for the following:
Cluster Shared Volumes (CSV)
Incremental or differential backups
Jobs that use catalogs to determine if a file has been backed up
You should consider the following things before you use checkpoint restart:
If the failure occurs in the middle of an append job, the media is no longer appendable. The media is not appendable until it is erased or overwritten, or the retention period expires. When the restart occurs, Backup Exec uses new media. You should select an appropriate media overwrite protection level to ensure that the restart does not overwrite the media that was used before the job failure.
If the failure occurs during a verify job or a database consistency check job, the job restarts at the beginning.
Full backups that were interrupted and resumed from the point of failure do not display in the Simplified Disaster Recovery Recover This Computer Wizard. However, you can restore these backup sets manually after you make the initial recovery by using the Recover This Computer Wizard.
You can enable the checkpoint restart option for a full backup job that uses theoption. If the job fails and is resumed, the files are not deleted from the source volume after the backup completes.
You can change the default checkpoint restart settings in the error-handling rules settings. You can specify the number of times that you want checkpoint restart to retry a failed job, the interval between restart attempts, and the final job disposition for any jobs that cannot be successfully restarted.
To change default checkpoint restart settings
- Click the Backup Exec button, select Configuration and Settings, and then select Error-Handling Rules.
- Select Checkpoint Restart, and then click Edit.
- Select Enable error-handling rule.
- Select Retry job.
- Complete the following fields:
Enter the maximum number of times that you want Backup Exec to retry a job that fails.
Enter the interval of time in minutes that you want Backup Exec to wait before it attempts to restart a job.
- In the Final job disposition group box, select one of the following options:
Place job on hold until error condition has been manually cleared
Select this option to have Backup Exec place the job on hold if the job cannot be completed successfully after the maximum number of retries. The job remains on hold until the error condition has been manually cleared.
Reschedule job for its next scheduled service
Select this option to have Backup Exec reschedule the job for its next scheduled occurrence if the job cannot be completed successfully after the maximum number of retries.
- (Optional) In the Notes field, type any additional notes about the error-handling rule.
- Click OK.