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
Changing network and security options for Backup Exec
You can configure how Backup Exec works with your network configuration and security. The network and security options are global options that affect all Backup Exec jobs.
If the global network and security settings that you configure do not apply for a specific backup job, you can change the network settings when you create the backup job.
To edit network and security options
- Click the Backup Exec button, select Configuration and Settings, and then click Backup Exec Settings.
- In the left pane, select Network and Security.
- Configure any of the following options:
Select the name of the network interface card that connects the Backup Exec server to the default network that you want to use for backup jobs. The list includes all available network interfaces on the Backup Exec server.
Select the default protocol you want to use for backup jobs.
The options are as follows:
Use any available protocol
Select the 32-bit number that determines the subnet to which the network interface card belongs.
Allow use of any available network interface, subnet, or protocol for Backup Exec agents not bound to the above network interface, subnet, or protocol
Select this option to let Backup Exec use any available network if the remote system that you selected for backup or restore is not part of the specified backup network.
If you do not select this option and the remote system is not part of the specified backup network, the job fails. Backup Exec cannot access the data from the remote system.
Click this option to view the Media Access Control (MAC) address, adapter type, description, IP addresses, and subnet prefixes for the interface that you selected for the backup network.
Enable selection of user shares
Select this option to include user-defined shares in jobs.
If you do not select this option, you cannot select user-defined shares when you create jobs.
Enable TCP dynamic port range
Lets Backup Exec agents use a range of ports for communication.
You enter the port range. If the first port that Backup Exec attempts to use is not available, Backup Exec attempts to use one of the other ports in the range. If none of the ports in the range is available, Backup Exec uses any available dynamic port. Default port ranges are 1025 to 65535. It is recommended that you use a range of 25 allocated ports for the remote system if you use Backup Exec with a firewall.
Use a custom port to receive operation requests from the Oracle server
Lets you specify the port that Backup Exec uses for communication between the Backup Exec server and the remote computer for both DBA and Backup Exec server-initiated operations. By default, Backup Exec uses port 5633.
If you change the port number on the remote Windows or Linux computer, you must also change it on the Backup Exec server. Then you must restart the Backup Exec Job Engine service on the Backup Exec server.
Use FIPS 140-2 compliant software encryption
Lets you enable software encryption that complies with FIPS 140-2 standards. If you select this option, you must use a 256-bit AES encryption key. This option is available only for Windows computers.
You must stop and restart the Backup Exec services for this change to take effect.
Lets you create a new encryption key or manage existing encryption keys.
Allow only Kerberos authentication from the Remote Administration Console
Allows Backup Exec to restrict clients, such as Remote Administration Console to use Kerberos only authentication.
If you select this check box to use only Kerberos authentication, the Backup Exec Management Service must be restarted. Any connections from Remote Administration Console that fall back to use NTLM authentication are disabled.
By default, this option is not selected.
This option is disabled when a Backup Exec server is in a workgroup. Only the owner of a System Logon Account, who is logged on to the Backup Exec console has the privileges to change the option.
The System Logon Account must be a member of Domain Admins group.
Secure the Backup Exec console
Lets you secure the Backup Exec console by providing the following features when you select the Secure the Backup Exec Console check box:
After you select the Secure the Backup Exec Console check box, the authentication setting is enabled and the next time that you launch Backup Exec, you need to enter Backup Exec login credentials to connect to the console.
If you do not enter the credentials you cannot connect to the Backup Exec console.
Lock Console option
After you select the Secure the Backup Exec Console check box, this feature is enabled. You can lock the Backup Exec session that you are working on and secure the Backup Exec console from unauthorized access. Unless you unlock the Backup Exec console, you cannot perform any tasks in the Backup Exec user interface.
By default, this check box is not selected.
This option is not applicable for Remote Administration Console (RAC) as you must always provide credentials to connect to the Backup Exec console.
Only the owner of a System Logon Account, who is logged on to the Backup Exec console has the privileges to change the user access settings. If you want to know the owner of the System Logon Account, click the Backup Exec button, and then select Configuration and Settings > Select Logon Accounts > Manage Logon Accounts. On the Logon Account Management dialog box, the Owner column displays the owner of the System Logon Account.
In case of rolling upgrade, if you have an earlier version of MMS and an updated version of CAS, and you connect to MMS from CAS, this check box is available and you can select it. However, this setting is not enabled for MMS.
Disk storage lockdown setting
The Ransomware Resilience feature lets you enable or disable the lockdown setting on the disk storage.
The disk storage lockdown setting protects the disk-based backup storage configured with Backup Exec. Access to disk storage is limited only to authorized processes like Backup Exec services. Only Backup Exec is allowed to write to the disk storage (Backup Exec data folders where the backup jobs are targeted). No other process can write to the disk storage. In addition, external processes are not allowed to modify backup data by injecting code into Backup Exec processes.
While the lockdown is enabled, backups and restores continue to work without a change.
If the disk storage is created on a network share hosted on a remote server, Backup Exec can only monitor the write operations originating from the media server. If the network share is accessed from any other server, which does not have Backup Exec installed, write access is allowed.
This setting is enabled by default and is the recommended setting to protect your backup data. You can disable the setting by providing the System Logon Account credentials.
When the lockdown is in effect, the status displays Enabled.
The setting is disabled and the lockdown status displays Disabled. It is strongly recommended that you enable this setting to protect your disk-based storage. Any changes to the disk-based storage can only be done by Backup Exec.
If you disable the lockdown setting, the Send periodic alerts if the disk storage lockdown setting is disabled check box is selected so that you can receive periodic alerts. An alert is generated at 11 am every day until the lockdown setting is enabled again. By default, this check box is selected. You can clear the check box to stop the periodic alerts.
To enable the lockdown setting again, click Enable.
- Click OK.
If you selected the Allow only Kerberos authentication from the Remote Administration Console check box, a confirmation message is displayed.
- If you want to restart the Management Service, click Yes.