Symantec Backup Exec™ 2010 Readme

Last Updated: December 2, 2009

Copyright © 2009 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 information in the Administrator's Guide. If information in this document conflicts with the Administrator's Guide, the information in this document is correct.

For the most current information on Symantec Corporation products and services, please visit our Web site at http://www.symantec.com/.

Contents

What's new in Backup Exec 2010

What's new In Backup Exec 2010 agents and options

Where to find more information

Backup Exec installation notes

General Backup Exec notes

Cluster-aware Backup Exec notes

Backup Exec License Assessment Tool notes

Backup Exec agents and options notes

Exchange Agent notes

 Central Administration Server Option (CASO) notes

Archiving Option notes

Backup Exec Retrieve notes

Desktop and Laptop Option notes

Remote Agent for Linux or UNIX Servers notes

Remote Media Agent for Linux Servers notes

Advanced Open File Option (AOFO) notes

Advanced Disk-based Backup Option notes

Remote Agent for Windows Systems notes

Using Backup Exec and CPS with Symantec Endpoint Protection (SEP)

Agent for Microsoft Hyper-V notes

Agent for VMware Virtual Infrastructure notes

NDMP Option notes

Deduplication Option notes

Intelligent Disaster Recovery (IDR) Option notes

Backup Exec Utility (BEutility.exe) notes

Command Line Applet notes

 

What's new in Backup Exec 2010

This release of Backup Exec includes the following new features and capabilities:

Support for Microsoft Windows Server 2008 R2

Lets you do the following:

Support for the Server Core installation option of Windows Server 2008 R2

Lets you install the Backup Exec Remote Agent for Windows Systems on the Server Core installation for backup and restore operations. The Remote Agent also installs the Remote Agent Utility Command Line Applet. This applet lets you monitor Backup Exec operations on the remote computer.

Support for Microsoft Windows 7

Lets you install the Backup Exec Remote Agent on Microsoft Windows 7 computers for backup and restore operations. The Backup Exec Desktop and Laptop Option provides automated file protection for Windows 7 computers. Backup Exec also supports BitLocker drive encryption.

Enhanced Backup Exec License Assessment Tool

Supports the license key scans on all installations of Backup Exec and Backup Exec System Recovery on your network.

The License Assessment Tool report now provides the following information:

Support for new platforms for the Remote Agent for Linux or UNIX Servers

Supports the following platforms:

Support for a new platform for the Remote Media Agent for Linux

Supports SUSE Linux Enterprise 11.

Enhancement for Library Expansion Option

Supports each additional drive that you add after the first drive in each robotic library. When you install Backup Exec, support for the first drive in every robotic library is included.

Home view on the Backup Exec Administration Console

Lets you add or delete Web parts to customize the display of your important Backup Exec features. In one view, you can display summaries of jobs, alerts, and devices, and the technical support sites that you want fast access to. You can add as many or as few items as you want.

Share Your Ideas web link

Lets you suggest new ideas for Symantec Backup Exec by clicking this link that is located at the top of the Backup Exec Administration Console. After you have submitted your suggestions, other community members can vote or comment on the idea. The ideas with the most votes move to the top of the list. Symantec product managers review these ideas for possible features in future releases. You can click this link to find out if the feature is implemented.

Installation DVD

Provides all of the Backup Exec installation files on a single DVD.

DirectCopy

Enables Backup Exec to copy data from a virtual device directly to a physical device. The Backup Exec media server records information about the data in the catalog. Because the information about the copied data is in the catalog, you can restore data from either the virtual device or the physical device.

Verify backup sets template

Lets you run verify operations independent of backup and duplicate backup jobs. The verify backup sets template lets you schedule a verify operation to run at any time after a backup. For example, you can schedule the verify operation to run outside of your backup window if your network resources are scarce. The verify backup sets template also greatly enhances the benefits you receive from Backup Exec's Deduplication Option by letting you verify backup sets locally.

Backup Exec includes an example policy that is preconfigured with a verify backup sets template.

Backup Exec Continuous Protection Server

Supports Microsoft Windows 7. 

Back to top

What's new in Backup Exec agents and options

This release of Backup Exec includes the following new features and capabilities in the agents and options:

Agent for VMware Virtual Infrastructure

Agent for Microsoft Hyper-V (formerly known as the Agent for Microsoft Virtual Servers)

Agent for Microsoft Exchange Server

Agent for Enterprise Vault

Exchange Mailbox Archiving Option

Lets you archive Microsoft Exchange Server emails that have been backed up. After data is archived, it is deleted from its source location, which reduces the amount of data on the Exchange Server.

The Archiving Option uses Enterprise Vault technology to move archive data to disk-based vault stores. Only data that is already backed up is archived so that there is little effect on the Exchange Server. End users can retrieve current and previous versions of files by browsing a web interface called Backup Exec Retrieve.

File System Archiving Option

Lets you archive Windows NTFS data that has been backed up. After data is archived, it is deleted from its source location, which reduces the amount of data on the file server.

The Archiving Option uses Enterprise Vault technology to move archive data to disk-based vault stores. Only data that is already backed up is archived so that there is little effect on the Exchange Server. End users can retrieve current and previous versions of files by browsing a web interface called Backup Exec Retrieve.

Virtual Tape Library Unlimited Drive Option

Supports all additional drives that you add after the first drive in each virtual tape library (VTL). You can purchase the Virtual Tape Library Unlimited Drive Option to support all of the additional drives in each virtual tape library. You do not have to purchase separate instances of the Virtual Tape Library Unlimited Drive Option for each virtual drive.

Additional VTL enhancements include the following:

Deduplication Option

Provides the following features to support a data reduction strategy:

Active Directory Recovery Agent 

Supports Microsoft 2008 R2 Active Directory Domain Services objects.

Agent for Lotus Domino Server

Supports Lotus Domino version 8.5, including support for the Domino Attachment and Object Service (DAOS).

Symantec Online Storage for Backup Exec

Provides more efficient online backups. Symantec Online Storage for Backup Exec now compares your backup selections to any existing backup data from previous duplicate backup jobs. Any data that is unchanged from previous duplicate backup jobs is skipped. If only a portion of a file has changed, only that portion is backed up. This enhancement can reduce the amount of time and bandwidth that is required to run recurring backup jobs.

Desktop and Laptop Option

Supports Microsoft Windows Server 2008 R2 on the following components:

Supports Microsoft Windows 7 on the following components:

Back to top
 

Where to find more information

The Backup Exec Technical Support Knowledge Base contains information that pertains to this release of Backup Exec.

The Backup Exec Knowledge Base provides TechNotes, how-to topics, best practices, links to instructional videos, troubleshooting articles, and other valuable information to help you use Backup Exec to its fullest extent.

For more information, go to the following URL:

http://www.symantec.com/business/support/overview.jsp?pid=15047

Back to top

Backup Exec installation notes

Installation notes

The following notes provide information about installing Backup Exec:

·        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 Backup Exec Administrator's Guide:

Installing the Remote Agent for Linux or UNIX Servers

Installing the Remote Agent for Macintosh Systems

Installing the Remote Media Agent for Linux Servers

·        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/Server 2008. 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 will resolve this issue:

http://support.microsoft.com/kb/935606

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, 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 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.
 

·        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:

http://support.microsoft.com/kb/910229

·        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:

http://support.microsoft.com/default.aspx?scid=KB;en-us;298503&

·       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 installing 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:

  1. Access the Backup Exec installation media from the Windows Explorer browser.

  2. Change the directory to \BE\WINNT\INSTALL\BE32 or \BEx64, whichever is appropriate.

  3. Run setup.exe

Back to Top

Features no longer supported by Backup Exec

The following features are no longer supported by Backup Exec:

Back to Top

Hardware and driver notes

The 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 Support Web site at:

http://entsupport.symantec.com/umi/V-269-1

http://entsupport.symantec.com/umi/V-269-2

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 Support.

Back to top

General Backup Exec notes

The following notes detail general information about using 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.

·        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:

http://entsupport.symantec.com/docs/270139

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:

http://securityresponse.symantec.com/avcenter

When you add the URL, you ensure proper functionality between SEPM and 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.

·        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:

http://entsupport.symantec.com/docs/274583

·        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.

·        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:

http://entsupport.symantec.com/docs/288283

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.

·        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 by using the following link:

 http://entsupport.symantec.com/umi/v-79-57344-34110

·        Backup performance can be seriously degraded if you use LUN libraries that are attached to a 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 by using the following link:

http://support.microsoft.com/kb/842411

http://seer.entsupport.symantec.com/docs/290098.htm

                http://seer.entsupport.symantec.com/docs/288428.htm

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:

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.

Note: When a hub is in place instead of a switch, full duplex may not be supported. See the Original Equipment Manufacturer (OEM) for details on the device's features.

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.

http://entsupport.symantec.com/umi/v-269-11

Back to top

Cluster-aware Backup Exec notes

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 browsing servers, icons for both virtual and non-virtual servers appear identical until an icon for the virtual server is expanded.

Back to top

Backup Exec License Assessment Tool notes

The following notes detail information about using the License Assessment Tool with Backup Exec:

https://licensing.symantec.com

The following items are not supported for license key scans:

The license count for the Remote Agent for Linux or UNIX Servers may be inconsistent when the following occurs:

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.

 

Back to top

Backup Exec agents and options notes

Exchange Agent notes

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:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q838183

Back to top

Central Administration Server Option (CASO) notes

To perform a rolling upgrade, all of the managed media servers must run Backup Exec 12.5 with the most recent service pack

Archiving Option notes

The following notes apply to both the Exchange Mailbox Archiving Option and the File System Archiving Option:

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 hosts file, the Backup Exec installation saves a copy of the original hosts file as a file named hosts.beao.bak.

Skipping file data.txt. Files that contain alternate data streams are not archived.

Use the following steps to change this default to allow the archiving of files that contain alternate data streams:

  1. Open the registry editor.

  2. Under HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec For Windows\Backup Exec\Engine\Misc, change the value of the DWORD value ArchiveADSItems to 1.

Note: The DWORD value "ArchiveADSItems" is created after the archive job is run. After you change the above value to 1, all of the files that contain alternate data streams can be archived.

Back to top

Backup Exec Retrieve Notes

The following notes detail information about using Backup Exec Retrieve with Backup Exec:

Back to top

Desktop and Laptop Option (DLO) notes

You must be running DLO in Backup Exec 11d or later before you can use the command line (silent mode) method to upgrade to the DLO in Backup Exec 2010.

Back to top

Remote Agent for Linux or UNIX Servers notes

The following notes detail information about using the Remote Agent for Linux or UNIX Servers (Remote Agent) with Backup Exec:

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. 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 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:

As a resolution, try dismounting the GVFS, and retry the operation.

 

 

  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.

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 Symantec Backup Exec 2010 Administrator's Guide for more information.

Back to top

Remote Media Agent for Linux Servers notes

Tapes may become unappendable if they are written to while on tape devices that are accessed through the Remote Media Agent for Linux Servers. This issue occurs when the tape block size does not match the tape buffer size, which may be the default setting for the tape device.

To work around this issue, in the Properties page for the device, change the setting "Block size (per device)" to match the setting 'Buffer size (per device)".  You must then change the block size on any tapes that have become unappendable by running a Quick Erase operation.

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.

Back to top

Advanced Open File Option (AOFO) notes

The following notes detail information about using the Advanced Open File Option with Backup Exec:

·        When you use Hitachi's VSS provider with dynamic disks, you must configure AOFO to use the hardware manufacturer's technology. Go to the Snapshot provider field on the AOFO Backup Job Properties dialog box. Select Hardware - use technology provided by hardware manufacturer.

·        If you upgrade to Backup Exec 2010 on a computer that runs Windows Server 2003 or later, Backup Exec automatically removes the Symantec Volume Snapshot Provider (VSP). Backup Exec uses VSP on Windows 2000 Server/XP 32-bit, and Microsoft Volume Shadow Copy Service (VSS) on Windows Server 2003 and later on both 32-bit and 64-bit platforms.

Back to top

Advanced Disk-based Backup Option notes

The following notes detail information about using the Advanced Disk-based Backup Option with Backup Exec:

·        When you use the Hitachi VSS provider for the Advanced Disk-based Backup Option, if you upgrade a basic disk to a dynamic disk, you must manually split and then recreate the Hitachi snapshot pair. See your Hitachi documentation for details.

·        When you use Hitachi's VSS provider with dynamic disks, you must configure the Advanced Disk-based Backup Option to use the hardware manufacturer's technology. Go to the Snapshot provider field on the Advanced Disk-based Backup Option Backup Job Properties dialog box. Select Hardware - use technology provided by hardware manufacturer.

·        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.

Back to top

Remote Agent for Windows Systems notes

The following notes detail information about using the Remote Agent for Windows Systems with Backup Exec:

See the following link for instructions on starting the Remote Registry Service:

http://technet.microsoft.com/en-us/library/cc754820.aspx

 

%SystemRoot%\F52E2DD5-CE7D-4e54-8766-EE08A709C28E

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.

Back to top

Using Backup Exec and Continuous Protection Server with Symantec Endpoint Protection (SEP)

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.

Back to top

Agent for Microsoft Hyper-V notes

The following notes detail information about using the Agent for Microsoft Hyper-V (formerly known as the Agent for Microsoft Virtual Servers) with Backup Exec:
 

·        Backup Exec's Granular Recovery Technology (GRT) does not support virtual machines that use dynamic disks, such as spanned, mirrored, striped, or RAID 5 disks.
 

 

Back to top

Agent for VMware Virtual Infrastructure notes

If a virtual machine name contains a backslash (\), the following issues occur:

Back to top

NDMP Option notes

The following notes detail information about using the NDMP Option with Backup Exec:

Back to top

Deduplication Option notes

A deduplication storage folder could not be created in the given directory.

Additionally, you cannot locate the deduplication storage folder database in a database path that contains double-byte characters.

Back to top

Intelligent Disaster Recovery (IDR) Option notes

The following notes detail information about using Intelligent Disaster (IDR) with Backup Exec:

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.

clrest [-f] path [drive letter]

Symantec recommends that you exclude the recovery of the media server's deduplication storage folder. To exclude the deduplication storage folder from recovery, do not recover the Shadow Copy Components resource. Then, after the IDR operation has successfully completed, you can manually recover the deduplication storage folder and any remaining operating system data.

You can avoid this situation if you exclude the deduplication storage folder from the backups when you prepare the IDR recovery media for the media server. To exclude the deduplication storage folder from the backups, in backup selections, on the Shadow Copy Components resource, manually uncheck the "User Data\Backup Exec Deduplication Storage" node.

However, you must ensure that the media server's deduplication storage folder is backed up in a subsequent job by explicitly and individually selecting the "User Data\Backup Exec Deduplication Storage" node on the Shadow Copy Components resource.

To recover the deduplication storage folder, manually remove any pre-existing deduplication storage folder data before you start the recovery of the media server.


Back to top

Backup Exec Utility (BEutility.exe) notes

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 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:

  1. Change all of the secondary servers of the current primary server to standalone media servers. To perform this operation, use the Backup Exec Utility operation Remove Primary SAN SSO Server.

  2. Change the standalone media servers to secondary servers of the new primary server. Use the Backup Exec Utility operation Set Primary SAN SSO Server.

  3. To change the current primary server to a secondary server of the new primary server, do the following:

§  Uninstall Backup Exec on the current primary server.

§  Reinstall Backup Exec.

§  On the current primary server, run the Backup Exec Utility operation Set Primary SAN SSO 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 do the following:

  1. Change all of the managed media servers that belong to the current central administration server to standalone media servers. To perform this operation, use the Backup Exec Utility operation Remove Primary SAN SSO Server.

  2. Change the standalone media servers to managed media servers that belong to the new central administration server. Use the Backup Exec Utility operation Set Central Administration Server.

  3. To change the current central administration server to a managed media server that belongs to the new central administration server, uninstall Backup Exec on the current administration server.  Then reinstall Backup Exec. On the current primary server, run the Backup Exec Utility operation Set Central Administration Server.

Back to top

Command Line Applet notes

The Command Line Applet does not support backing up the following Enterprise Vault components: