Method to install and upgrade Bare Metal Restore (BMR) Master and Boot Servers

Article:TECH129963  |  Created: 2010-01-12  |  Updated: 2010-01-12  |  Article URL http://www.symantec.com/docs/TECH129963
Article Type
Technical Solution

Product(s)

Environment

Issue



Method to install and upgrade Bare Metal Restore (BMR) Master and Boot Servers

Solution



At release 6.5.X, the Bare Metal Restore Boot Server is always a separately installed software package.
This information is not relevant to the NBU 7.X releases.

UNIX servers installs:

For Unix systems, all of the BMR option software (Master and Boot Server) is in its own install package.
The preferred method for installing BMR option software is:

1.  Using the BMR Option install media, install the base BMR Master Server and Boot Server (as required) software.
The BMR Master Server must be installed on the same server that the NBU Master Server is installed. The location of BMR software and database files are the same as for NBU software and databases.
BMR Boot Servers can be installed on any NetBackup client system.

The install process should automatically enable/configure the BMR database (BMRDB) files.
Install of the Boot Server software should automatically register the server with the BMR Master Server in the BMRDB.
For Boot Server installs on a client system, the server will register with the BMR Master Server that is associated with the client's Master Server setting.


2. Patch the BMR Master Server to the same level as the NBU Master Server.
   You can verify if the patch was correctly installed by running:
   
   /usr/openv/netbackup/bin/bmrs -o query -res database -table CurrentVersion
   
   This should return the same BMRDB schema as the patch release.

You can also check the following text file:

/usr/openv/share/version_bmr      


3. Patch the BMR Boot Server to the same level as the system is already patched to. This level should never be higher than the Master Server level.
  It is recommended that the Boot Server be patched to the same level as the Master Server.
  Installs of the Boot Server patch should also automatically register the new version with the BMRDB on the Master Server.
.
   The BMR process 'bmrd' must be running on the Master Server for this to work properly.  
   The BMRDB must be initialized and available prior to this as well.
   You can verify the Boot Server registration by running (on the Master Server):
   
    /usr/openv/netbackup/bin/bmrs -o list -res BootServer

The installed software level is also shown in the text file at:

    /usr/openv/share/version_bmrboot

The two levels need to match.

If the version information in the BMRDB is not correct, run the following command on the Boot Server to update the version information:

    /usr/openv/netbackup/bin/bmrsetupboot

Verify the update using the command line noted above.

In some instances, particularly with Linux installs, the automatic initialization of the BMRDB will fail if the NBU level of the Master Server is at 6.5.4 or later.
If this is the case, install the patch release normally and then allow the BMRDB to be initialized.  It may be necessary to manually perform this action.
The manual initialization command is:

/usr/openv/netbackup/bin/bmrsetupmaster -patch


Windows Servers installs:

For Windows Systems, only the Boot Server software is still separately installed.  The BMR Master Server is automatically installed with the NBU Master Server install.  
The BMR Master Server still needs to be set up manually. From the desktop choose:

Start -> Programs -> Veritas Netbackup -> Bare Metal Restore - Master Server Setup

From the 6.5 GA release media, choose the option to install additional software.
For Windows 2003 64 bit BMR Client/Boot Server support, you must use the special 6.5.4 install software package as there was no BMR support
for 64 bit OS until then.

Once BMR Boot Server software is installed and properly patched, any subsequent patch activity to the server/client will automatically patch the Boot Server software as well, if it is seen as installed.

For instances where the BMR Boot Server was installed after the Master Server or client was upgraded to a later patch level, the following step must be performed:

In the same folder that holds the patch release level, run the command:

msiexec /l*v <logfile> /i "NetBackup Update.msi" /qn ADDLOCAL=BMR_RU_x86    (for 32 bit installs)
msiexec /l*v <logfile> /i "NetBackup Update.msi" /qn ADDLOCAL=BMR_RU_AMD64  (for 64 bit installs)

Substitute a file path/name of your choice for <logfile> that will hold the output log of the patch process.

IMPORTANT NOTES:  

1.  Due to a defect in the Windows patch mechanism, the use of the 'Repair Mode" patch install at any 6.5.X release will not perform properly in certain circumstances but will not generate an error message.  The Boot Server software will potentially still remain at the 6.5.0 level. The use of the "msiexec" command above will always correctly install the Boot Server software.

2.  It is never recommended to remove a NetBackup patch release back to the 6.5. GA release in order to then patch upgrade the BMR Boot Server.

3. You can always check to see the release version of the BMR Boot Server by running, on the Master Server:

$INST_PATH\NetBackup\bin\bmrs -o list -res BootServer

4. Another method is to check the following text file (on the Boot Server):

$INST_PATH\Netbackup\share\version_bmrboot.txt

Again, both versions noted should match. If not invoke the command:

$INST_PATH\NetBackup\bin\bmrsetupboot

The same registration restrictions are in effect as for a UNIX Boot Server.




Legacy ID



352285


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


Terms of use for this information are found in Legal Notices