Release Update NB_VBR_6.6.2_Windows.zip provides fixes and enhancements to Symantec Veritas Backup Reporter (tm) version 6.6 for Windows.

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


Environment

Issue



Release Update NB_VBR_6.6.2_Windows.zip provides fixes and enhancements to Symantec Veritas Backup Reporter (tm) version 6.6 for Windows.

Solution



Name: NB_VBR_6.6.2.README
Date: January 8, 2010

================================================================================
This Release Update provides updates and fixes to Veritas Backup Reporter (VBR) 6.6 software.
================================================================================

===========================
PREREQUISITES
===========================

Backup Reporter 6.6GA must be installed prior to deploying this Release Update

==========================
I. DOWNLOAD INSTRUCTIONS
==========================

1) Download the file NB_VBR_6.6.2_Windows_340223.zip into a temporary directory,
                     
2) Extract the NB_VBR_6.6.2_Windows_340223.zip file.
           
       Along with other files, this will create the following files:
       vbr-mp.exe

=============================
II. INSTALLATION INSTRUCTIONS
=============================

Before installing VBR, review the following items:

  -  You must install this VBR Release Update on VBR 6.6 release. Upgrade to VBR 6.6 if you are on an earlier version.
     Consult the VBR 6.6 documentation for the procedure.      
     
     Note: If upgrade to VBR 6.6 from a previous version has failed, then you must restore the backed up copy of the VBR database
     before upgrading to this Release Update.
     See Veritas Backup Reporter Administrator's Guide for instructions on restoring the database.
     However if your upgrade to VBR 6.6 has failed and you have applied the engineering fixes to fix the issues, you can install
     this Release Update without restoring the database.  

 -   When upgrading an existing installation, the VBR Management Server must be upgraded before the Agents or View Builder can be upgraded.
     Close the VBR Console before starting the server upgrade process.

  -  In case, the VBR components like VBR management server, VBR agents, and View Builder are installed on different machines,
     this Release Update must be installed on each of the machines separately.        

 -  You must have Administrator rights to install this Release Update.
 
 
To install the Release Update on Windows:
-----------------------------------------------------------------
CAUTION: If applying the Release Update to the Server, both the Server and the Agent (if installed) will be stopped during
          the update.

CAUTION: If applying the Release Update to the Agent, it will be stopped during the update.
 

CAUTION: There is no way to reverse updates to the database once
made. A database backup is recommended.
 

NOTE: Any files being updated will be backed up into a zip file
in the component's installation directory. The file name
will include the time of the update.
 

NOTE: There will be a prompt before any action is taken.
 

NOTE: If a component is not detected correctly, its directory
can be manually entered into locations.conf. See that
file for details.

 1. Run vbr-mp.exe.

 2. Follow the prompts, and choose 'y' when prompted to update
    each component.


=========================
III. UNINSTALL INSTRUCTIONS
=========================
Note: This will ONLY uninstall the Release Update from your local machine.

To uninstall the Release Update on Windows:
------------------------------------------------------------------
CAUTION: Once the database has been updated, the server maintenance pack should not be uninstalled. If a database backup was
made, stop the server and restore it before
uninstalling the Release Update.
 
 

NOTE: The server should be stopped before uninstalling.

 

NOTE: The agent should be stopped before uninstalling.

 

1. Stop the main service for any component being uninstalled.

 

2. Replace files in the installation directory with those
backed up in the zip file.
 

To install the Release Update on VCS clustered Agent
-------------------------------------------------------------

1. Freeze the VCS service group, which has the VBR Agent configured as a VCS Resource (Please refer to VCS documentation on how to freeze a service group)

2. Stop the VBR Agent process

4. Rename the following set of binaries in the agent lib directory
C:\Program Files\Symantec\Veritas Backup Reporter\Agent\lib (Change to appropriate location, if VBR is not installed in the default path)

a. ccsvc-AgentCore.jar
b. ccsvc-AgentModuleNetbackup.jar
c. ccsvc-AgentModulePureDisk.jar
d. ccsvc-AgentModuleTSM.jar
e. ccsvc-AgentShared.jar
f. ccsvc-ics.jar
g. ccsvc-info.jar
h. ccsvc-AgentModuleEnterpriseVault.jar

5. Copy the files from the extracted location (NB_VBR_6.6.2_Windows/reporting/agent/lib), to the above location

6. Rename the following set of files in the agent conf directory
C:\Program Files\Symantec\Veritas Backup Reporter\Agent\conf (Change to appropriate location, if VBR is not installed in the default path)

a.tsm-agent.conf

7. Copy the files from the extracted location (NB_VBR_6.6.2_sol/reporting/agent/conf), to the above location

8. Start the VBR Agent process

9. Un-Freeze the VCS service group, which has the VBR Agent configured as a VCS Resource (Please refer to VCS documentation on how to freeze a service group)


===========================
IV. Release Update CONTENT
===========================
This section contains the Release Update conventions, content, and historical
content that is applicable to the release.

Conventions:
------------
The following list describes the conventions used in the subsections that
following this section.  Each item listed in the Current Release Update
subsection describes a feature, enhancement, or issue fixed with this
Release Update.

For more information about the defects listed in this Release Update, please visit the Backup Reporter 6.6 Late Breaking News Bulletin at
http://entsupport.symantec.com/docs/324968

Description
    Describes a particular problem contained in this pack.

** Description **  
    Describes a problem that can lead to potential data loss. Please
    read these problem descriptions carefully.

Workaround
    Any available workarounds to a problem are also listed. Workarounds can be
    used INSTEAD of applying the patch, however, Symantec strongly recommends
    the "best practice" of being at the latest available patch level.

Additional Notes
    Any additional information regarding a problem is included.



Qualifications
----------------------

Symantec NetBackup 6.5.5
Symantec PureDisk 6.6


New Features
----------------------

Reporting on MS-SQL Database Instance Names
Purging of Break Up Jobs data
Auto classifying of Backup Clients as "In Active" if removed from NBU Policy



Current Release Update
----------------------

INCIDENT ABSTRACT
1782555 Client Risk Analysis Report throws exception while trying to save.
1853361 VBR not able to collect data from PureDisk 6.6
1891247 Job and policy data not collected for some policy types.
1879092 CorbaServer fails loading TDU data from NetWorker module into the VBR DB with error A217: S0: Data rejected by server: -100
1483302 Spooler Files have .lderr extension and they are not being processed by the VBR Agent
1724167 Date/time stamps stored in the DB for TSM modules is inaccurate
1744117 Image data is not purged
1748737 Spool files containing catarc backups are very slow to load. A file system object is created for each image path.
1785745 Saved reports throw an exception after upgrading to VBR 6.6 - An error has occurred - Undefined error
1834613 File count for a job in VBR report appears to be lower than the value noted in NBU Job/Image details.
1854758 Agent spoolers are hanging or very slow after running for one to three weeks.
1872341 Agent spooler hangs, agent must be restarted
1879425 Reports running significantly slower following upgrade from 6.5 to 6.6
1893889 Keyword phrase for user backup at submission time does not appear to be captured and cannot be selected for reports
1893911 After upgrade from 6.5.1.1 to 6.6, jobs are in random order for backup explorer.
1917967 Policy keyword phrase is not updated in the jobs table for scheduled/manual bkp jobs and cannot be selected for reports
1639747 Object merger for two master server fails with "ASA Error -186: Subquery cannot return more than one row"
1795674 TDP Oracle data is not being reported by VBR
1879434 Optimize data collection from TSM
1915605 Media data collection fails when media holds data more than 2TB
1898672 Job and media data collection fails while collecting data from NBU 6.5.5
1836824 Filtering of Saved Reports via Bkup image exp time relative not functioning properly.
1836837 Scheduled e-mail tabular reports only contain first page since upgrading from 6.5.1.1 to 6.6.
1913724 Request for EEB to fix regression to ET1450224 for on-demand running of tasks
1914897 In various ways, the Consecutive Failures report does not save the criteria selected.
1869843 Purge FS objects based on timestamp
1785423 Merging/aliasing hosts does not help object lookups during data load
1794407 View based reports not working after upgrade.
1794988 Emailed Reports ignore the met "Conditions".
1802192 "By Retention Level" incorrectly groups Unassigned Media in with Infinite Retention level.
1805896 Dbbackup.bat fails on 64-bit Windows host.
1837454 A217: S0: Data rejected by server
1837459 NullPointer Exception while parsing Image data
1837439 Object Merger fails with NullPointer Excdeption
1837442 Copying File System objects across tree nodes in View Builder generates Corba ServerException
1837447 Place Unassigned File Systems option in View Builder does not complete.
1837456 Client count is not correct for VBR with PD server reporting
1837457 Reports based on Views do not contain data.
1837452 Place Unassigned File Systems option in View Builder does not complete.
1837455 Data collection and data transmit errors A2030 and A203
1840744 Job Size and Count reports shows in-correct data, because of duplicate job been collected by VBR.
1837443 ViewBuilder errors when running Place Unassigned File Systems
1837450 Data collection and data transmit errors A2030 and A203
1837449 A217: S0: Data rejected by server
1837460 Reports not been emailed.
1837446 Place Unassigned File Systems option in View Builder does not complete.
1842952 Unable to see Alerts, Alert Policies or Alert Receipients after changedbpassword --setServerPassword.
1863567 Add support for detection of decommissioned clients
1871437 Filtering out more than ONE error code does not work properly in Consecutive Failure Report
1872347 Qualification of NBU 6.5.5
1877903 Restore job data collection fails
1877019 Consecutive Failures report shows 0's and 1's.
1880808 Too many references to Schedule names when creating custom reports
1880627 Add reference to directory server in Archive* tables
1890974 Job collection completes, but failures reported in web GUI with status code A217.
1911637 xml.bat for attribute assignment fails, Object o3 Error : Field does not exist.
1911630 Stored Backup Images - Historical consumes 100% CPU for over an hour, then fails to deliver the report.
1921171 Variance Report fails, because of divide by zero condition
1921170 Vaulted (duplicate) copy information is incorrect since upgrading from 6.5.1.1 to 6.6.
1880208 Reports showing "MS-SQL-Server Backups" for directory column instead of SQL databases actually backed up.
1911691 Data returned by bperror is bloating job spool files resulting in A219 errors.
1914582 Consecutive Failures Report is 2 days behind

Attachments

NB_VBR_6.6.2_Windows_340223.zip (54.3 MBytes)

Legacy ID



340223


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


Terms of use for this information are found in Legal Notices