Backup Exec 21 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)
- Updating Backup Exec with Veritas Update
- 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
- Changing network and security options for Backup Exec
- 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
- 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
- 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
Advanced Disk Configuration on the Recover This Computer Wizard
The Recover This Computer Wizard restores the hard drive volumes to the same sizes they were before the disaster. If the hard drive in the failed computer is larger than the hard drive that was in place before the disaster, it may result in unused and unallocated space. You can run Advanced Disk Configuration to alter the volume sizes to reflect the larger hard drive size.
The following is an example of why the hard drive volumes should be resized:
The pre-disaster computer hardware contains a 40 GB hard drive with two 20-GB volumes. You replace it with a 90-GB model. SDR then uses the disaster recovery information file to rebuild the hard disk partition table by using the partition information that is found on the original 40-GB hard drive. As a result, only 40 GB of space is allocated on the new 90 GB hard drive, with a partition map that consists of two 20-GB partitions.
You can access Advanced Disk Configuration from within the Recover This Computer Wizard.
You should be familiar with Microsoft Disk Management concepts before you run Advanced Disk Configuration.
The following table provides details about the additional disk-related operations that you can do with Advanced Disk Configuration.
Table: Advanced Disk Configuration tasks
A simple volume is a partition on a disk that contains a file system.
Disk volumes must be formatted before data can be stored on them.
If a disk contains some unallocated disk space that is adjacent to a functional volume, you can extend the volume to include the free space. To extend the volume, it must be either raw or formatted with the Windows NTFS file system.
You can decrease the size of a volume by shrinking the volume into the contiguous, unallocated disk space that is on the same disk.
When you shrink a volume, there is no need to reformat the volume. Ordinary files are automatically relocated on the disk to create the new, unallocated disk space.
A spanned volume spans more than one physical disk. You can create a spanned volume by spanning it across multiple physical disks, or by spanning the volume into unallocated disk space.
To create a spanned volume, you must have a startup volume and at least two dynamic volumes.
Spanned volumes are not fault-tolerant.
Striped volumes store data in stripes across two or more physical disks. Although striped volumes do not provide fault-tolerance protection, they do offer the best performance of all the volumes in Windows.
A mirrored volume provides a copy of the data that is written to a selected volume. Because all data is written to both the mirrored volume and the selected volume, mirroring reduces the capacity of both volumes by 50%.
You can view properties for each volume in the Current Disk Layout view or in the Original Disk Layout view.
You can change assigned drive letters for all volumes if you want to organize your drive letters in a certain way.
Deleting a volume erases all data from the volume; therefore, it is recommended that you use caution when considering the use of this option.
Converting basic disks to dynamic disks lets you create the volumes that span multiple disks. Dynamic disks also let you create fault-tolerant volumes, such as mirrored volumes and RAID-5 volumes. All volumes on dynamic disks are referred to as dynamic volumes.
MBR disks use the standard BIOS interface. GPT disks use extensible firmware interface (EFI).
You can convert MBR disks to GPT disks if the disk does not contain partitions or volumes.
GPT disks use extensible firmware interface (EFI). Master boot record (MBR) disks use the standard BIOS interface.
GPT disks can be converted to MBR disks if the disk does not contain partitions or volumes.
The original disk layout shows the actual hard disk layout that existed during the backup job. Within the simplified layout view, you can accept the disk geometry as it originally existed before the disaster, or you can alter the geometry by changing the volume sizes. Depending on the size of the existing disks, you can alter volume sizes in megabytes, gigabytes, or terabytes.
The simplified layout view has a Preview tab that lets you view the disk geometry as it presently exists. If you change the disk geometry and change volume sizes, click the Preview tab to see a graphical representation of your proposed changes.
If mismatched volumes appear in the simplified volume layout view, you can use the optionto automatically create a volume layout on the available hard disks. You can also manually create a volume layout by using the option.