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
About selecting data to back up
When you back up a server, Backup Exec includes all of the data on the server in the backup selections by default. If you want to modify the backup selections, you can click Selections box on the Backup Definitions Properties dialog box.in the
See Backing up data.
Instead of backing up all of the data on a server, you can select drives, folders, files, System State, network shares, or databases on the Browse tab.
To expand or collapse the view for an item, click the arrow next to it or double-click the item's name. To view the contents of an item, double-click the item's icon. The item's contents appear in the right frame of the backup selections view. You can traverse file levels from either side of the window by clicking folders and subfolders as they appear.
When you browse remote selections, Backup Exec requires a valid logon account to expand the computer contents. If the default logon account does not enable access to a remote selection, Backup Exec prompts you to select another existing logon account. You can also create a new logon account that can access the selection.
To include data in the backup, select the check box next to the drive or directory that you want to back up.
This topic includes the following information:
Theoption lets you select which resources are most important to you. When an item is tagged as a business-critical resource, Backup Exec prioritizes the backup of that resource within the backup window before any resources that are not tagged as business-critical. If you tag a resource as business-critical, all of its children are also tagged as critical. When you tag an item as a business-critical resource, Backup Exec changes the icon for that resource in the backup set view and in the restore wizard.
Theoption is enabled for the following resources:
Windows volumes and UNIX root volumes
Virtual machine folders
Note that theoption is disabled on partial selections. In addition, the option is not applicable to Enterprise Vault resources, such as Compliance Accelerator or Discovery Accelerator.
When an item is tagged as a business-critical resource, it applies only to that job. It is not a global setting. When you tag a server's resource as business-critical and also select other resources from the same server, then the backup priority for the business-critical resource is evaluated in relation to the other resources for that server only. For multi-server jobs, business-critical resources are backed up by the order in which the servers are prioritized, with the business-critical resources for servers at the top of the list being backed up before business-critical resources for the servers that are lower on the list.
Critical system resources can be tagged as business-critical as well. If critical system resources are not selected, then the resources that are tagged as business-critical are backed up before critical system resources if they are in the same backup job. However, the best practice for critical system resources is to back them up in a separate backup job. If you include both business-critical resources and critical system resources in the same backup job, note that system state is always backed up last regardless of whether it was tagged as a business-critical resource or not.
After you tag items as business-critical resources you can use the arrow buttons on thetab to change the order in which the items are backed up. However, an item that is not tagged as a business-critical resource cannot be moved ahead of an item that is tagged as a business-critical resource. For example, if you tagged your C drive as a business-critical resource, but did not tag your E drive as a business-critical resource, you cannot move the E drive ahead of the C drive.
During a rolling upgrade, the tag as business-critical feature is not applied to jobs that are delegated to managed Backup Exec servers until the managed servers are upgraded to the most recent version of Backup Exec.
The Selection Details tab lets you include or exclude files for backups by specifying file attributes. Exclusions apply to all of the jobs in a backup definition.
You can do any of the following on the Selection Details tab:
Include or exclude subdirectories. For example, you can choose to back up a parent folder without backing up any folders that reside inside it.
Include only modified files. For example, you can choose to back up only the files that have changed since the last backup job.
Include only read-only files.
Include or exclude files by file name attributes. For example, you can select only files with .txt extensions, or exclude files with .exe extensions from a backup. If you exclude files by an attribute that does not exist, all files of that type are excluded. For example, excludes based on SQL database dates result in global SQL excludes since SQL databases do not have date attributes.
Select only any files that fall within a specified date range. For example, you can select any files that were created or modified during the month of December.
Specify the files that have not been accessed in a specified number of days. For example, you can select the files that have not been accessed in 30 days from your "My Documents" folder. Then, run a full backup job for which you select the method to back up and delete the files.
If you select to back up data from multiple servers or applications, you can create separate backup definitions for each server or application. Alternatively, you can create one backup definition that includes all servers and applications. If you create separate backup definitions, it is easier to identify problems when backup jobs fail. Also, if an issue arises with one server that causes a backup job to fail, the other backup jobs can still complete successfully. If you create one backup definition that includes all of your servers and applications, it takes less work to monitor the job's status. You can select a default method for backing up multiple servers in the Backups dialog of the Backup Exec Settings.
When all the critical system components are included in your backup job selections, the Simplified Disaster Recovery indicator on the selections pane reads ON. If you deselect one or more critical system component files, the indicator changes to OFF.
If you deselect any critical system components, it can disqualify your backup data from being used in certain types of restore scenarios.
You must include all critical system components in your backup selections if you intend to use any of the following restore scenarios:
Simplified Disaster Recovery
Conversion to virtual machines
Complete online restore of a Microsoft Windows computer
You can enter fully qualified domain names in Backup Exec anywhere that you can enter a computer name. In addition, Backup Exec can show fully qualified domain names where computer names are listed.
For fully qualified domain names, the following rules apply:
The maximum number of characters for each label (the text between the dots) is 63
The maximum total number of characters in the fully qualified name is 254, including the dots, but excluding the \\
The name cannot include the following characters: * | < > ?
It is not recommended using both fully qualified domain names and non-qualified domain names. It is recommended that you use fully qualified domain names.
For example, if you have a computer named Test_Computer, you can have two selections for it. One selection is called Test_Computer. The fully qualified selection is called Test_Computer.domain.company.com. In this case, Backup Exec treats each selection as a separate computer, even though both selections are for the same computer. For any backup jobs that use the short computer name, the catalog contains the short computer name. For any backup jobs that use the fully qualified name, the catalog contains the fully qualified name.