Veritas Backup Reporter 6.5 Installation Guide Veritas Backup Reporter Installation Guide
The software described in this book is furnished under a license agreement and may be used only in accordance with the terms of the agreement. Documentation version 6.5 PN: : (HRO7210)SKU 11132088 Legal Notice Copyright © 2008 Symantec Corporation. All rights reserved. Federal acquisitions: Commercial Software - Government Users Subject to Standard License Terms and Conditions. Actionable Infrastructure™, Active Extensions™, ActiveAdmin™, Anti-Freeze™, Application Saver™, Backup Exec™, Bare Metal Restore™, BindView™, Bloodhound™, Bootguard™, Brightmail™, bv-Admin™, bv-Control™, CarrierScan™, CleanSweep™, ColorScale™, CommandCentral™, Confidence Online™, CrashGuard™, Day-End Sync™, dbAnywhere™, DeepSight™, Defender™, Digital Immune System™, DiskDoubler™, DiskLock™, Drive Image™, Enterprise Security Manager™, Enterprise Vault™, FlashSnap™, FlowChaser™, Ghost Walker™, Ghost™, GoBack™, Healthy PC™, i3™, iCommand™, I-Gear™, Indepth™, Information Integrity™, Intellicrypt™, Intruder Alert™, LiveUpdate™, LiveState™, Mail-Gear™, ManHunt™, ManTrap™, MicroMeasure™, Mobile Update™, NetBackup™, NetProwler™, NetRecon™, Norton™, Norton 360™, Norton AntiSpam™, Norton AntiVirus™, Norton Commander™, Norton Editor™, Norton Guides™, Norton Internet Security™, Norton Mobile Essentials™, Norton Password Security™, Norton SystemWorks™, Norton Utilities™, Norton WinDoctor™, OmniGuard™, OpForce™, PartitionMagic™, pcAnywhere™, PowerQuest™, PowerVPN™, Procomm™, Procomm Plus™, PureDisk™, QuickLog™, Raptor™, Recourse Technologies™, RELICORE™, Replication Exec™, SafetySweep™, SANPoint™, SANPoint Control™, SecureExchange™, SecureLink™, ServerMagic™, SESA™, SiteStor™, SmartSector™, SmarTune™, Speed Disk™, SpeedSend™, Storage Exec™, StorageCentral™, Sygate™, Symantec™, Symantec AntiVirus Research Center (SARC)™, Symantec AntiVirus™, Symantec DeployCenter™ Library, Symantec Enterprise Security Architecture™, Symantec Inform™, Symantec Insight™, Symantec Intruder Alert™, Symantec Logo, Symantec Mail-Gear™, Symantec Mobile Essentials™, Symantec ON Command Discovery™, Symantec ON iCommand™, Symantec ON iPatch™, TalkWorks™, TruStor™, UnErase™, UpScale™, V2i™, V2i Builder™, V2i Protector™, V2i Observer™, VelociRaptor™, Veritas™, Veritas Data Center Foundation™, Veritas Server Foundation™, Veritas Storage Foundation™, Vision360™, Virtually Anywhere™, WebDefender™, WinFax™, WipeDisk™, WipeFile™, Work Virtually Anywhere™ Windows is a trademark of Microsoft Corporation. Additional company and product names may be trademarks or registered trademarks of the individual companies and are respectfully acknowledged. The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Symantec Corporation and its licensors, if any. THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE. The Licensed Software and Documentation are deemed to be "commercial computer software" and "commercial computer software documentation" as defined in FAR Sections 12.212 and DFARS Section 227.7202. Symantec Corporation 20330 Stevens Creek Blvd. Cupertino, CA 95014 USA http://www.symantec.com Acknowledgments examples: This product includes software developed by the Apache Software Foundation (http://www.apache.org/), namely Tomcat Servlet Container, Jakarta Commons, Sprint Framework, Active MQ, Ehcache, Xerces XML Parser, Piccolo XML Parser, Log4J and Apache XML-RPC. A copy of Apache Software License 1.1 and 2.0 can be found at www.apache.org/licenses/. The Piccolo XML Parser library is copyright Yuval Oren. Technical Support
Symantec Technical Support maintains support centers globally. Technical Support’s primary role is to respond to specific queries about product feature and function, installation, and configuration. The Technical Support group also authors content for our online Knowledge Base. The Technical Support group works collaboratively with the other functional areas within Symantec to answer your questions in a timely fashion. For example, the Technical Support group works with Product Engineering and Symantec Security Response to provide alerting services and virus definition updates. Symantec’s maintenance offerings include the following:
■ A range of support options that give you the flexibility to select the right amount of service for any size organization
■ A telephone and web-based support that provides rapid response and up-to-the-minute information
■ Upgrade insurance that delivers automatic software upgrade protection
■ Global support that is available 24 hours a day, 7 days a week worldwide. Support is provided in a variety of languages for those customers that are enrolled in the Platinum Support program
■ Advanced features, including Technical Account Management For information about Symantec’s Maintenance Programs, you can visit our Web site at the following URL: www.symantec.com/techsupp/ent/enterprise.html Select your country or language under Global Support. The specific features that are available may vary based on the level of maintenance that was purchased and the specific product that you are using. Contacting Technical Support Customers with a current maintenance agreement may access Technical Support information at the following URL: www.symantec.com/techsupp/ent/enterprise.html Select your region or language under Global Support. Before contacting Technical Support, make sure you have satisfied the system requirements that are listed in your product documentation. Also, you should be at the computer on which the problem occurred, in case it is necessary to recreate the problem. When you contact Technical Support, please have the following information available:
■ Product release level
■ Hardware information
■ Available memory, disk space, and NIC information
■ Version and patch level
■ Network topology
■ Router, gateway, and IP address information
■ Problem description:
■ Error messages and log files
■ Troubleshooting that was performed before contacting Symantec
■ Recent software configuration changes and network changes
Licensing and registration If your Symantec product requires registration or a license key, access our technical support Web page at the following URL: www.symantec.com/techsupp/ent/enterprise.html Select your region or language under Global Support, and then select the Licensing and Registration page. Customer service Customer service information is available at the following URL: www.symantec.com/techsupp/ent/enterprise.html Select your country or language under Global Support. Customer Service is available to assist with the following types of issues:
■ Questions regarding product licensing or serialization
■ Product registration updates such as address or name changes
■ General product information (features, language availability, local dealers)
■ Latest information about product updates and upgrades
■ Information about upgrade insurance and maintenance contracts
■ Information about the Symantec Value License Program ■ Advice about Symantec's technical support options
■ Nontechnical presales questions
■ Issues that are related to CD-ROMs or manuals Maintenance agreement resources If you want to contact Symantec regarding an existing maintenance agreement, please contact the maintenance agreement administration team for your region as follows:
■ Asia-Pacific and Japan: [email protected]
■ Europe, Middle-East, and Africa: [email protected]
■ North America and Latin America: [email protected] Additional Enterprise services Symantec offers a comprehensive set of services that allow you to maximize your investment in Symantec products and to develop your knowledge, expertise, and global insight, which enable you to manage your business risks proactively. Enterprise services that are available include the following:
Symantec Early Warning Solutions These solutions provide early warning of cyber attacks, comprehensive threat analysis, and countermeasures to prevent attacks before they occur.
Managed Security Services These services remove the burden of managing and monitoring security devices and events, ensuring rapid response to real threats.
Consulting Services Symantec Consulting Services provide on-site technical expertise from Symantec and its trusted partners. Symantec Consulting Services offer a variety of prepackaged and customizable options that include assessment, design, implementation, monitoring and management capabilities, each focused on establishing and maintaining the integrity and availability of your IT resources.
Educational Services Educational Services provide a full array of technical training, security education, security certification, and awareness communication programs. To access more information about Enterprise services, please visit our Web site at the following URL: www.symantec.com Select your country or language from the site index. Veritas Backup Reporter 6.5 Symantec Software License Agreement
rights to the Licensed Software: a Symantec license SYMANTEC CORPORATION AND/OR ITS AFFILIATES certificate or a similar license document issued by (“SYMANTEC”) IS WILLING TO LICENSE THE LICENSED Symantec, or a written agreement between You and SOFTWARE TO YOU AS THE INDIVIDUAL, THE Symantec, that accompanies, precedes or follows this COMPANY, OR THE LEGAL ENTITY THAT WILL BE License Agreement. UTILIZING THE LICENSED SOFTWARE (REFERENCED BELOW AS “YOU” OR “YOUR”) ONLY ON THE “Licensed Software” means the Symantec software CONDITION THAT YOU ACCEPT ALL OF THE TERMS product, in object code form, accompanying this License OF THIS LICENSE AGREEMENT (“LICENSE Agreement, including any Documentation included in, AGREEMENT”). READ THE TERMS AND CONDITIONS or provided for use with, such software or that OF THIS LICENSE AGREEMENT CAREFULLY BEFORE accompanies this License Agreement. USING THE LICENSED SOFTWARE. THIS IS A LEGAL AND ENFORCEABLE CONTRACT BETWEEN YOU AND “Support Certificate” means the certificate sent by SYMANTEC. BY OPENING THE LICENSED SOFTWARE Symantec confirming Your purchase of the applicable PACKAGE, BREAKING THE LICENSED SOFTWARE SEAL, Symantec maintenance/support for the Licensed CLICKING THE “I AGREE” OR “YES” BUTTON, OR Software. OTHERWISE INDICATING ASSENT ELECTRONICALLY, “Upgrade” means any version of the Licensed Software OR LOADING THE LICENSED SOFTWARE OR that has been released to the public and which replaces OTHERWISE USING THE LICENSED SOFTWARE, YOU the prior version of the Licensed Software on Symantec’s AGREE TO THE TERMS AND CONDITIONS OF THIS price list pursuant to Symantec’s then-current upgrade LICENSE AGREEMENT. IF YOU DO NOT AGREE TO policies. THESE TERMS AND CONDITIONS, CLICK THE “I DO NOT AGREE” OR “NO” BUTTON OR OTHERWISE “Use Level” means the license use meter or model (which INDICATE REFUSAL AND MAKE NO FURTHER USE OF may include operating system, hardware system, THE LICENSED SOFTWARE. UNLESS OTHERWISE application or machine tier limitations, if applicable) by DEFINED HEREIN, CAPITALIZED TERMS WILL HAVE which Symantec measures, prices and licenses the right THE MEANING GIVEN IN THE “DEFINITIONS” SECTION to use the Licensed Software, in effect at the time an OF THIS LICENSE AGREEMENT AND SUCH order is placed for such Licensed Software, as indicated CAPITALIZED TERMS MAY BE USED IN THE SINGULAR in this License Agreement and the applicable License OR IN THE PLURAL, AS THE CONTEXT REQUIRES. Instrument. Should You have any questions regarding this 2. License Grant: Agreement, or wish to contact Licensor, You may write to Symantec Corporation, Attention: : Legal Department, Subject to Your compliance with the terms and 20330 Stevens Creek Blvd, CC1, 1st Floor Cupertino, CA conditions of this License Agreement, Symantec grants 95014. to You the following rights: (i) a non-exclusive, non-transferable (except as stated otherwise in Section 1. Definitions: 16.1) license to use the Licensed Software solely in support of Your internal business operations in the “Content Updates” means content used by certain quantities and at the Use Levels described in this License Symantec products which is updated from time to time, Agreement and the applicable License Instrument; and including but not limited to: updated anti-spyware (ii) the right to make a single uninstalled copy of the definitions for anti-spyware products; updated antispam Licensed Software for archival purposes which You may rules for antispam products; updated virus definitions use and install for disaster-recovery purposes (i.e. where for antivirus and crimeware products; updated URL lists the primary installation of the Licensed Software for content filtering and antiphishing products; updated becomes unavailable for use). firewall rules for firewall products; updated intrusion detection data for intrusion detection products; updated 2.1 Term lists of authenticated web pages for website The term of the Licensed Software license granted under authentication products; updated policy compliance this License Agreement shall be perpetual (subject to rules for policy compliance products; and updated Section 14) unless stated otherwise in Section 17 or vulnerability signatures for vulnerability assessment unless You have obtained the Licensed Software on a products. non-perpetual basis, such as, under a subscription or “Documentation” means the user documentation term-based license for the period of time indicated on Symantec provides with the Licensed Software. the applicable License Instrument. If You have obtained the Licensed Software on a non-perpetual basis, Your “License Instrument” means one or more of the following rights to use such Licensed Software shall end on the applicable documents which further defines Your license applicable end date as indicated on the applicable License Instrument and You shall cease use of the Licensed applicable License Instrument. An upgrade to an existing Software as of such applicable end date. license shall not be deemed to increase the number of licenses which You are authorized to use. Additionally, 3. License Restrictions: if You upgrade a Licensed Software license, or purchase a Licensed Software license listed on the applicable You may not, without Symantec’s prior written consent, License Instrument to cross-grade an existing license conduct, cause or permit the: (i) use, copying, (i.e. to increase its functionality, and/or transfer it to a modification, rental, lease, sublease, sublicense, or new operating system, hardware tier or licensing meter), transfer of the Licensed Software except as expressly then Symantec issues the applicable Licensed Instrument provided in this License Agreement; (ii) creation of any based on the understanding that You agree to cease using derivative works based on the Licensed Software; (iii) the original license. Any such license upgrade or reverse engineering, disassembly, or decompiling of the cross-grade is provided under Symantec's policies in Licensed Software (except that You may decompile the effect at the time of order. This License Agreement does Licensed Software for the purposes of interoperability not separately license You for additional licenses beyond only to the extent permitted by and subject to strict those which You have purchased, and which have been compliance under applicable law); (iv) use of the Licensed authorized by Symantec as indicated on the applicable Software in connection with service bureau, facility License Instrument. management, timeshare, service provider or like activity whereby You operate or use the Licensed Software for 7. Limited Warranty: the benefit of a third party; (v) use of the Licensed Software by any party other than You; (vi) use of a later 7.1 Media Warranty: version of the Licensed Software other than the version that accompanies this License Agreement unless You If Symantec provides the Licensed Software to You on have separately acquired the right to use such later tangible media, Symantec warrants that the magnetic version through a License Instrument or Support media upon which the Licensed Software is recorded will Certificate; nor (vii) use of the Licensed Software above not be defective under normal use, for a period of ninety the quantity and Use Level that have been licensed to (90) days from delivery. Symantec will replace any You under this License Agreement or the applicable defective media returned to Symantec within the License Instrument. warranty period at no charge to You. The above warranty is inapplicable in the event the Licensed Software media becomes defective due to unauthorized use of the 4. Ownership/Title: Licensed Software. THE FOREGOING IS YOUR SOLE AND EXCLUSIVE REMEDY FOR SYMANTEC’S BREACH The Licensed Software is the proprietary property of OF THIS WARRANTY. Symantec or its licensors and is protected by copyright law. Symantec and its licensors retain any and all rights, 7.2 Performance Warranty: title and interest in and to the Licensed Software, including in all copies, improvements, enhancements, Symantec warrants that the Licensed Software, as modifications and derivative works of the Licensed delivered by Symantec and when used in accordance Software. Your rights to use the Licensed Software shall with the Documentation, will substantially conform to be limited to those expressly granted in this License the Documentation for a period of ninety (90) days from Agreement. All rights not expressly granted to You are delivery. If the Licensed Software does not comply with retained by Symantec and/or its licensors. this warranty and such non-compliance is reported by You to Symantec within the ninety (90) day warranty period, Symantec will do one of the following, selected 5. Content Updates: at Symantec’s reasonable discretion: either (i) repair the If You purchase a Symantec maintenance/support Licensed Software, (ii) replace the Licensed Software offering consisting of or including Content Updates, as with software of substantially the same functionality, indicated on Your Support Certificate, You are granted or (iii) terminate this License Agreement and refund the the right to use, as part of the Licensed Software, such relevant license fees paid for such non-compliant Content Updates as and when they are made generally Licensed Software. The above warranty specifically available to Symantec’s end user customers who have excludes defects resulting from accident, abuse, purchased such maintenance/support offering and for unauthorized repair, modifications or enhancements, such period of time as indicated on the face of the or misapplication. THE FOREGOING IS YOUR SOLE AND applicable Support Certificate. This License Agreement EXCLUSIVE REMEDY FOR SYMANTEC’S BREACH OF does not otherwise permit You to obtain and use Content THIS WARRANTY. Updates. 8. Warranty Disclaimers: 6. Upgrades/Cross-grades: TO THE MAXIMUM EXTENT PERMITTED BY Symantec reserves the right to require that any upgrades APPLICABLE LAW, THE WARRANTIES SET FORTH IN (if any) of the Licensed Software may only be obtained SECTIONS 7.1 AND 7.2 ARE YOUR EXCLUSIVE in a quantity equal to the number indicated on the WARRANTIES AND ARE IN LIEU OF ALL OTHER WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED an evaluation agreement with Symantec for the Licensed WARRANTIES OF MERCHANTABILITY, SATISFACTORY Software and if You are provided the Licensed Software QUALITY, FITNESS FOR A PARTICULAR PURPOSE, for evaluation purposes, the following terms and AND NONINFRINGEMENT OF INTELLECTUAL conditions shall apply. Symantec grants to You a PROPERTY RIGHTS. SYMANTEC MAKES NO nonexclusive, temporary, royalty-free, non-assignable WARRANTIES OR REPRESENTATIONS THAT THE license to use the Licensed Software solely for internal LICENSED SOFTWARE, CONTENT UPDATES OR non-production evaluation. Such evaluation license shall UPGRADES WILL MEET YOUR REQUIREMENTS OR terminate (i) on the end date of the pre-determined THAT OPERATION OR USE OF THE LICENSED evaluation period, if an evaluation period is SOFTWARE, CONTENT UPDATES, AND UPGRADES pre-determined in the Licensed Software or (ii) sixty (60) WILL BE UNINTERRUPTED OR ERROR-FREE. YOU MAY days from the date of Your initial installation of the HAVE OTHER WARRANTY RIGHTS, WHICH MAY VARY Licensed Software, if no such evaluation period is FROM STATE TO STATE AND COUNTRY TO COUNTRY. pre-determined in the Licensed Software (“Evaluation Period”). The Licensed Software may not be transferred 9. Limitation of Liability: and is provided “AS IS” without warranty of any kind. You are solely responsible to take appropriate measures TO THE MAXIMUM EXTENT PERMITTED BY to back up Your system and take other measures to APPLICABLE LAW AND REGARDLESS OF WHETHER prevent any loss of files or data. The Licensed Software ANY REMEDY SET FORTH HEREIN FAILS OF ITS may contain an automatic disabling mechanism that ESSENTIAL PURPOSE, IN NO EVENT WILL SYMANTEC prevents its use after a certain period of time. Upon OR ITS LICENSORS, RESELLERS, SUPPLIERS OR expiration of the Licensed Software Evaluation Period, AGENTS BE LIABLE TO YOU FOR (i) ANY COSTS OF You will cease use of the Licensed Software and destroy PROCUREMENT OF SUBSTITUTE OR REPLACEMENT all copies of the Licensed Software. All other terms and GOODS AND SERVICES, LOSS OF PROFITS, LOSS OF conditions of this License Agreement shall otherwise USE, LOSS OF OR CORRUPTION TO DATA, BUSINESS apply to Your evaluation of the Licensed Software as INTERRUPTION, LOSS OF PRODUCTION, LOSS OF permitted herein. REVENUES, LOSS OF CONTRACTS, LOSS OF GOODWILL, OR ANTICIPATED SAVINGS OR WASTED 12. U.S. Government Restricted Rights: MANAGEMENT AND STAFF TIME; OR (ii) ANY SPECIAL, CONSEQUENTIAL, INCIDENTAL OR INDIRECT The Licensed Software is deemed to be commercial DAMAGES WHETHER ARISING DIRECTLY OR computer software as defined in FAR 12.212 and subject INDIRECTLY OUT OF THIS LICENSE AGREEMENT, to restricted rights as defined in FAR Section 52.227-19 EVEN IF SYMANTEC OR ITS LICENSORS, RESELLERS, "Commercial Computer Licensed Software - Restricted SUPPLIERS OR AGENTS HAS BEEN ADVISED SUCH Rights" and DFARS 227.7202, “Rights in Commercial DAMAGES MIGHT OCCUR. IN NO CASE SHALL Computer Licensed Software or Commercial Computer SYMANTEC’S LIABILITY EXCEED THE FEES YOU PAID Licensed Software Documentation”, as applicable, and FOR THE LICENSED SOFTWARE GIVING RISE TO THE any successor regulations. Any use, modification, CLAIM. NOTHING IN THIS AGREEMENT SHALL reproduction release, performance, display or disclosure OPERATE SO AS TO EXCLUDE OR LIMIT SYMANTEC’S of the Licensed Software by the U.S. Government shall LIABILITY TO YOU FOR DEATH OR PERSONAL INJURY be solely in accordance with the terms of this License ARISING OUT OF NEGLIGENCE OR FOR ANY OTHER Agreement. LIABILITY WHICH CANNOT BE EXCLUDED OR LIMITED BY LAW. THE DISCLAIMERS AND LIMITATIONS SET “Veritas Backup Reporter Client” is defined as a single FORTH ABOVE WILL APPLY REGARDLESS OF computer, storage drive or other device (i) on which WHETHER OR NOT YOU ACCEPT THE LICENSED licensee can install and use the software, (ii) from which SOFTWARE, CONTENT UPDATES OR UPGRADES. licensee accesses and uses the software installed on a network, or (iii) a physical connection point that links together two separate devices. A “Veritas Backup 10. Maintenance/Support: Reporter Client” is managed, monitored and/or protected by the software but that may not actually be running the Symantec has no obligation under this License software itself. Agreement to provide maintenance/support for the Licensed Software. Any maintenance/support purchased 12.2 Installation on Servers: for the Licensed Software is subject to Symantec’s then-current maintenance/support policies. The Licensed Software shall be licensed for the maximum number of Veritas Backup Reporter Clients managed by the Licensed Software. In the event that the Licensed 11. Software Evaluation: Software includes components to be installed on a server If the Licensed Software is provided to You for evaluation computer, You may install such portions of the Licensed purposes and You have an evaluation agreement with Software on any number of server computers so long as Symantec for the Licensed Software, Your rights to such installed Licensed Software is only used for the evaluate the Licensed Software will be pursuant to the authorized maximum number of Veritas Backup Reporter terms of such evaluation agreement. If You do not have Clients as may be specified in the License Module. 12.3 Third Party Access Licenses: and regulations in connection with Your use of the Licensed Software. In order to use any components of the Licensed Software designated as third party access license modules or 16.3. Audit: options in support of licensed Veritas Backup Reporter Clients (for example, IBM Tivoli Storage Manger Option, An auditor, selected by Symantec and reasonably Legato Networker Option and Commvault Option etc.), acceptable to You, may, upon reasonable notice and You must acquire a license for each such third party during normal business hours, but not more often than modules or options at additional charges for use with once each year, inspect Your records and deployment in VERITAS Backup Reporter order to confirm that Your use of the Licensed Software complies with this License Agreement and the applicable License Instrument. Symantec shall bear the costs of 13. Export Regulation: any such audit, except where the audit demonstrates that the Manufacturer’s Suggested Reseller Price (MSRP) You acknowledge that the Licensed Software and related value of Your non-compliant usage exceeds five percent technical data and services (collectively "Controlled (5%) of the MSRP value of Your compliant deployments. Technology") are subject to the import and export laws In such case, in addition to purchasing appropriate of the United States, specifically the U.S. Export licenses for any over-deployed Licensed Software, You Administration Regulations (EAR), and the laws of any shall reimburse Symantec for the auditor’s reasonable country where Controlled Technology is imported or actual fees for such audit. re-exported. You agree to comply with all relevant laws and will not to export any Controlled Technology in 16.4. Governing Law; Severability; Waiver: contravention to U.S. law nor to any prohibited country, entity, or person for which an export license or other If You are located in North America or Latin America, governmental approval is required. All Symantec this License Agreement will be governed by the laws of products, including the Controlled Technology are the State of California, United States of America. If you prohibited for export or re-export to Cuba, North Korea, are located in China, this License Agreement will be Iran, Syria and Sudan and to any country subject to governed by the laws of the Peoples Republic of China. relevant trade sanctions. You hereby agree that You will Otherwise, this License Agreement will be governed by not export or sell any Controlled Technology for use in the laws of England. Such governing laws are exclusive connection with chemical, biological, or nuclear weapons, of any provisions of the United Nations Convention on or missiles, drones or space launch vehicles capable of Contracts for Sale of Goods, including any amendments delivering such weapons. thereto, and without regard to principles of conflicts of law. If any provision of this License Agreement is found partly or wholly illegal or unenforceable, such provision 14. Termination: shall be enforced to the maximum extent permissible, This License Agreement shall terminate upon Your and remaining provisions of this License Agreement breach of any term contained herein. Upon termination, shall remain in full force and effect. A waiver of any You shall immediately stop using and destroy all copies breach or default under this License Agreement shall of the Licensed Software. not constitute a waiver of any other subsequent breach or default. 15. Survival: 16.5. Third Party Programs: The following provisions of this License Agreement This Licensed Software may contain third party software survive termination of this License Agreement: programs (“Third Party Programs”) that are available Definitions, License Restrictions and any other under open source or free software licenses. This License restrictions on use of intellectual property, Agreement does not alter any rights or obligations You Ownership/Title, Warranty Disclaimers, Limitation of may have under those open source or free software Liability, U.S. Government Restricted Rights, Export licenses. Notwithstanding anything to the contrary Regulation, Survival, and General. contained in such licenses, the disclaimer of warranties and the limitation of liability provisions in this License Agreement shall apply to such Third Party Programs. 16. General: 16.6. Customer Service: 16.1. Assignment: Should You have any questions concerning this License You may not assign the rights granted hereunder or this Agreement, or if You desire to contact Symantec for any License Agreement, in whole or in part and whether by reason, please write to: (i) Symantec Enterprise Customer operation of contract, law or otherwise, without Care, 555 International Way, Springfield, Oregon 97477, Symantec’s prior express written consent. U.S.A., (ii) Symantec Enterprise Customer Care Center, 16.2. Compliance With Applicable Law: PO BOX 5689, Dublin 15, Ireland, or (iii) Symantec Enterprise Customer Care, 1 Julius Ave, North Ryde, You are solely responsible for Your compliance with, NSW 2113, Australia. and You agree to comply with, all applicable laws, rules, 16.7. Entire Agreement: This License Agreement and any related License for all managed Clients being reported on through the Instrument are the complete and exclusive agreement use of the Licensed Software, whether virtual or physical. between You and Symantec relating to the Licensed Software and supersede any previous or contemporaneous oral or written communications, proposals, and representations with respect to its subject matter. This License Agreement prevails over any conflicting or additional terms of any purchase order, ordering document, acknowledgement or confirmation or other document issued by You, even if signed and returned. This License Agreement may only be modified by a License Instrument that accompanies or follows this License Agreement.
17. Additional Terms and Conditions: Your use of the Licensed Software is subject to the terms and conditions below in addition to those stated above. 17.1. Definitions: “Client” is defined as a single computer or other device (i) on which licensee can install and use the software, (ii) from which licensee accesses and uses the software installed on a network. In addition, a “managed Client” is defined as a Client that is managed, monitored and/or protected by the software but that may not actually be running the software itself. 17.2. Installation on Servers: The Licensed Software shall be licensed for the maximum number of Clients managed by the Licensed Software. In the event that the Licensed Software includes components to be installed on a server computer, You may install such portions of the Licensed Software on any number of server computers so long as such installed Licensed Software is only used for the authorized maximum number of managed Clients as may be specified in the License Instrument. 17.3. Third-Party Access Licenses: In order to use any components of the Licensed Software designated as third party access license modules or options in support of licensed managed Clients (for example, IBM Tivoli Storage Manger Option, Legato Networker Option and Commvault Option etc.), You must acquire a license for each such third party modules or options at additional charges for use with VERITAS NetBackup Backup Reporter. 17.4. Virtualization: Notwithstanding any other provision of this Agreement, if You are using the Licensed Software in a virtual environment to manage and create reports from a virtual Client(s), You must acquire a license to use the Licensed Software for the number of managed virtual Clients from which reporting is made. For the purposes of this Agreement in such situations, a virtual Client, machine or environment is considered the same as an actual physical Client, machine or environment in connection with such computer. Therefore, You understand that you must acquire a license to use the Licensed Software Contents
Technical Support ...... 4 Chapter 1 Planning your Veritas Backup Reporter installation ...... 17 About the resources required in the installation process ...... 17 About selecting Veritas Backup Reporter hosts ...... 18 About selecting a Veritas Backup Reporter Management Server host ...... 18 About selecting a Veritas Backup Reporter Agent host ...... 19 About selecting a Java View Builder host ...... 19 About selecting a Veritas Backup Reporter console host ...... 19 About typical Veritas Backup Reporter Agent deployment scenarios ...... 20 Scenario 1: Veritas Backup Reporter Agent installed on the management server host ...... 20 Scenario 2: Veritas Backup Reporter Agent installed on a backup application host ...... 21 Scenario 3: Veritas Backup Reporter Agents installed on backup application hosts ...... 22 Chapter 2 Veritas Backup Reporter host and firewall requirements ...... 25 Operating system requirements ...... 25 System resource requirements ...... 27 Solaris system resource requirements ...... 28 Windows system resource requirements ...... 28 About configuring Veritas Backup Reporter firewall ...... 29 Changing the VRTSweb HTTP port ...... 32 Configuring Veritas Backup Reporter Management Server behind NAT firewall ...... 33 Web browser requirements ...... 35 14 Contents
Chapter 3 Installing, uninstalling, and upgrading Veritas Backup Reporter ...... 37 Installing Veritas Backup Reporter ...... 37 About AT configuration scenarios in Veritas Backup Reporter 6.5 ...... 37 Verifying the authentication mode for Symantec Product Authentication Service ...... 38 Installing Veritas Backup Reporter on Solaris ...... 40 Installing Veritas Backup Reporter on Windows ...... 45 Resolving agent authentication failures manually on Solaris and Windows ...... 49 Verifying that Veritas Backup Reporter is running properly ...... 51 Installing and removing the Veritas Backup Reporter demo database on Windows ...... 51 Upgrading Veritas Backup Reporter ...... 53 Upgrading to Veritas Backup Reporter 6.5 components on Solaris ...... 53 Upgrading the database manually on Solaris and Windows ...... 55 Identifying the version of .jar files ...... 58 Modifying Veritas Backup Reporter on Solaris ...... 59 Modifying Veritas Backup Reporter on Windows ...... 59 Uninstalling Veritas Backup Reporter on Solaris and Windows ...... 60 Uninstalling Veritas Backup Reporter on Solaris ...... 60 Uninstalling Veritas Backup Reporter on Windows ...... 62 Chapter 4 Starting and stopping Veritas Backup Reporter Service ...... 65 Starting and stopping the Veritas Backup Reporter Management Server on Solaris and Windows ...... 65 Stopping and starting the Veritas Backup Reporter Agent on Solaris and Windows ...... 68
Chapter 5 Configuring Veritas Backup Reporter service ...... 71 Setting data retention policies ...... 71 Configuring Veritas Backup Reporter Agent Modules ...... 72 About the Veritas NetBackup PureDisk module ...... 72 About Veritas NetBackup module variables ...... 73 About the Veritas BackupExec module variables ...... 75 About the EMC Legato Networker module variables ...... 75 About the IBM Tivoli Storage Manager module variables ...... 76 Contents 15
About the CommVault Galaxy & Backup agent module variables ...... 77 Configuring the SMTP Mail server for Veritas Backup Reporter for Solaris and Windows ...... 77 Disabling error log collection on Veritas Backup Reporter Agents ...... 78 About creating and importing object views in XML ...... 79 Chapter 6 Backing up and restoring Veritas Backup Reporter data ...... 81 Backing up the Veritas Backup Reporter database ...... 81 Restoring the Veritas Backup Reporter database ...... 82
Appendix A Veritas Backup Reporter install packages ...... 87 About Veritas Backup Reporter install packages for Solaris and Windows ...... 87 Solaris packages installed with Veritas Backup Reporter components ...... 89
Index ...... 91 16 Contents Chapter 1
Planning your Veritas Backup Reporter installation
This chapter includes the following topics:
■ About the resources required in the installation process
■ About selecting Veritas Backup Reporter hosts
■ About typical Veritas Backup Reporter Agent deployment scenarios
About the resources required in the installation process Rreview the documentation and resources that Symantec provides before you install Veritas Backup Reporter, to ensure proper product functionality. The following documents and resources are necessary to plan and successfully complete your installation.
■ Veritas Backup Reporter Hardware and Software Compatibility List (HSCL.pdf) that is shipped with the product CD and is updated regularly at http://support.veritas.com/docs/285754.
■ Veritas Backup Reporter Release Notes
■ A license key (possibly multiple keys for different features)
■ Administrator accounts and passwords for all target hosts
■ A checklist of the Veritas Backup Reporter features you plan to use 18 Planning your Veritas Backup Reporter installation About selecting Veritas Backup Reporter hosts
■ Additional backup application licenses, depending on how you choose to deploy the Veritas Backup Reporter Agent The backup products (for example, Veritas NetBackup or Veritas BackupExec) you need to report on determine the deployment scenario of the Veritas Backup Reporter Agent. See “About typical Veritas Backup Reporter Agent deployment scenarios” on page 20.
About selecting Veritas Backup Reporter hosts In addition to the standard system requirements for Veritas Backup Reporter, its various components play important role while you choose hosts. The following topics provide additional information for choosing hosts: About selecting a Veritas Backup Reporter Management Server host About selecting a Veritas Backup Reporter Agent host About selecting a Java View Builder host About selecting a Veritas Backup Reporter console host
About selecting a Veritas Backup Reporter Management Server host The Veritas Backup Reporter Management Server is a Web application that acts as the central point of the product. Veritas Backup Reporter Agent Modules collect data from various backup products and send it to the management server. The management server then merges the backup data received from all backup products and stores it in the Sybase ASA database server. Use the following criteria to identify the kind of system that you need for hosting the management server and Web Engine:
■ The host should meet the system requirements described in detail in theVeritas Backup Reporter Release Notes and Veritas Backup Reporter Installation Guide. See “System resource requirements ” on page 27.
■ The host should have sufficient storage space to accommodate the historical data. It is recommended that you install the database on mirrored or RAID-protected storage.
■ The host must have network access to hosts that are running backup applications, such as Veritas NetBackup, Veritas Backup Exec, or EMC Legato Networker. Planning your Veritas Backup Reporter installation 19 About selecting Veritas Backup Reporter hosts
For more information about the Veritas Backup Reporter Management Server and its architecture, see the Veritas Backup Reporter Administrator’s Guide.
About selecting a Veritas Backup Reporter Agent host The Veritas Backup Reporter Agent collects high-level data from various backup applications. Veritas Backup Reporter monitors these applications locally or remotely. Use the following general criteria to identify the kind of system you need to host the agent:
■ The system should meet the system requirements described in detail in the Veritas Backup Reporter Release Notes and Veritas Backup Reporter Installation Guide. See “System resource requirements ” on page 27.
■ If the agent and the management server are installed on separate hosts, the agent host must connect to the management server host through the 1556 and 2821 ports. The management server host must connect to the 7806 port of the agent host. The choice of an agent host also depends on your network environment, the backup applications that you want to monitor, and the operating systems of the backup application hosts. For more information about the Veritas Backup Reporter Agent and its architecture, see the Veritas Backup Reporter Administrator’s Guide.
About selecting a Java View Builder host An administrator can create, modify, and manage access to the object views (logical groups of IT assets) using Java View Builder. The views are available in the Veritas Backup Reporter console. The type of system that you need to host the Java View Builder should meet the system requirements described in detail in the Veritas Backup Reporter Release Notesand Veritas Backup Reporter Installation Guide. See “System resource requirements ” on page 27. For more information about the Java View Builder and its architecture, see the Veritas Backup Reporter Administrator’s Guide.
About selecting a Veritas Backup Reporter console host The Veritas Backup Reporter console is a graphical user interface that displays reports and other information for users of Veritas Backup Reporter through a 20 Planning your Veritas Backup Reporter installation About typical Veritas Backup Reporter Agent deployment scenarios
standard Web browser. For the Veritas Backup Reporter users, the console is a central point to manage cost analysis and chargeback for services, displaying and managing reports. One of the following Web browsers is required to run the console:
■ Internet Explorer 6.x or later
■ Mozilla Firefox 1.5 or later Your browser must support JScript 5.5 with Microsoft Internet Explorer 6 or later. Additionally, for Internet Explorer, Secure Sockets Layer (SSL) 3.0 ActiveX scripting must be enabled.
Note: For Internet Explorer 6.0 on Windows 2003 (Server and Advanced Server), set the default Intranet zone security level to medium or lower.
About typical Veritas Backup Reporter Agent deployment scenarios Following are the typical deployment scenarios for the Veritas Backup Reporter Agent: Scenario 1: Veritas Backup Reporter Agent installed on the management server host Scenario 2: Veritas Backup Reporter Agent installed on a backup application host Scenario 3: Veritas Backup Reporter Agents installed on backup application hosts The scenario you choose depends on a number of factors, including the following:
■ The backup application you want to monitor
■ The operating system of the host running the backup application
■ Your organization’s policies that determine adding software on dedicated backup application hosts
■ Backup host system performance criteria
Scenario 1: Veritas Backup Reporter Agent installed on the management server host You can install the Veritas Backup Reporter Agent on the Veritas Backup Reporter Management Server host. You then can configure the agent to collect data from backup application master and media servers. Planning your Veritas Backup Reporter installation 21 About typical Veritas Backup Reporter Agent deployment scenarios
In this deployment scenario, Veritas Backup Reporter can monitor the following:
■ Veritas NetBackup
■ Veritas NetBackup PureDisk
■ Veritas Backup Exec
■ IBM Tivoli Storage Manager
■ CommVault Galaxy Backup & Recovery
■ EMC Legato Networker This deployment scenario is recommended if the operating systems of the NetBackup or Tivoli Storage Manager hosts are not supported by the Veritas Backup Reporter Agent. Advantages of installing the Veritas Backup Reporter Agent on the Veritas Backup Reporter Management Server host include the following:
■ You do not have to install additional software on backup application hosts as the backup data is gathered remotely.
■ You need to maintain only one machine for both Veritas Backup Reporter Management Server and agent, which avoids the maintenance that might otherwise be involved in upgrading the agent. Disadvantages of installing the Veritas Backup Reporter Agent on the Veritas Backup Reporter Management Server host include the following:
■ You must install a component of the backup application on the Veritas Backup Reporter Management Server host.
■ In some situations, a backup application license key is required for the component installed on the Veritas Backup Reporter Management Server host. For more information about enabling, modifying, and disabling Veritas Backup Reporter Agent Module configurations, see the Veritas Backup Reporter Administrator’s Guide.
Scenario 2: Veritas Backup Reporter Agent installed on a backup application host You can install the Veritas Backup Reporter Agent on a system in your network that hosts a backup application. You can configure the agent to collect data from the backup application on its own host as well as applications on other hosts within the network. In this deployment scenario, Veritas Backup Reporter can monitor the following:
■ Veritas NetBackup 22 Planning your Veritas Backup Reporter installation About typical Veritas Backup Reporter Agent deployment scenarios
■ IBM Tivoli Storage Manager
■ EMC Legato Networker This is the highly recommended deployment scenario because it has a very low impact on the backup environment by adding only one agent. The operating system of the backup application host must be supported by the Veritas Backup Reporter Agent. Advantages of installing the Veritas Backup Reporter Agent on a remote backup application host include the following:
■ Ease of maintenance to upgrade agent; you only service one host.
■ Minimal intrusion on backup hosts; agent installed on only one backup host. A disadvantage of installing the Veritas Backup Reporter Agent on a remote backup application host is that the Veritas Backup Reporter Agent may use significant system resources, which can impact the backup application host’s performance. For more information about enabling, modifying, and disabling Veritas Backup Reporter Agent Module configurations, see the Veritas Backup Reporter Administrator’s Guide.
Scenario 3: Veritas Backup Reporter Agents installed on backup application hosts You can install the Veritas Backup Reporter Agents on all backup hosts in your network, provided the hosts run an operating system that the agent supports. You can then configure each agent to collect data from the backup host on which it is installed. In this deployment scenario, Veritas Backup Reporter can monitor the following:
■ Veritas NetBackup
■ Veritas Backup Exec
■ IBM Tivoli Storage Manager
■ EMC Legato Networker For most environments, Symantec does not recommend this deployment strategy. However, for Legato NetWorker environment, it is the only supported deployment option. The advantage of installing the Veritas Backup Reporter Agents on backup application hosts is that it distributes the data collection task across all backup hosts, minimizing the load on any one host. Planning your Veritas Backup Reporter installation 23 About typical Veritas Backup Reporter Agent deployment scenarios
The disadvantages of installing the Veritas Backup Reporter Agents on backup application hosts is that the maintenance is high while upgrading the Veritas Backup Reporter Agent. For more information about enabling, modifying, and disabling Veritas Backup Reporter Agent Module configurations, see the Veritas Backup Reporter Administrator’s Guide. 24 Planning your Veritas Backup Reporter installation About typical Veritas Backup Reporter Agent deployment scenarios Chapter 2
Veritas Backup Reporter host and firewall requirements
This chapter includes the following topics:
■ Operating system requirements
■ System resource requirements
■ About configuring Veritas Backup Reporter firewall
■ Web browser requirements
Operating system requirements Table 2-1 lists the operating system requirements for Veritas Backup Reporter hosts.
Note: The Veritas Backup Reporter Management Server, Agent, and Java View Builder require the following components to be installed on a Windows system: Microsoft C Runtime library 7.1 and Microsoft C++ runtime library 7.1 26 Veritas Backup Reporter host and firewall requirements Operating system requirements
Table 2-1 Veritas Backup Reporter operating system requirements
Veritas Backup Supported operating systems System resources Reporter component
Management Solaris 8, 9, 10 Solaris Server Windows 2000 SP4 or later (Server, ■ 2 x 1 GHz UltraSPARC® Advanced Server, Datacenter Server) IIIi processor or faster CPUs, 4 GB RAM, 40 GB Windows Server 2003 (Standard Edition, of file system space Enterprise Edition [32-bit only], (Minimum) Datacenter Edition [32-bit only], Web Edition) ■ 4 x 1 GHz UltraSPARC® IIIi processor or faster VMware ESX Server 3.0 CPUs, 12 GB RAM, 2 Note: Management Server is supported dedicated disks of 20 when operated in a VMware virtual GB each, for DB machine guest operating system (Recommended) environment. Windows
■ 2 x 2.5 GHz or faster CPUs, 4 GB RAM, 40 GB of file system space ■ 4 x 2.5 GHz or faster CPUs, 8 GB RAM, 2 dedicated disks of 20 GB each, for DB (Recommended)
Agent Solaris 8, 9, 10 Solaris
Windows 2000 SP4 or later (Server, ■ 1 GHz, 1 GB RAM Advanced Server, Datacenter Server) (Minimum) Windows Server 2003 (Standard Edition, Windows Enterprise Edition [32-bit only], ■ 2.5 GHz, 1GB RAM Datacenter Edition [32-bit only], Web (Minimum) Edition) VMware ESX Server 3.0 Note: Agent is supported when operated in a VMware virtual machine guest operating system environment. Veritas Backup Reporter host and firewall requirements 27 System resource requirements
Table 2-1 Veritas Backup Reporter operating system requirements (continued)
Veritas Backup Supported operating systems System resources Reporter component
Java View Builder Solaris 8, 9, 10 Solaris
Windows 2000 SP4 or later (Server, ■ 1 GHz, 1 GB RAM Advanced Server, Datacenter Server) (Minimum) Windows Server 2003 (Standard Edition, Windows Enterprise Edition [32-bit only], ■ 2.5 GHz, 1GB RAM Datacenter Edition [32-bit only], Web (Minimum) Edition)
Console Any platform with network access to the The minimum required Veritas Backup Reporter Management resolution for the console Server host and a supported Web is 1024 x 768. browser. Veritas Backup Reporter supports the following Web browsers:
■ For Solaris - Mozilla Firefox 1.5 or later ■ For Windows - Mozilla Firefox 1.5 or later, Internet Explorer 6.0 or later
For information on applying operating system patches, see Veritas Backup Reporter Release Notes.
Note: The Veritas Backup Reporter installer automatically sets the max heap size to 1024MB. If your system requires a lesser max heap size to properly run all applications, set the max heap size to 512MB. Refer to the Performance Tuning section from the Veritas Backup Reporter Administrator's Guide to set the max heap size.
System resource requirements You can determine the memory and disk space requirements for Veritas Backup Reporter hosts that are different depending on your operating system. Memory and disk spaces are required in addition to the resources already being used by other software on the host. 28 Veritas Backup Reporter host and firewall requirements System resource requirements
Note: The Veritas Backup Reporter installer automatically sets the max heap size to 1024 MB. If your system requires a lesser max heap size to properly run all applications, set the max heap size to 512 MB. Refer to the Performance Tuning section from the Veritas Backup Reporter Administrator's Guide to set the max heap size.
Warning: Veritas Backup Reporter requires an NTFS-formatted installation directory. Installations attempted on drives formatted with FAT32 will fail.
Solaris system resource requirements Table 2-2 provides system resource requirements for Solaris hosts.
Table 2-2 System resources for Solaris hosts
Veritas Backup Reporter Memory required Memory recommended Disk component space required
Management Server 2 GB 4 GB 900 MB
Agent 1 GB - 300 MB
Java View Builder 256 MB - 300 MB
CPU recommendations for Solaris hosts are as follows:
Minimum required CPU times speed 2 x 1 GHz
Recommended CPU times speed 4 x 1 GHz
Windows system resource requirements Table 2-3 provides system resource requirements for Windows hosts.
Table 2-3 System resources for Windows hosts
Veritas Backup Reporter Memory required Memory Disk component recommended space required
Management Server 512 MB 1 GB 900 MB
Agent 256 MB 512 MB 200 MB Veritas Backup Reporter host and firewall requirements 29 About configuring Veritas Backup Reporter firewall
Table 2-3 System resources for Windows hosts (continued)
Veritas Backup Reporter Memory required Memory Disk component recommended space required
Java View Builder 256 MB 512 MB 200 MB
CPU recommendations for Windows hosts are as follows:
Minimum required CPU times speed 2 x 2.5 GHz
Recommended CPU times speed 4 x 2.5 GHz
The Veritas Backup Reporter Hardware and Software Compatibility List contains the latest information about supported hardware and software. The list is updated regularly. You also can refer to http://www.ccsvc.veritas.com/tpmweb/public/sizing/sizing_recommendations.html for the latest information regarding hardware and software requirements. You can find the current compatibility list on the Symantec Support Web site http://support.veritas.com/docs/285754.
Note: Before installing or upgrading Veritas Backup Reporter, review the current compatibility list to confirm the compatibility of your hardware and software.
If you do not find your hardware or software listed or if you have any questions about the information in the compatibility list, contact Symantec Support.
About configuring Veritas Backup Reporter firewall For the Veritas Backup Reporter Management Server, agent, and Java View Builder to communicate across a firewall, the firewall must be configured to allow http access to several specific ports. Table 2-4 lists the default ports that Veritas Backup Reporter uses to transfer information. 30 Veritas Backup Reporter host and firewall requirements About configuring Veritas Backup Reporter firewall
Table 2-4 Default ports in a Veritas Backup Reporter installation
Port Protocol Initiator > recipient Purpose Impact if blocked
25 SMTP over Veritas Backup Email reports You cannot receive scheduled TCP/IP Reporter Management email reports if the Server > email server management server cannot reach the email server that is configured to use.
1885 TCP/IP Veritas Backup Trap sharing None. Not used across Reporter Management firewall. Server > Veritas Backup Reporter Management Server
2821 TCP/IP agent, Java View Authentication with Users cannot authenticate Builder, CLI tools > Veritas Backup Reporter with Symantec Product Veritas Backup Management Server Authentication Service and Reporter Management Veritas Backup Reporter Server Management Server; access is denied to the users.
2994 TCP/IP Veritas Backup Store settings None. Not used across Reporter Management firewall. Server > Database
2994 TCP/IP Alert Manager > Store collector data, alerts, None. Not used across Database policy settings firewall.
5431 IIOP over TCP/IP Alert Manager > Alert monitoring None. Not used across Veritas Backup firewall. Reporter Management Server
1556 CORBA over agent, Java View All communications with Veritas Backup Reporter SSLIOP Builder, CLI tools > Veritas Backup Reporter Management Server does not Veritas Backup Management Server respond to agent, Java View Reporter Management (through PBX) Builder, and so on. Server
7806 CORBA over Veritas Backup Status and data requests Agent status page does not TCP/IP Reporter Management for frequent updates of the work, CLI tools for querying Server and CLI tools > agent agent do not work remotely. agent
8181 HTTP over Web browser > Veritas Run Veritas Enterprise Users cannot access the TCP/IP Backup Reporter Reporter console console. Management Server Veritas Backup Reporter host and firewall requirements 31 About configuring Veritas Backup Reporter firewall
Table 2-4 Default ports in a Veritas Backup Reporter installation (continued)
Port Protocol Initiator > recipient Purpose Impact if blocked
8443 HTTPS over Web browser > Veritas Run Veritas Enterprise Users cannot access the TCP/IP Backup Reporter Reporter console console. Management Server
Figure 2-1shows the default port assignments. 32 Veritas Backup Reporter host and firewall requirements About configuring Veritas Backup Reporter firewall
Figure 2-1 Veritas Backup Reporter default ports
Changing the VRTSweb HTTP port Use the webgui delport and webgui add commands to delete and add ports. If you need to change the VRTSweb HTTP port on either Windows or Solaris, use the following procedures. Veritas Backup Reporter host and firewall requirements 33 About configuring Veritas Backup Reporter firewall
For additional information about the webgui command, refer to help provided by running the webgui help delport and webgui help addport commands. To change the VRTSweb HTTP port on Windows 1 Before changing the port, confirm that no other service is listening on the port by typing the following command:
netstat -an | find "9191"
No lines should be returned. The -an option is important in case any program has updated the services list. 2 Type the following command:
cd "c:\Program Files\VERITAS\VRTSweb\bin" 3 To delete and add the new port number, type the following commands:
webgui delport 8181
webgui addport 9191 HTTP where port 8181 is the original port that you want to change, and port 9191 is whatever new port number you chosen. To change the VRTSweb HTTP port on Solaris 1 Before changing the port, confirm that no other service is listening on the port by typing the following command:
netstat -an | grep 9191
No lines should be returned. The -an option is important in case any program updated the services list. 2 Type the following command:
/opt/VRTSweb/bin 3 To delete and add the new port number, type the following commands:
. /webgui delport 8181
. /webgui addport 9191 HTTP where port 8181 is the original port that you want to change, and port 9191 is whatever new port number you chose.
Configuring Veritas Backup Reporter Management Server behind NAT firewall When a firewall is configured to act as a Network Address Translation (NAT) device to route packets to hidden addresses behind the firewall, you must change 34 Veritas Backup Reporter host and firewall requirements About configuring Veritas Backup Reporter firewall
the actual public IP address (the NAT address) of the Veritas Backup Reporter Management Server and the Veritas Alert Manager. To configure the Veritas Backup Reporter Management Server behind a NAT 1 On the Veritas Backup Reporter Management Server, do one of the following:
■ On Solaris, open a console and log in as root.
■ On Windows, open a Windows command prompt and log in as an administrator or user in the Administrators group. 2 Stop the Veritas Backup Reporter Management Server.
■ On Solaris, enter /opt/VRTSccsvs/bin/Veritas Backup Reporterserver stop
■ On Windows, use the Windows Service Control Manager (SCM) and stop the Veritas Backup Reporter Management Server.
3 Using a text editor, open the Veritas Backup Reporter_conf.properties present in the following default location:
■ On Solaris, enter /opt/VRTSccsvs/conf
■ On Windows, enter \Program Files\Symantec\Veritas Backup Reporter\Server\conf
4 Using your text editor, search for the following string. corba.external.ip= If the string is not present, add it. 5 Enter the actual public IP address (the “natted” address) for the Veritas Backup Reporter Management Server. For example: corba.external.ip=255.255.255.255 6 Save your changes and close the Veritas Backup Reporter_conf.properties file. 7 Restart the Veritas Backup Reporter Management Server by doing one of the following:
On Solaris, enter /opt/VRTSccsvs/bin/Veritas Backup Reporterserver start On Windows, use the Windows SCM and restart the Veritas Backup Reporter Management Server. Veritas Backup Reporter host and firewall requirements 35 Web browser requirements
Note: To enable users to select a domain at logon, Veritas Backup Reporter Management Server hosts running Windows must be configured either in DNS or with a fully qualified domain name.
Web browser requirements You can run the Veritas Backup Reporter console on any of the following Web browsers:
■ Internet Explorer 6.0 or later
■ Netscape Navigator 7.2 or later
■ Mozilla 1.4 or later (for Solaris only)
■ Mozilla Firefox 1.0 or later Your Web browser must support either JScript 5.5 (provided with Microsoft Internet Explorer 6 or later) or JavaScript 1.2 (provided with Netscape Navigator 7.x). Additionally, for Internet Explorer, Secure Sockets Layer (SSL) 3.0 ActiveX scripting must be enabled. If you use pop-up blockers, either disable them or configure them to accept pop-ups from the Veritas Backup Reporter Web engines to which you connect. Note that pop-up blocking is enabled by default in Netscape 7.2.
Note: For Internet Explorer 6.0 on Windows 2003 (Server and Advanced Server), set the default Intranet zone security level to MEDIUM or lower. 36 Veritas Backup Reporter host and firewall requirements Web browser requirements Chapter 3
Installing, uninstalling, and upgrading Veritas Backup Reporter
This chapter includes the following topics:
■ Installing Veritas Backup Reporter
■ Upgrading Veritas Backup Reporter
■ Uninstalling Veritas Backup Reporter on Solaris and Windows
Installing Veritas Backup Reporter This section describes the installation procedures of Veritas Backup Reporter on Solaris and Windows.
About AT configuration scenarios in Veritas Backup Reporter 6.5 Veritas Backup Reporter uses Symantec Product Authentication Service (AT) to handle user authentication. Refer to the Veritas Backup Reporter Administrator's Guide for more details on Symantec Product Authentication Service. For instructions on migrating brokers, refer to the Symantec Product Authentication Service Administrator's Guide. In Veritas Backup Reporter 6.5, you can configure AT - Root Broker (Root) and Authentication Broker (AB) - in a number of ways as per your requirements, during installation or upgrade. The possible AT scenarios are described as follows: 38 Installing, uninstalling, and upgrading Veritas Backup Reporter Installing Veritas Backup Reporter
Fresh install of Veritas ■ Root + AB on Veritas Backup Reporter Management Server Backup Reporter 6.5 host (local Root) ■ AB on Veritas Backup Reporter Management Server host and Root on a remote host (remote root)
Fresh install of Veritas ■ Retain the existing Root + AB configuration for Veritas Backup Backup Reporter 6.5 on Reporter 6.5 AT host ■ Configure AB on the existing Root Broker host (Root > Root + AB) ■ Configure Root Broker with the existing AB (AB > Root + AB) ■ Retain the existing AB configuration with the existing remote Root ■ Retain the existing AB configuration with the new remote Root
Upgrade from Veritas ■ Retain the existing Root + AB configuration from Veritas Backup Reporter to 6.2 Backup Reporter to 6.2 to 6.5 ■ Downgrade from Root + AB to AB (required for PureDisk Agent Module configuration) in Veritas Backup Reporter to 6.2 installation and retain the AB configuration in Veritas Backup Reporter 6.5 using the existing remote Root ■ Downgrade from Root + AB to AB (required for PureDisk Agent Module configuration) Veritas Backup Reporter to 6.2, retain the AB configuration in Veritas Backup Reporter 6.5 and point to the new remote Root ■ Downgrade from Root + AB to AB (required for PureDisk Agent Module configuration) Veritas Backup Reporter to 6.2, and upgrade the configuration to Root+AB in Veritas Backup Reporter 6.5
In case you want to change the AT configuration after installing or upgrading Veritas Backup Reporter, you can downgrade or upgrade Veritas Backup Reporter. Refer to the Veritas Backup Reporter Administrator's Guide.
Verifying the authentication mode for Symantec Product Authentication Service This section provides the procedure to verify the authentication mode of Symantec Product Authentication Service AT. Installing, uninstalling, and upgrading Veritas Backup Reporter 39 Installing Veritas Backup Reporter
To verify the authentication mode for Symantec Product Authentication Service on Solaris 1 Determine if Symantec Product Authentication Service is installed on the host by running the following command:
pkginfo | grep VRTSat 2 Change your directory to the installation directory as follows:
cd /opt/VRTSat/bin/ 3 If Symantec Product Authentication Service is installed, at a command prompt, enter the following:
./vssat showbrokermode The command returns an integer value in the range of 0 to 3.
The vssat command can be used to verify the following:
■ Appropriate trust relationship was established
■ Private domains were created for the product
■ Authentication principles have been created for the product
Mode 0: The broker is not configured Mode 1: The broker is running in AB mode Mode 2: The broker is running in Root Only mode. Mode 3: The broker is running in Root + AB mode
To modify the authentication mode for Symantec Product Authentication Service on Solaris 1 Stop the vxatd process by entering the following:
vxatd stop 2 Change your directory to the installation directory by entering the following:
cd /opt/VRTSat/bin 3 Run the following command to change the Symantec Product Authentication Service mode:
vxatd -o -a -r 4 Start the vxatd process by entering the following:
vxatd start 40 Installing, uninstalling, and upgrading Veritas Backup Reporter Installing Veritas Backup Reporter
To verify the authentication mode for Symantec Product Authentication Service on Windows 1 Determine if Symantec Product Authentication Service is installed on a Windows host by checking the Windows Services. 2 Change your directory to the installation directory by entering the following:
cd \Program Files\Veritas\Security\Authentication\bin 3 At the command prompt, enter the following:
vssat showbrokermode The command returns an integer value in the range of 0 to 3.
Mode 0: The broker is not configured Mode 1: The broker is running in AB mode Mode 2: The broker is running in Root Only mode Mode 3: The broker is running in Root + AB mode
To modify the authentication mode for Symantec Product Authentication Service on Windows 1 Using the Windows services console, stop the Symantec Product Authentication Service. 2 Change your directory to the installation directory as follows:
cd \Program Files\Veritas\Security\Authentication\bin 3 Run the following command to change the Symantec Product Authentication Service mode:
vxatd -o -a -r 4 Using the Windows Services console, restart the Symantec Product Authentication Service.
Installing Veritas Backup Reporter on Solaris You can install, modify, and uninstall Veritas Backup Reporter components on Solaris and Windows hosts. You can also upgrade from 4.2, 6.0, and 6.2 versions to Veritas Backup Reporter 6.5.
Note: To install Veritas Backup Reporter in clustered mode, refer to the Veritas Backup Reporter Clustering Guide. Installing, uninstalling, and upgrading Veritas Backup Reporter 41 Installing Veritas Backup Reporter
Use the Veritas Backup Reporter Install Script, which resides in the root directory in the product CD, to install Veritas Backup Reporter on a Solaris host. The install comprises the following phases:
■ Selecting components to install
■ Configuring components in the install queue
■ Installing the components To install Veritas Backup Reporter components on Solaris 1 Open a UNIX console and log in as root on the target host. 2 Mount the appropriate Veritas Backup Reporter 6.5 product CD for the components you are installing. 3 Type the following command and press Enter:
./installvbr The Install Script displays a list of Veritas Backup Reporter components available for installation. If any components are already installed, the script lists those separately. 4 To add the component to the install queue, type its corresponding menu number and press Enter. The label [INSTALL] appears next to each selected component to indicate that it is in the install queue. Repeat this step for each component you want to install. 5 To remove a selected component from the install queue, type the component’s menu number again and press Enter. 6 After adding components to the queue, type the menu number that corresponds to the Finished with selections option and press Enter. 7 Review the list of components in the install queue. 8 Type y and press Enter to confirm the selection and continue.
9 Type n and press Enter to return to the component list and revise your selection. The next series of prompts collects configuration information for the components in the install queue. The steps you need to complete may vary depending on which components you plan to install. 42 Installing, uninstalling, and upgrading Veritas Backup Reporter Installing Veritas Backup Reporter
To configure components in the install queue 1 Type a directory path under which to install the components and press Enter. 2 To accept the default path (/opt), press Enter without typing a directory path. The remaining configuration steps may vary depending on which components you are installing. 3 If you are installing the Veritas Backup Reporter Management Server, do the following:
■ Type a directory path under which to install the Veritas Backup Reporter database and press Enter.
The Veritas Backup Reporter database server may require up to 1 GB of temporary space at runtime. By default, temporary files will be created in the database installation directory, /var/Veritas/ccs_data.
To accept the default path (/var/Veritas/ccs_data), press Enter without typing a directory path. If you specify an alternate database directory, the script creates the folder ccs_data below your directory. This part of the directory path is fixed.
■ Type the network address (fully qualified domain name or IP address) to which users should point their browsers to connect to the Web Engine, and then press Enter.
Please specify a network address for the Veritas Backup Reporter server and Web Engine. Do not use 'localhost'. This should be a fully qualified domain name or an IP address that other machines can use: (installsystem) installsystem.subdomain.Veritas.com
■ Press Enter to accept the default port (8181) for connections to the Web Engine, or type an alternate port number, and then press Enter.
Please enter a port for the Symantec Web Server, or
■ Type the name or IP address of an SMTP server host to use for emailing reports and press Enter.
Enter the name or IP address of an SMTP server to use for emailing reports: (localhost) smtp.Veritas.com Installing, uninstalling, and upgrading Veritas Backup Reporter 43 Installing Veritas Backup Reporter
4 Select any of the following options to configure AT:
If you have an existing VxAT setup in your environment then you can configure VBR VxAT to point to an existing root broker. Do you want to configure VBR VxAT to point to an existing root broker? [y,n,q] (n)
Note: If you are upgrading to Veritas Backup Reporter 6.5 you can choose to retain the existing AT configuration.
Before configuring AT, refer to the following section: “About AT configuration scenarios in Veritas Backup Reporter 6.5” on page 37.
■ Select n if you want to configure Symantec Product Authentication Service (AT) server on the Veritas Backup Reporter Management Server host. The management server host works in the Root+Authentication Broker mode. In this case, you do not need to enter AT server (root) host details, such as root host or root port, as these details are same as of the management server host.
■ Enter y to point to the existing root broker and specify the following information.
■ Root broker machine name
■ Remote user name
■ Domain name
■ Password of the above user
■ Root hash code or root hash file name as follows:
Do you want to enter Root hash directly. No option will ask you the root hash file location [y,n,q] (y)
Enter y to enter root hash code. Enter n to enter root hash file name
5 If you are installing the Veritas Backup Reporter Management Server, choose whether to configure the agent to report to a Veritas Backup Reporter Management Server host at this time by doing the following:
■ Type y and press Enter.
■ Type the name of the Veritas Backup Reporter Management Server host and press Enter. Otherwise, type n and press Enter. 44 Installing, uninstalling, and upgrading Veritas Backup Reporter Installing Veritas Backup Reporter
The host on which you are installing the agent must have network access to the Veritas Backup Reporter Management Server host you specify. It is best to specify the Veritas Backup Reporter Management Server host using its fully qualified domain name or IP address. 6 Review the installation options you selected. 7 Type y and press Enter to confirm the selection and continue.
8 Type n and press Enter to repeat the configuration steps and revise your selection. The next series of prompts enable you to confirm your selections and to continue the installation after the script performs its pre-installation checks. After the script finishes installing the queued components, it prompts you to start Veritas Backup Reporter components. To complete Veritas Backup Reporter component installation 1 After the initial system check completes, press Enter to continue. 2 Review the list of packages to be installed and press Enter to continue. The Install Script checks the system for Veritas Backup Reporter components, dependencies, and required patches. If a required patch is not found on the system, the script displays a list of the missing patches and a prompt asking whether you want to continue the installation. It is recommended that you cancel the installation and install the patches before you install Veritas Backup Reporter components. 3 After the installation requirements check succeeds, press Enter to continue. The Install Script installs the Veritas Backup Reporter component packages. 4 After all the packages are installed, press Enter to continue. If the installed components require manual configuration, the Install Script displays information on how to perform the configuration. 5 Press Enter to continue. The Install Script performs any automatic configuration that the installed components require. 6 Press Enter to continue. 7 Do one of the following:
■ Type y and press Enter to start Veritas Backup Reporter processes.
■ Type n and press Enter if you want to manually start the processes later. The Install Script displays a summary of the installation, including the location of the installation log files. Installing, uninstalling, and upgrading Veritas Backup Reporter 45 Installing Veritas Backup Reporter
Locating installation or uninstallation log directory data on Solaris The installation or uninstallation logs for Solaris can be found at the following locations on the Server:
Installation Logs /var/tmp/installvbr
Uninstallation Logs /var/tmp/uninstallvbr
where
◆ Type the following commands to find the latest installation/uninstallation log directory for the Veritas Backup Reporter Management Server:
cd /var/tmp
ls -ltrd *installvbr* The latest installation or uninstallation directory logs are at the bottom of the list. There are multiple log files within that directory. In case you want to submit the installation or uninstallation logs to Symantec technical support team, send the .tar and .zip and all other files in the installation or uninstallation log directory.
Installing Veritas Backup Reporter on Windows Use the Install Wizard to install Veritas Backup Reporter on a Windows host. The wizard resides at the top level of the Veritas Backup Reporter 6.5 product CD. The install comprises the following phases:
■ Selecting components to install
■ Configuring components in the install queue
■ Installing the component.
Note: If you do not have version 1.1 or later of the Windows Installer on your Windows host, Veritas Backup Reporter components do not install properly. 46 Installing, uninstalling, and upgrading Veritas Backup Reporter Installing Veritas Backup Reporter
To install the Windows installer 1 Exit the wizard now and install the Windows Installer. 2 If the Windows Installer is already installed, test its integrity by starting and stopping it from the Windows Services console. The Windows Installer is available for download from the Microsoft Web site: http://msdn.microsoft.com/downloads/ To install Veritas Backup Reporter on Windows 1 Log on to the target host with administrator privileges. 2 Insert the appropriate Veritas Backup Reporter 6.5 product CD in the CD-ROM drive. 3 If autorun is enabled, the Veritas Backup Reporter Install Wizard appears. You can select to install Veritas Backup Reporter on Windows. 4 On the Start menu, click Run. 5 Type the following in the Open file text box and press Enter:
12 Click Next. 13 Select a file for CORBA Server logs. The next series of prompts in the Veritas Backup Reporter Install Wizard collects configuration information for the components in the install queue. The steps you need to complete may vary, depending on which components are queued for installation. To configure components in the install queue 1 If you are installing the Veritas Backup Reporter Management Server, in the Host text box, type the name of the host running the Veritas Backup Reporter Management Server. 2 If you are installing the Veritas Backup Reporter Agent, do the following:
■ In the Host text box, type the name of the host running the Veritas Backup Reporter Management Server. If the Veritas Backup Reporter Management Server is running on the same host where you are installing the agent, use the default value Localhost.
■ Optionally, in the Port text box, type an alternate port for the agent to management server connection (default 1556). 3 Type 8181, the default port for the Veritas Backup Reporter Web Engine, or the alternate port in the Port text box. 4 Click Change to select the directory for the Veritas Backup Reporter Agent spooler. The spooler resides on the agent host and can hold the backup data up to its maximum memory usage. The spooler data then sequentially transfers to the Veritas Backup Reporter Management Server.
The default directory for the spooler is C:\Program Files\Symantec\Veritas Backup Reporter\Agent\Data. 5 Type address of the SMTP mail server. 48 Installing, uninstalling, and upgrading Veritas Backup Reporter Installing Veritas Backup Reporter
6 On the Authentication Settings screen, select any of the options available to configure AT. Before configuring AT, refer to the following: “About AT configuration scenarios in Veritas Backup Reporter 6.5” on page 37.
Note: If you are upgrading to Veritas Backup Reporter 6.5 you have an additional option to select - Existing Configuration. Select this option to retain the existing AT configuration.
Local Root Broker Select this option if you want to configure Symantec Product Authentication Service (AT) server on the Veritas Backup Reporter Management Server host. The management server host works in the Root+Authentication Broker mode. In this case, you do not need to enter AT server (root) host details, such as root host or root port, as these details are same as of the management server host.
Remote Root Select this option if you want to configure AT Authentication Broker Broker on the Veritas Backup Reporter Management Server host and you want to point to the AT root that is present on a different host. The management server host works in the Authentication Broker mode. Configure the management server host for the AT root by entering the following details: Root host name - Enter the AT root host name Root port number - Enter the AT port number Identity - Enter the principal user name Password - Enter the password of the prinicipal user account Domain - Enter the root domain name of the AT root host. Root hash file - Enter the root hash file name that you have copied from the AT root Check this box to use root hash code instead of root hash file
7 Click Next when you finish configuring these options. The next series of prompts in the Veritas Backup Reporter Install Wizard are primarily confirmation prompts to continue the installation after the Install Wizard performs its pre-installation checks. Installing, uninstalling, and upgrading Veritas Backup Reporter 49 Installing Veritas Backup Reporter
To complete Veritas Backup Reporter component installation 1 Review the installation settings. 2 If they are correct, click Next to begin the installation. 3 If you want to view a PDF of the Veritas Backup Reporter Release Notes, check the check box on the wizard’s closing panel before closing the Install Wizard. Read the Veritas Backup Reporter release Notes to find updates that are not contained in the user documentation. You can download a free copy of Adobe Reader at following URL: http://www.adobe.com 4 Click Finish to close the Install Wizard. 5 Reboot your system.
Locating installation or uninstallation logs Windows You can locate the installation and uninstallation log for the Veritas Backup Reporter Management Server on Windows at the following location:
%ALLUSERSPROFILE%\Application Data\Symantec\VeritasBackupReporter\VeritasBackupReporter.log On most systems, the %ALLUSERSPROFILE% directory is as follows:
C:\Documents and Settings\All Users The Application Data directory is a hidden directory. To view the hidden Application Data directory from Windows Explorer
◆ Select Tools > Folder Options > View and click the option for displaying hidden files and folders. The installation log file increases in size with each installation or uninstallation, so the installation and uninstallation logs contain all the required log information for your system. When submitting the installation or uninstallation logs to Symantec technical support, zip all the files contained in the installation or uninstallation log directory and send the files to the appropriate Symantec contact.
Resolving agent authentication failures manually on Solaris and Windows If the Veritas Backup Reporter Agent authentication fails on Solaris or Windows, use the following procedures to manually resolving agent authentication failures. 50 Installing, uninstalling, and upgrading Veritas Backup Reporter Installing Veritas Backup Reporter
If the Veritas Backup Reporter Agent is cannot connect to the Veritas Backup Reporter Management Server, a message such as the following may appear in the logs:
Authentication failed The user or password are not valid in the given domain. Domain = cc_users@myServer User = admin
To manually resolve agent authentication failures on a Solaris system
◆ Run the following command:
/opt/VRTSccsva/bin/agentauth -server
\Program Files\Symantec\Veritas Backup Reporter\Agent\bin 4 Type the following command and press Enter:
agentauth.exe -server
The agentauth.exe command can fail for a number of reasons. Two of the most common reasons for the agentauth.exe command to fail are as follows:
■ The Security Dynamic Link Libraries (DLLs) are not in the PATH. The workaround for this is to run the following commands:
■ cd \Program Files\Veritas\Security\Authentication\bin
■ "\Program Files\Symantec\Veritas Backup Reporter\Agent\bin\agentauth.exe" -server
■ The management server cannot be contacted. Ensure that the Veritas Backup Reporter Management Server and Authentication Service are running and can be reached on ports 1556 and 2821, respectively. Installing, uninstalling, and upgrading Veritas Backup Reporter 51 Installing Veritas Backup Reporter
Note: Further documentation on the agentauth command is available in the Veritas Backup Reporter administrator's Guide.
5 Restart the agent service.
Verifying that Veritas Backup Reporter is running properly After installing Veritas Backup Reporter on either UNIX or Windows, perform a check to verify that Veritas Backup Reporter is running properly. To verify that Veritas Backup Reporter is running properly 1 Go to http://
■ Go to Settings > Global Settings > Agent Configuration. The Veritas Backup Reporter Agent should appear. If an agent does not appear, do not click Create. Instead, troubleshoot the problem by checking that you correctly configured the ports.
Installing and removing the Veritas Backup Reporter demo database on Windows You can install the Veritas Backup Reporter Demo on Windows hosts. The demo populates the Veritas Backup Reporter database with r ich sample data containing instances of many types of discovered devices and applications. It thus enables you to view an example of a fully installed Veritas Backup Reporter environment in which you can test product functionality and generate reports. 52 Installing, uninstalling, and upgrading Veritas Backup Reporter Installing Veritas Backup Reporter
Note: You can install the demo after you install the full product. During the Veritas Backup Reporter Demo install, your current Veritas Backup Reporter environment is saved. This lets you return your install to its pre-demo configuration. If you installed Veritas Backup Reporter to the default location, your pre-demo configuration is saved to \Program Files\Symantec\Veritas Backup Reporter\DB\Data.
To install the Veritas Backup Reporter demo database on Windows 1 Log on to the Veritas Backup Reporter Management Service host as a user with administrator privileges. 2 Insert the appropriate Veritas Backup Reporter product CD in the CD-ROM drive. 3 Browse the CD and copy the Veritas Backup ReporterDemo directory and Veritas Backup ReporterDemo.vbs and Veritas Backup ReporterProduction.vbs files to the host’s hard drive. This host may or may not be the same host as the Veritas Backup Reporter Web Engine host.
The Veritas Backup ReporterDemo.vbs and Veritas Backup ReporterProduction.vbs files must reside at the same directory level as the Veritas Backup ReporterDemo directory. 4 At the Windows command prompt, change to the directory where you copied the directory and files and run the Veritas Backup Reporter Demo script by using one of the following methods:
Non-interactive At a command prompt, run cscript ccdemo.vbs. mode All script messages appear within the command window. (Recommended)
Interactive (GUI) At a command prompt, run ccdemo.vbs. mode In this mode, you have to acknowledge the prompts that appear.
5 To view backup reports that provide data for a specific time frame (for example, last 24 hours or last week), do the following:
■ At the Windows command prompt, change to the Veritas Backup Reporter Management Server utilities directory: cd \Program Files\Symantec\Veritas Backup Reporter\Server\util
■ Run SampleDBUpdate.bat. Installing, uninstalling, and upgrading Veritas Backup Reporter 53 Upgrading Veritas Backup Reporter
Run this file in advance of a demo so that your reports contain data for the specified periods on which you want to report. To return your Veritas Backup Reporter installation to its pre-demo state on Windows 1 Log on to the Veritas Backup Reporter Management Server host with administrator privileges. 2 Run the script to return your environment to production (pre-demo) mode, using one of the following methods:
Non-interactive mode At a command prompt, run cscript Veritas Backup ReporterProduction.vbs.
All script messages appear within the command window.
Interactive (GUI) mode At a command prompt, run Veritas Backup ReporterProduction.vbs.
In this mode, you have to acknowledge the prompts that appear.
Upgrading Veritas Backup Reporter Veritas Backup Reporter 6.5 supports direct upgrades from CommandCentral Service 4.2, Veritas Backup Reporter 6.0, and 6.2. On Solaris, the install script handles the upgrade from 4.2, 6.0, or 6.2 Veritas Backup Reporter Management Server automatically. The script also automatically upgrades 4.2, 6.0, or 6.2 versions of the Veritas Backup Reporter Agent and Java View Builder. On Windows, the Veritas Backup Reporter Install Wizard handles the upgrade of all 4.2, 6.0. or 6.2 components automatically.
Note: Veritas Backup Reporter 6.5 does not support automatic Veritas Backup Reporter Agents upgrade. When you upgrade your Veritas Backup Reporter Management Server to 6.5, you must also upgrade Veritas Backup Reporter Agents to 6.5.
Upgrading to Veritas Backup Reporter 6.5 components on Solaris On Solaris, the 6.5 Install Script detects the presence of 4.2, 6.0, or 6.2 components and guides you through the upgrade to 6.5. 54 Installing, uninstalling, and upgrading Veritas Backup Reporter Upgrading Veritas Backup Reporter
To upgrade to Veritas Backup Reporter 6.5 components on Solaris
1 Open a UNIX console and log in as root on the target host. 2 Mount the appropriate Veritas Backup Reporter 6.5 product CD for the components you want to upgrade. 3 Type the following command and press Enter:
./installvbr The Veritas Backup Reporter Install Script detects 4.2, 6.0, or 6.2 components and prompts you to confirm your choice to upgrade.
4 Type y and press Enter. Veritas Backup Reporter installation files are backed up in the following default directory:
/var/Veritas/ccs_save 5 You can create a backup directory other than the default (/var/Veritas/ccs_save) by creating a symbolic link that the Veritas Backup Reporter installer can access by typing the following commands:
mkdir /
ln -s /
The /var/Veritas/ccs_save directory may already exist from a previous upgrade to 4.2. If the /var/Veritas/ccs_save directory already exists, move the directory by typing the following commands:
mv /var/Veritas/ccs_save /
ln -s /
9 Type n and press Enter to return to the component list and revise your selection. 10 After making your upgrade selections, the Install Script guides you through the same steps you follow to configure and complete a new Veritas Backup Reporter 6.5 component installation. Refer to the following procedures to configure and complete the upgrade: “To configure components in the install queue” on page 42. “To complete Veritas Backup Reporter component installation” on page 44. The install script displays a summary of the installation, including the location of the installation log files. 11 Confirm that the upgrade is successful as follows:
Solaris ■ Veritas Backup Reporter Management Server: # pkginfo –l VRTSccsvs | grep VERSION ■ Agent: # pkginfo –l VRTSccsva | grep VERSION ■ Java View Builder: # pkginfo -l VRTSccsvb | grep VERSION
Upgrading the database manually on Solaris and Windows While upgrading to Veritas Backup Reporter 6.5, you may encounter a database upgrade failure. In such case, you must upgrade the database manually. The following direct upgrade paths are supported:
■ 4.2 FP1 with or without hot fixes
■ 6.0 GA
■ 6.0 MP1a
■ 6.2 GA
■ 6.2 MP1, MP2, and MP3 with or without EEBs
Note: To upgrade to Veritas Backup Reporter 6.5 on Solaris in cluster mode, refer to the Veritas Backup Reporter Clustering Guide.
To manually upgrade to Veritas Backup Reporter 6.5 database on Solaris 1 Stop the database server using credential of a root user. 2 Run the following commands: 56 Installing, uninstalling, and upgrading Veritas Backup Reporter Upgrading Veritas Backup Reporter
■ cd /opt/VRTSdbms3
■ ./vxdbms_setenv.sh Alternatively, you can run the chmod +x ./vxdbms_setenv.sh command.
■ export VXDBMS_HOME=/opt/VRTSdbms3
■ cd bin
■ ./vxdbms_start_db.pl VERITAS_DBMS3_hostname -stop ccsvc -force If the above command throws an error, you can stop the database using the following commands:
■ ps –ef | grep dbsrv9
■ kill -9 processid Where “processid” is the identification number of the above process 3 Restore the backed up database from CommandCentral Service 4.2 installation. The backup location on Solaris is as follows: /var/VERITAS/ccs_save/CC_DB.
■ Copy the following files from the above location to /var/VERITAS/ccs_data: vxcc.db, vxdmbulk.db, and vxcc.log (if it exists).
■ If you are upgrading the database from the versions prior to Veritas Backup Reporter 6.0, rename vxcc.db to ccsvc.db and skip this step.
4 Restart the database service using the following commands:
■ cd /opt/VRTSdbms3/bin
■ ./vxdbms_start_db.pl VERITAS_DBMS3_hostname /var/VERITAS/ccs_data/ccsvc.db Installing, uninstalling, and upgrading Veritas Backup Reporter 57 Upgrading Veritas Backup Reporter
5 Navigate to the
During the VxAM upgrade process, the VxAMUpgrade.log file is created, which is used to identify failures, if any.
Note: Retain the VxAMUpgrade.log file for further use.
6 After successful upgrade of the Veritas Alert Manager, run the following command to upgrage the database: /opt/VRTSccsvs/bin/dbupgrade -f dbupgrade.log
During the database upgrade process, the dbupgrade.log is created, which is used to identify failures, if any.
Retain the dbupgrade.log file for further use. See “Locating installation or uninstallation log directory data on Solaris” on page 45.. To manually upgrade to Veritas Backup Reporter 6.5 database on Windows 1 Go to Start > Run > services.msc
2 Locate the VERITAS_DBMS3_hostname service. Where “hostname” is the name of the server host 3 Right-click the service name and click Stop. 4 Restore the backed up database from CommandCentral Service 4.2 installation.
■ To identify the backup location, examine the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Veritas Backup Reporter\Saved Data.
■ Copy the following files from the above location to %Veritas Backup ReporterInstallDir%\DB\dat: vxcc.db, vxdmbulk.db, and vxcc.log (if exists).
■ If you are upgrading the database from the versions prior to Veritas Backup Reporter 6.0, rename vxcc.db to ccsvc.dband skip this step.
5 Restart the database service. 58 Installing, uninstalling, and upgrading Veritas Backup Reporter Upgrading Veritas Backup Reporter
6 From command prompt, navigate to the [INSTALLDIR]\Veritas Backup Reporter\VxAM\Install\db\distribute directory and run the following command to upgrade the Veritas Alert Manager (VxAM): %Program Files%\VERITAS\VxDBMS3\Win32\dbisql.exe -q -nogui -dataSource VERITAS_DBMS3_hostname -c "uid=dba;pwd=dbpassword;ENG=VERITAS_DBMS3_hostname;dbn=ccsvc;astart=no;links=all" read .\VxAMUpgrade_ASA.sql > VxAMUpgrade.log 2>&1.
The default value of [INSTALLDIR] is %Program Files%\Symantec\. This can be configured at installation time. Current value of [INSTALLDIR] can be found from the registry value HKEY_LOCAL_MACHINE\Software\Symantec\Veritas Backup Reporter\Server\InstallDir.
During the VxAM upgrade process, the VxAMUpgrade.log file is created, which is used to identify failures, if any. Replace “dbpassword” with correct password in case of VxAM upgrade.
Note: Retain the VxAMUpgrade.log file for further use.
7 After successful upgrade of the Veritas Alert Manager, run the following command: [INSTALLDIR]Veritas Backup Reporter\Server\util\dbupgrade.exe" -logallusers -lib [INSTALLDIR]Veritas Backup Reporter\Server\lib.
The default value of [INSTALLDIR] is %Programfiles%\Symantec\. This can be configured at installation time. Current value of [INSTALLDIR] can be found from the registry value HKEY_LOCAL_MACHINE\Software\Symantec\Veritas Backup Reporter\Server\InstallDir. This upgrades the database.
During the database upgrade process, the dbupgrade.log is created, which is used to identify failures, if any.
Retain the dbupgrade.log file for further use. See “Locating installation or uninstallation logs Windows” on page 49.
Identifying the version of .jar files While upgrading to Veritas Backup Reporter 6.5, several .jar files are replaced with new patches. However, it is difficult to identify which .jar files have been replaced with the new ones, as the file names do not contain version numbers. Installing, uninstalling, and upgrading Veritas Backup Reporter 59 Upgrading Veritas Backup Reporter
To identify version numbers of .jar files 1 Extract a .jar file using an archiving tool (for example, Winzip on Windows or jar tool on Solaris). 2 Open META-INF/MANIFEST.MF file within the .jar file.
The META-INF/MANIFEST.MF file includes Module Vendor, Module Name, and Module Version. For example:
■ Module-Vendor: Symantec Software - application vendor
■ Module-Name: ccsvc-server-core - module name
■ Module-Version: 6.5.16.17 - version of module deployed
Modifying Veritas Backup Reporter on Solaris Use the Install Script, which resides at the top level of the product CD, to modify existing Veritas Backup Reporter installations. To modify Veritas Backup Reporter on Solaris
1 Open a Solaris console and log in as root on the target host. 2 Mount the appropriate Veritas Backup Reporter 6.5 product CD for the components you want to install. 3 If you are installing additional Veritas Backup Reporter components, type the following command and press Enter:
./installvbr 4 If you are altering the configuration of installed Veritas Backup Reporter components, do the following:
■ Type the following command and press Enter: ./installvbr -configure
■ Follow the prompts presented in the install script.
Modifying Veritas Backup Reporter on Windows Use the Install Wizard to modify Veritas Backup Reporter installations. The wizard resides at the top level of the Veritas Backup Reporter 6.5 product CD. 60 Installing, uninstalling, and upgrading Veritas Backup Reporter Uninstalling Veritas Backup Reporter on Solaris and Windows
To modify Veritas Backup Reporter on Windows 1 Log on to the target host as a user with administrator privileges. 2 Insert the appropriate Veritas Backup Reporter 6.5 product CD in the CD-ROM drive. If autorun is enabled, the Install Wizard appears and you can skip to 5. 3 On the Start menu, click Run. 4 In the Open text box, type the following and press Enter: D:\setup.exe where
■ Expand the branches in the component tree to display the components and utilities available to install.
■ For each component you want to install, select the component and click This feature will be installed from the context menu. The icon next to the component changes from an X to a drive icon, indicating that the component is in the install queue.
■ See “Installing Veritas Backup Reporter on Windows” on page 45.
7 If you are altering the configuration of installed Veritas Backup Reporter components, do the following:
■ See “Installing Veritas Backup Reporter on Windows” on page 45.
■ Follow the prompts presented in the wizard.
8 Reboot your system.
Uninstalling Veritas Backup Reporter on Solaris and Windows This section describes uninstallation procedures for Veritas Backup Reporter on Solaris and Windows.
Uninstalling Veritas Backup Reporter on Solaris Use the Uninstall Script, which resides in the root directory in the product CD, to uninstall Veritas Backup Reporter on a Solaris host. Installing, uninstalling, and upgrading Veritas Backup Reporter 61 Uninstalling Veritas Backup Reporter on Solaris and Windows
To uninstall Veritas Backup Reporter components on Solaris
1 Open a Solaris console and log in as root on the target host. 2 Change to the following directory:
/opt/VRTS/install 3 Type the following command and press Enter:
./uninstallvbr The Uninstall Script lists all components installed on the system. 4 To add a component to the uninstall queue, type the number of the component and press Enter. The label [UNINSTALL] appears next to the component to indicate that it is in the uninstall queue. Repeat this step for each component you want to uninstall. 5 To uninstall all the components, type the number that corresponds to the Select All option and press Enter. 6 To remove a selected component from the uninstall queue, type the component’s number again and press Enter. 7 When you finish adding components to the queue, type the number that corresponds to the Finished with selections option and press Enter. 8 Review the list of components in the uninstall queue. 9 Type y and press Enter to confirm the selection and continue.
10 Type n and press Enter to return to the component list and revise your selection. 11 If you are uninstalling the Veritas Backup Reporter Management Server, do the following:
■ Choose the data files you want to back up before uninstalling the Veritas Backup Reporter Management Server.
■ To add a file type to the backup queue, type its corresponding menu number and press Enter. The label [BACKUP] appears next to the file type to indicate that it is in the backup queue. Data files are backed up to the directory /var/Veritas/ccs_save.
■ When you finish adding files to the backup queue, type the number that corresponds to the Finished with selections option and press Enter.
■ Review the backup options you selected. 62 Installing, uninstalling, and upgrading Veritas Backup Reporter Uninstalling Veritas Backup Reporter on Solaris and Windows
■ Type y and press Enter to confirm the selection and continue.
■ Type n and press Enter to repeat the backup steps and revise your selection. The Uninstall Script backs up files in the backup queue. If you are backing up a large database, this may take a significant amount of time. 12 After the system uninstall requirements check succeeds, press Enter to continue. The Uninstall Script stops all processes and then uninstalls the component packages. When the uninstall is complete, it displays a summary of the uninstall, including the location of the uninstall log files. 13 Do one of the following:
■ Type y and press Enter to start the uninstall process.
■ Type n and press Enter to cancel the uninstall procedure.
Uninstalling Veritas Backup Reporter on Windows Use the Windows Add/Remove Programs utility to uninstall Veritas Backup Reporter on a Windows host. If you also have CommandCentral Storage components installed on the same host, and you do not want to remove them at the same time, use the Veritas Backup Reporter 6.5 product CD (original media) to remove Veritas Backup Reporter. This leaves CommandCentral Storage installed on the host. See the Veritas Backup Reporter Installation Guide. To uninstall Veritas Backup Reporter on Windows 1 Log on to the target host as a user with administrator privileges. 2 In the Windows Control Panel, click Add/Remove Programs. 3 Click Veritas Backup Reporter Suite and click Remove. 4 In the Welcome panel of the Uninstall Wizard, click Next to continue. 5 Review the list of components to be uninstalled. 6 Click Next to continue. 7 Clear the check boxes to uninstall Veritas Backup Reporter without saving its database and configuration files. The default is to save the database and configuration files. Installing, uninstalling, and upgrading Veritas Backup Reporter 63 Uninstalling Veritas Backup Reporter on Solaris and Windows
8 Click Change to change the location where the database and configuration files are saved. 9 Click Next to begin uninstalling Veritas Backup Reporter components. When you see the Veritas Backup Reporter Uninstall Wizard closing panel, you are finished uninstalling Veritas Backup Reporter components. 10 Click Finish to close the Veritas Backup Reporter Uninstall Wizard. 64 Installing, uninstalling, and upgrading Veritas Backup Reporter Uninstalling Veritas Backup Reporter on Solaris and Windows Chapter 4
Starting and stopping Veritas Backup Reporter Service
This chapter includes the following topics:
■ Starting and stopping the Veritas Backup Reporter Management Server on Solaris and Windows
■ Stopping and starting the Veritas Backup Reporter Agent on Solaris and Windows
Starting and stopping the Veritas Backup Reporter Management Server on Solaris and Windows By default, the Veritas Backup Reporter Management Server starts whenever you boot your Veritas Backup Reporter Management Server host. However, you can manually stop and restart the Veritas Backup Reporter Management Server. 66 Starting and stopping Veritas Backup Reporter Service Starting and stopping the Veritas Backup Reporter Management Server on Solaris and Windows
To stop and restart the Veritas Backup Reporter Management Server on Solaris 1 Open a Solaris console, and log on to the Veritas Backup Reporter Management Server host as root. 2 In the console, change to the Veritas Backup Reporter Management Server directory.
By default, this directory is: /opt/VRTSccsvs/bin For example:
cd /opt/VRTSccsvs/bin Veritas Backup Reporter (Veritas Backup Reporter) creates symbolic links to all its scripts and commands in the /opt/VRTS/bin directory at installation.
3 Add /opt/VRTS/bin to your host’s PATH environment variable to access the Veritas Backup Reporter scripts and commands from any directory on the host. 4 Shut down the Veritas Backup Reporter Management Server by typing the following command:
./vbrserver stop force
The vbrserver stop force command stops the Veritas Backup Reporter Management Server and its shared components, such as Symantec Product Authentication Service, Veritas Backup Reporter database, Alert Manager, and Licensing. Starting and stopping Veritas Backup Reporter Service 67 Starting and stopping the Veritas Backup Reporter Management Server on Solaris and Windows
5 To stop the Veritas Backup Reporter Management Server but not components that are shared among products, use the vbrserver stop command. After stopping the Veritas Backup Reporter Management Server, wait about 30 seconds before starting it again. This gives the operating system time to free up logical ports and other resources that the Veritas Backup Reporter Management Server may need upon restart. This command neither starts nor stops the Veritas Backup Reporter Agent. 6 Restart the Veritas Backup Reporter Management Server from the same directory by typing the following command:
./vbrserver start The start command starts the Veritas Backup Reporter Management Server and its components, including components shared with other Veritas products. By default, the Veritas Backup Reporter Management Server starts whenever you boot its host.
The command vbrserver start starts the Veritas Backup Reporter Management Server, its services, and the Veritas Backup Reporter database and loads data in the database. To stop and restart the Veritas Backup Reporter Management Server on Windows 1 Log on to the Veritas Backup Reporter Management Server host as an administrator or a user in the Administrators group. 2 Using the Windows Service Control Manager (SCM), to stop the following Veritas services in the order listed, right-click the service and click Stop.
Adaptive Server Anywhere (Sybase ASA) Symantec Private Branch Exchange Symantec Product Authentication Service Veritas Alert Manager Veritas Automation Server Symantec Web Server Veritas Common Login Service Veritas Backup Reporter Management Server Veritas Backup Reporter Agent
After stopping the Veritas Backup Reporter Management Server, wait about 30 seconds before starting it again. This gives the operating system time to free up logical ports and other resources that the Veritas Backup Reporter Management Server may need upon restart. 68 Starting and stopping Veritas Backup Reporter Service Stopping and starting the Veritas Backup Reporter Agent on Solaris and Windows
3 Alternatively, you can also use the following command to automatically stop Veritas services:
cd
Veritas Backup Reporter Management Server Veritas Backup Reporter Common Login Service Symantec Web Server VERITAS Automation Server VERITAS Alert Manager Symantec Product Authentication Service Symantec Private Branch Exchange Adaptive Server Anywhere (Sybase ASA)
5 Alternatively, you can also use the following command to automatically start the Veritas services.
cd
Stopping and starting the Veritas Backup Reporter Agent on Solaris and Windows By default, the Veritas Backup Reporter Agent starts whenever you boot your agent host. To stop or start the agent on Solaris, you can use the startup and shutdown script, Veritas Backup Reporteragent. If you have administrator-level rights on your Windows hosts, use the Windows Services application to stop or start the Veritas Backup Reporter Agent. Starting and stopping Veritas Backup Reporter Service 69 Stopping and starting the Veritas Backup Reporter Agent on Solaris and Windows
To stop and restart the Veritas Backup Reporter Agent on Solaris
1 Open a UNIX console, and log on to the agent host as root. 2 In the console, change to the agent directory. By default, this directory is: /opt/VRTSccsva/bin For example:
cd /opt/VRTSccsva/bin Veritas Backup Reporter creates symbolic links to all its scripts and commands in the /opt/VRTS/bin directory at installation.
3 Add /opt/VRTS/bin to your host’s PATH environment variable to access the Veritas Backup Reporter scripts and commands from any directory on the host. 4 Shut down the agent by typing the following command:
./vbragent stop After stopping the agent, wait about 30 seconds before starting it again. This gives the operating system time to free up logical ports and other resources that the agent may need upon restart. 5 Restart the agent from the same directory by typing the following command:
./vbragent start To stop and start the Veritas Backup Reporter Agent on Windows 1 Log on to the Windows 2000 agent host as an administrator or a user in the Administrators group. 2 Using the Windows Service Control Manager (SCM), stop the Veritas Backup Reporter Agent service. 3 Right-click the service and then click Stop. After stopping the agent, wait about 30 seconds before starting it again. This gives the operating system time to free up logical ports and other resources that the agent may need upon restart. 4 Restart the Veritas Backup Reporter Agent service. 5 Right-click the service and click Start. 6 Close the Windows Service Control Manager. 70 Starting and stopping Veritas Backup Reporter Service Stopping and starting the Veritas Backup Reporter Agent on Solaris and Windows Chapter 5
Configuring Veritas Backup Reporter service
This chapter includes the following topics:
■ Setting data retention policies
■ Configuring Veritas Backup Reporter Agent Modules
■ Configuring the SMTP Mail server for Veritas Backup Reporter for Solaris and Windows
■ Disabling error log collection on Veritas Backup Reporter Agents
■ About creating and importing object views in XML
Setting data retention policies Before you install and run the Veritas Backup Reporter Agent on any backup servers, you should configure data retention settings on the Veritas Backup Reporter Management Server. When the agent discovers the backup server logs for the first time, it collects a large amount of historical data, which it then passes to the Veritas Backup Reporter Management Server. However, the Veritas Backup Reporter Management Server immediately cleans out all data older than the default period for data retention. In the case of backup log data, the default retention period is short (3 days). To accommodate a larger amount of historical data from the agent’s initial discovery, you must change the default data retention settings before running the agent. 72 Configuring Veritas Backup Reporter service Configuring Veritas Backup Reporter Agent Modules
To configure data retention settings for the Veritas Backup Reporter Management Server 1 Connect to the Veritas Backup Reporter Management Server with administrator-level privileges. For instructions on how to start the console and connect to the Veritas Backup Reporter Management Server, see the Veritas Backup Reporter User’s Guide. 2 In the console navigation bar, click Settings > Global Settings. 3 In the console’s Administration page, click Data Retention. 4 In the Data Retention dialog box, edit the value in the Backup Log Data field and any other fields you want to modify. 5 Click Save.
Configuring Veritas Backup Reporter Agent Modules You can configure Veritas Backup Reporter Agent Modules on an agent host using the Veritas Backup Reporter console. To configure Veritas Backup Reporter Agent Modules 1 Connect to the Veritas Backup Reporter Management Server with administrator-level privileges. For instructions on how to start the console and connect to the Veritas Backup Reporter Management Server, see the Veritas Backup Reporter User’s Guide. 2 In the console navigation bar, click Settings > Global Settings. 3 In the console’s Administration page, click Agent Configuration. 4 In the table of Veritas Backup Reporter Agent hosts, select the agent whose discovery modules you want to configure. 5 In the Agent Configuration panel, use the options on the Agent Configuration panel to delete (disable) existing discovery modules, add (enable) new ones, or modify a module’s variable settings.
About the Veritas NetBackup PureDisk module Veritas Backup Reporter supports collection of data from Veritas NetBackup PureDisk. The collected data is stored in the Veritas Backup Reporter database, based on which you can generate reports. Veritas Backup Reporter can collect Job and Policy data types from a PureDisk server. PureDisk server and its components run on the PureDisk operating system (PDOS). The Single Instance Storage (SIS) or de-duplication technology of NetBackup Configuring Veritas Backup Reporter service 73 Configuring Veritas Backup Reporter Agent Modules
PureDisk is unique in storage and backup industry. PureDisk identifies files and data segments that contain identical data and treats them as a single instance of a file, which it backs up only once. This helps you to save storage space. Attributes of identical files, such as name and date of modification can vary. While backing up a file, PureDisk determines whether multiple instances of the file are present on hosts across the network, including remote hosts. By using the de-duplication technology, PureDisk stores only one instance of the file. You need to specify the following PureDisk module variable:
Product Version Veritas PureDisk version, 6.2 or 6.2.1
About Veritas NetBackup module variables Table 5-1 describes the required variables for the Veritas NetBackup module.
Table 5-1 Veritas NetBackup module variables
Module variable Description
EMM Server Host Enterprise Media Manager host name
Home Directory The home directory for the Veritas NetBackup installation.
Volume Manager Home The home directory for the Veritas Volume Manager installation.
Breakup Jobs Breaks up a job (using data from the NBU catalog) so that the size and backup file count have finer granularity. Enabling this option increases the load on the agent, the load on the master server, and the time it takes to gather and load data. This feature is most effective if you explicitly list multiple paths in your policy include lists in NetBackup.
Collection Method Specifies the collection method that the module uses. The valid collection method is: CLIcli.
The CLI method uses the bpdbjobs command to gather job data. 74 Configuring Veritas Backup Reporter service Configuring Veritas Backup Reporter Agent Modules
Table 5-1 Veritas NetBackup module variables (continued)
Module variable Description
Days Per Image Fetch Determines the number of calls to bpimagelist. bpimagelist is used to collect image data. Each round of collection data load may trigger multiple calls to bpimagelist. Days Per Image Fetch limits the amount of collection data used by bpimagelist. For example, if you load image data from three months ago to today, and you set the Days Per Image Fetch variable to 30 days, then bpimagelist is called three times with different time options: Example of Days Per Image Fetch time options:
■ 3 months ago to 2 months ago ■ 2 months ago to 1 month ago ■ 1 month ago to today
A default value of five years (1800 days) is sufficient for most users. Users with larger environments where bpimagelist does not successfully return the default can set this value lower. The drop-down list consists of the following values:
■ 1800 days (default) ■ 360 days ■ 180 days ■ 90 days ■ 30 days ■ 7 days
Library Capacity Library Capacity either enables or disables the collection of the slot count information, which is required for calculating the tape library capacity.
Role Informs the module how to collect media data. If the host is both a master server and a media server, then use Master. Configuring Veritas Backup Reporter service 75 Configuring Veritas Backup Reporter Agent Modules
Table 5-1 Veritas NetBackup module variables (continued)
Module variable Description
Skip Errors for Tape Drive Select Skip Errors for Non-configured Media Server to skip Usage errors that occur while collecting data from a non-configured Media Server and continue collecting data. Select Skip Errors for All Media Servers to skip errors that occur while collecting data from any Media Server, regardless of whether it is configured or not and continue collecting data. Select Do Not Skip Errors if you do not want to skip any errors. This terminates the data collection.
About the Veritas BackupExec module variables Table 5-2 describes the required variables for the Veritas BackupExec module.
Table 5-2 Veritas BackupExec module variables
Module variable Description
Home Directory The home directory for the Veritas BackupExec installation.
Password The password required to connect to database.
userName The user name required to connect to database.
Version The version of Veritas BackupExec.
About the EMC Legato Networker module variables Table 5-3 describes the required variables for the EMC Legato Networker module.
Table 5-3 EMC Legato Networker module variables
Module variable Description
Home Directory The home directory for the EMC Legato Networker installation. 76 Configuring Veritas Backup Reporter service Configuring Veritas Backup Reporter Agent Modules
Table 5-3 EMC Legato Networker module variables (continued)
Module variable Description
Messages File The directory path for the log file containing group-complete messages. This path may be absolute or relative to homeDirectory. The default file name is messages.
To increase the efficiency of the Networker module, configure Networker to create a log that contains only group complete messages, and point messagesFile to this log
mminfoBinary The directory path of the mminfo Command-Line Interface (CLI), absolute or relative to homeDirectory
mminfoFile Output of mminfo(Optional)
nsrAdminBinary The directory path of the nsradmin CLI, absolute or relative to homeDirectory
nsrFile Output of an nsradmin command (Optional)
The Veritas Backup Reporter console displays nsrResFile, nsrFile, and mminfoFile even though these variables are optional and should be set by advanced users only.
nsrResFile The Networker resource file to use instead of the default file used by nsradmin (Optional)
About the IBM Tivoli Storage Manager module variables Table 5-4 describes the required variables for the Tivoli Storage Manager module.
Table 5-4 IBM Tivoli Storage Manager module variables
Module variable Description
Home Directory The home directory for the Tivoli Storage Manager installation. (This variable can be left blank.)
TSM ID An administrator-level login used to connect to the Tivoli Storage Manager server. (The default is admin.)
TSM Password The password for the account (specified in tsmId) for connecting to the TSM server. (The default password is admin.) Configuring Veritas Backup Reporter service 77 Configuring the SMTP Mail server for Veritas Backup Reporter for Solaris and Windows
Table 5-4 IBM Tivoli Storage Manager module variables (continued)
Module variable Description
TSM Server Port (Windows only) The TCP port on the TSM server through which the module establishes a connection. The TSM Server Port has no effect on Solaris. The Solaris module uses only product host settings.
dsmConfig The path to the dsm.opt file.
dsmDir The path where files to be run dsmadmc reside.
dsmadmc Location The path of TSM administrative client (dsmadmc).
About the CommVault Galaxy & Backup agent module variables Table 5-5 describes the required variables for the CommVault Galaxy & Backup agent module.
Table 5-5 CommVault Galaxy & Backup agent module variables
Module variable Description
password The password required to connect to database.
port The optional port required for database connection.
username The username required to connect to database.
Configuring the SMTP Mail server for Veritas Backup Reporter for Solaris and Windows You need to change the SMTP Mail server you specified when installing Veritas Backup Reporter. The following procedures describe how to configure SMTP Mail on Solaris and Windows platforms. 78 Configuring Veritas Backup Reporter service Disabling error log collection on Veritas Backup Reporter Agents
To configure SMTP Mail on Solaris 1 Open a Solaris console and log on to the Veritas Backup Reporter Management Server host as root.
2 In the console, change to the /bin subdirectory in the Symantec Web server installation directory.
By default, the installation directory is: /opt/VRTSweb For example:
cd /opt/VRTSweb/bin 3 Type the following command and press Enter.
./webgui smtp setserver
By default, the installation directory is: C:\Program Files\VERITAS\VRTSweb For example:
C:\Program Files\VERITAS\VRTSweb 3 Type the following command and press Enter.
webgui smtp setserver serverName where
Disabling error log collection on Veritas Backup Reporter Agents The Veritas Backup Reporter Agent error logs require a large amount of storage space. If you do not want to retail the error logs, you can disable them using the Veritas Backup Reporter console. Configuring Veritas Backup Reporter service 79 About creating and importing object views in XML
To disable Veritas Backup Reporter Agent error log collection 1 In the navigation bar of the Veritas Backup Reporter console, click Settings > Global Settings. 2 In the console’s Administration page, click Agent Configuration. 3 Select the Veritas Backup Reporter Agent for which you want to disable error log collection. 4 In the Agent Log Configuration panel, click Off from the drop-down list in the Level field. 5 Click Save.
About creating and importing object views in XML You can use the console to create object views on the Veritas Backup Reporter Management Server. Alternatively, you can create XML files that describe the object views you want to create, which you can import into Veritas Backup Reporter. Veritas Backup Reporter provides an XML utility to import and export your XML files. This utility resides in the following locations on the Veritas Backup Reporter Management Server host:
■
■
Backing up and restoring Veritas Backup Reporter data
This chapter includes the following topics:
■ Backing up the Veritas Backup Reporter database
■ Restoring the Veritas Backup Reporter database
Backing up the Veritas Backup Reporter database Veritas Backup Reporter is shipped with a database backup script that performs backup of the database without interrupting its operations, which is referred to as hot backup. On Solaris as well as Windows platforms, the script overwrites existing database (db) files before backing up or restoring the database. The db files are as follows: ccsvc.db, vxdmbulk.db, and ccsvc.log. The script backs up or restores the ccsvc.log file (if it exists).
Note: Regular filesystem backups are not sufficient for backing up the Veritas Backup Reporter database. You must schedule periodic hot backups for the Veritas Backup Reporter database to avoid losing any important data. 82 Backing up and restoring Veritas Backup Reporter data Restoring the Veritas Backup Reporter database
To back up the Veritas Backup Reporter database 1 Log on to the Veritas Backup Reporter database server host in one of the following ways:
Solaris root
Windows As an administrator or user in the Administrator group
2 Open the Solaris console or Windows command prompt. 3 Run the backup script that is appropriate for your platform. Specify one of the following backup directories depending on your platform:
Solaris /opt/VRTSdbms3/bin/dbbackup /my_db_backup_dir
Windows C:\Program Files\VERITAS\VxDBMS3\Win32\DbBackup.bat C:\MyDbBackupFolder
The backup script creates ccsvc.db, vxdmbulk.db, and ccsvc.log (if it exists) in the backup directory that you specified.
Restoring the Veritas Backup Reporter database After you backup the database, you can restore it. On Solaris hosts, the restore operation automatically stops the database, restores the backup database files, and restarts the database. On Windows hosts, you issue a series of commands that stop the database, restore individual backup database files, and restart the database. On Solaris as well as Windows platforms, the script overwrites existing database (db) files before backing up or restoring the database. The db files are as follows: ccsvc.db, vxdmbulk.db, and ccsvc.log. The script backs up or restores the ccsvc.log file (if it exists). Backing up and restoring Veritas Backup Reporter data 83 Restoring the Veritas Backup Reporter database
To restore a backed up Veritas Backup Reporter database 1 On the management server whose backup data you want to restore, open a UNIX console or a Windows command prompt and log in as root (on UNIX) or as an administrator or user in the Administrators group (on Windows).
Solaris Open a Solaris console and then log in as root.
Windows Open a Windows command prompt and log in as an administrator or user in the Administrators group.
All the paths shown in the steps that follow are the default database install paths. These paths may different for your site if the database was installed anywhere other than the default location. 2 To stop all Veritas Backup Reporter processes, do one of the following:
Solaris Type the following command and press Enter.
/opt/VRTS/bin/vbrserver stop force
Windows Use the Windows Service Control Manager (SCM) to stop all Veritas Backup Reporter services. Alternatively, you can also use the following commands to automatically stop all Veritas Backup Reporter processes: cd
cscript vx_services_stop.vbs 84 Backing up and restoring Veritas Backup Reporter data Restoring the Veritas Backup Reporter database
3 To restore the backed up database, do one of the following:
Solaris Type the following command and press Enter.
/opt/VRTSccsvs/bin/dbbackup
Windows Type the following command and press Enter.
C:\Program Files\VERITAS\VxDBMS3\Win32\DbBackup.bat
where backupDir is the directory where the backed up database resides, and
If not used, vxcc_db_backup and DbBackup.bat restores to the default database directory:
Solaris /var/VERITAS/ccs_data
Windows C:\Program Files\Symantec\Veritas Backup Reporter\DB\Data
If you specified a non-default directory location, you must specify the restoreDiroption. The script prompts you with a message similar to the following:
WARNING: this operation will overwrite the active Veritas Backup Reporter data on this host. Do you wish to continue ? [y/n] (n) Backing up and restoring Veritas Backup Reporter data 85 Restoring the Veritas Backup Reporter database
4 To continue with the restore, type y.
vx_ccdb_backup and DbBackup.bat automatically stops and restarts the database. 5 To restart all Veritas Backup Reporter processes, do one of the following:
Solaris Type the following command and press Enter.
/opt/VRTS/bin/vbrserver
Windows Use the Windows Service Control Manager (SCM) to start all Veritas Backup Reporter services. Alternatively, you can also use the following commands to automatically start all Veritas Backup Reporter processes: cd
cscript vx_services_start.vbs 86 Backing up and restoring Veritas Backup Reporter data Restoring the Veritas Backup Reporter database Appendix A
Veritas Backup Reporter install packages
This appendix includes the following topics:
■ About Veritas Backup Reporter install packages for Solaris and Windows
■ Solaris packages installed with Veritas Backup Reporter components
About Veritas Backup Reporter install packages for Solaris and Windows The following sections list directories containing Veritas Backup Reporter install packages for Solaris and Windows. Table A-1 lists the directories containing Veritas Backup Reporter install packages for Solaris.
Table A-1 Veritas Backup Reporter install packages for Solaris (Solaris Server CD—pkgs)
Install package Description
VRTSbrsh Installable package of Veritas Shared Utilities
VRTSvlic.tar.gz Compressed package of Veritas License Utilities
VRTSdbms3.tar.gz Compressed package of Veritas Database Management Server
VRTSbram.tar.gz Compressed package of Veritas Alert Manager
VRTSccdb.tar.gz Compressed package of Veritas Backup Reporter database 88 Veritas Backup Reporter install packages About Veritas Backup Reporter install packages for Solaris and Windows
Table A-1 Veritas Backup Reporter install packages for Solaris (Solaris Server CD—pkgs) (continued)
Install package Description
VRTSicsco.tar.gz Compressed package of Veritas Infrastructure Core Services Common
VRTSpbx.tar.gz Compressed package of Symantec Private Branch Exchange
VRTSat.tar.gz Compressed package of Symantec Product Authentication Service
VRTSjre15.tar.gz Compressed package of Veritas Java Runtime Environment Redistribution
VRTSweb.tar.gz Compressed package of Veritas Java Web Server
VRTSccsvs.tar.gz Compressed package of Veritas Backup Reporter Management Server
VRTSccdc.tar.gz Compressed package of Veritas Backup Reporter documentation
VRTSccsva.tar.gz Compressed package of Veritas Backup Reporter Agent
VRTSbrdc.tar.gz Compressed package of Veritas Backup Reporter Java View Builder
Table A-2 lists the directories containing Veritas Backup Reporter install packages for Windows.
Table A-2 Veritas Backup Reporter install packages for Windows (Windows Server CD)
Install package Description
setup.exe Install utility for Veritas Backup Reporter components
Veritas Backup Installable package of the Veritas Backup Reporter Agent. Reporter Agent.msi
Veritas Backup Installable package of the Veritas Backup Reporter Java View Reporter View Builder. Builder.msi Veritas Backup Reporter install packages 89 Solaris packages installed with Veritas Backup Reporter components
Solaris packages installed with Veritas Backup Reporter components The following sections list Solaris packages that are installed with various Veritas Backup Reporter components. Table A-3 lists the Solaris packages that are installed with the Veritas Backup Reporter Management Server.
Table A-3 Solaris packages installed with Veritas Backup Reporter Management Server
Package Description Relocatable installed
VRTSbrsh Veritas Shared Utilities Yes
VRTSvlic Veritas License Utilities No
VRTSdbms3 Veritas Database Management No Server
VRTSbram Veritas Alert Manager Yes
VRTSccdb Veritas Backup Reporter database Yes
VRTSat Symantec Product Authentication No Service
VRTSjre15 Veritas Java Runtime Environment Yes Redistribution
VRTSweb Veritas Java Web Server No
VRTSccsvs Veritas Backup Reporter Yes Management Server
VRTSbrdc Veritas Backup Reporter Yes documentation
VRTSpbx Symantec Private Branch Exchange No
VRTSicsco Veritas Infrastructure Core No Services Common
Table A-4 lists the Solaris packages that are installed with the Veritas Backup Reporter Agent. 90 Veritas Backup Reporter install packages Solaris packages installed with Veritas Backup Reporter components
Table A-4 Solaris packages installed with Veritas Backup Reporter Agent
Package Description Relocatable installed
VRTSbrsh Veritas Shared Utilities Yes
VRTSat Symantec Product Authentication Service No
VRTSjre15 Veritas Java Runtime Environment Redistribution Yes
VRTSccsva Veritas Backup Reporter Agent Yes
Table A-5 lists the Solaris packages that are installed with the Veritas Backup Reporter Java View Builder.
Table A-5 Solaris packages installed with Veritas Backup Reporter Java View Builder
Package Description Relocatable installed
VRTSat Symantec Product Authentication Service No
VRTSjre15 Veritas Java Runtime Environment Redistribution Yes
VRTSccsvb Veritas Backup Reporter Java View Builder Yes
VRTSbrsh Veritas Shared Utilities Yes Index
Symbols F 37 firewalls ports 29 A Veritas Backup Reporter requirements 29 agent resolving authentication failures manually 49 H authentication failures hosts resolving manually 49 interoperability 25 See also hosts B HTTP 29 HTTPS 29 backing up Veritas Backup Reporter database 81 I C installation or uninstallation log directory data Solaris 45 communication protocols 29 installing configuration packages 87 Veritas Backup Reporter Veritas Backup Reporter typical 20 Solaris 40 configuring Windows 45 SMTP Mail server 77 Veritas Backup Reporter demo database 51 configuring Veritas Backup Reporter Agent Installing Veritas Backup Reporter 37 Modules 72 installvbr 40 CORBA 29 interoperability hosts 25 D data M setting data retention policies 71 memory requirements disabling Veritas Backup Reporter 27 error log collection 78 modifying Veritas Backup Reporter Agent Modules 72 Veritas Backup Reporter disk space requirements Solaris 59 Veritas Backup Reporter 27 Windows 59
E O enabling operating system requirements Veritas Backup Reporter Agent Modules 72 Veritas Backup Reporter 25 error log disabling collection 78 92 Index
P Solaris (continued) ports Veritas Backup Reporter Management Server 1556 29 (continued) 1885 29 stopping 66 25 29 starting 2821 29 Veritas Backup Reporter Agent 2993 29 Solaris 69 5431 29 Windows 69 60389 29 Veritas Backup Reporter Management Server 7806 29 Solaris 66 8181 29 Windows 67 8443 29 Veritas Backup Reporter services 67–68 8453 29 stopping changing VRTSweb HTTP port 32 Veritas Backup Reporter Agent firewalls 29 Solaris 69 protocols Windows 69 communication 29 Veritas Backup Reporter Management Server Solaris 66 R Windows 67 Veritas Backup Reporter services 67–68 requirements Symantec Product Authentication Service 38 disk space system resource resources Veritas Backup Reporter 27 Veritas Backup Reporter 25 firewalls Veritas Backup Reporter 29 Web browser 35 T restoring TCP/IP 29 Veritas Backup Reporter database 82 U S UDP 29 scripts uninstalling installvbr 40 Veritas Backup Reporter Veritas Backup Reporteragent 68 Solaris 60 Veritas Backup Reporterserver 65 Veritas Backup Reporter on Windows 62 SMTP 29 upgrading SMTP Mail server Veritas Backup Reporter Agent configuring 77 Solaris 53 Solaris Veritas Backup Reporter Management Server finding installation or uninstallation log Solaris 53 directory data 45 View Builder installing Solaris 53 Veritas Backup Reporter 40 Upgrading Veritas Backup Reporter 53 modifying Veritas Backup Reporter 59 V Veritas Backup Reporter Agent Veritas Backup Reporter starting 69 firewall requirements 29 stopping 69 installing Veritas Backup Reporter Management Server Solaris 40 starting 66 Windows 45 Index 93
Veritas Backup Reporter (continued) W modifying Web browser Solaris 59 requirements 35 Windows 59 Web browser requirements 35 requirements Windows disk space 27 installing sanity check after installing 51 Veritas Backup Reporter 45 starting services 67–68 Veritas Backup Reporter demo database 51 stopping services 67–68 modifying uninstalling Veritas Backup Reporter 59 Solaris 60 uninstalling Windows 62 Veritas Backup Reporter 62 Veritas Backup Reporter Agent Veritas Backup Reporter Agent modules starting 69 enabling and disabling 72 stopping 69 Solaris Veritas Backup Reporter Management Server starting 69 starting 67 stopping 69 stopping 67 upgrading 53 startup script 68 Windows starting 69 stopping 69 Veritas Backup Reporter database backing up 81 restoring 82 Veritas Backup Reporter demo 51 Veritas Backup Reporter demo database installing 51 Veritas Backup Reporter Management Server ports 29 Solaris starting 66 stopping 66 upgrading 53 Windows stopping 67 Veritas Backup Reporterserver 65 View Builder Solaris upgrading 53 VRTSccsta install package 87 VRTSccsts install package 87 VRTSob install package 87 VRTSweb HTTP port changing 32