Maintenance Pack NB_BMR_60_7_M.rs6000.tar provides updates and fixes for Veritas NetBackup (tm) Enterprise Server / Server 6.0 Bare Metal Restore Client on AIX platforms.

Article:TECH63308  |  Created: 2008-01-15  |  Updated: 2008-01-23  |  Article URL http://www.symantec.com/docs/TECH63308
Article Type
Technical Solution


Environment

Issue



Maintenance Pack NB_BMR_60_7_M.rs6000.tar provides updates and fixes for Veritas NetBackup (tm) Enterprise Server / Server 6.0 Bare Metal Restore Client on AIX platforms.

Solution



BMR 6.0GA Pack NB_BMR_60_7_M README September 15, 2008
Requirement: NB_60_7_M
Corequirement: NB_BBS_60_7_M
Directives: BMRDB_Upgrade BMRDB_Recover
================================================================================
This Maintenance Pack provides updates and fixes for Veritas NetBackup(tm)
Bare Metal Restore (BMR).

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


=================
PACK DEPENDENCIES
=================
-- NB_60_7_M_<6 digit number>.<server>.tar must be installed before this
Maintenance Pack is installed.

-- Only if Bare Metal Restore Boot Server is installed,
NB_BBS_60_7_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.


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_BMR_60_7_M
Maintenance Pack History
NB_BMR_60_6_M
NB_BMR_60_5_M
NB_BMR_60_4_M
NB_BMR_60_3_M
NB_BMR_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.

+ When restoring on a Windows system that uses the Broadcom NetExtreme II chip
set, the Bare Metal Restore (BMR) cleanup process may hang. Self Restores that
use a "Current" Configuration will work. However, you may encounter problems
while attempting a Dissimilar Restores (DSR ) or a Self Restores using "copied"
configuration.

Before you attempt any such restores, Symantec recommends that you refer to
the following TechNote on the Symantec Support Web site for more details.
http://entsupport.symantec.com/docs/289611




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

where <6 digit number> is an internal tracking identifier

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

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

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




=============================
IV. INSTALLATION INSTRUCTIONS
=============================
** 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 NetBackup Master 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
=========================

** The content of this online Readme supersedes the information in the Readme
contained in the download. **

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} in the following command:

cd /usr/openv/pack/${PACK}/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_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 = ET1201741

Description:
Prepare to restore failed on a client that had shared (or restricted)
disks in VxVM disk groups when specifying a shared resource tree (SRT)
that did not contain VxVM and/or VxFS.

Workaround:
If you encounter this issue, install VxVM and/or VxFS into the shared
resource tree.
--------------------------------------------------------------------------------
Etrack Incident = ET1212630
Associated Primary Etrack = ET1211879
Titan cases: 281-285-629

Description:
Mirroring of a Solaris client VxVM encapsulated root disk to a second
disk fails. This happens after a BMR restoration where the original client
configuration is a two copy mirror and the mirror is broken in the
configuration because of dissimilar disk restore mapping. It exhibits the
following error (post-restore) after adding the mirror disk back into the
disk group:

# /etc/vx/bin/vxmirror -g rootdg -a
! vxassist -g rootdg mirror export
! vxassist -g rootdg mirror rootvol
! vxassist -g rootdg mirror swapvol
! vxbootsetup -g rootdg
VxVM vxmksdpart ERROR V-5-2-3612 Partition 0 is not available on device
c0t0d0s2

Workaround:
To resolve this issue, delete the VTOC on the second disk and re-initialize
the disk into the disk group with vxdiskadm.
--------------------------------------------------------------------------------
Etrack Incident = ET1213219

Description:
A user no longer needs to capture a screen shot of disk comparisons when a
restore triggers the auto-discovery mode.
--------------------------------------------------------------------------------
Etrack Incident = ET1219751
Associated Primary Etrack = ET1211325
Titan cases: 240-699-368

Description:
BMR would sometimes fail to restore clients with configurations that utilize
VxVM with disk multipathing (DMP) because it was not choosing a previously
active path to restore to.
--------------------------------------------------------------------------------
Etrack Incident = ET1222733
Associated Primary Etrack = ET1220159
Titan cases: 290-932-689

Description:
Moving from a smaller disk to a larger disk would fail in mklv allocation.

In the case of an AIX 5.3 client OS, if the original client rootvg was
installed on a smaller disk size of about 10GB and later during a restore
the large disk was selected to have install rootvg on it (around 80GB),
then the restore would fail while creating logical volumes on the rootvg
volume group.

Workaround:
Perform the following steps to resolve this problem.
1. This workaround requires you to modify the restore script that is
generated after bmrprep and stored in the BMR master server database.

2. Pull the <client_hex_addr>.restore script from master server using
the bmrc command line interface (CLI)

3. The bmrc CLI syntax is:
/usr/openv/netbackup/bin/bmrc/bmrc -o pull -r INFO -client <cl_name>

4. The source is:
<client_hex_addr.restore file name> -destination /tmp/foo
5. Open the /tmp/foo file for editing.

6. In the function MkVg(), which creates a rootvg volume group, before
the creation of each logical volume under rootvg (for example, just
before mklv command) write the following two lines.

let LVPartitions=LVPartitions+PPSizeMultiplier-1
let LVPartitions=LVPartitions/PPSizeMultiplier

7. Upload the /tmp/foo file into the master server database using the
bmrc CLI.

/usr/openv/netbackup/bin/bmrc/bmrc -o push -r INFO -client <cl_name>
-source /tmp/foo -destination <client_hex_addr.restore file name>

8. Try to restore the client machine. This should resolve the problem.
--------------------------------------------------------------------------------
Etrack Incident = ET1231109

Description:
If an expired VxVM or VxFS license key is encountered during restoration
of an AIX client, the restoration process does not prompt the user to enter
an updated key.

Workaround:
If you encounter this issue, update the license key in an editable
configuration for the client.
--------------------------------------------------------------------------------
Etrack Incident = ET1228989

Description:
Self-restores on RHEL 2.4 and 2.6 BMR clients would go into Dissimilar Disk
Restore (DDR) mode. This problem was encountered when the BMR client had
HBA- and USB-based storage devices.
--------------------------------------------------------------------------------
Etrack Incident = ET1212202
Associated Primary Etrack = ET1209045
Titan cases: 220-177-120

Description:
If the backup image was multiplexed (doing a multiplex restore), and the
client connect options were set to 2,1,1 (meaning: (2) Use Default ports -
which is the reserved port, (1) VNETD port for connect back, and (1) VNETD
for the Daemon Connection port, respectively) then the BMR restore to the
client would fail with bptm unable to connect to the client.
--------------------------------------------------------------------------------
Etrack Incident = ET1175891

Description:
In Windows, while creating a new Shared Resource Tree (SRT), if an
existing SRT's name was given (case insensitive), then the older SRT was
overwritten and became unusable.

A change was made so that the Shared Resource Tree (SRT) name is now
case-insensitive for UNIX. It was already case-insensitive for Windows.
This change was made to maintain a similar structure across all platforms
in BMR.

Additional Notes:
If you are upgrading a server and if multiple SRTs with a same name but
a different case already exist, some operations, such as deleting an
SRT, would behave in an ambiguous manner and a wrong operation might be
performed. However, a change has been made that does not allow the
creation of SRTs with the same name (with a different case).
--------------------------------------------------------------------------------
Etrack Incident = ET1195956

Description:
A BMR client entry would show duplicates with case sensitivity.

After performing a backup of a BMR client, if the client name case was
changed, the next backup would add another client entry, and the case
sensitivity would give an impression that there were now two different
clients.
--------------------------------------------------------------------------------



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

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

=============
NB_BMR_60_6_M
=============
Etrack Incident = ET1100826
Associated Primary Etrack = ET1100064
Titan cases: 320-060-202

Description:
Performing a relayout of VxVM volumes that are on an encapsulated root
disk group on a Solaris client creates a situation where the machine
will not boot after restoration. This is due to a defect where the VxVM
volume field use_type for both the rootvol and swapvol are set to
"fsgen" instead of "root" and "swap" respectively.

Workaround:
To resolve this issue, perform the following procedure:

1) On the master server, after running Prepare To Restore, run the
following:
bmrs -o query -r database -t restoreconfigfile
2) Note the name of the <hex_address>.restore file name for the client
from the output
3) Enter the following:
bmrc -o pull -r info -client <client> -source <hex_address>.
restore -dest /tmp/client.restore
4) Edit /tmp/client.restore and find shell script code for "rootvol"
and "swapvol". Once you find those entries for creating those
volumes, search for use_type for each and change "fsgen" in each to
"root" and "swap" respectively.
5) Enter the following:
bmrc -o push -r info -c client -source /tmp/client.restore -dest
<hex_address>.restore
6) Continue with normal restoration.
--------------------------------------------------------------------------------
Etrack Incident = ET1116059

Description:
Linux restoration could break into auto-DDR mode and not allow the
user to restore the client.
--------------------------------------------------------------------------------
Etrack Incident = ET1109594
Associated Primary Etrack = ET1109590
Titan cases: 290834099

Description:
The post-restoration boot of a Solaris client fails with the error,
"No boot block install target device is specified".

If the client originally had a VxVM encapsulated root disk that was
mirrored and a plex on any of the encapsulated volumes was disabled,
the import of the client configuration would not recognize the disk
encapsulation and fail to recreate the underlying disk slices.
--------------------------------------------------------------------------------
Etrack Incident = ET1115944
Associated Primary Etrack = ET1115544
Titan cases: 320063430

Description:
AIX restores fail if any of the logical volumes being restored have an
Intra-Disk policy of "inner middle" or "inner edge"

Workaround:
To avoid this issue, use DDR to exclude such volumes from the
restoration, if possible.

Additional Notes:
After you install this pack, you must run a new backup on the client, or
use Point-In-Time retrieval for that client before this fix is effective.
This includes retrieving the "current" configuration from the client
backup, in case the client is unavailable for a new backup.
--------------------------------------------------------------------------------
Etrack Incident = ET1119044

Description:
Running a Point-in-Time (PIT) configuration retrieval for a Windows
client that is utilizing a UNIX or Linux Master Server could fail due
to a difference in the NetBackup client installation path versus the
INSTALLDIR setting in the registry. The installation path uses
"VERITAS" and the registry entry uses "Veritas". This becomes a
case-sensitivity issue when performing this type of operation on a UNIX
or Linux Master Server.
--------------------------------------------------------------------------------
Etrack Incident = ET1130594
Associated Primary Etrack = ET1124350
Titan cases: 240-626-530

Description:
The restoration of a client with a DMP-attached fibre device that
utilizes VxVM would fail during VxVM disk initialization operations.
--------------------------------------------------------------------------------
Etrack Incident = ET1131126
Associated Primary Etrack = ET1121777
Titan cases: 230408646

Description:
Solaris 10 clients (11/06 based CD) would fail to restore when using
media boot.
--------------------------------------------------------------------------------
Etrack Incident = ET602147

Description:
The restoration of an AIX client fails if a configuration mapping
occurs that does not include a JFS log for a volume group.

Workaround:
To resolve this issue, perform the mapping again, however include the
JFS log in the mapping operation.
--------------------------------------------------------------------------------
Etrack Incident = ET1162774

Description:
The UNIX pack installer no longer gives "nbdb_ping" errors in the case
of a BMR patch install on a master server with a remote EMM server. The
two instances of Sybase, one for BMRDB, and the other for NBDB, are now
pinged separately following the upgrades.
--------------------------------------------------------------------------------
Etrack Incident = ET1148909

Description:
The restoration of an AIX client that originally utilized JFS2 file
systems with inline logging would fail.
--------------------------------------------------------------------------------
Etrack Incident = ET1172182

Description:
HP-UX clients that utilize a VxVM boot disk may not boot after a
dissimilar disk restoration to an alternate disk because the primary
boot disk path is not set.

Workaround:
To avoid this issue, run "setboot -p <boot disk path>" in a maintenance
shell.
--------------------------------------------------------------------------------
Etrack Incident = ET1171778

Description:
An HP-UX client utilizing a VxVM boot disk will fail to boot after
restoration if a dissimilar disk mapping has been performed on the boot
disk group and the "standvol" volume has not been mapped first.

Workaround:
To resolve this issue, map configuration again and choose to map
"Disk Group Only" and then map the volumes within the disk group one at
a time making sure to map "standvol" first, then rootvol, and swapvol
onto the same disk.
--------------------------------------------------------------------------------
Etrack Incident = ET1166347

Description:
HP-UX volume groups had invalid size values after performing DDR
mapping operations.
--------------------------------------------------------------------------------
Etrack Incident = ET1159518

Description:
VxVM disk enclosure-based names can be incorrectly numbered in the
"vxdisk list" output after a BMR restoration.

Workaround:
To avoid this issue, remove the file, /etc/vx/disk.info, and then
reboot the client.
--------------------------------------------------------------------------------
Etrack Incident = ET1160487
Associated Primary Etrack = ET1160484

Description:
Bmrprep or bmrsrtadm can fail in an HP-UX environment if the HP-UX
boot server has a volume group that is offline.

Workaround:
To avoid this issue, online or remove the offline volume group.
--------------------------------------------------------------------------------
Etrack Incident = ET1177363
Associated Primary Etrack = ET1175826
Titan cases: 290-881-855

Description:
The "Prepare To Restore" (bmrprep) restore was failing for clients with a
"/boot" or a "/" on the RAID device.
--------------------------------------------------------------------------------
Etrack Incident = ET1177593

Description:
Mapping a VxVM volume and choosing to not restore the file system does
not allow for a reduction in volume size that is smaller than the
original used space of the volume.
--------------------------------------------------------------------------------
Etrack Incident = ET1182143

Description:
Mapping Solaris Volume Manager (SVM) disk sets would fail, stating that
the number of disks did not match the original number of disks in the
disk set.
--------------------------------------------------------------------------------
Etrack Incident = ET1181897

Description:
Unmapping Solaris Volume Manager (SVM) disk sets would fail with a
status code 252.
--------------------------------------------------------------------------------





=============
NB_BMR_60_5_M
=============
Etrack Incident = ET865996

Description:
Restoration of a Linux LVM-based root file system client could fail to boot
in dissimilar disk restore situations where the Linux LVM partition had been
remapped to another disk, and another partition resided in the same location
as the original Linux LVM partition. This was caused by the vgscan command
running and discovering the original LVM volume group descriptor area.
--------------------------------------------------------------------------------
Etrack Incident = ET860244

Description:
Initialization of a configuration for dissimilar disk restore (DDR) on a
Solaris 10 configuration that contains a Solaris Volume Manager database
replica and is using Solaris Zones fails with a return code 114.
--------------------------------------------------------------------------------
Etrack Incident = ET922453

Description:
The self-restore of a client that has an extended VxVM volume that expands
into multiple disks would fail with the following error in the BMR restore
log:

# /usr/sbin/vxvol -g rootdg -o delayrecover start mdsd-concatenated
vxvm:vxvol: ERROR: Volume mdsd-concatenated has no complete, non-volatile
ACTIVE plexes
--------------------------------------------------------------------------------
Etrack Incident = ET916721
Associated Primary Etrack = ET916708
Titan cases: 230-247-487

Description:
The prepare-to-restore operation may fail on Windows master servers when
run in a non-English environment.
--------------------------------------------------------------------------------
Etrack Incident = ET586783

Description:
Buffer overflow areas have been identified and corrected in daemons and
programs that run on Veritas NetBackup Bare Metal Restore master and boot
servers, and clients. Successful access to a vulnerable Veritas NetBackup
server, and the ability to successfully execute arbitrary code, could
potentially result in unauthorized access with elevated privileges on a
system.
--------------------------------------------------------------------------------
Etrack Incident = ET863495
Associated Primary Etrack = ET863494
Titan cases: 280-869-770

Description:
Prepare-to-restore fails to share the shared resource tree (SRT) folder
when the ownership is not an administrator account.

Workaround:
To avoid this issue, change the ownership of the SRT folder to the
administrator account.
--------------------------------------------------------------------------------
Etrack Incident = ET862330
Associated Primary Etrack = ET806140

Description:
The error message, "Access to Client failed", would appear if media servers
were absent from the Hosts list at restore time.
--------------------------------------------------------------------------------
Etrack Incident = ET928834

Description:
This pack enables the basic restoration support for UNIX clients that run
VxVM and VxFS Version 5.0 without the preservation of disk group and disk
tagging.
--------------------------------------------------------------------------------
Etrack Incident = ET862339

Description:
A fix has been made that enables you to restore an AIX client that does not
have a default route.
--------------------------------------------------------------------------------
Etrack Incident = ET932384
Associated Primary Etrack = ET932367
Titan cases: 230-261-966

Description:
A problem existed on AIX 5.3 systems that caused a media boot to fail with
the following message, "ln ./helpers is a directory. (cannot unlink)�.
--------------------------------------------------------------------------------
Etrack Incident = ET925915
Associated Primary Etrack = ET925905
Titan cases: 280-918-606

Description:
The bmrd process will fail to import a configuration of an AIX client if the
/etc/filesystems file has a empty line with a single blank space.


Workaround:
To resolve this issue, edit the /etc/filesystems file by removing any single
blank space on the empty line.
--------------------------------------------------------------------------------
Etrack Incident = ET970583
Associated Primary Etrack = ET970553
Titan cases: 280975845

Description:
Linux restores would fail with the following message:

ERROR: SCSI Module Load Order Problem

The message suggests a new scsiLoadOrder variable setting which often times
does not fix the problem.

Additional Notes:
There are many issues associated with the loading of device drivers at
restore time. This fix includes many changes that deal with the
complexities of loading device drivers in the proper order to maintain
the proper device locations and names for machine restoration.
--------------------------------------------------------------------------------
Etrack Incident = ET967447

Description:
Restoration of AIX clients shows an error when an attempt is made at
importing the volume group named "VeritasVolumes".

Workaround:
To avoid this issue, create an editable configuration and remove the volume
group "VeritasVolumes" from the configuration.
--------------------------------------------------------------------------------
Etrack Incident = ET965699
Associated Primary Etrack = ET800883

Description:
After restoration of a Solaris client, the machine can fail to boot if
the eeprom "boot-device" setting is not referring to the correct PROM
device.

Workaround:
To resolve this issue, set the eeprom "boot-device" correctly for the
boot disk partition.
--------------------------------------------------------------------------------
Etrack Incident = ET1004121

Description:
A Linux client, when utilizing the logical volume manager (LVM), failed
to boot after the BMR restoration complained that the volume group was
not found.
--------------------------------------------------------------------------------
Etrack Incident = ET1004430
Titan cases: 281-036-717

Description:
The BMR database file would grow in size because of old copies of unused
files being left behind in the database. This happened primarily when a
client configuration was imported on successive backups.
--------------------------------------------------------------------------------
Etrack Incident = ET1026247

Description:
Restoration of Linux clients utilizing Linux LVM for root file system(s)
may fail to boot because of a kernel panic. This was caused by a mismatch
in the LVM device minor numbers.
--------------------------------------------------------------------------------
Etrack Incident = ET1030267
Associated Primary Etrack = ET1030259
Titan cases: 230-280-364

Description:
Large client configurations would cause excessively slow database query
performance. In addition, importing an AIX client configuration that
contained vpath disks had the potential for creating large client
configurations that could cause the excessive performance issues.
--------------------------------------------------------------------------------
Etrack Incident = ET1055442
Associated Primary Etrack = ET1055440
Titan cases: 281-107-942

Description:
An AIX 5.3 client restoration that had been restored on a machine with a
larger disk for rootvg would fail to boot after being restored with BMR
due to BMR possibly creating the rootvg volume group as scalable.
--------------------------------------------------------------------------------
Etrack Incident = ET1065639
Associated Primary Etrack = ET1064866
Titan cases: 240-587-968

Description:
The bmrd process on the master server would sometimes core dump or hang
indefinitely while importing a Solaris client configuration that had
Solaris Volume Manager database replicas configured.
--------------------------------------------------------------------------------




=============
NB_BMR_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_BMR_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://support.veritas.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_BMR_60_2_M
=============

Etrack Incident = ET411631

Description:
Running bmrconfig on an AIX client no longer causes an error when mapping
a striped volume that needs more disks than available columns.
--------------------------------------------------------------------------------
Etrack Incident = ET409373

Description:
Could not restore an AIX client if the boot logical volume was not hd5.
--------------------------------------------------------------------------------
Etrack Incident = ET414241

Description:
Mapping a Solaris disk or Solaris Volume Manager managed disk failed if
the source disk was not using slice 2 as a backup slice and the disk was
filled to capacity.

Workaround:
To avoid this issue, unmap slice 2 from the target disk after configuration
initialization and before you attempt to map to the source disk.
--------------------------------------------------------------------------------
Etrack Incident = ET412755

Description:
Mapping Windows spanned volumes onto more than one disk no longer results
in an error message that complained about inadequate free space even
though adequate free space existed. The error message has the following
format: "A subdisk of length X does not fit on disk Y", where X is some
number and Y is a disk name.
--------------------------------------------------------------------------------
Etrack Incident = ET414965

Description:
A �prepare to restore� operation fails on a Solaris client that has a
configuration containing a Solaris Volume Manager disk set that has no
metadevices in it.

Workaround:
To avoid this issue, remove the empty Solaris Volume Manager disk set from
the configuration and rerun the �prepare to restore� operation.
--------------------------------------------------------------------------------
Etrack Incident = ET424767

Description:
During Solaris client restoration, disks allocated for Solaris Volume
Manager disk sets were not being formatted after being added to the disk
set causing failures to create metadevices.
--------------------------------------------------------------------------------
Etrack Incident = ET416705

Description:
Restoration or Dissimilar Disk Restore (DDR) mapping of a Solaris Volume
Manager one-way mirror metadevice no longer fails.
--------------------------------------------------------------------------------
Etrack Incident = ET415984

Description:
Resizing a VxVM volume on an encapsulated disk that contained a B0 subdisk
in the source disk no longer fails.
--------------------------------------------------------------------------------
Etrack Incident = ET366934

Description:
Disks with only swap volumes/partitions on them were not being considered
as system-critical disks during restoration.
--------------------------------------------------------------------------------
Etrack Incident = ET408810

Description:
When performing a Dissimilar Disk Restore (DDR) mapping, the user could
not remove Linux partitions, multi-devices, or physical volumes whose
components (usually partitions) were not the last component on the disk.

For example, if the disk had partitions A, B, and C, then neither
partition A or B could be removed. The user had to start removing
partition C followed by partition B, and then partition A.

Additional Notes:
An extra message was added in case a failure occurred. The message reads:
"The partition <PART NUMBER> could not be removed."
--------------------------------------------------------------------------------
Etrack Incident = ET426030

Description:
The bmrsavecfg UNIX command removes the directory,
/usr/openv/netbackup/baremetal/client/data upon each invocation which
then causes the ClientCustomFiles feature to break because it is contained
in this same directory.
--------------------------------------------------------------------------------
Etrack Incident = ET425710

Description:
A Solaris machine fails to boot after restoration because of device major
number entries are not being synchronized between /dev and /devices device
special files and their specifications in the file /etc/name_to_major.

Workaround:
To avoid this issue, boot the machine into single-user mode and synchronize
the device major number entries with the device special files in /dev and
/devices.
--------------------------------------------------------------------------------
Etrack Incident = ET401379

Description:
If the Linux root file system (/) is mirrored using a Multi Device and
this mirror is broken (converted to a RAID 0 device) using Dissimilar
Disk Restore, the kernel will panic on boot after a restore.


--------------------------------------------------------------------------------
Etrack Incident = ET413615

Description:
When mapping a volume, that is not a vendor or system volume, in a
Dissimilar System Restore configuration the �Map� option is now always
enabled.
--------------------------------------------------------------------------------
Etrack Incident = ET409857

Description:
Changing the size of a Windows mirrored system volume no longer causes
the mirrored slices to be different sizes.
--------------------------------------------------------------------------------
Etrack Incident = ET409679

Description:
When removing a Windows disk that contains the secondary mirror of a
mirrored system volume, the system volume is correctly changed to a
concatenated volume instead of a primary partition.
--------------------------------------------------------------------------------
Etrack Incident = ET338590

Description:
Mapping a Windows-striped volume will now correctly show the amount of
space used in the target volume.
--------------------------------------------------------------------------------
Etrack Incident = ET416745

Description:
The Solaris Volume Manager read/write and raid5 interlace options are now
correctly preserved.
--------------------------------------------------------------------------------
Etrack Incident = ET411601

Description:
An error occurred while creating a SUSE Shared Resource Tree (SRT).
Cleanup of this SRT would fail and display the following incorrect message:

[Error] V-125-376 No space left on device. Please ensure that the
specified target location for the Shared Resource Tree has adequate free
space, and retry the command.

Please refer to the Bare Metal Restore System Administrator's Guide
for the space requirements for creating Shared Resource Trees.
--------------------------------------------------------------------------------
Etrack Incident = ET506663

Description:
A Point in Time (PIT) retrieval of a UNIX client configuration being
managed by a Windows Master BMR server failed and produced the following
error message:

"The requested operation could not be completed. The server returned
code 1."
--------------------------------------------------------------------------------
Etrack Incident = ET492456

Description:
An incorrect message was added in the log file when the External Procedures
option was chosen at "Prepare to Restore" time:

"External Procedures Notify: You have chosen to run External Procedures,
but no external procedures are defined for client"
--------------------------------------------------------------------------------
Etrack Incident = ET506668

Description:
For Linux clients, some S-ATA devices were not being handled correctly
at restore time. Changes contained in this pack load the proper modules
correctly in the restore environment so the restoration can be performed.

Additional Notes:
The original problem presents itself when the restore environment boots.
After loading the SRT, the restoration will stop, requesting for a reboot
of the client, with a boot order string that contains the ata_piix module.

Even if the client is rebooted and the order string is passed from the boot
prompt, the message appears again and the restoration can never proceed.

Once this patch is applied on the Boot Server, the SRT needs to be
recreated for this fix to be available. SRTs created with bmrsrtadm
versions prior to the one contained in this patch will have the problem.
--------------------------------------------------------------------------------
Etrack Incident = ET509515

Description:
A change was made to enable version compatibility checking between
bmrsavecfg and the import configuration procedure in bmrd.

Additional Notes:
Clients that are running later versions of NetBackup than the version on
the master server with which they are associated will have failed
bmrsavecfg jobs. Subsequently, no configuration for a backup will be
saved. There will be a message produced in the "Detailed Status" for the
bmrsavecfg job that states the incompatibility.
--------------------------------------------------------------------------------
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 = ET492907

Description:
You can now add Maintenance Packs and Language Packs to Shared Resource
Trees.
--------------------------------------------------------------------------------
Etrack Incident = ET420327

Description:
If a hotfix package name contained non-English characters, it could not be
added to a configuration.
--------------------------------------------------------------------------------
Etrack Incident = ET420099

Description:
The handling of the Chinese character set GB18030 was incorrect.
--------------------------------------------------------------------------------
Etrack Incident = ET532743

Description:
In some cases, BMR was not detecting more than one Solaris SVM metaset
(diskset).
--------------------------------------------------------------------------------
Etrack Incident = ET533706

Description:
Base AIX 5.3 client support was added for BMR in this pack.

Refer to the following TechNote for more specific support limitations.
Note: Advanced features of AIX 5.3 are not yet supported.

http://support.veritas.com/docs/282054
--------------------------------------------------------------------------------
Etrack Incident = ET568191

Description:
Could not retrieve Windows client configurations (PIT) on a Linux master
server.
--------------------------------------------------------------------------------
Etrack Incident = ET567466

Description:
Note on uninstalling the Bare Metal Restore Maintenance Packs
-------------------------------------------------------------
Uninstalling the BMR 6.0 MP2 on the master server

BMR 6.0 MP2 added support for AIX 5.3 clients. To protect AIX 5.3 clients,
the BMR master server, as well as the AIX 5.3 BMR clients, must be using
BMR 6.0 MP2. After the BMR 6.0 MP2 is uninstalled on the master server
(downgraded), AIX 5.3 clients will no longer be supported. However, the
configurations of the AIX 5.3 clients, saved while the master server was
at BMR 6.0 MP2, will continue to show up in the NetBackup Administrative
Console even after the server is downgraded. These configurations cannot
be used to restore the AIX 5.3 clients. Results of attempting such
operations are unpredictable.

Uninstalling the BMR 6.0 MP2 on the boot server

All SRTs that were created while the boot server was at BMR 6.0 MP2, and
all SRTs that were created while the boot server was at BMR 6.0 GA but
used while the boot server was at BMR 6.0 MP2, will not be usable after
the BMR 6.0 MP2 is uninstalled on the boot server. This exception does
not apply to Windows SRTs.
--------------------------------------------------------------------------------
Etrack Incident = ET569498

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



Attachments

NB_BMR_60_7_M.rs6000_308537.tar (65.4 MBytes)


Legacy ID



308537


Article URL http://www.symantec.com/docs/TECH63308


Terms of use for this information are found in Legal Notices