Maintenance Pack NB_SMU_60_7_M.hp_11.tar provides fixes to the Veritas Storage Migrator (tm) 6.0 for UNIX on HP-UX platforms.

Problem

Maintenance Pack NB_SMU_60_7_M.hp_11.tar provides fixes to the Veritas Storage Migrator (tm) 6.0 for UNIX on HP-UX platforms.

Solution

SMU 6.0GA Pack NB_SMU_60_7_M README September 15, 2008
Requirement: NB_CLT_60_7_M
================================================================================
This Maintenance Pack provides fixes to the Veritas Storage Migrator (tm) for
UNIX (VSM).

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


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

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

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

-- This Maintenance Pack contains added support for VSM 6.0 on HP-UX 11.23.
If you are attempting to install NetBackup VSM 6.0 GA, you will receive
an error stating that VSM 6.0 is not supported on HP-UX 11.23. You must
refer to TechNote 281653 on the Symantec Support Web site for instructions
on how to install VSM 6.0 GA on an HP-UX 11.23 system.

After you have successfully installed VSM 6.0 GA, you can then install
this maintenance pack and HP-UX 11.23 will be supported.



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_SMU_60_7_M
Maintenance Pack History
NB_SMU_60_6_M
NB_SMU_60_5_M
NB_SMU_60_4_M
NB_SMU_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_SMU_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_11 or solaris_dm

2) untar NB_SMU_60_7_M_<6 digit number>.<platform>.tar

/bin/tar xvf NB_SMU_60_7_M_<6 digit number>.<platform>.tar

This will create the files:
Vrts_pack.install
VrtsNB_SMU_60_7_M.postinstall (hp_11 only)
VrtsNB_SMU_60_7_M.README
VrtsNB_SMU_60_7_M.<platform>.tar.Z




=============================
IV. INSTALLATION INSTRUCTIONS
=============================
As root on the Storage Migrator server:

1) Stop the VSM daemons and all VSM activity by running

/usr/openv/hsm/bin/migVSMshutdown

2) Install Maintenance Pack binaries.

cd /tmp
/bin/sh Vrts_pack.install

3) Restart daemons.

/usr/openv/hsm/bin/migVSMstartup




=========================
V. UNINSTALL INSTRUCTIONS
=========================
1) Stop the VSM daemons and all VSM activity by running

/usr/openv/hsm/bin/migVSMshutdown

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) Restart daemons.

/usr/openv/hsm/bin/migVSMstartup




==================================
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 = ET1280906
Associated Primary Etrack = ET1280901
Titan cases: 311-918-123

Description:
Cache of a large file fails if the primary copy volume cannot be mounted;
no attempt is made to cache from the secondary copy volume.
--------------------------------------------------------------------------------



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

This section contains an accumulative list of all maintenance pack information
contained in previous releases.

=============
NB_SMU_60_6_M
=============
Etrack Incident = ET1101108
Titan cases: 220-102-240

Description:
Consolidation ran even though an incorrect method was specified for an
input volume. This resulted in no granules being consolidated but the
volume was still recycled. The fix verifies that the correct method
has been specified for all input volumes before continuing with
consolidation.

Workaround:
To avoid this issue, make sure that the correct method is specified for
all consolidation input volumes.
--------------------------------------------------------------------------------
Etrack Incident = ET1114252
Associated Primary Etrack = ET1114136
Titan cases: 220-104-816

Description:
When run as part of the migcons process, migmdclean inappropriately
removed all dk entries from the FHDB such that any unmade copies could
not then be made.

Workaround:
Ensure that all copies have been made before running migcons to
consolidate *any* tape or optical volumes.
--------------------------------------------------------------------------------
Etrack Incident = ET1157026
Associated Primary Etrack = ET1137938
Titan cases: 220-109-400

Description:
Consolidation (migcons) did not validate the output method and volset.
This could result in consolidation to an unconfigured method.volset or
both copies of file data residing on the same tape.
--------------------------------------------------------------------------------




=============
NB_SMU_60_5_M
=============

Etrack Incident = ET862332
Titan cases: 230-102-748

Description:
A problem can occur when a tape written by VSM on an SGI (IRIX) system is
read by VSM on a Solaris or HP-UX system. When the last granule for the
file contains an odd number of bytes, and when the last byte has the top
bit set, the checksum calculation on SGI differs from the checksum
calculation on Solaris or HP-UX by 1. This will cause a cache of the
file on Solaris or HP-UX to fail with a CRC error.

The fix is to detect this "off by 1" condition in migcopy and to allow the
checksum difference. When the off by one condition occurs, the following
two INFO messages are logged in the HSM log.

1/27 17:00:42 [5345]migcopy[5346]: INFO: On media crc 3579 != 3580 current crc
for Handle 3E8M1974A at offset 0x0.
01/27 17:00:42 [5345]migcopy[5346]: INFO: The difference will be ignored -
assuming the granule came from IRIX.

Workaround:
You can use the "-c" option on migstage to cache a file back and ignore crc
errors. This allows the "manual" cache of such a file on a non-SGI platform.
--------------------------------------------------------------------------------
Etrack Incident = ET866960
Associated Primary Etrack = ET861002
Titan cases: 220-082-818

Description:
This fix ensures that the VOLDB does not get truncated if the database
file system fills during a merge operation.
--------------------------------------------------------------------------------
Etrack Incident = ET993032
Associated Primary Etrack = ET992352
Titan cases: 220-090-707

Description:
Files smaller than the configured slice size could show as "PURGED"
even though all of the data was on disk.
--------------------------------------------------------------------------------
Etrack Incident = ET966608
Associated Primary Etrack = ET960560
Titan cases: 220-088-901

Description:
migtrans kept the VOLDB open, holding a lock on the VOLDB.LK file, for
the duration of its run. This prevented nospace processing, if necessary,
from being able to run to completion because migmerge could not get a lock.
--------------------------------------------------------------------------------
Etrack Incident = ET1016066

Description:
migsetdb sometimes logged a spurious "FHDB not locked" message and in some
cases could get into an infinite loop when trying to set a volume to be empty.
--------------------------------------------------------------------------------
Etrack Incident = ET1012172
Associated Primary Etrack = ET1010994
Titan cases: 220-094-910

Description:
migsa would hang at login if the output of bpminlicense exceeded
8192 characters.

Workaround:
Run "bpminlicense -verbose | wc" to check if the bpminlicense output exceeds
8192 characters. If that is the case, then there are two possible workarounds.
If migsa is hung, use "ps" to find the bpminlicense process and kill it.
migsa will then come up okay, but it will not know that Vault is licensed
(which is probably not a problem for most users).

Once migsa is not hung, you can use the NetBackup-Java Administration Console
to delete any unnecessary/redundant licenses (if there are any) to try to
reduce the amount of output that bpminlicense generates.
--------------------------------------------------------------------------------
Etrack Incident = ET1078477

Description:
The VSM Java GUI (migsa) incorrectly grays out commands when it is
connected to the file system primary node in a cluster.
--------------------------------------------------------------------------------




=============
NB_SMU_60_4_M
=============
Etrack Incident = ET649439

Description:
It is possible for a DMAPI read-managed region to exist on a portion of a
file that is actually still on disk. With Veritas File System (VxFS)
levels 3.5 and earlier this is not a problem. With Solaris VxFS 4.0 (and
later releases) this causes a problem when a process attempts to read the
file.

The VSM daemon migd loops forever processing the event, and the event
is continually regenerated.

If this happens, the following type of entries will be seen in the
Global VSM log (/tmp/hsm.log)


01/27 15:12:40 [1]migd[29660]: INFO: token=4559 DM_EVENT_READ (17),
offset=0 len =8192 sum=8192 dmapi handle=
00000000045cc738000e114000000000000000002cc64a4b0000010000000000

01/27 15:12:40 [1]migd[29660]: INFO: token=4561 DM_EVENT_READ (17),
offset=0 len =8192 sum=8192 dmapi handle=
00000000045cc738000e114000000000000000002cc64a4b0000010000000000

etc....

This is a problem on Solaris only because VxFS 4.0 is not
supported on HP-UX systems.
--------------------------------------------------------------------------------
Etrack Incident = ET649441

Description:
The migcat command fails on a file that has been moved to a different
directory (or renamed). It exits immediately and the log shows:

02/16 16:55:23 [29646]migin[29650]: starting reload of file 1F40MB85C16
02/16 16:55:23 [29646]migin[29650]: proc_start
/usr/openv/hsm/bin/admincmd/migcopy
02/16 16:55:23 [29650]migcopy[29654]: Streaming -M -s 1846908 -t 1 -o user8
/tmp/miginlvaq65
02/16 16:55:23 [29650]migcopy[29654]: reading from /tmp/miginlvaq65
02/16 16:55:23 [29650]migcopy[29654]: ERROR: copy_file: dm_path_to_handle
failed for
02/16 16:55:23 [29650]migcopy[29654]: perror 2: No such file or directory
02/16 16:55:23 [29650]migcopy[29654]: REPORT: 1F40MB85C16 1 5071 3 0 0 0 11533
02/16 16:55:23 [29650]migcopy[29654]: ERROR: Failed to copy 0xB85C16; tret = 3
02/16 16:55:23 [29650]migcopy[29654]: ERROR: copy_for_method() ret=3
02/16 16:55:23 [29650]migcopy[29654]: Finished 3
02/16 16:55:23 [29650]migcopy[29654]: INFO: Memory Used = 22 pages (8192
bytes/page)

Note that migcat calls migin which calls migcopy. The error is actually
in program migcopy.

Workaround:
If the file is moved back then the migcat command works.

Additional Notes:
Note that although the "migcat" command is used to demonstrate the problem,
the fix is actually in program "migcopy".
--------------------------------------------------------------------------------
Etrack Incident = ET649444

Description:
A memory leak caused migmdclean to fail for large databases.
--------------------------------------------------------------------------------
Etrack Incident = ET649446

Description:
"migconfg <hsmname>" deletes the <hsmname> entry from the VSM global
configuration file.

Workaround:
Always specify either "-a" or "-d", whichever is
appropriate, to add or delete an entry from the global
configuration file.
--------------------------------------------------------------------------------
Etrack Incident = ET649447

Description:
migsweep might never select any files for migration. This problem only
occurred when running Solaris 9 (or higher) with VxFs 5.0 (or higher).
--------------------------------------------------------------------------------
Etrack Incident = ET649448 ET771355 ET791706

Description:
The migmdclean command lacked knowledge of optical platter partner
sides. This fix adds logic to make sure that one side cannot be
removed from the VOLDB unless the partner side is equally eligible
to be removed from the VOLDB. If the partner is not removable, then
the first side will be marked with the "dead" flag but will be retained
in the VOLDB.

This fix also has logic similar to what was in releases prior to 6.0,
to make sure that the referenced volumes (whether tape or optical) do
not appear in any DVDB files that might be left over from unfinished
migrations.

Note that the migcons command uses migmdclean and thus is affected by
this fix.

Finally, a change has been made that fixes an error in the migcons script
which produced extra log messages due to an incorrect usage of the
migmdclean command.

Workaround:
When using the migcons or migmdclean commands for optical platters,
specify both sides of the platter rather than just one side. In the case
of the VSM-Java user interface, you can use the new command for stripes to
consolidate multiple volumes in a single operation, but should avoid the
old command to consolidate a single volume.
--------------------------------------------------------------------------------
Etrack Incident = ET649451

Description:
When backing up files on a VSM managed file system, bpbkar would keep the
FHDB open and locked, which would lock out all VSM activity for the
duration of the backup.

Workaround:
To avoid this issue, do not run NetBackup backups and VSM processes
concurrently.
--------------------------------------------------------------------------------
Etrack Incident = ET797249

Description:
On an HP-UX system migcopy would core dump when trying to select a new
tape from the HSM pool.

Workaround:
To avoid this issue, use migreg to pre-register media for an HSM before
migrating and copying files.



=============
NB_SMU_60_2_M
=============
Etrack Incident = ET416587

Description:
A problem existed where migcopy would get into a loop and continue to
re-issue log messages. This can happen is a file is removed while
it is being cached.
This condition has been corrected and no longer exists.
--------------------------------------------------------------------------------
Etrack Incident = ET498537

Description:
When failing over in a clustered environment, HSM sometimes had
missing or duplicate entries in the global configuration file,
/usr/var/openv/hsm/database/migconfg.
--------------------------------------------------------------------------------
Etrack Incident = ET427764

Description:
The migrate command failed with an open error when run using the
ftp "quote site exec" feature.
--------------------------------------------------------------------------------
Etrack Incident = ET513667

Description:
When there was a lot of caching from tape activity, a migcopy process
running on a multi-processor machine could hang while holding a lock
on the MOTAB, causing all other processes that needed MOTAB access to
be blocked.
--------------------------------------------------------------------------------
Etrack Incident = ET534184

Description:
Added support for HP-UX 11i v2 (11.23) on PA-RISC by installing the
necessary migattr driver.
================================================================================


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)