Backup Exec 20.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
- Backups
- Backing up data
- Restores
- How Backup Exec catalogs work
- Job management and monitoring
- 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
- 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
- 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
- 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
- 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 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
Installing the Remote Media Agent for Linux
You can install Remote Media Agent for Linux on a local Linux server or push-install it to one or more remote Linux servers.
See About installing the Remote Media Agent for Linux.
Note:
You must unzip the RALUS_RMALS_<version number>.gz file on a Linux server. The installation does not run if it is unzipped on a computer that runs the Windows operating system.
To install the Remote Media Agent for Linux
- At a Linux server, place the Backup Exec installation media in the appropriate drive.
- Log on as root on the server on which you want to install the Remote Media Agent for Linux.
- Navigate to the following path on the installation media:
<Linux>
- Copy the RALUS_RMALS_<version number>.gz file in this directory to a directory on the local server.
- Unzip the file.
For example:
gunzip RALUS_RMALS_<version number>.gz
- Untar the file.
For example:
tar -xf RALUS_RMALS_<version number>.tar
- Start the installrmal script.
For example:
./installrmal
- Do one of the following:
To install on a local server
Press Enter.
To install to one remote server
Type the name, IP address, or fully qualified domain name of a Linux server.
To install to multiple remote servers
Type the names, IP addresses, or fully qualified domain names of the Linux servers. Leave a space between each identifier.
- After the installer checks for a valid Linux operating system during the initial system check, press Enter.
- Review the package installation summary, and then press Enter.
- After the system installation requirements check completes, press Enter.
- Start the prerequisites check by pressing Enter.
- Type the name, IP address, or fully qualified domain name of the Backup Exec server (directory host) that you want to use this Remote Media Agent.
- Type any names, IP addresses, or fully qualified domain names of additional Backup Exec servers that you want to use this Remote Media Agent.
- Do one of the following:
If the server name, IP address, or fully qualified domain name is correct
Press Enter to continue the installation.
If you want to change a server name, IP address, or fully qualified domain name
Type N, press Enter, and then change the information.
- Start the NIS server scan by pressing Enter.
- Examine the results of the NIS server scan, and then do one of the following:
If an NIS server is detected
The Remote Media Agent for Linux installer cannot create the beoper group. You must create it manually after the Remote Media Agent for Linux installation is complete.
Continue with the next step.
If an NIS server is not detected
Use the installer to create the beoper group.
Do the following in the order listed:
To let the installer create the beoper group, type y.
To select the next available Group ID, type n.
To add the root user account to the beoper group, type y.
Continue with the next step.
- Start the installation by pressing Enter.
- After installation completes, press Enter to start the post-installation configurations and installation of SymSnap drivers.
- Press Y to automatically start the Beremote service; otherwise, press N to start the service later.
- After the configuration process completes, press Enter to save the installation log to the following file:
/var/tmp/vxif/installrmalsummary file number/installrmal.log
- If the RMAL installer did not create a beoper group, you must create it.
See Creating the Backup Exec operators (beoper) group manually for the Remote Media Agent for Linux.
- Start the Agent for Linux daemon.
- Add the Linux server as a Remote Media Agent.
See About adding a Linux server as a Remote Media Agent for Linux .