Symantec NetBackup 7.

1 Emergency Engineering Binary Guide

The software described in this book is furnished under a license agreement and may be used only in accordance with the terms of the agreement.

Legal Notice
Copyright 2011 Symantec Corporation. All rights reserved. Symantec and the Symantec Logo 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. This Symantec product may contain third party software for which Symantec is required to provide attribution to the third party (Third Party Programs). Some of the Third Party Programs are available under open source or free software licenses. The License Agreement accompanying the Software does not alter any rights or obligations you may have under those open source or free software licenses. Please see the Third Party Legal Notice Appendix to this Documentation or TPIP ReadMe File accompanying this Symantec product for more information 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 document may be reproduced in any form by any means without prior written authorization of Symantec Corporation and its licensors, if any. THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE. The Licensed Software and Documentation are deemed to be commercial computer software as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19 "Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights in Commercial Computer Software or Commercial Computer Software Documentation", as applicable, and any successor regulations. Any use, modification, reproduction release, performance, display or disclosure of the Licensed Software and Documentation by the U.S. Government shall be solely in accordance with the terms of this Agreement.

Symantec Corporation 350 Ellis Street Mountain View, CA 94043 http://www.symantec.com

Technical Support
Symantec Technical Support maintains support centers globally. Technical Supports primary role is to respond to specific queries about product features and functionality. The Technical Support group also creates content for our online Knowledge Base. The Technical Support group works collaboratively with the other functional areas within Symantec to answer your questions in a timely fashion. For example, the Technical Support group works with Product Engineering and Symantec Security Response to provide alerting services and virus definition updates. Symantecs support offerings include the following:

A range of support options that give you the flexibility to select the right amount of service for any size organization Telephone and/or Web-based support that provides rapid response and up-to-the-minute information Upgrade assurance that delivers software upgrades Global support purchased on a regional business hours or 24 hours a day, 7 days a week basis Premium service offerings that include Account Management Services

For information about Symantecs support offerings, you can visit our Web site at the following URL: www.symantec.com/business/support/ All support services will be delivered in accordance with your support agreement and the then-current enterprise technical support policy.

Contacting Technical Support

Customers with a current support agreement may access Technical Support information at the following URL: www.symantec.com/business/support/ Before contacting Technical Support, make sure you have satisfied the system requirements that are listed in your product documentation. Also, you should be at the computer on which the problem occurred, in case it is necessary to replicate the problem. When you contact Technical Support, please have the following information available:

Product release level

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 registration

If your Symantec product requires registration or a license key, access our technical support Web page at the following URL: www.symantec.com/business/support/

Customer service
Customer 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 the following 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

Support agreement resources

If you want to contact Symantec regarding an existing support agreement, please contact the support agreement administration team for your region as follows:
Asia-Pacific and Japan Europe, Middle-East, and Africa North America and Latin America customercare_apac@symantec.com semea@symantec.com supportsolutions@symantec.com

About the NetBackup 7.1 EEB 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, and available to our customers in the form of an Emergency Engineering Binary (EEB). NetBackup 7.1 contains each of these EEBs. It is possible that additional EEBs were released since this document was posted. If you do not see an EEB that you expected to see in this document, contact your Symantec NetBackup Support representative. In addition, if you require additional information about an issue in this table, contact your Symantec NetBackup Support representative. Table 1-1 Summary ISSUE
S2151061

NetBackup 7.1 EEB Listing Emergency Engineering Binary Description

Unable to perform a successful BMR restore of a Windows 2008 cluster because of the changes that were made in the way Windows Server 2008 protects service executables. Changes were made to address an issue that caused nbvault to crash and produce a status 26 error. A change was to fix an issue that caused the nbsl to core dump.

Etrack Number
2150760

S2029271

2028605

S2147024

2146758

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

Table 1-1 Summary ISSUE

S2061629

NetBackup 7.1 EEB Listing (continued) Emergency Engineering Binary Description

Improvements were made to improve the Informix logical log backup performance. For more information, about the improvements that were made, refer also to ET899832. A fix was made to address an issue that caused bmrd to loop continuously in a Linux client configuration where a disk has an EFI label. This issue caused significant CPU consumption when importing. Additional changes were made to address an issue that caused bmrd to consume too much CPU resource. That caused a Point-in-time restore never complete. When running the bplist command with the -l flag on a Windows 7.0 master server, it does not report the backup time of the files as it should. Even with the -b flag, the time field is not correct. More than 10 local drives in the file selection list cannot be backed up without an error message appearing.

Etrack Number
2061099

S2001448

2001213

S1980257

1979906

S2024901

2024848

S2089113

2089090 2191820 2191821 2191822 2118416 2090654

S2091734

A non-multiplexed Oracle restore would send a SIGUSR1 to child pid -1 signal. That caused other non-NetBackup system services to be sent a signal 16. Although NetBackup client service is running as an account that has read and write permissions to a UNC path, restores to that path using the option, restore the file using a temporary file name, does not work. Fragments for staged backups (non-SLP) were left in the EMM database when images were expired after the expiry date was reached. The bpdm -mark_as_swept command erroneously put tape fragments into the EMM database. A change was made to ensure that the user_ops/dbext/jobs/vxbsa pid files and user_ops/dbext/logs logs get cleaned up on HP-UX 11.23 IA64 and PA-RISC systems.

S2016562

2015816

S1669826

1668996

S1669826

2056075

S2186223

2154895 2186190

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

Table 1-1 Summary ISSUE

S1991878

NetBackup 7.1 EEB Listing (continued) Emergency Engineering Binary Description

Multiple changes were made to address the issues that caused the bpbkar application to fail. These failures may occur in a clustered environment, during a Shadow Copy Components backup, or when doing a backup of all local drives. Refer to the listed Etrack for more information about the failures that were fixed. A change was made to address an issue that caused an error 255 to occur when all drivers to be used during restore were removed. The process did not allow the removal of drivers that were not required. Individual file restores failed when the path was part of a nested mount point from FlashBackup-Windows images. A change was made to address an issue that caused nbpem to core dump. A fixed was added to correct an issue that caused nbpem ASSERT ((m_streams.insert(StreamPair(childId,streamNumber))).second) to fail. A change was made to address an issue that caused nbpem to core dumps because of a memory leak on a SUSE Linux 10 system. A change was made to ensure that you have to ability to connect to failover SQL2008 instances when multiple SQL server versions are present within the same Windows Cluster. A change was made to correct an issue that caused PREFERRED_NETWORK issue if some addresses were excluded. The FT media server bundle, nbfdrv64, start-up would fail on shared PCI-E, SUNW, T2000, and T5240 with the following error with an older Solaris 10 release level such as update 6: Fatal application error #0x0009 (Target-Side Application Initialization Failure) @ stdfapi.c[354] (CPU 0):

Etrack Number
1990870 1926700 2140536 2015296 1829794 2015190 2161818 2124907

S2054362

2054303

S2071154

2071131

S1993882

1993541

S1993882

2031604

S1993882

2137219

S2011221

2011198

S2137287

2137288

S1940101

1987613 1940043

S2095081

2161303

A fix was made to address an issue that occurred when a hard limit was reached on the file system. A large number of directories (32,765) in the /var/tmp/ location caused the issue. In the Windows Administration Console, you were unable to override default priority from the Vault Profile Duplication tab.

S2133338

2133009

10

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

Table 1-1 Summary ISSUE

S2037471

NetBackup 7.1 EEB Listing (continued) Emergency Engineering Binary Description

A change was made to add a wrapper or vxship implementation for vxrecover. A MEDIA_READY followed by SIGUSR1 may interrupt a legacy data socket accept. A small number of jobs were Active on the weekends when a large number of jobs usually start. SAP local restores were successful, however a fix was created to address a child backint report error to brrestore. The nbdevconfig -mergedps command does not update the image database (imageDB). When is a restore considered successful even though the total restored do not match the total requested for restore? A change was made to ensure that the nbsvcmon process does not restart processes. The monitoring had not been enabled. The tape ImageExpireDateTime is less than expiration date for the last image to expire on the tape. The NetBackup Administration Console provides an option to "unfreeze" these tapes which are not frozen. If you clicked the option, the tape returns to scratch even though there were valid images. PDF and HTML report exports do not honor the order that the columns are set to. After a backup failure the tapes from the failed backup are reused, however they fail with position errors as BPTM tries to position to the end of media (EOM). If a BPTM freezes the media the following error could occur when the physical end of the tape is reached. A EEB was created to allow an SLP to duplicate synthetics. The NetBackup-Java Administration Console for the Vault, Deferred Eject option does not populate the preview area to allow ejects. Unable to restore the GRT Exchange objects that are older than six months. A change was made to address a status 50 process aborted error that occurred after duplications started.

Etrack Number
2037201

S2060548

2060471

S2079761

2078903

S2140399

2140282

S2021738

2021721

S1947615

1947428

S2100742

2100745

S2145884

2145710

S2111915

2111910

S2072780

2166912 2072065 2140608

S2140227 S2099016

2139668 2196391 2098852 2115458

S2049556

2049361 2123756

S2115689

2115680

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

11

Table 1-1 Summary ISSUE

S2151154

NetBackup 7.1 EEB Listing (continued) Emergency Engineering Binary Description

The NetBackup Administration Console did not handle the scratch pool check box correctly. A restore of the Windows 2008 MSCS node failed when BMR was used. Upgrade form VBR 6.6 to OpsCenter 7.0 stops to process hangs, migration of original VBR records stalls. Intermittent VxSS authentication failures occurred on the media server. A change was made to address an issue that caused an occasional Status 12 message during SLP duplications. An HTML formatted report that is sent with email would arrive as an attachment rather than inline. An error occurred while fetching the report output when the second page of the Week at a Glance report is displayed. The bpVMutil would continuously restart itself if the cache file could not be updated. That caused session strain on the vCenter server. The nbdb_move with -config_only command does not update database spaces, dbspaces, with the new location. Vendor unique library handling of barcodes would cause inject operations to fail and require you to use command line interface (CLI) operations. Backups failed with a status 52 if the Media Mount Timeout is set and client deduplication is used to either deduplication or MSDP storage units. The bpdbm.exe executable in NetBackup 7.0.1 would generate an application fault after you upgraded to this version. In addition, a fix was added to ensure that bpdbm would not core dump at end of an Exchange GRT backup. The exclude and include lists were being recognized by the USER type backups. A change was made to be able to inhibit email of the empty reports that were based on conditions as was possible with VBR.

Etrack Number
2150533

S2143309

2143165

S2052931

2052905

S1980936

2044615 1980731

S1997112

1996957

S2041281

2108097 2041226

S2146621

2146566

S2027111

2027071

S2106969

2106941 2183727

S1486637

1486729 2088224

S2094820

2093914 2169140

S2090513

2183484

S2099769

2115722 2099750

S2139906

2139776

12

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

Table 1-1 Summary ISSUE

S2050461

NetBackup 7.1 EEB Listing (continued) Emergency Engineering Binary Description

The vStorage Mapped FullVM backups of the VirtualCenter would fail with the following error message.NfcFssrvrRecv: failed with code = 9 Vault ejects would fail after a 30-minute MAILSLOT_OP_TIMEOUT setting. Incremental FlashBackup jobs failed with the following error message. Cannot allocate bitmap - EXIT STATUS 36: failed trying to allocate memory The media ID was padded to six characters which caused multiple ejects from the user interface to fail. When running Vault to duplicate images, there are some duplicate jobs that queued and never started. The duplication jobs started by Vault created one bid file and did not use all available tape drives. A change was made to address an issue that caused the following NetBackupmerror:NetBackup Error: vault eject partially succeeded (288) The foreign characters that were in discovered streams caused a status 71 error for the stream and the parent job. A Solaris 9 ISO image creation failed with a dd error when using a USB attached CDROM/DVDROM device. The SQLINSTANCE $ALL keyword failed on single NIC hosts. An instance of SQL Server was not found on this client. An enhancement was made to provide an option for hot catalog backups to not follow symbolic links within the imageDB. The timestamp on the browse restore selection of SQL images was misleading. Partitions that are part of a Vault Store that include Partitions stored on EMC Centera Archivers are not protected. The bpdbjobs -report command did not show the tape, however bpdbjobs -all_columns jobid did.

Etrack Number
2123706

S2052906

2052876 2140996

S1680598

1876368 1950720 2127022 1680568 1971419

S2006387

2005609

S1935303

1935220

S1935303

2214116

S2050748

2050561

S2071022

2070712 2071122

S2060238

2060208

S2002634

2002605

S2109643

2109487

S2086916

2043217 2086766

S2071418

2071406

S2050139

2049953 2065835

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

13

Table 1-1 Summary ISSUE

S2030550

NetBackup 7.1 EEB Listing (continued) Emergency Engineering Binary Description

Skipped file names were truncated when the name starts with "System State:\", "Shadow Copy Components:\", "SYS:ETC/", or "SYS:VERITAS/". The nbpemreq -predict -legacy command was off an hour during the week that followed a daylight saving time change. Need EEB related to Etrack 1557413 back ported to NetBackup 6.5.4. Multiple changes were made to ensure that the Activity Monitor showed to proper job status information. For example, the Activity Monitor would show jobs that were terminated or ghost jobs with a status 50 error, and in some instances, some jobs that were in the queue but the details showed a done status. Adding a valid report filter caused the report to hang. bpadm was creating synthetic backups when NetBackup-Catalog cumulative incremental schedules were updated. The tpautoconf -verify command would fail with an NDMP_IO_ERR error from the NetApp filer. The vltrun -preview command failed with an invalid command parameter. The application cluster (app_cluster) server was not available for selection from within the vault policy settings. A change was made to address an issue that caused an error in revoking access of the user group for the node. GRT Exchange backups would hang or take a long time to complete. In addition, 2007 and 2010 GRT backups would exit with a status 1, OPEN DATABASE FAILED: -543 error. The NetBackup-Java Administration Console reports a parsing error while viewing or generating backup reports. The bpvmutil utility would crash when trying to fill in the resource pool and datastore information. The restore of a spanned backup would displays the wrong number of restored KB's and fail with an error code 23.

Etrack Number
2033551

S2012030

2176944 2011944

S2061676

2025957

S2061676

2155673 2130090 2070663 2089741 2171814 1557413

S1968490 S2047115

1968462 2047053

S2011616

2061876 2011596

S2116563

2116099

S2145934

2145401

S2051808

2051769

S2051711

2051693 2209840

S1880690

2090491

S2198120

2197597

S1976325

1976037 2013011

14

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

Table 1-1 Summary ISSUE

S2076232

NetBackup 7.1 EEB Listing (continued) Emergency Engineering Binary Description

The bmrprep process would change file permissions of /etc/exports and dhcpd.conf on the boot server . An enhancement has been added that enables you to collect job data that has been missed. An Incremental FlashBackup would skip empty directories and the job would complete with a status 0. A change was made to address an issue that caused the Windows NBConole to be missing the Vault and BMR Management interfaces after installing the NetBackup 7.01. Backups would fail an with error 130 if more than four EV_VAULT_STORE_DB directives were listed in the backup selection on the same policy. The OpsCenter Scheduled HTML email reports were missing data in all of the columns except for the last column. The spoold would not start. The explanation was that compactd.log could not be moved. The bpbkar exclude list entries match shorter file names, which should not match. A partial name matches. The bpresolver process would generate an application fault during an Exchange 2010 GRT restore. Changes were made to improve the time it takes to complete updates to the client configurations using the JAVA or Windows consoles. Catalog cleanup would run 170 hours on a 2.4TB catalog.

Etrack Number
2076151

S2063639

2063635

S1853696

1853682

S2111207

2110878

S2105090

2104652

S2140540

2140519

S2073971

2073963 2158198

S2072855

2072832

S2211772

2211762

S2057324

2057238

S2086545

2113882 2086529 2113784 2049184

S2049234

A change was made to address an issue that caused a VxMS error 4109 when running Optimized (exclude unused and deleted blocks) backup with vStorage API on a large vmdk. Children jobs for a multistream backup would fail, but only a subset were rerun after the failure history time elapsed. SRT using latest IBM ServRAID M1015 driver set failed to load the drivers into the Windows WinPE environment. Logical drives are not visible at restore time.

S2065832

2065758

S2174514

2174494

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

15

Table 1-1 Summary ISSUE

S2056005

NetBackup 7.1 EEB Listing (continued) Emergency Engineering Binary Description

A change was made to address an issue that caused the following error. WIN32 87: The parameter is incorrect - when backing C:\Documents and Settings\ Changes have been made to improve the speed of C: drive backups for a Windows 2008 cluster when VSS is enabled. The Device Configuration Wizard did not name drives correctly after reaching 999 drives. CIBC needs a new 6.5.6 nbemm binary file that combines the fixes in ET2072044 and ET2073042 A change was made to provide an option to exclude public folder databases from Exchange 2010 DAG backups. Reports that use the Media Retention Level column would display two numbers instead of readable data. An Oracle production database would receive corrupted blocks during a backup. The blocks contained dbclient log info. Duplication of a FlashBackup image from a Disk Storage unit can fails if the TIR fragment is greater than 2GB. Trying to stage or relocate a large NDMP backup of a NetApp filer would fail at the last TIR fragment. The failure would produce a status 85 error. Duplication would fail with the following error if the TIR file size did not match the TIR file size in the TIR header.validate_tir_header_data: TIR file size from catalog (4414224878) does not match the TIR file size in the TIR header (119257582)

Etrack Number
2055965

S2056005

2146659

S2072215

2072044

S2072215

2126318

S2024659

2024651

S2081949

2081940

S2053933

2130277

S2141028

2141027

S2063646

2074944

S2063646

2108394

S2080339

2080231

nbdelete would remove disk fragments from backups that are suspended. A change was made to ensure backups would resume. A change was made to correct an issue that caused the NetBackup Resource Broker (nbrb)to loop under certain circumstances.

S1296912

1296887 2081299 1530187

16

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

Table 1-1 Summary ISSUE

S2054868

NetBackup 7.1 EEB Listing (continued) Emergency Engineering Binary Description

The NetBackup-Java Administration Console would allow edits of the Temporary location for log files: field when performing a snapshot restore of Exchange 2010. That issue caused a status error 39 during the restore operation. A change was made to correct this. On a SLES 11 client, NetBackup would treat a bind-mounted file system /proc as a normal file system and cause the backup to hang. The NSORDER environment variable setting was invalid for AIX client restores. The NDMP backup showed the wrong value for kilobytes in NetBackup-Java Administration Console after a NetBackup 7.0.1 upgrade. The NetBackup-Java Administration Console for NetBackup 7.0.1 displays time in activity monitor in a 12 hour format. A change was made to enable the user to display time in military time. An Exchange 2010 backup using wildcard would fail with a status 130 error. A change was made to correct an issue that caused a number of images to be stuck in a LIFECYCLE STATE=1 state from previous SLP backups. A change was made to correct an issue that caused a post-condition violation. The change ensures that when a backupid presents a zero (byte or block) count, the batches that are not affected are processed and an error noting the offending backupid is reported. A change was made to address an issue that caused bpdbjobs to core dump. A fix wa added to correct an unexpected latency for the Job Collection data type in OpsCenter. A change was made to address an issue that caused bpdbm to core dump. A Linux client failed to import and produced an error message that indicates an, "unable to parse client information" condition. In addition, it was necessary to have a fix for a Windows 2003 X64 version of bmrd and a Solaris master server version to match the Linux client fix.

Etrack Number
2158760 2174329

S2115635

2115589

S2024018

2023881 2041936

S2170730

2170240

S2135964

2135271 2138445

S2165691

2165686

S1999951

1999892

S2037700

2037090

S2158663

2155602

S2147154

2147137

S2008783

2008738

S1856638

1856604 1944922 1936803

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

17

Table 1-1 Summary ISSUE

S2071622

NetBackup 7.1 EEB Listing (continued) Emergency Engineering Binary Description

A change was made to address an issue that caused bptm to core dump after the following error message was received. <16> ConnectionCache::checkProcess: An EEB fix was created to retry a Persistent Frozen Image (PFI) backup from an existing snapshot. A change was made to address an issue that caused a phantom snapshot, dated 1969, to appear in the database. A tool has been added to report orphaned snapshots that remain on the client. A change was made to optimize duplications that failed with a status 174 error. A change was added to address the following error: ADGRT "Error status:12 (-528/-528 The current log file is missing. )"

Etrack Number
2177566

S1937772

1921881 1953880

S1672203

1848405

S1672203

1671923

S2176370

2176297

S2143830

2150159 2143811

S2051712

2051701 2101713

SLP duplications would take 15 seconds between images for 1000's of small images. The vmoprcmd executable would fault when run from a Remote Administration Console. A change was made that enables a user to run vmoprcmd.exe from a NetBackup Remote Admin Console. A Windows 2008 SP2 system with system partition that has no drive letter would fail to restore. The Windows 2008 R2 system does not fail. A change was made to correct an issue that caused Snapshot backups to fail with the following error message in bpbkar.tpc_handle_sparse: ERR - tpc_handle_sparse failed: err 2067 A change was made to ensure that you can perform an individual file restore of a VMWare backup. In addition, a change was made to ensure the files are mapped properly after a vStorage backup completes with Status 0. The NetBackup-Java Administration Console did not show the Limit I/O Streams option in the Change Disk Pool dialog window. Enhancements were made to improve the Deduplication rates.

S2049789

2049760

S2185548

2185530

S2010665

2010280

S2076152

2075918 2191446

S2043591

2042613

S2158523

2158522 2158524

18

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

Table 1-1 Summary ISSUE

S2192397

NetBackup 7.1 EEB Listing (continued) Emergency Engineering Binary Description

A change was made to correct an issue that caused nbrmms to core dump on an AIX 6.1 system. A change was made to correct an issue that caused a Status 255 error on NDMP restore. Changes were made to prevent a bpbkar crash fro happening when an attempt is made to read ACLs on a Linux system. In addition, a fix was added to address an issue that caused a backup of mount points with ACLs to fails with a status 130 error. While cloning a disk group using sliced disks, the cds flag should be set to off. A change was made to that the nbdecommission does not fail with the following error when master server is in a cluster. Unable to obtain media sharing group Error log entries were incomplete or corrupt and caused bperror -backstat to not report the correct job status. An enhancement was added to ensure that BMR restore for SUSE 10 system on a Huawei blade server does not hang. Need to find a solution for backup with EMC VSS Provider where the database and log resides in two different volumes belonging to two disk groups. The bpbrm vnet_async_connect() command fails if the RANDOM_PORT value is NO. DSSU duplications would fail after upgrading to NetBackup 7.0.1. A change was added to address this issue. A change was made to allow NBAC commands to have spaces in passwords. A change was added to ensure master server services are disabled after a media server install. A change was made to correct an issue that caused the nbproxy log to fill with the following messages: [bplibFacadeImpl::getProcessList: NB API: bpcr_get_process_list_rqst() failed

Etrack Number
2192229

S2112081

2111988

S2039060

2175129 2038064 2173067 2149505

S1834922

1834662

S2069337

2090832 2069316

S1955789

2077768 2101815 2100707 1955507 2026740 1875821

S1842975

S1838593

2051054

S2162745

2162673

S2107011

2106924

S2109190

2108306

S2062726

2062718

S2089909

2092994 2089889

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

19

Table 1-1 Summary ISSUE

S2142751

NetBackup 7.1 EEB Listing (continued) Emergency Engineering Binary Description

After upgrading to NetBackup 7.0.1 on an HP-UX 11.31 IA64 system with IBM's ATDD driver and Block position check returns 0 at what should be the end of the tape. BPTM freezes the tape with Status 84. Synthetic backups would get a File record not found in synthetic backup error because of a stream misalignment. That caused a status 238 error. On an HP SAN client, only one of two Fiber channel HBA's would find the target and nbftconfig would crash in segment fault on the Windows master server. Fixed an issue that would occur if a user clicked on buttons in the Week at a glance report in the dashboard. That action would send the user back to the logon screen. Snapshot backups would fail on a vxsnap refresh call that resulted in a status 156 error. A change was made to ensure that the Windows client exclude list is honored on a shared drive of a Microsoft Cluster after you upgrade. Request for EEB with fix for both ET 2125979 and ET 2140536 The Windows client exclude list was not honored on the shared drive of a Microsoft Cluster following an upgrade from NetBackup 7.0 to NetBackup 7.01. The bpimagelist and bpimmedia commands would fail with a file read failed error when a corrupt image header was present. A change was made to enable you to load external host details into OpsCenter Analytics and to be able to report on those details. The dbbackup.exe executable crashed when the All but selected option and two database names were selected at the NetBackup SQL Agent user interface. The backup job of legacy encryption would fail with a status 9 after the key file pass phrase was changed. NDMP backups would end with a Status 84, when EOM was invoked.

Etrack Number
2142743

S2161247

2200369 2175571 2161172

S2154842

2154751

S2062584

2062550

S2025154

2025109

S2092274

2091959 2119112

S2092274 S2092274

2153889 2125979

S2075006

2074966

S2094946

2086975

S2080378

2080326

S2124205

2124196

S2132186

2131806

20

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

Table 1-1 Summary ISSUE

S2060928

NetBackup 7.1 EEB Listing (continued) Emergency Engineering Binary Description

A change was added that enables you to add users from existing domains of the broker if OpsCenter is clustered. A restore would fail with a status 5 because of a connection error in vnet_bind_and_connect_extra(). Requesting 7.0.1 EEB from ET2064202 This EEB contained the following enhancements and fixes:

Etrack Number
2060916 2112934

S1238164

2064202

S1238164 S2084752

2132211 2084710 2114580 2120174 2114460 2065362

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 to multiple NetBackup domains in the OpsCenter database. Fixed an incorrect timezone setting that caused disk mapping to not complete. Fixed the Windows repair time disc.cml because it contained an invalid format for the timezone and caused a failed auto discover. Addressed an issue that caused the recovery of a Windows 2008 SP2 Enterprise. The recovery would lead to a blank screen upon completion.

S1974566

1974504

Restoring a Web application caused additional managed paths to be restored. The Client Count report would return data for a Job Count. A change was made to resolve a catalog backup status code 2 error. A change was made to address an issue that caused bmrprep to receive an unknown exception and a halting status 114 error. The backint process would crash if the backint log directory was not created. The Remote NetBackup installation feature was not working as documented. A SUSE 10 BMR restore failed because the data=writeback was not specified. A restore using Fibre Transport would fail with the following error.ERR - Invalid TAR header found

S2150094 S2111836 S2076233

2150061 2110798 2075958

S2109878

2109712 2188729

S2086385

2086091

S2142400

2142387

S1719441

1718862

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

21

Table 1-1 Summary ISSUE

S2170104

NetBackup 7.1 EEB Listing (continued) Emergency Engineering Binary Description

An Exchange 2010 DAG backup would fail with the following error when there was a recovery database whose name occurs alphabetically before the mail stores. No databases in the file list are mounted A Mapped FullVM Backup would complete with a Status 1 and report two RvpLdm.cpp errors and one VmdkGuest.cpp error. A fix was made to address a Java exception that displayed vault job details. Some of the displayed data is repeated and some is missing. A change was added to address an issue that caused bmrsrtadm to fail with the following message. internal error - failed to load SRT/BI contents for platform "x86_64-RHEL-5.4"

Etrack Number
2170086

S1809084

1809067

S2045697

2166731 2044866

S2070639

2070425

S2034642

2034611 2148178

A VxVM snapshot failed during a vxassist unassign process. The unassign process failed because FSRM has a file handle open. Week At A Glance reports did not sort properly. In addition, only the first page of results were shown when the report was exported or emailed. Renaming tape drives caused OpsCenter to report additional tape drives. The procedure entry point: !!OACE_Thread_Mutex@@QAE@PBG@Z could not be located in the dynamix link library vxACE_3.dll. Clarification on the High Water Mark processing has been added for an AdvancedDisk storage unit . A change was added to address an issue that caused bpjobd to core dump in the send_file_to_monitor process. Tapes were not being expired after all of the images on the tapes were expired. The tpautoconf -replace_drive command core dumps on a clustered NetBackup 6.5.5 and 6.5.6 master and media server. Synthetic full backup would change the Read media server.

S2094081

2094046

S2158506

2158458

S2150328

2150308

S2045647

2045109

S1936491

1936394

S2174655

2174639

S2084344

2084066

S1851460

1851065 2099464

22

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

Table 1-1 Summary ISSUE

S2077776

NetBackup 7.1 EEB Listing (continued) Emergency Engineering Binary Description

A change was added that enables a user who has an ONTAP Provider on a Windows Client, to use a Microsoft VSS provider for SCC and SS backups. A fix was added in which an Exchange CCR backup failed if the local node was not available when the cluster failed over. FlashBackup restores would fail with a block map error. A fix was made to correct and error in file the F:\VERITAS\NetBackupDB\scripts\create_nbdbspaces.sql file. NDMP backups of a Mirapoint device would fail with a status code 13. A network interface with no route to media servers was used as a PBX endpoint. The NetBackup-Java Administration Console presented Advanced Filter integer-based operators for the Activity Monitor string-based Data Movement field. Custom reports did not display dates in correct format. NetBackup 7.0 vStorage credential validation and backups did not work if the non-default port was used by vCenter server for SSL. The jnbSA -r 6.5 -H command from a NetBackup 7.0.1 master to a 6.5.6 master server did not work. It failed with the following error.bpjava-msvc is not compatible with this application version If expmgr failed, the disk cleanup would not run again for a disk staging storage unit. This caused the jobs to hang. Post nbstserv recovery logic took a long time after NetBackup restart. The OpsCenter DBbackup.bat script on Windows validated the active database instance instead of the backup copy. That caused the validation to report errors. Windows XP clients all failed for Prepare-To-Restore. The FileToFind list was invalid.

Etrack Number
2077740

S2162333

2162306

S1926527 S2054885

1926429 2054818

S2083057

2082693 2135605

S2202703

2202693

S2202983

2202458

S2043032 S2003436

2042942 2003415 2078819

S2139203

2138777

S2016865

2016797

S1975697

1975674

S2150469

2150397

S2173489

2173294

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

23

Table 1-1 Summary ISSUE

S2021794

NetBackup 7.1 EEB Listing (continued) Emergency Engineering Binary Description

The runstoredquery command returned errors during a successful operation. That was documented incorrectly. In addition, it writes its output file to an unconfigured location. The vfm_open_file_index failed and the FlashBackup job exited with a status 1. VMware VCB backups would fail with a status 1and with the VFM error set to 11. A change was made to the Activity Monitor's right-click menu. The proposed change was to move the Cancel All Jobs option away from the Cancel Job option to help prevent accidentally canceling all jobs. Could not transfer tapes written by an NDMP server from the merge table into EMM database media table. VM restore using the NetBackup-Java Administration Console would quietly fail with a NullPointerException being reported in log. Adding a VxVM patch to a Solaris 10 U6 SRT would leave it in the DAMAGED state. The Picking List for Robot report was not showing an Expiration date on the report. During a restore from an SAP VxVM Instant Recovery Snapshot backup, bprd started bpbrm on the wrong server. A vxdg join would fail to join a split disk group. The Vault schedule did not appear in the NetBackup-Java Administration Console. A change was made to add a configuration parameter to disable the get_fqdn_hostname during FullVM restores to accommodate restores to the vSphere inventory where short names were used for hosts. Could not modify an existing schedule in a vault policy after the NetBackup-Java Administration Console was restarted. An NDMP backup to disk operation would create a 0KB fragment if a volume in the policy's backup selection did not exist.

Etrack Number
2021647

S1958297

1958264

S1958297

2159395

S2070585

2070587

S1979851

1979699

S2049579

2049443 2099556

S1988255

1988238

S2131518

2131482 2165675

S2056296

2055653

S2036312 S2074263

2036147 2074195

S2132010

2131870

S2047710

2047268

S1975985

1975956

24

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

Table 1-1 Summary ISSUE

S2010397

NetBackup 7.1 EEB Listing (continued) Emergency Engineering Binary Description

NDMP host credential modification can cause unexpected deletion of the credential in NetBackup-Java Administration Console. A change was made to address an issue that caused a catalog status 1 error to occur. A change was made to address an issue to exclude a busy error log file from catalog backup. NetBackup 7.0 Java Administration Console was missing the robotic details for the drives that used the Change Drive. The NetBackup 7.0.1 Windows Remote Administration Console was unable to connect to a master server. A change wa made to address an issue that was related to multiple Media servers running nbdelete to cleanup the same disk volumes during the same time periods. Persistent Frozen Image (PFI) Type SAP on Oracle restores would succeed, however, the following errors are posted to the brrestore detail log.Unable to unmount file system Attempting to configure a Vault catalog backup schedule with a storage unit group would fail with a status 227 error. Exchange email attachments did not get restored if a user had pre-NetBackup 7.0 backup images. Installation of NetBackup was destructive to the PendingFileRenameOperations list. Wrong (zero) media date was saved in an image fragment on the HP-UX IA-64 master server platform with NetBackup 6.5.4 installed. On a Solaris Master server( only), the parent job failed with a status 5, while the child job finished successfully for GRT message restore from both DAG and standalone backups. A change has been made to address an issue that caused nbrb to core dump in the add_new_buffer buffer as the process approaches 4 GB. During a FlashBackup restore excessive messages were written to the bprd logs even at a verbose level of zero.

Etrack Number
2010354

S1955778

1984489

S1955778

1955505

S2187845

2187120 2196235

S2112110

2112063

S2177668

2177640

S2074422

2074332

S2144215

2144182

S2065442

2065420

S2142962

2142880

S1879746

1879717

S2054705

2071749

S2062559

2062537

S2000990

2000243

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

25

Table 1-1 Summary ISSUE

S2023806

NetBackup 7.1 EEB Listing (continued) Emergency Engineering Binary Description

OpsCenter would send inappropriate alerts with regards to services that were not running on a media server. Upgrading to OpsCenter failing with 'Database schema is inconsistent with the released database schema' vStorage would choose the wrong IP address for a VM. Report filter for the policy type would select the wrong number. ET 2077740 only works with SCC backups, not File System backups. Fixes were added for an Optimized Synthetics error 610 and vmdk deduplication ratio. A Flashbackup restore after upgrading to 6.5.3 failed with the following error.<32> bprd.sfr: transadr: assertion failed (at sfr.c.1563) FlashBackup restore of a large number of files would hang for a long time, and then fail with a status 5. A change was made to address an issue that caused bpdbm -consistency to hang due to a corrupt image. A change was made to correct a possible issue with the PBX communications in NetBackup 7.0.1. The issue was that the ANY_CLUSTER_INTERFACE setting was not being honored or recognized for a clustered NetBackup master server.

Etrack Number
2023773

S2043520

2043496

S2024814 S2062702 S2145467 S2160122

2024766 2062609 2145368 2158839

S1952228

1702329 1765926

S1952228

1925536 1952155

S2011449

2011291

S2140767

2140749

26

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