Symantec Backup Exec 2010 R3 SP3 Readme

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

http://www.symantec.com/

All hyperlinks in Symantec products and documentation lead to English-language websites.

What's new in Backup Exec 2010 R3 SP3

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

Note:

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

Item

Description

Support for Windows Server 2012

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.

See Windows Server 2012 notes.

Backup Exec Agent for Hyper-V

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.

See Agent for Hyper-V notes.

Backup Exec Agent for VMware Virtual Infrastructure

The Agent for VMware Virtual Infrastructure supports backups and restores of VMware vSphere/ESX/vCenter 5.1 and hardware version 9.

See Agent for VMware Virtual Infrastructure notes.

Backup Exec Agent for Microsoft Exchange Server

The Exchange Agent supports Microsoft Exchange Server 2010 SP3.

Backup Exec Agent for Microsoft SQL Server

The SQL Agent supports the following:

  • Microsoft SQL Server 2008 R2 SP2

  • Microsoft SQL Server 2012 SP1. However, you cannot install the Backup Exec Database on a Microsoft SQL Server 2012 instance.

    Additionally, SQL Server 2012 availability group databases can be backed up and restored using the host instance on the primary node. However, specific support for availability groups is not provided in this release.

Features no longer supported by Backup Exec

Backup Exec no longer supports the following features:

Where to find more information

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:

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

Hardware and driver notes

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:

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 technical support.

Backup Exec installation notes

The following notes provide information about installing 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:

  1. Access the Backup Exec installation media from the Windows Explorer browser.
  2. Change the directory to \BEx64.
  3. Run setup.exe

To uninstall the VMware SVGA II driver and use the Standard VGA Graphics Adapter instead:

  1. Click Start > Control Panel > Hardware > Display.
  2. Select Change display settings, and then select Advanced Settings.
  3. Select Properties, and then click the Driver tab.
  4. If VMware SVGA II drivers are installed, select Uninstall.
  5. Select the checkbox to Delete the driver software for this system, and then click OK.
  6. Select Yes to restart your computer now.
  7. After the computer restarts, check to ensure that the Standard VGA Graphics Adapter is installed.

General Backup Exec notes

The following notes detail general information about using Backup Exec:

Windows Server 2012 notes

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 notes

The following notes provide backup information when you use Backup Exec:

To add the fully qualified domain name of the Oracle server to the Backup Exec Oracle modify list

  1. Click Tools > Options > Oracle.
  2. Click Modify list.
  3. Click New.
  4. Under Oracle or DB2 Server, type a fully qualified domain name.

    For example, <oracleservername.example.com>

  5. Under Logon Account, assign a logon account.
  6. Click OK.
  7. On the Authentication Credentials for Oracle and DB2 Servers dialog box, click OK.

Restore notes

The following notes provide restore information when you use Backup Exec:

Advanced Disk-based Backup Option notes

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

Agent for Hyper-V notes

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.

See Notes about how the Agent for Hyper-V works with Windows Server 2012.

See General notes about the Agent for Hyper-V.

Notes about how the Agent for Hyper-V works with Windows Server 2012

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:

General notes about the Agent for Hyper-V

The following notes detail information about how to use the Agent for Hyper-V with any supported version of Microsoft Windows.

Agent for VMware Virtual Infrastructure notes

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:

The following information applies to all Agent for VMware Virtual Infrastructure jobs, regardless of the platform used:

The following information applies to ESX 4.0 environments:

Archiving Option notes

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

To change the default behavior of the Backup Exec File System Archiving Option

  1. Open the registry editor.
  2. Under HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec For Windows\Backup Exec\Engine\Misc, select one of the following:
    • 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 2 to skip files with 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.

      Note:

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

Backup Exec Retrieve notes

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

Cluster-aware Backup Exec notes

The following notes detail information about using cluster-aware Backup Exec:

Deduplication Option notes

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

Exchange Agent notes

The following notes detail information about using the Exchange Agent with Backup Exec:

Intelligent Disaster Recovery (IDR) Option notes

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

NDMP Option notes

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

Remote Agent for Linux and UNIX Servers notes

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

Remote Media Agent for Linux Servers notes

The following notes detail information about using the Remote Media Agent for Linux Servers with Backup Exec:

Remote Agent for Windows Systems notes

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

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.

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 Symantec technical support.

To move all of the secondary server to a new primary server

  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.

To use the Backup Exec Utility Remove Primary SAN SSO Server operation

  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.

Backup Exec License Assessment Tool notes

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

Command Line Applet notes

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: