NB_PDE_6.5.1.2_EEB14-rollup1 is a PureDisk 6.5.1.2 EEB (Emergency Engineering Binary) package for PureDisk servers.

Article:TECH77314  |  Created: 2009-01-25  |  Updated: 2009-01-25  |  Article URL http://www.symantec.com/docs/TECH77314
Article Type
Technical Solution


Environment

Issue



NB_PDE_6.5.1.2_EEB14-rollup1 is a PureDisk 6.5.1.2 EEB (Emergency Engineering Binary) package for PureDisk servers.

Solution



Name: NB_PDE_6.5.1.2_EEB14-rollup1
Date: May 06, 2009

==============================================================================
This Engineering Binary provides features and fixes to the Veritas NetBackup
PureDisk Remote Office Edition 6.5 software.
==============================================================================

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

Install PureDisk 6.5.1.2, before you install this Engineering Binary.

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

- MB Garbage Collection, with the parameter 'extensive cleanup' enabled,
 removes "delete Pos" (modtype: D) entries from the Metabase
 before previous versions of that file have been marked as expired.
 This causes delay in Data removal and an increase of Storage usage.
 It is recommended to mark all Data Selections as dirty to re-insert
 the "delete POs" again, if 'extensive cleanup' was enabled.
 (From 6.5.1_EEB03-mbgc_del_pos, Internal reference: ET 1481748)
 http://entsupport.symantec.com/docs/320755
 http://entsupport.symantec.com/docs/320756

- Replication now contains retry mechanism, which restarts the entire job step
 inside the same job, when an error occurs (e.g. network interrupt).
 To enable this feature: change 'maxretrycount' in the [replication] section
 to a value higher than 1 through 'Configuration File Templates' in the
 PureDisk UI. Next execute 'Push Configuration Files'.
 (From 6.5.1_EEB05-replication_retry, Internal reference: ET 1513110)

- Pre-6.5.1 Data Selections still contained slow VIEWs in the Metabase.
 With this fix replication of these Data Selections becomes much faster.
 (From 6.5.1_EEB09-update_old_ds_views, Internal reference: ET 1542049, ET 1557416)
 http://entsupport.symantec.com/docs/323254

- Error 'Could not find parent dir' during MBImport, caused by parent directory
 having trailing white space.
 (From 6.5.1_EEB10-mbe_parent_id, Internal reference: ET 1555757)
 http://entsupport.symantec.com/docs/313970

- Error 'FilesetIterator Exception occurred while evaluating' during MBImport,
 fixed by using prepared statements and handling NULL values properly
 (From 6.5.1_EEB10-mbe_parent_id, Internal reference: ET 1287876, 1402477)
 http://entsupport.symantec.com/docs/308776

- Error 'portal C_7 does not exist' during MBImport
 (From 6.5.1_EEB10-mbe_parent_id, Internal reference: ET 1414971)
 http://entsupport.symantec.com/docs/316202

- Replication: mode field of fake POs is incorrect,
 causing problems when restoring NBU export of such a directory
 (From 6.5.1_EEB10-mbe_parent_id, Internal reference: ET 1486573)

- Restores from a dataselection which has corruption within it complete (Success
 with Errors) if you use a single stream. However the same restore will fail with
 '[2]Invalid argument supplied for foreach()' if multiple streams are selected.
 (From 6.5.1_EEB12-restore_multi_stream_stats, Internal reference: ET 1543791)
 http://entsupport.symantec.com/docs/333203

- Maintenance jobs now show progress info for every 100 jobs or policy runs being removed
 (Internal reference: ET 1542390)  

- URL and DNS validation fails is hostname contains an underscore
 (Internal reference: ET 1633947)

- "Memcache::connect(): Can't connect to 127.0.0.1:11211" randomly occurring
 (Internal reference: ET 1603599)

- Central Reporting: Capacity Report reports incorrect Frontend Storage
 (Internal reference: ET 1630596)


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

1.  Use rcp or scp to copy the tar file, NB_PDE_6.5.1.2_EEB14-rollup1.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 Engineering Binary:

       md5sum /root/NB_PDE_6.5.1.2_EEB14-rollup1.tar

   This command computes the md5 checksum of the Engineering Binary.  The md5
   checksum of the Engineering Binary must match '42e565f6b8decf38412db79859cf149f'.

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

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

       tar -C / -xf /root/NB_PDE_6.5.1.2_EEB14-rollup1.tar ./NB_PDE_6.5.1.2_EEB14-rollup1.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 Engineering Binary software:

       tar -C / -xf /root/NB_PDE_6.5.1.2_EEB14-rollup1.tar ./opt

5.  Type the following command to run and install the Engineering Binary:

       /opt/pdinstall/apply-NB_PDE_6.5.1.2_EEB14-rollup1.sh

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

   The Engineering Binary 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


Attachments

NB_PDE_6.5.1.2_EEB14-rollup1_337816.tar (1.1 MBytes)


Legacy ID



337816


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


Terms of use for this information are found in Legal Notices