Symantec Backup Exec 2010 R2 Readme
Table: What's new in Backup Exec 2010 R2
Provides a new, simpler wizard for installation. This installation method is designed for small or uncomplicated environments. Backup Exec makes many of the installation decisions for you, based on common installation scenarios. If you prefer to set all of your installation options, you can use the Custom installation option, which provides the same installation wizard that was available in Backup Exec 2010.
The Renewal Assistant uses the contract expiration information to automatically set the Backup Exec alerts that remind you to renew the maintenance contracts before they expire. Reminder alerts are set at 30-day, 60-day, and 90-day intervals, based on the expiration date of the maintenance contract.
Includes the following new features:
Includes the following new features:
Backup Exec no longer supports the following features:
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.
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.
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.
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:
The following notes provide information about installing Backup Exec:
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:
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 resolves this issue:
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.
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.
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 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.
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 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.
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:
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.
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:
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.
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.
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:
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.
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 add the fully qualified domain name of the Oracle server to the Backup Exec Oracle modify list
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:
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.
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:
The restore of a Microsoft 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.
The Backup Exec Granular Recovery Technology (GRT) feature does not support 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. Backing up to a backup-to-disk folder is supported.
The following notes detail information about using the Agent for VMWare with Backup Exec:
To avoid issues with quiesced snapshots when you back up VMware virtual machines in ESX 4.0 environments, 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.
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 two entries to the hosts file. The entries in the hosts file point to the loopback address (127.0.0.1) of the system. The first entry is for EnterpriseVaultSiteAlias. The second entry is EV-<machineName>-<hex timestamp>. Backup Exec adds the following comment to the hosts file:
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.
The Backup Exec File System Archiving Option does not store alternate data streams that my 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:
To change the default behaviour of the Backup Exec File System Archiving Option
The following notes detail information about using Backup Exec Retrieve with Backup Exec:
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:
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.
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:
The following notes detail information about using Intelligent Disaster (IDR) with Backup Exec:
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.
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:
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.
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.
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.
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:
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:
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:
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.
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.
For Remote Agent for Linux and UNIX Servers agents that run on Linux systems where the locale is set to one of the eastern languages (Chinese, Japanese, Korean, and so forth), the Remote Agent may stop running when it tries to back up a path name that exceeds 150 characters, and when the path contains UNICODE or multi-byte characters. With shorter path names, Backup Exec may not be able to restore the data that is backed up from such paths.
As a workaround, do not back up data from path names that might contain UNICODE or multi-byte characters. Try to rename the path names by using character sets that use single character encoding, such as LATIN-1 or ASCII.
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.
The following notes detail information about using the Remote Media Agent for Linux Servers with Backup Exec:
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 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.
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.
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:
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:
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.