Backup Exec 2010 revision 2896 Hotfix 348284

Problem

Backup Exec 2010 revision 2896 Hotfix 348284

Solution

Summary
This hotfix contains a critical fix for the Backup Exec.

Affected versions
Backup Exec 2010 revision 2896 32bit Media Servers
Backup Exec 2010 revision 2896 x64bit Media Servers
Backup Exec 2010 revision 2896 32bit Agent for Windows Servers
Backup Exec 2010 revision 2896 x64bit Agent for Windows Servers
Backup Exec 2010 revision 2896 Remote Media Agent for Linux Servers (32bit Linux Platforms) - BERMALS
Backup Exec 2010 revision 2896 Remote Media Agent for Linux Servers (64bit Linux Platforms) - BERMALS


Prerequisites
- Administrative privileges are required to install this hotfix.


Post requisites
- A full backup is recommended after installing this hotfix.
- The IDR recovery media (the ISO created through the IDR Wizard) needs to be recreated after installing this hotfix.
- Remote Agent for Windows Servers will need to be updated after installing this hotfix.

Download links
For 32bit Media Servers: www.symantec.com/docs/TECH129104
For x64bit Media Servers: www.symantec.com/docs/TECH129106
For BERMALS (32bit Linux platforms): www.symantec.com/docs/TECH125635
For BERMALS (x64bit Linux platforms): www.symantec.com/docs/TECH125635

Issue(s) resolved
 
Advanced Disk Based Option (ADBO):
 
-Baseline Synthetic Backup jobs fail with a timeout error during the collection of synthetic backup information. ( For more details, please refer to the following document: www.symantec.com/docs/TECH61130
 

 
Archiving Option (BEAO):
 
- BEAO:BEServer crashes on the longevity setup when jobs (Backup and Archive) are continuously running for few days.
 

 
Backup Exec Command Line (BEMCMD):
 
-The Backup Exec Command Line Applet (BEMCMD) will not permit more than one BackupToDisk Device setting to be enabled at the same time. (For more details, please refer to the following document: www.symantec.com/docs/TECH88161
 
-The Backup Exec Command Line Applet (BEMCMD) will not change a BackupToDisk Device setting to 'Auto detect'. ( For more details, please refer to the following document: www.symantec.com/docs/TECH88170
-BEMCMD -o129 option to delete media does not work with the Backup Exec other than English edition. ( For more details, please refer to the following document: www.symantec.com/docs/TECH127154
 
-Bemcmd -o1 returns "-1" when backup job is configured with notification recipients. ( For more details, please refer to the following document: www.symantec.com/docs/TECH71813
 

 
CORE:
 
-After install / upgrade or adding license keys to the Backup Exec 2010 Installation, the Backup Exec Server service hangs in a starting state. ( For more details, please refer to the following document: www.symantec.com/docs/TECH126174
 
-Backup Exec Server Service (BESERVER.EXE) terminates when backup device settings are viewed or modified while active jobs are running. ( For more details, please refer to the following document: www.symantec.com/docs/TECH77862
 
-Backup of a Remote Server fails with the error "Access is denied to Remote Agent" if global excludes are configured. ( For more details, please refer to the following document: www.symantec.com/docs/TECH60661
 
-When a back up job fails it may reference the wrong resource in the error message. ( For more details, please refer to the following document: www.symantec.com/docs/TECH126069
 
-A post-command does not run on each server backed up after job verification completes. ( For more details, please refer to the following document: www.symantec.com/docs/TECH126061
 
-After upgrading to Backup Exec 12.5, the Backup Exec Job Engine service crashes intermittently and an EVENT ID 1000 is reported with description "Faulting application Bengine.exe,version 12.5.2213.158,faulting module MSVCR80.DLL,version 8.0.50727.3053 " ( For more details, please refer to the following document: www.symantec.com/docs/TECH77668
 
-When launching the Backup Exec console, a security warning "The Backup Exec user interface can only be run as a fully trusted application under .NET security policies." is encountered. ( For more details, please refer to the following document: www.symantec.com/docs/TECH126929
 
-Backup Exec for Windows 2010 console will not launch after installing a hotfix manually or thru Live Update due to a pending reboot request. ( For more details, please refer to the following document: www.symantec.com/docs/TECH125754
 
-Backup Exec for Windows 2010 upgrade reports there was a problem upgrading the Backup Exec Device & Media Service and the Backup Exec services will not start. ( For more details, please refer to the following document: www.symantec.com/docs/TECH125397
 
-In Backup Exec 2010, the Backup Exec Server Service terminates during/after the Backup Exec internal Database Maintenance has run. ( For more details, please refer to the following document: www.symantec.com/docs/TECH124862
 
-An upgrade installation of Backup Exec 2010 fails in the migration process and the Event Logs report that the "BEMIG.EXE" process terminated midway. ( For more details, please refer to the following document: www.symantec.com/docs/TECH124741
- Backup Exec is unable to reuse/reclaim space from OLD IMG media that are located in a Removable Backup to Disk Folder (For example DELL RDX 1000 device) and these IMG media show up under the "Backup Exec and Windows NT Backup Media" media set. ( For more details, please refer to the following document: www.symantec.com/docs/TECH70364
 
-Beremote.exe crashes when backing up file data from a 2008 R2 server with Exchange 2010 installed. ( For more details, please refer to the following document: www.symantec.com/docs/TECH77355
 
-Final Byte Count incorrect for Jobs
 
-Copy and Delete job shows wrong job rate
 
-bengine faults in THEFH_LibCatalog.dll
 
-BENGINE crash in ImageBasedFHPlugin
 
-UI Crash, Colletion was modified
 
- UI Crashes when it does not have access to the registry
 
-EULA displayed in English for all languages
 

 
DB2 Agent:
 
-Unable to restore Incremental backup of DB2 instance. ( For more details, please refer to the following document: www.symantec.com/docs/TECH77670
 
-Unable to restore DB2 due to incorrect archive log association. ( For more details, please refer to the following document: www.symantec.com/docs/TECH128830
 

 
Deduplication Option:
 
-During concurrent media changes on two separate deduplication devices on the same media server, using the Deduplication Option (Dedupe), the data on one of the devices could be inadvertently corrupted.  (For more details on this please refer to document: www.symantec.com/docs/TECH125840
 
-OST: ExaGrid Logical Storage unit is not displaying if server name is typed out.
 
-Licensing: Scheduler: Error: At Least one transport mode must be selected. When trying to submit a Next Run for job created by a policy.
 
-Need to update PostgreSQL Database from 8.3.7 to 8.3.8
 

 
Device and Media\Hardware\IDR:
 
-Cannot inventory large number of slots in a VTL
 
-Erasing of IMG files get Communication Timeout
 
-Issues with PDDE related to Windows dynamic cache issue
 
-Serialization of a B2D can result in a crash of BEServer.exe.
 
-The format and format WORM operation is enabled for a Quantum LTO-3 drive and it should not be allowed.
 
-ITDC-EOOC-Library Slot Sort order wrong.
 
-HP: IDR: Recovered system fails to boot. MBR not being written to new fixed disk.
 
-BEDIAG NDMP Enhancement - Display NDMP server information regardless if the NDMP server has no tape device attached locally.  
 
-HW: Device timeout when restoring data from tape system attached to CentricStor VTL
 
-BEWS: Wrong error message after running an inventory job on incompatible media.  
 
-IDR/OBDR: The bootable tape image is not being written to tape on an HP OBDR capable DAT tape drive
 
-When "missing" devices are no longer missing, they should be automatically deleted from the database.  
 
-IDR: Brocade Miniport driver not loaded during IDR
 
-IDR/OBDR: The HP DAT320-USB tape drive is not listed as a restore source during an OBDR/IDR recovery on 2008-x64  
 
-device discovery failing for ATAPI devices (W2008 specific)
 
-Iomega Rev loader is not properly serialized in BE.
 
-OST: If the source and destination block sizes of an opt-dupe job are different the job fails.  
 
-Could not remove library partitions after removing partitioned library from the UI.
 
-IDR/OBDR does not switch a USB tape drive from CD-ROM to sequential mode on 2008.
 
-IDR loops errors restoring PDDE for Matador server when PDDE's virtual disk is unavailable.
 
-Add encryption recognition for LTO5 strings.
 
-Quantum (HP rebranded) LTO3HH SCSI WORM Failure.
 
-IDR: IDR recovery wizard incorrectly maps the C: boot partition to the Dedupe LUN
 

 
Domino Agent:
 
-Lotus Domino databases residing on a mount point are skipped and not reported in the job log.(For more details, please refer to the following document: www.symantec.com/docs/TECH77399
 
-Added support for Lotus Domino Support for 8.5.1
 

 
Microsoft Exchange Agent:
 
-Restore of individual email messages from Granular Recovery Technology (GRT) enabled Exchange Information Store backup sets using Backup Exec 2010 fail with error "0xe00002f8 one or multiple mail messages could not be opened because of an unknown MAPI error " if the Exchange Client Access Server has Secure Socket Layer (SSL) certificates installed. (For more details, please refer to the following document: www.symantec.com/docs/TECH77354
 
-Restore of individual emails/mailbox from a Granular Recovery Technology (GRT) backup set of Exchange database, completes successfully but no messages are restored (For more details, please refer to the following document: www.symantec.com/docs/TECH125478
 
-Unable to restore GRT Exchange 2010 data for users that have a special characters in the display name. (For more details, please refer to the following document: www.symantec.com/docs/TECH124573
 
-The Exchange Information Store selection is no longer visible in the backup selection for a Exchange 2007 Cluster Continuous Replication (CCR) setup after upgrading to Backup Exec 2010 (For more details, please refer to the following document: www.symantec.com/docs/TECH125307
 
-Exchange 2003: Restore of an individual mail message completes with exceptions: WARNING: The file 'MessageName" was restored from a file that was corrupt when it was backed up, or the backup file is now missing or corrupt. Try restoring the file from another backup, or try repairing the file. (For more details, please refer to the following document: www.symantec.com/docs/TECH124598
 
-In Backup Exec when trying to expand a Granular Recovery Technology (GRT) enabled DISK based backup set of a Public Folder Database, the error "[SYMANTEC][Backup Exec Catalog Driver] (One or more messages were skipped because MAPI failed to enumerate the messages.Review the job log for more information.) " is received. (For more details, please refer to the following document: www.symantec.com/docs/TECH129487
 

 
Virtual Agents (AVVI and Hyper-V Agent):
 
-A backup of a guest machine on an ESX (vSphere) with two virtual disks that have the same file name only backs up one of the virtual disks. ( For more details, please refer to the following document: www.symantec.com/docs/TECH125641
 
-Backup of a virtual machine using the Backup Exec 2010 Agent for VMware Virtual Infrastructure (AVVI) fails with the error "V-79-57344-38264 - Unable to copy the virtual machine disk using the VMware VixDiskLib. VixDiskLib_Read() reported the error: You have requested access to an area of the virtual disk that is out of bounds ". ( For more details, please refer to the following document: www.symantec.com/docs/TECH77353
 
-A restore job fails with 0xe0009744 when restoring individual items such as files or folders in the backed up 2nd VMDK file or later of a virtual machine. ( For more details, please refer to the following document: www.symantec.com/docs/TECH125559
 
-Backup of Virtual Machines on a VMWare ESX 3.5 host complete with the exception V-79-57344-38725 - One or more virtual disks contain volumes that do not support Granular Recovery Technology (GRT). Granular restores cannot be performed for these volumes. ( For more details, please refer to the following document: www.symantec.com/docs/TECH125915
 
-In Backup Exec 2010, during a backup of a Virtual Machine the AVVI agent is incorrectly identifying used blocks of data as unused, resulting in missing data from the backup and the inability to restore the missing data. ( For more details, please refer to the following document: www.symantec.com/docs/TECH128232
 
-AppGRT backups for AVVI and Hyper-V Agent fail when SQL and Exchange present. ( For more details, please refer to the following document: www.symantec.com/docs/TECH128831
 
-ESX:some guest OS files might not be restored even if restore job had completed without error. ( For more details, please refer to the following document: www.symantec.com/docs/TECH128927
 
- Hyper-v all VM backups fail if master VM has pass through disk is configured on it.
 
-AVVI: Backing up a local thick disk and selecting SAN only causes beremote to crash.
 
-AVVI: Restore of a VM with two disks on different datastores restores both disks to the first datastore.
 

 

Installation Guide
This installation guide contains general information for installing Backup Exec product updates as well as special instructions for configurations including CPS, Agent for Windows Servers, Remote Agent for Linux/Unix/Macintosh Servers (RALUS/RAMS), Clustered Backup Exec, Shared Storage (SSO) installations, Central Admin Servers (CASO) installations, and SAP/R3 Oracle Agents.www.symantec.com/docs/TECH58186

Uninstalling this hotfix
This hotfix can be uninstalled.  For steps on how to uninstall a Backup Exec hotfix, refer to this technote: www.symantec.com/docs/TECH58187
For File Information see attached PDF

 

 

 

 

 

 

 

 

Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)