Backup Exec 25 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)
- About updates to Backup Exec using Arctera Update
- Backup Exec license contract information
- About upgrading to Backup Exec
- Getting Started
- Configuring the Home tab
- Backups
- Recommendations for when to use virtual-based backup and agent-based backup
- Backing up data
- Restores
- 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
- Cloud deduplication storage device
- Requirements for configuring a cloud deduplication storage device
- About the Backup Exec™ CloudConnect Optimizer
- Generic S3 Configurator
- OpenStorage devices
- Microsoft 365
- OneDrive plugin: Performance and throttling configuration
- Exchange plugin: Performance and throttling configuration
- SharePoint plugin: Performance and throttling configuration
- Teams plugin: Performance and throttling configuration
- 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
- Configuring role-based access settings
- Configuring parallel streams and job settings for Microsoft 365
- Changing network and security options for Backup Exec
- 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
- 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
- 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
- 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
- About SQL Server Always On availability groups
- 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 File Servers
- Appendix O. Backup Exec Agent for Linux and Unix
- About installing the Agent for Linux and Unix
- About establishing trust for a remote Linux and Unix computer in the Backup Exec list of servers
- Editing configuration options for Linux and Unix computers
- About backing up a Linux and Unix computer by using the Agent for Linux and Unix
- About restoring data to Linux and Unix computers
- Editing the default backup job options for Linux and Unix computers
- Uninstalling the Agent for Linux and Unix
Troubleshooting the Agent for Linux and Unix
If you experience problems with the Agent for Linux and Unix (Linux and Unix Agent) review the following questions and answers.
See About the Agent for Linux and Unix.
Table: Troubleshooting the Linux and Unix Agent
Question | Answer |
---|---|
Some characters do not appear correctly in the terminal session during the installation. What should I do? | This error occurs when the system location uses a non-English language character-set on the computer on which you install the Linux and Unix Agent. You can switch to another location setting of the same language to try to resolve this issue. |
The Linux and Unix Agent installer is unable to install the Linux and Unix Agent. The following error is reported in the installralus log file. What should I do? VxIF::Error:: Unable to compress files. Hash(0x8711e8)->({GUNZIP} not found on <hostname> | To support the uncompressing of the Linux and Unix Agent platform-specific packages, you can install the GNU data compression utility. Install this utility on the computer on which you want to install the Linux and Unix Agent. The utility is available at the following URL: |
The Agent for Linux and Unix is installed on a Linux and Unix server in an NIS domain. Backup Exec is unable to browse resources on the server. What should I do? | Verify if the group line and the password line in the nsswitch.conf file are set to compatibility mode. If they are, then you must configure the /etc/passwd and /etc/group files. Refer to the nsswitch.conf man pages for additional information on how to configure the nsswitch.conf to use compatibility mode. Alternatively, change the password line and the group line to NIS files so that the Linux and Unix server validates the user through NIS. If the NIS server is unavailable or if the user is not found, the local files are used for validation. |
I cannot load the Linux and Unix Agent. When I attempt to load the Linux and Unix Agent in console mode, /beremote --log-console shows the following message: ACE_SV_Semaphore_Complex: no space left on device. What should I do? | This issue occurs when the computer reaches its maximum limit on allowable semaphores. It can occur after an unexpected termination of the Linux and Unix Agent. When the Linux and Unix Agent unexpectedly terminates, it is unable to clean up some of the semaphore resources that it used. Other processes may have caused the use of semaphores to reach the limit. You must restart the computer to safely recover it from this condition. If other processes are running, it may not be feasible to restart the computer. Instead, you can use the commands that let you list and then remove all semaphores that are in use by the operating system. Be careful when you select semaphores to remove. Semaphores that are in use by the Linux and Unix Agent cannot be identified. If you remove semaphores of other programs that are in use, those programs can become unstable. To list semaphores, you can type the following command: ipcs -a To remove semaphores for each identifier that is listed, you can type the following command: ipcrm -s <id> |
I cannot load the Linux and Unix Agent. When I attempt to load the Linux and Unix Agent in console mode, /beremote --log-console shows the following message: Error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory. What should I do? | This error indicates that the libstdc++.so.5 library is not in the /usr/lib directory. This library is necessary to let the Linux and Unix Agent start and function. To resolve this issue, install the libstdc++5 package. You can install this package from the media on which your copy of Linux was provided. Or, you can run the following command from a computer that has Internet access: apt-get install libstdc++5 For SUSE Linux Enterprise Server 11, run the following command: zypper install libstdc++5 |
On an Asianux operating system, Backup Exec displays an error that the Exec logon account for backup and restore options is not a part of the beoper group. What should I do? | Sometimes the /etc/group file is not correctly updated when a user is added to the beoper group. This leads to a failure of the getgrnam() Linux API. As a workaround, you should manually edit the /etc/group file and add the specific POSIX user name for the logon account in question to the beoper group. For more information on editing the /etc/group file, see the Asianux operating system documentation. |
On any Linux and Unix computer on which the GNOME Virtual File System (GVFS) is installed and mounted, the GVFS cannot be browsed, backed up, or restored to. What should I do? | On computers on which GVFS is installed, the .gvfs mount point is created for every user who logs on using the GNOME user interface. The mount point is created in the user's home directory. For example, if the user's logon name is John, then the directory appears as the following: Echo $>ls - la /home/John dr-x------ 2 John John 0 2009-06-16 18:16 .gvfs The output of the mount command appears as the following: "gvfs-fuse-daemon on /home/John/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=John)". This mount point is created when the user logs on using the GNOME graphical user interface. The mount point is deleted when the user logs off. Note: : Logging on by using SSH or telnet does not show the mount point. A defect has been reported for the GVFS that even the superuser (root) does not have access to the file system. Refer to the following URL for more information: http://bugzilla.gnome.org/show_bug.cgi?id=560658 This defect prevents the Agent for Linux and Unix from running on the GVFS. Therefore, the GVFS cannot be browsed, backed up, or restored to. Other file systems on Linux and Unix computers on which GVFS is installed are also inaccessible. Additionally, on Linux and Unix computers on which GVFS is installed and mounted on the home folder of a particular user, browse operations, and backup and restore operations on or to the following file systems may fail:
As a resolution, try dismounting the GVFS, and retry the operation. |
The Agent for Linux and Unix installer does not install the Perl Switch.pm module on 64 bit Ubuntu 14.04. What should I do? | Using the following steps, you must manually install Switch.pm before you attempt to install the Backup Exec Agent for Windows.
For Ubuntu 14.04, you must enable manual logins and add a root user using the following steps:
|