Backup Exec 20.4 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
- 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
- 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
Restoring Exchange data
The Exchange Agent lets you restore Exchange databases as well as individual mailbox items. You can restore items to their original location or you can redirect the restore to a new location.
The Restore Wizard displays only up to 30,000 items. If you want to restore data from a database or mailbox that contains more than 30,000 items, you must search for the item that you want to restore. You can use search criteria such as the type of data and the date of the original backup to help reduce the number of items that display.
The requirements and procedures for restoring Exchange data vary depending on the backup strategy you used. Before you restore Exchange data, you should review the required configuration and tasks.
You can restore Exchange data in the following ways:
Use the recovery database to recover data from an older backup copy of the store without disturbing client access to current data.
Restore Exchange data from snapshot backups.
Restore individual Exchange items from a backup that is enabled for Granular Recovery Technology (GRT).
Restore Exchange data to a server other than the one from which it was backed up.
This topic includes the following information:
Review the following before restoring Exchange:
The databases must already exist on the destination server, and must have the same names as the original databases.
The destination server must have the same Organization and Administrative Group name as the source server.
Before you start the restore, configure the destination databases so that they can be overwritten by a restore.
You cannot restore messages with attachments that contain contact groups and undeliverable reports because Microsoft Exchange Web Services (EWS) for Microsoft Exchange 2013 does not support the restore of distribution lists and message reports when they are attachments. It is recommended that you restore messages that contain these types of attachments to a .PST file.
Before you restore Exchange, you should configure the destination database.
To configure a database
- Do one of the following:
For Exchange 2010
Open the Exchange Management Console utility.
For Exchange 2013 or later
Open the Exchange Admin Center.
- Right-click the database that you want to overwrite.
- Click Properties.
- Do the following:
For Exchange Server 2010 or later
On the Maintenance tab, select This database can be overwritten by a restore.
Exchange Server 2010 or later lets you mount a second copy of an Exchange mailbox store on any Exchange Server in the same Exchange Administrative Group as the original while the original store is still running and serving clients. This allows you to recover data from an older backup copy of the store without disturbing client access to current data.
Exchange Server 2010 or later uses recovery databases (RDB). Each server has a recovery database and there cannot be more than one mounted recovery database.
See your Microsoft Exchange documentation for more information about RDBs and recovery databases.
After the RDB is created, you can restore online backup sets to it. Then you can use the version of the Exchange Management Shell in Exchange to extract mailbox data from the stores into .PST files, and optionally merge the extracted data back into the online stores.
If the RDB resides on a different Exchange Server than the databases you are restoring, you should review the requirements for redirecting the restore of Exchange recovery databases.
Following are requirements for restoring data using the Exchange Server 2010 or later recovery database:
If multiple stores are selected for restore, mailbox stores in the RDB must come from the same database. You cannot add mailbox stores from different databases to the RDB at the same time.
Public folder stores are not supported for restore using the RDB.
Do not mount mailbox stores in the RDB before the restore. If you do mount the stores before the restore, then you must dismount them. Select the following option on the database property page in Exchange System Manager:
This database can be overwritten by a restore.
Then, delete any files created in the data path for the RDB and added stores prior to restoring them.
Any files created in the data path for the RDB and added store or stores should be deleted as well, if stores were mounted prior to the restore.
On the server that hosts the RDB, there must be a database with the same name as the original database for the data you are restoring. If no such database exists on the server, then you can use that name for the RDB when you create it.
The Active Directory topology of the Exchange system must be intact and in the same state it was in when the backup was made. You cannot restore mailbox stores that were deleted and recreated. In addition, you cannot recover mailboxes from stores if the mailboxes were deleted and purged from the system or moved to other servers or mailbox stores.
When the RDB exists on a server, the mailbox stores that it contains are the only stores that can be restored on that server by default. It is recommended that you create the RDB only when you intend to recover data using it, and remove the RDB from the server after the data recovery is complete.
You can have more than one recovery database; however, you can only mount one recovery database to recover data.
Do not mount the recovery database before the restore. If you do mount the recovery database before the restore, you must dismount it. Select theoption on the database property page in the Exchange Management Console utility.
Refer to your Microsoft Exchange Server documentation for more information on the requirements and restrictions of recovering Exchange data.
Note the following when restoring Exchange data from snapshot backups:
If circular logging is enabled, only point-in-time, loss restores are possible. Roll-forward, no-loss restores cannot be performed.
To restore individual public folder messages from tape, you must first duplicate the backup sets that contain the messages to disk storage. You can then restore the data from that disk storage.
The backup that you want to restore from must be a full backup or a copy backup. If there is an incremental or differential backup that is subsequent to the full backup, then you can restore individual items from the incremental or differential backup. The backup sets for the full backup and the incremental or differential backup must be on the same volume.
You cannot restore individual public folder messages from tape if the original backup is an incremental backup.
To restore individual Exchange public folder messages from tape by duplicating backup sets to disk
- Insert the tape containing the required Exchange backup sets into a tape drive.
- Create a duplicate backup sets job.
- After the job completes, run a restore job to restore the individual public folder messages from the Exchange backup sets that are duplicated on the disk storage.
With Backup Exec, you can restore Exchange data to the server from which it was backed up or redirect the Exchange data to a different location. When redirecting Exchange data, the service pack on the Exchange Server where data is being redirected should be the same as the service pack on the original Exchange Server.
Following are requirements for redirecting Exchange database restores:
The databases must already exist on the destination server.
The destination server must have the same Organization Group name as the source server.
The destination databases must be configured so that they can be overwritten.
You cannot redirect the restore of the following:
A version of Exchange Server database to a different version of the database. Service packs for both Exchange Servers should also be the same.
Site Replication Service (SRS) and Key Management Service (KMS). These services are dependent on the computer they reside on; redirection to another computer is not supported and could result in the loss of functionality of these services.
KMS is not available in Exchange.
Before starting the redirected restore job, review information on finding and viewing specific data to restore, as well as for details on restore options and submitting restore jobs.
After completing the restore, it is recommended that a full backup of the restored databases be performed.
With Backup Exec, you can restore mailbox items such as mailboxes and public folders to a different mailbox on the same server or to a different location.
You can also restore mailboxes or mailbox items to a .PST, which is a Microsoft Outlook data file that is compatible with Microsoft Outlook 2007 or 2010.
Following are requirements for redirecting Exchange mailbox and public folder items back to Exchange:
The specified mailbox or public folder store must exist.
The Backup Exec logon account must have rights to the destination mailbox.
To overwrite existing public folder data, the logon account must have ownership of the public data. In this rare situation, it is recommended that when you restore public folder data, do not use the restore option Overwrite existing mail messages and folders on the Restore wizard panel titled How do you want to restore the items?.
Following are requirements for restoring to a .PST file:
The Agent for Windows must be installed on the destination server to which you redirect mailbox or public folder items.
Microsoft Outlook 2007 or 2010 (32-bit only) must be installed on the destination server.
The maximum size of the .PST file is 20 GB. If the restore exceeds the size limit, the data is spanned across multiple .PST files which are numbered consecutively.