Engineering Hotfix Bundle NB_PDE_6.6.1.2_EEB04-rollup1 provides fixes to Symantec NetBackup (tm) PureDisk 6.6.1.2.

Article:TECH156445  |  Created: 2011-03-24  |  Updated: 2011-03-24  |  Article URL http://www.symantec.com/docs/TECH156445
Article Type
Technical Solution

Product(s)

Issue



Engineering Hotfix Bundle NB_PDE_6.6.1.2_EEB04-rollup1 provides fixes to Symantec NetBackup (tm) PureDisk 6.6.1.2.


Solution



 

Name: NB_PDE_6.6.1.2_EEB04-rollup1

Date: March 15, 2011

 

==============================================================================

This Engineering Binary provides features and fixes to the Veritas NetBackup

PureDisk Remote Office Edition 6.6 software.

 

WARNING: When you apply this Engineering Binary, all PureDisk services stop

         and start.  This can cause running jobs to abort.

==============================================================================

 

=================

PACK DEPENDENCIES

=================

 

Install PureDisk 6.6.1.2 before you install this Engineering Binary.

 

 

=============

PRODUCT FIXES

=============

 

This Engineering Binary contains the PureDisk Health Checker v1.02 under /opt/pdconfigure/scripts/support/

 

This Engineering Binary contain fixes  for the following issues:

 

General fixes:

--------------

ET2240413 - MBE-CLI_MBGarbageCollection fail/error 'Query failed: ERROR: relation "tmp_expired_history_ds_* ...does not exist'

Metabase Garbage Collection jobs, with 'Log deleted records' enabled, fail with:

[2]pg_query(): Query failed: ERROR:  relation "tmp_expired_history_ds_20" does not exist

 

This change in behavior no longer uses intermediate table in Metabase database,

but logs deleted records directly to output files under /Storage/log/gc/.

 

ET2252992 - Datamining workflow hangs/fails, "JobStep has failed because it was not running on the agent"

Metabase data mining job fail with error message:

End JobStep: Failed to parse logfile. Reported error was: Failed to open input file: /Storage/tmp/workflow.9746

This JobStep has failed because it was not running on the agent while it should have been running according to the workflow engine.

 

ET2187410 - Stability improvements to 'pdbackup' for AIX client agents

 

ET2262000 - Sync of topology failed: [2]fopen(/Component.lck): failed to open stream

    After installation of PureDisk 6.6.1.1, the following alerts show every hour:

     Sync of topology failed: ***ERROR***nr: 999999severity: 6server:source:

        Application_Component Application not yet initialized; latest captured error:

        [2]fopen(/Component.lck): failed to open stream: Permission denied

 

ET2262831 - Always allow to start rerouting of storage pool in the PureDisk GUI

 

ET2262865 - Rerouting fails because job fails to connect to CR to retrieve progress info

    If the rerouting process is in the "WaitCRDelete" or the "ReRoutingMonitorCR"

    step, then it is contacting the CR every 3 or 5 seconds to check for the

    progress of this step. Every time these steps contact the CR there is also an

    authentication check. At enviroment with many CRs (up to 7 CRs) and if the

    Storage Pool is under load during rerouting, the progress check in

    "WaitCRDelete" or "ReRoutingMonitorCR" can fail with an authorisation error.

 

    This makes the entire rerouting job to fail. The entire rerouting job needs

    to be restarted. Sometimes multiple times.

 

    Fix:

    Change the check interval from 3 and 5 seconds, to 5 minutes.

 

ET2273819 - PureDisk replication job gives incorrect message about PDDO replication

A PureDisk replication job on a non-PDDO data selection shows this incorrect

warning message:

This is a PDDO scheduled replication, not forwarding

NBU tag files (NBU_PD_MARKER) and (NBU_PD_SERVER) in the top level directory.

 

ET2270169 - MonitorStatistics is run immediately on startup of PureDisk services by pdagent.

This can result in erroneous Critical Alert if other services are slow to startup.

Change is to not execute MonitorStatistics on the agent in the first 10 minutes after

startup

Change is to not execute MonitorStatistics on the agent in the first 10 minutes after

startup..

 

ET2273819 - PureDisk replication job gives incorrect message about PDDO replication

When running replication jobs of a 'Files and Folder; dataselection on PureDisk,

the following message is seen:

This is a PDDO scheduled replication, not forwarding NBU tag files (NBU_PD_MARKER) 

and (NBU_PD_SERVER) in the top level directory.

 

ET2271180 - Unable to create UNC data selection in PureDisk UI.

When expanding the domainname during UNC data selection creation, the following error is

shown: "Unable to execute dirlist on agent <agentname>(id) for path: /<domainname>"

 

ET2269894 - Unable to browse files with commas in the name.

 

ET2253079 - Database connection leak in PD 6.6.1 Authorization daemon.

 

PureDisk GUI fixes:

-------------------

ET2109691 - Error when viewing the alerts page in GUI

Fixed the following error occuring when attempting to view alerts page:

nested exception is: org.xml.sax.SAXParseException: An invalid XML character

(Unicode: 0xe) was found in the element content of the document.:Unable to view

all critical alerts

 

ET2227180 - Using "storage pool configuration wizard" to add a service to PD needs a warning if it is going to re-install PD.

Improvement to the PureDisk Installer interface, to prevent accidently storage pool re-installation and data loss:

1.Add "Confirm" message box on the last page of wizard when it is a re-installation.

2.A summary on last page of wizard about which action is going to be taken (But only shows summary when it is re-installation)

3.Fix incorrect warning message at "Broker configuration" page.

 

ET2043474 - Restored folder gets named with wrong symbols if it contains special characters in the folder name

A PureDisk restore to a folder with "special characters" will create a new restore destination folder with incorrect symbols.

 

ET2221041 - Not able to choose dataselection in data removal policy

PureDisk GUI improvement to display replicated clients and data selections in the data removal policy

 

PDDO Fixes:

-----------

ET2178573 - Optimized duplication failing between PDDO to PDDO storage units using AIX PDDO plug-in

    Log example for failed duplication jobs using AIX PDDO plug-in:

        Critical bpdm (pid=409846) sts_copy_extent failed: error 2060013 no more entries

        Critical bpdm (pid=409846) image copy failed: error 2060013: no more entries

        Error bpdm (pid=409846) cannot copy image from disk,bytesCopied = 18446744073709551615

        Critical bpdm (pid=409846) sts_close_handle failed:2060022 software error

 

ET2209928 - PDDO backup to 6.6.1 fails w/setup_pdvfs_image_cache error Bad file descriptor

    Backups to PDDO fail with status 83 and this error in the bptm log:

    setup_pdvfs_image_cache error (-1 9 Bad file descriptor) PDVFS_IOCTL_ADD_DO_FP_CACHE

 

ET2215029 - Backups to dedupe STU failing with status 84 when attempting to write first fragment header.

 

ET2280249 - Rerouting hangs with the data backed up from NetBackup 7.0.1

When backing up from NBU 7.0.1 to a PureDisk storage pool, rerouting cannot proceed to the end, the data 

transfer is always in progress. The newly added CR node is filled with data. 

 

ET2272289 - PDDO Restores during Re-Routing are failing with "Could not send get operations for DOs: zero-sized object"

Example of log:

PDVFS: [1] pdvfs_lib_log: Could not send get operations for DOs: zero-sized object

PDVFS: [1] pdvfs_lib_log: Could not send all DO get operations via recommended route table: zero-sized object

PDVFS: [1] pdvfs_pread: CRDOReaderRead for myclient_1295398433_C1_F5.map failed: 47 (zero-sized object)

verify_mapfile_version error reading mapfile version (5 Input/output error)

 

ET2251112 - VmWare VCB Flashbackup (Type 3 Virtual machine) backups to PDDO storage unit fail with status 84.

 

ET2244429 - Content Router hangs due to deadlock caused by parallel Disaster Recovery backup and restore or duplication job on 

NetBackup side. Batch prefetching is disabled by fix this (PREFETCH_SIZE=0) to prevent hang.

 

IMPORTANT: A 'client agent update' job will NOT be created for PDDO agents. Please

follow the procedure 'Upgrading PDDO client agents on Media Servers'.

 

 

Content Router Queue Processing:

--------------------------------

ET2246881 - Detailed progress logging on a more regular time interval during CR queue processing

Logging for Content Router queue processing steps (sorting, tlog processing, delayed file processing,

creating database index, ...) is more verbose and more frequently logged, so a distinction can be made

between a hanging and a slow queue processing job.

 

ET2253050 - ET2215448 - ET2222209 - ET2222453 - ET2248352: CR queue processing improvements for stability and supportability.

 

These improvements are made to provide more stability and easier troubleshooting for CR queue processing:

1. Read the tlog file again right after it was closed.

2. Create copy of the tlog file in processed directory (/Storage/processed) at the start of queue processing.

3. Delete the tlog copy after queue processing completes successfully.

 

The Content Router process will also shut down after five consecutive failures during queue processing.

This behavior prevents the queue from grower any further and forces the customer to take action before continuing,

 

ET2312853 - Queue processing fails to create new .tlog in queue directory.

Queue processing error:  Could not move spool log /Storage/spool/8748.tlog to /Storage/spoold/8748.tlog (The file exists.)

 

 

=====================

DOWNLOAD INSTRUCTIONS

=====================

 

1.  Use rcp or scp to copy the tar file, NB_PDE_6.6.1.2_EEB04-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.6.1.2_EEB04-rollup1.tar

 

    This command computes the md5 checksum of the Engineering Binary.

    It should match the one mentioned by support or on the support website.

 

    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.6.1.2_EEB04-rollup1.tar ./NB_PDE_6.6.1.2_EEB04-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.6.1.2_EEB04-rollup1.tar ./opt

 

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

 

        /opt/pdinstall/apply-NB_PDE_6.6.1.2_EEB04-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

    resource group before you unfreeze the cluster.

 

7.  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 one of the upgrade jobs fails, PureDisk deactivates those client agents.

    You will need to activate these agents again and to select the client to

    upgrade to. Follow the steps below:

 

    A.  Invoke the Web UI.

    B.  Click the Data management tab.

    C.  In the middle pane, select the 'Deactivated client agents by storage pool' view,

        which is the third view from the left.

    D.  Select the 'storage pool' level in the middle pane

        and choose 'Activate Agents' from the left hand pane.

    E.  Refresh the middle pane.

        It will switch back to the default view with all clients.

    F.  Select the 'storage pool' level in the middle pane

        and choose 'Upgrade Agents' from the left hand pane.

        Choose the version you want to upgrade to.

 

    Monitor these upgrade jobs again, start over if they fail or time-out.

 

8.  (Conditional)  Upgrade the PDDO agent software on PDDO media server

    clients.

 

    Perform the procedure called "UPGRADING PDDO AGENTS ON MEDIA SERVER

    CLIENTS", which follows.  The release update includes upgraded

    PDDO agents for Linux, Solaris, and Windows clients. 

 

======================================

UPGRADING PDDO AGENTS ON MEDIA SERVERS

======================================

 

1.  Make sure that the storage pool software for the PDDO clients has been

    upgraded.

 

2.  Refresh the PureDisk landing page.

 

    The landing page can be found on:

    

        https://<your-puredisk-spa>/

        

    For <your-puredisk-spa>, type the hostname or the IP address of your

    PureDisk Storaga Pool Authority.

 

    Be aware that this release update includes both the PureDisk 6.6

    base release agents and revised agents for Linux, Solaris, and Windows

    clients.  The revised agents include updates for PDDO agent installation

    only.  A later step in this procedure instructs you to download the

    revised agents if you want to upgrade the PDDO agent on a client.

 

3.  Log in to each PDDO client.

 

4.  From the PDDO media server client, download the new PDDO agent software.

 

    The landing page includes more than one software version of the PDDO

    agent, so take care to download the most recent agent.  

 

5.  Stop all NetBackup services on the NetBackup media server. 

 

6.  Install the agent software included with this release update.

    

    * On Windows systems, double-click the PureDisk agent icon.  This starts

      the Windows installation Wizard.

 

    * On Linux or Solaris systems, you can use either the attended or the

      unattended installation method.  The installer prompts you to confirm

      the upgrade.  For example, type the following command to upgrade the

      Solaris 10 agent:

 

      # sh pdagent-Solaris_10_sparc-6.6.0.NNNNN.run

 

      For NNNNN, type the name of the PureDisk upgrade release number.

 

    NOTE:  The upgrade software removes the old PDDO agent software

    automatically.

 

    For more information about how to install the PDDO agent, see the Veritas

    NetBackup PureDisk Deduplication Option Guide.

 

7.  Start all the NetBackup services on the NetBackup media server. 

 

 


Attachments

NB_PDE_6.6.1.2_EEB04-rollup1
NB_PDE_6.6.1.2_EEB04-rollup1.tar (161.5 MBytes)

Supplemental Materials

SourceETrack
Value2253079


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


Terms of use for this information are found in Legal Notices