Maintenance Pack NB_ADC_60_7_M.tar provides an update to Veritas NetBackup (tm) Enterprise Server Advanced Client 6.0 for HP-UX and Solaris platforms.

Problem

Maintenance Pack NB_ADC_60_7_M.tar provides an update to Veritas NetBackup (tm) Enterprise Server Advanced Client 6.0 for HP-UX and Solaris platforms.

Solution

ADC 6.0GA Pack NB_ADC_60_7_M README September 15, 2008
Requirement: NB_CLT_60_7_M
================================================================================
This Maintenance Pack provides an update to Veritas NetBackup(tm) Advanced
Client (ADC).

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


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

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

-- UNIX Client Pack NB_CLT_60_7_M 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_ADC_60_7_M
Maintenance Pack History
NB_ADC_60_6_M
NB_ADC_60_5_M
NB_ADC_60_4_M
NB_ADC_60_3_M
NB_ADC_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.

There are no known issues for this release.




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

where <6 digit number> is an internal tracking identifier

2) Extract NB_ADC_60_7_M_<6 digit number>.tar
/bin/tar -xvf NB_ADC_60_7_M_<6 digit number>.tar

This will create the files:
Vrts_pack.install
VrtsNB_ADC_60_7_M.README
VrtsNB_ADC_60_7_M.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 Advanced Client:
1) Install Maintenance Pack binaries.

cd /tmp
/bin/sh Vrts_pack.install

2) Update the NetBackup Advanced Client clients, which should
include the NetBackup master server, with the new Advanced Client
software.

Distribute the NetBackup Advanced Client software to all currently
defined clients by executing the following command:

/usr/openv/netbackup/bin/update_clients -Install_ADC <hardware> <os>

where <hardware> <os> is one of the following:

HP9000-700 HP-UX11.00
HP9000-800 HP-UX11.00
HP9000-700 HP-UX11.11
HP9000-800 HP-UX11.11
HP9000-700 HP-UX11.23
HP9000-800 HP-UX11.23
Linux RedHat2.4
RS6000 AIX5
Solaris Solaris8
Solaris Solaris9
Solaris Solaris10




=========================
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 update_clients was run after the pack was originally INSTALLED,
run it again after that pack is successfully UNINSTALLED.

6) 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 = ET1179426

Description:
The ltid daemon would become unresponsive on a master server and cause the
master to be unavailable for tape backups. A change was made to ltid to
unlock shared memory before the EMM call, to avoid a deadlock with the
robotics parent process.
--------------------------------------------------------------------------------
Etrack Incident = ET1220903
Associated Primary Etrack = ET1218116
Titan cases: 311-842-209

Description:
Offline catalog backups were failing with a status 124 when the IGNORE_XATTR
setting was configured on the Master server.

Workaround:
If you encounter this issue, remove the IGNORE_XATTR setting on the Master
server when performing the cold catalog backup.
--------------------------------------------------------------------------------
Etrack Incident = ET1227575
Associated Primary Etrack = ET1195987
Titan cases: 240-666-425 311-859-827

Description:
In NDMP backups, if the master server was only reachable using Internet
or WAN communication, some backups of large volumes would fail with a
status 23. This failure occurred because a five-minute timeout was reached.

To resolve this issue, add a new touch file in the NetBackup directory
and name the file "ndmp_connect_timeout". Add a value of the number of
minutes in seconds to the file (initial suggestion is 480).

When the value is present the following message with the specified timeout
will appear in the logs.

ndmp_net_connect: Timeout Value:
--------------------------------------------------------------------------------
Etrack Incident = ET1239595

Description:
In a network environment that was experiencing connection issues, such as
one where a router failed, the communication between bpbrm and bpfis could
be such that when bpfis attempted to read the file list it would
continually get a null string. In this case, bpfis continues to try and
read the file list, resulting in an endless loop that would quickly
exhaust disk space if logging was turned on. This change caused an empty
string to be treated like a timeout on the read.
--------------------------------------------------------------------------------
Etrack Incident = ET1235529
Associated Primary Etrack = ET1182999
Titan cases: 311-769-409

Description:
In some cases, restores of multiple Flashbackup volumes would fail when
doing single-file restores.
--------------------------------------------------------------------------------
Etrack Incident = ET1231895
Associated Primary Etrack = ET1212805
Titan cases: 230-478-184

Description:
A change was made to replace "vxadm dg version" with the parsing output
from "vxdg list".

Workaround:
To avoid this issue, make sure "vxadm dg version" gives the correct version.
--------------------------------------------------------------------------------
Etrack Incident = ET1219116
Titan cases: 230-083-542

Description:
With EMC PowerPath and VxVM 4.1 installed, bpdgclone would fail when trying
to enable the controller.
--------------------------------------------------------------------------------
Etrack Incident = ET1134888

Description:
True Image Restore (TIR) is required for a backup to a NearStore storage
unit with filesystem export enabled. The filesystem export feature
provides a filesystem export of the data set as well as improved data
de-duplication on the filer. Some users may want the improved data
de-duplication but are not interested in the filesystem export. They
also may not want to configure their policies with the overhead of TIR.
This change allows TIR to be optional for backups to a NearStore storage
unit with filesystem export.
--------------------------------------------------------------------------------
Etrack Incident = ET1211678

Description:
A NAS_Snapshot copy-back restore would fail with a truncated snapshot
pathname in the REMAP directive.
--------------------------------------------------------------------------------
Etrack Incident = ET1275147
Associated Primary Etrack = ET1114023
Titan cases: 240611709

Description:
A change was made to address a Status 190 error received from bpduplicate
when using Disk Staging and doing VxVM Offhost backups with Instant
Recovery Enabled.
--------------------------------------------------------------------------------
Etrack Incident = ET1227541
Associated Primary Etrack = ET1145949
Titan cases: 290-840-787

Description:
Duplicate jobs would not launch because the bpduplicate command would
ignore the priority switch.
--------------------------------------------------------------------------------
Etrack Incident = ET1210195

Description:
A FlashBackup of an alternate Shadow image would fail on Solaris.


--------------------------------------------------------------------------------
Etrack Incident = ET1361434

Description:
A multiple copy backup to a Nearstore P3 storage unit would fail with a
status 83 - media open error (final status 40).
--------------------------------------------------------------------------------



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

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

=============
NB_ADC_60_6_M
=============
Etrack Incident = ET1111632
Associated Primary Etrack = ET1110560
Titan cases: 220-106-633 220-107-647 220-123-952 220-124-005 220-128-090
220-134-360 220-135-424 220-141-611 220-166-641 220-195-865 230-465-751
230-486-709 240-636-320 240-638-126 240-679-234 281-188-518 281-194-083
281-218-316 281-225-395 281-226-360 281-228-919 281-229-734 281-232-785
281-251-406 290-838-026 290-849-196 290-852-756 290-879-214 290-885-868
311-667-624 311-721-571 311-757-726 320-075-784 320-080-207

Description:
NDMP Backups would fail with an error code 27 if the NUMBER_DATA_BUFFERS
file was present.

Workaround:
To resolve this issue, remove the NUMBERS_DATA_BUFFERS file.
--------------------------------------------------------------------------------
Etrack Incident = ET1118215
Associated Primary Etrack = ET1114229
Titan cases: 230-413-472

Description:
Snapvault backups would fail with a status code 156 after several hours.
In some cases, large Qtree backups would fail because a timer was reached
prematurely.
--------------------------------------------------------------------------------
Etrack Incident = ET1116287
Associated Primary Etrack = ET1095286
Titan cases: 240-626-756 281-142-668

Description:
The SnapVault secondary incremental image is not removed when the NetBackup
image expires. This issue only occurs when the images are retained for
30 days or longer.

Clean-up logic in the code would remove reference files from the NetBackup
Server. Without these files NetBackup cannot remove the snapshot images
from the secondary.

Workaround:
To avoid this issue, reduce the retention periods for Snapvault policies to
less than 30 days.
--------------------------------------------------------------------------------
Etrack Incident = ET1131098

Description:
A deadlock would occur when the JobMonitor was restarted when its separator
was being processed by the JobUpdaterThread.
--------------------------------------------------------------------------------
Etrack Incident = ET1119235 ET1137969
Associated Primary Etrack = ET1275377 ET1129823
Titan cases: 240-628-676 281-176-389 220-125-326 281-239-168 290-868-053
290-838-243

Description:
A media write error was causing status 1 and status 191 errors on
staging duplications operations after NetBackup 6.0 MP5 was applied.
--------------------------------------------------------------------------------
Etrack Incident = ET1155362

Description:
The mmcrawl utility would consume more than 1.4GB of memory, making it
unable to allocate memory and therefore not run. A change was made to
address this memory consumption issue.
--------------------------------------------------------------------------------
Etrack Incident = ET1161161

Description:
Bare Metal Restore of Linux clients goes into DDR mode even if the restore
is being carried out on the same client.

When restoring a BMR Linux client machine that has HBAs, the restore
would go into DDR mode even if the restore was carried out on the same
client and the client machine's hardware (disks) was not modified.
--------------------------------------------------------------------------------
Etrack Incident = ET1127680

Description:
Added support with FlashBackup-Windows Instant Recovery file restores
making it possible to backup file lists that contain mount points.
Also fixed a 6.0MP5 max_snapshots>1 FlashSnap snapshot IR rotation
regression.
--------------------------------------------------------------------------------
Etrack Incident = ET1152595
Associated Primary Etrack = ET1079261
Titan cases: 290-814-962

Description:
When using scripts with DB_BEGIN_BACKUP_CMD and the SnapVault option,
the scripts would not run prior to the snapshot on the SnapVault Primary
being taken.


--------------------------------------------------------------------------------
Etrack Incident = ET1170164

Description:
Oracle restore would fail with a table space larger than 2G from a
Flashsnap snap-only backup.
--------------------------------------------------------------------------------
Etrack Incident = ET791283

Description:
SAP raw partition restores using the ROLLBACK method were failing
with a STATUS = 249.
--------------------------------------------------------------------------------
Etrack Incident = ET1178736

Description:
Max_snapshot in a NAS_snapshot backup was not deleting the image or the
snapshot when it was hit.

--------------------------------------------------------------------------------
Etrack Incident = ET1183173
Associated Primary Etrack = ET1178906
Titan cases: 240-679-029

Description:
A restore of an Oracle offhost backup detected data corruption when the
database was greater than 4 GB.

Workaround:
To resolve this issue, reduce the database to less than 4 GB, or use a
local host backup method.
--------------------------------------------------------------------------------
Etrack Incident = ET1179361
Associated Primary Etrack = ET1148343
Titan cases: 220-110-886

Description:
bpdgclone does not always close file descriptors.


Workaround:
To resolve this issue, stop and then restart the NetBackup services.
--------------------------------------------------------------------------------
Etrack Incident = ET1186775

Description:
File system verification would fail if the snapshot had already been
mounted.
--------------------------------------------------------------------------------
Etrack Incident = ET1187805

Description:
Truncated messages without a trailing new-line character were being
emitted by bpfis.
--------------------------------------------------------------------------------




=============
NB_ADC_60_5_M
=============

Etrack Incident = ET866903
Associated Primary Etrack = ET776663

Description:
When running on a multi-homed client that specifies a REQUIRED_INTERFACE in
bp.conf, Advanced Client ignored the setting and used the wrong interface.
--------------------------------------------------------------------------------
Etrack Incident = ET924742

Description:
When using VSP as the Windows Open File Backup (WOFB) snapshot provider on a
Windows NT4 client, the file system backups of Windows NT4 clients may end
with partial success. VSP snapshot creation failed on Windows NT4 clients
because the VSP driver did not initialized correctly after a clean install.
--------------------------------------------------------------------------------
Etrack Incident = ET417904

Description:
NetBackup clients using Windows Open File Backup and VSP as its snapshot
provider may intermittently have some VSP cache files leftover when running
multi-streamed jobs. This was because the snapshot cleanup functionality in
the client was done at the end of a backup instead of the beginning of a
backup. Multi-streamed backups that last a long time (first stream takes
about an hour and the rest of the streams take longer than an hour) with
multiple groups of streams running at the same time may have problems
deleting VSP snapshots because of this.
--------------------------------------------------------------------------------
Etrack Incident = ET830573

Description:
The ShadowImage and TimeFinder FIMs would fail with VxVM3.5
--------------------------------------------------------------------------------
Etrack Incident = ET820206

Description:
When attempting Oracle flashsnap backups on HP-UX systems, bpfis would fail
because of SIGPIPE. The following is a snippet of the bpfis log file on the
alternate client.

12:39:29.849 [1540] <2> logparams: bpfis create -dptgt -id
oracle_vxfs_FULL_1160069964.6445 -rhost m
ack -vnet_ipc /tmp/vnet-06474160069967272180000000003-a06474 -PCB
/usr/openv/netbackup/logs/user_ops
/dbext/logs/vxbsa.1160069964.6445.files -pt 4
12:39:29.909 [1540] <4> bpfis main: INF - BACKUP START 1540
12:39:29.909 [1540] <16> bpfis sighandler: ERR - bpfis killed by SIGPIPE
12:39:29.910 [1540] <2> bpfis sighandler: INF - ignoring additional SIGPIPE
signals
12:39:29.910 [1540] <4> bpfis Exit: INF - EXIT STATUS 40: network connection
broken
12:39:29.910 [1540] <2> bpfis Exit: INF - Close of stdout complete

Workaround:
To avoid this issue, configure the master and media server using a separate
machine.
--------------------------------------------------------------------------------
Etrack Incident = ET864243

Description:
FlashBackup had an upper limit on the size of the partition that could be
backed up of two Terabytes. An enhancement has been made that increases
the size of the partition to 16 Terabytes.
--------------------------------------------------------------------------------
Etrack Incident = ET915203

Description:
After upgrading from NetBackup 5.1MP6, users were unable to list the images
from a NAS snapshot backup. Changes have been added to correct this issue.
--------------------------------------------------------------------------------
Etrack Incident = ET854608

Description:
NetBackup 6.0 should be upgraded to VxFI 4.3, Build 166
for the next maintenance pack release.
--------------------------------------------------------------------------------
Etrack Incident = ET536897

Description:
FlashBackup would recode directory nodes as possible hard links. This
caused additional overhead activity during the restore that greatly
increased the restore time.
--------------------------------------------------------------------------------
Etrack Incident = ET430491

Description:
The Offhost backup of an Oracle table space no longer fails with a
130 system error.
--------------------------------------------------------------------------------
Etrack Incident = ET1007086
Associated Primary Etrack = ET493269

Description:
Oracle Enterprise Manager (EM) does not except the SEND command and
NetBackup does not recognize the PARMS command.

A user may want to run backups through EM which only accepts the PARMS
command. At this time, Oracle does not support the SEND command through EM.
The following testing has been performed.

1. Tried using the SEND command in the EM vendor-specific field, and it
was not working.
2. When the Oracle backup is initiated from the master server through a
policy and then called the backup template using the Send command,
the backup worked. However, using PARMS, the backup failed with a
status code 230 because in the Activity Monitor it will show a
different policy that is not defined in the PARMS environment
parameters. Changing the PARMS to SEND always work.
--------------------------------------------------------------------------------
Etrack Incident = ET1015953

Description:
A change was made to upgrade this maintenance pack with an updated VxFI
build (VxFI 4.3 build 168).
--------------------------------------------------------------------------------
Etrack Incident = ET1015630

Description:
Made a change to correct a policy validation failure that occurred when
a ShadowImage snapshot method was configured.
--------------------------------------------------------------------------------
Etrack Incident = ET1017756

Description:
Dynamic linkage of some Advanced Client libraries failed with missing
symbols.
--------------------------------------------------------------------------------
Etrack Incident = ET1015630

Description:
Corrected a Snapshot verify failure that occurred on an Hitachi array. The
resulting error was, "port_convert: Cannot find port number".
--------------------------------------------------------------------------------
Etrack Incident = ET1039580

Description:
A change was made to address a bpbkar core dump issue that occurred on an
offhost backup of a raw partition because it was trying to access a file
system pointer.
--------------------------------------------------------------------------------
Etrack Incident = ET1061651

Description:
ShadowImage snapshot on an AMS500 would fail because of a character
truncation.
--------------------------------------------------------------------------------
Etrack Incident = ET1060535

Description:
The Instant Recovery snapshot rotation would not work if the master server
was on a Linux system. The log file contains the following data:

16:22:30.667 [24106] <4> delete_pfi_copy: executing cmd:
"/usr/openv/netbackup/bin/
admincmd/bpexpdate" -backupid power01_1180513348 -d 0 -copy 1 -M nbu-server
-force
16:22:30.667 [24106] <16> delete_pfi_copy: cannot execute bpexpdate to
delete image

Workaround:
Use master server on other platforms.
--------------------------------------------------------------------------------
Etrack Incident = ET1062727

Description:
bppfi core dumps during an Instant Recovery database restore and
the backup that was used for the restore has two fragments. The
first fragment is not a VxFS_Checkpoint snapshot, however the
second fragment is a VxFS_Checkpoint snapshot.

Workaround:
To resolve this issue, do not use the "auto" snapshot method.
--------------------------------------------------------------------------------



=============
NB_ADC_60_4_M
=============
Etrack Incident = ET626156

Description:
Offhost mapping of a UFS file system that is mounted on a six-disk, striped
VxVM volume became CPU bound which caused the backup throughput to be very
low.
--------------------------------------------------------------------------------
Etrack Incident = ET639044

Description:
The VSS_Transportable Frozen Image Method (FIM) would cause corruption of
the dynamic storage heap. This would lead to a crash of the bpfis process.
--------------------------------------------------------------------------------
Etrack Incident = ET770401

Description:
FlashBackup no longer fails when backing up a 1.4 TB file system.
--------------------------------------------------------------------------------
Etrack Incident = ET704749

Description:
An offhost backup failed in changed block processing with a reference
to an incorrectly formatted disk path, and the mapped device was a
stable mirror and should not have had changed blocks.
--------------------------------------------------------------------------------
Etrack Incident = ET766218

Description:
The ShadowImage FIM did not work correctly with the AMS500 and the
Tagma USP models because the serial number had been increased. This caused
the FIM to fail with messages indicating that it was unable to find the
target device.
--------------------------------------------------------------------------------
Etrack Incident = ET783447

Description:
NetBackup was upgraded to use the VxFS 5.0 shim libraries to work with a
VxFS 5.0 installation.
--------------------------------------------------------------------------------
Etrack Incident = ET793571

Description:
The bpdgclone command no longer fails on the alternate client. That
failure would produce the following error.

"Error creating snapshot (156) bpfis - error during bpdgclone"
--------------------------------------------------------------------------------
Etrack Incident = ET793576

Description:
Shadowimage snapshot delete failed when S-vols were only visible on the
alternate client.
--------------------------------------------------------------------------------
Etrack Incident = ET793563

Description:
Hardware snapshots fail when the disk group name plus the host
name are longer than 25 characters.

Workaround:
To avoid this issue, rename the disk group, and make the name shorter.
However, sometimes it may not be an option.
--------------------------------------------------------------------------------
Etrack Incident = ET796445

Description:
Upgraded NetBackup 6.0MP4 to VxFI build level 163 for all Windows
platforms.
--------------------------------------------------------------------------------
Etrack Incident = ET784650

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 = ET798218

Description:
Upgraded NetBackup 6.0MP4 to VxFI build level 164 for all Windows
platforms.
--------------------------------------------------------------------------------
Etrack Incident = ET802685

Description:
A change made to deal with inode differences for different versions of VxFS
caused file permissions to be lost.
--------------------------------------------------------------------------------
Etrack Incident = ET803811

Description:
FlashBackup backups were leaving snapshots active when the backups were
terminated at the start of the backup.

Workaround:
Using the backup configured as a snapshot backup instead of adding a CACHE=
in the filelist will reduce the chances of this error occurring.
--------------------------------------------------------------------------------
Etrack Incident = ET806048

Description:
Offhost mapping of sparse files was incorrect if the hole in the sparse
file exceeded the 1 gigabyte mapping window.
--------------------------------------------------------------------------------
Etrack Incident = ET829687

Description:
An offhost FlashBackup failed with an error 11 during segment remapping.
--------------------------------------------------------------------------------
Etrack Incident = ET831215

Description:
A FlashSnap backup of a shared Veritas (tm) Volume Manager by Symantec
(VxVM) disk group failed during snapshot deletion. The error in the
online_util log file on the primary client looked like the following:

14:51:07.556 [11175] <2> onlfi_vfms_logf: INF - -- Dumping file
/var/tmp/VfMSHAABBa40v (stderr):
14:51:07.556 [11175] <2> onlfi_vfms_logf: INF - VxVM vxdg ERROR V-5-1-4597
14:51:07.556 [11175] <2> onlfi_vfms_logf: INF - shareddg : Operation is
not supported
14:51:07.556 [11175] <2> onlfi_vfms_logf: INF - --- End of file
/var/tmp/VfMSHAABBa40v
14:51:07.557 [11175] <32> do_resync: FTL - do_resync() failed: Errno = 11
--------------------------------------------------------------------------------
Etrack Incident = ET802299

Description:
Incremental cumulative backups no longer fail with the following error.

"Retain snapshots for Instant Recovery"
--------------------------------------------------------------------------------




=============
NB_ADC_60_3_M
=============
Etrack Incident = ET613055

Description:
Implemented concurrent NetApp SnapVault qtree transfers.
--------------------------------------------------------------------------------
Etrack Incident = ET625416 ET613055

Description:
Corrections were made to the P2 concurrent transfer code for snapshots.
================================================================================



=============
NB_ADC_60_2_M
=============

Etrack Incident = ET494126

Description:
Updated the VxFI package for NetBackup 6.0 MP2.
--------------------------------------------------------------------------------
Etrack Incident = ET525943

Description:
Advanced Client VxFS_Checkpoint snapshot method could not create more than
one VxFS storage checkpoint within a second on the same file system. This
was because the VxFS storage checkpoint name was based on the local time
and �second� is the minimal resolution; thus, making the name within a
second not unique. The bpfis process error is as follows :

vxfs_ckpt_freeze: Cannot create checkpoint, status=17 - Unknown Checkpoint
API error
--------------------------------------------------------------------------------
Etrack Incident = ET524603

Description:
The file system was not getting locked and flushed when a raw snapshot
backup of a volume set, sub-volume using nbu_snap. This caused data
integrity issues when the partition was restored.
--------------------------------------------------------------------------------
Etrack Incident = ET518760

Description:
Disk group cloning would fail because Advanced Client did not recognize
different format types of the disk. Only the default disk type "cds"
would work.

The change takes place in bpdgclone.c, by adding a "format" field in the
disk attribute record. bpdgclone can now remember the type of format and
pass it to either the local or the alternate host.
================================================================================


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)