Backup Exec 16 Best Practices
- Backup Exec 16 Best Practices
- Best practices for Backup Exec 16 software encryption
- Best practices for Backup Exec 16 installation
- Best practices for Backup Exec 16 tape management
- Best practices for Backup Exec 16 disk-based storage
- Best practices for Backup Exec 16 data lifecycle management (DLM)
- Best practices for Backup Exec 16 catalogs
- Best practices for Backup Exec 16 backups
- Best practices for Backup Exec 16 backing up critical system components
- Best practices for Backup Exec 16 Agent for Microsoft Exchange Server
- Best practices for Backup Exec 16 Agent for Microsoft SQL Server
- Best practices for Backup Exec 16 Agent for Linux
- Best practices for Backup Exec 16 Agent for Microsoft SharePoint
- Best practices for Backup Exec 16 Central Admin Server Option
- Best practices for Backup Exec Agent for Oracle on Windows and Linux Servers
- Best practices for Backup Exec 16 NDMP Option
- Best practices for Backup Exec 16 reports
- Best practices for Backup Exec 16 and LiveUpdate
- Best practices for Backup Exec 16 Simplified Disaster Recovery
- Best practices for Backup Exec 16 Agent for Enterprise Vault and the Backup Exec Migrator
- Best practices for Backup Exec 16 Granular Recovery Technology
- Best practices for Backup Exec 16 Remote Media Agent for Linux
- Best practices for Backup Exec 16 Agent for Microsoft Hyper-V
- Best practices for Backup Exec 16 Agent for VMware
- Best practices for Backup Exec 16 Storage Provisioning Option
- Best practices for using Backup Exec 16 with server clusters
- Best practices for Backup Exec 16 Deduplication Option
- Best practices for using Backup Exec 16 Deduplication Option with the Central Admin Server Option
- Best practices for using hot-pluggable devices such as USB devices in a drive rotation strategy
- Best practices for Backup Exec 16 database encryption keys
- Best Practices for Using the Veritas Backup Exec Cloud Connector
Best practices for Backup Exec 16 Remote Media Agent for Linux
Best practices include tips and recommendations to help you use Veritas Backup Exec Remote Media Agent for Linux (RMAL) effectively. For more information about the RMAL, see the Backup Exec Administrator's Guide.
Ensure that the storage device that is attached to the Linux server is supported. Also, confirm that the operating system can access the device before you start the RMAL.
You can find a list of compatible devices at the following URL:
Ensure that a minimum of 500 MB of available storage space exists on the Linux server when you use the Tape Library Simulator Utility. The available space includes hard disk space, flash drives, and USB drives. If there is not enough space, the jobs fail with an end-of-media error. You must either create available disk space or you must direct the jobs to another volume, and then start the jobs again.
Add an RMAL from the central administration server if you use the Backup Exec Central Admin Server Option (CASO). You cannot add an RMAL from a managed Backup Exec server.
If you use the Shared Storage option when you add a RMAL, use the Linux server's hostname and not its IP address. If you use the IP address, the Backup Exec Database cannot distinguish which device path to use for jobs.
Only Microsoft Tape Format media are supported if you use an RMAL to restore data from the tapes that other applications create. Backup Exec does not support GRT-enabled backup and restore jobs targeted to an RMAL device.