Hotfix NB_PDE_6.5.1.1.tar provides critical fixes to Symantec Veritas NetBackup (tm) PureDisk Remote Office Edition 6.5.1.

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


Environment

Issue



Hotfix NB_PDE_6.5.1.1.tar provides critical fixes to Symantec Veritas NetBackup (tm) PureDisk Remote Office Edition 6.5.1.

Solution



Name: NB_PDE_6.5.1.1
Date: March 26, 2009

==============================================================================
This hotfix provides a fix to
the Veritas NetBackup PureDisk Remote Office Edition 6.5 software.

WARNING: When you apply this fix, the Web UI will be restarted
==============================================================================

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

Install PureDisk 6.5.1 before you install this hotfix.


=============
PRODUCT FIXES
=============

This hotfix fixes the following issue as described in
Tech Alert 321408 (http://support.veritas.com/docs/321408):

   The parameter 'Remove versions backed up : Older than (in days)'
   specified in a 'Time Based Data Removal Policy' is always interpreted as zero.
   This implies that only the last version of every file is retained.
   For files that were deleted (on the source/client) before the latest backup,
   no version will be retained at all.
   
   * This bug leads to incomplete point-in-time restores.
     If you select 'Restore version from date',
     several files will be missing from the restore.

   * This bug does NOT affect restores from the latest version.
     If you select 'Restore latest version', the restore will be correct.
   
   Data Removal Policies using Version Based Data Removal are NOT affected.
   Only 6.5.1 is affected.
   Any other versions: 6.5.0, 6.5.0.1, 6.2.2, 6.1_MP2_P01, ... are NOT affected.

(Internal reference: ET 1557553)

=====================
DOWNLOAD INSTRUCTIONS
=====================

1.  Use rcp or scp to copy the tar file, NB_PDE_6.5.1.1_321603.tar,
   to the /root directory of the PureDisk node that hosts the storage pool authority.

2.  Log on as root to the node that hosts the storage pool authority.

3.  Type cd /root to go to the /root directory.

4.  Type the following command to verify the integrity of the Patch:

       md5sum /root/NB_PDE_6.5.1.1_321603.tar

   This command computes the md5 checksum of the Patch.  The md5
   checksum of the Patch must match '2894c7b333118287cabc52ea58c3c22a'.

   If you obtain a different checksum, the Patch was corrupted during
   download. Try to download the Patch again.

5.  Type the following command to extract the README file:

       tar -C / -xf /root/NB_PDE_6.5.1.1_321603.tar ./NB_PDE_6.5.1.1.README

=========================
INSTALLATION INSTRUCTIONS
=========================

1.  Make sure that no PureDisk jobs are currently running or are scheduled to be run.

2.  Log out from the Web UI.

3.  (Conditional) Freeze PD service groups for clustered PD server.

   Perform this step if the storage pool is installed with VCS cluster
   software.  Use the Cluster Manager Java Console, and freeze all the service
   groups.

   For information about how to freeze and unfreeze clustered storage pools,
   see the Veritas NetBackup PureDisk Storage Pool Installation Guide.

4.  Type the following command to unpack the Patch software:

       tar -C / -xf /root/NB_PDE_6.5.1.1_321603.tar ./opt

5.  Type the following command to run and install the Patch:

       /opt/pdinstall/apply-NB_PDE_6.5.1.1.sh

   If the topology.ini file is encrypted, the software prompts you for the
   password to decrypt this file.

   The Patch automatically pushes the software to all nodes in the
   storage pool and to all clients.

   At the end of a successful installation, the software prompts you to encrypt
   the topology.ini file.

6.  (Conditional) Unfreeze PD service groups for clustered PD server.

   Perform this step if the storage pool is installed with VCS cluster
   software.

   The Veritas Cluster Server (VCS) software might detect some faults
   during the upgrade process.  If any upgrade actions generate a VCS fault,
   use the Cluster Manager Java Console to clear the fault and probe that
   resource group before you unfreeze the cluster.



Attachments

NB_PDE_6.5.1.1_321753.tar (100 kBytes)


Legacy ID



321753


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


Terms of use for this information are found in Legal Notices