Backup Exec 22.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
- Configuring the Home tab
- Backups
- Recommendations for when to use virtual-based backup and agent-based backup
- 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
- Cloud deduplication storage device
- Requirements for configuring a cloud deduplication storage device
- About the Backup Exec™ CloudConnect Optimizer
- Generic S3 Configurator
- OpenStorage devices
- Microsoft 365
- OneDrive plugin: Performance and throttling configuration
- Exchange plugin: Performance and throttling configuration
- SharePoint plugin: Performance and throttling configuration
- Teams plugin: Performance and throttling configuration
- 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
- Configuring parallel streams and job settings for Microsoft 365
- 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
- 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
- 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
- About SQL Server Always On availability groups
- 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 File Servers
- Appendix O. Backup Exec Agent for Linux and Unix
- About installing the Agent for Linux and Unix
- About establishing trust for a remote Linux and Unix computer in the Backup Exec list of servers
- Editing configuration options for Linux and Unix computers
- About backing up a Linux and Unix computer by using the Agent for Linux and Unix
- About restoring data to Linux and Unix computers
- Editing the default backup job options for Linux and Unix computers
- Uninstalling the Agent for Linux and Unix
- Appendix P. 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 Q. Accessibility and Backup Exec
- About keyboard shortcuts in Backup Exec
- Backup and Restore tab keyboard shortcuts
- Storage tab keyboard shortcuts
Notes for Microsoft 365
Note the following points:
For primary backups, Forever Incremental, Consolidate full, and Custom full templates only deduplication disk storage is supported. Duplicate backups can be targeted to any supported storage.
For Exchange Online restore, ensure that the destination mailbox is already created.
For Exchange Online restore, only the name, comment, permissions, and retention settings for folders are restored.
For OneDrive restore, ensure that the user OneDrive is already created.
For OneDrive restore, to receive an email invite for direct access permission that is shared with groups, you must enable the
setting and click . To enable the setting, go to .Note:
This setting is only available in the Microsoft 365 portal and does not exist in Backup Exec.
For OneDrive, Deep Directory only supports restore of a specific number of items. For more information, refer to the following link:
For OneDrive Notebook restore, if the Notebooks folder is not available in the root directory, it is created automatically.
For OneDrive, backup of Preservation Hold Library is supported but you can only restore Preservation Hold Library to a file system.
For OneDrive, only the latest version of the item at the time of a backup, is protected as part of that backup job.
For SharePoint, if any list item attachments are removed or updated after a backup is completed, those attachments are restored as a part of the restore operation. The restore operation does not delete or modify any attachments, which are not part of the backup data.
For Sharepoint, TLE (Top Level Entity) and Site name are always the same. The restore browse view also displays the same names.
If a document is backed up with pending approval status, it is approved during the restore operation.
After a new SharePoint site is created, Microsoft API may take some time to make the site available for backups in Backup Exec.
When you restore an event, ensure that you select all the records for repeated events from the restore browse view.
If you restore a deleted non-repeated event multiple times, duplicate entries of the event are created.
During file system restore, in the folder created for each event, any character that is not allowed in the file/folder name is replaced with an underscore (_).
SharePoint Online only restores the latest version of the item and for file system restore, all versions are restored.
Microsoft Teams backup is performed using Graph Export APIs. These are metered APIs and there is a cost associated with the download of each message with these APIs. Refer to the Microsoft documentation for more information about the associated cost.
https://learn.microsoft.com/en-us/graph/teams-licenses - model=B
Get messages across all channels - under model=B
BackupExec uses model=B based on the recommendation by Microsoft.
The following applications in channel tabs are protected and can be restored: PowerPoint, Excel, SharePoint, PDF, Word, OneNote, Visio, Power BI, Planner, Document Library, Website, Polly, and Whiteboard. The tabs display applications only if the reference data is available.
Applications added to a conversation are supported for backup and restore if Teams creates a channel tab for them. Applications that are added directly to a conversation without creating a tab are not supported for backup and restore. For example, PDF and Power BI.
After the restore operation, you may see messages with the name of the Azure AD application that was created during tenant configuration. This is because the restore operation works in the context of the Azure AD application and not in the context of any specific user.
After backup, if a Teams user gets a higher privilege role assigned (for example, owner) then the restore process does not revert this role. The higher privilege role is preserved.