Maintenance Pack NB_DMP_60_7_M.solaris.tar provides updates and fixes for Veritas NetBackup (tm) Enterprise Server / Server 6.0 NDMP Agent on Solaris platforms.

Problem

Maintenance Pack NB_DMP_60_7_M.solaris.tar provides updates and fixes for Veritas NetBackup (tm) Enterprise Server / Server 6.0 NDMP Agent on Solaris platforms.

Solution

DMP 6.0GA Pack NB_DMP_60_7_M README September 15, 2008
Requirement: NB_CLT_60_7_M
================================================================================
This Maintenance Pack should only be applied to Veritas NetBackup (tm) UNIX
servers running NetBackup for Network Data Management Protocol (NDMP).

================================================================================


=================
PACK DEPENDENCIES
=================

-- Installation of this Maintenance Pack requires version 1.33.10.18
of the Vrts_pack.install.

-- NB_CLT_60_7_M client Maintenance Pack must be installed prior to
installing this Maintenance Pack.



I. NEW FEATURES AND PLATFORM PROLIFERATIONS
II. KNOWN ISSUES
III. DOWNLOAD INSTRUCTIONS
IV. INSTALLATION INSTRUCTIONS
V. UNINSTALL INSTRUCTIONS
VI. CURRENT MAINTENANCE PACK INDEX
VII. MAINTENANCE PACK CONTENT
Conventions
Current Maintenance Pack
NB_DMP_60_7_M
Maintenance Pack History
NB_DMP_60_6_M
NB_DMP_60_5_M
NB_DMP_60_4_M
NB_DMP_60_2_M



============================================
I. NEW FEATURES AND PLATFORM PROLIFERATIONS
============================================
Many new features, enhancements, and platform proliferations have been made
to NetBackup 6.0 MP7 in general. For a complete list of these additions, refer
to the New Features and Platform Proliferations section in the NB_CLT_60_7_M
online Readme that you installed prior to installing this package.




==================
II. KNOWN ISSUES
==================

This section contains known issues with this maintenance pack that have not
yet been fixed in NetBackup. These issues will likely be fixed in future
Maintenance Packs for this version of NetBackup.

There are no known issues with this maintenance pack.




==========================
III. DOWNLOAD INSTRUCTIONS
==========================
1) Download NB_DMP_60_7_M_<6 digit number>.<platform>.tar into the
/tmp directory.

where <6 digit number> is an internal tracking identifier

where <platform> is: hp_ux, linux, rs6000, solaris

2) Extract NB_DMP_60_7_M_<6 digit number>.<platform>.tar
/bin/tar xvf NB_DMP_60_7_M_<6 digit number>.<platform>.tar

This will create the files
Vrts_pack.install
VrtsNB_DMP_60_7_M.README
VrtsNB_DMP_60_7_M.<platform>.tar.Z




=============================
IV. INSTALLATION INSTRUCTIONS
=============================
** The content of this online Readme supersedes the information in the Readme
contained in the download. **

As root on the NetBackup Server with NetBackup for NDMP:
1) Install Maintenance Pack binaries.

cd /tmp
/bin/sh Vrts_pack.install




=========================
V. UNINSTALL INSTRUCTIONS
=========================
Note: This will ONLY uninstall the Maintenance Pack from your local machine.

1) Close the NetBackup user interfaces.

Make sure the NetBackup server has no active jobs running (for
example, backups, restores, or duplications).

If a database agent is being used, such as Oracle,
ensure that the database services are stopped.

2) Change directory to the patch save directory.
Substitute the pack name for ${PACK.EN_US} in the following command:

cd /usr/openv/pack/${PACK.EN_US}/save

3) Run the un-install script:

./Vrts_pack.uninstall

4) Verify that the pack uninstalled successfully by checking
/usr/openv/pack/pack.history.

5) If necessary, restart the NetBackup and Media Manager daemons:
/usr/openv/netbackup/bin/goodies/netbackup start




==================================
VI. CURRENT MAINTENANCE PACK INDEX
==================================

This section contains a master index for all UNIX packages of Etracks that
have been fixed in this release, sorted according to the containers that
they comprise.


NB_60_7_M
---------
1128726 1145685 1146635 1150657 1172971 1178481 1194284 1175361 1196200 1160439
1191148 1193696 1197056 1201124 1186553 1201289 1200945 1193183 1186256 1202780
1181024 1046203 1188094 1193241 1200911 1196151 1204133 1194711 1203203 1203315
1204149 1203341 1196108 1206982 1149072 1203743 1206988 1209668 1141942 1210324
1181990 1205097 1157872 1028523 1193739 1202703 1139683 1213186 1210997 1213398
1194467 1198779 1163522 1194630 1186713 1159797 1215592 1215486 1213931 1146675
1213936 1217081 1019035 1003076 1199328 1173094 1211957 1209824 1210121 1219899
1206849 1204494 852979 1168028 1190482 1223027 1223019 1229928 1159536 1200897
1224637 1214052 1201393 1152608 1042411 1211653 1137917 1135737 1227823 814704
1175373 1236186 1237077 1237818 918372 1200166 1216170 1039111 1238630 1229969
1238098 1239178 1236032 1242512 1245566 1244766 1245997 1244622 1221477 1036931
1200190 1089296 1251778 1252326 1219002 1252345 1268942 1184332 1223173 1212526
1259059 1195231 1260503 1259252 1262091 1150199 1240367 1261507 1261430 1269061
1273387 1275369 1269918 1228938 1261282 1097416 1275549 1281153 1270235 1253532
1283873 1283865 1277786 1077528 1189875 1190428 1291060 1260324 1287242 1292773
1294647 1291761 1295792 1302098 1251842 1316727 1316894 1321914 1178607

NB_ADC_60_7_M
-------------
1179426 1220903 1227575 1239595 1235529 1231895 1219116 1134888 1211678 1275147
1227541 1210195 1361434

NB_BBS_60_7_M
-------------
1194900 1198426 1201794 1240183

NB_BMR_60_7_M
-------------
1201741 1212630 1213219 1219751 1222733 1231109 1228989 1212202 1175891 1195956


NB_CLT_60_7_M
-------------
1128726 1145685 1146635 1150657 1172971 1178481 1194284 1175361 1196200 1160439
1191148 1193696 1197056 1201124 1186553 1201289 1200945 1193183 1186256 1202780
1181024 1046203 1188094 1193241 1200911 1196151 1204133 1194711 1203203 1203315
1204149 1203341 1196108 1206982 1149072 1203743 1206988 1209668 1141942 1210324
1181990 1205097 1157872 1028523 1193739 1202703 1139683 1213186 1210997 1213398
1194467 1198779 1163522 1194630 1186713 1159797 1215592 1215486 1213931 1146675
1213936 1217081 1019035 1003076 1199328 1173094 1211957 1209824 1210121 1219899
1206849 1204494 852979 1168028 1190482 1223027 1223019 1229928 1159536 1200897
1224637 1214052 1201393 1152608 1042411 1211653 1137917 1135737 1227823 814704
1175373 1236186 1237077 1237818 918372 1204203 1200166 1216170 1039111 1238630
1229969 1238098 1239178 1236032 1242512 1245566 1244766 1245997 1244622 1221477
1036931 1200190 1089296 1251778 1252326 1219002 1252345 1268942 1184332 1223173
1212526 1259059 1195231 1260503 1259252 1262091 1150199 1240367 1261507 1261430
1269061 1273387 1250877 1275369 1269918 1228938 1261282 1097416 1275549 1281153
1271278 1270235 1253532 1283873 1283865 1277786 1077528 1189875 1190428 1291060
1260324 1287242 1292773 1294647 1291761 1296282 1295792 1302098 1251842 1316727
1316894 1321914 1178607

NB_DB2_60_7_M
-------------
1294774

NB_DMP_60_7_M
-------------
1152587 1213695 1222258 1214070 1235538 1233401 1249754 1257297

NB_ENC_60_7_M
-------------
1238098

NB_INX_60_7_M
-------------
1145850

NB_JAV_60_7_M
-------------
1188650 1194367 1135270 1187772 1205636 384091 1278056 1255609 1301700

NB_LOT_60_7_M
-------------
1314264

NB_NOM_60_7_M
-------------
1226692 1233746 1195149 1238422 1204000 1122893 1036931 1283800 1291729

NB_ORA_60_7_M
-------------
1226883 1224664 1294774

NB_SAP_60_7_M
-------------
1209710 1142467 1210594

NB_SMU_60_7_M
-------------
1280906

NB_VLT_60_7_M
-------------
1238369 1166277 1283692 1297162 1385494




=============================
VII. MAINTENANCE PACK CONTENT
=============================
This section contains the maintenance pack conventions, content, and historical
content that is applicable to the release.

Conventions:
------------
The following list describes the conventions used in the subsections that
following this section. Each item listed in the Current Maintenance Pack
subsection describes a feature, enhancement, or issue fixed with this
Maintenance Pack.

Description
Describes a particular problem contained in this pack.

** Description **
Describes a problem that can lead to potential data loss. Please
read these problem descriptions carefully.

Workaround
Any available workarounds to a problem are also listed. Workarounds can be
used INSTEAD of applying the patch, however, Symantec strongly recommends
the "best practice" of being at the latest available patch level.

Additional Notes
Any additional information regarding a problem is included.



Current Maintenance Pack
------------------------
Each item listed in this section describes a feature, enhancement, or change
that comprises this Maintenance Pack. Please read this section thoroughly to
understand the contents of this update.
--------------------------------------------------------------------------------
Etrack Incident = ET1152587
Associated Primary Etrack = ET1142525
Titan cases: 311-685-600

Description:
bptm would generate a Dr. Watson error when drive cleaning was run on
NDMP drives. When attempting to run drive cleaning on an NDMP drive, the
cleaning job is completed with a status 0, but bptm would generate a
Dr.Watson log.
--------------------------------------------------------------------------------
Etrack Incident = ET1213695
Associated Primary Etrack = ET1173896
Titan cases: 220-203-493 220-288-767 240-631-316 240-654-553 240-717-856
281-257-682 281-274-501 281-289-315 281-329-183 281-337-228 290-904-083
290-906-114 290-926-355 290-940-579 311-881-843 311-882-571 311-895-561
311-966-172 320-103-859

Description:
An NDMP backup would fail with the following tape positioning error.

Error:bptm:too many data blocks written, check tape/driver block size
configuration.
--------------------------------------------------------------------------------
Etrack Incident = ET1222258
Associated Primary Etrack = ET1118175
Titan cases: 240-620-995 281-127-394

Description:
Changes were added to address many malloc errors that were reported when
using NDMP, such as: ndmp_tape_execute_cdb: malloc(0) failed.

The following error occurred when running the set_ndmp_attr command:
ndmp_config_get_ext_list: malloc() failed

During normal backup activity, the following error appeared in the NDMP
log:
[ndmp_logger_vxul] ndmp_tape_execute_cdb: malloc(0) failed

This was a platform dependent issue and occurred only on AIX 5.2.
--------------------------------------------------------------------------------
Etrack Incident = ET1214070

Description:
An NDMP DAR restore fails when file names contain non-ASCII characters.

If the list of files to restore contain the special characters '{' or '}'
the restore may fail. The ndmpagent log (orgid 134) showed that the fh_info
and node values for the files is 0.

Workaround:
To avoid this issue, disable DAR for NDMP restores.
--------------------------------------------------------------------------------
Etrack Incident = ET1235538

Description:
NDMP backups would fail when there was a percent (%) character in the
backup path name.
--------------------------------------------------------------------------------
Etrack Incident = ET1233401

Description:
Verifying an NDMP backup that is greater than 4TB will fail with the
following error message.

Raw partition size gigabytes does not match for file

Workaround:
If you receive this error message, ignore it. The backup data is correct
and restores from the backup will work okay.
--------------------------------------------------------------------------------
Etrack Incident = ET1249754
Associated Primary Etrack = ET1249433
Titan cases: 220-264-336

Description:
An NDMP backup would fail with a status 99 after 24 hours. A change has
been made to increase the maximum value of the NDMP_PROGRESS_TIMEOUT
timeout to seven days.
--------------------------------------------------------------------------------
Etrack Incident = ET1257297

Description:
Duplicating a backup image over 2 TB in size would fail if you used NDMP
tape devices. The progress log would report a status 85 - media read error.
--------------------------------------------------------------------------------



Maintenance Pack History
------------------------

This section contains an accumulative list of all Maintenance Pack information
contained in previous releases.

=============
NB_DMP_60_6_M
=============
Etrack Incident = ET1135508

Description:
Restoring from a multi-path NDMP backup may hang on a file from second
or later paths.

This type of backup fails with a restore from an NDMP backup that
included two or more paths, where the first path backed up completely
on one tape, then tape spanning occurred on a subsequent path. The
restore fails if a file from the first path is selected, then a file
that is completely on the second tape is selected.

Workaround:
To avoid this issue, restore files that are all within the same backup
path. If additional files are needed, restore them in a separate job.
--------------------------------------------------------------------------------
Etrack Incident = ET1162159
Associated Primary Etrack = ET1129884
Titan cases: 281-199-021 281-218-316

Description:
Remote NDMP backups fail with the following error:

"Error ndmpagent(pid=4100) Received continue when not PAUSED, state =
ACTIVE"


Workaround:
To resolve this issue, lower logging levels and make sure the fragment
size is not too small.
--------------------------------------------------------------------------------




=============
NB_DMP_60_5_M
=============
Etrack Incident = ET863277

Description:
Disk Access Record (DAR) information is not saved if type=TAR is set using
all capital letters.

Workaround:
To avoid this issue, use lower case letters when setting the type by using
the following command: set type=tar.
--------------------------------------------------------------------------------
Etrack Incident = ET863424

Description:
Because IBM markets NetApp filers, new checks have been added to search for
either "NetApp" or "IBM" as a filer vendor.

--------------------------------------------------------------------------------
Etrack Incident = ET863343

Description:
The restore would fail to recover the requested backed up files for Hitachi
filers.
--------------------------------------------------------------------------------
Etrack Incident = ET863306

Description:
Restoring a spanned backup would display the wrong number of restored KB's.


--------------------------------------------------------------------------------
Etrack Incident = ET276146

Description:
Changes were made to enhance the performance of an NDMP DAR restore to
optimize catalog calls. These changes also improved performance on the
restore of a large number of files.
--------------------------------------------------------------------------------
Etrack Incident = ET863338

Description:
An issue exists where you are unable to verify a spanned non-NDMP image
using an NDMP drive.

Workaround:
To avoid this issue, do not use an NDMP drive to verify a spanned
non-NDMP image.
--------------------------------------------------------------------------------
Etrack Incident = ET863353
Associated Primary Etrack = ET863346

Description:
A restore failure would occur that caused bptm to send the wrong image
length to ndmpagent.
--------------------------------------------------------------------------------
Etrack Incident = ET863363

Description:
Job details for backup shows NDMP_XDR_DECODE_ERR error message, even though
the job completes successfully. This occurred only when the backup job
spans tapes.

Workaround:
If the job completed successfully, this error can be ignored.
--------------------------------------------------------------------------------
Etrack Incident = ET863403
Titan cases: 280-516-588

Description:
The selected host does not have the service BPRD operating. (Error 25)

This problem occurred on Windows. The handle count for the process
"tldcd.exe" was very high (several thousand). This resulted in a lack
of resources that caused other processes, such as bprd, to fail.

Workaround:
Stopping and starting the Device Manager Services will cause a new tldcd
process. The old tldcd process will shutdown and release all its unclosed
handles.
--------------------------------------------------------------------------------
Etrack Incident = ET863430
Titan cases: 240-172-903

Description:
An NDMP backup this is greater than 4 terabytes (TB) fails on duplication.
The following error appears in the progress log:

ERR - Unable to create data socket to receive TIR data.

Workaround:
To avoid this issue, break up the backups so that they are smaller than 4TB.
--------------------------------------------------------------------------------
Etrack Incident = ET863447

Description:
NDMP restore from an Overland tape device failed because the same
fragment was loaded twice.
--------------------------------------------------------------------------------
Etrack Incident = ET863435

Description:
It was possible that tape drives for SSO could cause a DEVICE_BUSY_ERR
error on the backup host. Retry logic was added in this maintenance
pack so that if an NDMP_DEVICE_BUSY_ERR error is received when opening
an NDMP drive, a retry will occur.
--------------------------------------------------------------------------------
Etrack Incident = ET863432
Titan cases: 290-208-339

Description:
ndmpagent dumps core if the last line in the path list is not a path.

This happens if the user incorrectly adds a "SET" line to the end of the
path list. For example:
/vol/dir_to_backup
SET HIST=n

The "SET" line must come before the path to backup. A fix was added so
that it no longer causes a core dump and instead runs the job and reports
partial success.

Workaround:
To resolve this issue, correct the path list so that it ends with a path.
--------------------------------------------------------------------------------
Etrack Incident = ET863453

Description:
An error message "write to socket returned -1" occurs on NDMP restore.

The restore is reported as successful. In fact, the restore is successful.
The error message is misleading and has been removed from the user
interface.

Workaround:
Since the restore was successful, the error message can be ignored.
--------------------------------------------------------------------------------
Etrack Incident = ET863454

Description:
The Veritas Unified Logging (VxUL) logging level for NDMP (ORGID=151) does
not change while an NDMP backup or restore is in process. A change has
been made that enables you to change to DebugLevel for NDMP so that it
takes affect while an NDMP backup or restore is in process.
--------------------------------------------------------------------------------
Etrack Incident = ET863357

Description:
A change was made to ensure that bpadm asks for Max Fragment Size on an
NDMP storage unit in the create and modify modes.
--------------------------------------------------------------------------------
Etrack Incident = ET863458

Description:
NDMP backup no longer fails a block position check when two directories are
backed up.
--------------------------------------------------------------------------------
Etrack Incident = ET863457

Description:
NDMP restores using SpectraLogic Gator fails

The NetBackup NDMP log showed an NDMP_MOVER_STOP message failing with
NDMP_ILLEGAL_STATE_ERR.


Additional Notes:
The SpectraLogic Gator did not detect that the data connection from the
data side of the 3-way backup had closed. It also did not process the
NDMP_MOVER_CLOSE message properly, as that should have brought it to a
HALTED state where the NDMP_MOVER_STOP would have been okay. And
NetBackup should have ignored all of this because the data side
reported a SUCCESSFUL status for the restore.

This fix detects the problem in the mover side and issues
NDMP_MOVER_ABORT to bring it to HALTED state.
--------------------------------------------------------------------------------
Etrack Incident = ET863443
Titan cases: 230-115-105

Description:
An NDMP backup a file that is greater than 2GB no longer causes the reported
size of that file to be incorrect in the catalog file.
--------------------------------------------------------------------------------
Etrack Incident = ET863377
Associated Primary Etrack = ET863373
Titan cases: 290-035-402

Description:
After an NDMP backup spans media, the second tape is mounted in a drive in
the same robot, however the drive is attached to a different NAS filer. The
tape mount caused the backup to fail because it should not have used a
drive that is attached to a different NAS filer.
--------------------------------------------------------------------------------
Etrack Incident = ET863289

Description:
NDMP_LOG_ERROR messages are now sent to the progress log.

When doing an NDMP backup or restore, if the NAS device detects an error
and sends NetBackup a message of type NDMP_LOG_ERROR, this message will
be displayed in the progress log. This is consistent with functionality
in pre-6.0 NetBackup.
--------------------------------------------------------------------------------
Etrack Incident = ET863382

Description:
bpduplicate would fail when using the ndmp_mover_connect method.

In NetBackup 6.0, the ndmp_mover_connect method is not used by default, so
this would only fail if this feature had been explicitly enabled. The
failure occurred when the duplicate fragments because of a maximum fragment
size or tape spanning.
--------------------------------------------------------------------------------
Etrack Incident = ET848040
Associated Primary Etrack = ET841853
Titan cases: 280-687-557 290-397-014

Description:
Incremental NDMP backups would fail with status code 99 when no data has
changed. The problem occurred because of an incremental backup that had no
changed data, and thus, was a 0-byte backup.

A change was made to add support for backup, restore, duplicate, verify, and
import of 0-byte backups.
--------------------------------------------------------------------------------
Etrack Incident = ET828518 ET959929 ET959931
Associated Primary Etrack = ET828513
Titan cases: 290-343-976

Description:
Added NDMP support for multiple NICs with multiple disjoint networks.

For example, consider the following configuration:
- Media Server with two NICs (Network Interface Cards)
- Each NIC is connected to a network that is independent of the other.
- NDMP servers on each of the networks.
- Tape drives attached to the Media Server (used for Remote NDMP backups)

Previous to this patch update, the Media Server would not be able to
perform Remote NDMP backups for all of the NDMP servers in the
configuration. It would have been able to support the NDMP servers on
one network or the other, but not on both.

With this update, a single Media Server can support multiple NICs and
multiple networks.

Another smaller part of this update is that, when writing the catalog file
to tape (which is done after every NDMP backup) and when doing duplicate,
verify, and import using NDMP drives, NetBackup now creates a listen socket
and sends it to the NDMP server to connect to. Previous to this patch, the
NDMP server would create the listen socket and NetBackup would connect to
it. This change is intended to help control firewall situations by
enabling NetBackup users to specify the port ranges used. The port ranges
that are used are specified in the "Host Properties" for NetBackup.

Additional Notes:
For most network topologies this should work without any additional
configuration of NetBackup. Where an additional configuration might be
needed is in situations where there are more than one network path to a
particular NDMP server, and one network path is preferred over another.
An example might be where there are both 100 Mbps and 1000 Mbps networks.
In such cases, the preferred network can be specified.

NOTE: These parameters effect only the NDMP data connections, they do not
effect the NDMP control connections. The NDMP control connection is used
to send/receive NDMP control messages, while the NDMP data connection is
used to transfer the backup data stream.

To specify the network path to use for NDMP data connections, create the
following file:

<installdir>/netbackup/db/config/ndmp.cfg


To specify the Media Server host name to use for all NDMP data
connections between the media Server and any NDMP host, add the following
line:

NDMP_DATA_CONNECTION_HOST_NAME=host_name

Where host_name is either xx.xx.xx.xx or the host_name as a string.


To specify the Media Server host name to use for NDMP data connections
between the Media Server and a specific NDMP host, add the following
line:

NDMP_DATA_CONNECTION_HOST_NAME_FOR_nnnn=host_name

Where nnn is the NDMP host name, and
Where host_name is either xx.xx.xx.xx or the host_name as a string.
--------------------------------------------------------------------------------
Etrack Incident = ET515960

Description:
When a NDMP backup is initiated on Windows using a local NDMP drive, and if
a write-protected tape is grabbed, the backup will hang and continuously
mount and unmount the same write-protected tape.

Workaround:
To avoid this issue, do not put a write-protected tape in the media pool.
--------------------------------------------------------------------------------
Etrack Incident = ET1042448

Description:
Snapvault backups are running has snapshot backups on the filer,
under the volume's .snapshot directory and no "sv" is present in
the snapshot name, for example:

NAS+NBU+PFI+steeljacket.min.veritas.com+snapvault+sr+vol1+
2007.05.04.14h37m35s
--------------------------------------------------------------------------------
Etrack Incident = ET1043639

Description:
Restoring files on a second tape of an NDMP backup would cause a failure.


--------------------------------------------------------------------------------
Etrack Incident = ET1052642

Description:
Added credentials from the user interface for an NDMP host failure
that occurred on HP-UX 11.11 systems.

From command line the following command would fail on HP-UX 11.11:
- "tpautoconf -verify <ndmphost>"
- "set_ndmp_attr -verify <ndmphost>"

(This failure occurred only with certain patches on HP-UX 11.11.)
--------------------------------------------------------------------------------




=============
NB_DMP_60_4_M
=============
Etrack Incident = ET646977

Description:
A backup would fail if there was a space in the user and group name
in bpdbm.
--------------------------------------------------------------------------------
Etrack Incident = ET649559
Associated Primary Etracks = ET646615

Description:
NDMP backups no longer fail with a status 84 - Cannot write TIR data to
media.
--------------------------------------------------------------------------------
Etrack Incident = ET791401
Associated Primary Etracks = ET647711

Description:
If the Media Mount Timeout was set in the Master Server properties >
Timeouts section, the backup for NDMP would fail with the following
error message.

"timed out waiting for media manager to mount volume"

Workaround:
To avoid this issue, disable the media mount timeout in the Master Server
properties > Timeouts section. For NDMP backup, the backup should execute
if this is disabled.
--------------------------------------------------------------------------------
Etrack Incident = ET784650
Associated Primary Etracks = ET829340

Description:
NetBackup communication between components that were separated by a
firewall did not work. For instance, when a master server was behind the
firewall and a media server was outside the firewall, all communication
from the master server had an internal host address that was not accessible
from outside systems.

This is the same when clients and other services are in question.

Additional Notes:
To activate NAT address replacement, systems outside of the firewall should
have the FIREWALL_IN parameter specified in their bp.conf/registry.

Format: FIREWALL_IN=hostname1,nat_address1|hostname2,nat_address2|...

Where: <hostname> is the name of the host system that needs to be accessed
and <nat_address> is the actual NAT address for the firewall to do
forwarding.
--------------------------------------------------------------------------------
Etrack Incident = ET796423
Associated Primary Etracks = ET783384

Description:
Remote NDMP performance for NetBackup 6.0 was less than half that of
NetBackup 5.x. This issue appeared to affect UNIX more than Windows, as
Windows performance was much closer to NetBackup 5.x rates. Also, this
was only a problem with GigE and high performance tape drives.

This fix brings the Remote NDMP performance rates closer to that of
Previous NetBackup versions for both UNIX and Windows.

Additional Notes:
You may also need to increase the number of buffers to 16 or 32. Use the
following to add the number of buffers desired to the file:
/user/openv/netbackup/db/config/NUMBER_DATA_BUFFERS

If you have multiple NICs and want to choose which is to be used for
the data connection to the filer, (for example, if one of them is not
1000Mbps) create the following file:
/user/openv/netbackup/db/config/ndmp.cfg
With the following line:
NDMP_DATA_CONNECTION_HOST_NAME=<host_name>

<host_name> can be either xx.xx.xx.xx or the host_name as a string.

Also, performance can be impacted by VxUL tracing. DebugLevel=4 should be
used for ndmp and ndmpagent (to avoid tracing file history which can also
cause a 2x to 3x reduction in performance).

To set DebugLevel, use the following commands:

/usr/openv/netbackup/bin/vxlogcfg -a -p nb -o ndmpagent -s
"DiagnosticLevel=5"
/usr/openv/netbackup/bin/vxlogcfg -a -p nb -o ndmpagent -s "DebugLevel=4"
/usr/openv/netbackup/bin/vxlogcfg -a -p nb -o ndmp -s "DebugLevel=4"
--------------------------------------------------------------------------------



=============
NB_DMP_60_2_M
=============

Etrack Incident = ET521071

Description:
NDMP backups do not complete after an upgrade to NetBackup 5.1 or later.

This problem can occur when doing NDMP backups to a NAS device that is on
the other side of a firewall from NetBackup. An error occurs when
NetBackup attempts to connect to the NAS device to write the catalog
information (after the backup has completed), but the error is not
reported and the job never terminates. This pack contains a fix for the
error reporting.

Workaround:
To avoid the error caused by the inability to connect across the firewall,
add the following line to the netbackup/db/config/ndmp.cfg file.

NDMP_MOVER_CLIENT_DISABLE

This workaround will impact the performance of backups that have a large
number of files.
--------------------------------------------------------------------------------
Etrack Incident = ET494976

Description:
The backup no longer fails when backing up a directory that contains
special files such as named pipe, blockdevice, and chardevice. Another
type of special file is, TYPE=tar (path based FH).

Additional Notes:
Additional Notes:
The bpbrm log would show something similar to the following:

15:53:13.321 [14506] <16> bpbrm main: db_FLIST send failed:
file read failed (13)
================================================================================


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)