Symantec Backup Exec 2010 R3 SP3 Readme
Last updated: June 17, 2013.
Copyright © 2013 Symantec Corporation. All rights reserved. Symantec, the Symantec Logo, and Backup Exec are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.
The Licensed Software and Documentation are deemed to be "commercial computer software" and "commercial computer software documentation" as defined in FAR Sections 12.212 and DFARS Section 227.7202.
This document contains release notes for Backup Exec and contains information that may not be in the Administrator's Guide. The information in this document is more current than the information in the Administrator's Guide. If the information in this file conflicts with the Administrator's Guide, the information in this file is correct.
For the most current information on Symantec Corporation products and services, please visit our website:
All hyperlinks in Symantec products and documentation lead to English-language websites.
This release of Backup Exec includes the following new features and capabilities:
For a list of what was new in Backup Exec 2010 R3 prior to SP3, refer to the topics "What's new in Backup Exec" and "What's new in Backup Exec agents and options" in the Symantec Backup Exec 2010 R3 Administrator's Guide.
Table: What's new in Backup Exec 2010 R3 SP3
Backup Exec 2010 R3 SP3 supports Windows Server 2012 with some limitations. You cannot install a Backup Exec server on a Windows Server 2012 computer. However, you can use the Agent for Windows to back up and restore Windows Server 2012 computers with their operating systems and legacy features. You cannot install the Remote Agent for Windows Systems on ReFS volumes or any volumes that have been enabled for deduplication in Windows.
The Agent for Hyper-V in Backup Exec 2010 R3 SP3 includes support for Windows Server 2012. You can perform a full back up and restore of Hyper-V virtual machines that use the VHDX file format. Granular Recovery Technology (GRT) is not supported for Hyper-V 2012 virtual machines that use the VHDX format, Windows 2012 Resilient File System (ReFS), and Windows 2012 deduplication volumes.
The Agent for VMware Virtual Infrastructure supports backups and restores of VMware vSphere/ESX/vCenter 5.1 and hardware version 9.
The Exchange Agent supports Microsoft Exchange Server 2010 SP3.
The SQL Agent supports the following:
Backup Exec no longer supports the following features:
Microsoft SQL Server 7.
Backup Exec does not support the backup and restore of SQL Server 7 databases. However, you can continue to back up and restore SQL Server 7 databases on remote computers by using the Backup Exec 12.5 for Windows Servers Remote Agent.
Microsoft SharePoint 2001.
Microsoft Exchange 2000.
Media server support for Windows 2000.
Media server support for Windows Small Business Server 2000.
Use of Microsoft SQL 2000 for the Backup Exec database repository.
Tivoli Storage Manager.
The Clone CD feature.
Cascaded drive pools.
On upgrade, cascaded drive pools are converted to device pools.
The Backup Exec for NetWare Agent push install.
HP-UX, AIX, SUSE Linux Enterprise Server 9, Novell Open Enterprise Server (OES) 1, and Red Hat Enterprise Linux 3 are no longer supported for backup by the Remote Agent for Linux or UNIX Servers.
SUSE Linux Enterprise Server 9 and Novell Open Enterprise Server (OES) 1 are no longer supported for backup by the Remote Media Agent for Linux Servers.
PowerPC is no longer supported by the Remote Agent for Macintosh Systems.
The split mirror alias backup option is no longer supported by the Command Line Applet. Symantec recommends that you use off-host backups instead.
The Backup Exec Archive Media set is no longer supported, and has been removed from the Imported Media node. All media in the Backup Exec Archive Media set have been moved to the Backup Exec and Windows NT Media set.
Symantec Protection Network (SPN)
The Backup Exec technical support knowledge base contains the information that pertains to this release of Backup Exec.
The Backup Exec knowledge base provides technical notes, how-to topics, best practices, links to instructional videos, troubleshooting articles, and other valuable information to help you use Backup Exec.
For more information, go to the following URL:
The hardware and software compatibility lists contain the latest information about supported and unsupported hardware and software and is updated regularly. Before you install or upgrade Backup Exec, review the current compatibility lists to confirm the compatibility of your hardware and software. You can find the current compatibility lists on the Symantec technical support Web site at:
If you don't find your hardware or software listed, or if you have questions about the information in the compatibility lists, please contact Symantec technical support.
The following notes provide information about installing Backup Exec:
After you install the service pack, you should update the Remote Agent for Windows Systems (Remote Agent) and the Remote Agent for Linux or UNIX Servers. Updating the agents ensures that you have the most recent versions and that you have proper support for the new features.
Backup Exec does not install the most recent patches for the Remote Agent when you push-install it to a computer that runs Windows Server Core or a Hyper-V Server. You can ensure that you have the most recent patches for the Remote Agent by updating it after you push-install it to a computer that runs Windows Server Core or a Hyper-V Server. To update the Remote Agent, run LiveUpdate on the media server and repeat the push-installation.
Refer to the topic "About installing Backup Exec options to remote computers" in the Symantec Backup Exec Administrator's Guide for more information.
When installing Backup Exec for Windows Servers on a Windows 2008 Server with a Small Business Server that is virtualized (SBS Premium), the virtual Small Business Server must be powered on in Hyper-V when entering the Small Business Server Serial Number. Failure to do so may result in the following error: "An Invalid license key has been entered. Please verify the key and try again."
For the Remote Agent for Linux or UNIX Servers, the Remote Agent for Macintosh Systems, and the Remote Media Agent for Linux Servers, you must unzip the RALUS_RMALS_RAMS_<revision number>.gz file on a Linux or UNIX server. The installation does not run if it is unzipped on a computer that runs the Windows operating system. After you unzip the file, you must untar it. For instructions, refer to the following topics in the Administrator's Guide:
You cannot install a Backup Exec media server on a computer running Microsoft Windows Vista or Windows 7.
Windows Resource Protection (WRP) prevents backup and restore jobs from functioning normally on computers that run Windows Vista. Although Backup Exec can complete backup and restore jobs, performance may suffer. Refer to the following Microsoft article for more information and to obtain a hotfix that resolves this issue:
Because WRP affects the Windows Installer, you should install the hotfix before you install Backup Exec agents or options on a computer that runs Windows Vista.
To push-install Backup Exec or its options to a computer that runs Windows Vista/Server 2008/Server 2012, you must enable File and Printer Sharing and Windows Management Instrumentation (WMI) on the Windows Firewall Exceptions list. If you install the Remote Agent for Windows Systems on a Windows Vista/Server 2008/Server 2012 computer, you can use an Active Directory installation or use the Backup Exec installation media to perform a local installation. If you use either of these installation methods, you do not need to enable File and Printer Sharing and Windows Management Instrumentation (WMI) on the Windows Firewall Exceptions list.
For more information, refer to your Microsoft Windows documentation.
To push-install Backup Exec or its options to a computer that runs Windows XP Pro SP2/Server 2003 SP1 or later, you must enable File and Printer Sharing on the Windows Firewall Exceptions list and enable the "Allow remote administration exception" group policy.
For more information, refer to your Microsoft Windows documentation.
To push-install Backup Exec or its options to Windows Vista/Server 2008/7/Server 2012 computers that do not belong to a domain, do one of the following:
Make sure that the Administrator account on the computer from which you push-install the agent or option is also defined on the destination computer
Disable User Access Control temporarily on the destination computer during the installation process
For more information, refer to your Microsoft Windows documentation.
If you install Backup Exec on a Veritas Cluster Server node that runs Microsoft Exchange, that node must be offline at the time of installation. If you keep Exchange online during installation, services do not start properly. If you want to use the SQL Express database that is included with Backup Exec, you must switch the Exchange group to another node or take it offline. Otherwise the installation of SQL Express cannot complete successfully.
If installation fails due to a SQL Express installation error, refer to the section about setup issues in the Microsoft SQL Server 2005 Express Edition readme:
An error (error code 2) may occur when you install SQL Express in an environment with the following conditions:
Active Directory is installed on a computer that runs Windows Server 2008.
The computer belongs to a root domain that uses a short domain name such as "first.com".
To avoid this error, install SQL Express to a child domain such as "second.first.com", or use an instance of SQL Server instead of SQL Express.
If the SQL Server 2005/2008 instance is on the same server that you install Backup Exec on, the service account for the instance must have full permissions to the destination folder where Backup Exec is installed.
If you install Storage Foundation for Windows Servers High Availability Administrative Console (SFWSHAAC) components on a central administration server, you must restart the central administration server after the installation completes.
If you perform a remote install or a push-install, and you specify a domain administrator account for the Backup Exec Services, you must enter an existing domain administrator account. New accounts are not granted proper rights for domains. If you specify a new local administrator account, the account will be granted proper rights when it is created.
When you install Backup Exec, or when you install tape device drivers from Backup Exec, a Microsoft message may appear that indicates one of the following:
The software that you are about to install does not contain a Microsoft digital signature.
Windows can't verify the publisher of this driver software.
The software has not passed Windows Logo testing.
Symantec recommends that you allow the Symantec driver software to continue being installed.
To prevent this message from appearing, you can change the policy setting. However, if you change the policy setting to "silently succeed", other driver software can be installed without any warning.
Refer to the following Microsoft article:
The user-created folders that are in the Backup Exec installation folder or subfolders are deleted when you uninstall Backup Exec. If you want to keep the folders, copy them to another location before you uninstall Backup Exec.
When you install Backup Exec on a computer that runs Windows Server 2008 R2, the default VMware SVGA II driver causes the computer to freeze. Before you install Backup Exec on a computer that runs Windows Server 2008 R2, do one of the following:
To use the Windows Explorer browser to install Backup Exec:
To uninstall the VMware SVGA II driver and use the Standard VGA Graphics Adapter instead:
The following notes detail general information about using Backup Exec:
Backup Exec System Recovery is now Symantec System Recovery. This product name change applies to all references of Backup Exec System Recovery in the Backup Exec Administrator's Guide. It also applies to the product documentation or the peripheral information that is included with Backup Exec 2010 R3.
Your support ID is listed in the confirmation email that Symantec sends you after you register Backup Exec. Please record this number as it is required should you need to contact Support.
Backup Exec has improved the response time for displaying restore selections in environments with large amounts of media. Because of this change, you can no longer perform catalog searches on individual media. The search will include all cataloged media.
If you run Windows 2003 Service Pack 1 or later or Windows XP Service Pack 2 or later, the following may occur:
Remote backups and restores may require manual configuration.
When the Remote Agent for Windows or NetWare Systems runs, it automatically creates an exclusion in the Microsoft firewall.
For more information, refer to the following TechNote:
Additional information can also be found on the Microsoft Web site.
You must install Symantec Endpoint Protection Manager (SEPM) on the media server to enable integration features between Backup Exec and SEPM. However, the ThreatCon-triggered backup feature does not require SEPM on the media server. Additionally, if Internet Explorer's Trusted sites security level is set to High, you must add the following URL as a trusted site on the Internet Explorer Security tab:
When you add the URL, you ensure proper functionality between SEPM and Backup Exec.
Backup Exec reserves port 3527. For instructions on how to configure Backup Exec to use a port other than 3527, refer to the following TechNote:
In Microsoft Windows Vista/Server 2008, the default locations of user data has changed. To ensure backward compatibility with previous Windows platforms, the operating systems create special junctions. These junctions redirect access from one directory to another. For example, %SystemDrive%\Documents and Settings is now a junction that points to %SystemDrive%\Users.
For more information about which directories have changed in Windows Vista/Server 2008, go to the following URL:
Backup Exec must be able to back up and restore these junctions but it does not need to traverse them to back up the computer.
Backup Exec version 11d and later detects the new junctions but does not cross them, even if you select the backup option titled Back up files and directories by following junction points.
If you upgrade your operating system to Windows Vista/Server 2008, examine existing selection lists. Change references to old directories to reflect the new directory structure to ensure that your data is backed up correctly.
Windows 2003 Service Pack 2 introduced a new update called Scalable Networking Pack (SNP). In newer network interface cards (NICs), this update utilizes a feature called either TCP/IP Offload Engine (TOE) or TCP Chimney. When TOE or TCP Chimney is enabled for certain NICs, there may be throughput or connectivity issues between the media server and the remote computers. If your Backup Exec configuration has performance or connectivity issues, and if the media server or a remote computer is using TOE or TCP Chimney, refer to the following TechNote:
To support character sets for languages that use UTF8 (NetApp filers) or Unicode Mode (EMC Celerra Servers), you must create or edit a registry key called UseUTF8. Refer to the following TechNote:
You can find detailed information about Backup Exec Microsoft Windows Server Certification status at the following link:
Using an unsupported version of the Adobe Acrobat Reader on Windows Server 2008 R2 can cause issues with Backup Exec. Ensure that you use the latest supported version of Adobe Acrobat Reader on Windows Server 2008 R2.
Backup Exec 2010 R3 SP3 supports Windows Server 2012 with some limitations. You cannot install a media server on a Windows Server 2012 computer. However, you can use the Remote Agent for Windows Systems (Remote Agent) to back up and restore Windows Server 2012 computers with their operating systems and features. You cannot install the Remote Agent on ReFS volumes or any volumes that have been enabled for deduplication in Windows.
The following are limitations of using Backup Exec with Windows Server 2012:
Backup Exec supports the backup of data on any volumes that have Windows deduplication enabled. If you try to back up data from a volume that has Windows deduplication enabled, Backup Exec backs it up in its original, non-deduplicated format. Ensure that you have enough storage space for the non-deduplicated data before you run a backup.
Backup Exec does not support backing up the Windows Server 2012 feature Windows to Go.
To back up a Windows Server 2012 recovery partition, you must assign a drive letter to it. If you attempt to back up a recovery partition without assigning a drive letter to it, you may not be able to restore the recovery partition later. Without the recovery partition, you may not be able to use certain Windows Server 2012 features.
Backup Exec supports the non-deduplicated restore of volumes that have Windows deduplication enabled. When you restore files from a volume that has Windows deduplication enabled, Backup Exec places the files on the disk as non-deduplicated. Ensure that you have enough disk space to restore the non-deduplicated data before you run a restore job.
The files are only subsequently deduplicated as appropriate when the normal Windows data deduplication process runs on the disk.
The Intelligent Disaster Recovery Option is not supported for Windows Server 2012.
However, you can restore the critical system components that are required to start the computer, and then you can use Backup Exec to restore the Windows Server 2012 features.
The Remote Administator is not supported for Windows Server 2012.
If you back up the System State of a Windows Server 2012 computer using a Windows 2003 media server, the backup completes successfully, but it is not enabled for Granular Recovery Technology (GRT). This behavior is the same as if you back up System State on a 64-bit Windows Server using a 32-bit media server.
Refer to the Agent for Microsoft Hyper-V notes section for more information about limitations to using the Agent for Hyper-V with Windows Server 2012.
The following notes provide backup information when you use Backup Exec:
When you protect a server that runs Veritas Cluster Server 4.3 by Symantec, and a virtual file share resource is manually failed over or taken offline while backup job preprocessing is in progress, the backup job stops responding.
When Windows Internet Name Service (WINS) is installed and the WINS data directory (%SystemRoot%\system32\wins) is backed up, non-snapshot backups result in a job status of "Completed with Exceptions". For Windows 2003, this job status is because the winstmp.mdb (temporary) file is in use. WINS is protected by the WINS VSS Writer via the Backup Exec Shadow Copy Components resource so the backup error is benign and you can ignore it.
When you run an off-host backup of Veritas Storage Foundation for Windows version 4.3 with Maintenance Packs 1 or 2 on a 64-bit computer, the error code V-79-57344-34110 appears.
To resolve this issue, update your Storage Foundation for Windows software.
Backup performance can be seriously degraded if you use LUN libraries that are attached to a computer that runs Windows Server 2008. Instead of a backup rate of hundreds of MB per minute, you could experience a backup rate of 3 to 4 MB per minute. To resolve this issue, set the AutoRun registry key that is associated with both the tape drive and the associated library to 0. For more information, go to the following link:
If you experience slow throughput when you back up remote disks, consider the following:
The backup speed for a remote disk is limited by the speed of the physical connection. The rate at which a remote server's hard disks are able to be backed up depends on the following items:
The make/model of network cards.
The mode/frame type configuration for the adapter.
The connectivity equipment (hubs, switches, routers, and so on).
The Windows settings.
Local disk drives on the media server can usually be backed up at a faster speed than backing up remote servers across a network. A common reason for slow network backups can be networking configuration.
Features such as full-duplex and auto-detect may not be fully supported in every environment. Manually set the speed to 100 MB and the duplex to half/full for the server side. On the switch, find out which Ethernet port the server is connected to and set the SWITCH PORT setting to 100 MB and half/full duplex. Do this for the backup server switch port, and any switch ports for computers that you back up.
Both the switch and the network interface card (NIC) must have matching settings. For example, if the switch port is set to 100 half, the NIC for the server should also be set to 100 half.
If a full duplex backup job is slower than the half duplex backup job, full duplex may not be supported for the combination of NIC, driver, and switch. Contact the NIC and switch manufacturer for updated drivers, firmware, or other support documentation.
The NIC driver is another common cause for slow throughput when you back up remote disks. The NIC driver can be easily overwritten by an operating system service pack. If a service pack has been applied and if the driver has been overwritten, reinstall the OEM driver.
If a backup job uses the "Back up and delete the files" full backup method, and if some files or directories are backed up but not deleted, Backup Exec does not correctly report the job status as "Completed With Exceptions". You should check the job log after the job completes.
If you select the full backup method named "Back up and delete the files", and if the clock on the remote computer is faster than the clock on the media server, then the file appears to have been modified after it was backed up. Therefore, the file is not deleted. You should either synchronize the clocks, or select older files for backup.
When you run a Duplicate existing backup sets job of OpenStorage backup sets that use optimized duplication or DirectCopy to tape backup sets, the media may not be copied to the destination in the correct order. To ensure that the media is copied in the correct order, use the View by Resource tab to select the sets that you want to copy.
Some Oracle backup jobs may fail with the error "This server name is not in the media server's authentication list. Enter the server's fully qualified domain name and logon account into the media server's authentication list. Server names in the authentication list are case-sensitive." This error occurs when the Backup Exec media server's Oracle modify list does not contain the fully qualified domain name of the Oracle server.
To resolve this issue, you must add the fully qualified domain name of the Oracle server to the Backup Exec Oracle modify list.
To add the fully qualified domain name of the Oracle server to the Backup Exec Oracle modify list
For example, <oracleservername.example.com>
The following notes provide restore information when you use Backup Exec:
When you browse remote restore selections, you may receive an informational message that the Backup Exec Remote Agent for Windows Systems must be installed. This message may appear even though the agent is installed. You can ignore this message. Click OK to continue.
For the Backup Exec Agents for Oracle, DB2, and the Backup Exec Migrator for Enterprise Vault, a restore of a resource is not supported if backups for the same resource are performed on Remote Media Agent devices as well as on devices that are attached to the local media server. For example, you cannot restore an Oracle database from a full backup that is on a backup-to-disk folder and from a backup of a single tablespace that is on a Remote Media Agent device.
The following notes detail information about using the Advanced Disk-based Backup Option with Backup Exec:
For information about using Hitachi VSS provider for the Advanced Disk-based Backup Option you can find the current hardware compatibility list at:
If you select the "Collect additional information for synthetic backup and true image restore" option for a backup job, remote resources that are included in the backup selections must be in the same time zone as the media server.
Offhost backup does not support volumes that run Windows Bitlocker Driver Encryption.
Off-host backup supports Exchange Agent backups for Microsoft Exchange Server 2010 on Windows Server 2008 with Service Pack 2 or later. Both the media server and the Exchange server must be running the same version with the same software patch level (including VSS patches). The devices must also be listed on the hardware compatibility list.
This section contains information about how the Agent for Hyper-V works with Windows Server 2012 and general notes for using the Agent for Hyper-V with any supported operating system in this release of Backup Exec.
The Backup Exec 2010 R3 SP3 Agent for Hyper-V lets you back up and restore Hyper-V virtual machines that are hosted on Microsoft Windows Server 2012. This version of Backup Exec supports the Windows Server 2012 VHDX file format.
Microsoft's new VHDX file format supports virtual disks that are up to 64 TB in size. Backup Exec supports backups and restores for VHDX-based virtual machines. Backup Exec processes the VHDX files similarly to how it processes VHD files. Granular Recovery Technology (GRT) is not supported at the application level or at the file/folder level for VHDX files. Backup jobs for virtual machines that use Windows Server 2012 and that are enabled for GRT will complete with a status of success with exceptions, but no GRT restore capability will be available. A full restore of the virtual machine will be available.
The following limitations apply to using the Agent for Hyper-V with Windows Server 2012:
Microsoft incremental backups are not supported.
Virtual machines that are configured with Fibre Channel HBAs are skipped during backup jobs. The job log lists a message to indicate that the virtual machine was skipped.
A virtual machine that was backed up from a Hyper-V 2012 host cannot be restored to a virtual machine with an earlier version of Hyper-V, such as 2008 or 2008 R2.
Hyper-V Replication virtual machine backups may result in redundant backups of the primary virtual machine and the replicated virtual machine.
A VSS Copy backup of a Windows 2012 Hyper-V virtual machine is not supported.
Remote VSS is not supported.
Application-level and file/folder-level GRT are not supported for virtual machines that are configured with Windows 2012 Resilient File System (ReFS). Backup jobs for virtual machines that are configured with Windows 2012 ReFS and are enabled for GRT will complete with a status of success with exceptions. File/folder-level GRT is supported for volumes that are configured with NTFS.
Application-level GRT and file/folder-level GRT are not supported for virtual machines that are configured with Windows 2012 deduplication volumes. Backup jobs for virtual machines that are configured with Windows 2012 deduplication volumes and are enabled for GRT will complete with a status of success with exceptions. File/folder-level GRT is supported for volumes that are configured with NTFS.
GRT is not supported for VHDX files.
Virtual machines that have storage spaces are not supported because Microsoft Hyper-V VSS is unable to take snapshots of virtual machines with storage spaces.
The following notes detail information about how to use the Agent for Hyper-V with any supported version of Microsoft Windows.
GRT is not supported for virtual machines that use dynamic disks, such as spanned, mirrored, striped, or RAID 5 disks.
You must assign shadow storage to each NTFS volume that exists on a virtual machine if the virtual machine uses the Windows 2008 operating system. Otherwise, the backup job fails.
The restore of a Hyper-V virtual machine that is created within a mount point fails if the mount point does not exist at the time of the restore. To avoid this issue, configure the virtual machine to use volume GUID paths with no mount points. To solve this issue, recreate the mount point path or restore the volume that contains the mount point before you restore the virtual machine.
GRT is no supported for backups to tape of an Exchange 2003 virtual machine that runs on a Hyper-V host that is installed as a server role on a Server Core installation of Windows Server 2008 or later. Baking up to a backup-to-disk folder is supported.
Backup Exec does not support virtual machines that have duplicate names.
During backup of a Hyper-V virtual machine that contains a ReFS volume, you may encounter the following message:
This version of Windows doesn't support the ReFS format on <drive x>.
This message does not affect the backup. Clickto dismiss the message. Note that file/folder-level GRT is not supporte for volumes that use ReFS.
The following information applies to virtual machines that use Windows Server 2012 and VMware ESX 5.1 or 5.0 with Backup Exec 2010 R3 SP3:
GPT disks are not supported.
File/folder-level Granular Recovery Technology (GRT) is not supported for volumes that use Windows 2012 Resilient File System (ReFS). Application-level GRT cannot be performed for the virtual machine that has a Windows 2012 ReFS volume. A backup job for a virtual machine that is configured with Windows 2012 ReFS and is enabled for GRT will complete with a status of success with exceptions.
File/folder-level Granular Recovery Technology (GRT) is not supported for volumes that have Windows 2012 deduplication enabled. Application-level GRT cannot be performed for the virtual machine that has Windows 2012 deduplication enabled. A backup job for a virtual machine that is configured with a Windows 2012 deduplication volume and is enabled for GRT will complete with a status of success with exceptions.
The following information applies to all Agent for VMware Virtual Infrastructure jobs, regardless of the platform used:
If a virtual machine name contains a backslash (\), the following issues occur:
VMware does not support non-standard English ASCII characters for host names, data store names, port names, CD ISO names, or other fields. If you use non-standard ASCII characters in these fields, it may result in failed backup and restore jobs.
Refer to the following article on the VMware knowledge base for more information:
The following information applies to ESX 4.0 environments:
To avoid issues with quiesced snapshots when you back up VMware virtual machines in an ESX 4.0 environment, Symantec recommends that you install the latest ESX 4.0 patch from VMware. The patch fixes problems related to the installation of VMware's VSS Snapshot Provider. See the VMware website for more information about ESX 4.0 patches.
The following notes apply to both the Exchange Mailbox Archiving Option and the File System Archiving Option:
When you install the Archiving Option, Backup Exec adds an entry to the hosts file. The entry in the hosts file points to the loopback address (127.0.0.1) of the system. The entry is for the EnterpriseVaultSiteAlias. In addition, when you install only the File System Archiving Option, Backup Exec adds another entry to the hosts file. The entry in the hosts file points to the loopback address (127.0.0.1) of the system. The second entry is BE-<machineName>-<hex timestamp>.<domainName>. Backup Exec adds the following comment to the hosts file:
Created by Backup Exec Archiving Option
These entries are required for the Archiving Option to function properly and should not be removed. Before Backup Exec modifies the host file, the Backup Exec installation saves a copy of the original hosts file as a file named hosts<date>_<time>.beao.bak.
For the Exchange Mailbox Archiving Option, the following notes apply:
Outlook must be installed as the default mail client on the media server to archive Exchange data.
The following versions of Microsoft Outlook are supported:
Outlook 2003 SP3
Outlook 2007 SP2 + hot fix
For the File System Archiving Option, the following notes apply:
If Windows Firewall is enabled, then you must enable the "Allow Remote Administration exception" setting in the Windows Firewall configuration settings.
The Backup Exec File System Archiving Option does not store the alternate data streams that may be included in archived files. By default, the Backup Exec File System Archiving Option also does not archive any files, other than Microsoft Office files, that contain an alternate data stream. The archiving operation skips such files. The following message is logged in the job log:
Skipping file data.txt. Files that contain alternate data streams are not archived.
Use the following steps to change this default behavior:
To change the default behavior of the Backup Exec File System Archiving Option
Change the value of the DWORD value ArchiveADSItems to 1 to allow the archiving of files that contain alternate data streams.
Change the value of the DWORD value ArchiveADSItems to 0 to allow the archiving of Microsoft Office files that contain alternate data streams.
The following notes detail information about using Backup Exec Retrieve with Backup Exec:
Backup Exec Retrieve is no longer installed via Continuous Protection Server. You can install Backup Exec Retrieve from the installation media.
The Backup Retrieve Web server requires ASP.NET and IIS. These components are not installed by default on Windows Server 2003/2008 and you may need to manually install them if they are not installed already. For information on how to install ASP.NET and IIS on Windows Server 2003/2008, refer to the Microsoft Web site.
On some operating systems, installing Backup Exec Retrieve on a server that has non-ANSI characters in its server name could prevent the Microsoft Silverlight application from launching Backup Exec Retrieve in the browser. If this occurs, you can do one of the following:
Give the server a static IP address and have users browse to the IP address to access Backup Exec Retrieve.
Rename the server on which Backup Exec Retrieve is installed so that multi-byte characters are not used.
In a domain, on the DNS server, give the server on which Backup Exec Retrieve is installed an alias that does not contain any multi-byte characters. Have users browse to the alias to access Backup Exec Retrieve.
The following notes detail information about using cluster-aware Backup Exec:
If a failover occurs during a backup that uses the Incremental - Changed Files - Reset Archive Bit backup method, Backup Exec skips the data that was backed up before the failover when the job is restarted on the failover node. In addition, catalog files are not generated for the data that was backed up before the failover.
To prevent possible loss of data in failover situations, Symantec recommends that you use the Incremental - Using modified time backup method instead of the Incremental - Changed Files - Reset Archive Bit method.
When you establish a trust relationship between the media server and a cluster, only the active node becomes a trusted source. Before you can back up the cluster, you must manually establish a trust relationship between the media server and all of the nodes in the cluster. To establish a trust relationship, add the remote agent to the Favorite Resources in the backup selections tree.
The following notes detail information about using the Deduplication Option with Backup Exec:
If you cannot configure your OST device with this release of Backup Exec, you may need to install a later version of your OST plug-in. Please contact your vendor to obtain the most recent plug-in for your device.
Deduplication requirements have changed and are as follows:
Ensure that the media server on which you create a deduplication storage folder has the appropriate amount of RAM. The minimum amount of RAM is 8 GB, which supports up to 5 TB of deduplicated data.
For more than 5 TB of data, use the following calculation to determine the required amount of RAM: 1.5 GB x N, where N equals the number of TB of storage in the deduplicated volume. Up to 32 TB of data is supported. Example: Use the following equation to calculate the required amount of RAM for 10 TB of data: 1.5 x 10 = 15 GB RAM
You must establish a trust relationship between the media server and a remote computer if you want to configure the remote computer to perform client-side deduplication.
The client-side deduplication feature is not supported in the following conditions:
You are using the Agent for VMware Virtual Infrastructure.
Your environment contains multi-server configurations of Microsoft SharePoint servers, Microsoft Exchange 2010 DAG servers, and Symantec Enterprise Vault servers.
You attempt to back up multiple servers in the same job.
If these conditions occur, the following message appears:
"You have chosen to use client-side deduplication to back up your selections. All resources selected for a backup job using client-side deduplication must come from the same server".
You can edit the selection list, or you can disable client-side deduplication for the job.
You cannot create a deduplication storage folder in a storage path that contains double-byte characters. The following error appears:
A deduplication storage folder could not be created in the given directory.
The ability to store a deduplication storage folder and its related database on separate volumes is no longer available. Backup Exec creates the database on the same volume as the deduplication storage folder. This applies to new deduplication storage folders that are created in Backup Exec 2010 R3 and later. If you stored the database in a separate volume in a previous release of Backup Exec, that configuration is preserved when you upgrade to Backup Exec 2010 R3.
The following notes detail information about using the Exchange Agent with Backup Exec:
On Windows Small Business Server 2003, the Microsoft Exchange Server 2003 VSS Writer is disabled, which causes snapshot backups for Exchange 2003 to fail. To successfully perform an Exchange 2003 snapshot backup, review the following Microsoft Knowledge Base article:
An incremental GRT-enabled backup of Exchange that targets a deduplication device is not recommended because the transaction logs contain primarily unique data that does not deduplicate well. For best results, create a policy that performs a full backup of Exchange to a deduplication device and performs incremental backups to a backup-to-disk folder.
Backup Exec determines the staging location for GRT-enabled backups of Exchange, and it may use a staging location other than the one that is configured in default backup options. However, this location does not affect the performance or the amount of available disk space.
The following notes detail information about using Intelligent Disaster (IDR) with Backup Exec:
Intelligent Disaster Recovery is not supported for Windows Server 2012.
On Windows 2000, to avoid issues when using IDR to recover dynamic disks that are managed by Veritas Volume Manager by Symantec or Microsoft's Logical Disk Manager, create a nonbootable IDR ISO image.
Do the following to create the image:
1. In the Intelligent Disaster Recovery Preparation wizard, select the option Create nonbootable disaster recovery CD image.
2. Burn the .ISO image to a CD.
3. Reinstall the operating system. Install Volume Manager if it was on the computer when the backup for IDR was created.
4. Run the IDR recovery application (bedrwiz.exe) from the System32\bkupexec\ directory on the CD.
5. Follow the prompts on the IDR Wizard to complete the recovery.
When you create IDR CDs and tape images for Windows 2000/XP/2003, you can also enter the path to an existing ISO image file for the operating system that you are protecting. This does not apply to IDR boot images for Windows Vista or later operating systems.
The IDR recovery process does not automatically recreate the volumes on dynamic disks in Windows 2000 operating systems. However, you can still manually convert the basic disks to dynamic disks and create the dynamic volumes by using the Disk Management console application in IDR.
Tapes that were created with non-Symantec drivers using block sizes that are greater than 64 KB cannot be used with the Backup Exec Intelligent Disaster Recovery Option. In this case, you must perform a manual recovery of the system, install the device driver that was used to perform the backup, reinstall Backup Exec, and then recover the system.
If the SQL database that is used for Backup Exec resides on a remote SQL server, then the system database files that are used by IDR also reside on the remote SQL server. When you perform a full IDR backup, you must include IDR files such as master$4idr, Model$4idr, and MSDB$4idr from the remote SQL server. Otherwise, the files are not available for recovery. You must also back up the bedb.bak file to restore your Backup Exec database.
The IDR process on a cluster node does not restore the quorum data to the quorum drive. To restore the quorum data, run clrest.exe from the command line. This command moves the data from the default location to the quorum drive. The clrest.exe utility is in the Backup Exec installation directory. Use the following format:
clrest [-f] path [drive letter]
If you use Windows 2000 and you recover data from USB-based backup-to-disk devices, such as Iomega REV devices, you must provide the Windows 2000 service pack 4 integrated CD when you create the IDR CDs.
If you use the Copy option in the IDR Preparation Wizard, you can copy the *.dr file to a writable drive.
During automated remote IDR, if the encryption key for an encrypted backup set that you want to restore is not found on the media server, a temporary encryption key is created. You are prompted to provide a pass phrase for this key. The temporary encryption key is removed from the media server after the IDR wizard quits.
When you run an automated recovery of a computer that runs Windows Vista and that spans a volume across two identical hard drives, an error occurs. IDR cannot create the required partitions during the recovery process. You can manually create the partitions and assign drive letters by using Disk Management when the IDR Recovery Wizard prompts you.
If you use IDR to prepare for the recovery of a media server, do not select a deduplication storage folder on the local media server in which to store the backup sets and disaster recovery (*.dr) files. If you use IDR to recover a media server, the Intelligent Disaster Recovery Wizard cannot restore data from a local deduplication storage folder. In order to use a deduplication storage folder to protect a local media server, a remote media server must be used to prepare for the recovery of the local media server.
If you use IDR to recover a media server that contains a deduplication storage folder, any existing backup sets that were sent to the deduplication storage folder after it was backed up cannot be restored.
If you use IDR to recover a media server that contains a deduplication storage folder, the deduplication storage folder may not be in an operational state after the recovery.
To recover the deduplication storage folder, manually remove any pre-existing deduplication storage folder data before you start the recovery of the media server.
IDR will not recover a deduplication storage folder. Refer to the Administrator's Guide for more information.
Before you can use IDR to restore a remote computer that was backed up using client-side deduplication, you must delete the Remote Agent for Deduplication. The remote agent appears in theview on the media server. You must then restart the Backup Exec services.
The following notes detail information about using the NDMP Option with Backup Exec:
You must restart Backup Exec services on both the primary server and the secondary server if you use the Shared Storage Option and add an NDMP device from a secondary server. Also, you must refresh the devices list manually on all other secondary servers.
You must have the same buffer size for a duplicate backup sets job or a restore job as you have for the backup job to prevent the job from failing.
The following notes detail information about using the Remote Agent for Linux or UNIX Servers (Remote Agent) with Backup Exec:
On any Linux computer on which the GNOME Virtual File System (GVFS) is installed and mounted, the GVFS cannot be browsed, backed up, or restored to.
On computers on which GVFS is installed, the .gvfs mount point is created for every user who logs on via 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.
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:
This defect prevents the Backup Exec Remote Agent from running on the GVFS. Therefore, the GVFS cannot be browsed, backed up, or restored to. Other file systems on Linux computers on which GVFS is installed are also inaccessible.
Additionally, on Linux 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:
SMBFS (commonly known as Samba)
Common Internet File System (CIFS)
Network File System (NFS)
As a resolution, try dismounting the GVFS, and retry the operation.
The Remote Agent installer supports the Traditional Chinese locale setting (EUC, big5 encodings) only on Linux platforms. On all other platforms, the Remote Agent installer displays the Traditional Chinese locale setting in English.
On an Asianux server, files that are mounted on a Network File System (NFS) may not be backed up if the option "Lock remote files" is enabled on the Linux, Unix, and Macintosh dialog box. This option is enabled by default. To work around this issue, do the following:
1. On the Backup Job Properties dialog box, under Settings, click Linux, Unix, and Macintosh.
2. Ensure that the option Lock remote files is unchecked before you back up files on an Asianux server.
If you stop the Remote Agent for Linux or UNIX Server daemon on a Solaris 9 or 10 operating system for SPARC platforms or on a Solaris 10 platform on Intel processors, it may take up to 40 seconds before the daemon stops.
Do not use the push-install operation to install the Remote Agent for Linux or UNIX Servers on a computer that runs the Solaris operating system. The Remote Agent for Linux or UNIX Servers daemon cannot be started.
The following error message appears:
Starting Symantec Backup Exec Remote Agent:FAILED
If you already push-installed the Remote Agent for Linux or UNIX Servers to a Solaris computer and you received this message, you must uninstall the Remote Agent. Then, insert the Backup Exec installation media into the appropriate drive on the computer. Start the installation for the Remote Agent for Linux or UNIX Servers.
Refer to the Administrator's Guide for more information.
On computers that run a supported version of the Asianux operating system, Backup Exec may occasionally report the that logon account used for backup or restore operations may not be part of the Backup Operators Group (beoper). Sometimes the /etc/group file may not correctly be 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.
The following notes detail information about using the Remote Media Agent for Linux Servers with Backup Exec:
You cannot run fast cataloging of tapes that have become unappendable. Backup Exec automatically reverts to slow cataloging. The following message is written in the catalog job's job log:
"An error was encountered while attempting to read the Media Based Catalog's Set Map data. Attempting to catalog the media by reading the data area of each backup set."
This problem occurs because an incomplete on-tape catalog is written to the tape at the end of a backup job. As a result, subsequent backup jobs cannot find the tape's set map, and flag the tape as unreadable.
The following notes detail information about using the Remote Agent for Windows Systems with Backup Exec:
When you push-install the Remote Agent to a computer that runs Windows Server Core, you cannot browse the backup selections in Backup Exec. The problem is caused because Backup Exec does not install the most recent patches for the Remote Agent when you push-install it to a computer that runs Windows Server Core. You can ensure that you have the most recent patches for the Remote Agent by updating it after you push-install it to a computer that runs Windows Server Core.
Refer to the topic "About installing Backup Exec options to remote computers" in the Symantec Backup Exec Administrator's Guide for more information.
If you attempt to push install the Remote Agent to a computer running Windows 7, you may be required to start the Remote Registry Service before the install.
See the following link for instructions on starting the Remote Registry Service:
When you restore the Windows Vista System State, Backup Exec may create the following temporary directory on the Windows Vista computer:
After the restore job finishes, you can delete the directory.
When you uninstall the Backup Exec Remote Agent, you may encounter a message that presents a list of applications that you should close before you continue the uninstall process. If the list contains only the following, you can ignore the message and continue the uninstall process.
Backup Exec Setup Launcher
Backup Exec Log Server
Backup Exec Remote Agent for Windows Systems
If additional applications appear, close all applications except the ones that are listed above before you continue with the uninstall process.
If you have SEP installed on a remote server, the remote server may block the network ports that CPS uses. To install CPS remotely or to run a CPS backup job, you must enable the CPS network ports in the SEP firewall rules. For more information about which ports to enable, refer to the Symantec Backup Exec Continuous Protection Server Administrator's Guide.
The following notes detail information about using Backup Exec Utility (BEutility.exe) with Backup Exec. You should use Backup Exec Utility with the assistance of Symantec technical support.
Do not place Backup Exec cluster nodes in the same Media Server Group as the virtual Backup Exec server. If a function runs on a Media Server Group that contains cluster nodes and contains the virtual Backup Exec server, Backup Exec Utility has problems when it tries to modify the virtual Backup Exec server.
The operation Move Primary SAN SSO Server moves all SAN SSO secondary servers to a new primary SAN SSO server. The operation then changes the previous primary server to a secondary server of the new primary server. This operation does not support moving a primary SAN SSO server that has a remote user-defined instance. The BKUPEXEC instance cannot be installed locally on the primary SAN SSO server. In this situation, to move all of the secondary servers to a new primary server, you must do the following:
To move all of the secondary server to a new primary server
The Move Central Administration Server operation moves all managed media servers of the current central administration server to a new central administration server. The operation also changes the current central administration server to a managed media server that belongs to the new central administration server. However, if the new central administration server is also a SAN SSO primary server, then the current central administration server is changed to a SAN SSO secondary server of the new SAN SSO primary server.
This operation does not support moving a central administration server that is also a SAN SSO primary sever if it has a remote user-defined instance. The BKUPEXEC instance cannot be installed locally on the primary SAN SSO server.
In this situation, you must use the Backup Exec Utility operation Remove Primary SAN SSO Server and do the following:
To use the Backup Exec Utility Remove Primary SAN SSO Server operation
The following notes detail information about using the License Assessment Tool with Backup Exec:
Running the License Assessment Tool does not ensure license compliance. For more information about licenses, contact your reseller or go to the following URL:
License key scans for time periods and date ranges do not apply to the Backup Exec Archiving Option. Only the resources that are backed up by Remote Agents are scanned if you select a time period or date range for scans.
The License Assessment Tool does not support license key scans for some Backup Exec options. These options may be displayed in the license key scan report, but the number of license keys that are used for each option is not included.
The following items are not supported for license key scans:
Desktop and Laptop Option
Central Admin Server Option
Advanced Disk-based Backup Option
SAN Shared Storage Option
Intelligent Disaster Recovery for NetWare Servers
Open File Option for NetWare Servers
Symantec LiveState Recovery
Backup Exec Continuous Protection Server
Backup Exec instances in a cluster
Backup Exec System Recovery 2010 for Linux
The license count for the Remote Agent for Linux or UNIX Servers may be inconsistent when the following occurs:
The Remote Media Agent for Linux Servers is installed on a remote computer.
The remote Linux computer is backed up to a backup-to-disk folder, a simulated tape library, or a tape device.
You should ignore the license counts for the Remote Agent for Linux or UNIX Servers that appear on the computers on which you have installed a license for the Remote Media Agent for Linux Servers.
The following notes detail information about using the Command Line Applet.
The Command Line Applet does not support backing up the following Enterprise Vault components:
Any Enterprise Vault entities that are under the Enterprise Vault site. These components include index locations, vault store groups, vault stores, open or closed partitions, Fingerprint databases, and vault store databases.
Compliance and Discovery Accelerator databases. These databases include Configuration, Customer, and Custodian databases.