Veritas NetBackup (tm) PureDisk Remote Office Edition 6.1 Maintenance Pack 2 (MP2) - Symantec Corporation NB_PDE_61_MP2_290104.tar


Veritas NetBackup (tm) PureDisk Remote Office Edition 6.1 Maintenance Pack 2 (MP2) - Symantec Corporation NB_PDE_61_MP2_290104.tar


Name: NB_PDE_61_MP2
Date: July 31, 2007

This maintenance pack provides features and fixes to the Veritas NetBackup
PureDisk Remote Office Edition 6.1 software.

WARNING: When you apply this maintenance pack, all PureDisk services stop
        and start.  This can cause running jobs to abort.


Install PureDisk 6.1 MP1A (NB_PDE_61_MP1A_287416) before you install
this maintenance pack.


This maintenance pack adds a Server Maintenance policy that vacuums the databases.
To see this policy, expand the workflows tab and look under Storage pool management
policies.  The default policy is configured to run daily.


* PHP component upgrade to PHP 5.2.3. This upgrade improves PureDisk security,
 performance, and stability.

* SNMP fixes.  This fix adds the sysuptime variable to the SNMP packet.

* PureDisk disaster recovery improvements.  PureDisk no longer restores
 the NetBackup data dictionary to the PureDisk node during a disaster
 recovery backup.

 If the data dictionary is found locally, this file is used. If not, the
 file is retrieved from the NetBackup server.

 NOTE: After you apply this patch, it is not possible for the first run
 of the disaster recovery workflow to find a local data dictionary.
 PureDisk retrieves it from the NetBackup server. Please verify that the
 necessary media is loaded before you start a PureDisk disaster recovery

* MBDataMining workflow fixes.  This maintenance pack addresses the
 following problems:

 - MBDataMining fails with 'Authentication for user 'Login' failed'
 - MBDataMining gathers too much information and times out
 - MBDataMining does not clean up report when it fails

 After you apply this maintenance pack, the following conditions exists:

 - Reports for previous MBDataMining runs might be retrievable only through
   the Data Management tab in the Web UI.

 - The next MBDataMining run might fail to complete because the report
   table still contains partial data from the previous failed run.

* Controller fixes.  These fixes address the following problems:

 - Unresponsiveness that makes the storage pool freeze.
 - Intermittent crashes.
 - Stalled communication to and from the agent that causes slow system
   performance and stalled jobs.

* Metabase performance and memory management improvements.  These improvements

 - Elimination from the database of several seldom used indexes.
 - An increase to 2,000,000 of the free space mapping value.
 - Vacuum done on a per table and on a regular basis.
 - Metabase garbage collection uses less memory and no longer fails due
   to an out-of-memory condition.

* Workflow engine fix.  This fix prevents stalls during queue processing.

* Behavioral consistency improvements.  These fixes make PureDisk behavior
 consistent when you apply policies to data selection templates.

* New client agents.  This maintenance pack contains updated client agent
 software for the following platforms:

 - Windows 32-bit
 - Windows 64-bit (x64)
 - AIX
 - Solaris SPARC 8, 9, 10
 - Linux

 Fixes to all of these agents include the following:

 - Upgrade from PHP 5.1.2 to 5.2.3
 - Improved pdengine.exe event handling
 - Improved web service logging
 - Fix for failing backup on client systems with more than 4 Gbyte
   of internal memory

 Fixes to the Windows agents include the following:

 - Fix to System State and Services backups on systems that use Microsoft
   File Server Resource Manager.

 - Fixes to address problems with file access time being modified during backup.

 - Fixes to the PLscanFileSystem.  It no longer fails when you have special file
   types, like sparse files and reparse points, on your file system.

 - A fix that changes the port for snapshotting from port 2000 to port 7325.

 - A new VxFI package necessary for the use of VSS (snapshotting).

* Kernel update for PDOS.  This maintenance pack contains a script that you can
 use to upgrade your kernel to version  Compared to version,
 this new kernel contains security and reliability updates that improve security,
 performance, and stability.

    You need to run this script manually on each node after you upgrade
    to 6.1 MP2.  See the installation instructions in this README.

    If you installed custom kernel modules that enable specific hardware
    recognition, the upgrade software does not upgrade these modules
    to work properly with the new kernel.  Please contact your
    hardware provider, to make sure that you have an updated version for these
    kernel modules available, before you start the kernel upgrade.

    Not upgrading possible custom kernel modules can lead to non-functional
    hardware (no hard disk, no network interface) after reboot.


1.  Use rcp or scp to copy the tar file, NB_PDE_61_MP2_290104.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 maintenance pack:

       md5sum /root/NB_PDE_61_MP2_290104.tar

   This command computes the md5 checksum of the maintenance pack file.  The md5
   checksum of the maintenance pack file must match '363871c26fcea45bcd96a41f7111ae0b'.

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

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

       tar -C / -xf /root/NB_PDE_61_MP2_290104.tar ./README.txt


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

2.  Log out from the Web UI.

3.  Type the following command to unpack the maintenance pack software:

       tar -C / -xf /root/NB_PDE_61_MP2_290104.tar ./opt

4.  Type the following command to run and install the maintenance pack:


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

   The maintenance pack 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.

5.  On each node, run the following script to update the PDOS kernel:


   This upgrade script generates some internal messages.  You can safely
   ignore the following message during the kernel upgrade:

       Cannot determine dependencies of module <modulename>.
       Is modules.dep up to date?

6.  (Conditional) On each node, apply vendor-specific kernel modules.

   Perform this step if you had installed vendor-specific kernel modules on your
   PureDisk nodes.  Failure to apply these modules can lead to nonfunctioning
   hardware.  Contact your hardware provider for assistance or for modules.

7.  Update your existing Maintenance policy and review the new Server Maintenance

   Click the Workflows tab to see these two workflows.  Note the following:

   - The Maintenance policy now only removes temporary files on both server
     nodes and clients.  Symantec recommends that you run this once a month or
     once every 2 weeks.

   - The Server Maintenance policy will only vacuum the databases.  This
     maintenance action removes unreferenced and unnecessary data from the databases
     and is necessary not to slow down the operation of the databases.
     Symantec recommends that you run this once a day, which is the current

8.  Monitor the client agent update jobs.

   Take the following actions to monitor the client agent upgrade jobs:

   A.  Invoke the Web UI.
   B.  Click the Workflows tab.
   C.  Select the Agent update workflow.

   If it occurs that one of the upgrade jobs fail, that agent becomes
   deactivated.  When you activate these agents again, PureDisk schedules a
   new upgrade job.  If the client is connected to the network, PureDisk
   schedules the job within 15 minutes.  To determine which agents are
   deactivated, take the following actions:

   A.  Invoke the Web UI.
   B.  Click the Data management tab.
   C.  Select the Deactivated client agents by storage pool view, which is
       the third view from the left.
   D.  Re-activate the deactivated Windows agents; a new update Job will
       be created if they are not yet on version

Terms of use for this information are found in Legal Notices.



Did this article answer your question or resolve your issue?


Did this article save you the trouble of contacting technical support?


How can we make this article more helpful?

Email Address (Optional)