Backup Exec 21 Best Practices
- Backup Exec Best Practices
- Best practices for Backup Exec software encryption
- Best practices for Backup Exec installation
- Best practices for Backup Exec tape management
- Best practices for Backup Exec disk-based storage
- Best practices for Backup Exec data lifecycle management (DLM)
- Best practices for Backup Exec catalogs
- Best practices for Backup Exec backups
- Best practices for Backup Exec backing up critical system components
- Best practices for Backup Exec Agent for Microsoft Exchange Server
- Best practices for Backup Exec Agent for Microsoft SQL Server
- Best practices for Backup Exec Agent for Linux
- Best practices for Backup Exec Agent for Microsoft SharePoint
- Best practices for Backup Exec Central Admin Server Option
- Best practices for Backup Exec Agent for Oracle on Windows and Linux Servers
- Best practices for Backup Exec NDMP Option
- Best practices for Backup Exec reports
- Best practices for Backup Exec and Veritas Update
- Best practices for Backup Exec Simplified Disaster Recovery
- Best practices for Backup Exec Agent for Enterprise Vault and the Backup Exec Migrator
- Best practices for Backup Exec Granular Recovery Technology
- Best practices for Backup Exec Remote Media Agent for Linux
- Best practices for Backup Exec Agent for Microsoft Hyper-V
- Best practices for Backup Exec Agent for VMware
- Best practices for using Backup Exec with server clusters
- Best practices for Backup Exec Deduplication Option
- Best practices for using Backup Exec 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 database encryption keys
- Best Practices for Using the Backup Exec Cloud Connector
Best practices for Backup Exec Agent for Linux
Best practices include tips and recommendations to help you use Backup Exec Agent for Linux (Linux Agent) effectively. For more information about the Linux Agent, see the Backup Exec Administrator's Guide.
Use the Linux Agent to back up user data and configuration files. However, because of the lack of open file handling support, Veritas does not recommend the Linux Agent as a complete system for disaster recovery.
Select the Using modified time option for the backup method that you choose.
Disable file locking for backup jobs.
Exclude pipes and socks from backup jobs.
Add the same directories manually to the Backup Exec Exclude list if you have added directories to the autofs automounter utility. When you add these directories to the Exclude list, you can inadvertently avoid backing up data from sources such as CD-ROM drives.
Assign administrator permissions to the user or add the user in the beoper group, who backs up the computer.
For files and directories on a host that you do not want to back up, enter file and directory exclusion information in the
ralus.cfgfile. After you add the information, the file and the directories are ignored during backup.Run a small restore job periodically to test the validity of your storage media.
If you have gvfs mounted directories on your Linux server, unmount the directories before trying to browse selections for Linux backups or running actual backups. Linux agent does not support backing up or restoring to gvfs filesystems. If a gvfs mounted directory is present, backup browse actual backup does not work and gives an error.
Use a port number that is not in use by another application or service when you add a Linux agent in Backup Exec.
To change the port number, see the following URL: