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
Troubleshooting blocked access to backed up items with GDPR Guard
If you have problems with blocking access to backed up items with GDPR Guard, review the following points.
If the import command is successful but the restore and search view continue to display and restore the blocked items, check the following:
Check if the full path of any blocked item entry in the CSV file that was specified during import contains a comma (,). If the file name or any of the folders in the path contain a comma, the entry is not imported properly. For example: E:\Folder,Delimited\file.txt and E:\F1\ab,a.txt are unsupported entries for blocked items.
Some entries may get blocked if the full path of a blocked item's entry contains a wildcard within a folder that is also applicable to the items of that folder and its subfolders. For example: E:\F1\a*.txt blocks all text files starting with letter 'a' inside the E:\F1 folder and inside the E:\F1\F2 folder. To ensure that the item within a subfolder is not blocked, you must add each entry separately and not use wildcards in this scenario.
If the same server is added in Backup Exec using multiple names, such as by the NetBIOS name, FQDN, or IP address, the items are blocked only for the server name that is specified in the blocked item entry in the CSV. To resolve this issue, add the blocked item entries via each of the server names separately in the input CSV for the import operation.
If some blocked items are skipped during the import operation with the reason displayed as invalid item path, check the following:
The full path for the skipped item does not start with the volume or share name and starts with server name. For example: E:\folder1\a.txt and TestShare\F1\b.txt are acceptable entries in the full path.
Only the file name in the item path contains '*' related wildcards. If the folder path contains the wildcard, the entry is skipped. For example: G:\Test2\*\CatTrans.xsl and G:\*\results.txt are invalid entries.
If Import operations terminate with the following error: "An error occurred while processing a blocked item. The internal list of blocked items does not exist".
Check whether the input CSV file path is correct and does not point to an invalid drive or network location.
If the export operation terminates with the following error: "An error occurred while opening the internal list of blocked items".
Ensure that the specified output folder path is valid and does not point to an invalid drive or network location..
If some of the blocked items are displayed in the restore or search view that may be due to the following reasons:
An import operation is running for the CSV file containing some blocked items of the same resource.
The integrity check failed for the internal list of blocked items for that resource or some problem occurred while reading from the internal list of blocked files for the restore or search view.
If you run the restore job, the restore job log displays the exact reason of the failure in reading from the internal list of blocked files.
If a soft or hard link path is specified in the CSV, only the link is blocked. To block the folder that the link is pointing to, specify the actual path of the folder in the CSV.
If you want to remove a blocked file entry from an already imported CSV file, do the following in the order listed:
Run the export command.
Remove the entry from the generated CSV.
Delete the internal file containing the list of blocked items for the resource whose entry is removed. Remove the internal file from te following location: "data\BLFileInfo" folder under the Backup Exec installation directory.
Run the import command again with the
Import-BEItemsToBlock - RESETifCorrupted - CsvFilePath <CVS file path> - ColumnNameForServerName <Name of 1st column> - ColumnNameForBlockedItemPath <Name of 2nd column>
If the restore and search view does not display results for a long time it can be because a large number of blocked items are added for that resource. In such a scenario, restore job can still be run at the folder or volume level to view the items that are restored and viewed.
If a standalone media server that has blocked items needs to be converted into an MBES server, perform the following steps in the order listed:
Export the blocked items file.
Delete the bin files from the
Data\BLFileInfofolder under the Backup Exec installation folder.
Convert the standalone server to an MBES server.
Import the blocked items on CAS using the exported file that you created.
See About GDPR Guard.