Backup Exec 20.1 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
- 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
- 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
List of job statuses in Backup Exec
Backup Exec displays various job statuses for active, completed, and scheduled jobs.
See Active job statuses.
The following statuses may appear for the jobs that are active:
Table: Active job statuses
The operation is underway.
The job has been initiated, but Backup Exec is actively looking for a suitable drive or media.
Backup Exec cannot process the Cancel request immediately. This status is displayed until the job is actually canceled. The job is then displayed in the job history with a status of Canceled.
The media is being loaded and positioned on the target device.
This status can indicate any or all of the following:
Backup Exec is processing a snapshot operation.
The device that the job was sent to is paused.
The Backup Exec server is paused.
The Backup Exec services have become unresponsive.
You must insert media for the job to continue.
Communications between the managed Backup Exec server and the central administration server have not occurred within the configured time threshold.
No communication about jobs is being received at the central administration server from the managed Backup Exec server. The configured time threshold has been reached.
Backup Exec is running a consistency check of the databases before backup.
Backup Exec is updating the catalog information.
The following statuses may appear for the jobs that were completed:
Table: Job completion status
The job completed without errors.
Completed with exceptions
The job completed, but some files were in use, skipped, or corrupted.
The job ran in a cluster environment and was active on one computer, and then the cluster performed a failover and the job was restarted on another computer in the cluster. Two separate sets of job history are available when a job is failed over. The first job history includes the failed over status and the second job history includes the status that is appropriate for the completed job.
The status is the same as the failed over status, however theoption was selected.
The administrator terminated the operation as it was running.
Canceled, timed out
Thefeature was enabled and the job was not completed within the specified timeframe.
The operation took place, but one or more significant errors occurred. The job log should indicate what caused the errors so that you can decide if you want to run the job again. For example, if a job failure occurred due to a lost connection during job processing, you could choose to resubmit the job when the connection is restored.
If a drive loses power during a backup operation, you should restart the backup job using a different tape. You can restore the data that was written to the tape up to the point of the power loss, but you should not reuse the tape for subsequent backup operations.
A failed job has an error message in the Errors section of the job log with a link to the Veritas Technical Support website.
A job may fail for the following reasons:
The job was active when the status of the managed Backup Exec server was changed from Communication Stalled to No Communication. The custom error-handling rule for Recovered Jobs was applied to the job.
The job did not run during the scheduled time window. The job is rescheduled to run based on the time window that you configured.
The following statuses may appear for the jobs that are scheduled:
Table: Scheduled job statuses
The scheduled job will not run because of a scheduling issue.
Not in time window
The job was ready to be sent for processing, but the time window for the job closed.
The job has been placed on hold.
A temporary state that displays when Backup Exec is applying an error-handling rule that is enabled to retry the job.
The job is ready to run, but cannot for one of the following reasons:
The job is scheduled to run in the future. The scheduled jobs that are linked to another job, such as a job to duplicate backup sets, will not display a scheduled job status.
The job is ready, but the Backup Exec server has been paused. No jobs are dispatched while the Backup Exec server is paused.
To Be Scheduled
A state that the scheduled job transitions through as it is being sent for processing.
The job cannot run because one or more of the settings in the backup definition cannot be satisfied.
The Rule Blocked status may appear for any of the following reasons: