Backup Exec 20.1 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 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
- 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
- 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 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 default backup settings
You can choose the processing method to use for Hyper-V backups. You set this option for the Backup Exec server, so the method that you choose is applied to all backups of Hyper-V virtual machines that the Backup Exec server protects.
Two processing options are available:
The standard processing method. This method reads the whole virtual disk and identifies the changes that should be backed up. The changed blocks that are identified are then backed up.
The default option for processing new Hyper-V backups is
.The faster processing method. This method is faster than the standard processing method because it writes all changes to a new differencing disk and then backs up only the differencing disk. This method saves time because the entire disk does not have to be read.
Table: Difference between the standard processing and the faster processing method
Processing method | Supported Hyper-V servers | Backup type | Disk storage space | Performance |
---|---|---|---|---|
Standard processing method | Windows 2008 and later. |
| No extra space is required. | Does not impact performance |
Faster processing method | Windows 2012 and later. |
| Requires extra space on the Hyper-V host even after the backup job is complete. The extra space required depends on how long the checkpoint is not merged back into the parent disk and the number of writes that have happened before the merge. The space consumed for each virtual machine might not be significant but if there are many virtual machines in your environment, the checkpoints consumes a significant amount of space. However, you can use this method if you take frequent backups and disk space is not a constraint. | May slow down system performance because a checkpoint is always present for each virtual machine backed up using this method. |
The following notes provide information for upgrades:
When you upgrade from Backup Exec 15 Feature Pack 3, the existing Hyper-V backup setting does not change. Existing and new backup jobs use the setting that was configured in Feature Pack 3, unless you change it.
When you upgrade from Backup Exec 15 Feature Pack 2 or earlier, the default Hyper-V backup setting for existing jobs is
. Existing and new backup jobs use this setting unless you change it.You set these options for the Backup Exec server, so the method that you choose is applied to all backups of Hyper-V virtual machines that the Backup Exec server protect.
To configure Hyper-V incremental backup settings
- Click the Backup Exec button, select Configuration and Settings, and then click Backup Exec Settings.
- In the left pane, select Virtual Machines.
- Select the processing method that you want to use for all Hyper-V incremental backup jobs.
Use the faster processing method
Select this method if you want incremental backups jobs to be processed as quickly as possible, and do not want to perform any differential backups. This option does not support differential backups. If you select this option, all Hyper-V differential backups are processed as incremental backups.
Note:
This option is available only for Hyper-V servers that run Windows 2012 and later. For all supported previous versions of Windows, the standard processing method must be used.
Use the standard processing method
Select this option if you want to run both incremental backups and differential backups.
Note:
When you select a different incremental backup processing method, the next job runs as a full backup instead of an incremental backup.
Note:
In a CAS environment, if the processing method is not the same on the central administration server and the managed Backup Exec server, the method that is set for the managed Backup Exec server is used when a job is delegated from the central administration server.
- Click OK.
In the Virtual Machine Validation Settings, you can change the timeout settings of a virtual machine for VMware and Hyper-V. After you create the validation job for a virtual machine, before the job runs, you can change the maximum time that it takes for a virtual machine to boot. This is a global setting that is applicable to all validation jobs. If the virtual machine does not boot within the selected time, the validation job fails.
To change virtual machine validation settings for VMware and Hyper-V
- Click the Backup Exec button, select Configuration and Settings, and then click Backup Exec Settings.
- In the left pane, select Virtual Machines.
- In the Select the maximum boot time for a virtual machine option, select the time in minutes.
By default, 5 minutes is selected. You can select from 1 to 60 minutes.