Maintenance Pack NB_BBS_60_6_M.hp_ux.tar provides updates and fixes for Veritas NetBackup (tm) Enterprise Server / Server 6.0 Bare Metal Restore Boot Server on HP-UX platforms.

Problem

Maintenance Pack NB_BBS_60_6_M.hp_ux.tar provides updates and fixes for Veritas NetBackup (tm) Enterprise Server / Server 6.0 Bare Metal Restore Boot Server on HP-UX platforms.

Solution

BBS 6.0GA Pack NB_BBS_60_6_M README February 7, 2008
Requirement: NB_CLT_60_6_M
Corequirement: NB_BMR_60_6_M
Deleted: usr/openv/netbackup/baremetal/server/data/createsrt.conf
================================================================================
This Maintenance Pack provides fixes for Veritas NetBackup (tm) Bare Metal Boot
Server(BBS).

This NB_BBS_60_6_M Maintenance Pack must be downloaded and installed on all
Bare Metal Restore (BMR) Boot Servers if and when the NB_BMR_60_6_M Maintenance
Pack is installed on the master server.
================================================================================


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

-- NB_CLT_60_6_M_<6 digit number>.tar must be installed before this
Maintenance Pack is installed.

-- Only if Bare Metal Restore is installed,
NB_BMR_60_6_M_<6 digit number>.<platform>.tar must be installed after
this Maintenance Pack is installed.

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


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_BBS_60_6_M
Maintenance Pack History
NB_BBS_60_5_M
NB_BBS_60_4_M
NB_BBS_60_3_M
NB_BBS_60_2_M



============================================
I. NEW FEATURES AND PLATFORM PROLIFERATIONS
============================================
Many new features, enhancements, and platform proliferations have been made
to NetBackup 6.0 MP6 in general. For a complete list of these additions, refer
to the New Features and Platform Proliferations section in the NB_CLT_60_6_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 the NB_BBS_60_6_M_<6 digit number>.<platform>.tar and
NB_CLT_60_6_M_<6 digit number>.tar files into the
/tmp directory,

where <6 digit number> is an internal tracking identifier

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


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

This will create the files:
Vrts_pack.install
VrtsNB_BBS_60_6_M.README
VrtsNB_BBS_60_6_M.postinstall
VrtsNB_BBS_60_6_M.postuninstall
VrtsNB_BBS_60_6_M.<platform>.tar.Z




===============================
IV. INSTALLATION INSTRUCTIONS
===============================
** Some recent changes have been made to the following installation procedure
for this product. The content of this online Readme supersedes the information
in the Readme contained in the download. **

NOTE: Click on the "Download Now" link, near the bottom of this document
prior to running the following installation procedure for this pack.

As root on the Bare Metal Boot Server:

1) Install Maintenance Pack binaries.

cd /tmp
/bin/sh Vrts_pack.install

2) The Vrts_pack.install script will prompt you to restart daemons.
Otherwise, after the pack installation has completed, run:

/usr/openv/netbackup/bin/goodies/netbackup start

If this machine is a BMR boot server, then also run:

/usr/openv/netbackup/bin/rc.bmrbd start

and then, after the master server has been patched and is back up, run:

/usr/openv/netbackup/bin/bmrsetupboot

3) The pack install logs can be found in /usr/openv/pack/pack.history once the
installation is complete.



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

Notes on uninstalling the Bare Metal Restore Maintenance Packs:
---------------------------------------------------------------
- Uninstalling BMR 6.0 Maintenance Packs on the boot server

Partial AIX 5.3 support has been available since NetBackup 6.0 MP2 with
limitations described in Symantec TechNote number 283726. You can view
this TechNote on the Symantec Support Web site, using the following URL:

http://entsupport.symantec.com/docs/283726

If NetBackup 6.0 MP4 is uninstalled from any BMR component (master server,
boot server, or client) full support for AIX 5.3 and Solaris 10 clients
will no longer be available.

- Uninstalling the BMR 6.0 MP6 on the boot server

If the BMR boot server is uninstalled to a version before NetBackup 6.0 MP2
(that is, 6.0 MP1 or 6.0GA), then there are circumstances where shared
resource trees (SRTs) will become unusable. These conditions are specific
to uninstall scenarios and do not apply if you do not uninstall. These
specific circumstances are described below:

- Any SRT created from a 6.0 MP2 (or higher) boot server will not be
usable after you uninstall to versions 6.0 MP1 or 6.0 GA. These SRTs
will have to be recreated after the uninstall is complete.

- SRTs created from a 6.0 MP1 or 6.0 GA boot server have potential to
become unusable. If the BMR boot server is upgraded to 6.0 MP2 or
higher, and then the BMR boot server is uninstalled to 6.0 MP1 or 6.0 GA,
then these SRTs become unusable and must be recreated when the uninstall
is complete.


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

6) If necessary, restart the BMR boot server daemon:

/usr/openv/netbackup/bin/rc.bmrbd 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_6_M
---------
819221 1065715 1133900 971561 1051431 1064859 917571 1050256 1077696 1047273
786040 1086515 962767 937157 971736 1019102 1060918 1075048 1075976 1101998
1110609 1102522 1108542 1112393 1099114 1089269 1102716 1081386 1118152 1053711
1122376 1056577 1016205 1103635 1032459 1122873 1078507 1081410 856463 1119141
609282 788886 1125132 1074817 701767 1058587 930868 1124179 1128964 1115039
1061995 1032486 993132 1077799 1125794 1034245 991063 1067776 1062667 1129777
1130930 1131165 1131156 1101047 999338 862454 1059861 1132293 1072957 1087582
834749 1133604 1131174 1131176 1131169 1064771 1096991 1118074 1127677 1124931
1098793 1131177 1131183 1094037 1131285 1128915 1136368 1052440 1054432 1129714
1054522 1122310 1016365 1030320 1138853 1051726 1139766 1107694 1138823 1141194
1049452 1143290 1141860 1131162 1078652 1141801 1146112 1145873 1141129 1043447
1150050 1137310 1154517 1154458 829241 1152641 1142057 1157508 1077555 1161182
1161349 1163510 1161334 1167061 1166792 1150787 1151846 1174720 1162317 1159724
1177687 1173328 1176655 1176304 1177982 1177072 1178397 1140137 1183648 1176200
1182020 1177985 1182062 1173920 1186192 1187051 1165566 1190469 1143454 1055679
1188445 1190635 1190602 1188080 1198270 1210874

NB_ADC_60_6_M
-------------
1111632 1118215 1116287 1131098 1119235 1137969 1155362 1161161 1127680 1152595
1170164 791283 1178736 1183173 1179361 1186775 1187805

NB_BBS_60_6_M
-------------
1113798 1128744 1134158 1091226

NB_BMR_60_6_M
-------------
1100826 1116059 1109594 1115944 1119044 1130594 1131126 602147 1162774 1148909
1172182 1171778 1166347 1159518 1160487 1177593 1182143 1181897

NB_CLT_60_6_M
-------------
819221 1065715 1133900 971561 1051431 1064859 917571 1050256 1077696 1047273
786040 1086515 962767 937157 971736 1019102 1060918 1075048 1075976 1101998
1110609 1102522 1108542 1112393 1099114 1089269 1102716 1081386 1118152 1053711
1122376 1056577 1016205 1103635 1032459 1122873 1078507 1081410 856463 1119141
609282 788886 1044598 1126542 1126545 1125132 1074817 701767 1058587 930868
1124179 1128964 1115039 1061995 1032486 993132 1077799 1125794 1034245 991063
1067776 1062667 1129777 1130930 1131165 1131156 1101047 999338 862454 1059861
1132293 1072957 1087582 834749 1133604 1131174 1131176 1131169 1064771 1096991
1118074 1127677 1124931 1098793 1131177 1131183 1094037 1131285 1128915 1136368
1120743 786841 1052440 1054432 1129714 1054522 1122310 1016365 1030320 1138853
1051726 1139766 1107694 1138823 1141194 1049452 1143290 1141860 1131162 1078652
1141801 1146112 1145873 1141129 1043447 1150050 1137310 1154517 1154458 829241
1152641 1142057 1157508 1077555 1161182 1161349 1163510 1161334 1167061 1168990
1166792 1150787 1151846 1172601 1002113 1174720 1162317 1159724 1177687 1173328
1176655 1176304 1177982 1177072 1178397 1140137 1183648 1176200 1182020 1177985
1182062 1173920 1186192 1187051 1165566 1190469 1143454 1055679 1188445 1190635
1190602 1188080 1198270 1210874

NB_DB2_60_6_M
-------------
1014122 1152840

NB_DMP_60_6_M
-------------
1135508 1162159

NB_ENC_60_6_M
-------------
1172601

NB_INX_60_6_M
-------------
1112364

NB_JAV_60_6_M
-------------
1096255 1113358 1066322 1066330 1067652 1039772 1026840 1115060 1135357 1137877
1173731 1179942

NB_LOT_60_6_M
-------------
1095195 1075535 969293 1075540 1060843 1075552 1129723 1154418 1167648

NB_NOM_60_6_M
-------------
1131094 1131134 1131137 1131103 1131138 1131108 1137125 1171031 1167658 1167639
1170302 1186173

NB_ORA_60_6_M
-------------
1095133 1173881

NB_SAP_60_6_M
-------------
642819 637916 1082843

NB_SMC_60_6_M
-------------
1078643

NB_SMU_60_6_M
-------------
1101108 1114252 1157026

NB_SYB_60_6_M
-------------
1112364 1115046

NB_VLT_60_6_M
-------------
1104857 1075835 619266 1051239 1054735 1168696 1169329 1160350




=============================
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 = ET1113798
Associated Primary Etrack = ET1113617
Titan cases: 220-104-735

Description:
A shared resource tree (SRT) modification can reach in the inconsistent
state if the NetBackup client or NetBackup client maintenance pack is
installed twice. This problem was encountered with NetBackup 6.0MP4. The
user sees the following error:

[Error] V-125-111 Internal error - SRT state is inconsistent. Cannot
proceed.

The log file entry would look like the following:

8/15/2007 03:58:27.851 [createSrt.cpp:bmrmain()] g_SrtContents=33
8/15/2007 03:58:27.851 [Error] V-125-111 Internal error - SRT state
is inconsistent. Cannot proceed.
--------------------------------------------------------------------------------
Etrack Incident = ET1128744
Titan cases: 311-687-198

Description:
The HP-UX boot server process bmrbd fails with an exit code 127 during
a prepare to restore operation.

Workaround:
To avoid this issue, stop bmrbd on the HP-UX boot server and be sure
/usr/sbin is in the PATH environment variable. Then restart bmrbd.
--------------------------------------------------------------------------------
Etrack Incident = ET1134158
Associated Primary Etrack = ET1131768
Titan cases: 230424864

Description:
The creation of a media boot CD ISO image for an AIX system fails with
a mkcd error when running bmrsrtadm on a Shared Resource Tree that is
AIX version 5.3.0.50 or higher.

Workaround:
To resolve this issue, perform the following steps.

1) Create a temporary file (<tempFile>) with the following:
CuDv:
name = "cd0"
status = 1
chgstatus = 2
ddins = ""
location = ""
parent = ""
connwhere = ""
PdDvLn = ""

2) Run "ODMDIR=${SRTROOT.EN_US}/usr/lpp/bos/inst_root/etc/objrepos
/usr/bin/odmadd <tempFile>"
- Where ${SRTROOT.EN_US} is the top level of the Shared Resource Tree

This adds the missing stanza to the ODM database in the Shared Resource
Tree.
--------------------------------------------------------------------------------
Etrack Incident = ET1091226

Description:
The SuSE 8 client fails to restore because of a scsiLoadOrder error.

Workaround:
To avoid this issue, remove "scsi_mod" and "sd_mod" from the
scsiLoadOrder list in the boot server file
/tftpboot/bmr/<hexaddress>.info file.
--------------------------------------------------------------------------------



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

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

=============
NB_BBS_60_5_M
=============
Etrack Incident = ET862340

Description:
Copying Solaris 10 Shared Resource Trees (SRT's) would fail if they had
packages or patches added to them because of a zone lock-file that was
left behind from pkgadd operation.

Workaround:
To avoid this issue, remove any ${SRTROOT.EN_US}/tmp/.ai-pkg.zone.lock-*
files from the Shared Resource Tree (SRT) after a package or patch
has been installed into the SRT.
--------------------------------------------------------------------------------
Etrack Incident = ET918447

Description:
BMR no longer creates multiple boot server records for the same boot server.
--------------------------------------------------------------------------------
Etrack Incident = ET968569

Description:
A change was made to correct and error that caused the creation of a media
Shared Resource Table (SRT) to fail on an AIX system.
--------------------------------------------------------------------------------
Etrack Incident = ET993246

Description:
The Linux client restoration no longer fails while trying to bring up
the network interfaces.
--------------------------------------------------------------------------------
Etrack Incident = ET1004000

Description:
Added a missing env command so that bmrsrtadm is able to apply the
NetBackup 6.0 MP5 client patch into the SRT.

Workaround:
None.
--------------------------------------------------------------------------------
Etrack Incident = ET1003978

Description:
Windows 2003 SP2 can't be added to a Legacy (DOS) Shared Resource Tree.
--------------------------------------------------------------------------------
Etrack Incident = ET1016277

Description:
bmrsrtadm would fail while applying a NetBackup client maintenance pack to
the SRT for an AIX 5.1 SRT that has had an AIX maintenance pack installed.
--------------------------------------------------------------------------------
Etrack Incident = ET1020340

Description:
The Windows DOS Media Boot would stop the restore process
because of a failure in cmdlines.exe.
--------------------------------------------------------------------------------
Etrack Incident = ET1048241
Associated Primary Etrack = ET1041371

Description:
Windows client no longer fails to restore if the original
system drive was X.
--------------------------------------------------------------------------------



=============
NB_BBS_60_4_M
=============
Etrack Incident = ET589226
Description:
Restore logs on the master server did not contain the time value. Only the
date was shown.
--------------------------------------------------------------------------------
Etrack Incident = ET507217
Description:
After patching the BMR boot server and running the bmrsetupboot command, the
boot server version in the BMR node in the NetBackup Administration Console,
and the output of 'bmrs -o list -r bootserver' command, were expected to be
updated, however, version 6.0.0.0 was the version that appears.
--------------------------------------------------------------------------------
Etrack Incident = ET565954
Description:
Creation of Solaris 8 Shared Resource Trees (SRTs) on a Solaris 10 boot
server would cause an unfriendly user message to print.
--------------------------------------------------------------------------------
Etrack Incident = ET567284
Description:
Media SRTs could not be created if the VRTSlic package was installed in
the SRT.
--------------------------------------------------------------------------------
Etrack Incident = ET594189
Description:
BMR restores of AIX 5.3 clients, while using the Media Boot feature, would
always fail with an error indicating non-existing ODM classes.
--------------------------------------------------------------------------------
Etrack Incident = ET594173
Description:
Unfriendly warnings are no longer displayed during restores.
--------------------------------------------------------------------------------
Etrack Incident = ET595564
Description:
Could not use the media boot to restore Solaris 10, Update 1 clients.
--------------------------------------------------------------------------------
Etrack Incident = ET598114
Description:
bmrsavecfg failed to collect system information on servers that were
running some versions of the MSSQL server.
--------------------------------------------------------------------------------
Etrack Incident = ET540828
Description:
BMR did not save the configuration for a Solaris box that does not have a
swap device assigned.
--------------------------------------------------------------------------------
Etrack Incident = ET596795
Description:
Veritas Volume Manager (VxVM) volumes with names longer than 28 characters
were incorrectly re-mapped when performing a change configuration action
(for example, Dissimilar Disk Restore).
--------------------------------------------------------------------------------
Etrack Incident = ET577771
Description:
Some BMR commands such as bmrprep and bmrsavecfg, under certain rare
circumstances, would hang indefinitely.
--------------------------------------------------------------------------------
Etrack Incident = ET601380
Description:
Solaris Volume Management (SVM) stripes were incorrectly stored by BMR. The
Volume was being saved as a concatenation rather than a stripe.
--------------------------------------------------------------------------------
Etrack Incident = ET409317
Description:
Customers should not use "BmrCreatePkg" utility to add service packs
to the server. This fix displays this information on the BmrCreatePkg
user interface to remind them.
--------------------------------------------------------------------------------
Etrack Incident = ET602249
Description:
AIX file systems would not appear in the configuration change, disk view
screen because of a problem with importing file systems. The problem
would occur when two logical volumes were created on the same disk that
contained substrings of each other in the name. For instance, creating
logical volumes named logjfs1a and jfs1a would cause the failure to occur.
--------------------------------------------------------------------------------
Etrack Incident = ET612051
Description:
For some Solaris Volume Manager (SVM) volumes, Bare Metal Restore was not
handling the components properly after a Dissimilar Disk Restore (DDR)
mapping. The affected volumes were raid0 (concatenation) with multiple
slices used as components.
--------------------------------------------------------------------------------
Etrack Incident = ET613131
Description:
A Dissimilar Disk Restore (DDR) of a Solaris machine, where controllers
(such as, /dev/cfg/c*) were not in normal sequential order, could cause
extra device path symbolic links to appear on the restored system. For
instance, if a user had a client with an original configuration of
/dev/cfg/c0 and /dev/cfg/c2 where the root disk was on /dev/dsk/c0* and the
data file systems were on /dev/dsk/c2*, then after the discovery boot and
mapping /dev/dsk/c2* to /dev/dsk/c1* in the discovered configuration, the
post-restore machine would have symbolic links to the /devices entry from
both /dev/dsk/c1* and /dev/dsk/c2*.
--------------------------------------------------------------------------------
Etrack Incident = ET603139
Description:
On Red Hat 3.0, Update 5, bmrsavecfg no longer fails when multiple disks
are present.
--------------------------------------------------------------------------------
Etrack Incident = ET535286
Description:
Changed the implementation of AIX client Dissimilar Disk Restore (DDR)
restoration so that the volume group TFactor is no longer adjusted or
multiplied; instead, the volume group physical partition size is increased
until the mkvg request is satisfied. This enables better support for
scenarios where there is a DDR to a larger disk to limit the possibility of
running out of physical partitions.
--------------------------------------------------------------------------------
Etrack Incident = ET570599
Description:
On a Solaris 5.8 client, swap entries for SDS metadevices in /etc/vfstab
were not maintained in a post-restore client. They should be in the file in
the basic Solaris slice format.
--------------------------------------------------------------------------------
Etrack Incident = ET411598
Description:
Copying a Linux SRT to a freshly installed boot server requires the user to
provide the third party CD image during the copy operation. This patch
obviates the need for the third party CD image during the copy operation.
However, the SRTs that were created before applying this patch to the source
boot server continue to require the user to provide the third party CD image
irrespective of the target boot server's patch level. Also, even if the SRT
was created after applying this patch to the source boot server, the third
party CD is still required if the target boot server, where that SRT is
being copied to, does not have this patch applied. In all cases, if an SRT
is ever created on the target boot server, irrespective of its patch level,
the third party CD image is not required during the copy operation.
--------------------------------------------------------------------------------
Etrack Incident = ET564236
Description:
There was no way to change the boot server's IP address in the database.
This problem occurred when the boot server had multiple interfaces, and the
default address chosen by BMR was not usable.
--------------------------------------------------------------------------------
Etrack Incident = ET613719
Description:
Dissimilar disk restore (DDR) mapping operations do not give the user a disk
selection of the desired disk if the original configuration contained a
slice that was more than half the disk in size and that slice contained
multiple SVM devices (database replicas and SVM volume). The mapping
operation worked correctly for the database replicas because of their small
size but failed for the metadevice volume that takes up the rest of the
slice. This was on Solaris 9 client configurations using SVM.
--------------------------------------------------------------------------------
Etrack Incident = ET612035
Description:
Solaris 10 clients, running VxVM 4.1 and having an encapsulated root disk on
an IDE disk drive, would not boot after restoring. The client would panic
during the boot process because of the inability to load the necessary
device drivers.

Workaround:
To avoid this issue, change the client restore script to perform "newfs" on
the underlying encapsulated slice instead of through the VxVM volume.
--------------------------------------------------------------------------------
Etrack Incident = ET627375
Description:
Media boot on all UNIX platforms failed if the interface that was brought up
during the media boot phase was assigned an IP address that was different
from the IP address of the NetBackup client name of that machine.
--------------------------------------------------------------------------------
Etrack Incident = ET625279
Description:
On an AIX boot server, if /usr/openv was linked to an alternate location,
the NetBackup client could not be installed into an SRT.
--------------------------------------------------------------------------------
Etrack Incident = ET639252
Description:
Multi-network interface card AIX boot servers would not have the proper
hostname set in the /tftpboot/<client>.info file if the boot server was
configured to use a hostname that was not the hostname of the machine
(alternate interface). This had the possibility of causing client machines
to fail in mounting the SRT file systems at restore time.
--------------------------------------------------------------------------------
Etrack Incident = ET632311
Description:
Removing a Linux Shared Resource Tree would clean other clients that were
ready to be restored using different Shared Resource Trees
--------------------------------------------------------------------------------
Etrack Incident = ET648820
Description:
Restoration of Linux clients that have whole disk PVs or MDs would fail
with errors.
--------------------------------------------------------------------------------
Etrack Incident = ET701018
Description:
Prepare-to-restore failed on an AIX client if a volume group contained a
disk or disks that were multi-pathed.
--------------------------------------------------------------------------------
Etrack Incident = ET622074
Description:
The Media Boot Shared Resource Tree (SRT) creation failed if the SRT was
too large fit on a CD media.

Additional Notes:
Media Boot support is enhanced in this patch to include support for
DVD media.
--------------------------------------------------------------------------------
Etrack Incident = ET622102
Description:
Added support for the following:
- Bare Metal Restore Support for Solaris 10
- Bare Metal Restore Support for Veritas Volume Manager 4.1 in Solaris
--------------------------------------------------------------------------------
Etrack Incident = ET765357
Description:
Restoring from a NetBackup MP4 master server will initiate autoDDR on an
AIX 5.3 client that is running NetBackup 6.0MP2 or MP3.

Additional Notes:
AIX 5.3 clients running NetBackup 6.0 MP2 and MP3 should be upgraded to
NetBackup 6.0 MP4 and backed up immediately after installing MP4 on the
master server.

Workaround:
To restore a client that is still at NetBackup 6.0 MP2 or MP3, you must
use a NetBackup 6.0 MP4 Shared Resource Tree (SRT) to discover a
configuration from the hardware (or use the configuration generated by
autoDDR with a NetBackup MP4 SRT), and then use DDR with this
configuration to restore the client.
--------------------------------------------------------------------------------
Etrack Incident = ET768305
Description:
For Windows clients, after initializing disk information in a
configuration, discovered disks were blank and unrestricted. Even if the
user did not map any volumes to those disks, any discovered volumes on
those disks were erased unless the user restricted those disks.

With this change, discovered disks are automatically restricted when a
configuration is initialized. The user must manually unrestrict those
disks before mapping volumes to them.

Workaround:
If the user wants to prevent the restore process from altering unused
disks, the user should edit the configuration and mark those disks as
restricted.
--------------------------------------------------------------------------------
Etrack Incident = ET769511
Description:
An AIX client that was utilizing VxVM 4.x disk groups could not perform
dissimilar disk mapping operations on its configuration using a
discovered configuration because of incomplete physical volume information
stored in the discovered configuration.
--------------------------------------------------------------------------------
Etrack Incident = ET774743
Description:
Solaris client configurations that contained a �rootdg� on a slice Veritas
Volume Manager (VxVM) configuration on a full disk, fail to self-restore
and are forced into auto-DDR mode at restore time.
--------------------------------------------------------------------------------
Etrack Incident = ET779084, ET771267, ET772825, ET772735, ET773720
Description:
A new version of the BMR Windows Fast Recovery Disk is provided
in this MP. Users should re-run the Boot Server Assistant from the
Start Menu, and follow the menus to create a new CD/DVD ISO image.
--------------------------------------------------------------------------------
Etrack Incident = ET786931
Description:
A Solaris client self-restore can fail under conditions where the original
live client had file systems that were not mounted when the backup was
taken.
--------------------------------------------------------------------------------
Etrack Incident = ET783882
Description:
If a Solaris 10 boot server is hosting a Solaris 8 or Solaris 9 SRT, and if
the first "Prepare to Restore" operation using this boot server does not
use a Solaris 10 SRT, the "Prepare to Restore" operation will fail.

Workaround:
To avoid this issue, start the tftp service by hand.
--------------------------------------------------------------------------------
Etrack Incident = ET788817
Description:
BMR did not collect the configuration information correctly on machines
running in a non-English locale.
--------------------------------------------------------------------------------
Etrack Incident = ET792676
Description:
Large file, file systems were not being created properly on HP-UX 11.i
systems.
--------------------------------------------------------------------------------
Etrack Incident = ET796403
Description:
A Linux client self-restore could fail because of invalid file system
configuration data. This would occur when the running client had file
systems mounted on device names that were long enough to cause the output
of the "df" command to span two lines.
--------------------------------------------------------------------------------
Etrack Incident = ET801098
Description:
Linux client configuration editing allows DDR mapping to disks that have
been restricted. In addition, there are no checks in place so that restores
are not allowed on disks that are restricted.
--------------------------------------------------------------------------------
Etrack Incident = ET820368
Description:
External procedures no longer fail to run on Windows 2003 SP1, (with
security updates installed).
--------------------------------------------------------------------------------
Etrack Incident = ET801694
Description:
Under extremely rare conditions, the bmrprep command fails when invoked
from the user interface but succeeds when invoked from the command line.
--------------------------------------------------------------------------------




=============
NB_BBS_60_3_M
=============

- This pack contained an exciting fast-windows-restore feature to the Bare
Metal Restore (BMR) option. This feature performs a complete restore
of a Windows system in as little as 15 minutes. This feature means it is
no longer necessary to create DOS-based floppies or CDs. In addition,
feature enables BMR to operate in a low-infrastructure mode, where the
BMR Boot Server, Windows Shared Resource Tree, and the Prepare-To-Restore
step are no longer mandatory to restore a Windows system.

For a description of how to use this new feature, along with feature
requirements and limitations, please refer to the Symantec TechDoc #283726.
This document can be accessed on the Symantec Support Web site using the
following URL:

http://entsupport.symantec.com/docs/283726


Etrack Incident = ET613657

Description:
All Windows BMR Boot Servers now contain a new wizard to assist in
creating a CD image to be used for the Fast Restore feature. This new
feature can restore Windows systems in approximately 15 minutes.
================================================================================



=============
NB_BBS_60_2_M
=============

Etrack Incident = ET506666

Description:
A Linux client with an empty or non-existent /etc/resolv.conf file would
halt at restore time even though the client's original configuration did
not use the /etc/resolv.conf file.

Additional Notes:
Linux Shared Resource Trees (SRT) created after this pack is applied will
correctly handle an empty or non-existent /etc/resolv.conf file.
--------------------------------------------------------------------------------
Etrack Incident = ET404593

Description:
Changes were made to store UNIX boot images in the Shared Resource
Tree (SRT) and put them into use only during a Prepare-to-Restore. This
gives the ability to use the Boot Server in a clustered environment and
only share the disks where the SRT's reside. In addition, the ability to
use varying levels of SRT's and boot images for Hewlett Packard (HP) was
enabled.

Additional Notes:
On HP-UX platform, the SRTs created while the boot server is at 6.0GA
version cannot be used after the boot server is upgraded to 6.0MP2. New
SRTs must be created after upgrading the boot server to 6.0MP2

--------------------------------------------------------------------------------
Etrack Incident = ET506661

Description:
After installing NetBackup into a Solaris Shared Resource Tree (SRT), if
the source of the installation is a CD-ROM, the device is left mounted and
the CD-ROM cannot be ejected.

Workaround:
After installing NetBackup into the Shared Resource Tree, exit bmrsrtadm,
start bmrsrtadm again, and this time choose the Share Resource Tree that
was just created.
--------------------------------------------------------------------------------
Etrack Incident = ET327111

Description:
Prepare-to-Restore failures no longer display specific error messages on
the NetBackup Administration Console, rather than indicate that the user
should get the error details from the server logs.
--------------------------------------------------------------------------------
Etrack Incident = ET535310 ET536715

Description:
The Shared Resource Tree (SRT) creation no longer fails after installing
the operating system software into it.
--------------------------------------------------------------------------------
Etrack Incident = ET542779

Description:
Shared Resource Trees (SRTs) cannot be created on boot servers where
NetBackup is not installed in /usr/openv./netbackup
--------------------------------------------------------------------------------
Etrack Incident = ET543876

Description:
Discovering disks on HP-UX clients using the "discovery boot"
unsuccessfully gets the disk names under certain circumstances.

Additional Notes:
If the disks in an HP-UX client cannot be discovered, create a new SRT
with this pack installed on the server and perform a new discovery boot.
--------------------------------------------------------------------------------
Etrack Incident = ET546889

Description:
Prepare-to-Restore operation would fail complaining that a needed
directory does not exist on the boot server.
--------------------------------------------------------------------------------
Etrack Incident = ET569498

Description:
Retrieving a Windows client configuration (PIT) using the NetBackup
Administrative Console on a UNIX master server fails.
================================================================================




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)