Bmc Recovery Manager For Databases: Enterprise - Off

Transcript

BMC® Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Supporting BMC SQL-BackTrack® products version 6.5 BMC Recovery Manager for Databases version 6.5 BMC Recovery Manager for Databases on Microsoft Windows version 6.5 BMC Recovery Manager for Databases: Enterprise Policy Monitor version 2.9 April 2007 www.bmc.com Contacting BMC Software You can access the BMC Software website at http://www.bmc.com. From this website, you can obtain information about the company, its products, corporate offices, special events, and career opportunities. United States and Canada Address BMC SOFTWARE INC 2101 CITYWEST BLVD HOUSTON TX 77042-2827 USA Telephone 713 918 8800 or 800 841 2031 Fax (01) 713 918 8000 Fax 713 918 8000 Outside United States and Canada Telephone (01) 713 918 8800 Copyright March 5, 2007 BMC Software, Inc., as an unpublished work. All rights reserved. BMC Software, the BMC Software logos, and all other BMC Software product or service names are registered trademarks or trademarks of BMC Software, Inc. All other trademarks belong to their respective companies. BMC Software considers information included in this documentation to be proprietary and confidential. Your use of this information is subject to the terms and conditions of the applicable End User License Agreement for the product and the proprietary and restricted rights notices included in this documentation. Restricted rights legend U.S. Government Restricted Rights to Computer Software. UNPUBLISHED -- RIGHTS RESERVED UNDER THE COPYRIGHT LAWS OF THE UNITED STATES. Use, duplication, or disclosure of any data and computer software by the U.S. Government is subject to restrictions, as applicable, set forth in FAR Section 52.227-14, DFARS 252.227-7013, DFARS 252.227-7014, DFARS 252.227-7015, and DFARS 252.227-7025, as amended from time to time. Contractor/Manufacturer is BMC SOFTWARE INC, 2101 CITYWEST BLVD, HOUSTON TX 77042-2827, USA. Any contract notices should be sent to this address. Customer support You can obtain technical support by using the BMC Software Customer Support website or by contacting Customer Support by telephone or e-mail. To expedite your inquiry, see “Before contacting BMC.” Support website You can obtain technical support from BMC 24 hours a day, 7 days a week at http://www.bmc.com/support_home. From this website, you can ■ ■ ■ ■ ■ ■ ■ read overviews about support services and programs that BMC offers find the most current information about BMC products search a database for issues similar to yours and possible solutions order or download product documentation report an issue or ask a question subscribe to receive proactive e-mail alerts when new product notices are released find worldwide BMC support center locations and contact information, including e-mail addresses, fax numbers, and telephone numbers Support by telephone or e-mail In the United States and Canada, if you need technical support and do not have access to the web, call 800 537 1813 or send an e-mail message to [email protected]. Outside the United States and Canada, contact your local support center for assistance. Before contacting BMC Have the following information available so that Customer Support can begin working on your issue immediately: ■ product information — — — ■ product name product version (release number) license number and password (trial or permanent) operating system and environment information — — — — — machine type operating system type, version, and service pack or other maintenance level such as PUT or PTF system hardware configuration serial numbers related software (database, application, and communication) including type, version, and service pack or maintenance level ■ sequence of events leading to the issue ■ commands and options that you used ■ messages received (and the time and date that you received them) — — — product error messages messages from the operating system, such as file system full messages from related software 3 4 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Contents Chapter 1 Introduction to BMC Recovery Manager 13 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Features and benefits of the Enterprise Policy Monitor . . . . . . . . . . . . . . . . . . . . . . . . . Understanding the architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC SQL-BackTrack utility with BMC Recovery Manager services . . . . . . . . . . Enterprise Policy Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Policy hub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Key concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Metrics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Policies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How to use this product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 14 16 17 18 18 18 18 19 20 20 Chapter 2 23 Installing the BMC Recovery Manager components Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing BMC SQL-BackTrack with BMC Recovery Manager services. . . . . . . . . . . Installing and configuring the EPM and the policy hub . . . . . . . . . . . . . . . . . . . . . . . . Preinstallation considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the EPM and the policy hub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the EPM remote client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the demonstration data file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrading an EPM and policy hub installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the EPM-BSM integration component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uninstalling BMC Recovery Manager components . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing BMC Recovery Manager services from the database server host . . . . Removing the EPM and the policy hub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing the EPM remote client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 24 25 25 25 26 29 31 32 33 34 34 34 35 Chapter 3 37 Introducing the Enterprise Policy Monitor Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting the EPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting the EPM from a remote host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connecting to the policy hub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Registering a database server host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Data Sources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Navigating the EPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Contents 37 38 38 38 39 40 42 42 5 Accessing the Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Navigating the Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Printing the Help topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Chapter 4 Policy administration 45 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Prerequisites for using policy administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Policy administration tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Monitoring policy compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Chapter 5 Working with the policy hub 51 Configuring the policy hub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Backing up the policy hub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Validating and recovering the policy hub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Managing data expiry in the repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Other policy hub configuration parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Implementing policy hub security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Predefined roles and privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Configuring EPM for security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Typical security tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Sharing policy hub data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Exporting policy hub data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Importing policy hub data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Chapter 6 Integrating with BMC Atrium 67 BMC Atrium integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 BSM integration architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Installing BSM integration components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Configuring BSM integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Configuring the EPM to send policy events to BMC Impact Manager . . . . . . . . . 71 Enabling and disabling BSM events for a data source . . . . . . . . . . . . . . . . . . . . . . . 71 Creating a service model that includes data sources monitored by the EPM. . . . 72 Monitoring EPM policy events from the BMC Impact Explorer . . . . . . . . . . . . . . 73 EPM events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Chapter 7 Configuring e-mail notification 77 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Roadmap of e-mail notification configuration tasks. . . . . . . . . . . . . . . . . . . . . . . . . 77 How are e-mail notification messages triggered? . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Configuring the SMTP server and testing e-mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Managing contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Managing distribution lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Managing e-mail lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 E-mail notification states. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 6 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Chapter 8 Using BMC Recovery Manager in a clustered environment 87 Server clustering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Specifying a host name for a computer in a cluster . . . . . . . . . . . . . . . . . . . . . . . . . Displaying clustered servers as a group in the EPM . . . . . . . . . . . . . . . . . . . . . . . . Resolving a host registration by cluster name failure . . . . . . . . . . . . . . . . . . . . . . . Clustering in a RAC or failover environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting services during a node failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 88 89 89 91 92 Chapter 9 93 Troubleshooting Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Verifying installation of services on the database server host . . . . . . . . . . . . . . . . . . . 94 Resolving BMC Recovery Manager port conflicts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Displaying and changing port numbers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Displaying database server host port numbers examples. . . . . . . . . . . . . . . . . . . . 98 Stopping and starting the policy hub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Starting and stopping BMC Recovery Manager services in the database server host. . 100 Automatically restarting BMC Recovery Manager services . . . . . . . . . . . . . . . . . 101 Manually starting and stopping BMC Recovery Manager services . . . . . . . . . . 102 Manually migrating an existing data file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Troubleshooting database server host registration. . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Modifying data collection configuration parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Clearing the Java cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Resolving a Java out-of-memory error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Appendix A Installing third-party drivers for generating reports 111 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating an alias for the driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 111 112 112 Appendix B 115 Policy hub data reference Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Understanding the data model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Querying the policy hub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Attribute table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BackTrackInstall table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BackTrackInstall_DataSourceDetail table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DataModel table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DataSource table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DataSourceAttribute table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DataSourceDetail table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Host table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LicenseType table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Metric data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BackTrackConfig table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Contents 116 116 117 117 119 119 120 121 121 122 122 123 124 124 126 7 DataSourceTaskPhase table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 DataSourceTaskProperty table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 Job table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 JobType table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 Task data tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 TaskAlert table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 TaskMethod table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 TaskMode table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 TaskProperty table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 TaskScope table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 TaskStatus table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 TaskDataSource table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 Policy data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 BackupPolicyDetail table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 DataSourcePolicyHistory table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Policy table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 PolicyDetail table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 PolicyStatus table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 PolicyStatusHistory table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 RecoveryPolicyDetail table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 UserInfo table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 BackupExclusionParameter table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Appendix C BMC Recovery Manager reports 147 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 Generating BMC Recovery Manager reports from the console. . . . . . . . . . . . . . . . . . 148 Generating BMC Recovery Manager reports from the command line. . . . . . . . . . . . 150 epmreport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Report categories and types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 Policy reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 Compliance reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 Backup reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 Recovery reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Miscellaneous reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 Using custom attributes in reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 8 Glossary 177 Index 181 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Figures BMC Recovery Manager components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 BMC Recovery Manager installation task map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Available attributes for defining a backup policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Select Backup Exclusion Time Period dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Available attributes for defining a recovery policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 BSM integration process flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Example CSV import file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Relationship between e-mail list, failures, distribution list, and contact list . . . . . . . 83 Configuration data model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Metric data model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 Policy data model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Policy Change History report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 Policy Definition Summary report (page 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 Policy Definition Summary report (page 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 Policy Non-Compliance History report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 Status Performance Summary report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 Recoverability Chart report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 Total Database Size Graph report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Figures 9 10 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Tables Enterprise Policy Monitor features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Task-based guide to using BMC Recovery Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Policy tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 EPM parameters you can set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Policy hub configuration parameters: controlling automated policy hub backups . 53 Policy hub configuration parameters: controlling automated validation and recovery 56 Policy hub configuration parameters: managing data expiry . . . . . . . . . . . . . . . . . . . 58 Policy hub configuration parameters: controlling various functions . . . . . . . . . . . . . 59 User roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Policy hub configuration parameters: preparing for security . . . . . . . . . . . . . . . . . . . 61 Typical security tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 BSM integration components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 BSM integration tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 E-mail notification configuration tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 E-mail notification triggering events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Managing e-mail lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 E-mail notification states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Host name parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Options for the epmportconfig utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Parameters for automatic restart of SQL-BackTrack services on a managed node . 101 Database server host registration error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Configuration parameters for data collection on the database server host in $DTBASE/common/jboss/3.2.4/server/bmc/conf/ebrdc.cfg . . . . . . . . . . . . . . 105 Configuration parameters for data collection on the database server host in the $DTBASE//ebr/config/ebrdc.cfg file . . . . . . . . . . . . . . . . . . . . . . . 107 Attribute table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 BackTrackInstall table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 BackTrackInstall_DataSourceDetail table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 DataModel table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 DataSource table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 DataSourceAttribute table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 DataSourceDetail table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 Host table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 LicenseType table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 BackTrackConfig table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 DataSourceTaskPhase table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 DataSourceTaskProperty table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 Job table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 JobType table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 Tables 11 Task data tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 Task data table exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 TaskAlert table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 TaskMethod table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 TaskMode table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 TaskProperty table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 TaskScope table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 TaskStatus table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 TaskDataSource table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 BackupPolicyDetail table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 DataSourcePolicyHistory table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Policy table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 PolicyDetail table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 PolicyStatus table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 PolicyStatusHistory table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 RecoveryPolicyDetail table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 UserInfo table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 BackupExclusionParameter table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Required option for the epmreport command to create an identification file . . . . . 152 Required options for the epmreport command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 Optional options for the epmreport command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Example epmreport commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 Report categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 Report types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 Policy reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 Compliance reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 Backup reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 Recovery reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Backup and Recovery Status Performance Summary Report options . . . . . . . . . . . . 167 Miscellaneous reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 Custom attribute Summary Report options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 12 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Chapter 1 Introduction to BMC Recovery Manager 1 This chapter presents the following topics: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Features and benefits of the Enterprise Policy Monitor . . . . . . . . . . . . . . . . . . . . . . . . . Understanding the architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC SQL-BackTrack utility with BMC Recovery Manager services . . . . . . . . . . Enterprise Policy Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Policy hub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Key concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Metrics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Policies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How to use this product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 14 16 17 18 18 18 18 19 20 20 Overview In an environment where BMC SQL-BackTrack is installed and running on one or more hosts, the BMC Recovery Manager Enterprise Policy Monitor (EPM) enables you to monitor your BMC SQL-BackTrack backup and recovery activities and audit your backup and recovery practices from an enterprise-wide perspective. The EPM enables you to ■ monitor backup and recovery information for all managed data sources (including Oracle, Sybase, DB2 Universal Database [UDB], and Microsoft SQL Server data) from a single console window ■ define and assign audit policies so that you can easily identify data sources that are not complying with your organization’s backup and recovery requirements Chapter 1 Introduction to BMC Recovery Manager 13 Features and benefits of the Enterprise Policy Monitor ■ specify custom attributes to categorize your data sources and easily associate them with a particular DBA, location, customer, or application ■ view both current and historical backup and recovery information for an individual data source ■ generate summary, historical, and graphical trend reports For information about installing and configuring BMC Recovery Manager, see Chapter 2, “Installing the BMC Recovery Manager components” on page 23. Features and benefits of the Enterprise Policy Monitor The EPM provides monitoring and other features for all of your registered BMC SQL-BackTrack data sources. Table 1 on page 15 provides more information about the benefits of each feature. 14 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Features and benefits of the Enterprise Policy Monitor Table 1 Enterprise Policy Monitor features Enterprise Policy Monitor feature enterprise monitoring data source management and monitoring backup and recovery management personalized display Benefits ■ collects backup and recovery activity from numerous data sources, which can include different database types, operating systems, and storage environments ■ enables you to establish backup and recovery policies and monitor compliance to ensure that Service Level Objectives are met across the enterprise ■ enables you to view backup and recovery activity for a variety of database management systems in a single console window ■ enables you to establish a role-based security system to limit individual access to data source information ■ enables you to integrate with Business Service Management (BSM), so that you can push EPM policy events into the BSM Impact Manager application ■ provides detailed information for each data source on all registered database server hosts, including database type and version, operating system and version of the database server host, and BMC SQL-BackTrack version ■ provides current and historical backup and recovery information for each registered data source ■ enables you to associate e-mail lists with data sources so that backup, recovery, and policy failures trigger e-mail notification messages to specified distribution lists ■ enables you to delete data sources so that you do not have to monitor every data source on a registered database server host; deleting a data source also deletes its associated metric data ■ enables you to enable a deleted data source, which undeletes it ■ enables you to establish backup and recovery requirements for a specific data source or a group of data sources ■ displays an alert for each data source that does not meet the established requirements ■ enables you to customize the manner in which the EPM displays information about each data source ■ provides filtering, sorting, and preferences to refine the information displayed for each data source ■ provides custom attributes so you can categorize and group data sources according to attributes that you designate; you can include the custom attributes in reports Chapter 1 Introduction to BMC Recovery Manager 15 Understanding the architecture NOTE The PATROL® Knowledge Module® for BMC Recovery Manager enables a PATROL Agent to collect the same data source information described in Table 1 on page 15 and display it in a PATROL console. See PATROL for BMC Recovery Manager Getting Started for more information. Understanding the architecture BMC Recovery Manager has the following sets of components. To use all of the features described in “Features and benefits of the Enterprise Policy Monitor” on page 14, all of these component sets must be installed or configured. ■ ■ BMC SQL-BackTrack utility with BMC Recovery Manager services EPM and the policy hub Figure 1 on page 17 illustrates the components included with BMC Recovery Manager and the interaction among the components. 16 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Understanding the architecture Figure 1 BMC Recovery Manager components BMC SQL-BackTrack utility with BMC Recovery Manager services The BMC Recovery Manager services are automatically installed on the database server host when you install any BMC SQL-BackTrack utility that is version 5.0 or later. These BMC Recovery Manager services collect status and performance metrics from BMC SQL-BackTrack and send the metrics to the policy hub. Chapter 1 Introduction to BMC Recovery Manager 17 Key concepts Enterprise Policy Monitor The EPM is the client interface with which you can view all of the information gathered from data sources that have been registered with the EPM. To launch the EPM, see “Starting the EPM” on page 38. The EPM connects to the policy hub. Policy hub The policy hub stores the following information: ■ all of the information gathered from the data sources that have been registered with the EPM in a policy hub ■ policy information and custom attributes, that you define through the EPM The policy hub also enables communication between the EPM and BMC SQL-BackTrack by processing incoming EPM requests for information and returning the data to each client interface. Key concepts This section describes the basic concepts that will help you to effectively use BMC Recovery Manager. Data sources A data source is the database entity that represents the recoverable unit for a particular database management system (DBMS). This data source is the database for most DBMS types and a partition for DB2 UDB. Data sources reside on a database server host, are associated with a BMC SQL-BackTrack installation, and are monitored through BMC Recovery Manager services, as illustrated in Figure 1 on page 17. NOTE You do not have to monitor all data sources on a registered database server host. Through the EPM, you can delete any data sources that you do not want to monitor. You can also undelete a data source by enabling deleted data sources. See the Help for more information about deleting data sources. 18 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Key concepts Because BMC Recovery Manager supports a variety of DBMSs, you can monitor different database types, such as Sybase, Oracle, DB2 UDB, and SQL Server, simultaneously through the EPM. These databases can run on a variety of operating systems. To monitor data sources with BMC Recovery Manager, in the EPM you must first register the database server host on which they reside. See the Help for more information about registering database server hosts. (“Viewing Help” on page 42 explains how to access the Help.) Metrics In BMC Recovery Manager, metrics refers to status and performance information about managed data sources. BMC Recovery Manager services on the database server host collect and publish the metrics to the policy hub. The types of metrics include ■ backup metrics, such as the date and time of the last successful backup ■ recovery metrics, such as the date and time of the last successful recovery ■ component-specific metrics, such as the BMC SQL-BackTrack version, IP address of the database server host, and total size of the data source ■ measurements or evaluations, such as the number of blocks processed during a backup The policy hub stores these metrics according to a specific data model. See Appendix B, “Policy hub data reference” on page 115 for more information. NOTE The measurements and evaluations collected by the BMC Recovery Manager services on the database server host can vary from similar information stored in the logs for the BMC SQL-BackTrack utilities. For example, you might see a slight difference in the throughput rate, raw backup size, backup compression ratio, and other metrics such as the start time, end time, and elapsed time, reported in the EPM when compared to similar values in BMC SQL-BackTrack logs. The variance can be from 1 KB to 50 KB. Such discrepancies are due to the frequency at which the BMC Recovery Manager services collect information about a specific data source. Chapter 1 Introduction to BMC Recovery Manager 19 How to use this product Policies The EPM provides you with the ability to define policies that specify backup and recovery requirements for data sources. A policy is a set of rules. For example, you can define rules to create a policy to provide requirements for ■ ■ ■ how frequently a full, incremental, or logical backup is performed the maximum estimated time required to recover a data source time-range restrictions on when a backup will run After you have assigned policies to the data sources, the EPM starts to monitor policy compliance by comparing the specifications defined in the policy against the metric data that it collects from the BMC SQL-BackTrack installations for the data source. The status of this policy compliance is displayed in the EPM. If a data source fails to meet the requirements specified in the policy, a Failure icon in the Policy status column indicates the failure. The EPM also enables you to integrate with Business Service Management (BSM), so that you can push EPM policy events into the BMC Impact Manager application, and can use the BMC Impact Explorer to monitor these events. For more information about using policy administration, see Chapter 4, “Policy administration” on page 45. NOTE A policy does not cause the specified requirement to occur, but only indicates whether a database conforms to the guidelines provided in a policy. How to use this product Based on your role within the organization, you might use certain aspects of the BMC Recovery Manager solution to accomplish a specific set of goals. For example, your responsibility might be to ensure the recoverability of all data in the organization. Or, perhaps, your primary responsibility is to run or schedule database backups. “Task-based guide to using BMC Recovery Manager” on page 21 provides a task-based guide to show how you can use this product to accomplish typical goals that might be associated with your role. 20 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started How to use this product Table 2 Task-based guide to using BMC Recovery Manager (Part 1 of 2) Goal Required components Tasks run backups and recoveries on your database server BMC SQL-BackTrack utility Use the BMC SQL-BackTrack utility to initiate backup and recovery jobs. For instructions, see the user guide and reference manual for your BMC SQL-BackTrack utility. monitor backup and recovery All product components statuses from a GUI interface must be installed. 1. Launch the EPM. 2. Connect to the policy hub. 3. Register data sources with the EPM. See Chapter 3, “Introducing the Enterprise Policy Monitor” on page 37. track compliance with SLA objectives for backup and recovery All product components must be installed. 1. Launch the EPM. 2. Define policies that specify your SLA requirements. 3. Assign the policies to the appropriate data sources. 4. Monitor policy compliance in the EPM. 5. Generate reports as a record of compliance. See Chapter 4, “Policy administration” on page 45. audit backup and recovery objectives All product components must be installed. 1. Launch the EPM. 2. Define and assign policies for backup and recovery requirements. 3. Monitor backup and recovery statuses in the EPM. See Chapter 4, “Policy administration” on page 45. Chapter 1 Introduction to BMC Recovery Manager 21 How to use this product Table 2 Task-based guide to using BMC Recovery Manager (Part 2 of 2) Goal Required components set up policies that correspond to your organization’s disaster recovery plan for missioncritical data servers All product components must be installed. Tasks 1. Launch the EPM. 2. Define policies for mission-critical objectives and assign to the appropriate data sources. 3. Monitor policy status in the EPM. 4. Observe failure alerts in the EPM. See Chapter 4, “Policy administration” on page 45. set up BSM integration so that the EPM pushes the BSM events into the BMC Impact Manager application ■ All product components must be installed. ■ BSM integration components must be installed. 1. Launch the EPM. 2. Configure BSM integration. All product components set up e-mail notification so that e-mail messages are sent must be installed. to specified contacts when a backup, recovery, or policy failure occurs for a monitored data source See Chapter 6, “Integrating with BMC Atrium” on page 67. 1. Launch the EPM. 2. Configure e-mail notification. 3. Define contacts and distribution lists to receive e-mail notification messages. 4. Create e-mail lists that associate distribution lists with failure types. 5. Assign e-mail lists to monitored data sources so that e-mail notification messages are triggered when failures occur against the data sources. 6. Enable e-mail notification. See Chapter 7, “Configuring e-mail notification” on page 77. set up security features to limit user access to reports and menu functions All product components must be installed 1. Launch the EPM. 2. Create data sets. 3. Create user defined roles combining EPM roles and specified data sets. 4. Map user defined roles to individual users and to user groups. See “Implementing policy hub security” on page 60. 22 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Chapter 2 Installing the BMC Recovery Manager components 2 This chapter presents the following topics: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing BMC SQL-BackTrack with BMC Recovery Manager services. . . . . . . . . . . Installing and configuring the EPM and the policy hub . . . . . . . . . . . . . . . . . . . . . . . . Preinstallation considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the EPM and the policy hub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the EPM remote client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the demonstration data file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrading an EPM and policy hub installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the EPM-BSM integration component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uninstalling BMC Recovery Manager components . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uninstalling BMC Recovery Manager components . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing BMC Recovery Manager services from the database server host . . . . Removing the EPM and the policy hub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing the EPM remote client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 24 25 25 25 26 29 31 32 33 34 34 34 34 35 Overview This chapter presents information about installing the components necessary to take advantage of BMC Recovery Manager. The necessary components are described and illustrated in “Understanding the architecture” on page 16. If you have not already done so, read that information on page 16 before you begin the installation process. Figure 2 on page 24 provides an overview of the installation process and the tasks that you must perform to complete the installation of the BMC Recovery Manager components. The task map also lists the sections of this chapter that contain information about each task. Chapter 2 Installing the BMC Recovery Manager components 23 Installation requirements Figure 2 BMC Recovery Manager installation task map Install BMC SQL-BackTrack and BMC Recovery Manager services. 1 Installation begins. Install SQL-BackTrack on each database server host. “Installing BMC SQL-BackTrack with BMC Recovery Manager services” on page 25 Install and configure the EPM and the policy hub. Install and configure the EPM and the policy hub. yes 2 Do you want to use the EPM? “Installing and configuring the EPM and the policy hub” on page 25 no Installation ends. Installation requirements See the release notes for installation requirements for ■ ■ BMC SQL-BackTrack and the database server host EPM and policy hub host NOTE If you are installing the BMC Recovery Manager components in an environment with a firewall, the database server host and the policy hub host must be behind the same firewall. 24 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Installing BMC SQL-BackTrack with BMC Recovery Manager services Installing BMC SQL-BackTrack with BMC Recovery Manager services The BMC Recovery Manager services are automatically installed when you install BMC SQL-BackTrack, version 5.0 or later, on the database server host. For instructions for installing BMC SQL-BackTrack, see the installation guide for your BMC SQL-BackTrack utility. NOTE If you install a BMC SQL-BackTrack utility version 5.6 over another BMC SQL-BackTrack utility (such as BMC SQL-BackTrack for Oracle or BMC SQL-BackTrack for Sybase), your EPM components are upgraded automatically. No informational message is displayed. Installing and configuring the EPM and the policy hub You must install the EPM and the policy hub if you want to use BMC Recovery Manager to monitor and manage data sources. The policy hub stores all of the information gathered from the data sources that have been registered with the EPM. The EPM Report Command Utility is automatically installed when you install the policy hub. Using this utility, you can run BMC Recovery Manager reports. See Appendix C, “BMC Recovery Manager reports,” for information about this utility. Preinstallation considerations Consider the following information before installing the EPM and policy hub: ■ By default, the EPM and the policy hub are installed in the following directory on Windows: C:/Program Files/BMC Software/BMC Recovery Manager/Enterprise Policy Management By default, the EPM and the policy hub are installed in the following directory on Linux: opt\bmc\BMCRecoveryManager\EnterprisePolicyManagement Chapter 2 Installing the BMC Recovery Manager components 25 Installing and configuring the EPM and the policy hub During installation, you might choose to install the EPM and the policy hub in a different directory. This book uses the variable to represent the directory where the EPM and policy hub are installed. ■ Product components use TCP/IP connections to communicate. To use TCP/IP with a firewall, you must configure the firewall to support the TCP/IP protocol. See your firewall documentation for detailed information about using the firewall with the TCP/IP protocol. ■ The EPM communicates with the policy hub through a port number that is automatically assigned during the policy hub installation. To determine which port number the EPM uses to connect to the policy hub, open the EPM Configuration dialog box as described in “Configuring the policy hub” on page 51 and locate the JBoss port JNDI entry. You will need to know this port number when planning which ports to allow within your firewall. ■ The policy hub installation adds entries to the Microsoft Windows Registry at HKEY_LOCAL_MACHINE\SOFTWARE\BMC Software and HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services. ■ Installing multiple policy hub components on the same host is not supported. ■ If you are upgrading an existing installation, see “Upgrading an EPM and policy hub installation” on page 32 for instructions. Installing the EPM and the policy hub Use the following procedures to install the EPM and policy hub on a Microsoft Windows or a Linux platform. Before you begin Before you begin your installation of the EPM and policy hub, verify that the following prerequisites are met: 26 ■ The EPM and policy hub host must meet the requirements listed in the release notes. ■ If applicable to your environment, you have planned which ports to allow for within your firewall to enable communication from clients to the policy hub. ■ For Windows, you must be a member of the Administrators group to install the EPM and policy hub. ■ For Linux, you must have root authority to install the EPM and policy hub. BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Installing and configuring the EPM and the policy hub To install the EPM and policy hub on a Windows host 1 Insert the BMC Recovery Manager EPM Policy Hub CD into the CD drive on the Windows host. If the installation script does not automatically start when the CD is inserted into the drive, start the program by running one of the following files on the CD: ■ PolicyHub\setupwin32.exe for a Windows computer ■ PolicyHub/setuplinux.sh for a Linux computer 2 On the Welcome page, click Next. 3 On the License Agreement page, review the license agreement and click I accept the terms of the license agreement to accept the terms of the agreement. 4 On the Installation page, click Browse to choose an installation directory or click Next to use the following default installation path: C:/Program Files/BMC Software/BMC Recovery Manager/Enterprise Policy Management 5 On the Client port page, accept the default port number, or enter a port number, for communication between the local and remote clients. You can click Validate to validate whether the port number is available for communications. Click Next. 6 If BMC Recovery Manager detects a previous installation of the EPM Policy Hub you are prompted to choose whether to reuse the existing data repository. Choose one of the following actions: ■ ■ Upgrade the repository from the pre-2.9.00 version Install a new repository Click Next. 7 On the Summary Information page, click Install to continue installing the product. 8 On the second Summary Information page, record the URL for the remote installation if you want to install the client on a remote host. Then, click Finish to exit the installation script. Chapter 2 Installing the BMC Recovery Manager components 27 Installing and configuring the EPM and the policy hub NOTE ■ If the installation does not finish successfully, the installation program still creates the /_uninst directory and places the following file into that directory so that you can uninstall the EPM and policy hub: uninstaller.exe. ■ You must uninstall the EPM and policy hub before you attempt to install it again. See “Removing the EPM and the policy hub” on page 34. To install the EPM and policy hub on a Linux host 1 Insert the BMC Recovery Manager EPM Policy Hub CD into the CD drive on the Linux host. If the installation script does not start automatically, start the program by running the setuplinux.sh file on the CD. 2 On the Welcome page, click Next. 3 On the License Agreement page, review the license agreement and click I accept the terms of the license agreement to accept the terms of the agreement. 4 On the Installation page, click Browse to choose an installation directory or click Next to use the following default installation path: /opt/bmc/BMCRecoveryManager/EnterprisePolicyManagement 5 On the Client port page, accept the default port number, or enter a port number, for communication between the local and remote clients. You can click Validate to validate whether the port number is available for communications. Click Next. 6 If BMC Recovery Manager detects a previous installation of the EPM Policy Hub you are prompted to choose whether to reuse the existing data repository. Choose one of the following actions: ■ ■ Upgrade the repository from the pre-2.9.00 version Install a new repository 7 Click Next. 8 On the Summary Information page, click Install to continue installing the product. 9 On the second Summary Information page, record the URL for the remote installation if you want to install the client on a remote host. Then, click Finish to exit the installation script. 28 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Installing and configuring the EPM and the policy hub Installing the EPM remote client You can install the EPM client files on a remote Microsoft Windows or Linux host by using the URL location provided during the EPM and policy hub installation in step 8 on page 27. You can then launch the EPM from the remote host and connect to the policy hub on the local host. NOTE If you have previuosly installed the EPM remote client, you must uninstall it before you can install it again. The EPM Report Command Utility is automatically installed when you install the remote client. Using this utility, you can run BMC Recovery Manager reports. See Appendix C, “BMC Recovery Manager reports,” for information about this utility. To install the EPM client files on a remote Windows host 1 From the remote host on which you want to install the EPM client files, open a browser. At the address field, enter the URL location provided during the EPM and policy hub installation in step 8 on page 27. Generally, this is your computer name, plus the port number assigned to the policy hub, such as the following URL: http://bmc-aus-01:8082/ Click Go. 2 On the Welcome page, click Next. 3 On the License Agreement page, review the license agreement and click I accept the terms of the license agreement to accept the terms of the agreement. 4 On the Installation page, click Browse to choose an installation directory or click Next to use the following default installation path: C:\Program Files\BMC Software\BMC Recovery Manager\EPM Remote Client 5 On the Installation type page, choose the installation type: Typical or Custom. Click Next. 6 On the Summary Information page, click Install to continue installing the product. 7 Click Finish to exit the installation script. Chapter 2 Installing the BMC Recovery Manager components 29 Installing and configuring the EPM and the policy hub To install the EPM client files on a remote Linux host NOTE To install the EPM client files on a remote Linux host, you must ensure that Firefox is Javaenabled by using the following procedure: 1. Download the J2SE Java Runtime Environment (JRE) from http://java.sun.com. JRE version 1.4.2_10 is recommended. 2. Execute the JRE installation program to uncompress RPM. 3. Install RPM by using the following command: `rpm –ivh `cd 4. Change to the browser plugin directory: `cd /usr/lib/firefox-1.0/plugins/` 5. Link to the plugin shared library within the installed JRE by using the following command: `ln –s /usr/java/jre1.5.0_06/plugin/i386/ns7/libjavaplugin_oji.so` 1 From the remote host on which you want to install the EPM client files, open a browser. At the address field, enter the URL location provided during the EPM and policy hub installation in step 9 on page 28. Generally, this is your computer name, plus the port number assigned to the policy hub, such as the following URL: http://bmc-aus-01:8082/ Click Go. 2 On the Welcome page, click Next. 3 On the License Agreement page, review the license agreement and click I accept the terms of the license agreement to accept the terms of the agreement. 4 On the Installation page, click Browse to choose an installation directory or click Next to use the following default installation path: /opt/bmc/BMCRecoveryManager/EnterprisePolicyManagement/EPMRemoteClient 5 On the Installation type page, choose the installation type: Typical or Custom. Click Next. 6 On the Summary Information page, click Install to continue installing the product. 30 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Installing and configuring the EPM and the policy hub 7 Click Finish to exit the installation script. NOTE ■ As a default, all users are assigned the role of view. Before any user can perform any tasks except viewing data, you must log in to EPM as ebrsuperadmin and map other roles to the users who need to perform other tasks. See “Implementing policy hub security” on page 60 for more information. Using the demonstration data file BMC Recovery Manager includes a demonstration data file on the BMC Recovery Manager EPM Policy Hub CD. You can use the demonstration data file to set up a policy hub that is prepopulated with backup and recovery status and performance metrics. The prepopulated policy hub enables you to run the EPM with sample data so that you can become familiar with the interface before registering your own database server hosts. To use the demonstration data file 1 From Services, shut down the policy hub service by right-clicking the BMC EPM Policy Hub service and choosing Stop. 2 Make a backup copy of the original data file for your policy hub by renaming it to save.ebrderby. The save. prefix is required. 3 Copy the ebrderby.zip file from the demo directory on the BMC Recovery Manager EPM Policy Hub CD to /dataRepository/bin, the original data file directory. 4 Unzip the ebrderby.zip file. 5 Start the EPM: A From the Start menu, choose Programs => Enterprise Policy Management => Launch EPM Console. BMC Recovery Manager starts and displays the EPM. B Connect to the policy hub, supplying the correct information when requested. C Verify that the host names and data source names from the demonstration data file are displayed in the EPM. Chapter 2 Installing the BMC Recovery Manager components 31 Installing and configuring the EPM and the policy hub D View the backup and recovery metrics from the demonstration data file and experiment with the options available for displaying detailed information for the data sources, backups, and recoveries. 6 When you are finished using the demonstration data file and you want to begin monitoring your own data sources, complete the following steps: A From Services, stop the policy hub service by right-clicking the BMC EPM Policy Hub service and choosing Stop. B Rename the saved data file to the original file name to overwrite the demonstration data file. For example, rename save.ebrderby to ebrderby. C From Services, start the policy hub service by right-clicking the BMC EPM Policy Hub service and choosing Start. D Register the database server hosts in your environment by using the EPM as instructed in the Help. Upgrading an EPM and policy hub installation To upgrade an EPM and policy hub installation, install the new version of the EPM and policy hub. The new version detects the existing installation and automatically upgrades the EPM, policy hub, and existing data files. You should not manually uninstall the previous version before installing the new version. When the upgrade is complete, the previous version will be uninstalled automatically. NOTE If your data files are large and you are upgrading from version 2.6 or earlier, the upgrade may take several minutes. To upgrade an EPM and policy hub installation 1 Install the new EPM and policy hub using the procedure described in “Installing the EPM and the policy hub” on page 26. 2 To migrate your existing data file, during installation on the Data File Selection page, choose the option to use an existing data file. The existing data file will be copied for use with the new installation. 32 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Installing the EPM-BSM integration component NOTE ■ Migrating the data file gives you access to the historical status and performance metrics for the data sources in that data file. ■ If you experience problems migrating your data file during installation, see “Manually migrating an existing data file” on page 102 for troubleshooting information. ■ After you upgrade, all users are assigned the default role of view. Before any user can perform any tasks except viewing data, you must log in to EPM as ebrsuperadmin and map other roles to the users who need to perform other tasks. See “Implementing policy hub security” on page 60 for more information. Installing the EPM-BSM integration component You can configure the EPM to push policy events to Business Service Management (BSM). By installing BSM integration components, including the EPM-BSM integration component, and configuring BSM integration through the EPM, you can push policy events into the BMC Impact Manager application. Then, you can monitor policy events through the BMC Impact Explorer. Install the EPM-BSM integration component only if you are integrating with BSM. For more information about BSM integration, see Chapter 6, “Integrating with BMC Atrium.” 1 On the BMC Recovery Manager EPM Policy Hub CD, locate the MasterCell folder. 2 On Windows, run setupwin32.exe to start the installation. On Linux, run setuplinux.sh to start the installation. The EPM-BSM Integration wizard opens. 3 On the Welcome page, click Next. 4 On the Installation page, click Browse to choose an installation directory or click Next to use the following default Windows installation path: C:\Program Files\BMC SOFTWARE\EPM-BSM Integration For Linux, the default path is: opt/bmc/BMCSOFTWARE/EPM-BSMIntegration Chapter 2 Installing the BMC Recovery Manager components 33 Uninstalling BMC Recovery Manager components 5 On the Master cell location page, click Browse to choose a BMC Impact Manager (cell) location or click Next to use the default cell location. If BMC Recovery Manager detects a BMC Impact Manager installation, it displays the cell location here. 6 On the next page, which displays where BMC Recovery Manager will install the EPM-BSM integration component, click Next. 7 On the Summary information page, click Install. 8 On the second Summary information page, click Finish. Uninstalling BMC Recovery Manager components If you need to remove some or all of the BMC Recovery Manager components from their hosts, use the instructions provided in this section. Removing BMC Recovery Manager services from the database server host The BMC Recovery Manager services that enable the collection of status and performance metrics are automatically installed on the database server host when you install BMC SQL-BackTrack. If you uninstall the BMC SQL-BackTrack product, the BMC Recovery Manager components are also automatically uninstalled. To learn how to uninstall only the services that enable monitoring and management in the EPM (without uninstalling BMC SQL-BackTrack), see the installation guide for your BMC SQL-BackTrack utility. Removing the EPM and the policy hub NOTE On Windows, you must be a member of the Administrators group to uninstall the EPM and policy hub. On Liux, you must have root authority to uninstall the EPM and policy hub. 34 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Uninstalling BMC Recovery Manager components 1 Go to the directory where the EPM and policy hub are installed. The default installation directory on Windows is: C:/Program Files/BMC Software/BMC Recovery Manager/Enterprise Policy Management The default installation directory on Linux is: /opt/bmc/BMCRecoveryManager/EnterprisePolicyManagement 2 In the _uninst directory, locate the uninstaller.exe file (Windows) or the uninstaller.sh file (Linux). 3 Run uninstaller.exe (Windows) or uninstaller.sh (Linux). Removing the EPM remote client 1 On the remote host, go to the directory where the EPM remote client files are installed. The default installation directory on Windows is: C:/Program Files/BMC Software/BMC Recovery Manager/EPM Remote Client The default installation directory on Linux is: \opt\bmc\BMCRecoveryManager\EPMRemoteClient 2 In the _uninst directory, locate the uninstaller.exe file (Windows) or the uninstaller.sh file (Linux). 3 Run uninstaller.exe (Windows) or uninstaller.sh (Linux). Chapter 2 Installing the BMC Recovery Manager components 35 Uninstalling BMC Recovery Manager components 36 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Chapter 3 Introducing the Enterprise Policy Monitor 3 This chapter presents the following topics: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting the EPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting the EPM from a remote host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connecting to the policy hub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Registering a database server host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Data Sources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Navigating the EPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Accessing the Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Navigating the Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printing the Help topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 38 38 38 39 40 42 42 42 43 43 Overview The Enterprise Policy Monitor (EPM) interface in BMC Recovery Manager is a flexible management tool appropriate for a wide variety of users, including database administrators, system administrators, storage administrators, IT managers, application managers, and chief information officers (CIOs). These users can monitor and manage data sources on database server hosts that you register. To understand how the interface is useful, consider the following examples. If you want to monitor all databases of a specific type regardless of location, you can use the EPM to set up this particular display and then save it for future use. You can also use the monitor to determine whether specific data sources are being backed up at designated intervals and whether recovery actions are successful. This chapter provides an introduction to the EPM. For more detailed information, see the BMC Recovery Manager Help. Chapter 3 Introducing the Enterprise Policy Monitor 37 Starting the EPM Starting the EPM From the Start menu, choose Programs => BMC Recovery Manager => Enterprise Policy Management => Launch EPM Console. BMC Recovery Manager starts and displays the EPM. Starting the EPM from a remote host On the remote host, from the Start menu, choose Programs => BMC Recovery Manager => EPM Remote Client => => EPM Remote Client. BMC Recovery Manager starts and displays the EPM remote client after you enter the login information. Connecting to the policy hub You must connect to the BMC Recovery Manager policy hub to register database server hosts and then monitor data sources with the EPM. To learn how to register the database server hosts on which your data sources reside, see the Help. NOTE ■ EPM version 2.9 clients automatically connect to the policy hub that is installed on the computer from which the EPM is launched. ■ If a policy hub is not installed on the same computer as the EPM, you are prompted for the host name of the computer on which the policy hub is installed. ■ Also, be aware of the following compatibility restrictions: — You cannot use EPM version 2.5 or earlier to connect to the policy hub. — You cannot use EPM version 2.9 or later to connect to an earlier version of the data repository. To connect to the policy hub, perform the following steps in the BMC Recovery Manager Login dialog box. 1 From the Start menu, choose Programs => Enterprise Policy Management => Launch EPM Console. BMC Recovery Manager starts and displays BMC Recovery Manager Login dialog box. 38 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Registering a database server host 2 Enter your user name for the Linux account or Windows domain for the computer on which the policy hub resides. If the policy hub host is a Windows computer that requires domain authentication, your user name must include a domain name (\). 3 Enter the Linux or Windows password to connect to the computer on which the policy hub resides. 4 Click OK. Registering a database server host Before you can monitor your data sources, you must identify the database server hosts that contain these data sources. The database server hosts must be associated with an installation of BMC SQL-BackTrack 5.0 or later. After you register a database server host, BMC Recovery Manager starts to gather information for that host and store the information in the policy hub. Even after registering the database server host, you may not see any metric data displayed in the EPM console. The EPM console will not display any metric data unless there is a backup or recovery completed on the database server host you have registered. To register a database server host, perform the following steps. 1 From the Admin menu, choose Register New Hosts. 2 In the Register Database Server Hosts dialog box, perform the following steps for each database server host that you want to register: A At Host name, enter the name of the database server host that contains data sources that you want to monitor. B At Port number, enter the port number used by the database server host to communicate with the Enterprise Policy Monitor. C Click Add to List. The host name and port number are added to the Database server hosts to register list. 3 (Optional) When you finish entering the information for database server hosts, click Save List to save the server host information for later use. Chapter 3 Introducing the Enterprise Policy Monitor 39 Managing Data Sources 4 To start the registration process, click Register. 5 In the Database Server Host Registration Status dialog box, monitor the registration progress as it occurs. This dialog box indicates if any problems occur during the registration of the database server hosts. When the registration process ends, those hosts that were registered have a registration status of Success. The hosts that could not be registered have a status of Failure. NOTE If you receive a warning message, there may be a misconfigured firewall environment or a DNS environment where the policy hub can see the database server host but the database server host cannot see the policy hub. Before proceeding, if you have a DNS configuration, verify that the BMC Recovery Manager host name can be resolved using DNS. If you have a firewall environment, verify the firewall configuration. In the event of a misconfigured DNS environment or firewall, the registration process will complete, and the policy hub can proceed to gather metrics using an alternate communication method. However, you may experience slower performance using the alternate method than if the DNS or firewall environment were properly configured. If you modify the firewall or DNS configuration, you must reregister the database server host before the product can resume gathering metrics. See “Troubleshooting database server host registration” on page 103 or more information. 6 If you are finished registering database server hosts, click Close. Otherwise, return to step 2. NOTE BMC Recovery Manager can monitor the data sources within a database server host only if the backup and recovery activities of that host are associated with BMC SQL-BackTrack 5.0 or later. Managing Data Sources This section contains procedures to delete a data source and to enable deleted data sources. When you register a database server host all of the data sources on that host are monitored in the EPM console. To selectively exclude some data sources from being monitored, use the procedure “To delete a data source.” To resume the monitoring of a data source that you deleted, use the procedure “To enable a deleted data source” on page 41. 40 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Managing Data Sources To delete a data source 1 In the Enterprise Policy Monitor, right-click the data source that you want to delete and choose Delete Data Source. Use the Shift or Ctrl key to select multiple data sources. 2 On the Delete Data Sources dialog box, click Yes to delete the data source or data sources. The selected data sources and their associated metric information are removed. To enable a deleted data source 1 In the Enterprise Policy Monitor, choose Admin => Enable Deleted Data Sources. The Enable Deleted Data Sources dialog box appears. 2 In the Current deleted data source list column, select the data sources that you want to enable. 3 Click the right arrow button to move the deleted data sources to the Data sources to be enabled column. 4 Click Apply to enable the data sources. 5 On the Enable Deleted Data Sources dialog box, click Yes to enable the data sources. 6 Click OK. 7 Click Close. The selected data sources and their associated metric information are enabled. NOTE To move a data source back to the Current deleted data source list, select the data source in the Data sources to be enabled list, and click the left arrow. When you enable a deleted data source, its associated metric information is also enabled. Chapter 3 Introducing the Enterprise Policy Monitor 41 Navigating the EPM Navigating the EPM The following elements in the EPM play an important role when you monitor your data sources: ■ ■ ■ filter criteria window monitor window status bar The menu bar and toolbar perform standard functions. For detailed information about the menu commands and toolbar options that are available, see the Help. In the filter criteria window, you can limit the data sources that are displayed in the monitor window to those that match specified criteria. To learn how to select the columns and set the values that you want to include as criteria, see the Help. The monitor window displays summary information for the data sources on registered database server hosts. This window contains numerous columns of important information for each data source that meets the criteria specified in the filter criteria window. See the Help for specific details about the columns of information displayed in the monitor window. The status bar displays information about the filter that currently affects which data sources are displayed, such as the name of the current filter and how many data sources match the criteria. NOTE When data for a particular combination of metric and data source is not available, the EPM displays a blank field or column. For example, if you have not associated a data source with a policy, the Policy Name column for that data source (in the monitor window) is blank. The same is true when a particular metric is not applicable. Viewing Help The EPM provides Help to assist you in performing your data management tasks. Use the context-sensitive Help to access instant answers to procedural and conceptual questions. The following sections explain how to access, navigate, and print the Help. Accessing the Help You can access the Help as follows: 42 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Viewing Help ■ Click the Help button that appears on dialog boxes. Context-sensitive Help appears for that particular interface element. ■ Go to the Help menu in the BMC Recovery Manager menu bar and choose Help topics. Navigating the Help You can use the back and forward buttons to navigate through the Help topics. The Help provides standard navigation, using hyperlinks. The Contents, Index, Search, and Messages tabs can help you locate specific topics. Printing the Help topics You can use the print button on the toolbar of the Help viewer to print the Help topic that is visible in the right pane. Chapter 3 Introducing the Enterprise Policy Monitor 43 Viewing Help 44 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Chapter 4 4 Policy administration This chapter presents the following topics: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites for using policy administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Policy administration tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitoring policy compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 46 46 50 Overview One of the key features in BMC Recovery Manager is the ability to audit backup and recovery requirements through policy administration. A policy is a set of rules that you define in the Enterprise Policy Monitor (EPM). “Policies” on page 20 discusses the concept of policies in BMC Recovery Manager. The policy administration feature enables you to ■ define rules that help you track service-level agreement (SLA) requirements for backup and recovery ■ monitor inconsistencies in backup and recovery practices ■ detect compliance failures and receive failure notifications ■ establish rules that can help you manage your disaster recovery plans ■ keep track of registered hosts in your BMC SQL-BackTrack environment You define policies through the EPM, which stores the policies in the policy hub. You can then assign a policy to one or more data sources. You can have multiple policies defined; however, each data source can be associated with only one policy. Chapter 4 Policy administration 45 Prerequisites for using policy administration After you have assigned a policy to each of the data sources, the EPM starts to monitor policy compliance by comparing the specifications defined in the policy against the metric data that it collects from the BMC SQL-BackTrack installations for the data source. The status of this policy compliance is displayed in the EPM. If a data source fails to meet the requirements specified in the policy, a Failure icon in the Policy status column indicates the failure. NOTE A policy does not cause the specified requirement to occur, but only indicate whether a database conforms to the guidelines provided in a policy. Prerequisites for using policy administration Before you begin administering back up and recovery policies, you must: ■ Ensure that all the BMC Recovery Manager components are installed and configured. ■ Ensure that all BSM integration components are installed and configured, if you wish to push EPM policy events to Business Service Management (BSM) applications. ■ Ensure that BMC SQL-BackTrack is installed on the database server hosts that you want to manage in the EPM. ■ Ensure that your data source hosts are registered in the EPM. ■ Determine the requirements for the policies that you want to define. After you have satisfied the prerequisites, you are ready to establish backup and recovery policies and to begin monitoring compliance. The next section introduces you to the policy administration tasks. Policy administration tasks It can be very difficult to maintain consistent backup and recovery standards in large distributed environments. Although operations manuals, customer SLAs, and other sources define these standards, they are hard to implement and enforce because of the many different systems and individuals involved. EPM provides a way to define 46 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Policy administration tasks policies that capture these standards, to apply the policies to different databases, and to monitor ongoing compliance with the policies. EPM reports a policy compliance failure any time a backup or recovery action does not meet the criteria of the applicable policy. Figure 3 on page 47 shows the information that you can use to define a backup policy with standards for type of backup, backup frequency, and backup retention. Figure 3 Available attributes for defining a backup policy You can specify a backup exclusion period as part of a policy definition. For example, “Full backup every Sunday and Incremental backup every day except Sunday,” or “No backups during regular working hours.” The Select Backup Exclusion Time Period dialog box shown in Figure 4 on page 48 contains the controls for setting an exclusion period for a weekly recurrence. You can also specify the recurrence pattern by month or year. Chapter 4 Policy administration 47 Policy administration tasks Figure 4 Select Backup Exclusion Time Period dialog box EPM will generate a policy compliance failure for any backup activities during the exclusion period. Even if you make backups everyday, you might still have problems recovering due to factors in your processes or environment. EPM can help you maintain your ability to recover on an ongoing basis by setting up policies to monitor the automated recovery tests. Figure 5 on page 49 shows the information that you can specify for a recovery policy. For detailed information about policy attributes, click the Help button on the interface. 48 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Policy administration tasks Figure 5 Available attributes for defining a recovery policy After you have defined backup and recovery policies, you can use the Action menu to manage the policy assignments for your data sources. NOTE You can also use the Admin menu to view the hosts that are registered in the EPM, or to register a host. Table 3 on page 50 lists the policy tasks that you can use in BMC Recovery Manager. For detailed instructions about how to complete a task, see the BMC Recovery Manager Help. Chapter 4 Policy administration 49 Monitoring policy compliance Table 3 Policy tasks Task Description Menu create a new policy define a policy by specifying the requirements for backup and recovery Admin => New Policy Note: The EPM does not allow you to create a new policy with the same name as a deleted policy. If the deleted policy was assigned to a data source, the EPM maintains a history of the policy so that a policy compliance history report can be generated. The deleted policy is not completely deleted but is “marked to delete.” assign a policy assign a new policy to a registered data Action => Assign Policy source modify a policy edit the specifications for a selected policy Admin => Edit Policy delete a policy delete a policy from a list of defined policies Admin => Delete Policy unassign a policy remove a policy assignment Action => Remove Policy Assignment view policy information view policy status details for selected data sources Action => Policy Status Details Monitoring policy compliance After you have defined the policies and assigned the policies to the data sources for all registered database server hosts, you can monitor compliance through the EPM. For more information, see the Help. 50 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Chapter 5 5 Working with the policy hub This chapter presents the following topics: Configuring the policy hub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backing up the policy hub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Validating and recovering the policy hub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing data expiry in the repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Other policy hub configuration parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Implementing policy hub security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Predefined roles and privileges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring EPM for security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Typical security tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sharing policy hub data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exporting policy hub data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Importing policy hub data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 53 55 57 58 60 61 61 62 64 65 65 Configuring the policy hub EPM provides a number of parameters that you can use to configure the policy hub. Example configuration options include the following: ■ ■ ■ ■ automatically back up the policy hub automatically validate the policy hub and recover when errors are detected manage data expiry in the history tables of the policy hub change where custom attribute columns are located in reports The parameters for these and other configuration options are described in the sections that follow. All of the parameters have built-in default values that will work in your environment. Depending on your specific requirements, you might want to modify the values for one or more parameters. Chapter 5 Working with the policy hub 51 Configuring the policy hub To configure the policy hub 1 Select Admin => Configure The EPM Configuration dialog box is displayed. 2 Click the Policy hub tab. 3 Scroll the list to find the parameter you want to change and enter the new value for the parameter in the Value field. Table 4 lists the parameters in the EPM Configuration dialog box that can be modified. Table 4 52 EPM parameters you can set Parameter For more information, see Backup automatically Table 5 on page 53 Backup interval in days Table 5 on page 53 Backup start time Table 5 on page 53 Custom attribute report position Table 8 on page 59 Default role Table 10 on page 61 Discovery failure timer interval Table 8 on page 59 DNS Host Name Table 18 on page 88 Dry-run recovery margin Table 8 on page 59 Evaluation interval Table 8 on page 59 Expiry delay in days Table 7 on page 58 Expiry interval in days Table 7 on page 58 Expiry timer Table 7 on page 58 IP Address Table 18 on page 88 Managed node monitor timer delay Table 8 on page 59 Managed node monitor timer interval Table 8 on page 59 Number of generations to keep Table 5 on page 53 Policy evaluation delay in seconds Table 8 on page 59 Recovery margin Table 8 on page 59 Recovery validation timer Table 6 on page 56 Resync history Table 8 on page 59 Use IP Address Table 18 on page 88 Validation delay in hours Table 6 on page 56 Validation interval in hours Table 6 on page 56 Windows server name for users or groups Table 10 on page 61 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Configuring the policy hub Backing up the policy hub You have the option of backing up the policy hub automatically or manually, as described in the following sections. Automatic backup To control automatic backups of the policy hub, edit the backup parameters identified in Table 5 on page 53. For information about editing configuration parameters, see “To configure the policy hub” on page 52. NOTE The policy hub backup, which by default runs every day at 19:00, fails if another process uses the EPM database. Policy hub backup requires that the database be shut down prior to copying the EPM data file. If any user currently uses the database (for example, by running a direct query to the EPM database by using dbisql), the backup process does not shut down the database and the backup process terminates. Table 5 Policy hub configuration parameters: controlling automated policy hub backups (Part 1 of 2) Parameter Description Backup automatically Determines whether the data file for the policy hub is automatically backed up. The default value is true and the data file is automatically backed up. To manually back up the data file, set this parameter to false. Backup start time Indicates the time of day that you want to automatically back up the data file for the policy hub. Valid parameter values are 0 through 23, where 0 is 12 A.M. and 23 is 11:00 P.M. The default value is 19 (7:00 P.M.). If the Backup automatically parameter is false, this parameter is not used. Chapter 5 Working with the policy hub 53 Configuring the policy hub Table 5 Policy hub configuration parameters: controlling automated policy hub backups (Part 2 of 2) Parameter Description Backup interval in days Indicates how often automatic backups of the data file for the policy hub should occur. Valid parameter values include any number greater than 0. The default value is 1 and the data file is backed up every day. Setting it to 5 means the policy hub will be backed up every five days. If the Backup automatically parameter is false, this parameter is not used. If the Backup automatically parameter is true, this parameter must be greater than 0. Number of generations to keep Indicates how many generations or backup copies to keep of the data file for the policy hub. By default, the 7 most recent copies of the data file are saved to the data\backups directory under the policy hub installation directory. If the Backup automatically parameter is false, this parameter is not used. If the Backup automatically parameter is true, this parameter must be greater than 0. The automatic backup files are stored in the following directory: /dataRepository/data/backups where is the directory where the policy hub is installed. This directory contains the current backup file and a subdirectory for each stored backup file (as specified by the value for the Number of generations to keep parameter). The automatic recovery procedure uses the current backup file to perform the recovery. 54 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Configuring the policy hub Manual backup To manually back up the policy hub, copy the data file to a backup directory as follows. 1 Locate the data directory. By default, the data directory is installed in the /data directory. The default name for the directory is ebrderby. If you need assistance locating the policy hub installation directory, see “Installing and configuring the EPM and the policy hub” on page 25. 2 Stop the policy hub. See “Stopping and starting the policy hub” on page 100 for more information. 3 Back up the data file by copying it from the data directory to the data/backups directory. 4 Start the policy hub. See “Stopping and starting the policy hub” on page 100 for more information. Validating and recovering the policy hub You have the option of recovering the policy hub automatically or manually, as described in the following sections. Automatic recovery To enable automatic validation and recovery of the policy hub when errors are detected, edit the validation and recovery parameters identified in Table 6 on page 56. For information about editing configuration parameters, see “To configure the policy hub” on page 52. Chapter 5 Working with the policy hub 55 Configuring the policy hub Table 6 Policy hub configuration parameters: controlling automated validation and recovery Parameter Description Recovery validation timer Set this parameter to true to perform the following actions on the data file in the policy hub: ■ automate validation (data integrity checking) of the data in the data file based on the interval specified by the Validation interval in hours parameter. ■ restore the most recent copy of the data file if the validation fails By default this parameter is false and the data file is validated only when it is backed up. Validation interval in hours Indicates how often validation of the data file in the policy hub occurs. Valid parameter values include any number greater than 0. By default, this value is 7 and validation occurs every 7 hours. Notes: Validation delay in hours ■ If the Recovery validation timer parameter is false, this parameter is not used. ■ If the Recovery validation timer parameter is true, this value must be greater than 0 and this value should be less than the backup interval multiplied by 24 hours (see Backup interval in days on page 54.) Indicates the time interval between starting the policy hub and running the first validation (data integrity check) on the data file. By default, this value is 0, which causes the first validation to occur immediately after the policy hub starts. Note: If the Recovery validation timer parameter is false, this parameter is not used. 56 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Configuring the policy hub Manual recovery To manually recover the policy hub, copy the data file from the backups directory to the data directory as follows. 1 Locate the backup zip file. By default, the file is stored in the /data/backups directory. The most current backup is named ebrderby.zip. Previous backups are stored in directories labelled with timestamps. If you need assistance locating the policy hub installation directory, see “Installing and configuring the EPM and the policy hub” on page 25. 2 Stop the policy hub. See “Stopping and starting the policy hub” on page 100 for more information. 3 Recover the data file by copying the zip file from the /data/backups directory to the /data directory and extracting it. 4 Restart the policy hub. See “Stopping and starting the policy hub” on page 100 for more information. Managing data expiry in the repository To ensure that the history tables within the policy hub do not become too large, BMC Recovery Manager provides an automatic way to manage their size by using data expiry. If you want BMC Recovery Manager to automatically manage data expiry, edit the data expiry parameters in Table 7 on page 58. For information about editing configuration parameters, see “To configure the policy hub” on page 52. Chapter 5 Working with the policy hub 57 Configuring the policy hub Table 7 Policy hub configuration parameters: managing data expiry Parameter Description Expiry delay in days Indicates the time interval between starting the policy hub and running the first expiration check. The default value is 0 and the first expiration check occurs immediately after the policy hub starts. If the Expiry timer parameter is false, this parameter is not used. Expiry interval in days Determines how frequently the data in the data file for the policy hub is checked against the expiration criteria. The default value is 31 and data that meets the expiration criteria is deleted every 31 days. If the Expiry timer parameter is false, this parameter is not used. Expiry timer Determines whether the data in the data file for the policy hub is automatically deleted based on the interval set for the Expiry interval in days parameter. The default value is true and data is automatically deleted. If you do not want to automatically delete data, set this parameter to false. The expiry.cfg file The expiry.cfg file indicates the number of days BMC Recovery Manager should store data for each history table in the policy hub. Each entry starts with the table name and is followed by a value that indicates the number of days of data that should be stored in the corresponding table. When data expiration occurs according to the Expiry interval in days setting, data that is older than that indicated for each table is deleted. For example, if you wanted to retain ten days worth of data for each history table in the policy hub, your expiry.cfg file would contain each table name followed by a value of 10. Other policy hub configuration parameters The configuration parameters that control policy hub maintenance (backup, recovery, and data expiry) are discussed in “Backing up the policy hub” on page 53, and “Managing data expiry in the repository” on page 57. All other configuration parameters that you can change are described in Table 8 on page 59. 58 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Configuring the policy hub Table 8 Policy hub configuration parameters: controlling various functions (Part 1 of 2) Parameter Description Custom attribute report position the location of the columns with the selected custom attributes in the summary report. Valid values are Discovery failure timer interval ■ prefix (default) first columns after the data source name ■ suffix last columns of report time interval that limits the amount of time that the policy hub has to complete the registration process for a database server host The default value is 240 seconds. Dry-run recovery margin factor used to calculate the estimated time to recovery if the last recovery is a dry run recovery The default value is 30 percent or 1.30 as follows: 1.30 [factor] x 60 seconds [elapsed dry run recovery time] = 78 seconds [estimated time to recovery] Managed node monitor timer delay indicates the time interval between starting the policy hub and running the first validation on the database server host connectivity. The default for the monitor time delay is 1 hour (3600 seconds). Managed node monitor timer interval indicates how often the policy hub validates the database server host connectivity in an environment where there is configuration problem with the DNS or the firewall. If the database server host is restarted after being down, the connectivity will be checked and restored when the timer is fired. The default for the monitor time interval is 1 hour (3600 seconds). Policy evaluation delay in seconds delay between starting the policy hub and initiating the first policy evaluation By default, this value is 0 seconds and the first policy evaluation occurs immediately after the policy hub starts up. Chapter 5 Working with the policy hub 59 Implementing policy hub security Table 8 Policy hub configuration parameters: controlling various functions (Part 2 of 2) Parameter Description Evaluation interval time interval between policy evaluations The default value is 1200 seconds. Recovery margin factor used to calculate the estimated time to recovery if the last recovery is an actual recovery The default value is 10 percent or 1.10 as follows: 1.10 [factor] x 120 seconds [elapsed recovery time] = 132 seconds [estimated time to recovery] Resync history number of days of historical data that the policy hub requests from a newly registered database server host The default value is 7 days. Implementing policy hub security The Enterprise Policy Monitor (EPM) provides role-based security that restricts user access to menu functions, dialog boxes, and reports. The roles can be assigned, or mapped, to individual users and to user groups. In addition, you can create user defined roles that relate the privileges of EPM roles to specific data sets. EPM provides a set of roles with varying privileges. Any user or user group can have one or more roles mapped to it. In addition, you can create user defined roles that relate the privileges of EPM roles to specific data sets. One of the roles, the superadmin role, has the authority to map roles to users and groups. When you install EPM, one account is created with superadmin privileges. This account is called ebrsuperadmin and has changeme as the password. As a default, all other users are assigned the role view. Before anyone can configure EPM, you must log in as ebrsuperadmin and map roles with other privileges to users, including at least one superadmin user. After you use ebrsuperadmin to map the superadmin role to another user, the ebrsuperadmin account is disabled and you can no longer use it. NOTE If you need to reinstate the ebrsuperadmin user, consult Customer Support. 60 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Implementing policy hub security Predefined roles and privileges Table 9 lists the predefined roles for users and user groups. User groups are the UNIX groups or the Windows system groups defined in your environment. Table 9 User roles Role Privilege level superadmin all EPM tasks admin all EPM tasks except deleting hosts, creating and modifying data sets, roles, and role mapping and deleting and undeleting data sources edit assign policies, attributes, and e-mail alert assignments to data sources and all privileges of the report role report generate reports and export to spreadsheets and all privileges of the view role view view only More than one role can be mapped to a user or a user group. The Active Role selection list in the Enterprise Policy Monitor window shows all the role that have been mapped to you. You can select the role that you want to use at any time with the Active Role selection list. Configuring EPM for security EPM provides two optional configuration parameters to use if you want to use the role mapping security features. For information about these parameters, see Table 10 on page 61. For information about editing configuration parameters, see “To configure the policy hub” on page 52. Table 10 Policy hub configuration parameters: preparing for security Parameter Description Default role default role for users who do not have a role assigned. The default is view. Windows server name for users or groups the DNS or NetBIOS name of the Windows server on which the users or groups are located. The default value is null. If no value is specified, you will not be able to browse the available Windows users and groups when mapping EPM roles. You can still browse UNIX user groups and you can type the names of users or groups. Chapter 5 Working with the policy hub 61 Implementing policy hub security Typical security tasks You must have superadmin privileges to perform these tasks. Table 11 Typical security tasks Task For more information, see Configuring security parameters “Configuring EPM for security” on page 61 Create data sets “To create a data set” on page 62 Create user defined roles “To create a user defined role” on page 63 Map the user defined roles to the users “To create a user role mapping” on page 63 Map the user defined roles to user groupss “To create a user group role mapping” on page 64 To create a data set 1 On the Admin menu, select Dataset. The EPM Dataset dialog box is displayed. 2 Click New. The Add Dataset dialog box is displayed. 3 In the Dataset name field, type the name of the data set you want to create. 4 In the Name column of the Dataset Criteria field, click the first criteria you want to specify. 5 Use the Select values field to specify the criteria values. ■ To add a value to the data set definition, click the value in the Available Values column, and click the right arrow to move the value to the Selected Values column. ■ To create a new value for the criteria, click New and enter the value in the Input dialog box. Then select the new value in the Available Values column, and click the right arrow to move the value to the Selected Values column. 6 Repeat for all the criteria you want to use for the data set. 7 Review the Summary field and click OK. 62 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Implementing policy hub security To create a user defined role 1 On the Admin menu, select Role->User Defined Role. The User Defined Role dialog box is displayed. 2 Click New. The Add User Defined Role dialog box is displayed. 3 Type the name for the new role. 4 Select the name of the EPM role with the privileges you want this user defined role to have. Available EPM roles are admin, edit, report, and view. 5 Select the name of the data set you want this role to apply to. The data set must have already been defined. 6 Click OK. The user defined role is listed in the User Defined Role dialog box and in the list of available roles in the Add User Role and the Add Group Role dialog boxes. To create a user role mapping 1 On the Admin menu, select Role->Map Role. The Map Role dialog box is displayed. 2 Click the Users tab. 3 Click New. The Add User Role dialog box is displayed. 4 Type the name of the user that you want to assign roles to in the User name field, or browse to select a user from the available users. The name you type for user name must be a valid user for the system. 5 In the Available Roles column, click the role or roles you want to assign to the user. If you have created any user defined roles, those roles will be listed along with the EPM roles. 6 Click the right arrow to move the roles to the Assigned Roles column. 7 Click OK. Chapter 5 Working with the policy hub 63 Sharing policy hub data To create a user group role mapping 1 On the Admin menu, select Role->Map Role. The Map Role dialog box is displayed. 2 Click the Groups tab. 3 Click New. The Add Group Role dialog box is displayed. 4 Type the name of the group that you want to assign roles to in the Group name field, or browse to select a group from the available groups. The name you type for group name must be a valid user group for the system 5 In the Available Roles column, click the role or roles you want to assign to the user group. If you have created any user defined roles, those roles will be listed along with the EPM roles. 6 Click the right arrow to move the roles to the Assigned Roles column. 7 Click OK. Sharing policy hub data Enterprise Policy Monitor allows you to share non metric data between policy hubs by exporting and importing the data you want to share. The non metric data that you can share includes: ■ ■ ■ ■ policy definitions contact list distribution lists e-mail lists When you export data from a policy hub, EPM stores the data in an XML file, which can be read by policy hub that is importing the data. NOTE EPM can only import data that was exported by a policy hub that has the same version or an earlier version than the importing policy hub.The exporting policy hub cannot be a more recent version than the policy hub that is importing the data. 64 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Sharing policy hub data Exporting policy hub data EPM allows you to export any or all policies as well as contact, e-mail, and distribution lists. You can choose to export only the contact list, but if you choose to export the distribution list, the contact list will be exported as well. If you choose to export the email list, then the distribution list and the contact list will also be exported. To export policy hub data 1 Select Admin => Export Policy Hub Data. 2 In the Export Policy Hub Data dialog box, select the policy or policies you want to export. 3 In the Export Policy Hub Data dialog box, select the contact, distribution, or e-mail list you want to export. 4 Click Export. 5 Enter the file name and location where you want to save the data and click OK. EPM exports the data. If there is a large amount of data to export, EPM might take a long time to complete the export. 6 If EPM displays a dialog box warning you of the delay, click Yes to finish the export. Importing policy hub data EPM allows you to import policies as well as contact, e-mail, and distribution lists that have been exported from a policy hub with the Admin => Export Policy Hub Data. You can choose to import only the contact list, but if you choose to import the distribution list, the contact list will be imported as well. If you choose to import the e-mail list, then the distribution list and the contact list will also be imported. To import policy hub data 1 Select Admin => Import Policy Hub Data. 2 In the Import Policy Hub Data dialog box, type the name or browse to select the file that contains the data you want to import. Chapter 5 Working with the policy hub 65 Sharing policy hub data 3 In the Conflict Resolution Options area, specify what you want EPM to do if there are conflicts between the current data and the data you want to import. A If you want EPM to overwrite any policies that are in conflict with the import data file, click Overwrite All. If not, click Skip All. B If you want EPM to overwrite any contact, distribution, or e-mail lists that are in conflict with the import data file, click Overwrite All. If not, click Skip All. NOTE You can select different conflict resolution options for policies and for lists. The same conflict resolution option must apply to all lists. 4 Click Import. EPM imports the data. ■ If there are no conflicts, or if you selected Overwrite All, all the data is imported. ■ If there are conflicts with policy data, and you selected Skip All, the policies with conflicts are not imported. ■ If there are conflicts with list data, and you selected Skip All, the individual records with conflicts are not imported. Records that do not contain conflicts are imported. 5 Review the data in the View Import status information dialog box, and then click Close. 66 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Chapter 6 6 Integrating with BMC Atrium This chapter presents the following topics: BMC Atrium integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSM integration architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing BSM integration components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring BSM integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the EPM to send policy events to BMC Impact Manager . . . . . . . . . Enabling and disabling BSM events for a data source . . . . . . . . . . . . . . . . . . . . . . . Creating a service model that includes data sources monitored by the EPM . . . Monitoring EPM policy events from the BMC Impact Explorer . . . . . . . . . . . . . . EPM events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 68 69 70 71 71 72 73 73 BMC Atrium integration The Enterprise Policy Monitor (EPM) provides real-time monitoring of backups and recoveries in BMC SQL-BackTrack. In addition, it provides the ability to create definitions of best and required practices (policies) for database backup and recovery. The policies are evaluated at configurable intervals, and failures to meet the policy requirements are flagged in the monitor with an alert, resulting in policy events. You can configure the EPM to push policy events to BMC Atrium®. By installing Business Service Management (BSM) integration components and configuring BSM integration through the EPM, you can configure the EPM to push policy events into the BMC Impact Manager application. Then, you can monitor policy events through the BMC Impact Explorer. The following sections describe the BSM integration architecture, the BSM integration components, and the tasks you must perform to configure BSM integration. Chapter 6 Integrating with BMC Atrium 67 BMC Atrium integration BSM integration architecture To integrate BSM with EPM, you must install multiple BSM integration components. Table 12 on page 68 lists the required components. Table 12 BSM integration components Component Description BMC Impact Portal The BMC Impact Portal is a JBoss, web-based application. It typically contains a Service Model Editor (SME). It also contains the Access Control List (ACL) for the application. The BMC Impact Portal application is a multi-CD installation that includes Oracle. The BMC Impact Manager is an application that receives events from a BMC Impact Integration Web Service (BMC Note: Each instance of BMC IIWS) server. You can access the stored data by using the Impact Manager is equivalent BMC Impact Explorer. The BMC Impact Manager contains the object descriptions, called BAROC files, that are used for to a cell parsing objects and displaying the data. The BMC Impact Manager also contains the tools for compiling BAROC file customizations. BMC Impact Manager EPM-BSM integration component The EPM-BSM integration component configures communication between the BMC Impact Manager and the EPM. For information about installing this component, see “Installing the EPM-BSM integration component” on page 33. BMC Impact Integration Web You install the BMC Impact Integration Web Service (BMC Service (BMC IIWS) server IIWS) server as a part of the BMC Impact Integration Developer’s Kit (BMC IIDK). This is the integration point for sending events. It is a SOAP endpoint that permits connection and supports functions that are available from the BMC IIDK documentation. BMC Impact Explorer The BMC Impact Explorer is the user interface for viewing events that are delivered to the BMC Impact Manager. It is a stand-alone application, but it does require access to a BMC Impact Portal for user authentication. Figure 6 on page 69 shows the flow between the BSM integration components. 68 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Installing BSM integration components Figure 6 BSM integration process flow Installing BSM integration components You must install the following BSM integration components to be able to integrate the EPM with BSM. Chapter 6 Integrating with BMC Atrium 69 Configuring BSM integration Component Reference BMC Portal, which includes the Service Model Editor (SME) BMC Impact Manager product documentation CMDB BMC Impact Explorer BMC Impact Manager Note: Each instance of BMC Impact Manager is equivalent to a cell. EPM-BSM integration component “Installing the EPM-BSM integration component” on page 33 NOTE Install a new BMC Impact Manager or choose an existing one as a dedicated cell for EPM. Record the name of the cell. For example, this chapter uses cell epm-aus-01 as an example dedicated EPM cell. Configuring BSM integration To integrate with BSM, you must perform the tasks listed in Table 13. Table 13 BSM integration tasks Task Reference 1. Configure the EPM to send events to the “Configuring the EPM to send policy events to BMC Impact Manager. BMC Impact Manager” on page 71 2. Choose the data sources that you want “Enabling and disabling BSM events for a data source” on page 71 to monitor in the BMC Impact Explorer, and enable BSM for each data source. 70 3. Create a service model that includes data sources monitored by the EPM. “Creating a service model that includes data sources monitored by the EPM” on page 72 4. Monitor EPM policy events from the BMC Impact Manager. “Monitoring EPM policy events from the BMC Impact Explorer” on page 73 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Configuring BSM integration Configuring the EPM to send policy events to BMC Impact Manager 1 Ensure that you have installed the EPM-BSM integration component. See “Installing the EPM-BSM integration component” on page 33. 2 Launch the EPM. 3 In the EPM, choose Admin => Configure. The EPM Configuration dialog box is displayed. 4 Choose the BSM tab. The BSM configuration dialog box is displayed. 5 Enter the required information in the Impact Integration Web Service (IIWS) server fields and the Local event queue fields. NOTE For more information about what to enter in these fields, see the BMC Recovery Manager Help. 6 (optional) Click Test configuration to test the BSM configuration. The EPM sends an EPM test event to the specified BMC Impact Manager, which you can view from the BMC Impact Explorer. 7 Click Apply to apply the BSM configuration settings. Click Close. Enabling and disabling BSM events for a data source You must enable BSM events for a data source before the EPM can send policy events to the BMC Impact Manager. To enable BSM events for a data source 1 In the EPM, select the row or rows for the data sources for which you want to enable BSM events. 2 Choose Actions => Enable BSM => On. The value On appears in the BSM Enable column. Chapter 6 Integrating with BMC Atrium 71 Configuring BSM integration To disable BSM events for a data source 1 In the EPM, select the row or rows for the data sources for which you want to disable BSM events. 2 Choose Actions => Enable BSM => Off. The value Off appears in the BSM Enable column. Creating a service model that includes data sources monitored by the EPM Create a service model, or update an existing one, to include databases being monitored by the EPM. Use the Service Model Editor (SME), installed as part of the BMC Portal, to create or update your service model. Associate a service model component with the EPM data sources that you want to monitor. For example, you might want the database components to correspond to EPM data sources as follows: Database component EPM data source oracle-prd01 prd01::::DBName_7419 oracle-prd03 prd03::::DBName_7077 UDB-prd05 prd05:Server_8632:Inst8632:0:DBName_8632 When you edit or create the service model component, perform the following steps: 1 Specify the EPM dedicated cell as the cell to which you want to publish the service model. For example, when you edit the oracle-prd01 component, you might select epm-aus-01 as the cell to which to publish the service model. 2 In the Edit component Properties window, create the appropriate alias. To associated a database components with an EPM data source, you must assign the EPM data source as an alias to the component. For example, you would add the alias prd01::::DBName_7419 to the component oracle-prd01. 3 Select File => Publish Service Model to publish the service model to the cell. 72 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Configuring BSM integration Monitoring EPM policy events from the BMC Impact Explorer After you publish your service model to the cell, you can view it from the BMC Impact Explorer. 1 Log into the BMC Impact Explorer. 2 From the Services tab, find the service model that you just published. 3 Choose the parent component (for example, EPM Corporation) and select View Service => Causes. 4 Double-click on the parent component to drill down to the lower level of the tree. EPM events After you have configured BSM integration, BMC Recovery Manager sends an EPM event for a policy failure for any data source for which BSM is enabled. There are 23 types of policy items that generate an EPM event failure. Each event is associated with a specific data source for a specific policy hub. The event status remains open as long as the failure exists and is closed when any of the following conditions occur: ■ ■ ■ ■ ■ ■ ■ The policy item was deleted The policy assignment was removed The policy attained compliance (becomes successful) The BSM enable flag was turned off for the data source The data source host was unregistered The EPM master cell was replaced The BSM global switch enable flag was turned off The following information is displayed with the event: Chapter 6 Integrating with BMC Atrium 73 Configuring BSM integration Information Field data source information epm_datasourcename epm_status Description same description as appears in the EPM epm_DatabaseHost epm_DatabaseServer epm_DatabaseInstance epm_DatabaseNode epm_DatabaseName epm_HostName epm_OSName epm_DBMS epm_application epm_applicationGroup epm_customer epm_location epm_admin epm_adminGroup epm_policyName 74 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Configuring BSM integration Information Field Event specific information epm_PolicyInitialDateApplied Description The date and time the event is opened epm_PolicyLastDateApplied: The date and time the event is last updated epm_PolicyInitialVersion The initial version of the policy when the event is opened epm_PolicyLastVersion The version of the policy when the event was last updated epm_LastPolicyName The name of the policy when the event was last updated epm_PolicyDeletedDate When the event is closed because the policy item was deleted, this field contains the date when the policy item was deleted epm_PolicyItemDeletedDate When the event is closed because the policy was deleted, this field contains the date when the policy item was deleted epm_PolicyValue The latest policy item value epm_RealValue The latest value for this parameter epm_PolicyHub The host name of the policy hub epm_EventClosureReason The reason the event was closed, which is one of the following: ■ The policy item was deleted ■ The policy assignment was removed ■ The policy attained compliance (becomes successful) ■ The BSM enable flag was turned off for the data source ■ The data source host was unregistered ■ The EPM master cell was replaced ■ The BSM global switch enable flag was turned off Chapter 6 Integrating with BMC Atrium 75 Configuring BSM integration 76 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Chapter 7 7 Configuring e-mail notification This chapter presents the following topics: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Roadmap of e-mail notification configuration tasks . . . . . . . . . . . . . . . . . . . . . . . . How are e-mail notification messages triggered?. . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the SMTP server and testing e-mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing distribution lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing e-mail lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-mail notification states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 77 79 80 81 82 83 85 Overview The e-mail notification feature of BMC Recovery Manager enables you to automatically send e-mail messages to specified contacts when backup, recovery, and policy failures occur for specified data sources. For example, you can configure BMC Recovery Manager to send an e-mail message to a set of contacts on a distribution list whenever a backup fails on a certain Oracle database instance. Roadmap of e-mail notification configuration tasks Table 14 on page 78 describes the tasks you must perform to create e-mail lists and trigger e-mail notifications. Chapter 7 Configuring e-mail notification 77 Overview Table 14 E-mail notification configuration tasks Task Description Reference 1. Configure an SMTP server to send e-mails. When you configure the SMTP server, you “Configuring the SMTP can also send a test e-mail message to server and testing e-mail” verify that the server is working. on page 80 2. Create contacts to be added to distribution lists. You can add only contacts that you have created through EPM to distribution lists. “Managing contacts” on page 81 3. Create distribution lists from existing contacts. You create a distribution list by adding contacts that you have created to the list. You use distribution lists to create e-mail lists. “Managing distribution lists” on page 82 4. Create and activate e-mail lists When you create e-mail lists, you associate “Managing e-mail lists” on page 83 by performing the following one or more distribution lists with the tasks: e-mail list name and with one or more failure types: backup, recovery, or policy. ■ Create e-mail lists. You might create an e-mail list named EmailOracle, which associates backup ■ Assign e-mail lists to data sources monitored by BMC failures with a distribution list named DistBackup, and recovery failures with a Recovery Manager. distribution list named DistRecovery. ■ Activate e-mail lists. Then, you associate e-mail lists with specified data sources. For example, you might associate the EmailOracle e-mail list with the oradb1 data source. After you associate the EmailOracle e-mail list with the oradb1 data source, you then turn on the e-mail list to make it active. When a backup failure occurs on oradb1, BMC Recovery Manager sends an e-mail message to contacts on the DistBackup distribution list. When a recovery failure occurs on oradb1, BMC Recovery Manager sends an e-mail message to contacts on the DistRecovery distribution list. 78 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Overview How are e-mail notification messages triggered? In BMC Recovery Manager, e-mail notification messages are triggered when all of the following conditions have been met: ■ ■ ■ ■ ■ Table 15 an e-mail list exists that e-mail list is assigned to a data source that e-mail list is active for the data source the e-mail list associates at least one distribution list for the failure type at least one triggering event listed in Table 15 occurs E-mail notification triggering events (Part 1 of 2) Event Description e-mail list change You turn on an e-mail list for a data source that has an e-mail list assigned to it. BMC Recovery Manager sends an e-mail message if one current failure exists for the failure type (backup, recovery, or policy) for the specified data source. You update an e-mail list that is currently assigned to a data source. BMC Recovery Manager sends an e-mail message to any added contacts for any current failures on the assigned data sources for any failure type. backup failure The policy hub is notified of a new backup failure. BMC Recovery Manager sends an e-mail message if the data source has an e-mail list assigned and the e-mail list specifies a backup e-mail distribution list. recovery failure The policy hub is notified of a new recovery failure. BMC Recovery Manager sends an e-mail message if the data source has an e-mail list assigned and the e-mail list specifies a recovery e-mail distribution list. data import conflict results in overwriting of data You import data that contains conflicts with existing policy hub data and you have selected “Overwrite all” as the conflict resolution option. BMC Recovery Manager sends an e-mail message. policy failure The policy hub is notified of a new policy failure. BMC Recovery Manager sends an e-mail message if the data source has an e-mail list assigned and the e-mail list specifies a policy e-mail distribution list. Chapter 7 Configuring e-mail notification 79 Configuring the SMTP server and testing e-mail Table 15 E-mail notification triggering events (Part 2 of 2) Event Description policy change You assign a new or different policy to a data source that has an e-mail list assigned to it, and the policy fails. BMC Recovery Manager sends an e-mail message if the data source has an e-mail list assigned and the e-mail list specifies a policy e-mail distribution list. You update the policy definition that is assigned to a data source that has an e-mail list assigned, and the policy fails. BMC Recovery Manager sends an e-mail message if the data source has an e-mail list assigned, and the e-mail list specifies a policy e-mail distribution list. A policy audit occurs, and the audit results in a policy failure for a data source that has an e-mail list assigned; one of the policy attribute statuses is changed from N/A or Success to Failure. Note: BMC Recovery Manager does not send an e-mail message if the policy attribute status remains the same, or if the status is Success. Configuring the SMTP server and testing e-mail 1 To configure the SMTP server and to test e-mail, click Admin => Configure. The EPM Configuration dialog box is displayed. 2 Choose the E-mail tab. The E-mail configuration dialog box is displayed. 3 Select Enable all e-mail notifications to turn on all e-mail lists assigned to data sources. You must enable this switch to enable e-mail notifications. In the future, if you add new e-mail lists, they are turned on by default. Conversely, if you disable all e-mail notifications, even if an individual data source has e-mail notification enabled, no e-mail is sent. For more information about how the Enable all e-mail notifications switch affects e-mail notification, see Table 17 on page 85. 4 Enter SMTP server information as follows: 80 ■ host name and port number of the SMTP server ■ whether the SMTP server requires authentication, and, if so, the SMTP user name and password BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Managing contacts 5 Enter E-mail header information as follows: ■ In the From label field, enter the e-mail address from which all notification e-mail messages are to be sent. ■ In the Reply-to address field, enter the e-mail address to which responses are to be sent if the user replies to the e-mail notification message. 6 (optional) Enter Test configuration information as follows: ■ In the Recipient of test e-mail field, enter an e-mail address to which a test e-mail message is to be sent. BMC Recovery Manager uses this string as the To: field in the test e-mail message. ■ Click Test configuration to send a test e-mail message by using the SMTP server. 7 Click Apply to apply the e-mail configuration settings. For more information about configuring the SMTP server, see the BMC Recovery Manager Help. Managing contacts To manage contacts, click Admin => E-mail => Contact List. Each contact is displayed with its e-mail address, alias, and optional description. From the E-mail Contact List dialog box, you can create a new contact (New), modify an existing contact (Edit), or delete an existing contact (Delete). NOTE If you delete a contact that belongs to a distribution list, the contact is automatically deleted from any distribution list to which the contact belongs. You can also save (Export) the contact list in a local file or load (Import) a contact list from a local file in comma-separated value (CSV) format to EPM. Exporting a contact list stores the list in a local file in CSV format. Importing loads a CSV file containing contact list information.You also can share contact lists between policy hubs using the Admin => Export Policy Hub Data and Admin => Export Policy Hub Data commands. NOTE Importing contact lists from Microsoft Outlook export files, LDAP service export files, and other types of export files is not currently supported. Chapter 7 Configuring e-mail notification 81 Managing distribution lists Figure 7 shows a sample CSV file to which a contact list has been exported. a Figure 7 Example CSV import file [email protected],Joe Smith,Manager [email protected],Jane Smith [email protected],Charlie Green,Programmer NOTE ■ The third field (description) in the CSV import file is optional. ■ If the current contact list and the imported contact list contain inconsistencies, BMC Recovery Manager does not try to reconcile the lists. For example, if the current contact list contains an entry for John Doe with an e-mail address of [email protected], and the imported contact list contains an entry to John Doe with an e-mail address of [email protected], after the import is performed, both entries appear in the contact list. For more information about managing contact lists, see the BMC Recovery Manager Help. Managing distribution lists To manage distribution lists, click Admin => E-mail => Distribution List. Each distribution list is displayed with its name, information about the last person to modify the list, and optional description. Distribution lists are sorted by distribution list name. From the E-mail Distribution List dialog box, you can create a new distribution list (New), modify an existing distribution list (Edit), or delete an existing distribution list (Delete). NOTE If you delete a distribution list that is associated with an e-mail list, the distribution list is automatically deleted from any e-mail list to which it belongs. For more information about managing distribution lists, see the BMC Recovery Manager Help. 82 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Managing e-mail lists Managing e-mail lists An e-mail list associates an e-mail list name with one or more failure types: backup, recovery, or policy failure. For each failure type, an e-mail list associates one or more distribution lists with the failure type. For example, you might associate an e-mail list name, EmailList1, with distribution lists Dist1 and Dist2 for backup failures, and distribution lists Dist3 and Dist4 for recovery failures. Complete the tasks in Table 16 on page 84 to create and activate e-mail lists. Then, when a failure occurs for a specified data source, the e-mail list triggers an e-mail notification message that is sent to the contacts on the associated distribution lists for that failure type. For example, Figure 8 on page 83 shows an e-mail list, EmailList1. Figure 8 Relationship between e-mail list, failures, distribution list, and contact list If a backup failure occurs for the data source associated with e-mail list EmailList1, BMC Recovery Manager sends e-mail notification messages to the contacts on the associated distribution lists: ■ Dist1 ([email protected], [email protected], and [email protected]) ■ Dist2 ([email protected], [email protected], and [email protected]) Chapter 7 Configuring e-mail notification 83 Managing e-mail lists Table 16 Managing e-mail lists Task 1. Configure e-mail notification. Description Choose Admin => Configure. Select the E-mail tab. Notes: ■ You must configure the SMTP server before you can turn on an e-mail list. ■ On the E-mail configuration dialog box, you must select Enable e-mail notifications to enable e-mail notification messages. 2. Create an e-mail list. Choose Admin => E-mail => New E-mail List. 3. Edit an e-mail list. Choose Admin => E-mail => Edit E-mail List 4. Delete an e-mail list. Choose Admin => E-mail => Delete E-mail List 5. Assign an e-mail list to a data source. On the BMC Recovery Manager console, select and right-click the row or rows for the data sources to which you want to assign an e-mail list. Choose Assign E-mail List, and choose an e-mail list. The e-mail list name appears in the E-mail column. By default, the e-mail list is turned off. Notes: 6. Turn on an assigned e-mail list. ■ If an e-mail list is already assigned to the data source, the original assignment is removed, and the new e-mail list is assigned to the data source. ■ You can assign only one e-mail list per data source. To turn on the e-mail list, select and right-click the row or rows for the data sources for which you want to turn on an e-mail list. Choose E-mail => On. The value On appears in the E-mail column. 7. Turn off an assigned e-mail list. To turn off the e-mail list, select and right-click the row or rows for the data sources for which you want to turn off an e-mail list. Choose E-mail => Off. The value Off appears in the E-mail column. 8. Remove an e-mail list assignment. On the BMC Recovery Manager console, select and right-click the row or rows for the data sources for which you want to remove an e-mail list assignment. Choose Remove E-mail List Assignment. The e-mail list name is removed from the E-mail list column. The value Off appears in the E-mail column. 84 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Managing e-mail lists E-mail notification states Table 17 shows the icons for the various states for e-mail notification. To globally enable e-mail notification messages, select Enable e-mail notifications on the E-mail configuration dialog box. Table 17 E-mail notification states E-mail column E-mail list column Conditions Outcome dimmed E-mail notification is not configured, and by default, Enable e-mail notifications is disabled. E-mail notification messages are not sent. dimmed not dimmed ■ E-mail notification is configured, and Enable e-mail notifications is disabled. ■ An e-mail list is not assigned to the data source. ■ E-mail notification is configured, and Enable e-mail notifications is enabled or disabled. ■ An e-mail list is assigned to the data source. ■ E-mail column is turned off. ■ E-mail notification is configured, and Enable e-mail notifications is enabled or disabled. ■ An e-mail list is assigned to the data source. ■ E-mail column is turned on. ■ E-mail notification is configured, and Enable e-mail notifications is enabled. ■ An e-mail list is not assigned to the data source. E-mail notification messages are not sent. E-mail notification messages are not sent. E-mail notification messages are sent. E-mail notification messages are not sent. Chapter 7 Configuring e-mail notification 85 Managing e-mail lists 86 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Chapter 8 Using BMC Recovery Manager in a clustered environment 8 This chapter discusses the issues that exist when displaying data for clustered computers through the EPM. The following clustered environments are discussed: Server clustering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Specifying a host name for a computer in a cluster . . . . . . . . . . . . . . . . . . . . . . . . . Displaying clustered servers as a group in the EPM . . . . . . . . . . . . . . . . . . . . . . . . Resolving a host registration by cluster name failure . . . . . . . . . . . . . . . . . . . . . . . Clustering in a RAC or failover environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting services during a node failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 88 89 89 91 92 Server clustering In a clustered environment, multiple servers are linked together to handle variable workloads if a server fails. Sometimes, BMC Recovery Manager cannot resolve the name of a computer in a cluster. For example, a database server host might return a cluster name rather than the adapter name as the host name. The symptom of this problem is that when you attempt to register a database server host, the registration fails. For example, a cluster named mcs123 is configured with multiple adapters. The Domain Name Server (DNS) does not serve the cluster name, but it does serve the names of the adapters in the cluster. NOTE The DNS server maintains a database of domain names (host names) and their corresponding IP addresses. Chapter 8 Using BMC Recovery Manager in a clustered environment 87 Server clustering BMC Recovery Manager provides host name parameters (that you specify in a property file) to indicate the host name by which the policy hub is to recognize a computer in a cluster. Specifying a host name for a computer in a cluster BMC Recovery Manager provides parameters in the ebrdr.cfg and ebrdc.cfg files that let you specify a host name for a computer in a cluster. After you have set the host name for a computer in a cluster, you can group the display of data sources by cluster name in the EPM. See “Displaying clustered servers as a group in the EPM” on page 89. To change the name by which the EPM recognizes a host computer, edit the host name parameters shown in Table 18 on page 88. ■ To change the policy hub host name, edit these parameters in the ebrdr.cfg property file using the EPM configuration dialog box. For information about editing configuration parameters with the EPM configuration dialog box, see “To configure the policy hub” on page 52. ■ To change the database server host name, edit these parameters in the ebrdc.cfg file located in the JBoss installation directory, $DTBASE/common/jboss/3.2.4/server/bmc/conf/. Table 18 Host name parameters Parameter Description DNS Host Name or ebrDnsHostName Set this parameter to the name by which BMC Recovery Manager is to recognize this host. IP Address or ebrIpAddress Set this parameter to the IP address of the host. Use IP Address or ebrUseIpAddress Set this flag to true to indicate that BMC Recovery Manager is to use the IP address to identify the host. When this flag is set to true, BMC Recovery Manager uses the : to communicate with the host, instead of its host name, which is useful when BMC Recovery Manager has an issue resolving the specified host computer with a correct IP address. NOTE Stop and start the JBoss service on the policy hub or the database server host to update these parameters. 88 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Server clustering Displaying clustered servers as a group in the EPM After you set the host name parameters in the ebrdr.cfg or ebrdc.cfg file, you can use the EPM to display the clustered computers as a group. To display clustered servers as a group 1 In the EPM, for each host that you want to display as part of a cluster group, double-click the cell in the Cluster column, and enter a name for the cluster. 2 Choose Display => Set Up Groups. 3 In the Set Up Groups dialog box, from the First Column list select Cluster as the primary column by which you want to group the data sources. 4 (optional) If you want to group the data sources within the primary column, select a column in the Second Column list. 5 Click OK. NOTE ■ If you sort columns after grouping data sources, the data sources are sorted within their group. The group has precedence over sort order. ■ The EPM remembers the most recently used group criteria. You can choose the Group by => Group command to use previously defined grouping criteria. Resolving a host registration by cluster name failure If the EPM fails to register a host by its cluster name, you must modify configuration files on the policy hub and the database server host, and then register the database server host by its IP address. To modify the configuration on the policy hub In the examples in this procedure, replace the variable with the actual IP address of the policy hub. Chapter 8 Using BMC Recovery Manager in a clustered environment 89 Server clustering 1 On the policy hub, force the RMI stubs to bind a public IP address by editing the \jboss\4.0.2\conf\wrapper.conf file and adding the lines shown in bold in the following figure. Replace with the public IP address of your policy hub. # Force JBoss services to bind a public IP address # Java Additional Parameters wrapper.java.additional.1=-Dprogram.name=run.bat wrapper.java.additional.2=-Xincgc wrapper.java.additional.3=-Djava.rmi.server.hostname="" # Application parameters. Add parameters as needed starting from 1 wrapper.app.parameter.1=org.jboss.Main wrapper.app.parameter.2=-c wrapper.app.parameter.3=%JBOSS_CFG% wrapper.app.parameter.4=--host= 2 On the policy hub, edit the ebrdr.cfg file and add the lines shown in the following figure: ebrDnsHostName=drHostName ebrUseIpAddress=true ebrIpAddress= Ensure that the drHostName parameter specified in the ebrdr.cfg file is visible to the Domain Name Server (DNS). 3 On the policy hub, edit the hosts file and add the public IP address of the policy hub and a valid host name, as shown in the following figure: 127.0.0.0 localhost drHostName alias To modify the configuration on the database server host In the examples in this procedure, replace the variable with the actual IP address of the database server host. 1 On the database server host, force the RMI stubs to bind a public IP address by editing the \common\jboss\3.2.4\bin\run_bmc.sh file as follows: A Modify JAVA_OPTS as shown in the following figure. Replace the with the public IP address of your database server host. (old) JAVA_OPTS=" -Xms128m -Xmx1024m " (new) JAVA_OPTS=" -Xms128m -Xmx1024m -Djava.rmi.server.hostname=” 90 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Clustering in a RAC or failover environment B Add the –host option after $JBOSS_CFG, as shown in the following figure: (old) nohup su - ${RUN_ID} -c "exec $JAVACMD $JAVA_OPTS $JBOSS_OPTS -classpath $CLASSPATH org.jboss.Main -c $JBOSS_CFG " (new) nohup su - ${RUN_ID} -c "exec $JAVACMD $JAVA_OPTS $JBOSS_OPTS -classpath $CLASSPATH org.jboss.Main -c $JBOSS_CFG --host= " 2 On the database server host, edit the ebrdc.cfg file and add the lines shown in the following figure: ebrDnsHostName=mnHostName ebrUseIpAddress=true ebrIpAddress= 3 Register the database server host by using the IP address that you specified in the database server host configuration files. Clustering in a RAC or failover environment In a RAC or failover environment, multiple hosts share the same Oracle database. The EPM, however, presents one row for each host, displayed by fully qualified name. BMC Recovery Manager generates fully qualified names for each host because backup and recovery data comes from these hosts, and in the EPM, the host name is the first element in the fully qualified name. BMC Recovery Manager provides a parameter that enables you to override the first element (host name) of the fully qualified name so that the EPM displays all hosts in a single row. To display a set of hosts as a single cluster row 1 If the EPM already displays a row for each host, unregister these hosts. 2 On each node in the cluster except for the primary node, add the following parameter to the ebrdc.cfg file located in the JBoss installation directory: ebrDatabaseHostName= Chapter 8 Using BMC Recovery Manager in a clustered environment 91 Clustering in a RAC or failover environment NOTE ■ You do not have to use the primary host name as . To specify a different name, set the ebrDatabaseHostName parameter to the name in the ebrdc.cfg file on all hosts. ■ To update the parameters, stop and start the JBoss service by using the shutdown.sh and startup.sh scripts in the $DT_OBACKTRACK_HOME/ebr/bin directory. 3 Through the EPM, register all hosts. A single consolidated row appears for all the backups and recoveries performed by any hosts in the cluster, with the name you specified for the ebrDatabaseHostName parameter. For example, two hosts (such as node1.bmc.com and node2.bmc.com) might be displayed as a single node, such as node1.bmc.com. This display results from adding the following parameter to the ebrdc.cfg file: ebrDatabaseHostName=node1.bmc.com Starting services during a node failover In certain cases, you must start services on the secondary node to ensure that the services continue to run during a node failure. If a node fails, start the JBoss service, which is required for the Enterprise Policy Monitor (EPM). To start the JBoss service 1 Copy all entries following the #BMC-PDM-DELIMITER line from the /etc/bmc_pdm file on the source computer to target computer. 2 Start the JBoss service by running the following script: $DTBASE/obacktrack/ebr/bin/startup.sh NOTE If you want to start the JBoss service automatically after every reboot, copy the entry for the JBoss service from the /etc/inittab file on the source computer to the target computer. This entry begins with the string j:, where is a number. 92 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Chapter 9 9 Troubleshooting This chapter presents the following topics: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Verifying installation of services on the database server host . . . . . . . . . . . . . . . . . . . 94 Resolving BMC Recovery Manager port conflicts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Displaying and changing port numbers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Displaying database server host port numbers examples. . . . . . . . . . . . . . . . . . . . 98 Stopping and starting the policy hub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Starting and stopping BMC Recovery Manager services in the database server host. . 100 Automatically restarting BMC Recovery Manager services . . . . . . . . . . . . . . . . . 101 Manually starting and stopping BMC Recovery Manager services . . . . . . . . . . 102 Manually migrating an existing data file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Troubleshooting database server host registration. . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Modifying data collection configuration parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Clearing the Java cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Resolving a Java out-of-memory error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Overview If the installation or subsequent launch of one of the BMC Recovery Manager components causes unexpected results, use the procedures in this chapter to help determine the source of the problem. Chapter 9 Troubleshooting 93 Verifying installation of services on the database server host Verifying installation of services on the database server host If you cannot connect to the database server host, verify that the BMC Recovery Manager services are installed and running on the database server host by running the diagnostic utility. To verify that BMC Recovery Manager services are installed on Windows 1 At the installation directory for the data collection services, change to the diagUtil directory: $DTBASE\xbacktrack\ebr\support\diagUtil $DTBASE is the base installation directory for BMC SQL-BackTrack. 2 Run the diagnostic utility by executing the run.bat script with the -check_install option to verify that the following components are installed and running on the database server host: ■ ■ ■ data collection services (includes Java Runtime Environment) metric API (MAPI) library metric data collector The diagnostic utility reports whether the verification checks for the components succeeded or failed. If any components are not installed or not running, the diagnostic utility issues an error and records diagnostic information in a file. The utility displays the file name and location on screen, as in the following example: Log file Name:C:\Documents and Settings\\Local Settings\Temp\epm_diag_msg49289.log If any of these services is not running, see “Starting and stopping BMC Recovery Manager services in the database server host” on page 100. To verify that BMC Recovery Manager services are installed on UNIX 1 At the installation directory for the BMC Recovery Manager services, change to the diagUtil directory: $DTBASE/xbacktrack/ebr/support/diagUtil $DTBASE is the base installation directory for BMC SQL-BackTrack. 94 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Resolving BMC Recovery Manager port conflicts TIP To find out where you installed the BMC Recovery Manager services on the database server host, look at the EBRDC__<32/64>_installDir entry in the /etc/bmc_pdm file. 2 Run the diagnostic utility by executing the run.sh script with the -check_install option to verify that the following components are installed and running on the database server host: ■ ■ ■ data collection services (includes Java Runtime Environment) metric API (MAPI) library metric data collector The diagnostic utility reports whether the verification checks for the components succeeded or failed. If any components are not installed or not running, the diagnostic utility issues an error and records diagnostic information in a file. The utility displays the file name and location on screen, as in the following example: Diagnostic information in file: /var/tmp/diag_info61901.zip NOTE If the host contains multiple installations of the policy hub, you must use the -install_loc option to specify the installation that you want to check. To display the complete list of options available for the run.sh utility, you can execute the utility with the -help option. If any of these services is not running, see “Starting and stopping BMC Recovery Manager services in the database server host” on page 100. Resolving BMC Recovery Manager port conflicts Any other products that use ports must be running when you install BMC Recovery Manager. Otherwise, the installation program does not detect port conflicts. If the other products are not running when you install BMC Recovery Manager and you experience port conflicts when attempting to start the other products, perform one of the following workarounds: ■ Change the port number that your other application is using before running BMC Recovery Manager. ■ Edit the appropriate configuration file to change the port number for the EPM client. Chapter 9 Troubleshooting 95 Displaying and changing port numbers Editing the configuration files is not recommended and should be done only if you cannot otherwise resolve a port conflict. After installing the product, stop the BMC JBoss 4.0.2 service before editing the configuration files. Restart the service after you have finished editing the files. The following files contain port numbers that you can edit: — server.xml contains the HTTP and servlet engine port numbers. — repdb.properties contains the port number used by the internal BMC Recovery Manager repository. If you change the HTTP port number, you must communicate the new port number to remote users. You must also modify the command that is invoked to launch the console from the Start menu on all client computers that use that application server. Displaying and changing port numbers If you experience port conflicts when using BMC Recovery Manager and other products, you can change the port numbers that the other products are using, or you can use the emportconfig utility to change the ports that the BMC Recovery Manager components are using. The epmPortConfig.bat and epmPortConfig.sh files are automatically installed when you install Enterprise Policy Monitor or the Recovery Manager for Database Server Host. The scripts are located in the following directories: ■ /dataRepository/bin for Policy Hub ■ $DTBASE/xbacktrack/ebr/bin for Recovery Manager for Database Server Host. To change the ports that the BMC Recovery Manager components are using, enter the following command: epmportconfig [-tier auto|policyHub|managedNode] [[-show [all|portName]| [-modify [-targetport |-targetportRange :]] [-restart] Table 19 shows the options for the emportconfig command. 96 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Displaying and changing port numbers Table 19 Options for the epmportconfig utility (Part 1 of 2) Option and arguments Description -tier auto|policyHub|managedNode specifies the component to configure: ■ auto specifies the ports for all BMC Recovery Manager components currently installed on the computer (default) ■ policyHub specifies the EPM component ports ■ managedNode specifies the ports for the database server If you do not use this option, epmportconfig automatically detects and configures the ports for the BMC Recovery Manager components currently installed on the computer. -show all|portName lists the external ports currently configured for the component You can list all of the external ports or a specific external port. Valid portnames are: ■ ■ ■ ■ ■ ■ rmio jndi http rmi uil pool Use either this option or -modify, but not both. Chapter 9 Troubleshooting 97 Displaying and changing port numbers Table 19 Options for the epmportconfig utility (Part 2 of 2) Option and arguments Description -modify all|portName -targetport modifies the external ports currently configured for BMC Recovery Manager portNum or -modify all|portName -targetportRange You can list all of the external ports or a specific external start:end port. Valid portnames are: ■ ■ ■ ■ ■ ■ rmio jndi http rmi uil pool Specify a port range to modify one or all of the external ports, or modify an individual external port by specifying a single port number. The utility validates that a port number is not in use prior to assigning it to a port. For a port range, the utility assigns each external port to the first available port number from the target port range. Use either this option or -show, but not both. restarts the services, making the port changes take effect immediately -restart If you do not use this option, the changes take effect when you restart the service manually or when the computer is rebooted. Displaying database server host port numbers examples Examples 1 and 2 are Windows examples; examples 3 and 4 are Linux examples. Example 1 At the command line, type: \dataRepository\bin>epmPortConfig.bat The port configuration utility displays all the ports being used by the Policy Hub and Recovery Manager in the database server host. Output: bmc-epm-rmio bmc-epm-http 98 : : 54444 8082 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Displaying and changing port numbers bmc-epm-jndi bmc-epm-rmi bmc-epm-uil bmc-epm-pool : : : : 12000 51098 58093 54445 Example 2 At the command line, type: \dataRepository\bin>epmPortConfig.bat -show rmi The port configuration utility displays the port number for the port s being used by the Recovery Manager in the database server host. Output: bmc-epm-rmi : 51098 Example 3 At the command line, type: # $DTBASE/xbacktrack/ebr/bin/epmPortConfig.sh -modify jndi targetport 12002 Output: Port in use false JNDI port is modified bmc-epm-jndi : 12002 Example 4 At the command line, type: # $DTBASE/xbacktrack/ebr/bin/epmPortConfig.sh -modify all targetrange 12005:13000 Output: Managed Node Ports RMI Port is modified bmc-epm-rmi : 12006 RMIObject Port is modified bmc-epm-rmio : 12007 JNDI Port is modified bmc-epm-jndi : 12005 UIL Port is modified bmc-epm-uil : 12009 EPMPool Port is modified Chapter 9 Troubleshooting 99 Stopping and starting the policy hub bmc-epm-pool : 12010 HTTP Port is not modified Stopping and starting the policy hub The policy hub is started automatically when you install it; however, in certain situations you might need to manually stop and start the policy hub. For example, if you want to manually recover the policy hub, you must first shut it down. ■ On Linux, use the following command: /etc/init.d/epm {start|stop|restart} ■ On Windows, use the Start and Stop buttons from the Services window to start and stop the BMC EPM Policy Hub service. The script is located in the /bin directory (where represents the directory where the policy hub is installed). NOTE ■ During an automatic backup, the policy hub is shut down. Ensure that the policy hub is not in use during the scheduled backups. Starting and stopping BMC Recovery Manager services in the database server host If you receive an error message indicating a possible problem with the BMC Recovery Manager services installed on the database server host, you can stop and restart these services. 100 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Starting and stopping BMC Recovery Manager services in the database server host Automatically restarting BMC Recovery Manager services To use this feature, edit the following three parameters in the $DTBASE/common/jboss/3.2.4/server/bmc/conf/ebrdc.cfg file on each on database server host you want to restart automatically: ■ ■ ■ JBossTimer JBossTimerIntervalInDays JBossTimerHourOfDay For more information about these parameters, see Table 20. Table 20 Parameters for automatic restart of SQL-BackTrack services on a managed node Parameter Description JBossTimer specifies whether to automatically restart the JBoss 3.2.4 service on the database server host at the specified interval ■ ■ JBossTimerIntervalInDays set to true to restart automatically set to false to restart manually (default). (used only if JBossTimer is true) Specifies the number of days between JBoss 3.2.4 service restarts on the database server host. Valid parameter values are 0 or any integer greater than 0. Typical values: ■ 0—the service is restarted every day (including today) ■ 1—the service is restarted every day (not including today) ■ 5—the service is restarted every 5 days The default value is 1. JBossTimerHourOfDay (used only if JBossTimer is true) Specifies the time of day the EPM managed node JBoss 3.2.4 service is restarted on the database server host. Valid parameter values are 0 (12:00 A.M.) through 23 (11:00 P.M.) The default value is 5. Chapter 9 Troubleshooting 101 Manually migrating an existing data file NOTE Use a text editor to edit the ebrdc.cfg file and list the parameters on separate lines. You do not need to stop and restart the BMC Recovery Manager services after you have set the JBossTimer parameters. The parameter values are read automatically. The default interval for checking the parameters is 60 seconds. Manually starting and stopping BMC Recovery Manager services ■ On UNIX, use the startup.sh and shutdown.sh scripts in $DTBASE/xbacktrack/ebr/bin. ■ On Windows, use the Start and Stop buttons from the Services window to start and stop the BMC JBoss 3.2.cfg bmc service $DTBASE is the base installation directory for BMC SQL-BackTrack. Manually migrating an existing data file If you experience problems with an existing data file during policy hub installation, you can manually migrate a data file by using the ebrdbmigrate utility. To manually migrate a data file on Windows hosts 1 From Services, shut down the policy hub service by right-clicking the BMC EPM Policy Hub 2.9.00 service and choose Stop. 2 Locate the migration utility in the following policy hub directory: \dataRepository\bin The default installation directory is located here: C:\Program Files\BMC Software\BMC Recovery Manager\Enterprise Policy Management 3 Execute the ebrdbmigrate.bat utility with the following required information listed in the order shown: 102 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Troubleshooting database server host registration A The absolute path of the source data file that you want to migrate. NOTE The existing data file must reside on the local host. You cannot migrate a data file from a remote host. B The name and location for the new data directory for the new policy hub installation. This data file will be the end result of the migration. You can use the same name and location that you used for the existing data file. If you do, BMC Recovery Manager renames the existing data file to datadir.orig and makes datadir the migrated file. C A name and directory location for the output file that BMC Recovery Manager creates to record the migration and its results. Your input using the ebrdbmigrate.bat utility would be similar to the following example: ebrdbmigrate.bat "c:\Program Files\BMC Software\BMC Recovery Manager\Enterprise Policy Management\dataRepository\data\ebrderby" "c:\Program Files\BMC Software\BMC Recovery Manager\Enterprise Policy Management\dataRepository\data\ebrderby" c:\migrate.log 4 From Services, start the policy hub service by right-clicking the BMC EPM Policy Hub 2.9.00 service and choosing Start. Troubleshooting database server host registration During registration of the database server hosts, you may encounter failure messages in the Database Server Host Registration Status dialog box. Use Table 21 on page 104 to determine the user action in the event you receive any of the messages provided. Chapter 9 Troubleshooting 103 Troubleshooting database server host registration Table 21 Database server host registration error messages Message Explanation and user response BMCEBR6555401E: BMC Recovery Manager could not resolve the host name provided. Explanation: BMC Recovery Manager could not resolve the database server host name using the network Domain Name Service. User response: Perform one or more of the following tasks: ■ Verify that the host name can be resolved using Domain Name Service. ■ Verify the firewall configuration. Ensure that the policy hub host can connect to the database server host and that the database server host can connect to the policy hub host. ■ Provide the IP address for the database server host you are trying to register. ■ Verify that the port number is valid. BMCEBR6555402W: The discovered Explanation: There may be a misconfigured firewall environment host could not respond back to the BMC or a DNS environment where the policy hub can see the database Recovery Manager. server host but the database server host cannot see the policy hub. User response: Perform the following tasks: ■ Verify that the host name can be resolved using Domain Name Service. ■ Verify the firewall configuration. In the event of a misconfigured DNS environment or firewall, the registration process will complete, and the policy hub can proceed to gather metrics using an alternate communication method. However, you may experience slower performance using the alternate method than if the DNS or firewall environment were properly configured. If you modify the firewall or DNS configuration, you must reregister the database server host before the product can resume gathering metrics. 104 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Modifying data collection configuration parameters Modifying data collection configuration parameters The parameters used for configuring data collection are located in two configuration files on the database server host. Both files are named ebrdc.cfg but they are located in different directories. All of the parameters in the ebrdc.cfg files have built-in default values that work in your environment. Depending on your specific requirements, you might want to modify the values for one or more parameters in the ebrdc.cfg files. Before you begin Before editing the ebrdc.cfg files, review the following usage considerations: ■ If you need assistance locating the recovery management data collection services, see “Installing BMC SQL-BackTrack with BMC Recovery Manager services” on page 25. ■ Each BMC SQL-BackTrack installation on your database server host has a separate ebrdc.cfg file. ■ Use a text editor to edit the ebrdc.cfg file. ■ List parameters on separate lines. Table 23 describes the parameters in the ebrdc.cfg file that is located in the $DTBASE/common/jboss/3.2.4/server/bmc/conf directory where $DTBASE is the base installation directory for BMC SQL-BackTrack. Table 22 Configuration parameters for data collection on the database server host in $DTBASE/common/jboss/3.2.4/server/bmc/conf/ebrdc.cfg (Part 1 of 2) Parameter Description ARCHIVE_FILE= location of the archive.log file The default location for this file on the database server host is as follows: $DTBASE/common/jboss/4.0.2/server/bmc/run ARCHIVE_GENERATIONS= number of generations of the archive.log file to keep The default is two generations. Chapter 9 Troubleshooting 105 Modifying data collection configuration parameters Table 22 Configuration parameters for data collection on the database server host in $DTBASE/common/jboss/3.2.4/server/bmc/conf/ebrdc.cfg (Part 2 of 2) Parameter Description ARCHIVE_SIZE= size of the archive.log file The default file size is 500 MB. The default location for this file on the database server host is as follows: $DTBASE/common/jboss/4.0.2/server/bmc/run autodiscovery_timer_delay_in_seconds= a time interval to limit the amount of time that the BMC Recovery Manager services have after they start up to discover any new or changed information about the BMC SQL-BackTrack installations on the database server host The default value is 600 seconds. autodiscovery_timer_interval_in_seconds= time (in seconds) between the initial startup of the AutoDiscovery Timer and any subsequent startups JBossTimer specifies whether to automatically restart the JBoss 3.2.4 service on the database server host at the specified interval ■ ■ JBossTimerIntervalInDays set to true to restart automatically set to false to restart manually (default). (used only if JBossTimer is true) Specifies the number of days between JBoss 3.2.4 service restarts on the database server host. Valid parameter values are 0 or any integer greater than 0. Typical values: ■ 0—the service is restarted every day (including today) ■ 1—the service is restarted every day (not including today) ■ 5—the service is restarted every 5 days The default value is 1. JBossTimerHourOfDay (used only if JBossTimer is true) Specifies the time of day the EPM managed node JBoss 3.2.4 service is restarted on the database server host. Valid parameter values are 0 (12:00 A.M.) through 23 (11:00 P.M.) The default value is 5. 106 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Modifying data collection configuration parameters Table 23 describes the parameters in the ebrdc.cfg file that is located in the $DTBASE//ebr/config/ directory where $DTBASE is the base installation directory for BMC SQL-BackTrack. Table 23 Configuration parameters for data collection on the database server host in the $DTBASE//ebr/config/ebrdc.cfg file (Part 1 of 3) Parameter Description collection=[enabled | disabled] flag that specifies whether the BMC Recovery Manager services collect metric data for the BMC SQL-BackTrack installation By default, data collection is enabled. If you do not want to collect or view metric data for the BMC SQL-BackTrack installation, change this value to disabled. defaultDataCollectorServicePort= port that the BMC Recovery Manager services on the database server host (including the JRE) uses The default port is 7777. You can use this parameter to specify a different port number for the BMC Recovery Manager services. enable_shortlived=[true | false] flag that specifies whether metric collection is enabled for BMC SQL-BackTrack tasks, such as transaction log backups and restores, that occur frequently and generate a large amount of data The default value is false to filter out data associated with these types of tasks. mdc_concurrent_tasks_margin= margin by which the memory allocated for concurrent tasks associated with a job can be increased, if necessary By default, the margin is 25 percent. mdc_log_level=[ 1 | 2 | 4 | 8 | 16] tracing level for the BMC Recovery Manager services as follows: ■ ■ ■ ■ ■ 1—fatal 2—fatal and error 4—fatal, error, and warning (the default value) 8—fatal, error, warning, and informational 16—fatal, error, warning, informational, and debug Note: To enable tracing, set the mdc_use_log_level_from_config_file parameter to 1. mdc_max_concurrent_tasks= maximum number of concurrent tasks that the BMC Recovery Manager services track for any BMC SQL-BackTrack job By default, the services allocate sufficient memory to collect data associated with 100 concurrent tasks. Chapter 9 Troubleshooting 107 Modifying data collection configuration parameters Table 23 Configuration parameters for data collection on the database server host in the $DTBASE//ebr/config/ebrdc.cfg file (Part 2 of 3) Parameter Description mdc_max_waittime_for_final_remote_data= time (in seconds) that the BMC Recovery Manager services on the primary host waits to receive job-completion notification from the remote host The default value is 100 seconds. mdc_publish_sub_task_details=[0 | 1] mdc_retry_connect_count_for_slave= flag that specifies whether subtask details are collected and displayed in the EPM ■ If this parameter is set to 1, subtask details are collected and available for display. ■ The default value is 0 so that subtask details are not collected. how many times the BMC Recovery Manager services on the remote host attempts to reconnect to the BMC Recovery Manager services on the primary host The default value is 20. mdc_retry_connect_interval_for_slave= flag that specifies at what interval the BMC Recovery Manager services on the remote host attempts to reconnect to the BMC Recovery Manager services running on the primary host The default value is 1 second. mdc_sampling_interval= interval at which the BMC Recovery Manager services reads the data reported by BMC SQL-BackTrack processes The default value is 10 seconds. mdc_timeout_period= timeout interval for BMC SQL-BackTrack processes If the BMC Recovery Manager services do not receive data from a BMC SQL-BackTrack process during the timeout interval, the services assume that the process has stopped responding, issue a warning to the policy hub, and then terminate. The default value is 3600 seconds. 108 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Clearing the Java cache Table 23 Configuration parameters for data collection on the database server host in the $DTBASE//ebr/config/ebrdc.cfg file (Part 3 of 3) Parameter Description mdc_use_log_level_from_config_file=[0 | 1] flag that specifies whether tracing is enabled for the BMC Recovery Manager services ■ If tracing is enabled, messages are recorded in the mdc.log file based on the tracing level defined in the mdc_log_level parameter. ■ By default, this parameter value is 0 and tracing is not enabled. Note: The mdc.log file is located in the $DTBASE//ebr/logs directory. mdc_warning_timeout= warning timeout period for the BMC Recovery Manager services If the BMC Recovery Manager services do not receive data from a BMC SQL-BackTrack process during the warning timeout interval, the services issue a warning message to the policy hub. The default value is 1800 seconds. mdcOperate_in_test_mode=[0 | 1] flag that specifies whether to run the BMC Recovery Manager services in test mode ■ The default value is 0 and test mode is not enabled. ■ Set this parameter to 1 to run the BMC Recovery Manager services in test mode only if you are requested to do so by BMC Software Customer Support. Clearing the Java cache If you are experiencing unexpected behavior after upgrading any product in the BMC Recovery Management family, you should clear the Java cache on the client. To clear the cache, complete the following steps: 1 From the client computer, open the Microsoft Windows Control Panel. 2 Open the Java Plug-in Control Panel. 3 On the Cache tab, click the Clear button. 4 Click Yes on the confirmation dialog box. Chapter 9 Troubleshooting 109 Resolving a Java out-of-memory error Resolving a Java out-of-memory error On an HP platform, if the kernel setting is too low, the server.log on the database server host report the following error: Problem starting service ebrdc:service=DSService java.lang.OutOfMemoryError: unable to create new native thread To resolve this error, increase the thread memory usage value to provide more memory per thread. The default setting is 64 KB, which is too low for BMC Recovery Manager. Contact your HP system administrator to adjust the setting. Because this is a kernel setting, restart the JBoss service on the database server host. You might also have to restart the database server host after adjusting this setting. For information about the parameters, see the following links: 110 ■ http://h21007.www2.hp.com/dspp/tech/tech_TechDocumentDetailPage_IDX/1,1 701,1616,00.html ■ http://h21007.www2.hp.com/dspp/tech/tech_TechDocumentDetailPage_IDX/1,1 701,1602,00.html BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Appendix A Installing third-party drivers for generating reports A This appendix presents the following topics: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating an alias for the driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 111 112 112 Overview You can use third-party reporting tools with the BMC Recovery Manager product by using ODBC connections to the policy hub. This appendix explains how to install and configure an ODBC driver to access the BMC Recovery Manager policy hub through third-party connections. Installing the drivers Use the following instructions to install the DB2 Run Time Client driver. 1 Go to the following url: https://www14.software.ibm.com/webapp/iwm/web/preLogin.do?source=rtcl 2 Complete the IBM registration process. 3 For the en_US_setup.exe file, click Download now. Appendix A Installing third-party drivers for generating reports 111 Creating an alias for the driver 4 On the download dialog box, click Open. 5 On the DB2 Setup wizard, click Next. 6 On the license agreement page, accept the terms of the license agreement and click Next. 7 On the installation type page, select Typical and click Next. 8 Click Install. 9 Click Finish. 10 Complete the configuration steps in the next section to configure the DB2 Run Time Client driver. Creating an alias for the driver Use the following instructions to create an alias for the DB2 Run Time Client driver to use to configure the driver. 1 Enter the following command at a command prompt: db2cmd This command opens the DB2 CLP (command line processor) window. 2 In the DB2 CLP window, change to the %PH_INSTALL_DIR%\bin directory. 3 Run the db2env command and make a note of the alias that has been created. You will needd the alias to configure the driver. Configuring the driver Use the following instructions to configure an ODBC driver for third-party connections after you have installed the ODBC driver. 112 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Configuring the driver Before you begin ■ You must install the Microsoft ODBC driver manager on the Windows host on which you are installing and configuring the ODBC driver. The Microsoft ODBC driver manager is used by the configuration process to enable the Data Sources administration interface in the Control Panel. ■ If you have multiple BMC Recovery Manager policy hubs, you must configure a different data source for each policy hub to which you want to connect using ODBC. 1 Using the Windows Control Panel, in Administrative Tools, click the Data Sources (ODBC) icon to launch the ODBC Data Source Administrator. 2 On the User DSN tab, click Add. The Create New Data Source dialog box opens. 3 Select the IBM DB2 ODBC DRIVER driver from the list and click Finish. The IBM DB2 ODBC DRIVER dialog box opens. 4 In the Data source name field, enter a name for the data source. 5 In the Database alias pulldown, select the alias that you created with the db2env command. 6 In the Description field, enter a description. 7 Click OK. 8 On the ODBC Data Source Administrator dialog box, select the new data source and click Configure. 9 On the CLI/ODBC Settings dialog box, perform the following steps: A Choose Supply user ID and password. B For User ID, enter ebruser. C For Password, enter ebruser. D Click Connect to test the connection. E Click OK. Appendix A Installing third-party drivers for generating reports 113 Configuring the driver 114 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Appendix B B Policy hub data reference This appendix presents the following topics: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Understanding the data model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Querying the policy hub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Attribute table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BackTrackInstall table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BackTrackInstall_DataSourceDetail table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DataModel table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DataSource table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DataSourceAttribute table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DataSourceDetail table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Host table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LicenseType table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Metric data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BackTrackConfig table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DataSourceTaskPhase table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DataSourceTaskProperty table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Job table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . JobType table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Task data tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TaskAlert table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TaskMethod table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TaskMode table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TaskProperty table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TaskScope table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TaskStatus table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TaskDataSource table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Policy data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BackupPolicyDetail table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DataSourcePolicyHistory table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Policy table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PolicyDetail table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PolicyStatus table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PolicyStatusHistory table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Appendix B Policy hub data reference 116 116 117 117 119 119 120 121 121 122 122 123 124 124 126 127 128 128 129 129 133 133 134 134 135 135 136 137 139 139 140 140 142 143 115 Overview RecoveryPolicyDetail table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 UserInfo table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Overview The BMC Recovery Manager policy hub stores all information gathered from the data sources that you manage by using the Enterprise Policy Monitor. The policy hub stores the following types of information: ■ ■ ■ configuration data metric data policy data Configuration data includes details about each data source such as the host name, BMC SQL-BackTrack version, and operating system version. Metric data includes status and performance information about managed data sources, such as the number of blocks processed during a backup, the date of the last successful backup, and the date of the last successful recovery. Policy data includes details about user-defined policy definitions, and policy status generated from policy evaluation such as minimum backup generations to keep, status, and the date applied. Understanding the data model BMC Recovery Manager stores the data that it collects from data sources for all registered database server hosts in the policy hub, which uses a relational database management system (RDBMS). The configuration, metric, and policy data are stored in various tables in one database. The following data model figures (Figure 9 on page 118, Figure 10 on page 125, and Figure 11 on page 138) show each table and the relationships among the data within those tables. The logical models for each type of data (configuration, metric, and policy) are shown. Following the data model figures for each type of data are details about the tables that make up the data models, such as the type of data in each column and the source for that data. Understanding the data models can help you access the information stored within them for reports that you might want to generate using third-party drivers. 116 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Querying the policy hub Querying the policy hub You can query the policy hub to generate reports and otherwise use the information about your data sources that BMC Recovery Manager collects and stores. The following example is a query that returns detailed information for a particular data source. You can use this example to build your own query. SELECT A.Data_Source_Detail_ID, DBMS, DBMS_Version, Host_Name, Time_Zone_ID, OS, OS_Version, Policy_Name, Data_Source_Name, Instance_Name, Server_Name, Partition_Name, Database_Name, Data_Source_Host FROM ebr.DataSourceDetail A, ebr.Host B, ebr.DataSource C, ebr.Policy D WHERE A.Fully_Qualified_Name = ‘sanfran.ZIM920lq’ and A.Host_ID = B.Host_ID and A.Data_Source_Detail_ID = C.Data_Source_Detail_ID and C.Policy_ID = D.Policy_ID and Is_Primary_Level = ‘1’ Configuration data The configuration data stored in the policy hub includes details about each registered data source such as the host name, BMC SQL-BackTrack version, and operating system version. Figure 9 on page 118 illustrates the logical data model for the configuration data. Appendix B Policy hub data reference 117 Configuration data Figure 9 118 Configuration data model BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Configuration data Attribute table The Attribute table stores all attributes from the EPM. The stored information includes user-defined and predefined attributes. Table 24 Attribute table Column name Description Source of data Date type Sample data Attribute ID Primary key Auto-generated integer 1 Attribute Name The name of the attribute EPM (alternate key) varchar(30) location Attribute Type Data type of the attribute EPM varchar(10) string Last Modified Timestamp Last modified time for this row System timestamp 2004-07-08 01:20:45.0000 BackTrackInstall table The BackTrackInstall table stores information specific to the BMC SQL-BackTrack utility that is installed on the database server host. The EPM acquires much of this information through the discovery process it performs when you register database server hosts. Table 25 BackTrackInstall table (Part 1 of 2) Column name Description Source of data Date type Sample data BackTrack ID Primary key Auto-generated integer 1 Host ID Part of combination key of the alternate key (also foreign key from Host table) Host table look up integer 1 BackTrack Version Discovery services BMC SQL-BackTrack version number (also part of combination key of the alternate key) varchar(15) 5.4.00 BackTrack Install ID Install ID created by BMC Discovery services SQL-BackTrack (also part of combination key of the alternate key) varchar(50) BKO-2004-12-17-0 9:38:51 BackTrack Edition BMC SQL-BackTrack edition Discovery services varchar(5) ESS BackTrack Installed Location Where on the host BMC SQL-BackTrack resides Discovery services varchar(256) /bmc/backtrack/ obacktrack-5.0.00 OS Word Size Supported OS word size (32 or 64-bit) Discovery services char(2) 32 Appendix B Policy hub data reference 119 Configuration data Table 25 BackTrackInstall table (Part 2 of 2) Column name Description Source of data Date type Sample data BackTrack Name Full name of the BMC SQL-BackTrack utility Discovery services varchar(50) BMC SQL-BackTrack for Oracle Metric API Version Current version of Discovery services internal API that accesses this data varchar(15) 1.00.00 License Type ID Type of license Lookup from License Type table integer 1 License Size Data size of the license Internal API long 1234 Last Modified Timestamp Last modified time for this row System timestamp 2004-07-08 01:20:45.0000 DB Version Supported List of supported database versions Internal API varchar(4000) 9.2.0.1, 8.1.7 BackTrackInstall_DataSourceDetail table The BackTrackInstall_DataSourceDetail table is the resolved table that stores the relationships between the BackTrackInstall and DataSourceDetail tables. Table 26 BackTrackInstall_DataSourceDetail table Column name Description Source of data Date type Sample data Data Source Detail ID Part of the combination key of the primary key (also a foreign key from the DataSourceDetail table) DataSourceDetail table integer 1 BackTrack ID Part of the combination key of the primary key (also a foreign key from the BackTrackInstall table) BackTrackInstall table integer 1 Last Modified Timestamp Last modified time for this row System timestamp 2004-07-08 01:20:45.0000 120 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Configuration data DataModel table The DataModel table stores the version of the data model currently in use. The components of BMC Recovery Manager require this information in case the data model is expanded in a future release. Table 27 DataModel table Column name Description Source of data Data type Sample data Data Model Version Primary key Installation varchar(11) 1.00.00.00 Last Modified Timestamp Last modified time for this row System timestamp 2004-07-08 01:20:45.0000 DataSource table The DataSource table stores information about the registered data source. The policy hub receives much of this information from the metrics collector service, which is one of the BMC Recovery Manager services on the database server host. Table 28 DataSource table Column name Description Source of data Date type Sample data Data Source ID Primary key Auto-generated integer 1 Data Source Detail ID Part of combination key of the alternate key (also foreign key from DataSourceDetail table) DataSourceDetail table integer 1 Data Source Level The level of this data source (part of combination key of the alternate key) Metrics collector integer 1 Data Source Name Name of this data source (part of combination key of the alternate key) Metrics collector varchar(30) sav720la Is Primary Level Indicates whether this data source is at the primary level Metrics collector boolean 0; 1 Last Modified Timestamp Last modified time for this row System timestamp 2004-07-08 01:20:45.0000 Policy ID The policy this data source uses Policy table integer 1 Appendix B Policy hub data reference 121 Configuration data DataSourceAttribute table The DataSourceAttribute table stores all attributes related to a specific data source. Table 29 DataSourceAttribute table Column name Description Source of data Date type Sample data Attribute ID Part of the combination key of the primary key (also a foreign key from the Attribute table) Attribute table integer 1 Attribute Value The value of the attribute EPM varchar(50) Austin Data Source Detail ID Part of the combination key of the primary key (also a foreign key from the DataSourceDetail table) DataSourceDetail table integer 1 Last Modified Timestamp System 2004-07-08 01:20:45.0000 Last modified time for this row timestamp DataSourceDetail table The DataSourceDetail table stores metadata about the registered data source. The policy hub receives much of this information from the metrics collector service, which is one of the BMC Recovery Manager services on the database server host. Table 30 DataSourceDetail table (Part 1 of 2) Column name Source of data Date type Sample data Data Source Detail ID Primary key Auto-generated integer 1 Fully Qualified Name Uniquely identifies the data source (alternate key) Metrics collector varchar(50) Savage...sav720la Host ID Host where the data source is installed Host table look up integer 1 DBMS The type of database management system Metrics collector varchar(30) Oracle DBMS Version Version of the database management system Metrics collector varchar(10) 9.2.0.1 DB Configuration Configuration of the database management system server Metrics collector varchar(18) EEE; OPS Discovered Timestamp The time this data source was discovered Metrics collector timestamp 2004-07-08 01:20:45.0000 122 Description BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Configuration data Table 30 DataSourceDetail table (Part 2 of 2) Column name Description Source of data Date type Sample data Primary Data Source Name The name of the primary entity of the data source Metrics collector varchar(30) SAV817la DB Word Size Supported word size (32- Metrics collector or 64-bit) of the data source char(2) 32 Data Source Host Name of the host where the data source is installed (also part of the fully qualified name) Metrics collector varchar(64) savage Instance Name Instance name of this data Metrics collector source (also part of the fully qualified name) varchar(32) sav720la Partition Name Partition name of this data source Metrics collector varchar(32) sav720la Database Name Database name of this data source Metrics collector varchar(32) sav720la Server Name Database server name for Metrics collector this data source varchar(32) sav720la Last Modified Timestamp Last modified time for this row timestamp 2004-07-08 01:20:45.0000 System Host table The Host table stores information about the database server host where the BMC SQL-BackTrack utility is installed. The EPM acquires much of this information through the discovery process that it performs when you register database server hosts. Table 31 Host table (Part 1 of 2) Column name Description Source of data Date type Sample data Host ID Primary key Auto-generated integer 1 Host Name Name of the host (alternate key) Discovery services varchar(50) savage.utc.com OS Operating system type Discovery services varchar(15) Solaris OS Version Operating system version Discovery services varchar(15) 8.0.00 IP Address IP address of the host Discovery services varchar(15) 173.17.63.78 OS Word Size 32- or 64-bit Discovery services char(2) 32 Last Message Timestamp Last message timestamp received by this host Discovery services timestamp 2004-07-08 01:20:45.0000 Last Modified Timestamp Last modified time for this row System timestamp 2004-07-08 01:20:45.0000 Appendix B Policy hub data reference 123 Metric data Table 31 Host table (Part 2 of 2) Column name Description Source of data Date type Sample data Registration Error Code Null when host is successfully registered; otherwise error code Discovery services varchar(15) BMCEBR000001E Time Zone ID Identifies the time zone for this host Discovery services varchar(50) America/Chicago Host URL Combination of host name (or IP address) and port number Discovery services varchar(270) 172.18.67.59:1099 LicenseType table The LicenseType table stores information about the type of BMC SQL-BackTrack license currently running on the database server host. For example, BMC SQL-BackTrack can be installed on a trial basis. Table 32 LicenseType table Column name Description Source of data Date type Sample data License Type ID Primary key Auto-generated integer 1 Last Modified Timestamp Last modified time for this row System timestamp 2004-07-08 01:20:45.0000 License Type Installation Type of BMC SQL-BackTrack license: Trial, Enterprise, or Single Host varchar(30) Single Host Metric data The metric data stored in the policy hub includes status and performance information about managed data sources, such as the number of blocks processed during a backup, the date of the last successful backup, and the date of the last successful recovery. Figure 10 on page 125 illustrates the logical data model for the metric data. NOTE Most of the tables documented in this section have a corresponding history table. For example, the DataSourceTaskSummary table has a corresponding DataSourceTaskSummaryHistory table. The history tables archive old data. 124 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Metric data Figure 10 Metric data model Appendix B Policy hub data reference 125 Metric data BackTrackConfig table The BackTrackConfig table stores job-related information for each database in a job. A job is any backup- or recovery-related activity initiated using a BMC SQL-BackTrack utility. One job can span several databases. One database can span several tasks, the details of which are stored in separate task details tables. Table 33 BackTrackConfig table Column name Description Job ID Date type Sample data Member of the composite Job table primary key (also a foreign key from the Job table) bigint 54135 Primary Data Source ID Member of the composite DataSource table primary key (also a foreign key from the DataSource table) integer 1 Max Backup Generations to Keep Number of backup generations to retain Managed data source integer 5 Job Type Indicates whether this job Managed data source is a backup or recovery operation integer 1 Estimated Recovery Time in Sec Estimate is calculated based on previous performance Managed data source integer 18000 Data Source Size in MB The size of the data source in megabytes Managed data source bigint 234567 Total Tasks Total number of tasks for the database Managed data source integer 100 Completed Tasks Number of completed tasks for the database Managed data source integer 100 Failed Tasks Number of failed tasks for Managed data source the database integer 0 Host ID Foreign key from the Host table integer 4 Expiry Time in Sec Number of days a backup Managed data source should be retained integer 3 License Aggregate Size in MB Measured aggregate size of the license bigint 568953 Is Primary Entity Level Indicates whether this job Managed data source is a database-level job boolean true Last Modified Timestamp Last modified timestamp for this job timestamp 2004-07-08 01:20:45.0000 126 Source of data Host table Managed data source Managed data source BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Metric data DataSourceTaskPhase table The DataSourceTaskPhase table stores information regarding the time spent by a task in its different phases. One row from one of the task summary tables will have zero, one, or more rows in this table. Table 34 DataSourceTaskPhase table Column name Description Phase Name Source of data Date type Sample data Member of the composite Managed data source alternate key to identify the phase for which data is being collected varchar(40) dump Phase Time The amount of time (in Managed data source seconds) the task spent in this phase integer 456 Job ID Managed data source Foreign key from one of the task detail tables (also a member of the composite alternate key) that identifies the job for which data is being stored bigint 123456 Task ID Managed data source Foreign key from one of the task detail tables (also a member of the composite alternate key) that identifies the task for which data is being stored integer 4 Primary Data Source ID Managed data source Foreign key from one of the task detail tables (also a member of the composite alternate key) that identifies the task for which data is being stored integer 67 Phase Percent The percentage of the phase that has been completed Managed data source integer 45 Phase Order The order in which the phases are sent in the message to other components Managed data source integer 2 Last Modified The time this record was last modified Managed data source timestamp 2004-07-08 01:20:45.0000 Appendix B Policy hub data reference 127 Metric data DataSourceTaskProperty table The DataSourceTaskProperty table stores the properties associated with a task. A task can have zero, one, or more properties associated with it. Table 35 DataSourceTaskProperty table Column name Description Property Source of data Date type Sample data Enumeration from a set of Managed data source known task properties, including data transfer, query, catalog sync, update history, same host, same instance, alternate host, alternate instance integer 3 Task ID Member of the composite Managed data source alternate key to identify the task to which this property belongs integer 4 Primary Data Source ID Member of the composite Managed data source alternate key to identify the task to which this property belongs integer 5 Job ID Member of the composite Managed data source alternate key to identify the task to which this property belongs bigint 5674 Last Modified Timestamp The time this record was last modified timestamp 2004-07-08 01:20:45.0000 Managed data source Job table The Job table stores job-related information. A job is any backup- or recovery-related activity initiated using a BMC SQL-BackTrack utility. One job can span several databases. Table 36 Job table (Part 1 of 2) Column name Description Source of data Date type Sample data Job ID Primary key Auto-generated bigint 1 BackTrack Job ID Alternate key Managed data source varchar(50) Universally unique identifier Job Start Timestamp The time the job started System timestamp 2004-07-08 01:20:45.0000 128 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Metric data Table 36 Job table (Part 2 of 2) Column name Description Source of data Date type Sample data Job End Timestamp The time the job ended System timestamp 2004-07-08 01:20:45.0000 BackTrack Job Tag Configuration Managed data source information about the job to enable it to run again varchar(64) character data Last Modified Timestamp The time this record was last modified timestamp 2004-07-08 01:20:45.0000 System JobType table The JobType table stores information about the job. The Job Type ID from this table is stored in other tables in the policy hub that require a value from an enumeration. Table 37 JobType table Column name Description Job Type ID Source of data Date type Sample data Primary key (corresponds Auto-generated to the enumeration of the Job Type value) integer 5 Job Type The string that is to be enumerated Managed data source varchar(128) backup Last Modified Timestamp Indicates when this record was inserted System generated timestamp 2004-07-08 01:20:45.0000 Task data tables The metric data stored in the policy hub includes five tables with almost identical columns for storing different categories of task data. A task is a portion of a job. A hierarchy of tasks make up a given job. The task data tables include Table 38 Task data tables (Part 1 of 2) Table Description DataSourceTaskDetail Stores details of tasks that belong to a database-level job. DataSourceTaskSummary Stores the summary information generated at the end of a database-level job. RunTimeTaskDetail Stores details of the tasks for the data model currently in memory. The policy hub can use this table for temporary data storage. Appendix B Policy hub data reference 129 Metric data Table 38 Task data tables (Part 2 of 2) Table Description SubDataSourceTaskDetail Stores details of tasks that belong to a job that is below the database level. For example, a job that operates on selected rows. SubDataSourceTaskSummary Stores the summary information of tasks that belong to a job that is below the database level. For example, a job that operates on selected rows. All task data tables are similar in design with the following exceptions: Table 39 ■ The RunTimeTaskDetail table does not include the Final Input Size, Final Output Size, and Final Compressed Size columns. ■ The SubDataSourceTaskDetail and SubDataSourceTaskSummary tables do not include the IsCompleted column. Task data table exceptions (Part 1 of 3) Column name Description Job ID Date type Sample data Member of the composite Job table primary key (also a foreign key from the Job table) bigint 1234 Primary Data Source ID Member of the composite DataSource table primary key (also a foreign key from the DataSource table) integer 1 Task ID Member of the composite Managed data source primary key; unique within a job integer 5 BackTrack ID Managed data source Identifies the BMC SQL-BackTrack installation associated with the task. The value is a foreign key reference to the BackTrack table. integer 23 Task Level Level of the task which is used to track the hierarchy of tasks and group similar tasks Managed data source integer 2 Elapsed Time in Sec Elapsed time since the task started Managed data source integer 7397298 Last Modified Timestamp The time this record was last modified Managed data source timestamp 2004-07-08 01:20:45.0000 130 Source of data BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Metric data Table 39 Task data table exceptions (Part 2 of 3) Column name Description Task Method Source of data Date type Sample data Managed data source Enumeration that indicates the task method; see the TaskMethod table to find the method that corresponds to this enumeration integer 2 Is Completed Whether the task is complete or incomplete Managed data source boolean true Task Status Enumeration that indicates successful completion, completion with warnings, completion with errors, and so on Managed data source integer 2 Task Alert Indicates whether an alert Managed data source condition (warning, error, and so on) is associated with this task. Defaults to ok. Foreign key to TaskAlert table. integer 3 Task Type Indicates whether this task is a backup or recovery task. Managed data source integer 1 Is Dry Run Whether the task is a dry run Managed data source boolean true Is Compressed Whether the task involves Managed data source compressed data boolean true boolean true Note: For recovery jobs, the top-level task does not track whether compression was enabled for any of the subtasks. Only the subtasks using compressed data indicate that the task involves compressed data. Is Encrypted Whether the task involves Managed data source encrypted data Note: For recovery jobs, the top-level task does not track whether encryption was enabled for any of the subtasks. Only the subtasks using encrypted data indicate that the task involves encrypted data. Appendix B Policy hub data reference 131 Metric data Table 39 Task data table exceptions (Part 3 of 3) Column name Description Source of data Date type Sample data Estimated Input Size in KB Estimated size of task input Managed data source bigint 4500 Bytes Processed Number of bytes currently processed Managed data source bigint 12345 Throughput Rate in Kbytes per Second Throughput of this task in Managed data source kilobytes per second integer 10254 Parent Task ID ID of the parent task Managed data source integer 4 Task Scope Enumeration that indicates database, all partitions, single partition, partition list, tablespace, all data files, single data file, or file group Managed data source integer 2 Task Mode Enumeration that indicates offline, online, cold, or hot Managed data source integer 2 Final Input Size in KB Final size of the task input Managed data source bigint 8209 Final Output Size in KB Final size of the task output Managed data source bigint 8209 Final Compressed Size in KB Final size of the compressed data Managed data source bigint 76543 Total Objects Total number of objects in Managed data source the task integer 99 Objects Processed Number of objects processed by this task integer 99 Host ID Foreign key from the Host Host table table integer 345 Managed data source Task Start Timestamp Time at which the task started Managed data source timestamp 2004-07-08 01:20:45.0000 Task End Timestamp Time at which the task ended Managed data source timestamp 2004-07-08 03:15:35.0000 Compression Ratio Managed data source float 40 132 Measure of the compression achieved by the backup with the compression feature turned on. BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Metric data TaskAlert table The TaskAlert table contains information about the possible alert conditions for a backup or recovery task. The Task Alert ID from this table is stored in other tables in the policy hub that require a value from an enumeration. Table 40 TaskAlert table Column name Description Task Alert ID Source of data Date type Sample data Primary key (corresponds Auto-generated to the enumeration of the Task Alert value) integer 3 Task Alert The string that is to be enumerated Managed data source varchar(128) failure Last Modified Timestamp Indicates when this record was inserted System generated timestamp 2004-07-08 01:20:45.0000 TaskMethod table The TaskMethod table contains information about a task. The Task Method ID from this table is stored in other tables in the policy hub that require a value from an enumeration. Table 41 TaskMethod table Column name Description Task Method ID Source of data Date type Sample data Primary key (corresponds Auto-generated to the enumeration of the Task Method value) integer 5 Task Method The string that is to be enumerated Managed data source varchar(128) incremental Last Modified Timestamp Indicates when this record was inserted System generated timestamp 2004-07-08 01:20:45.0000 Appendix B Policy hub data reference 133 Metric data TaskMode table The TaskMode table contains information about a task. The Task Mode ID from this table is stored in other tables in the policy hub that require a value from an enumeration. Table 42 TaskMode table Column name Description Task Mode ID Source of data Date type Sample data Primary key (corresponds Auto-generated to the enumeration of the Task Mode value) integer 5 Task Mode The string that is to be enumerated Managed data source varchar(128) offline Last Modified Timestamp Indicates when this record was inserted System generated timestamp 2004-07-08 01:20:45.0000 TaskProperty table The TaskProperty table contains information about a task. The Task Property ID from this table is stored in other tables in the policy hub that require a value from an enumeration. Table 43 TaskProperty table Column name Description Task Property ID Date type Sample data Primary key (corresponds Auto-generated to the enumeration of the Task Property value) integer 5 Task Property The string that is to be enumerated Managed data source varchar(128) data transfer Last Modified Timestamp Indicates when this record was inserted System generated timestamp 2004-07-08 01:20:45.0000 134 Source of data BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Metric data TaskScope table The TaskScope table contains information about a task. The Task Scope ID from this table is stored in other tables in the policy hub that require a value from an enumeration. Table 44 TaskScope table Column name Description Task Scope ID Source of data Date type Sample data Primary key (corresponds Auto-generated to the enumeration of the Task Scope value) integer 5 Task Scope The string that is to be enumerated Managed data source varchar(128) database Last Modified Timestamp Indicates when this record was inserted System generated timestamp 2004-07-08 01:20:45.0000 TaskStatus table The TaskStatus table contains information about a task. The Task Status ID from this table is stored in other tables in the policy hub that require a value from an enumeration. Table 45 TaskStatus table Column name Description Task Status ID Source of data Date type Sample data Primary key (corresponds Auto-generated to the enumeration of the Task Status value) integer 5 Task Status The string that is to be enumerated Managed data source varchar(128) completed successfully Last Modified Timestamp Indicates when this record was inserted System generated timestamp 2004-07-08 01:20:45.0000 Appendix B Policy hub data reference 135 Metric data TaskDataSource table The TaskDataSource table stores the Data Source ID corresponding to the name of the data file or logical entity (such as a table) associated with a task. One row from one of the task details tables will have one or more rows in this table. In cases where more than one logical entity is associated with a task, multiple rows are included in this table. Table 46 TaskDataSource table Column name Description Data Source ID Date type Sample data Managed data source ID corresponding to the name of the data file or logical entity with which the task is associated; a member of the composite alternate key and an alternate key from the DataSource table varchar(30) /oracle/System01. dbf Task ID Managed data source Foreign key from one of the task detail tables (also a member of the composite alternate key) that identifies the task for which the data source name is being stored integer 4 Job ID Managed data source Foreign key from one of the task detail tables (also a member of the composite alternate key) that identifies the task for which the data source name is being stored bigint 12345 Primary Data Source ID Managed data source Foreign key from one of the task detail tables (also a member of the composite alternate key) that identifies the task for which the data source name is being stored integer 86 Last Modified The time this record was last modified timestamp 2004-07-08 01:20:45.0000 136 Source of data Managed data source BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Policy data Policy data Policy data includes details about user-defined policy definitions, and policy status generated from policy evaluation such as minimum backup generations to keep, status, and the date applied. Figure 11 on page 138 illustrates the logical data model for the policy data. Appendix B Policy hub data reference 137 Policy data Figure 11 138 Policy data model BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Policy data BackupPolicyDetail table The BackupPolicyDetail table stores backup policy information. You use the EPM to establish backup policies for your data sources. Table 47 BackupPolicyDetail table Column name Description Source of data Date type Sample data Backup Policy Detail ID The primary key of the table. Auto-generated integer 1 Policy ID Foreign key from the PolicyDetail table. PolicyDetail table integer 1 Policy Version Foreign key from the PolicyDetail table. PolicyDetail table integer 1 Backup Type The type of backup this policy calls for. EPM varchar(30) cold backup Min Backup Frequency in Sec The minimum backup EPM frequency that this policy establishes (in seconds) integer 23456 Max Backup Time Allowed in Sec The maximum time allowed for a backup according to this policy (in seconds) EPM long 28800 Last Modified Timestamp Last modified time for this row System timestamp 2004-07-08 01:20:45.0000 DataSourcePolicyHistory table The DataSourcePolicyHistory table is used to track the policy assignments for data sources. The primary key is the combination of Data Source ID, Policy ID, and Policy. Table 48 DataSourcePolicyHistory table (Part 1 of 2) Column name Description Source of data Data type Sample data Data Source ID Foreign key from DataSource table Foreign key from DataSource table Integer 1 Policy ID Policy ID of the Foreign key from assigned policy for this PolicyDetail table data source Integer 1 Policy Version Policy version of the Foreign key from assigned policy for this PolicyDetail table data source Integer 1 Appendix B Policy hub data reference 139 Policy data Table 48 DataSourcePolicyHistory table (Part 2 of 2) Column name Description Source of data Data type Sample data UTC Timestamp Policy-assigned timestamp using UTC format System Timestamp 2003-07-08 01:20:45.0000 Last Modified Timestamp Last modified time for System this row Timestamp 2003-07-08 01:20:45.0000 Policy table The Policy table stores basic policy information. Table 49 Policy table Column name Description Source of data Date type Sample data Policy ID Primary key Auto-generated integer 1 Policy Name Name of the policy (alternate key) EPM varchar(100) Tier17x24x52 Latest Version The latest version of this policy Derived from policy services integer 1 UserInfo ID The user that created this Lookup from UserInfo integer policy table 1 Last Modified Timestamp Last modified time for this row System timestamp 2004-07-08 01:20:45.0000 Policy Creation Timestamp The time at which the policy was created EPM timestamp 2004-07-08 01:20:45.0000 Is Marked to Delete Indicates whether the GUI default value: false policy is marked for deletion from the console Boolean 1 PolicyDetail table The PolicyDetail table stores policy-related information. You use the EPM to establish policies for your data sources. Much of the information in this table is derived either from the EPM or the policy services component of BMC Recovery Manager. (Policy services reside on the same host as the policy hub.) 140 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Policy data Table 50 PolicyDetail table Column name Description Source of data Date type Sample data Policy ID Part of the combination key of the primary key (also a foreign key from the Policy table) Policy table integer 1 Policy Version The version of this policy Policy services (part of the combination key of the primary key) integer 1 Minimum Backup Generation to Keep Number of backup generations this policy requires for retention EPM integer 3 Policy Creation Timestamp The time this policy was created Policy services timestamp 2004-07-08 01:20:45.0000 Last Modified Timestamp The time this policy was most recently modified Policy services timestamp 2004-07-08 02:30:35.0000 Expiry Time in Seconds Minimum time in which a EPM recovery must complete for this policy integer 300 User Info ID The ID of the user who most recently modified the policy integer 1 A percentage to add on to EPM ETTR Dry Run the estimated time Recovery Compensation Factor required to perform a dry run recovery based on the performance of the most recent dry run float 10 ETTR Real Recovery A percentage to add on to EPM Compensation Factor the estimated time required to perform a recovery based on the performance of the most recent recovery float 10 Max Estimated Time to Recovery in Seconds The maximum time to allow for a recovery according to this policy EPM integer 28800 Backup Encryption Backup encryption is required. EPM integer 0 for false, 1 for true. Backup Encryption Check Backup encryption feature is enabled. EPM integer 0 for false, 1 for true. Backup Compression Backup compression is required. EPM integer 0 for false, 1 for true. Enable Compression Check EPM integer 0 for false, 1 for true. Backup compression feature is enabled. UserInfo table lookup Appendix B Policy hub data reference 141 Policy data PolicyStatus table The PolicyStatus table stores information about policies, such as identifying the task to which the policy was applied and the time at which the policy was applied. A policy is a set of rules that you define through the EPM that describe requirements for backup or recovery processing. Table 51 PolicyStatus table Column name Description Job ID Date type Sample data Member of the composite Managed data source alternate key to identify the job for which the policy was applied bigint 54321 Task ID Member of the composite Managed data source alternate key to identify the task for which the policy was applied integer 4 Primary Data Source ID Member of the composite Managed data source alternate key to identify the task for which the policy was applied integer 5 Policy ID Foreign key from the PolicyDetail table to identify the policy that was applied Managed data source integer 4 Policy Version Foreign key from the PolicyDetail table to identify the policy that was applied Managed data source integer 5 Status Indicates either success or Managed data source failure varchar(10) success Date Applied Date when the policy was Managed data source applied timestamp 2004-07-08 01:20:45.0000 Attribute Name String that contains the policy key value Managed data source varchar(50) Backup.full. Hot.Frequency Last Modified Timestamp The time this record was last modified Managed data source timestamp 2004-07-08 01:20:45.0000 Policy Value String that contains the value the user set for this policy as part of the policy definition Managed data source varchar(30) 7 days Metric Value Indicates the metric value Managed data source for this policy, which is the measured value gathered to compare to the policy value varchar(50) 5 days 142 Source of data BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Policy data PolicyStatusHistory table The PolicyStatusHistory table is used to store policy status history information so that we could provide policy compliance history information for report or user purpose. The primary key of PolicyStatusHistory table is the combination of Primary_Data_source_ID, Attribute_Name, and Policy_Status_Version. Because the history of policy status is required, a policy_status_version column had been added for this table instead providing a mirror definition on PolicyStatus table. Table 52 PolicyStatusHistory table Column name Description Primary Data Source ID Source of data Data type Sample data Part of the primary key Metric Integer 1 Attribute Name Part of the primary key Metric varchar(50) Backup.full.hot.frequ ency Date Applied Part of the primary key; date when the policy was applied Metric Timestamp 2003-07-08 01:20:45.0000 Job ID Job ID related to this primary data source Metric Integer 54321 Task ID Task ID related to this primary data source Metric Integer 4 Policy ID Policy ID to which this Metric primary data source been applied Integer 1 Policy Version Policy version for the policy applied to this data source Integer 1 Status Status of this policy on Metric the particular data source varchar(10) Success Policy Value String that contains the Metric value the user set for this policy as part of the policy definition varchar(30) 7 days Metric Value Metric Metric value for this policy, which is the measured value gathered to compare to the policy value varchar(50) 5 days Last Modified Timestamp Last modified time for System this row timestamp 2003-07-08 01:20:45.0000 Metric Appendix B Policy hub data reference 143 Policy data RecoveryPolicyDetail table The RecoveryPolicyDetail table stores recovery policy information. You use the EPM to establish recovery policies for your data sources. Table 53 RecoveryPolicyDetail table Column name Description Source of data Date type Sample data Recovery Policy Detail ID The primary key of the table. Auto-generated integer 1 Policy ID Foreign key from the PolicyDetail table. PolicyDetail table integer 1 Policy Version Foreign key from the PolicyDetail table. PolicyDetail table integer 1 Recovery Type The type of recovery this policy calls for. EPM varchar(30) Same host recovery Min Recovery Frequency in Sec The minimum recovery EPM frequency that this policy establishes (in seconds) integer 23456 Max Recovery Time Allowed in Sec The maximum time allowed for a recovery according to this policy (in seconds) EPM long 28800 Last Modified Timestamp Last modified time for this row System timestamp 2004-07-08 01:20:45.0000 UserInfo table The UserInfo table stores a user ID for each user of the EPM. Table 54 UserInfo table Column name Description Source of data Date type Sample data User Info ID Primary key Auto-generated integer 1 Login Name ID used to access the EPM EPM (alternate key) varchar(256) jsmith Last Modified Timestamp Last modified time for this row timestamp 2004-07-08 01:20:45.0000 Is Group The Login Name in this EPM row is a group name instead of user login name char(1) '0' 144 System BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Policy data BackupExclusionParameter table The BackupExclusionParameter table stores information about the period when backups are not to be made. Table 55 BackupExclusionParameter table Column Name Description Source of Data Data Type Sample data Exclusion Criteria ID The primary key of the table Auto-generated integer 1 Bckup Policy Detail ID Foreign key from BackupPolicyDetail table BackupPolicyDetail integer 1 Recursion Pattern The recursion pattern of the exclusion. EPM varchar(30) Monthly (Daybased) Start Date Start date of the backup exclusion. EPM timestamp 2007-02-28 00:00:00:0000 End Date End date of the backup exclusion. EPM timestamp 2007-02-28 00:00:00:0000 Start Time Start time of the backup exclusion. EPM varchar(5) 00:00 End Time End time of the backup exclusion. EPM varchar(5) 00:00 Months of Year Months of the year when exclusion occurs. EPM varchar(100) Jan Days of Month Days of month when exclusion occurs. EPM varchar(100) 9, 18 Days of Week Days of week when exclusion occurs. EPM varchar(100) Mon Exclusion Type Type of exclusion. EPM varchar(10) Standard Is Enabled Is backup exclusion enabled. EPM char(1) '0' for no, '1' for yes. Last Modified Timestamp Last modified time for this row. System timestamp 2007-02- Appendix B Policy hub data reference 145 Policy data 146 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Appendix C C BMC Recovery Manager reports This appendix presents the following topics: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Generating BMC Recovery Manager reports from the console . . . . . . . . . . . . . . . . . Generating BMC Recovery Manager reports from the command line . . . . . . . . . . . Report categories and types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Policy reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Compliance reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backup reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recovery reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Miscellaneous reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 148 150 156 158 162 163 165 172 Overview A variety of BMC Recovery Manager reports are available to help you audit backup and recovery activities and monitor trends in your data sources. These reports provide summary information or more detailed information depending on the report type that you choose. You can run reports by using one of the following methods: Method Reference Use the Reports menu option from the BMC Recovery Manager console. “Generating BMC Recovery Manager reports from the console” on page 148 Use the EPM Report command-line utility from the command line. “Generating BMC Recovery Manager reports from the command line” on page 150 Appendix C BMC Recovery Manager reports 147 Generating BMC Recovery Manager reports from the console Generating BMC Recovery Manager reports from the console 1 In the BMC Recovery Manager console, open the Reports menu and choose a report category. For a list of report categories, see Table 60 on page 157. 2 From the submenu, choose a report to view. 3 If applicable, select the type of report to view from the submenu. For a list of the report types, see Table 61 on page 157. 4 In the EPM Report Configuration dialog box, review the information on each of the tabs and specify any information required for the report, if applicable. The tabs in the dialog box vary depending on the report requested; one or more of the following tabs appear in this dialog box. For more information about any of the tabs, click the Help button. 148 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Generating BMC Recovery Manager reports from the console Tab Description File Info tab Review the default information that will be used to generate the report, or specify the output file name and location for the report. By default, the report file is stored in the _ebrtemp directory in the system temp directory and the file name is created by appending the report type to the report name. The following example shows this naming convention: PolicyComplianceSummary.pdf This file is overwritten each time you generate this type of report unless you change the location or file name. Click Browse to change the location or file name for the report. For backup and recovery graphical reports, specify your selection for the following options: Columns tab ■ Backup type: See “BackupType” on page 168. ■ Recovery type: See “RecoveryType” on page 170. ■ Include Dry Run: This option enables you to include the dry-run (test) backup or recovery in the graph. Select one or more columns to include in the Status Performance Summary report. Click Clear All to clear all selections. Click Select All to select all columns. Select a column and click Up or Down to move your selection to the previous or next item in the list. For a description of each column, see “Backup and Recovery Status Performance Summary Report options” on page 167. Data Sources tab Select the data sources to include in the report. In the Include column, select a checkbox to select a data source, or click Select All to select all items in the Data Sources list. Click Clear All to clear all selections. Click Up or Down to move your selection to the previous or next item in the list. Note: Use the filter criteria window to limit the number of data sources displayed in this view. Appendix C BMC Recovery Manager reports 149 Generating BMC Recovery Manager reports from the command line Tab Description Time Ranges tab Specify the period of time to include for the report. You can select a predefined time range, with intervals ranging from one day up to one year, or specify a Start time and End time by using the drop-down calendar and time selector options. You can select the rate of change unit, which is daily, weekly, or monthly. Custom Attributes tab (Optional) Select one or more custom attributes to include in the report. Click Clear All to clear all selections. Click Select All to select all columns. Select an attribute and click Up or Down to move your selection to the previous or next item in the list. Custom Attributes are available only for Summary reports. For a description of each custom attribute, see “Using custom attributes in reports” on page 174. 5 Click OK to generate the report. EPM creates the report in a PDF file and displays the report in the Adobe Reader window. 6 (Optional) To print the report, choose File => Print in the Adobe Reader window. NOTE You can download Adobe reader from the Adobe website at http://www.adobe.com. Generating BMC Recovery Manager reports from the command line You can run BMC Recovery Manager reports from the command line by using the EPM Report command-line utility. The epmReport.bat and epmReport.sh files are automatically installed when you install Enterprise Policy Monitor. The scripts are located in the /dataRepository/bin directoriy. 150 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Generating BMC Recovery Manager reports from the command line epmreport Use the epmreport command to generate BMC Recovery Manager reports from the command line. Running reports from the command line is a two-stage process: 1. Use epmreport to create the identification file. 2. Run epmreport by specifying the identification file and other parameters. For examples of these commands, see Table 59 on page 156. Syntax The syntax for the epmreport command is as follows: epmreport.bat | epmreport.sh -i -n -o [-a] [-b ] [-c { | ALL}] [-ca { | ALL}] [-d { | ALL}] [-e ] [-f { | ALL}] [-g ] [-h] [-k ] [-l] [-t ] [-u ] [-v] [-w ] [-x] Option descriptions Table 56 lists the required option for the epmreport command for creating an identification file. Table 57 on page 152 lists the required option for the epmreport command for generating a report. Appendix C BMC Recovery Manager reports 151 Generating BMC Recovery Manager reports from the command line Table 56 Required option for the epmreport command to create an identification file Option Description -a Use this option to generate the identification file. This option enables you to store your policy hub authentication information in a file that you can use upon each subsequent invocation of epmreport. Table 58 on page 153 lists the required options for the epmreport command for generating a report. Table 57 Required options for the epmreport command Option Description -i Use this option to specify the file name in which you have stored authentication information for your policy hub connection. -n Use this option to specify the name of the report you want to generate. To view a complete list of all available report names, use the epmreport command with the -l option. -o Use this option to specify the name of the output file in which you wish to store the report information. Specify a file name, including the full path if other than the default current directory. Do not specify a file extension in the name. Note: If the file already exists, the epmreport command overwrites the existing file. Table 58 on page 153 lists the optional options for the epmreport command for generating a report. 152 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Generating BMC Recovery Manager reports from the command line Table 58 Optional options for the epmreport command (Part 1 of 3) Option Description -b Use this option to specify the starting date and time for the time range for which you want to view historical or rate-of-change information. This option is applicable to History and ROC reports only. Use the following convention when entering date and time information: YYYY-MM-DD [HH:MM:SS] (where YYYY=year, MM=month, DD=day, HH=hour, MM=minutes, SS=seconds) Use leading zeros when the value specified is less than 10. -c { | ALL} Use this option to specify column names that you want to include in the report. This option applies only to the StatusPerformanceReport. You can specify one or more column names. Separate multiple column names with a comma. Another valid value for this option is the default option ALL. For a list of column names, see Table 66 on page 167. Note: To specify a large number of column names, you can use the -f option to specify the name of a file that contains the column names. [-ca Use this option to specify column names for custom { | attributes that you want to include in the report. This option ALL}] applies only to Summary reports. You can specify one or more custom attributes. Separate multiple custom attribute names with a comma. Another valid value for this option is the default option ALL. For a list of custom attribute names, see Table 68 on page 175. -d { | ALL} Use this option to specify one or more data sources to be included in a Detail, History, or Graphical report. Separate multiple data source names with a comma. Another valid value for this option is the default option ALL. Note: To specify a large number of data source names, you can use the -g option to specify the name of a file that contains the data source names. Appendix C BMC Recovery Manager reports 153 Generating BMC Recovery Manager reports from the command line Table 58 Optional options for the epmreport command (Part 2 of 3) Option Description -e Use this option to specify the ending date and time for the time range for which you want to view historical or rate-of-change information. This option is applicable to History and ROC reports only. Use the following convention when entering date and time information: YYYY-MM-DD [HH:MM:SS] (where YYYY=year, MM=month, DD=day, HH=hour, MM=minutes, SS=seconds) Use leading zeros when the value specified is less than 10. -f { | ALL} Use this option instead of the -c option to list the column names in a file and reference the file name for the request. Separate the list of names in the file by a comma or a line break. Another valid value for this option is the default option ALL. -g Use this option instead of the -d option to specify the file name if you intend to use a file for the list of data sources to include in a Detail, History, or Graphical report. -h Use this option to display Help information for the command usage. -k Use this option to specify the backup or recovery types you want to include for the following reports: ■ ■ ■ ■ ■ ■ ■ BackupThroughputROCReport RecoveryThroughputROCReport BackupElapsedTimeROCReport RecoveryElapsedTimeROCReport BackupCompressionRatioROCReport BackupFinalCompressionSizeROCReport RawBackupSizeROCReport Valid values for Backup reports are ■ ■ ■ ■ ■ ■ ■ FULL.ONLINE FULL.OFFLINE INCREMENTAL.ONLINE INCREMENTAL.OFFLINE DELTA.ONLINE DELTA.OFFLINE LOGICAL Valid values for Recovery reports are ■ ■ 154 REMOTEHOST LOCALHOST BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Generating BMC Recovery Manager reports from the command line Table 58 Optional options for the epmreport command (Part 3 of 3) Option Description -l Use this option to list the names of all available reports. -t Use this option to specify a predefined time period. Use one of the following values for : ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ -u LastYear Last 6 Months Last 3 Months Last Quarter Last Month Last 2 Weeks Last Week Last Day Month to Date Quarter to Date Year to Date First Calendar Quarter Second Calendar Quarter Third Calendar Quarter Fourth Calendar Quarter Use this option to specify the unit in which you would like to display the rate-of-change information. This option is for ROC reports only. Valid values for are ■ ■ ■ Monthly (default value) Weekly Daily -v Use this option to display the version of the policy hub to which you are connected. -w Use this option to specify how much time is allowed to process the request. The default value for this option is 10 minutes. -x Use this option to exclude the dry run information from specific ROC reports. For a list of the applicable reports, see the -k option. Examples Table 59 on page 156 provides examples of the epmreport command. Appendix C BMC Recovery Manager reports 155 Report categories and types Table 59 Example epmreport commands Description Example Create the identification file epmreport.bat -a You are prompted for the following information: Enter Policy Hub Host and Port (localhost:12000): Enter Policy Hub Host User Id: Enter Policy Hub Host Password: After the policy hub is successfully validated, you are prompted for a file name to save the authentication information: Enter File Name to Store the Authentication: epmreport stores the following information in an encrypted format using the DNA encryption utilities: ■ ■ ■ ■ ■ ■ Run a report Local user name Local host name Local domain name, if applicable Policy hub user name Policy hub password Policy hub URL (name:portnumber) epmreport.bat -o BackupThroughputROCReport03 -n BackupThroughputROCReport -i uchakrab-Apr-19 -d bakuli.bmc.com::::BAK101EB -b 2005-04-10 -e 2005-04-24 -k FULL.OFFLINE -x This command generates a BackupThroughputROCReport report by using the following information: ■ ■ ■ ■ ■ ■ The policy hub and user name contained in the identification file uchakrab-Apr-19 The data source bakuli.bmc.com::::BAK101EB A start time of 2005-04-10 An end time of 2005-04-24 A backup type FULL.OFFLINE, excluding the dry-run The report name BackupThroughtputROCReport03.pdf Report categories and types Table 60 on page 157 lists the categories of reports that are available from the Reports menu. 156 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Report categories and types Table 60 Report categories Report category Description Reference Policy Provides information about the policies that are defined in the EPM and the policy assignments and statuses for data sources for all registered database server hosts. “Policy reports” on page 158 Compliance Provides information about license compliance and policy compliance for data sources for all registered database server hosts. “Compliance reports” on page 162 Backup Provides information about the status of backups that occurred for the data sources for all registered database server hosts. “Backup reports” on page 163 Recovery Provides recovery status information “Recovery reports” on page 165 for the data sources for all registered database server hosts. Miscellaneous Provides general information about the data sources for all registered database server hosts. “Miscellaneous reports” on page 172 Table 61 lists the report types that are available for the BMC Recovery Manager reports. Table 61 Report types Report Description Summary Provides general status information for the data sources registered in the EPM. Each row represents summary information for a data source. Detail Provides detailed information from the most recently collected data for a selected data source. Each table represents detailed information for a data source. History Provides status details for a specified time period for a selected data source, and displays the output in table format. Graph Provides a graph (line chart) of the historical information for a selected data source. Note: Except for the recoverability graph report, which plots the raw data, all the other graphs represent rate of change (average) for a user-specified unit. NOTE For some report categories, only a summary report is available. For others, multiple report types are available depending on the activity for which you are requesting the report information. Appendix C BMC Recovery Manager reports 157 Report categories and types Policy reports The Policy reports provide information about the policies that are defined in the Enterprise Policy Monitor (EPM) and the policy assignments and statuses for data sources for all registered database server hosts. Table 62 lists the reports that are available from the Policy reports menu. Table 62 Policy reports Report name Description Policy Change History Reports the policy assignment date and changes that have occurred to the policy attributes over the specified time period for selected data sources. For an example of this report, see “Policy Change History report” on page 159. Policy Compliance Reports the policy status for data sources for all registered database server hosts. Choose Detail or Summary for the report type. The policy status value indicates whether the policy is in compliance with all backup and recovery rules. If any single attribute is out of compliance with the policy, this value indicates a failure status. Policy Definition Summary Lists policy values for all defined policies and the policy compliance status for assigned data sources. For an example of this report, see “Policy Definition Summary report” on page 159. Policy Non-Compliance History Reports out-of-compliance data for the selected data sources during the time period that you specify. For an example of this report, see “Policy Non-Compliance History report” on page 161. NOTE In the Policy Definition Summary report, an absence of data source information for a policy listing indicates that no data source is currently assigned to the policy. The Policy Compliance report and the Policy Non-Compliance History report are also available from the Compliance reports menu. 158 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Report categories and types Policy Change History report The Policy Change History report displays changes to policies. Policy changes are grouped by policy version. The report inserts a blank line between policy versions. Any change to a policy (such as a change to an attribute) constitutes a policy version change. Figure 12 shows an example of a Policy Change History report. Figure 12 Policy Change History report Policy Definition Summary report The Policy Definition Summary report displays policy definitions. For each policy definition, two pages are displayed. The first page displays the attributes of the policy. The second page displays the data sources to which the policy was applied. Figure 13 on page 160 shows the first page of a Policy Definition Summary report. Figure 14 on page 161 shows the second page of a Policy Definition Summary report. Appendix C BMC Recovery Manager reports 159 Report categories and types Figure 13 160 Policy Definition Summary report (page 1) BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Report categories and types Figure 14 Policy Definition Summary report (page 2) Policy Non-Compliance History report The Policy Non-Compliance History report displays policy attributes that were not in compliance. Policy noncompliance attributes are grouped by the date the policy was applied. The report inserts a blank line between policy dates. Figure 15 on page 162 shows an example of a Policy Non-Compliance History report. Appendix C BMC Recovery Manager reports 161 Report categories and types Figure 15 Policy Non-Compliance History report Compliance reports The Compliance reports provide information about license compliance and policy compliance for data sources for all registered database server hosts. Table 63 lists the reports that are available from the Compliance reports menu. Table 63 162 Compliance reports (Part 1 of 2) Report name Description License Compliance Projection Summary Projects license-out-of-compliance time lines for your BMC SQL-BackTrack installations, based on database growth and current license size requirements. License Compliance Status Summary Reports the data sources for all registered database server hosts that are in compliance with the assigned license policy. BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Report categories and types Table 63 Compliance reports (Part 2 of 2) Report name Description License Out of Compliance Summary Reports the data sources for all registered database server hosts that are not in compliance with the assigned license policy. Policy Compliance Reports the policy status for data sources for all registered database server hosts. Choose Detail or Summary for the report type. The policy status value indicates whether the policy is in compliance with all backup and recovery rules. If any single attribute is out of compliance with the policy, this value indicates a failure status. Policy Non-Compliance History Reports out-of-compliance data for the selected data sources during the time period that you specify. For an example of this report, see “Policy Non-Compliance History report” on page 161. NOTE The Policy Compliance report and the Policy Non-Compliance History report are also available from the Policy reports menu. Backup reports The Backup reports provide information about the status of backups that occurred for the data sources for all registered database server hosts. Table 64 on page 164 lists the reports that are available from the Backup reports menu. Appendix C BMC Recovery Manager reports 163 Report categories and types Table 64 Backup reports (Part 1 of 2) Report name Description Backup Compression Ratio (Graph) Plots the rate of change of the backup compression ratio for each backup completed during the time period specified for the selected data source. Backup Elapsed Time (Graph) Plots the rate of change of the backup elapsed time for each backup completed during the time period specified for the selected data source. The backup elapsed time value indicates how long (in minutes) the backup job took to complete. If the data source is currently being backed up, the value indicates how long it has been since the backup job started. Notes: Backup Final Compressed Size ■ If Indeterminate value is displayed, the EPM is not able to collect valid information for the related data source. In most cases, this occurs if the clocks for the policy hub host and database server host are not synchronized. ■ Elapsed times are not exact due to the frequency at which BMC Recovery Manager components collect information about a specific data source. Reports the final compressed size for each backup completed during the time period specified for the selected data source. Choose Graph or History for the report type. The graph plots the rate of change of the final compressed size. The final compressed time value indicates the final total size, in kilobytes, of the data that was backed up for the time period that you specify. Backup Status Reports the backup status for the selected data sources. Choose Detail for the backup status data for the last or current backup. Choose History for historical backup data for the time period that you specify. Backup Throughput Charts the backup throughput rate for all backups performed during the specified time period for the selected data sources. Choose Graph or History for the report type. The backup throughput rate value indicates the throughput rate at which data is backed up. The rate is expressed in kilobytes per second. Last Backup Summary 164 Reports the number of failed backups for the selected data sources. BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Report categories and types Table 64 Backup reports (Part 2 of 2) Report name Description Raw Backup Size Reports the raw backup size for all backups performed during the specified time period for the selected data sources. Choose Graph or History for the report type. The graph plots the rate of change of the raw backup size. The raw backup size value indicates the total size of the data, in kilobytes, selected for the time period that you specify. The size shown is the size of the data before compression takes place. Status Performance Summary Provides all the backup and recovery status information that you choose from a list of available columns for data sources for all registered database server hosts. For a list of columns from which you can choose, see “Backup and Recovery Status Performance Summary Report options” on page 167. For an example of this report, see “Status Performance Summary report” on page 170. Successful Backup Summary Provides information about all successful backups that occurred during the specified time period for the selected data sources. Unsuccessful Backup Summary Provides information about all failed backup attempts that occurred during the specified time period for the selected data sources. NOTE For additional details about current backup events, view the metrics in the EPM. Recovery reports The Recovery reports provide recovery status information for the data sources for all registered database server hosts. Table 65 on page 166 lists the reports that are available from the Recovery reports menu. Appendix C BMC Recovery Manager reports 165 Report categories and types Table 65 Recovery reports (Part 1 of 2) Report name Description Estimated Time To Recovery Reports the Estimated Time to Recovery for data sources based on the report type selected. Choose Graph, History, or Summary for the report type. The graph plots the rate of change of the estimated time to recovery. The Estimated Time to Recovery value indicates the estimated time it would take to recover the data source. The estimate is based on the elapsed time to recovery for the time period that you specify plus a user-definable compensation factor. Last Recovery Summary Reports the number of failed recoveries for data sources for all registered database server hosts and identifies the data sources and recoveries that failed. Recoverability Choose Graph or Summary for the report type. The Recoverability Summary report reports the data sources that have an assigned policy and have met the policy requirements. The Recoverability Graph report plots the estimated time to recovery for data sources for the time period that you specify. For an example of this report, see “Recoverability Graph report” on page 171. Recovery Elapsed Time (Graph) Plots the rate of change of the actual elapsed time to recover for all recoveries completed during the specified time period for the selected data sources, and plots the results in a graph. Notes Recovery Status ■ If Indeterminate value displays in this field, the EPM is not able to collect valid information for the related data source. In most cases this occurs if the clocks for the policy hub host and database server host are not synchronized. ■ Elapsed times are not exact due to the frequency at which BMC Recovery Manager components collect information about a specific data source. Reports the recovery status for the selected data sources. Choose Detail for the recovery status for the last or current recovery. Choose History for historical data for the time period that you specify. The status value displays the recovery status in a graphical form in the top-level monitoring summary view. 166 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Report categories and types Table 65 Recovery reports (Part 2 of 2) Report name Description Recovery Throughput Reports the rate of throughput for recoveries completed during the specified time period for the selected data sources. Choose Graph or History for the report type. The graph plots the rate of change of the recovery throughput. Status Performance Summary Provides all the backup and recovery status information that you choose from a list of available columns, for data sources for all registered database server hosts. For a list of columns from which you can choose, see “Backup and Recovery Status Performance Summary Report options” on page 167. For an example of this report, see “Status Performance Summary report” on page 170. Successful Recovery Summary Provides information about all successful recoveries that occurred for the data sources for all registered database server hosts. Test Recovery Reports the test recovery (dry-run recovery) status for the selected data sources. Choose Detail for the test recovery status data for the last or current test recovery. Choose History for historical test recovery data for the time period that you specify. NOTE For additional details about current recovery events, view the metrics in the EPM. Backup and Recovery Status Performance Summary Report options For the Backup or Recovery Status Performance Summary report, choose the columns to include in the report from the columns listed in Table 66. Select the column and click Up or Down to move the column in the report. Table 66 Backup and Recovery Status Performance Summary Report options (Part 1 of 4) Column Description Admin This value specifies the DBA or administrator that is associated with the data source. AdminGroup This value indicates the DBA or administrator group that is associated with the data source. Appendix C BMC Recovery Manager reports 167 Report categories and types Table 66 Backup and Recovery Status Performance Summary Report options (Part 2 of 4) Column Description Application This value specifies the application supported by the data source. ApplicationGroup This value specifies a group of applications supported by the data source. BackupCompressionRatio This value indicates the compression ratio for the backup. BackupElapsedTime This value indicates the elapsed time since this backup was started. Notes ■ If Indeterminate value displays in this field, the EPM is not able to collect valid information for the related data source. In most cases this occurs if the clocks for the policy hub host and database server host are not synchronized. ■ Elapsed times are not exact due to the frequency at which BMC Recovery Manager components collect information about a specific data source. BackupFinalCompressedSize This value indicates the final compressed size in KB of the last backup for this data source. BackupRate This value, measured in bytes per second, indicates the rate at which the data is being processed by the BMC SQL-BackTrack task. BackupRawSize This value indicates the raw size in KB of the last backup for this data source. BackupStatus This value indicates the status of the backup task and whether the task completed successfully. BackupType This value indicates the type of backup that was last performed for this data source. Valid values are ■ ■ ■ ■ ■ ■ ■ Full.offline Full.online Incremental.offline Incremental.online Delta.offline Delta.online Logical The types and formats of backups that are applicable for a particular data source depend on the DBMS of the database. For more information about the different types of backups, see the BMC SQL-BackTrack documentation for your DBMS. Cluster This value specifies the cluster name associated with the managed data source, if the database server host is part of a cluster. Customer 168 This value specifies the customer associated with the data source. BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Report categories and types Table 66 Backup and Recovery Status Performance Summary Report options (Part 3 of 4) Column Description DBMS This value indicates the database management system (DBMS) type of the data source. EstimatedTimeToRecovery This value indicates the estimated time necessary to recover this data source. ETSinceLastSuccessBackup This value indicates the amount of time that has passed since the last successful backup for this data source. ETSinceLastSuccessfulAutoRecoveryTest This value indicates the amount of time that has passed since an automated recovery test for this data source successfully completed. ETSinceLastSuccessRecovery This value indicates the amount of time that has passed since the last successful recovery occurred. ETSinceLastUpdatedDate This value indicates the amount of time that has passed since the information for this data source was updated. HostName This value indicates the name of the host computer on which the BMC SQL-BackTrack installation that is managing the data source resides. LastAutoRecoveryTestDate This value indicates the date and time that an automated recovery test was last attempted for this data source. LastBackupAttemptDate This value indicates the date and time that a backup was last attempted for this data source. LastRecoveryAttemptDate This value indicates the date and time that a recovery was last attempted for this data source. LastSuccessfulAutoRecoveryTestDate This value indicates the date and time that the last automated recovery test for this data source occurred. LastSuccessfulBackupDate This value indicates the date and time of the last backup that completed successfully for this data source. LastSuccessfulRecoveryDate This value indicates the date and time of the last successful recovery of this data source. LastUpdatedDate This value indicates the date and time that the information for this data source was last updated. Location This value identifies the location associated with the data source. OSName This value identifies the operating system of the database server host. PolicyName This value indicates the name of the backup and recovery policy assigned to this data source. PolicyStatus This value indicates whether the actual backup and recovery metrics collected for the data source meet the requirements specified in the backup and recovery policy. Appendix C BMC Recovery Manager reports 169 Report categories and types Table 66 Backup and Recovery Status Performance Summary Report options (Part 4 of 4) Column Description RecoveryElapsedTime This value indicates the elapsed time since this task was started. Notes ■ If Indeterminate value displays in this field, the EPM is not able to collect valid information for the related data source. In most cases this occurs if the clocks for the policy hub host and database server host are not synchronized. ■ Elapsed times are not exact due to the frequency at which BMC Recovery Manager components collect information about a specific data source. RecoveryRate This value indicates the rate at which the data is being recovered in bytes per second. RecoveryStatus This value indicates the status of the recovery task and whether the task completed successfully. RecoveryType This value indicates the type of recovery last processed for this data source. Valid values are ■ ■ LOCALHOST REMOTEHOST SubBackupElapsedTime This value indicates percentage of elapsed time that the different backup phases took for the data source specified. SubDBBackupStatus This value indicates the status of the current phase of the backup task. SubDBRecoveryStatus This value indicates the status of the current phase of the recovery task. SubRecoveryElapsedTime This value indicates percentage of elapsed time that the different recovery phases took for the data source specified. TotalDatabaseSize This value indicates the total size of the data source. Status Performance Summary report The Status Performance Summary report displays selected information about a data source. You choose the columns to display from the list of columns shown in Table 66 on page 167. Figure 16 on page 171 shows an example of this report. 170 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Report categories and types Figure 16 Status Performance Summary report Recoverability Graph report The Recoverability Graph report plots the estimated time to recovery for a data source for the time period specified. The graph charts the estimated policy violation date. Figure 17 on page 172 shows an example of this report. Appendix C BMC Recovery Manager reports 171 Report categories and types Figure 17 Recoverability Chart report Miscellaneous reports Miscellaneous reports provide general information about the data sources for all registered database server hosts. Table 67 on page 173 lists the reports that are available from the Miscellaneous reports menu. 172 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Report categories and types Table 67 Miscellaneous reports Report name Description Job Definition History Reports information about all backup and recovery jobs that occurred for a specified data source. Total Database Size Reports changes in the total database size over a specified time period. Choose Graph or History for the report type. The total database size value indicates the total size of the data source in megabytes. For an example of this report, see “Total Database Size Graph report.”. Total Database Size Graph report The Total Database Size Graph report graphs the changes in the database size over a specified period of time. Appendix C BMC Recovery Manager reports 173 Report categories and types Figure 18 Total Database Size Graph report Using custom attributes in reports The Enterprise Policy Monitor allows you to customize the following reports using the Custom Attributes tab in the EPM console or the -ca option with the empreport command: ■ ■ ■ ■ ■ ■ ■ ■ 174 EstimatedTimeToRecoverySummaryReport LastBackupSummaryReport LastRecoverySummaryReport PolicyComplianceSummaryReport ReconvertabilitySummaryReport SuccessfulBackupSummaryReport UnSuccessfulBackupSummaryReport SuccessfulRecoverySummaryReport BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Report categories and types For these Summary report, choose the custom attributes columns to include in the report from the custom attributes columns listed in Table 68. Select the column and click Up or Down to move the column in the report. Table 68 Custom attribute Summary Report options Custom Attribute column Description Admin This value specifies the DBA or administrator that is associated with the data source. AdminGroup This value indicates the DBA or administrator group that is associated with the data source. Application This value specifies the application supported by the data source. ApplicationGroup This value specifies a group of applications supported by the data source. Cluster This value specifies the cluster name associated with the managed data source, if the database server host is part of a cluster Customer This value specifies the customer associated with the data source. Location This value identifies the location associated with the data source. Appendix C BMC Recovery Manager reports 175 Report categories and types 176 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started A B C D E F G H I J K L M N O P Q R S T U V W X Y Z Glossary B BMC Recovery Manager services A set of services installed on the database server host that collect status and performance metrics from BMC SQL-BackTrack and send the metrics to the policy hub. The BMC Recovery Manager services are installed with BMC SQL-BackTrack utilities version 5.0.00 and later. C calculated metrics Metrics that are calculated values based on measured and collected metrics (for example, the throughput rate value that measures blocks moved per minute). client Any computer from which you access the policy hub. Your client computer may be the same computer on which you installed the policy hub. (The policy hub is automatically installed on the computer on which you install the EPM client.) You can choose to install the client files on a separate computer from the policy hub by installing the EPM remote client. collected metrics Metrics that are collected periodically and indicate statistical information and trends (such as percent complete of each phase in a job). custom attribute An attribute that you associate with a database through the Enterprise Policy Monitor. These attributes include admin, admin group, application, application group, customer, and location. D database server host A host computer that contains databases managed by one of the BMC SQL-BackTrack utilities and monitored through BMC Recovery Manager. data model The design of the policy hub. data source The database entity representing the recoverable unit for a particular database management system (DBMS) type. The data source is the database for most DBMS types and a partition for Glossary 177 A B C D E F G H I J K L M N O P Q R S T U V W X Y Z DB2 UDB. Data sources reside on a database server host, are associated with a BMC SQL-BackTrack installation, and are monitored through BMC Recovery Manager components and services. discovery The process by which BMC Recovery Manager identifies BMC SQL-BackTrack installations and supported databases on the database server hosts in the enterprise. E e-mail list A list of one or more distribution lists associated with one or more failure types. E-mail lists are assigned to data sources monitored by BMC Recovery Manager. When an e-mail list is triggered, an e-mail notification message is sent to the contacts on the associated distribution lists. Enterprise Policy Monitor The graphical user interface (GUI) for BMC Recovery Manager. F failure types The type of failure for which an e-mail list can be created. The failure types include backup, recovery, and policy failures. filter A method of limiting the databases displayed in the Enterprise Policy Monitor by showing only those databases that match criteria selected by the user. BMC Recovery Manager supports predefined filters and user-defined filters. J job An action directly or indirectly related to the backup or recovery of databases that was invoked using a BMC SQL-BackTrack utility. A job has an identifiable beginning, run, and result. M measured metrics Metrics that the BMC SQL-BackTrack utility provides, such as the number of blocks processed during a backup. metrics Information about the data sources that is based on data gathered from the BMC SQL-BackTrack utility and processed by the BMC Recovery Manager services on the database server host. The types of metrics gathered include measured metrics, calculated metrics, and collected metrics. 178 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started A B C D E F G H I J K L M N O P Q R S T U V W X Y Z P personalization The ability of users to customize data presentation in the Enterprise Policy Monitor, including defining custom filters and selecting what data to display, sort, and group. Users can save these customizations. policy A set of rules that the user can define through the Enterprise Policy Monitor that describe requirements for backup or recovery processing. The Enterprise Policy Monitor indicates which databases are in or out of compliance with the assigned policy. policy hub Stores all of the information gathered from the data sources on database server hosts that have been registered with the Enterprise Policy Monitor. The policy hub also stores information, including policy information and custom attributes, that you define through the Enterprise Policy Monitor. policy hub service A service that provides access to the configuration and metric data stored in the policy hub, computes derived metrics, and applies audit policies to this data. The policy hub service is installed with the policy hub. predefined filter A filter in the Enterprise Policy Monitor that is provided by the product. T task A portion of a job. One or more tasks form a job. A hierarchy of tasks compose a given job, with parent tasks spawning child tasks. U user-defined filter A filter in the Enterprise Policy Monitor that is defined by a user. Glossary 179 A B C D E F G H I J K L M N O P Q R S T U V W X Y Z 180 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started A B C D E F G H I J K L M N O P Q R S T U V W X Y Z Index A accessing Help 42 application server defined 18 function 18 architecture, BMC Recovery Manager 16 assigning e-mail lists to data sources 84 Attribute table 119 B backing up the policy hub automatically 53 BackTrackConfig table 126 BackTrackInstall table 119 BackTrackInstall_DataSourceDetail table 120 backup entries, ebrdr.cfg file 53 BackupPolicyDetail table 139 BMC Impact Explorer 73 BMC Recovery Manager architecture 16 installing 23 key concepts 18 reports 147 software components 17 BMC Software, contacting 2 bmc_pdm file 95 BMS integration tasks 70 BSM integration architecture 68 components 68 components, installing 69 C clearing, Java cache 109 commands, epmreport 147 components, BMC Recovery Manager 17 configuring BSM integration 70 database server host components 25 e-mail notification 78 EPM to send policy events to a master cell 71 policy hub 25 the EPM to send policy events to a master cell 71 connecting, to policy hub 38 contacts creating 78, 81 deleting 81 editing 81 exporting 81 importing 81 managing 81 modifying 81 creating contacts 78, 81 distribution lists 78, 82 e-mail lists 78, 83, 84 service model 72 CSV import file 82 customer support 3 D data expiration, managing 57 data models configuration data 119 defined 116 metric data 129 policy data 137 understanding 116 data sets and user defined roles 63 creating 62 data sources assigning e-mail lists to 84 database server host 18 defined 18 function 18 database server host BMC Recovery Manager services 17, 102 defined 17 DataModel table 121 DataSource table 121 DataSourceAttribute table 122 DataSourceDetail table 122 DataSourcePolicyHistory table 139 DataSourceTaskDetail table 129 DataSourceTaskPhase table 127 DataSourceTaskProperty table 128 Index 181 A B C D E F G H I J K L M N O P Q R S T U V W X Y Z DataSourceTaskSummary table 129 deleting contacts 81 distribution lists 82 e-mail lists 84 demonstration data file 31 diagram BMC Recovery Manager architecture 17 BMC Recovery Manager installation 24 disabling BSM events for a data source 71 distribution lists creating 78, 82 deleting 82 editing 82 managing 82 modifying 82 EPM data source 72 EPM Report command-line utility 147 EPM-BSM integration component installing 33 overview 68 required component 70 epmreport command examples 155 options 152 overview 151 syntax 151 errors, troubleshooting 93 expiry.cfg file defined 58 interactions with history tables 58 exporting contacts 81 exporting policy hub data 65 E F ebrDatabaseHostName parameter 91 ebrdbmigrate.bat utility 103 ebrdc.cfg file 88, 105 ebrDnsHostName parameter 88 ebrdr.cfg file 88 backup entries 53 data expiry entries 57 recovery entries 55 ebrIpAddress parameter 88 ebrsuperadmin 60 editing contacts 81 distribution lists 82 e-mail lists 84 e-mail lists assigning to data sources 84 creating 78, 83, 84 deleting 84 editing 84 managing 83 removing an assignment 84 turning off 84 turning on 84 e-mail notification overview 77 enabling BSM events for a data source 71 Enterprise Policy Monitor benefits 14 features 14 filter criteria window 42 monitor window 42 navigating online Help 43 starting 18 status bar 42 viewing online Help 42 failover environments node information, specifying 92 failure types 83 files bmc_pdm 95 CSV export 81 CSV import 81, 82 demonstration data 31 ebrdc.cfg 88, 105 ebrdr.cfg 57, 88 expiry.cfg 58 inittab 92 policy hub data 32 repdb.properties 96 server.xml 96 setuplinux.sh 27, 28 setupwin32.exe 27 uninstall.bat 35 wrapper.conf 90 For 53, 55 182 G group roles 64 H Host table 123 I importing contacts 81 importing policy hub data 65 inittab file 92 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started A B C D E F G H I J K L M N O P Q R S T U V W X Y Z installation planning 23 understanding requirements 23 installing BMC Recovery Manager components 23 BSM integration components 69 EPM clients files on a remote host 29, 30 EPM-BSM integration component 33 policy hub 27, 28 SQL-BackTrack with BMC Recovery Manager services 25 J Java cache, clearing 109 Job table 128 JobType table 129 L LicenseType table 124 M managing contacts 81 data expiration 57 distribution lists 82 e-mail lists 83 mapping roles 63, 64 metrics overview 19 types of 19 modifying contacts 81 distribution lists 82 e-mail lists 84 monitoring EPM policy events through the BMC Impact Explorer 73 N P planning installation 23 ports to allow in firewall 26 policies benefits 20 data tables 137 defined 20 function 20 requirement types 20 policy administration 45 policy hub backing up automatically 53 backing up manually 55 configuration data 116 data file 32 defined 18 function 18 history tables 124 installing 25 installing on Windows 27, 28, 29, 30 logging in 38 managing data expiration 57 metric data 116 querying 117 recovering automatically 55 recovering manually 57 tables. See tables, policy hub types of data within 116 uninstalling from Windows 35 validating automatically 55 verifying status 94 policy hub data exporting 65 importing 65 policy hub security 60–64 Policy table 140 PolicyDetail table 140 PolicyStatus table 142 PolicyStatusHistory table 143 port numbers resolving conflicts 95 privileges 60 product support 3 navigating, online Help 43 O Q querying, policy hub 117 online Help 42, 43 opsconfig.rdf file for failover environments 92 R recovering the policy hub automatically 55 Index 183 A B C D E F G H I J K L M N O P Q R S T U V W X Y Z recovering the policy hub (continued) manually 57 RecoveryPolicyDetail table 144 removing BMC Recovery Manager components 34 policy hub 35 removing an e-mail list assignment 84 repdb.properties file 96 reports generating from the command line 147 requirements, installation 24 resolving port conflicts 95 RunTimeTaskDetail table 129 S security 60–64 security tasks 62 server.xml file 96 service model, creating 72 setup.exe file 28 SMTP server, used for e-mail notification 78 starting database server host 102 status, verifying database server host 94 policy hub 94 stopping database server host 102 SubDataSourceTaskDetail table 130 SubDataSourceTaskSummary table 130 support, customer 3 U T tables, history 124 tables, policy hub Attribute 119 BackTrackConfig 126 BackTrackInstall 119 BackTrackInstall_DataSourceDetail 120 BackupExclusionParameter 145 BackupPolicyDetail 139 DataModel 121 DataSource 121 DataSourceAttribute 122 DataSourceDetail 122 DataSourcePolicyHistory 139 DataSourceTaskDetail 129 DataSourceTaskPhase 127 DataSourceTaskProperty 128 DataSourceTaskSummary 129 Host 123 Job 128 JobType 129 LicenseType 124 184 tables, policy hub (continued) Policy 140 PolicyDetail 140 PolicyStatus 142 PolicyStatusHistory 143 RecoveryPolicyDetail 144 RunTimeTaskDetail 129 SubDataSourceTaskDetail 130 SubDataSourceTaskSummary 130 TaskAlert 133 TaskDataSource 136 TaskMethod 133 TaskMode 134 TaskProperty 134 TaskScope 135 TaskStatus 135 UserInfo 144 task map, BMC Recovery Manager installation 24 TaskAlert table 133 TaskDataSource table 136 TaskMethod table 133 TaskMode table 134 TaskProperty table 134 TaskScope table 135 TaskStatus table 135 technical support 3 troubleshooting BMC Recovery Manager product upgrades 109 database server host issues 102 turning off an assigned e-mail list 84 turning on an assigned e-mail list 84 uninstall.bat file 35 uninstalling BMC Recovery Manager services from the database server host 34 policy hub 35 user defined roles 60, 63 user roles 60, 63 UserInfo table 144, 145 utilities ebrdbmigrate.bat 103 V validating, policy hub 55 viewing, online Help 42 W wrapper.conf file 90 BMC Recovery Manager for Databases: Enterprise Policy Monitor Getting Started Third-party product terms The following terms apply to third-party products that are included with or in a BMC Software product as described in the BMC Software, Inc., License Agreement that is applicable to the BMC Software product. Apache Software License, Version 1.1 This product includes the Apache software product found at www.apache.org and the Apache software product is distributed to us pursuant to the following terms and conditions: Copyright (c) 2000 The Apache Software Foundation. All rights reserved. 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. The end-user documentation included with the redistribution if any, must include the following acknowledgement: "This product includes software developed by the Apache Software Foundation (http://www.apache.org/)." Alternately, this acknowlegement may appear in the software itself, if and wherever such third-party acknowlegements normally appear. 4. The names "Apache", and "Apache Software Foundation" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact [email protected]. 5. Products derived from this software may not be called "Apache", nor may "Apache" appear in their name without prior written permission of the Apache Group. THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Apache Software License, Version 2.0 This product includes the Apache software product found at http://apache.org , and the Apache software product is distributed to us pursuant to the following terms and conditions: Copyright (c) 2000-2004 The Apache Software Foundation. All rights reserved. TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. GNU LESSER GENERAL PUBLIC LICENSE Various media for this product contain Jboss and JfreeChart ("Library"), which is licensed under the terms of the GNU Lesser General Public License, Version 2.1 ("LGPL"). Copies of the LGPL and the source code of the Library are provided on a separate distribution disk for this product.l The Library is: Jboss - © 2002 - 2005 Jboss Inc. All rights reserved.nc. All rights reserved JfreeChart - (C) Copyright 2000-2004, by Object Refinery Limited and Contributors. NO WARRANTY BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. The terms and conditions of the BMC Software agreement applicable to this product do not apply to the Library to the extent that any such term or condition imposes any further restriction on the exercise of any right with respect to the Library granted under the GPL. Certain object code of BMC software has been linked with the Library (the "Linked Software"). Although the terms of the LGPL are ambiguous and copyright law is uncertain with respect to application of the LGPL to Software, BMC is producing and distributing the Software in compliance with the LGPL to the extent the LGPL may apply. Accordingly, solely to the extent required by terms of the LGPL, the licensee of Software may modify the Software for the licensee's own use and reverse engineer the Software for debugging the permitted modifications. Sun Microsystems, Inc. Binary Code License Agreement 1. LICENSE TO USE. Sun grants you a non-exclusive and non-transferable license for the internal use only of the accompanying software and documentation and any error corrections provided by Sun (collectively "Software"), by the number of users and the class of computer hardware for which the corresponding fee has been paid. 2. RESTRICTIONS. Software is confidential and copyrighted. Title to Software and all associated intellectual property rights is retained by Sun and/or its licensors. Except as specifically authorized in any Supplemental License Terms, you may not make copies of Software, other than a single copy of Software for archival purposes. Unless enforcement is prohibited by applicable law, you may not modify, decompile, or reverse engineer Software. Licensee acknowledges that Licensed Software is not designed or intended for use in the design, construction, operation or maintenance of any nuclear facility. Sun Microsystems, Inc. disclaims any express or implied warranty of fitness for such uses. No right, title or interest in or to any trademark, service mark, logo or trade name of Sun or its licensors is granted under this Agreement. 3. LIMITED WARRANTY. Sun warrants to you that for a period of ninety (90) days from the date of purchase, as evidenced by a copy of the receipt, the media on which Software is furnished (if any) will be free of defects in materials and workmanship under normal use. Except for the foregoing, Software is provided "AS IS". Your exclusive remedy and Sun's entire liability under this limited warranty will be at Sun's option to replace Software media or refund the fee paid for Software. 4. DISCLAIMER OF WARRANTY. UNLESS SPECIFIED IN THIS AGREEMENT, 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 THESE DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. 5. LIMITATION OF LIABILITY. TO THE EXTENT NOT PROHIBITED BY LAW, IN NO EVENT WILL SUN OR ITS LICENSORS BE LIABLE FOR ANY LOST REVENUE, PROFIT OR DATA, OR FOR SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED REGARDLESS OF THE THEORY OF LIABILITY, ARISING OUT OF OR RELATED TO THE USE OF OR INABILITY TO USE SOFTWARE, EVEN IF SUN HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. In no event will Sun's liability to you, whether in contract, tort (including negligence), or otherwise, exceed the amount paid by you for Software under this Agreement. The foregoing limitations will apply even if the above stated warranty fails of its essential purpose. 6. Termination. This Agreement is effective until terminated. You may terminate this Agreement at any time by destroying all copies of Software. This Agreement will terminate immediately without notice from Sun if you fail to comply with any provision of this Agreement. Upon Termination, you must destroy all copies of Software. 7. Export Regulations. All Software and technical data delivered under this Agreement are subject to US export control laws and may be subject to export or import regulations in other countries. You agree to comply strictly with all such laws and regulations and acknowledge that you have the responsibility to obtain such licenses to export, re-export, or import as may be required after delivery to you. 8. U.S. Government Restricted Rights. If Software is being acquired by or on behalf of the U.S. Government or by a U.S. Government prime contractor or subcontractor (at any tier), then the Government's rights in Software and accompanying documentation will be only as set forth in this Agreement; this is in accordance with 48 CFR 227.7201 through 227.7202-4 (for Department of Defense (DOD) acquisitions) and with 48 CFR 2.101 and 12.212 (for non-DOD acquisitions). 9. Governing Law. Any action related to this Agreement will be governed by California law and controlling U.S. federal law. No choice of law rules of any jurisdiction will apply. 10. Severability. If any provision of this Agreement is held to be unenforceable, this Agreement will remain in effect with the provision omitted, unless omission would frustrate the intent of the parties, in which case this Agreement will immediately terminate. 11. Integration. This Agreement is the entire agreement between you and Sun relating to its subject matter. It supersedes all prior or contemporaneous oral or written communications, proposals, representations and warranties and prevails over any conflicting or additional terms of any quote, order, acknowledgment, or other communication between the parties relating to its subject matter during the term of this Agreement. No modification of this Agreement will be binding, unless in writing and signed by an authorized representative of each party. JAVA(TM) INTERFACE CLASSES JAVA API FOR XML-BASED RPC API CLASS FILES, VERSION 1.1 SUPPLEMENTAL LICENSE TERMS These supplemental license terms ("Supplemental Terms") add to or modify the terms of the Binary Code License Agreement (collectively, the "Agreement"). Capitalized terms not defined in these Supplemental Terms shall have the same meanings ascribed to them in the Agreement. These Supplemental Terms shall supersede any inconsistent or conflicting terms in the Agreement, or in any license contained within the Software. 1. Software Internal Use and Development License Grant. Subject to the terms and conditions of this Agreement, including, but not limited to Section 3 (Java(TM) Technology Restrictions) of these Supplemental Terms, Sun grants you a non-exclusive, non-transferable, limited license to reproduce internally and use internally the binary form of the Software, complete and unmodified, for the sole purpose of designing, developing and testing your Java applets and applications ("Programs"). 2. License to Distribute Software. In addition to the license granted in Section 1 (Software Internal Use and Development License Grant) of these Supplemental Terms, subject to the terms and conditions of this Agreement, including but not limited to Section 3 (Java Technology Restrictions), Sun grants you a non-exclusive, non-transferable, limited license to reproduce and distribute the Software in binary form only, provided that you (i) distribute the Software complete and unmodified and only bundled as part of your Programs, (ii) do not distribute additional software intended to replace any component(s) of the Software, (iii) do not remove or alter any proprietary legends or notices contained in the Software, (iv) only distribute the Software subject to a license agreement that protects Sun's interests consistent with the terms contained in this Agreement, and (v) agree to defend and indemnify Sun and its licensors from and against any damages, costs, liabilities, settlement amounts and/or expenses 3. Java Technology Restrictions. You may not modify the Java Platform Interface ("JPI", identified as classes contained within the "java" package or any subpackages of the "java" package), by creating additional classes within the JPI or otherwise causing the addition to or modification of the classes in the JPI. In the event that you create an additional class and associated API(s) which (i) extends the functionality of the Java Platform, and (ii) is exposed to third party software developers for the purpose of developing additional software which invokes such additional API, you must promptly publish broadly an accurate specification for such API for free use by all developers. You may not create, or authorize your licensees to create additional classes, interfaces, or subpackages that are in any way identified as "java", "javax", "sun" or similar convention as specified by Sun in any naming convention designation. 4. Trademarks and Logos. You acknowledge and agree as between you and Sun that Sun owns the SUN, SOLARIS, JAVA, JINI, FORTE, and iPLANET trademarks and all SUN, SOLARIS, JAVA, JINI, FORTE, and iPLANET-related trademarks, service marks, logos and other brand designations ("Sun Marks"), and you agree to comply with the Sun Trademark and Logo Usage Requirements currently located at http://www.sun.com/policies/trademarks. Any use you make of the Sun Marks inures to Sun's benefit. 5. Source Code. Software may contain source code that is provided solely for reference purposes pursuant to the terms of this Agreement. Source code may not be redistributed unless expressly provided for in this Agreement. 6. Termination for Infringement. Either party may terminate this Agreement immediately should any Software become, or in either party's opinion be likely to become, the subject of a claim of infringement of any intellectual property right. For inquiries please contact: Sun Microsystems, Inc. 4150 Network Circle, Santa Clara, California 95054 (LFI# 136499/Form ID# 011801) Bzip2 License Copyright (C) 1996-2005 Julian R Seward. All rights reserved. 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required. 3. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software. 4. The name of the author may not be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. *68020* *68020* *68020* *68020* *68020*