BMR 6.5 Pack NB_BMR_6.5.3 README                               November 10, 2008
Requirement: NB_6.5.3
Corequirement: NB_BBS_6.5.3
Directives: BMRDB_Upgrade BMRDB_Recover
SeqNumber: 20080731
================================================================================
This Release Update provides updates and fixes for Veritas NetBackup(tm)
Bare Metal Restore (BMR).

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


====================
RELEASE DEPENDENCIES
====================
    --  NB_6.5.3_<6 digit number>.<server>.tar must be installed before this
        Release Update is installed.

    --  Only if Bare Metal Restore Boot Server is installed,
        NB_BBS_6.5.3_<6 digit number>.tar must be installed after this Release
        Update is installed.

    -- Installation of this Release Update requires version 1.6.4.14.4.2 of
       the NB_update.install script.



I.    NEW FEATURES AND PLATFORM PROLIFERATIONS
II.   KNOWN ISSUES
III.  DOWNLOAD INSTRUCTIONS
IV.   INSTALLATION INSTRUCTIONS
V.    UNINSTALL INSTRUCTIONS
VI.   CURRENT RELEASE UPDATE INDEX  
VII.  RELEASE UPDATE CONTENT
        Conventions
        Current Release Update
           NB_BMR_6.5.3
        Release Update History
           NB_BMR_6.5.2
           NB_BMR_6.5.1




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




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

This section contains known issues with this Release Update that have not
yet been fixed in NetBackup.  These issues will likely be fixed in future
Release Updates for this version of NetBackup.

+  (ET1455616) An issue exists that can cause a BMR task to hang when
  BMR-enabled backup policies are started. After you have finished upgrading
  the NetBackup and BMR master server to NetBackup 6.5.3, backups that have
  the Collect BMR Information option enabled in the BMR backup policy can hang
  while the bmrd process consumes a significant percentage of CPU cycles. It
  is possible that this issue could affect other non-BMR-enabled backups
  because of potential CPU and memory resource contention.

  For more information and a solution on this issue, refer to the following
  TechNote on the Symantec Support Web site.

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

+  The Storage area network support section on page 103 of the NetBackup
  Bare Metal Restore Administrator's Guide contains the following note:

  Note: BMR does not support the restoration of systems with SAN attached
        volumes.

  This note is incorrect.  BMR does support the restoration of SAN-attached
  volumes. This note will be removed in the next revision of this document.

+  Dissimilar Disk Restore of a Solaris client fails if the client uses SVM
  metadevices (volumes) created using slice 2 of Solaris Disks. For more
  information on this issue, refer to the following TechNote on the Symantec
  Support Web site.

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

+  The following items are corrections that will be made to the NetBackup 6.5
  Bare Metal Restore (BMR) Administrator's Guide at the next major release of
  NetBackup.

  In the Storage Area Network Support section of Chapter 6, Restoring Clients,
  the following text appears:

     Bare Metal Restore can restore a system that is attached to a Storage Area
     Network (SAN). On Windows, AIX, and Solaris systems, if the host bus
     adapter (HBA) drivers are available in the restore environment, BMR
     automatically restores the SAN-attached volumes. BMR does not support the
     restoration of systems with SAN attached volumes on HP-UX and Linux.

  The following text is the correct replacement text.

     Bare Metal Restore can restore a system that is attached to a Storage Area
     Network (SAN). If the host bus adapter (HBA) drivers are available in the
     restore environment then
     -  On Solaris 10, BMR automatically restores the SAN-attached boot and
        data volumes.
     -  On Solaris 8 and Solaris 9, BMR automatically restores the SAN-attached
        data volumes.
     -  On Windows, BMR automatically restores the SAN-attached data volumes.
     -  On AIX, BMR automatically restores the SAN-attached data volumes.
     -  On HP-UX and Linux, BMR does not support the restoration of systems
        with SAN attached volumes.

  In the Configuration Summary section of Chapter 10, Managing clients and
  configurations the following text should be added:

     Client configuration can be modified to add, change and remove a license
     key for software discovered for a protected system. The license key, which
     is added or changed, is also added to the protected system after restore
     using the configuration to which the key was added. This facility is
     available only for Veritas Storage Foundation products.

+  (ET1414771) A BMR Fast Restore of a Windows client with a single partition
  fails with the following error message.

     Failed to run X:\BMR\NBU\BIN\BMRRST.EXE - begin

  When attempting a BMR restore of Windows clients with a single system or boot
  partition, the process could fail during the Finalizing Restore step with the
  error message mentioned above:

  If you encounter any issues attempting a BMR Fast Restore of a Windows client
  with a single partition, please consult with a Symantec Support representative
  for further guidance.




==========================
III. DOWNLOAD INSTRUCTIONS
==========================

1) Download NB_BMR_6.5.3_<6 digit number>.tar into the
  /tmp directory.

       where <6 digit number> is an internal tracking identifier

                           
2) Extract NB_BMR_6.5.3_<6 digit number>.tar
       /bin/tar -xvf NB_BMR_6.5.3_<6 digit number>.tar

       This will create the files:
       VrtsNB_BMR_6.5.3.README
       VrtsNB_BMR_6.5.3.<platform>.tar.Z
       VrtsNB_BMR_6.5.3.postinstall
       VrtsNB_BMR_6.5.3.preuninstall
       NB_update.install

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




=============================
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 Release Update.

For Release Update installation on a UNIX Cluster Environment:
--------------------------------------------------------------------------------
1) Before you install this Release Update, make sure that NetBackup is at
  release level 6.5 and configured to run in a cluster.

2) Install all 6.5.3 Release Updates on the inactive node(s) of the cluster
  (perform steps 1 through 3 below).

3) Install all 6.5.3 Release Updates on the active node of the cluster (perform
  steps listed below).

4) If the cluster is in a faulted state, clear the fault.

--------------------------------------------------------------------------------

As root on the NetBackup Master:

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) Install the Release Update binaries.

     cd /tmp
     /bin/sh NB_update.install

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

     /usr/openv/netbackup/bin/bp.start_all

3) The Release Update 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 Release Update from your local machine.

   
  1)Close the NetBackup user interfaces.

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

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

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

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

  3)Run the un-install script:

         ./NB_update.uninstall

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

  5)If necessary, restart the NetBackup and Media Manager daemons:
       
       /usr/openv/netbackup/bin/bp.start_all




================================
VI. CURRENT RELEASE UPDATE 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_6.5.3
--------
1275559 1302929 1302749 1317013 1317008 1317006 1317202 1317047 1276489 1318091
1289921 1322984 1364407 1364422 1322803 1364661 1373019 1383374 1382658 1383586
1383584 1184889 1276613 1382632 1383839 1383438 1383440 1383434 1383442 1383733
1383750 1383540 1384029 1375483 1383736 1383527 1383523 1384879 1385083 1385111
1386294 1383757 1384675 1383511 1385061 1382599 1376805 1383782 1383502 1383497
1383499 1384270 1386057 1386060 1383811 1383808 1382683 1384822 1386064 1386062
1386073 1383727 1383766 1386069 1384960 1386075 1386077 1384019 1386065 1386070
1387046 1383743 1384952 1387039 1383643 1384946 1384943 1388149 1384948 1383744
1386199 1384909 1389088 1374330 1388180 1383756 1388192 1382684 1383404 1390335
1383742 1383761 1391168 1382623 1391109 1383763 1394025 1383630 1392132 1388236
1384020 1395057 1384919 1383792 1383772 1393919 1384032 1384023 1384966 1395393
1383506 1396153 1391110 1397984 1399794 1393810 1393798 1397604 1398627 1388000
1387827 1393793 1396248 1402394 1396112 1395233 1402922 1403920 1405290 1402967
1320530 1398698 1396083 1392668 1409131 1409154 1411251 1411776 1410874 1412331
1408807 1412417 1413338 1411302 1413269 1410786 1413572 1385085 1414212 1412557
1415612 1413649 1401482 1413567 1415683 1414541 1416768 1421025 1425093 1424266
1423453 1425900 1425285 1428096 1423583 1426958 1427064 1429629 1430825 1428794
1431220 1428632 1432786 1431217 1431957 1432152 1432733 1431905 1436492 1436738
1439637

NB_BBS_6.5.3
------------
1386047 1383479

NB_BMR_6.5.3
------------
1289330 1385881

NB_CLT_6.5.3
------------
1275559 1302929 1302749 1317013 1317008 1317006 1317202 1317047 1276489 1318091
1289921 1322984 1364407 1364422 1322803 1364661 1373019 1383374 1382658 1383586
1383584 1184889 1276613 1382632 1383839 1383438 1383440 1383434 1383442 1383733
1383750 1383540 1384029 1375483 1383736 1382523 1383527 1383523 1384879 1385083
1385111 1386294 1383757 1384675 1383511 1385061 1382599 1384892 1376805 1383782
1383502 1383497 1383499 1384270 1386057 1386060 1383811 1383808 1382683 1384822
1386064 1386062 1386073 1383727 1383766 1386069 1384960 1386075 1386077 1384019
1386065 1386070 1387046 1383743 1384952 1387039 1383643 1384946 1384943 1388149
1384948 1383744 1386199 1384909 1389088 1374330 1388180 1383756 1388192 1382684
1383404 1387984 1390335 1383742 1383761 1391168 1382623 1391109 1383763 1394025
1383630 1392132 1388236 1384020 1395057 1384919 1383792 1383772 1393919 1384032
1384023 1384966 1395393 1383506 1396153 1391110 1397984 1399794 1393810 1393798
1397604 1398627 1388000 1387827 1393793 1396248 1402394 1396112 1395233 1402922
1403920 1405290 1402967 1320530 1398698 1396083 1392668 1409131 1409154 1411251
1411776 1410874 1412331 1408807 1412417 1413338 1411302 1413269 1410786 1413572
1385085 1414212 1412557 1415612 1413649 1401482 1413567 1415683 1414541 1416768
1421025 1425093 1424266 1423453 1425900 1425285 1428096 1423583 1426958 1427064
1429629 1430825 1428794 1431220 1428632 1432786 1431217 1431957 1432152 1432733
1431905 1436492 1436738 1439637

NB_DB2_6.5.3
------------
1388132

NB_DMP_6.5.3
------------
1384031

NB_INX_6.5.3
------------
1404905 1416672

NB_JAV_6.5.3
------------
1316222 1316255 1316257 1383469 1386728 1388080 1393518 1400256

NB_LOT_6.5.3
------------
1318437

NB_LUA_6.5.3
------------
1380529

NB_NOM_6.5.3
------------
1383447 1384380 1390067 1391157 1391161 1395092 1399345 1409923 1409925 1423226


NB_SAP_6.5.3
------------
1227447 1386537 1227458 1411527

NB_SMU_6.5.3
------------
1387861 1387867

NB_SNC_6.5.3
------------
1383582 1383429 1382596 1383498 1384025 1394039 1395089 1383512 1401373 1398467
1410597

NB_VLT_6.5.3
------------
1383258 1385764 1386756 1385614 1386760 1386763 1386750 1396286 1402907 1404850





===========================
VII. RELEASE UPDATE CONTENT
===========================
This section contains the Release Update 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 Release Update
subsection describes a feature, enhancement, or issue fixed with this
Release Update.

Description
    Describes a particular problem contained in this release update.

** 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 Release Update
----------------------
Each item listed in this section describes a feature, enhancement, or change
that comprises this Release Update. Please read this section thoroughly to
understand the contents of this update.  
--------------------------------------------------------------------------------
Etrack Incident = ET1289330

Description:
   Changes have been added to ensure that the BMR database levels match those
   of the NetBackup server.
--------------------------------------------------------------------------------
Etrack Incident = ET1385881
Associated Primary Etrack = ET1297511
Titan cases:  311-927-527

Description:
   When adding a driver package to a BMR-Windows Client's configuration,
   the operation takes a long time. While performing a Prepare To Restore (PTR)
   for a BMR client on such a setup, the PTR operation would also take a long
   time to complete.

Additional Notes:
   The problems described above are due to some unnecessary redundancies in
   the BMR database. A fix has been added to make sure that no new unnecessary
   redundancies get added to the database, but it does not eliminate the
   existing, unnecessary redundancies from the BMR database.
   
   Please contact Symantec Support for help on removing the existing
   unnecessary redundancies.
--------------------------------------------------------------------------------



Release Update History
----------------------

This section contains an accumulative list of all Release Update information
contained in previous releases.

============
NB_BMR_6.5.2
============
Etrack Incident = ET1154522

Description:
   Restore of Linux client fails if the PC BIOS has "Virtual Floppy" enabled.

Workaround:
   If you encounter this issue, perform the following steps.
     1. Turn off "Virtual Floppy" in BIOS.
     2. Re-import the client configuration bundle.dat file from the backup.
     3. Re-run bmrprep (Prepare To Restore).
     4. Repeat the restoration process.
--------------------------------------------------------------------------------
Etrack Incident = ET1159519

Description:
   Veritas Volume Manager (VxVM) disk enclosure-based names can be incorrectly
   numbered in "vxdisk list" output after a BMR restoration.

Workaround:
   To resolve this issue, remove the file /etc/vx/disk.info and then reboot
   the client.
--------------------------------------------------------------------------------
Etrack Incident = ET1151769

Description:
   Bmrprep would core dump if a client configuration had Veritas File System
   (VxFS) license keys installed but the VxFS software was not installed on
   the client.
--------------------------------------------------------------------------------
Etrack Incident = ET1155166

Description:
   EMC Powerpath disks were not allowed to be added to AIX and HP-UX
   volume groups.
--------------------------------------------------------------------------------
Etrack Incident = ET1166346

Description:
   HP-UX volume groups had invalid size values after performing Dissimilar
   Disk Restore (DDR) mapping operations.
--------------------------------------------------------------------------------
Etrack Incident = ET1155438

Description:
   Reimporting the same Windows discovered configuration is incorrectly allowed
   and yields a duplicate configuration entry.

Workaround:
   If you encounter this issue, delete the configuration entries by using the
   following command and then reimporting the discovered configuration.
   
      bmrs -o delete -r config -client <client> -config <config>
--------------------------------------------------------------------------------
Etrack Incident = ET1158002

Description:
   Unable to map VxVM disk groups that were based originally on EMC Powerpath
   disks to non-EMC Powerpath disks.
--------------------------------------------------------------------------------
Etrack Incident = ET1160488
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 resolve this issue, bring the volume group online or remove the offline
   volume group.
--------------------------------------------------------------------------------
Etrack Incident = ET1036244

Description:
   Deleting a client copied configuration does not delete the hidden
   "current.<timestamp>" version of the configuration.

Workaround:
   If you encoutner this issue, delete the configuration with the following
   command.
   
     bmrs -o delete -r config -client <client> -name current.<timestamp>
--------------------------------------------------------------------------------
Etrack Incident = ET1172180

Description:
   HP-UX clients utilizing 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:
   If you encounter this issue, run the following command in a maintenance
   shell.
   
     setboot -p <boot disk path>
--------------------------------------------------------------------------------
Etrack Incident = ET1155550

Description:
   A change was made to provide a better method for breaking mirror volumes
   in one operation when performing dissimilar disk mapping operations.
--------------------------------------------------------------------------------
Etrack Incident = ET1182144

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

Description:
   Restoration of Solaris clients utilizing zones no longer fail because a
   syntax error in the restore script function fixZoneDevices() has been fixed.
--------------------------------------------------------------------------------
Etrack Incident = ET1169652

Description:
   The restore process on a BMR Linux client would attempt to recreate
   Linux-LVM related data structures (such as, PVs, VGs, and LVs) on
   EMC-PowerPath disks although the disks were supposed to be restricted
   during a BMR restore.
--------------------------------------------------------------------------------
Etrack Incident = ET1212629
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 = ET1213218

Description:
   A user no longer needs to capture a screen shot of disk comparisons when a
   restore triggers the auto-discovery mode.
--------------------------------------------------------------------------------
Etrack Incident = ET1212201
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 = ET1219749
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 = ET1222715
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 = ET1168789

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

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

Description:
   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 = ET1234202
Associated Primary Etrack = ET1231920
Titan cases:  290-954-916

Description:
   Very large imported Solaris client configuration would cause BMR functions
   on the configuration to exhibit very poor performance.
--------------------------------------------------------------------------------





============
NB_BMR_6.5.1
============

Etrack Incident = ET1065640
Associated Primary Etrack = ET1064866
Titan cases:  240-587-968

Description:
   Bmrd would core dump and fail to import a Solaris client
   configuration that contained Solaris Volume Manager meta devices.
--------------------------------------------------------------------------------
Etrack Incident = ET596414
Associated Primary Etrack = ET596413
Titan cases:  280548990

Description:
   BMR did not properly support the backup and restoration of Solaris
   clients that had EMC Powerpath disks.
--------------------------------------------------------------------------------
Etrack Incident = ET1052364

Description:
   BMR leaves VxSS login credentials from the restore session on the
   client after it first boots.

Workaround:
   To avoid this issue, remove the root user version of the credentials
   file, /.vxss/credentials.
--------------------------------------------------------------------------------
Etrack Incident = ET1100827
Associated Primary Etrack = ET1100064
Titan cases:  320-060-202

Description:
   Remapping a VxVM encapsulated root disk on Solaris that originally
   contained two copy mirror volumes to one disk to break the mirrors
   causes the root volume ("rootvol") and swap volume ("swapvol") to
   have the wrong use_type field. It is incorrectly being set to "fsgen".
   This causes the machine to fail to boot after the restoration has
   completed because of the perceived absence of a root volume.

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 the 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 a normal restoration.
--------------------------------------------------------------------------------
Etrack Incident = ET1094236
Associated Primary Etrack = ET596413
Titan cases:  280548990

Description:
   BMR did not function correctly when AIX and HP-UX clients were
   utilizing EMC Powerpath disks.
--------------------------------------------------------------------------------
Etrack Incident = ET1100179

Description:
   The BMR "Prepare To Discover" operation on the NetBackup
   Administration Console failed with a error for Windows systems.
--------------------------------------------------------------------------------
Etrack Incident = ET1039434

Description:
   Filling a Linux LVM1 volume group with DDR can cause the restoration
   to fail.

Workaround:
   When mapping volumes to an LVM1 (not LVM2) volume group for a
   Linux client, leave some free space in the volume group that is
   equivalent to the size of one physical extent.
--------------------------------------------------------------------------------
Etrack Incident = ET1116060

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

Description:
   Added a change so that BMR functions correctly when Linux clients
   are utilizing EMC Powerpath disks.
--------------------------------------------------------------------------------
Etrack Incident = ET1109595
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 = ET1115945
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 Release Update, 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 = ET1119045

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 = ET1125002
Associated Primary Etrack = ET1124350
Titan cases:  240-626-530

Description:
   Restoration of a client with a DMP attached fiber device
   utilizing VxVM failed during VxVM disk initialization operations.
--------------------------------------------------------------------------------
Etrack Incident = ET1131127
Associated Primary Etrack = ET1121777
Titan cases:  230408646

Description:
   When attempting a Media Boot on a client that is on an isolated
   subnet with an SRT that was created with Solaris 10 DVD 11/06
   Update 3, the Media Boot fails after the restore procedure invoked
   the following tar command:
      /usr/bin/tar -xf /cdrom/Solaris_10/Tools/Boot/bmr/vxvm.tar
   
   It failed because of the following existing directory:
      tar: ./tmp/root/usr: symbolic link failed: File exists

Workaround:
   To avoid this issue, perform one of the following examples:
   - Use the media boot with an SRT of Solaris-10 03/05 CD  
   OR
   - Use the network boot with an SRT of Solaris 10 03/05 CD or
     11/06 CD.

Additional Notes:
   Setup Configuration:
   ====================
   This issue occurred with the following configuration:
   
   Master server:  
   OS:Solaris 10
   NetBackup / BMR version: nbu6.0+MP4
         
   BMR client:
   OS: Solaris 10
   NetBackup / BMR version:nbu6.0 +MP4
   VXVM: Storage Foundation 4.1 MP1
--------------------------------------------------------------------------------
Etrack Incident = ET1143101

Description:
   A backup job on a Linux client using a policy that has BMR
   enabled would hang for about 15 minutes after which it would
   time-out with an error.  A change was made to the BMR master
   server daemon, bmrd to correct this issue.
--------------------------------------------------------------------------------
Etrack Incident = ET1148419

Description:
   The restoration of an AIX client that was utilizing a JFS2 file
   system with an INLINE log would fail.
--------------------------------------------------------------------------------
Etrack Incident = ET1161249

Description:
   BMR-enabled backup jobs would fail when backing up a BMR client with
   a Linux 2.6 kernel.
   
   This problem was encounter during a backup of a BMR client with
   Linux 2.6, when an LVM volume was created in a Volume Group (VG),
   that was then created using a Physical Volume (PV) on a Multi
   Device (MD).  The problem occurred because the BMRD server crashed
   during the backup job.