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

Article:TECH46845  |  Created: 2006-01-22  |  Updated: 2006-01-27  |  Article URL http://www.symantec.com/docs/TECH46845
Article Type
Technical Solution


Environment

Issue



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

Solution



BMR 6.0GA Pack NB_BMR_60_2_M README March 23, 2006
Requirement: NB_60_2_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_2_M_<6 digit number>.<server>.tar must be installed before this
Maintenance Pack is installed.

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


I. DOWNLOAD INSTRUCTIONS
II. INSTALLATION INSTRUCTIONS
III. UNINSTALL INSTRUCTIONS
IV. DESCRIPTION OF PROBLEMS FIXED
Current Pack
NB_BMR_60_2_M

Pack History
None

=========================
I. DOWNLOAD INSTRUCTIONS
=========================
1) Download NB_BMR_60_2_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_2_M_<6 digit number>.<platform>.tar
/bin/tar -xvf NB_BMR_60_2_M_<6 digit number>.<platform>.tar

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

==============================
II. INSTALLATION INSTRUCTIONS
==============================
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

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

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

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.


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


==================================
IV. DESCRIPTION OF PROBLEMS FIXED
==================================
The following are descriptions of the problems fixed. Please read the entire
document before installing.

README Conventions:

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 patch level.

Additional Notes
Any additional information regarding a problem or feature is included.

=============
Current pack
=============

================================================================================
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 modeand 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 mirror 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.
================================================================================

============
Pack History
============

Nothing to report for this release.

Attachments

NB_BMR_60_2_M_282394.linux.tar (20.4 MBytes)


Legacy ID



282394


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


Terms of use for this information are found in Legal Notices