Veritas Backup Exec 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)
- Backup Exec license contract information
- About upgrading to Backup Exec
- Getting Started
- Backups
- Backing up data
- Restores
- How Backup Exec catalogs work
- Job management and monitoring
- 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 Veritas 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
- Reports
- 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
- Integration with Veritas™ Information Map
- Appendix A. Veritas Backup Exec Agent for Windows
- About the Backup Exec Agent Utility for Windows
- Appendix B. Veritas Backup Exec Deduplication Option
- Creating or importing deduplication disk storage
- Selecting storage devices for direct access sharing
- Appendix C. Veritas 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. Veritas 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. Veritas 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. Veritas Backup Exec Agent for Microsoft Exchange Server
- Backing up Exchange data
- Appendix G. Veritas Backup Exec Agent for Microsoft SharePoint
- Backing up Microsoft SharePoint data
- Appendix H. Veritas 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. Veritas 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. Veritas Backup Exec Agent for Microsoft Active Directory
- Appendix K. Veritas Backup Exec Central Admin Server Option
- 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. Veritas Backup Exec Advanced Disk-based Backup Option
- Appendix M. Veritas Backup Exec NDMP Option
- 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. Veritas 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. Veritas 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
Changing the settings for a managed Backup Exec server
The settings for a managed Backup Exec server determine how the managed Backup Exec server communicates and interacts with the central administration server. For example, you can change the connection type, the catalog location, and the job reporting and monitoring functionality. You can change the settings for a managed Backup Exec server at any time.
Note:
You may need to restart the services on the managed Backup Exec server after you change the settings. For example, if you change the catalog location, you must restart the services to enable the change to take effect.
To change the settings for a managed Backup Exec server
- On the central administration server, on the Storage tab, double-click the managed Backup Exec server.
- In the left pane, select Settings.
- Select the appropriate options.
Connection settings
Select one of the following types of connections with the central administration server:
Fast connection
Configures frequent communications between the central administration server and the managed Backup Exec server. By default, when you choose this setting, job status updates are sent every 10 seconds to the central administration server. Job logs and job histories are sent whenever a job on the managed Backup Exec server completes.
Slow connection
Configures less frequent communications between the central administration server and the managed Backup Exec server. By default, when you choose this setting, job status updates are sent every 120 seconds to the central administration server. Job logs and job histories are sent only when a job on the managed Backup Exec server fails.
Custom
Lets you change the thresholds that trigger the communication statuses when managed Backup Exec servers become unresponsive. You can also set how often the managed Backup Exec server sends active job status updates to the central administration server. The frequency affects the network traffic.
Communication stalled
Note:
This option appears only if Custom is selected in the Connection settings field.
Indicate the amount of time to allow before the managed Backup Exec server's status changes to Communication Stalled if the managed Backup Exec server is unresponsive.
The central administration server does not delegate jobs to the managed Backup Exec server when it has a status of Communication Stalled. Job delegation resumes if the managed Backup Exec server returns to an Enabled status before the threshold is exceeded.
The default threshold is five minutes.
No communication
Note:
This option appears only if Custom is selected in the Connection settings field.
Indicate the amount of time to allow before the managed Backup Exec server's status changes from Communication Stalled to No Communication.
When the status of the managed Backup Exec server changes from Communication Stalled to No Communication, the central administration server marks the active jobs on the managed Backup Exec server as Failed. The custom error-handling rule Recovered Jobs is applied to any job that is active when the No Communication status appears.
The default threshold is 15 minutes.
Send active job status updates to the central administration server
Note:
This option appears only if Custom is selected in the Connection settings field.
Select this option to enable the managed Backup Exec server to send a job status update to the central administration server. You can adjust the number of seconds that a managed Backup Exec server waits between sending job status updates to the central administration server. To preserve network bandwidth when many jobs are running, increase the amount of time between job update statuses. Decrease the amount of time if you want to send more updates.
The default is 10 seconds, which provides near real-time monitoring. This setting is recommended only for fast network connections.
Send status updates to the central administration server every
Note:
This option appears only if Custom is selected in the Connection settings field and Yes is selected in the Send active job status updates to the central administration server field.
Set the amount of time that a managed Backup Exec server waits between sending job status updates to the central administration server. To preserve network bandwidth when many jobs are running, increase the amount of time between job update statuses. Decrease the amount of time if you want to send more updates.
The default is 10 seconds, which provides near real-time monitoring. This setting is recommended only for fast network connections.
For low-bandwidth network connections, consider a setting of 120 seconds. This frequency allows updates to be displayed for a medium-sized job while still significantly decreasing the network traffic caused by job status updates.
If you uncheck the check box, job status updates are not sent. Job progress is not displayed on the central administration server. When the job is complete, the Job History on the central administration server is updated.
Send job log details to the central administration server
Choose when the job log for the managed Backup Exec server is sent to the central administration server. You can choose to send the job log one time per day, after a job completes, or never.
The following options are available:
Never
If you select this option, job logs are stored locally at the managed Backup Exec server.
Once a day
If you select this option, the Send job logs at field appears. You must select the time to send the job log to the central administration server.
On job completion
If you select this option, the Send job log only if the job fails field appears. Select Yes to send the job log only for failed jobs. Select No to send the job log regardless of the job disposition.
Send job logs at
Choose the time when Backup Exec sends the job logs for the managed Backup Exec server to the central administration server. This option appears only if Once a day is selected in the option Send job log details to the central administration server
Send job log only if the job fails
Choose whether to send the job log for failed jobs only or for all jobs. Select Yes to send the job log only for failed jobs. Select No to send the job log regardless of the job disposition. This option appears only if On job completion is selected in the option Send job log details to the central administration server
Send job history details to central administration server
Choose when the job history for the managed Backup Exec server is sent to the central administration server.
The following options are available:
Never
If you select this option, job histories are stored locally at the managed Backup Exec server.
Once a day
If you select this option, the Send job history logs at field appears. You must select the time to send the job history to the central administration server.
On job completion
If you select this option, the Send job history only if the job fails field appears. Select Yes to send the job history only for failed jobs. Select No to send the job history regardless of the job disposition.
Send job history at
Choose the time when Backup Exec sends the job history for the managed Backup Exec server to the central administration server. This option appears only if Once a day is selected in the option Send job history details to the central administration server.
Send job history details only if the job fails
Choose whether to send job history details for failed jobs only or for all jobs. Select Yes to send the job history details only for failed jobs. Select No to send the job history details regardless of the job disposition. This option appears only if On job completion is selected in the option Send job history details to the central administration server.
Monitor jobs that are created locally on the managed Backup Exec server
Select this option if you want to view delegated jobs and the jobs that are created on the local managed Backup Exec server.
You can also hold, delete, run, cancel, and change the priority order of the jobs that are created on or copied to the local managed Backup Exec server.
Display an alert when the time is not synchronized between the managed Backup Exec server and the central administration server
Select this option to enable Backup Exec to create an alert if the clock on the managed Backup Exec server differs from the clock on the central administration server. An alert is generated when the number of seconds indicated is exceeded.
CAS monitors the internal computer clocks on both the managed Backup Exec servers and the central administration server. If time differences develop between the central administration server and the managed Backup Exec servers, jobs could run at unexpected times. To prevent problems, the time that is reported on managed Backup Exec servers should match the time that is reported on the central administration server. If you receive time difference alerts, reset the clock on the managed Backup Exec server to match the system clock on the central administration server.
If you change the system time on either the managed Backup Exec server or the central administration server, you must restart the Backup Exec services on that server.
Send the alert after the servers are not synchronized for
Indicate the number of seconds that the clocks on the managed Backup Exec server and the central administration server must differ before Backup Exec sends an alert.
Note:
This option appears only if Enabled is selected in the Display an alert when the time is not synchronized between the managed Backup Exec server and the central administration server field.
Storage and media database location
Indicate whether the storage and media database is located on the central administration server or a managed Backup Exec server.
Keep the catalogs on
Set the location of the catalog to one of the following locations:
Managed Backup Exec server (distributed)
Distributes the catalog files between the central administration server and the managed Backup Exec server. If storage and media data is kept in a local database on the managed Backup Exec server, then the distributed location is the only available catalog location. Select this option if you have a low-bandwidth network connection.
Central administration server (centralized)
Keeps all catalog files on the central administration server. A high-bandwidth network connection is required for this option.
Both servers (replicated)
Replicates all catalog files from the managed Backup Exec server to the central administration server. If a managed Backup Exec server is unavailable, you can still browse the catalog from the central administration server. However, you cannot restore data because the managed Backup Exec server is unavailable. A high-bandwidth network connection is required for this option.
See CAS distributed, centralized, and replicated catalog locations.
Private cloud server
Select this option to enable a managed service provider to locate a Backup Exec server in its data center, and then configure it for a CAS environment with other Backup Exec servers that are located across the WAN at the managed service provider's customer locations. As an alternative to shipping tapes off-site for storage, backups can be run and stored locally, and then copied to the cloud server's deduplication disk storage device. Additionally, this feature can be used by customers with widely distributed networks who want to use Backup Exec servers in remote offices for local backups, and then copy the backup sets to a Backup Exec server that is located in a central data center. This option is part of the Cloud Services for Backup Exec feature.
- Click Apply.