+ All Categories
Home > Documents > NB 71 EEB Listing

NB 71 EEB Listing

Date post: 21-Apr-2015
Category:
Upload: ricardo-morschbacher
View: 237 times
Download: 1 times
Share this document with a friend
26
Symantec NetBackup™ 7.1 Emergency Engineering Binary Guide
Transcript
Page 1: NB 71 EEB Listing

Symantec NetBackup™ 7.1Emergency EngineeringBinary Guide

Page 2: NB 71 EEB Listing

The software described in this book is furnished under a license agreement andmay be usedonly in accordance with the terms of the agreement.

Legal NoticeCopyright © 2011 Symantec Corporation. All rights reserved.

Symantec and the Symantec Logo are trademarks or registered trademarks of SymantecCorporation or its affiliates in theU.S. and other countries. Other namesmaybe trademarksof their respective owners.

This Symantec product may contain third party software for which Symantec is requiredto provide attribution to the third party (“Third Party Programs”). Some of the Third PartyPrograms are available under open source or free software licenses. The LicenseAgreementaccompanying the Software does not alter any rights or obligations you may have underthose open source or free software licenses. Please see theThird Party LegalNoticeAppendixto this Documentation or TPIP ReadMe File accompanying this Symantec product for moreinformation on the Third Party Programs.

The product described in this document is distributed under licenses restricting its use,copying, distribution, and decompilation/reverse engineering. No part of this documentmay be reproduced in any form by any means without prior written authorization ofSymantec Corporation and its licensors, if any.

THEDOCUMENTATIONISPROVIDED"ASIS"ANDALLEXPRESSORIMPLIEDCONDITIONS,REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT,ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TOBELEGALLYINVALID.SYMANTECCORPORATIONSHALLNOTBELIABLEFORINCIDENTALOR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING,PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINEDIN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.

The Licensed Software andDocumentation are deemed to be commercial computer softwareas defined in FAR12.212 and subject to restricted rights as defined in FARSection 52.227-19"Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights inCommercial Computer Software or Commercial Computer Software Documentation", asapplicable, and any successor regulations. Any use, modification, reproduction release,performance, display or disclosure of the Licensed Software andDocumentation by theU.S.Government shall be solely in accordance with the terms of this Agreement.

Page 3: NB 71 EEB Listing

Symantec Corporation350 Ellis StreetMountain View, CA 94043

http://www.symantec.com

Page 4: NB 71 EEB Listing

Technical SupportSymantec Technical Support maintains support centers globally. TechnicalSupport’s primary role is to respond to specific queries about product featuresand functionality. TheTechnical Support group also creates content for our onlineKnowledge Base. The Technical Support group works collaboratively with theother functional areas within Symantec to answer your questions in a timelyfashion. For example, theTechnical Support groupworkswithProductEngineeringand Symantec Security Response to provide alerting services and virus definitionupdates.

Symantec’s support offerings include the following:

■ A range of support options that give you the flexibility to select the rightamount of service for any size organization

■ Telephone and/or Web-based support that provides rapid response andup-to-the-minute information

■ Upgrade assurance that delivers software upgrades

■ Global support purchased on a regional business hours or 24 hours a day, 7days a week basis

■ Premium service offerings that include Account Management Services

For information about Symantec’s support offerings, you can visit our Web siteat the following URL:

www.symantec.com/business/support/

All support services will be delivered in accordance with your support agreementand the then-current enterprise technical support policy.

Contacting Technical SupportCustomers with a current support agreement may access Technical Supportinformation at the following URL:

www.symantec.com/business/support/

Before contacting Technical Support, make sure you have satisfied the systemrequirements that are listed in your product documentation. Also, you should beat the computer onwhich theproblemoccurred, in case it is necessary to replicatethe problem.

When you contact Technical Support, please have the following informationavailable:

■ Product release level

Page 5: NB 71 EEB Listing

■ Hardware information

■ Available memory, disk space, and NIC information

■ Operating system

■ Version and patch level

■ Network topology

■ Router, gateway, and IP address information

■ Problem description:

■ Error messages and log files

■ Troubleshooting that was performed before contacting Symantec

■ Recent software configuration changes and network changes

Licensing and registrationIf yourSymantecproduct requires registrationor a licensekey, access our technicalsupport Web page at the following URL:

www.symantec.com/business/support/

Customer serviceCustomer service information is available at the following URL:

www.symantec.com/business/support/

Customer Service is available to assist with non-technical questions, such as thefollowing types of issues:

■ Questions regarding product licensing or serialization

■ Product registration updates, such as address or name changes

■ General product information (features, language availability, local dealers)

■ Latest information about product updates and upgrades

■ Information about upgrade assurance and support contracts

■ Information about the Symantec Buying Programs

■ Advice about Symantec's technical support options

■ Nontechnical presales questions

■ Issues that are related to CD-ROMs or manuals

Page 6: NB 71 EEB Listing

Support agreement resourcesIf youwant to contact Symantec regarding an existing support agreement, pleasecontact the support agreement administration team for your region as follows:

[email protected] and Japan

[email protected], Middle-East, and Africa

[email protected] America and Latin America

Page 7: NB 71 EEB Listing

About the NetBackup 7.1EEB listing

This document includes the following topics:

■ NetBackup 7.1 Emergency Engineering Binary (EEB) Listing

NetBackup 7.1 Emergency Engineering Binary (EEB)Listing

This following table contains the known issues that were identified, fixed, andavailable to our customers in the formof anEmergencyEngineeringBinary (EEB).NetBackup 7.1 contains each of these EEBs. It is possible that additional EEBswere released since this document was posted. If you do not see an EEB that youexpected to see in this document, contact your Symantec NetBackup Supportrepresentative. In addition, if you require additional information about an issuein this table, contact your Symantec NetBackup Support representative.

Table 1-1 NetBackup 7.1 EEB Listing

Emergency Engineering Binary DescriptionEtrack NumberSummary ISSUE

Unable to perform a successful BMR restore of a Windows 2008cluster because of the changes thatweremade in thewayWindowsServer 2008 protects service executables.

2150760S2151061

Changes were made to address an issue that caused nbvault tocrash and produce a status 26 error.

2028605S2029271

A change was to fix an issue that caused the nbsl to core dump.2146758S2147024

Page 8: NB 71 EEB Listing

Table 1-1 NetBackup 7.1 EEB Listing (continued)

Emergency Engineering Binary DescriptionEtrack NumberSummary ISSUE

Improvements were made to improve the Informix logical logbackup performance. For more information, about theimprovements that were made, refer also to ET899832.

2061099S2061629

A fix was made to address an issue that caused bmrd to loopcontinuously in a Linux client configuration where a disk has anEFI label. This issue caused significant CPU consumption whenimporting.

2001213S2001448

Additional changesweremade to address an issue that causedbmrdto consume too much CPU resource. That caused a Point-in-timerestore never complete.

1979906S1980257

Whenrunning thebplist commandwith the-l flagonaWindows7.0 master server, it does not report the backup time of the files asit should. Even with the -b flag, the time field is not correct.

2024848S2024901

More than 10 local drives in the file selection list cannot be backedup without an error message appearing.

2089090 21918202191821 21918222118416

S2089113

A non-multiplexed Oracle restore would send a SIGUSR1 to

child pid -1 signal. That caused other non-NetBackup systemservices to be sent a signal 16.

2090654S2091734

Although NetBackup client service is running as an account thathas read andwrite permissions to aUNCpath, restores to that pathusing the option, restore the file using a temporary file name, doesnot work.

2015816S2016562

Fragments for staged backups (non-SLP) were left in the EMMdatabase when images were expired after the expiry date wasreached.

1668996S1669826

The bpdm -mark_as_swept command erroneously put tapefragments into the EMM database.

2056075S1669826

A change was made to ensure that theuser_ops/dbext/jobs/vxbsa pid files anduser_ops/dbext/logs logs get cleaneduponHP-UX11.23 IA64and PA-RISC systems.

2154895 2186190S2186223

About the NetBackup 7.1 EEB listingNetBackup 7.1 Emergency Engineering Binary (EEB) Listing

8

Page 9: NB 71 EEB Listing

Table 1-1 NetBackup 7.1 EEB Listing (continued)

Emergency Engineering Binary DescriptionEtrack NumberSummary ISSUE

Multiple changes were made to address the issues that caused thebpbkar application to fail. These failures may occur in a clusteredenvironment, during a ShadowCopyComponents backup, orwhendoing a backup of all local drives. Refer to the listed Etrack formoreinformation about the failures that were fixed.

1990870 19267002140536 20152961829794 20151902161818 2124907

S1991878

A change was made to address an issue that caused an error 255to occur when all drivers to be used during restore were removed.The process did not allow the removal of drivers that were notrequired.

2054303S2054362

Individual file restores failed when the path was part of a nestedmount point from FlashBackup-Windows images.

2071131S2071154

A change was made to address an issue that caused nbpem to coredump.

1993541S1993882

A fixed was added to correct an issue that caused nbpem ASSERT

-

((m_streams.insert(StreamPair(childId,streamNumber))).second)

to fail.

2031604S1993882

A change was made to address an issue that caused nbpem to coredumps because of a memory leak on a SUSE Linux 10 system.

2137219S1993882

A change was made to ensure that you have to ability to connectto failover SQL2008 instances when multiple SQL server versionsare present within the same Windows Cluster.

2011198S2011221

A change was made to correct an issue that causedPREFERRED_NETWORK issue if some addresses were excluded.

2137288S2137287

The FT media server bundle, nbfdrv64, start-up would fail onshared PCI-E, SUNW, T2000, and T5240 with the following errorwith an older Solaris 10 release level such as update 6:

Fatal application error #0x0009 (Target-Side

Application Initialization Failure) @

stdfapi.c[354] (CPU 0):

1987613 1940043S1940101

A fix wasmade to address an issue that occurredwhen a hard limitwas reached on the file system. A large number of directories(32,765) in the /var/tmp/ location caused the issue.

2161303S2095081

In the Windows Administration Console, you were unable tooverride default priority from the Vault Profile Duplication tab.

2133009S2133338

9About the NetBackup 7.1 EEB listingNetBackup 7.1 Emergency Engineering Binary (EEB) Listing

Page 10: NB 71 EEB Listing

Table 1-1 NetBackup 7.1 EEB Listing (continued)

Emergency Engineering Binary DescriptionEtrack NumberSummary ISSUE

A change was made to add a wrapper or vxship implementationfor vxrecover.

2037201S2037471

A MEDIA_READY followed by SIGUSR1 may interrupt a legacydata socket accept.

2060471S2060548

A small number of jobs were Active on the weekends when a largenumber of jobs usually start.

2078903S2079761

SAP local restores were successful, however a fix was created toaddress a child backint report error to brrestore.

2140282S2140399

The nbdevconfig -mergedps command does not update theimage database (imageDB).

2021721S2021738

When is a restore considered successful even though the totalrestored do not match the total requested for restore?

1947428S1947615

A change wasmade to ensure that the nbsvcmon process does notrestart processes. The monitoring had not been enabled.

2100745S2100742

The tape ImageExpireDateTime is less than expiration date forthe last image to expire on the tape. TheNetBackupAdministrationConsole provides an option to "unfreeze" these tapeswhich are notfrozen. If you clicked the option, the tape returns to scratch eventhough there were valid images.

2145710S2145884

PDF and HTML report exports do not honor the order that thecolumns are set to.

2111910S2111915

After a backup failure the tapes from the failed backup are reused,however they fail with position errors as BPTM tries to position tothe end ofmedia (EOM). If a BPTM freezes themedia the followingerror could occur when the physical end of the tape is reached.

2166912 20720652140608

S2072780

A EEB was created to allow an SLP to duplicate synthetics.2139668 2196391S2140227

TheNetBackup-JavaAdministrationConsole for theVault,DeferredEject option does not populate the preview area to allow ejects.

2098852 2115458S2099016

Unable to restore theGRTExchange objects that are older than sixmonths.

2049361 2123756S2049556

A change was made to address a status 50 process aborted errorthat occurred after duplications started.

2115680S2115689

About the NetBackup 7.1 EEB listingNetBackup 7.1 Emergency Engineering Binary (EEB) Listing

10

Page 11: NB 71 EEB Listing

Table 1-1 NetBackup 7.1 EEB Listing (continued)

Emergency Engineering Binary DescriptionEtrack NumberSummary ISSUE

TheNetBackupAdministration Console did not handle the scratchpool check box correctly.

2150533S2151154

A restore of the Windows 2008 MSCS node failed when BMR wasused.

2143165S2143309

Upgrade form VBR 6.6 to OpsCenter 7.0 stops to process hangs,migration of original VBR records stalls.

2052905S2052931

Intermittent VxSS authentication failures occurred on the mediaserver.

2044615 1980731S1980936

A change was made to address an issue that caused an occasionalStatus 12 message during SLP duplications.

1996957S1997112

An HTML formatted report that is sent with email would arrive asan attachment rather than inline.

2108097 2041226S2041281

Anerror occurredwhile fetching the report outputwhen the secondpage of the Week at a Glance report is displayed.

2146566S2146621

The bpVMutil would continuously restart itself if the cache filecould not be updated. That caused session strain on the vCenterserver.

2027071S2027111

Thenbdb_move with -config_only commanddoesnotupdatedatabase spaces, dbspaces, with the new location.

2106941 2183727S2106969

Vendor unique library handling of barcodes would cause injectoperations to fail and require you to use command line interface(CLI) operations.

1486729 2088224S1486637

Backups failed with a status 52 if the MediaMountTimeout is setand client deduplication is used to either deduplication or MSDPstorage units.

2093914 2169140S2094820

The bpdbm.exe executable in NetBackup 7.0.1 would generate anapplication fault after you upgraded to this version. In addition, afix was added to ensure that bpdbmwould not core dump at end ofan Exchange GRT backup.

2183484S2090513

The exclude and include lists were being recognized by the USERtype backups.

2115722 2099750S2099769

A change wasmade to be able to inhibit email of the empty reportsthat were based on conditions as was possible with VBR.

2139776S2139906

11About the NetBackup 7.1 EEB listingNetBackup 7.1 Emergency Engineering Binary (EEB) Listing

Page 12: NB 71 EEB Listing

Table 1-1 NetBackup 7.1 EEB Listing (continued)

Emergency Engineering Binary DescriptionEtrack NumberSummary ISSUE

The vStorage Mapped FullVM backups of the VirtualCenter wouldfail with the following error message.NfcFssrvrRecv: failed withcode = 9

2123706S2050461

Vault ejectswould fail after a 30-minuteMAILSLOT_OP_TIMEOUTsetting.

2052876 2140996S2052906

Incremental FlashBackup jobs failed with the following errormessage.

Cannot allocate bitmap - EXIT STATUS 36: failed

trying to allocate memory

1876368 19507202127022 16805681971419

S1680598

The media ID was padded to six characters which caused multipleejects from the user interface to fail.

2005609S2006387

When runningVault to duplicate images, there are some duplicatejobs that queued and never started.

1935220S1935303

The duplication jobs started by Vault created one bid file and didnot use all available tape drives.

2214116S1935303

A change was made to address an issue that caused the followingNetBackupmerror:NetBackupError: vault eject partially succeeded(288)

2050561S2050748

The foreign characters that were in discovered streams caused astatus 71 error for the stream and the parent job.

2070712 2071122S2071022

A Solaris 9 ISO image creation failed with a dd error when using aUSB attached CDROM/DVDROM device.

2060208S2060238

The SQLINSTANCE $ALL keyword failed on single NIC hosts. Aninstance of SQL Server was not found on this client.

2002605S2002634

An enhancement was made to provide an option for hot catalogbackups to not follow symbolic links within the imageDB.

2109487S2109643

The timestamp on the browse restore selection of SQL images wasmisleading.

2043217 2086766S2086916

Partitions that are part of a Vault Store that include Partitionsstored on EMC Centera Archivers are not protected.

2071406S2071418

Thebpdbjobs -report commanddidnot show the tape, howeverbpdbjobs -all_columns jobid did.

2049953 2065835S2050139

About the NetBackup 7.1 EEB listingNetBackup 7.1 Emergency Engineering Binary (EEB) Listing

12

Page 13: NB 71 EEB Listing

Table 1-1 NetBackup 7.1 EEB Listing (continued)

Emergency Engineering Binary DescriptionEtrack NumberSummary ISSUE

Skipped file names were truncated when the name starts with"System State:\", "Shadow Copy Components:\", "SYS:ETC/", or"SYS:VERITAS/".

2033551S2030550

The nbpemreq -predict -legacy command was off an hourduring the week that followed a daylight saving time change.

2176944 2011944S2012030

Need EEB related to Etrack 1557413 back ported to NetBackup6.5.4.

2025957S2061676

Multiple changes were made to ensure that the Activity Monitorshowed to proper job status information. For example, theActivityMonitor would show jobs that were terminated or ghost jobs witha status 50 error, and in some instances, some jobs that were in thequeue but the details showed a done status.

2155673 21300902070663 20897412171814 1557413

S2061676

Adding a valid report filter caused the report to hang.1968462S1968490

bpadm was creating synthetic backups when NetBackup-Catalogcumulative incremental schedules were updated.

2047053S2047115

The tpautoconf -verify command would fail with anNDMP_IO_ERR error from the NetApp filer.

2061876 2011596S2011616

Thevltrun -preview command failedwith an invalid commandparameter.

2116099S2116563

The application cluster (app_cluster) server was not available forselection from within the vault policy settings.

2145401S2145934

A change was made to address an issue that caused an error inrevoking access of the user group for the node.

2051769S2051808

GRTExchange backupswouldhangor take a long time to complete.In addition, 2007 and 2010 GRT backups would exit with a status1, OPEN DATABASE FAILED: -543 error.

2051693 2209840S2051711

The NetBackup-Java Administration Console reports a parsingerror while viewing or generating backup reports.

2090491S1880690

Thebpvmutilutilitywould crashwhen trying to fill in the resourcepool and datastore information.

2197597S2198120

The restore of a spannedbackupwould displays thewrongnumberof restored KB's and fail with an error code 23.

1976037 2013011S1976325

13About the NetBackup 7.1 EEB listingNetBackup 7.1 Emergency Engineering Binary (EEB) Listing

Page 14: NB 71 EEB Listing

Table 1-1 NetBackup 7.1 EEB Listing (continued)

Emergency Engineering Binary DescriptionEtrack NumberSummary ISSUE

Thebmrprepprocesswould change file permissionsof /etc/exportsand dhcpd.conf on the boot server .

2076151S2076232

An enhancement has been added that enables you to collect jobdata that has been missed.

2063635S2063639

An Incremental FlashBackupwould skip empty directories and thejob would complete with a status 0.

1853682S1853696

A change was made to address an issue that caused the WindowsNBConole to bemissing theVault andBMRManagement interfacesafter installing the NetBackup 7.01.

2110878S2111207

Backups would fail an with error 130 if more than fourEV_VAULT_STORE_DB directives were listed in the backupselection on the same policy.

2104652S2105090

The OpsCenter Scheduled HTML email reports were missing datain all of the columns except for the last column.

2140519S2140540

The spoold would not start. The explanation was thatcompactd.log could not be moved.

2073963 2158198S2073971

The bpbkar exclude list entries match shorter file names, whichshould not match. A partial name matches.

2072832S2072855

The bpresolver process would generate an application faultduring an Exchange 2010 GRT restore.

2211762S2211772

Changes were made to improve the time it takes to completeupdates to the client configurations using the JAVA or Windowsconsoles.

2057238S2057324

Catalog cleanup would run 170 hours on a 2.4TB catalog.2113882 20865292113784

S2086545

A change was made to address an issue that caused a VxMS error4109when runningOptimized (exclude unused anddeleted blocks)backup with vStorage API on a large vmdk.

2049184S2049234

Children jobs for amultistreambackupwould fail, but only a subsetwere rerun after the failure history time elapsed.

2065758S2065832

SRT using latest IBM ServRAIDM1015 driver set failed to load thedrivers into the Windows WinPE environment. Logical drives arenot visible at restore time.

2174494S2174514

About the NetBackup 7.1 EEB listingNetBackup 7.1 Emergency Engineering Binary (EEB) Listing

14

Page 15: NB 71 EEB Listing

Table 1-1 NetBackup 7.1 EEB Listing (continued)

Emergency Engineering Binary DescriptionEtrack NumberSummary ISSUE

A change was made to address an issue that caused the followingerror. WIN32 87: The parameter is incorrect - when backingC:\Documents and Settings\

2055965S2056005

Changes have been made to improve the speed of C: drive backupsfor a Windows 2008 cluster when VSS is enabled.

2146659S2056005

The Device Configuration Wizard did not name drives correctlyafter reaching 999 drives.

2072044S2072215

CIBC needs a new 6.5.6 nbemm binary file that combines the fixesin ET2072044 and ET2073042

2126318S2072215

A change was made to provide an option to exclude public folderdatabases from Exchange 2010 DAG backups.

2024651S2024659

Reports that use the Media Retention Level column would displaytwo numbers instead of readable data.

2081940S2081949

An Oracle production database would receive corrupted blocksduring a backup. The blocks contained dbclient log info.

2130277S2053933

Duplication of a FlashBackup image from a Disk Storage unit canfails if the TIR fragment is greater than 2GB.

2141027S2141028

Trying to stage or relocate a large NDMP backup of a NetApp filerwould fail at the last TIR fragment. The failure would produce astatus 85 error.

2074944S2063646

Duplication would fail with the following error if the TIR file sizedid not match the TIR file size in the TIRheader.validate_tir_header_data:

TIR file size from catalog (4414224878) does not match the TIRfile size in the TIR header (119257582)

2108394S2063646

nbdelete would remove disk fragments from backups that aresuspended. A change was made to ensure backups would resume.

2080231S2080339

A change was made to correct an issue that caused the NetBackupResource Broker (nbrb)to loop under certain circumstances.

1296887 20812991530187

S1296912

15About the NetBackup 7.1 EEB listingNetBackup 7.1 Emergency Engineering Binary (EEB) Listing

Page 16: NB 71 EEB Listing

Table 1-1 NetBackup 7.1 EEB Listing (continued)

Emergency Engineering Binary DescriptionEtrack NumberSummary ISSUE

The NetBackup-Java Administration Console would allow edits ofthe Temporary location for log files: field when performing asnapshot restore of Exchange 2010. That issue caused a statuserror 39during the restore operation.A changewasmade to correctthis.

2158760 2174329S2054868

On a SLES 11 client, NetBackup would treat a bind-mounted filesystem /proc as a normal file systemand cause the backup tohang.

2115589S2115635

The NSORDER environment variable setting was invalid for AIXclient restores.

2023881 2041936S2024018

The NDMP backup showed the wrong value for kilobytes inNetBackup-Java Administration Console after a NetBackup 7.0.1upgrade.

2170240S2170730

The NetBackup-Java Administration Console for NetBackup 7.0.1displays time in activity monitor in a 12 hour format. A changewas made to enable the user to display time in military time.

2135271 2138445S2135964

An Exchange 2010 backup using wildcard would fail with a status130 error.

2165686S2165691

A change was made to correct an issue that caused a number ofimages to be stuck in a LIFECYCLE STATE=1 state from previousSLP backups.

1999892S1999951

A changewasmade to correct an issue that caused a post-conditionviolation. The change ensures that when a backupid presents azero (byte or block) count, the batches that are not affected areprocessed and an error noting the offendingbackupid is reported.

2037090S2037700

A change was made to address an issue that caused bpdbjobs tocore dump.

2155602S2158663

A fix wa added to correct an unexpected latency for the JobCollection data type in OpsCenter.

2147137S2147154

A change was made to address an issue that caused bpdbm to coredump.

2008738S2008783

ALinux client failed to import and produced an errormessage thatindicates an, "unable to parse client information" condition. Inaddition, it was necessary to have a fix for a Windows 2003 X64version of bmrd and a Solaris master server version to match theLinux client fix.

1856604 19449221936803

S1856638

About the NetBackup 7.1 EEB listingNetBackup 7.1 Emergency Engineering Binary (EEB) Listing

16

Page 17: NB 71 EEB Listing

Table 1-1 NetBackup 7.1 EEB Listing (continued)

Emergency Engineering Binary DescriptionEtrack NumberSummary ISSUE

A change was made to address an issue that caused bptm to coredump after the following error message was received. <16>ConnectionCache::checkProcess:

2177566S2071622

An EEB fix was created to retry a Persistent Frozen Image (PFI)backup from an existing snapshot.

1921881 1953880S1937772

A change was made to address an issue that caused a phantomsnapshot, dated 1969, to appear in the database.

1848405S1672203

A tool has been added to report orphaned snapshots that remainon the client.

1671923S1672203

A change was made to optimize duplications that failed with astatus 174 error.

2176297S2176370

A change was added to address the following error:

ADGRT "Error status:12 (-528/-528 The current log file ismissing.)"

2150159 2143811S2143830

SLPduplicationswould take 15 seconds between images for 1000'sof small images.

2051701 2101713S2051712

The vmoprcmd executable would fault when run from a RemoteAdministration Console. A change was made that enables a userto run vmoprcmd.exe from a NetBackup Remote Admin Console.

2049760S2049789

A Windows 2008 SP2 system with system partition that has nodrive letter would fail to restore. The Windows 2008 R2 systemdoes not fail.

2185530S2185548

A change was made to correct an issue that caused Snapshotbackups to fail with the following error message inbpbkar.tpc_handle_sparse: ERR - tpc_handle_sparse failed: err2067

2010280S2010665

A change was made to ensure that you can perform an individualfile restore of a VMWare backup. In addition, a change was madeto ensure the files are mapped properly after a vStorage backupcompletes with Status 0.

2075918 2191446S2076152

TheNetBackup-JavaAdministrationConsole didnot show theLimitI/O Streams option in the Change Disk Pool dialog window.

2042613S2043591

Enhancements were made to improve the Deduplication rates.2158522 2158524S2158523

17About the NetBackup 7.1 EEB listingNetBackup 7.1 Emergency Engineering Binary (EEB) Listing

Page 18: NB 71 EEB Listing

Table 1-1 NetBackup 7.1 EEB Listing (continued)

Emergency Engineering Binary DescriptionEtrack NumberSummary ISSUE

A change wasmade to correct an issue that caused nbrmms to coredump on an AIX 6.1 system.

2192229S2192397

A change was made to correct an issue that caused a Status 255error on NDMP restore.

2111988S2112081

Changesweremade to prevent a bpbkar crash fro happeningwhenan attempt is made to read ACLs on a Linux system. In addition, afix was added to address an issue that caused a backup of mountpoints with ACLs to fails with a status 130 error.

2175129 20380642173067 2149505

S2039060

While cloning a disk group using sliced disks, the cds flag shouldbe set to off.

1834662S1834922

A change was made to that the nbdecommission does not failwith the following error whenmaster server is in a cluster. Unableto obtain media sharing group

2090832 2069316S2069337

Error log entries were incomplete or corrupt and caused bperror-backstat to not report the correct job status.

2077768 21018152100707 1955507

S1955789

An enhancement was added to ensure that BMR restore for SUSE10 system on a Huawei blade server does not hang.

2026740 1875821S1842975

Need to find a solution for backup with EMC VSS Provider wherethe database and log resides in two different volumes belonging totwo disk groups.

2051054S1838593

The bpbrm vnet_async_connect() command fails if theRANDOM_PORT value is NO.

2162673S2162745

DSSU duplications would fail after upgrading to NetBackup 7.0.1.A change was added to address this issue.

2106924S2107011

A change was made to allow NBAC commands to have spaces inpasswords.

2108306S2109190

A change was added to ensure master server services are disabledafter a media server install.

2062718S2062726

A change was made to correct an issue that caused the nbproxylog to fill with the following messages:

[bplibFacadeImpl::getProcessList: NB API:

bpcr_get_process_list_rqst() failed

2092994 2089889S2089909

About the NetBackup 7.1 EEB listingNetBackup 7.1 Emergency Engineering Binary (EEB) Listing

18

Page 19: NB 71 EEB Listing

Table 1-1 NetBackup 7.1 EEB Listing (continued)

Emergency Engineering Binary DescriptionEtrack NumberSummary ISSUE

After upgrading toNetBackup7.0.1 onanHP-UX11.31 IA64 systemwith IBM'sATDDdriver andBlockposition check returns 0 atwhatshould be the end of the tape. BPTM freezes the tape with Status84.

2142743S2142751

Synthetic backups would get a File record not found in

synthetic backup error because of a streammisalignment. Thatcaused a status 238 error.

2200369 21755712161172

S2161247

On an HP SAN client, only one of two Fiber channel HBA's wouldfind the target and nbftconfig would crash in segment fault onthe Windows master server.

2154751S2154842

Fixed an issue that would occur if a user clicked on buttons in theWeek at a glance report in the dashboard. That action would sendthe user back to the logon screen.

2062550S2062584

Snapshot backupswould fail on avxsnap refresh call that resultedin a status 156 error.

2025109S2025154

A change was made to ensure that the Windows client exclude listis honored on a shared drive of a Microsoft Cluster after youupgrade.

2091959 2119112S2092274

Request for EEB with fix for both ET 2125979 and ET 21405362153889S2092274

The Windows client exclude list was not honored on the shareddrive of a Microsoft Cluster following an upgrade from NetBackup7.0 to NetBackup 7.01.

2125979S2092274

The bpimagelist and bpimmedia commands would fail with afile read failed error when a corrupt image header was present.

2074966S2075006

A change wasmade to enable you to load external host details intoOpsCenter Analytics and to be able to report on those details.

2086975S2094946

The dbbackup.exe executable crashed when the All but selectedoption and two database names were selected at the NetBackupSQL Agent user interface.

2080326S2080378

The backup job of legacy encryptionwould fail with a status 9 afterthe key file pass phrase was changed.

2124196S2124205

NDMPbackupswould endwith aStatus 84,whenEOMwas invoked.2131806S2132186

19About the NetBackup 7.1 EEB listingNetBackup 7.1 Emergency Engineering Binary (EEB) Listing

Page 20: NB 71 EEB Listing

Table 1-1 NetBackup 7.1 EEB Listing (continued)

Emergency Engineering Binary DescriptionEtrack NumberSummary ISSUE

A change was added that enables you to add users from existingdomains of the broker if OpsCenter is clustered.

2060916 2112934S2060928

A restore would fail with a status 5 because of a connection errorin vnet_bind_and_connect_extra().

2064202S1238164

Requesting 7.0.1 EEB from ET20642022132211S1238164

This EEB contained the following enhancements and fixes:

■ Fixed an issues that caused the bpdbm -consistency

command to core dump when there are corrupted images.

■ Fixed an issue that caused clients to unexpectedly duplicate tomultiple NetBackup domains in the OpsCenter database.

■ Fixed an incorrect timezone setting that caused disk mappingto not complete.

■ Fixed the Windows repair time disc.cml because it containedan invalid format for the timezone and caused a failed autodiscover.

■ Addressed an issue that caused the recovery of aWindows 2008SP2Enterprise. The recoverywould lead to a blank screenuponcompletion.

2084710 21145802120174 21144602065362

S2084752

Restoring a Web application caused additional managed paths tobe restored.

1974504S1974566

The Client Count report would return data for a Job Count.2150061S2150094

A changewasmade to resolve a catalog backup status code 2 error.2110798S2111836

A change was made to address an issue that caused bmrprep toreceive an unknown exception and a halting status 114 error.

2075958S2076233

The backint process would crash if the backint log directorywas not created.

2109712 2188729S2109878

The Remote NetBackup installation feature was not working asdocumented.

2086091S2086385

A SUSE 10 BMR restore failed because the data=writebackwas notspecified.

2142387S2142400

A restore using Fibre Transport would fail with the followingerror.ERR - Invalid TAR header found

1718862S1719441

About the NetBackup 7.1 EEB listingNetBackup 7.1 Emergency Engineering Binary (EEB) Listing

20

Page 21: NB 71 EEB Listing

Table 1-1 NetBackup 7.1 EEB Listing (continued)

Emergency Engineering Binary DescriptionEtrack NumberSummary ISSUE

AnExchange 2010DAGbackupwould fail with the following errorwhen there was a recovery database whose name occursalphabetically before the mail stores. No databases in the file listare mounted

2170086S2170104

A Mapped FullVM Backup would complete with a Status 1 andreport two RvpLdm.cpp errors and one VmdkGuest.cpp error.

1809067S1809084

A fix wasmade to address a Java exception that displayed vault jobdetails. Some of the displayed data is repeated and some ismissing.

2166731 2044866S2045697

A change was added to address an issue that caused bmrsrtadmto fail with the following message.

internal error - failed to load SRT/BI contents

for platform "x86_64-RHEL-5.4"

2070425S2070639

AVxVMsnapshot failedduringavxassistunassignprocess. Theunassign process failed because FSRM has a file handle open.

2034611 2148178S2034642

Week At A Glance reports did not sort properly. In addition, onlythe first page of results were shown when the report was exportedor emailed.

2094046S2094081

Renaming tape drives caused OpsCenter to report additional tapedrives.

2158458S2158506

Theprocedureentrypoint: !!OACE_Thread_Mutex@@QAE@PBG@Zcould not be located in the dynamix link library

vxACE_3.dll.

2150308S2150328

Clarification on the High Water Mark processing has been addedfor an AdvancedDisk storage unit .

2045109S2045647

A change was added to address an issue that caused bpjobd tocore dump in the send_file_to_monitor process.

1936394S1936491

Tapes were not being expired after all of the images on the tapeswere expired.

2174639S2174655

The tpautoconf -replace_drive command core dumps on aclustered NetBackup 6.5.5 and 6.5.6 master and media server.

2084066S2084344

Synthetic full backup would change the Read media server.1851065 2099464S1851460

21About the NetBackup 7.1 EEB listingNetBackup 7.1 Emergency Engineering Binary (EEB) Listing

Page 22: NB 71 EEB Listing

Table 1-1 NetBackup 7.1 EEB Listing (continued)

Emergency Engineering Binary DescriptionEtrack NumberSummary ISSUE

Achangewasadded that enables auserwhohas anONTAPProvideron a Windows Client, to use a Microsoft VSS provider for SCC andSS backups.

2077740S2077776

A fix was added in which an Exchange CCR backup failed if thelocal node was not available when the cluster failed over.

2162306S2162333

FlashBackup restores would fail with a block map error.1926429S1926527

A fix was made to correct and error in file theF:\VERITAS\NetBackupDB\scripts\create_nbdbspaces.sql file.

2054818S2054885

NDMP backups of a Mirapoint device would fail with a status code13.

2082693 2135605S2083057

A network interface with no route to media servers was used as aPBX endpoint.

2202693S2202703

The NetBackup-Java Administration Console presented AdvancedFilter integer-based operators for theActivityMonitor string-basedData Movement field.

2202458S2202983

Custom reports did not display dates in correct format.2042942S2043032

NetBackup 7.0 vStorage credential validation and backups did notwork if the non-default port was used by vCenter server for SSL.

2003415 2078819S2003436

The jnbSA -r 6.5 -H command from aNetBackup 7.0.1masterto a 6.5.6 master server did not work. It failed with the followingerror.bpjava-msvc is not compatible with this application version

2138777S2139203

If expmgr failed, the disk cleanup would not run again for a diskstaging storage unit. This caused the jobs to hang.

2016797S2016865

Post nbstserv recovery logic took a long time after NetBackuprestart.

1975674S1975697

The OpsCenter DBbackup.bat script on Windows validated theactive database instance instead of the backup copy. That causedthe validation to report errors.

2150397S2150469

Windows XP clients all failed for Prepare-To-Restore. TheFileToFind list was invalid.

2173294S2173489

About the NetBackup 7.1 EEB listingNetBackup 7.1 Emergency Engineering Binary (EEB) Listing

22

Page 23: NB 71 EEB Listing

Table 1-1 NetBackup 7.1 EEB Listing (continued)

Emergency Engineering Binary DescriptionEtrack NumberSummary ISSUE

The runstoredquery command returned errors during asuccessful operation. Thatwasdocumented incorrectly. In addition,it writes its output file to an unconfigured location.

2021647S2021794

The vfm_open_file_index failed and the FlashBackup job exitedwith a status 1.

1958264S1958297

VMware VCB backups would fail with a status 1and with the VFMerror set to 11.

2159395S1958297

A changewasmade to theActivityMonitor's right-clickmenu. Theproposed changewas tomove theCancelAll Jobs option away fromthe Cancel Job option to help prevent accidentally canceling alljobs.

2070587S2070585

Couldnot transfer tapeswrittenby anNDMPserver fromthemergetable into EMM database media table.

1979699S1979851

VM restore using the NetBackup-Java Administration Consolewould quietly fail with a NullPointerException being reported inlog.

2049443 2099556S2049579

Adding a VxVM patch to a Solaris 10 U6 SRT would leave it in theDAMAGED state.

1988238S1988255

The Picking List for Robot report was not showing an Expirationdate on the report.

2131482 2165675S2131518

During a restore from an SAP VxVM Instant Recovery Snapshotbackup, bprd started bpbrm on the wrong server.

2055653S2056296

A vxdg join would fail to join a split disk group.2036147S2036312

The Vault schedule did not appear in the NetBackup-JavaAdministration Console.

2074195S2074263

A change was made to add a configuration parameter to disablethe get_fqdn_hostname during FullVM restores to accommodaterestores to the vSphere inventory where short names were usedfor hosts.

2131870S2132010

Could not modify an existing schedule in a vault policy after theNetBackup-Java Administration Console was restarted.

2047268S2047710

An NDMP backup to disk operation would create a 0KB fragmentif a volume in the policy's backup selection did not exist.

1975956S1975985

23About the NetBackup 7.1 EEB listingNetBackup 7.1 Emergency Engineering Binary (EEB) Listing

Page 24: NB 71 EEB Listing

Table 1-1 NetBackup 7.1 EEB Listing (continued)

Emergency Engineering Binary DescriptionEtrack NumberSummary ISSUE

NDMPhost credentialmodification can cause unexpected deletionof the credential in NetBackup-Java Administration Console.

2010354S2010397

A changewasmade to address an issue that caused a catalog status1 error to occur.

1984489S1955778

A change was made to address an issue to exclude a busy error logfile from catalog backup.

1955505S1955778

NetBackup7.0 JavaAdministrationConsolewasmissing the roboticdetails for the drives that used the Change Drive.

2187120 2196235S2187845

The NetBackup 7.0.1 Windows Remote Administration Consolewas unable to connect to a master server.

2112063S2112110

A change wa made to address an issue that was related to multipleMedia servers runningnbdelete to cleanup the samediskvolumesduring the same time periods.

2177640S2177668

Persistent Frozen Image (PFI) Type SAP on Oracle restores wouldsucceed, however, the followingerrors areposted to thebrrestoredetail log.Unable to unmount file system

2074332S2074422

Attempting to configure a Vault catalog backup schedule with astorage unit group would fail with a status 227 error.

2144182S2144215

Exchange email attachments did not get restored if a user hadpre-NetBackup 7.0 backup images.

2065420S2065442

Installation of NetBackup was destructive to thePendingFileRenameOperations list.

2142880S2142962

Wrong (zero) media date was saved in an image fragment on theHP-UX IA-64master serverplatformwithNetBackup6.5.4 installed.

1879717S1879746

On a SolarisMaster server( only), the parent job failedwith a status5, while the child job finished successfully forGRTmessage restorefrom both DAG and standalone backups.

2071749S2054705

A change has been made to address an issue that caused nbrb tocore dump in the add_new_buffer buffer as the process approaches4 GB.

2062537S2062559

During a FlashBackup restore excessive messages were written tothe bprd logs even at a verbose level of zero.

2000243S2000990

About the NetBackup 7.1 EEB listingNetBackup 7.1 Emergency Engineering Binary (EEB) Listing

24

Page 25: NB 71 EEB Listing

Table 1-1 NetBackup 7.1 EEB Listing (continued)

Emergency Engineering Binary DescriptionEtrack NumberSummary ISSUE

OpsCenterwould send inappropriate alertswith regards to servicesthat were not running on a media server.

2023773S2023806

Upgrading to OpsCenter failing with 'Database schema isinconsistent with the released database schema'

2043496S2043520

vStorage would choose the wrong IP address for a VM.2024766S2024814

Report filter for the policy type would select the wrong number.2062609S2062702

ET2077740onlyworkswith SCCbackups, not File Systembackups.2145368S2145467

Fixes were added for an Optimized Synthetics error 610 and vmdkdeduplication ratio.

2158839S2160122

A Flashbackup restore after upgrading to 6.5.3 failed with thefollowing error.<32> bprd.sfr: transadr: assertion failed (atsfr.c.1563)

1702329 1765926S1952228

FlashBackup restore of a large number of files would hang for along time, and then fail with a status 5.

1925536 1952155S1952228

A change was made to address an issue that caused bpdbm-consistency to hang due to a corrupt image.

2011291S2011449

A change was made to correct a possible issue with the PBXcommunications in NetBackup 7.0.1. The issue was that theANY_CLUSTER_INTERFACE setting was not being honored orrecognized for a clustered NetBackup master server.

2140749S2140767

25About the NetBackup 7.1 EEB listingNetBackup 7.1 Emergency Engineering Binary (EEB) Listing

Page 26: NB 71 EEB Listing

About the NetBackup 7.1 EEB listingNetBackup 7.1 Emergency Engineering Binary (EEB) Listing

26


Recommended