Backup Exec 21 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)
- Updating Backup Exec with Veritas Update
- 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
- 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
- Changing network and security options for Backup Exec
- 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
- Instant Cloud Recovery
- Preconfigurations to be completed in the Azure portal
- GDPR Guard
- 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
- Integration with Veritas SaaS Backup
- Forever Incremental Backup
- 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
- 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
About true image restore for synthetic backups
True image restore is automatically enabled for synthetic backups. True image restore enables Backup Exec to restore the contents of directories to what they were at the time of any full backup or incremental backup. Restore selections in backup sets are made from a view of the directories as they existed at the time of the synthetic backup. Files that were deleted before the time of the backup are not restored. In true image restore, only the correct versions of files are restored from the appropriate full or incremental backups that contain them. Previous versions are not restored and then overwritten.
Note:
The Use storage-based catalogs option must be enabled in the Catalogs settings to use true image restore.
Backup Exec collects the information that is required to detect the files and directories that have been moved, renamed, or newly installed from a tape archive (tar) or a compressed archive. Depending on how the files were packaged and how they were installed, some newly installed files are not backed up by normal incremental backups. With true image restore enabled, Backup Exec compares path names with path names from the previous full or incremental backup. If a name is new or changed, the file or directory is backed up.
The following are examples where using true image restore backs up the files that would not otherwise be backed up:
A file named C:\pub\doc is moved to or installed in C:\spec\doc. Here, the archive bit is unchanged for files and subdirectories inside that directory, but C:\pub\doc is new in the C:\spec\ directory and is backed up.
A directory named C:\security\dev\ is renamed as C:\security\devices\. Here, the archive bit is unchanged for files and subdirectories inside that directory, but C:\security\devices\ is a new directory and is backed up.
The following table lists the files that are backed up in the C:\user\doc directory during a series of backups between December 1, 2012 and December 4, 2012:
Table: Example table of files backed up because true image restore is enabled
Day | Type of backup | Backed up files in C:\user\doc | Backed up files in C:\user\doc | Backed up files in C:\user\doc | Backed up files in C:\user\doc | Backed up files in C:\user\doc | Backed up files in C:\user\doc |
---|---|---|---|---|---|---|---|
December 1, 2012 | Full | file1 | file2 | dirA\fileA | dirB\fileB | file3 | |
December 2, 2012 | Incremental | file1 | file2 | dirA\fileA | ---------------- | ---------------- | |
December 3, 2012 | Incremental | file1 | file2 | dirA\fileA | ---------------- | ---------------- | |
December 4, 2012 | Incremental | file1 | file2 | ----------------- | ----------------- | ----------------- | file4 |
Note:
Dashes (-------) indicate that the file was deleted before this backup.
Assume that you want to restore the December 4, 2012 version of the C:\user\doc directory.
You perform a regular restore of the full backup set followed by a regular restore of subsequent incremental backup sets. The restored directory contains all files and directories that ever existed in C:\user\doc from December 1, 2012 (last full backup) through December 4, 2012.
For example, the following files and directories are included:
file1
file2
dirA\fileA
dirB\fileB
file3
file4
In a true image restore of the December 4, 2012 backup, the restored directory has only the files and directories that existed at the time of the incremental backup on December 4, 2012.
The following list includes the files and directories that existed:
file1
file2
file4
Backup Exec does not restore any of the files that were deleted before the December 4, 2012 incremental backup.
The restored directory does not include the 'dirA' subdirectories, even though they were backed up on December 4, 2012. Backup Exec does not restore these directories because they did not exist at the time of the incremental backup, which was the reference for the true image restore.
A true image restore preserves the files that are currently in the directory but were not present when the backup was completed. Assume that you created a file named file5 after the incremental backup that occurred on December 4, 2012, but before doing the restore.
In this case, the directory contains the following files after the restore:
file1
file2
file4
file5