Problem
Requirements for backing up remote Windows Machines with Backup Exec.
Solution
To be able to fully protect and support the backup and restore of remote Windows Machines, the Remote Agent for Windows Servers (RAWS) software must be installed on these machines (Servers, Cluster Nodes, SQL server, Exchange server, SharePoint server, etc.). Additionally, an activated license or trialware evaluation on the Backup Exec media server. During the Trialware Evaluation of Backup Exec, an unlimited number of remote machines can be backed up or restored. Once the core server licensing has been entered, a license must be entered on the media server to prevent the Remote Agents from being deactivated on the media server for each of these remote servers.
To protect remote servers that include resources such as Exchange or SQL the Remote Agent software is installed on the servers only. The ability to Backup Exchange or SQL resources is enabled\activated by entering the Application and Database license on the Backup Exec media server or enter a license that includes the Application and database features for Example.
Note: Fully protect means to be able to run a full backup of the entire machine that can be restored later (disaster recovery) if the machine crashes (i.e.: hardware failure, natural disaster), gets infected with a virus, etc.
It is possible, however, to backup and restore both Windows and non-Windows Operating System files via "User Shares" even when a Remote agent is not installed on them or can't be installed.
A Backup Exec license that enables remote server backups is required for each host that owns shares that are subject to backup operations.
The option "Enable selection of user shares" has to be enabled under Configuration and Settings | Backup Exec Settings | Network and Security within the Backup Exec Console to perform such a backup of User Shares.
Though this type of backup or restore of just files may be possible, backup or restore of Default Administrative Shares, Active Directory (System State), complete disaster recovery, etc... will not be possible.
The backup of User Shares selection is specifically designed for Servers\Devices for which Backup Exec does not have an agent. For example, SNAP Servers or NAS (Network Attached Storage) Boxes with an operating system that emulates Windows and a Remote Agent cannot be installed on, and those which are not supported by the Backup Exec NDMP Option.
Incremental and Differential backups via shares are not supported as change journalling and / or archive bit resets can fail against share level operations, resulting in unexpected quantities of data being backed up.
User Shares backup or restore of Windows Servers which do not have the Remote Agent installed are not supported and are classified as an Alternative Configuration. Only partial or limited support will be provided for the backup or restore of shares on non-Windows Machines, because an agent cannot be installed to enable all of the functionality and features the Backup Exec Product has available.
NOTE: The definition of Alternative Configuration (which can also be found in our compatibility lists) is:
Our Licensed Software is designed to interoperate with many types of systems, applications, and hardware. Sometimes a customer may choose to use our Licensed Software in an "Alternative Configuration", namely, an environment that has not been validated, approved, or verified to operate with our Licensed Software or which does not support such Licensed Software or only supports limited functionality. Veritas does not support Alternative Configurations, and we have no obligation to provide Support Services to Licensed Software in an Alternative Configuration. Veritas makes no warranty with respect to use of Licensed Software in an Alternative Configuration and any such use is at your own risk. A "Supported Configuration"
might be converted into an Alternative Configuration where a vendor modifies one of its components that is part of the original Supported Configuration. As a consequence, your Licensed Software would then be operating in an Alternative Configuration. If you experience a problem with the Licensed Software in an Alternative Configuration or if your issue deals with script that was not developed by Veritas or an authorized consulting partner, then we may ask you to reproduce the problem in a Supported Configuration environment. Please note we have no obligation to attempt to resolve problems that cannot be replicated in a Supported Configuration. However, if the problem can be replicated in a Supported Configuration, we will investigate the problem in that Supported Configuration and attempt to resolve it. If the problem cannot be replicated in a Supported Configuration, then Veritas has no obligation to investigate or attempt to resolve the problem.
Was this content helpful?
Translated Content
Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been made to the original version after this document was translated and published. Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of this knowledge base article for up-to-date information.