Catalogic DPX 4.3. Applications Guide. dpx4305/22/2014ag

Transcription

1 Catalogic DPX 4.3 Applications Guide dpx4305/22/2014ag

2 Catalogic Software, Inc., All rights reserved. This publication contains proprietary and confidential material, and is only for use by licensees of Catalogic DPX, Catalogic BEX, or Catalogic ECX proprietary software systems. This publication may not be reproduced in whole or in part, in any form, except with written permission from Catalogic Software. Catalogic, Catalogic Software, DPX, BEX, ECX, and NSB are trademarks of Catalogic Software, Inc. Backup Express is a registered trademark of Catalogic Software, Inc. All other company and product names used herein may be the trademarks of their respective owners.

3 Table of Contents Table of Contents Table of Contents 3 APPLICATIONS GUIDE OVERVIEW 5 Chapter 1: DPX Overview 6 Documentation, Knowledge Base, and Technical Support 6 Important Considerations 10 Chapter 2: Introduction to Applications Guide 11 Audience and Purpose 11 Topics Covered 11 DPX EXCHANGE MAILBOX RECOVERY and DPX SHAREPOINT OBJECT RECOVERY 12 Chapter 3: Using EMBR for Rapid Recovery of Exchange Mailbox Items 13 Introduction 13 How EMBR Works 13 How EMBR Works with Instant Access 13 Example Use of EMBR with Instant Access 13 Chapter 4: Using SPOR for Rapid Recovery of SharePoint Objects 17 Introduction 17 How SPOR Works 17 Supported Operating Systems and Applications 17 Additional Requirements 18 How SPOR Works with Instant Access 18 Using SPOR with Instant Access: A Quick Example 18 REPORTER 20 Chapter 5: Introduction to Reporter 21 About this Document 21 For Additional Information 22 Nomenclature 22 Important Considerations Before You Begin a Reporter Installation 22 Chapter 6: Installing Reporter 26 Chapter 7: Configuring Reporter 27 Step 1. Install Agent on the Master Server 27 Step 2. Configure the Master Server as a Reporter Resource 28 Step 3. Configure Virtualization VMware Resources 29 3

4 Table of Contents Step 4. Define Polling Resources 31 Chapter 8: Getting Started with Reporter 33 Logging In 33 Graphical User Interface Overview 33 Chapter 9: Uninstalling Reporter or Reporter Agents 35 ACRONYMS 36 TERMINOLOGY 43 TRADEMARKS 50 INDEX 53 4

5 APPLICATIONS GUIDE OVERVIEW APPLICATIONS GUIDE OVERVIEW DPX Overview on page 6 Introduction to Applications Guide on page 11 5

6 Chapter 1: DPX Overview Chapter 1: DPX Overview Catalogic DPX data protection software delivers unprecedented speed and savings with a single unified solution making backup and disaster recovery smarter, faster, and more efficient. It is uniquely designed to handle the most common data protection use cases that are challenging IT departments. DPX deploys quickly and scales easily to match the needs of rapidly growing cloud infrastructures. Additionally, the software exploits modern server virtualization and is optimized for backup and recovery of virtual systems. DPX Block Data Protection provides rapid and efficient backup, restore, bare metal recovery, application protection, and tape archiving. A complex backup environment can have multiple backup Enterprises each with more than one secondary system including NetApp storage and DPX open storage. There is one master server per data protection Enterprise. The master server is a DPX node that contains DPX software, including the Catalog and modules that control scheduling, media management, and distributed processing. Any other node in an Enterprise from which you may want to back up data is called a client. The master server may also be a client node. Note: For the latest system requirements and compatibility details regarding supported hardware, file systems, applications, operating systems, and service packs, go to System Requirements and Compatibility. Documentation, Knowledge Base, and Technical Support Documentation Roadmap The following documentation is available for Catalogic DPX : Quick Start Guide Deployment Guide User s Guide Reference Guide Bare Metal Recovery Guide Applications Guide Upgrade Assessment Tool Quick Start Guide Best Practices Troubleshooting Guide Documentation is available in both PDF and context-sensitive help invoked through DPX. You can find the documentation in the following locations: 6

7 Documentation, Knowledge Base, and Technical Support The MySupport website has the current documentation. For best results, use Internet Explorer to view the documentation PDFs. Select Help on the menu bar in the DPX management console. Navigate to the manuals directory on the product disk or in the ISO image to access the PDF documentation for the latest major release. Navigate to the directory on the master server where DPX was installed to find the documentation. Drill down to the \http\webapps\root\manuals directory to find the PDFs. Navigate to hostname or IP address>:6122/manuals/_document_library.pdf for a summary of available documentation. Tip: In Adobe Reader, clear the Open cross-document links in same window option to open links to additional DPX documentation while retaining your location in the original PDF. Clear this option in the Documents section on the Preferences window. For the latest customer notices, product documentation, and access to the Catalogic Software knowledge base, go to MySupport. Documentation Suite Overview The following describes the content included in each manual and indicates the intended audience. You are encouraged to read through this information for an understanding of where to find the information you are looking for. Also, use the Search and Index features in the Help system to locate pertinent information. In Help, you can search the entire documentation suite instead of searching through individual manuals. Quick Start Guide This document is intended for administrators and other end users of DPX. It is the starting point for understanding DPX documentation and provides a roadmap for using the documentation. The Quick Start Guide contains procedures for creating a NetApp storage volume or DPX open storage volume, provides procedures for a simple DPX backup and recovery scenario, and describes how to obtain additional information including technical support and online resources. Deployment Guide This document is intended for those who are responsible for setting up DPX at customer sites. This might be a Catalogic field technician or a NetApp certified field technician who also has familiarity with DPX and its licensing. The guide contains instructions for setting up a NetApp storage system for DPX backups. It also presents, in abbreviated form, procedures found in the User's Guide and Reference Guide, including installing DPX, running a software update, setting up a DPX Enterprise, setting up Catalog protection, setting up a tape library, and configuring media. At the conclusion of the implementation, the customer is ready to perform DPX backups and recoveries using the features provided by their DPX license. User s Guide This document is intended for administrators and other end users of DPX. It contains information and procedures for the most commonly used functions of Catalogic Data Protection Software. The topics covered in the User s Guide assume 7

8 Documentation, Knowledge Base, and Technical Support that your Enterprise is deployed and that the Catalogic Data Protection Software is installed and configured. The User s Guide includes: Product Overview. Describes the management console and procedures for launch and login. Disk-to-Disk Data Protection. Describes procedures for DPX Block Data Protection, remote seeding using NetApp storage or open storage, Instant Access to data, and NetApp SnapVault Management. Also, it provides an overview of Bare Metal Recovery. Virtual Environments. Describes Full Virtualization, Instant Virtualization, and Rapid Return to Production. Also, describes procedures for Agentless VMware Backup. Application Support. Describes data protection procedures for major applications, including SharePoint, Exchange, SQL Server, and Oracle. Includes the procedures for verifying the integrity of an application backup. Also, describes considerations for Windows and Novell OES Clusters. Maintenance. Describes procedures for maintaining the Catalog and for monitoring backup and restore jobs. Reference Guide This document is intended for administrators with appropriate licenses to use DPX features. Other users might be limited to a subset of the features. The Reference Guide contains information, considerations, and procedures for the less commonly used features of Catalogic Data Protection Software. The more commonly used functions are described in the User s Guide. The Reference Guide includes: Installation. Describes procedures for installing, upgrading, and updating DPX on Windows, Linux, and other platforms. Also includes information about protecting and maintaining the Catalog and describes administrator privileges and security considerations. Configuration. Describes procedures for configuring DPX by using the management console. Operation. Describes procedures for defining and running backup, copy, and restore jobs by using the management console and performing additional tasks using scripts. Also, includes details on controlling tape devices and migrating tapes, and managing reports and logs. Procedures for DPX Block Data Protection jobs are described in the User s Guide. Tape Library Setup. Describes procedures for creating the media changer device file needed to enable communication between DPX and the tape library as well as defining tape library properties. Clusters. Describes procedures for setting up a Windows or Novell cluster to work with DPX. Special Procedures. Describes procedures for setting up special tape libraries. Interfaces. Describes setup and usage of application interfaces not included in the User's Guide or Applications Guide. This includes NDMP backup and restore for disks and tapes. The remaining application interfaces are set up outside the management console. Bare Metal Recovery Guide This document is intended for administrators who must restore an entire system environment for an individual computer. A full recovery using Bare Metal Recovery includes the operating system, point-in-time backed up data, and Exchange, 8

9 Documentation, Knowledge Base, and Technical Support SQL Server, and Oracle applications if applicable. If the computer being recovered is a master server, Bare Metal Recovery restores the DPX application. The Bare Metal Recovery Guide describes procedures for restoring a machine with Windows and Linux. Applications Guide This document is intended for administrators and other end users of DPX that are licensed to use several special applications. Other commonly used functions and applications are described in the User s Guide and Reference Guide. The Applications Guide includes: DPX Exchange Mailbox Recovery. This application allows administrators to easily recover mailbox items from unmounted Exchange databases and Information Store files. Additionally, EMBR enables copying, searching, and analyzing and attachments. DPX SharePoint Object Recovery. This application allows administrators to find, recover, and restore entire SharePoint sites or individual SharePoint server objects. Additionally, SPOR can be used to locate and restore individual items, without having to restore entire databases, volumes, or servers. Reporter. This application enables robust reporting on nodes, storage, job progress, trending, exceptions, and more. Upgrade Assessment Tool Quick Start Guide This document is intended for administrators who want to upgrade to Catalogic DPX 4.3. It provides instruction on using the Upgrade Assessment Tool. The UAT scans your Enterprise and generates a report identifying feature differences and upgrade concerns you need to be aware of when upgrading from BEX 3.4 or Catalogic Data Protection Software 4.0 to DPX 4.3. Best Practices This document is targeted at DPX implementation professionals and advanced DPX administrators. The guidelines provided are based on deployment and administration experience, as well as best practices of the respective technology vendors. This document lists known parameters and configurations that lead to a successful DPX implementation. Use this document as a tool when architecting a solution that fits specific data protection needs. Troubleshooting Guide This document is intended for Catalogic Software Level 1 Support Engineers and advanced users of DPX. It provides answers to many frequently asked questions. Areas covered include compatibility and support, installation, configuration, general operations, Microsoft Exchange, Microsoft SQL Server, virtualization, and DPX Bare Metal Recovery. Knowledge Base In addition to the documentation suite, search the Knowledge Base for solutions and answers to your issues and questions. The Knowledge Base has solutions that can help you resolve many technical problems. We encourage you to search the Knowledge Base prior to contacting Catalogic Software Data Protection Technical Support for assistance. The Knowledge Base has thousands of solutions that can help you resolve many technical problems before opening a Service Request. You can find the knowledge base on MySupport. 9

10 Important Considerations Contacting Catalogic Software Data Protection Technical Support For issues relating to Catalogic Data Protection software, contact Catalogic Software Data Protection Technical Support. To contact us in the US or Canada: Call toll free (877) or (201) By To contact us in Europe, the Middle East, or Africa: By phone: Call toll free or By DPX provides a logs collection utility, bexcollect, for diagnostic purposes. The utility gathers informational files related to a specific job. If you contact Catalogic Software Data Protection Technical Support, you may be asked to run the utility and send the results for analysis. See Log Management in the Reference Guide. Tip: For NetApp or hardware related issues, contact your NetApp support representative at (888) 4NETAPP. For the latest system requirements and compatibility details regarding supported hardware, file systems, applications, operating systems, and service packs, go to System Requirements and Compatibility. Important Considerations Some features described in this guide are optional, separately licensable features. For inquiries regarding licensing of optional features, contact your data protection account representative or call (877) Catalogic DPX data protection software does not currently support Unicode for DPX-specific objects such as jobname, devicepath, qtree name, etc. Use the English character set only. Screen illustrations that appear in this guide may not match those found in your product implementation, due to variations in customization. For best results, use Internet Explorer to view the documentation PDFs. 10

11 Chapter 2: Introduction to Applications Guide Chapter 2: Introduction to Applications Guide Audience and Purpose The Catalogic DPX Applications Guide is intended for system administrators, administrators, and other end users of DPX that are licensed to use several special applications. Other commonly used functions and applications are described in the User s Guide and Reference Guide. Some features are optional, separately licensable features. For inquiries regarding licensing of optional features, contact your data protection account representative or call (877) Topics Covered The Catalogic DPX Applications Guide includes the following topics: Topic DPX Exchange Mailbox Recovery (EMBR) DPX SharePoint Object Recovery (SPOR) Reporter Description This application allows backup administrators to easily recover mailbox items from unmounted Exchange databases and Information Store files. Additionally, EMBR enables copying, searching, and analyzing and attachments. This application allows backup administrators to find, recover, and restore entire SharePoint sites or individual SharePoint server objects. Additionally, it can be used to locate and restore individual items, without having to restore entire databases, volumes, or servers. This application enables robust reporting on nodes, storage, job progress, trending, exceptions and more. 11

12 DPX EXCHANGE MAILBOX RECOVERY and DPX SHAREPOINT OBJECT RECOVERY DPX EXCHANGE MAILBOX RECOVERY and DPX SHAREPOINT OBJECT RECOVERY Using EMBR for Rapid Recovery of Exchange Mailbox Items on page 13 Using SPOR for Rapid Recovery of SharePoint Objects on page 17 12

13 Chapter 3: Using EMBR for Rapid Recovery of Exchange Mailbox Items Chapter 3: Using EMBR for Rapid Recovery of Exchange Mailbox Items Introduction DPX Exchange Mailbox Recovery allows backup administrators to easily recover mailbox items from unmounted Exchange databases and Information Store files. Additionally, EMBR enables copying, searching and analyzing and attachments. DPX can provide the backed up EDB files to EMBR through its Block backup functionality. The key is the Instant Access feature, which easily and rapidly mounts an Exchange backup instance to a Windows node. EMBR on this node can then quickly extract or search required items. This process is described below. How EMBR Works EMBR requires as input the backed up EDB files. These files should be local to a server (other than the Exchange Server) or workstation that has EMBR installed. EMBR can then open these files and either extract the individual items to a.pst file or import them directly into an online Exchange database. How EMBR Works with Instant Access Block backups of an Exchange server back up the logical volume (C:, D:, etc.) that contains the Exchange database files, which includes the EDB files. By virtue of the Block backup process, the database is backed up online once as a base backup; all subsequent backups are then block-level incremental backups, which greatly reduce CPU load, network traffic, and storage requirements. Any of the snapshots (one is created by each Block backup job) can then be mounted to a Windows node by using the IA feature. If EMBR is installed on this Windows node (the node should not be the Exchange Server), EMBR can then be used to extract mailbox items from the IA map. Example Use of EMBR with Instant Access For the example described below, a Windows 2003 Exchange server (IP ) was backed up three times using the Block backup functionality. The backup ran once as a base backup and subsequently as a block-level incremental backup. This created three recovery points of the E: drive on the secondary storage device. The third recovery point is then selected and IA mapped as the K: drive on a server that has EMBR installed (IP address in the example below): 13

14 Example Use of EMBR with Instant Access The IA function results in the K: drive on the server and this K: drive now houses the EDB files from when the Block backup ran (in this example, 3/25/09 12:12:13 PM). Note: There are two backup sets for Exchange: the data files (on the E: drive in the example) and the application itself on the EXCH volume. Only the data files can be IA-mapped. EMBR is then launched from the workstation and pointed to the location on the K: drive that contains the EDB files: 14

15 Example Use of EMBR with Instant Access The screen shot above shows the opened source file (K:\Program Files\Exchsrvr\MDBDATA\priv.edb) with all the mailboxes displayed in the top-left panel. The mailbox for user Louis is opened and the Inbox of that mailbox is shown (top-right panel). You can now search for mail items, or read s if needed (as shown in the open window above). To recover one or multiple s (or any of the objects shown above: Calendar, Contacts, Deleted Items, etc.) you can either save the items to be recovered to a.pst file, which can be sent to the user, who can read the items, or you can import the items to be recovered directly to an online Exchange server. To do the latter, point EMBR to the Exchange server, which will then populate the bottom Target information with the contents on the live mailbox. A recovery is then done by drag-and-dropping the items from Source panel to the Target panel as shown below: 15

16 Example Use of EMBR with Instant Access At the completion of the recovery EMBR is shut down and the IA map is unmapped. The recovery and search activities can be done with no impact to the online Exchange server. Instant Access used with EMBR is one example of the exceptional versatility and simplicity of DPX s access to snapshots generated by routine Block backups. Related Topics: Exchange 2010/2013 in the User's Guide Exchange 2003/2007 in the User's Guide Note: For the latest system requirements and compatibility details regarding supported hardware, file systems, applications, operating systems, and service packs, go to System Requirements and Compatibility. 16

17 Chapter 4: Using SPOR for Rapid Recovery of SharePoint Objects Chapter 4: Using SPOR for Rapid Recovery of SharePoint Objects Introduction You can use DPX SharePoint Object Recovery to find, recover, and restore entire SharePoint sites or individual SharePoint server objects such as documents, lists, libraries, and folders. Because SPOR reads existing content database backups directly, use it to locate and restore individual items, without having to restore entire databases, volumes, servers, etc. SPOR enables direct restores to any SharePoint server (or you can restore objects to any Windows-supported file system) thereby eliminating many constraints on same-server restores. With these unique SPOR features, you may find that your need for an additional recovery server is minimized. How SPOR Works To provide item-level restore functionality, SPOR must have the ability to access the content databases mapped/restored from the Block backup. SPOR can then read, extract, or export the data from the content databases to a selected SharePoint server or to a windows file system. Supported Operating Systems and Applications For the latest system requirements and compatibility details regarding supported hardware, file systems, applications, operating systems, and service packs, go to System Requirements and Compatibility. Considerations for SPOR with SQL Server: The following applies to both Clustered and Non-Clustered SQL Server platforms: When using SQL Server 2005, (32 bit or 64-bit) as your database server, you must install Microsoft SQL Server 2005 SP2, or a later version of that service pack. In addition, you must also install the Microsoft SQL Server 2005 Backward Compatibility Components for SQL Server package, which is one of the components of the Microsoft SQL Server 2008 Feature Pack, August 2008 installation package collection, and is available for download from the Microsoft Download Center website. The Microsoft SQL Server 2008 Feature Pack, August 2008 installation package collection contains many different items, but you will only need to install the Microsoft SQL Server 2005 Backward Compatibility Components for SQL Server package. SPOR does not support SQL 2000 database servers. If you use SQL Server 2000, you will be able to back up your databases using the SharePoint application and restore whole databases, but you will not be able to do an item-level restore from those backups. 17

18 Additional Requirements Additional Requirements Each SharePoint server that you intend to protect must have a native installation. How SPOR Works with Instant Access Before you can start using SPOR in your recovery efforts, DPX must create at least one base backup of a SharePoint volume. When you select a SharePoint volume for backup, it automatically includes a backup of each SQL content database hosted on that volume, including all.mdf,.ldf and/or.ndf database files. Note: The first backup process transfers all existing data from the volume. Any subsequent incremental backups will only transfer data for block-level changes to that volume. Using the Instant Access feature, you can mount any valid, block-level backup to a SPOR-enabled Windows node; using SPOR, you can access that volume, open the content database, and retrieve individual SharePoint objects. Using SPOR with Instant Access: A Quick Example In this example, assume that the backup functionality provided by DPX Block Data Protection has created a SharePoint backup of a Windows 2008 SQL server. This backup job ran once as a full backup of the Windows 2008 SQL server and it subsequently created a snapshot of the C: drive on the secondary storage device. When you use Instant Access on a server that has a SPOR installation, you can map this snapshot to a drive. See Mapping a Block Backup Instance to a Drive Letter in the User's Guide. A newly mapped drive contains an exact duplicate of each database file, as recorded for that specific date and time in the node s DPX Data Protection backup. Note: There are two available backups for SharePoint: the data files, as found in the C: drive on the physical node, and the application itself, which appears underneath the tree branch for the SharePoint virtual node. Instant Access only provides mapping functionality for data files. Making a Source Path Selection In this step, you launch SPOR from your SharePoint node and use IA mapping to select the G: drive as the source path. After you navigate through the path to the location of the content database to restore, SPOR displays a listing of all available SharePoint entities on-screen exactly as they appear in the content database backup. For more information about how to make a source path selection in SPOR, see the DPX SharePoint Object Recovery User Guide which can be found on the Applications CD. 18

19 Using SPOR with Instant Access: A Quick Example Making a Target Server Selection In the next step, you select a target server restore location. When making a target server selection, you can choose to select an alternate SharePoint database server or you can elect to save those individually recovered items in a new location on the same source server. See The DPX SharePoint Object Recovery User Guide which can be found on the Applications CD. Selecting Files, and Completing the Restore Process Using SPOR, you can drill down through the file structure and browse the sites, documents, folders, lists, and libraries to locate the items to restore. You can also perform a search based on multiple criteria, searching across one or more content databases, and you can elect to see all available versions of a file in one screen. To execute the recovery of one or more SharePoint objects, drag-and-drop each item from the Source panel to the Target panel. At the completion of the recovery, close the SPOR application. Related Topics: SharePoint in the User's Guide 19

20 REPORTER REPORTER Introduction to Reporter on page 21 Installing Reporter on page 26 Configuring Reporter on page 27 Getting Started with Reporter on page 33 Uninstalling Reporter or Reporter Agents on page 35 20

21 Chapter 5: Introduction to Reporter Chapter 5: Introduction to Reporter Reporter can help you schedule and monitor backup jobs for completion within a predefined processing window to reduce the load on servers, clients, and the network. Reporter enables access to robust sets of data related to the below topics: Node perspective. Provides information from the server, client, and job perspective and displays job sizes and throughput per node. Monitoring. Enables real-time monitoring of backup job status on all nodes, including in-progress, inactive, failed, and successful jobs. Alerts administrators to job failures and interruptions and helps them pinpoint time and cause. Post-job reports. Summarizes exceptions and cumulative data volumes. Reports also display the number of bytes backed up per job and the success/failure ratio within a specified period. Management reports. Generates reports that group backup servers for chargeback, SLA, and compliance needs. Trending. Provides trending information for backups, including total data backed up in the enterprise, throughput, and success rate trends. Forecasts. Predicts available disk space based on backup history and storage capacity. Multiple backup server data. Provides a cumulative view if multiple master servers are deployed. Master server reports. Indicates operating system performance, available disk space, network usage, HBA card status, and system errors for the master server. Exception reports. Pre-defined daily and cumulative reports identify failed and inactive jobs by client and group. Reports also provide group details, weekly summaries per group, server details, and weekly server summaries. Media reports. Displays detailed media information, including listings of free tapes per media pool, tapes requiring removal from the tape library, and tapes that can be brought back into production. A predefined report lists tapes for tape library export and import. Sub-reports include offsite-to-onsite, onsite-to-offsite, tape pools, and jobs-per-tape. Customizable reporting. A report wizard and numerous templates enable administrators to design reports to meet specific analysis needs. The report wizard can be used to modify existing reports, create new reports, and define sets of reports. Notifications. Versatile notifications can utilize , Web, SNMP for third party applications, and paging. About this Document This document describes how to install Reporter and configure resources for reporting. The major installation and configuration steps are: Install Reporter on a server. See Installing Reporter on page

22 For Additional Information Install the Reporter agent on the master server. See Step 1. Install Agent on the Master Server on page 27. Use Reporter to configure the master server as a Reporter resource. See Step 2. Configure the Master Server as a Reporter Resource on page 28. Use Reporter to configure VM resources if necessary. See Step 3. Configure Virtualization VMware Resources on page 29. Use Reporter to define polling resources. See Step 4. Define Polling Resources on page 31. This document also describes: How to login to Reporter and briefly describes elements of the interface. See Getting Started with Reporter on page 33. How to uninstall Reporter. See Uninstalling Reporter or Reporter Agents on page 35. For Additional Information For a description of Reporter features and configuration options, see the Reporter online documentation. Nomenclature In this topic, Reporter software, running on the Reporter server, is referred to as Reporter" or "DPX Reporter". In other documentation and in the product, Reporter software may be referred to as Reporter Server to distinguish it from Reporter Agent, which runs on machines to be monitored by Reporter. In this topic Reporter always refers to the server software, unless agent is specified. Important Considerations Before You Begin a Reporter Installation The following points should be noted before you begin installing or upgrading Reporter. General Considerations Note the following general considerations before installing Reporter: Reporter server is recommended for use with Windows 2003 and 2008 (x32 and x64). Reporter agent is recommended for use with Windows 2003 and 2008 (x32 and x64). It is also compatible with Windows 2003 and XP Professional, along with the Red Hat Linux, CentOS, SUSE Linux Enterprise, and Sun Solaris 10 operating systems. For full compatibility with DPX, DPX Reporter or later is required. For the latest system requirements and compatibility details regarding supported hardware, file systems, applications, operating systems, and service packs, go to System Requirements and Compatibility. 22

23 Important Considerations Before You Begin a Reporter Installation Reporter uses the following ports: Port 9000 as its Web Server Port (HTTP) for the GUI. This port can be changed in server.xml. Port 4319 as its communications port with Reporter Agents (HTTP). This port can be changed system wide or on an agent-by-agent basis. Port 162 as a trap listener. This port can be changed through the server setup. Related Topics: Administrative Privileges and Security Considerations in the Reference Guide Installing Reporter on a master server is not recommended. Reporter Server installs six services: MySQL (Reporter database): the MySQL repository for all data collected by Reporter. ReporterCollector (collector): collects data from agents. ReporterEventReceiver (event receiver): receives traps. ReporterMaintenance: runs maintenance routines in the background. ReporterPoller (poller): remotely polls devices or applications by a variety of methods. ReporterWebServer (web server): the Tomcat web server. An installation or upgrade does not require a reboot. Installing Reporter Server on a RAID or cluster drive is not recommended. The Reporter database should be excluded from normal backups and real time virus scans. For instructions to back up the database, request the document "Backing up the Reporter Database" from Catalogic Software Data Protection Technical Support. The Reporter server requires 3 GB memory, comprised of the following: Database: 512 MB Web Server: 512 MB Collector: 512 MB Event Receiver: 512 MB Maintenance Server: 256 MB Poller: 256 MB 23

24 Important Considerations Before You Begin a Reporter Installation Considerations for Fresh Install Note the following considerations for a fresh install of Reporter: Before installing, close any services windows. Installation will not work properly if you leave any of these windows open during install. If you have installed MySQL separately before installing Reporter, the installation will be terminated, since Windows can support only one instance of MySQL at a time. Before installing, stop the MySQL Windows service (if any) and then uninstall MySQL. Warning: Do not manually delete any MySQL directories even after uninstall is completed. Old database data is located under the MySQL install directory. All Reporter binary and data files are located under the installation directory. When installing, select a directory located on a partition with enough space (1 GB recommended) to store Reporter data files. If you are installing Reporter for the first time, you will need a license file from Catalogic Software to run Reporter. Catalogic Software Data Protection Technical Support and provide the IP address and MAC address of the machine where Reporter is to be installed. You will receive an with the appropriate license file attached. Follow the license application instructions, as specified in this , when applying this Reporter license. Considerations for Upgrades Note the following considerations for an upgrade installation of Reporter: The installation process will detect and upgrade previous versions of Reporter automatically. All historical data will be retained. Tip: It is highly recommended to back up your entire Reporter directory before upgrading to a new version of Reporter. The upgrade makes a physical copy of your database. Before upgrading, make sure you have free space equal to at least twice the current database size (for example if your database is 1 GB, ensure 2 GB of free space is available on that drive BEFORE starting the upgrade. Before upgrading, close any services windows. Installation will not work properly if you leave any of these windows open during installation. Close any applications viewing or editing a file or directory in the old installation directory. Versions older than are no longer upgraded with this release. If you have a version older than 3.8.6, upgrade to or later then upgrade to this version. You can reinstall Reporter, but you must first uninstall the existing software. You cannot reinstall over an existing installation. Tip: All previous data may be deleted after reinstallation. It is highly recommended that you do a backup of your entire Reporter directory before reinstallation. If you are upgrading Reporter, you will be prompted for a license key: 24

25 Important Considerations Before You Begin a Reporter Installation If you are upgrading from release 4.x, you do not need a new key. Click No; the existing license key will be used. If you are upgrading from a release earlier than 4.x, you will need a new license key. Click Yes and choose the new license key. An upgrade DOES NOT retain the current password for the Reporter database. If you are moving Reporter to a different host and/or switching IP addresses, you must request a new Reporter license, one that will accommodate the new MAC address assignment. For more information, obtain a copy of "Moving your Reporter Server" from Catalogic Software Data Protection Technical Support. 25

26 Chapter 6: Installing Reporter Chapter 6: Installing Reporter Install Reporter on any server that can communicate with the master server, as long as that Reporter installation will run on a supported operating system. Note: It is not recommended to install Reporter on your master server or any device server. Tip: 3 GB of space on the installed partition is recommended for installation and subsequent log file growth. To install Reporter: 1. Run <product>reporter_server-windows-xxx.exe (where xxx is the version number) from the Reporter installation CD. If you do not have a Reporter CD, contact Catalogic Software Data Protection Technical Support to get the URL for downloading the install.exe file from the Catalogic Software website. 2. You will be prompted for a destination folder. Accept the default or browse to another folder. Click Next. 3. You will be asked to specify a password for the database installed as part of Reporter. Supply the password and click Next. Tip: The database password is needed for assistance from Catalogic Software Data Protection Technical Support, so be sure to make a note of it in case you need support in the future. 4. You will be prompted to specify the Server Address (the IP Address used by the Reporter server), the Agent Port, and the SNMP Port. The Agent Port is used by the Reporter server to communicate with Reporter agents. The SNMP Port is used by the Reporter server to detect SNMP traps sent from configured devices. Accept the default values. The Reporter server stores this information to enable accurate configuration of the Reporter agents, discussed later in this instruction set. Click Next. 5. The Services Setup screen appears. Note that Reporter creates six services on your system as part of the installation. Five core services are created for Reporter plus a service for the backend database. It is recommended to accept the default values on the Services Setup screen. Click Next to install. 6. You will be prompted for a license key. If you click Yes, you can then browse for the license key. Select the license key file and click Open. Then click Next. Click Finish to complete the installation. 26

27 Chapter 7: Configuring Reporter Chapter 7: Configuring Reporter Following installation of Reporter, double-click the Reporter icon on the desktop. This opens a Web connection to the Reporter Web server on port If you chose to use a machine elsewhere on the network, type the URL, using either the domain name or IP address of your Reporter Server followed by a colon and the number If you successfully completed the installation, the Reporter login screen appears. The default username is admin and the default password is admin. To complete the setup of your Reporter environment, do the following: Step 1. Install a Reporter agent on the master server (and on other servers as needed to monitor their server activity not related to DPX). Step 2. Configure the master server agent (and other server agents as needed to monitor their server activity not related to DPX). Step 3. Configure Virtualization VMware Resources as needed. Step 4. Define Polling Resources. Step 1. Install Agent on the Master Server As a prerequisite for backup reporting, install a Reporter agent on your master server: 1. In Agents folder on the CD, locate the executable file for the operating system of your master server. For the latest system requirements and compatibility details regarding supported hardware, file systems, applications, operating systems, and service packs, go to System Requirements and Compatibility. Installing a Reporter agent on the master server is all that is required to monitor server activity of the master server itself. The agent on the master server does not enable monitoring of overall server activity on servers in the Enterprise, only related activity on those servers. 2. After agent software is installed on the master server, you will be prompted for Server Name (host name or IP address) of the Reporter server, the Agent Web Port (HTTP), and the Server Trap Port (SNMP). The ports should be identical to those you set up during installation of Reporter. See Installing Reporter on page 26. Tip: On the Resources screen, the port settings are displayed when you click in the Agent column for a machine. 3. Click Next. You will then be prompted for the default installation path of the agent software. The Windows default is product-directory\program Files\DPX\Reporter Agent. (Where product-directory represents the directory in which DPX was installed.) Other operating systems will have other defaults. In all cases, you can change the default path. After completing the Reporter agent installation, ReporterAgent is listed as a service among other Windows services. 27

28 Step 2. Configure the Master Server as a Reporter Resource Step 2. Configure the Master Server as a Reporter Resource After installing the appropriate resource agent on the master server, perform the following steps on the Reporter server to complete the configuration of your Agent: 1. On the main Reporter screen, select the Resources link under the Administration folder. The Resources screen appears. 2. From the drop-down list at the upper left, select Catalogic and click Add. The Create New Resource for Agent screen appears 3. Enter values for fields: Server IP Address: Select your master server. Resource Display Name: Enter a descriptive name for your master server (for example, win-210). Active: This check box is selected by default. It enables the Reporter agent to collect your Enterprise data. Accept the selection. Licensing: This check box is selected by default. Accept the selection. Location: Enter the location of DPX, usually c:\program Files\DPX. Click Save. The Configure Resource screen appears. 4. Configure Reporter agents by entering values in fields on the Configure Resource screen: Monitor Backup Server: Select whether or not to monitor backup/restore activity on the master server. Level of the Log: Select the level of detail the client agent will log. Install Dir: Enter the path of the install directory of DPX. Note that the default Windows path is C:\Program Files\DPX. User Name: Enter the user name used to log in to DPX. Password: Enter a password. Resource Name: Enter the resource name or IP address of the master server. Activity Frequency: Select how frequently the log file is monitored. The default frequency is five minutes. Media Frequency: Select how frequently the media database is monitored. The default frequency is twenty four hours. Click Save. This will return you to the Resources screen. 28

29 Step 3. Configure Virtualization VMware Resources On the Resources screen, the master server will display as two entries with same IP address: one entry is Reporter; the other entry is the master server. The master server entry enables Reporter to monitor computer activity on the master server. Note: On the Resources screen you will also see other resources, which are automatically discovered and added once agents are installed on those servers. Step 3. Configure Virtualization VMware Resources The following procedures apply to configuring agents in VMware environments. The procedures are described in the following two sections: Configuring VM Resources Configuring VM Virtual Center Resources Configuring VM Resources 1. On the main Reporter screen, select the Resources link under the Administration folder. The Resources screen appears. 2. From the drop-down list at the upper left, select Virtualization VMware ESX Host. Click Add. The Create New Resource for Agent: VMware ESX screen appears. 3. Enter values for fields on the Create New Resource for Agent: VMware ESX screen: Select Agent: Select a node that will communicate to DPX. This node can be any machine that has the Reporter agent installed. Note: Selecting the master server is not recommended. Tip: This node does not have to be in the Enterprise. Resource Display Name: Enter a descriptive name for your ESX master server. ESX IP Address: The IP address of your ESX Server. Active: Select this check box to enable the agent to collect VMware ESX data. Licensing: Select this check box. Click Save. A resources screen (Create New Resource for Agent: VMware ESX) appears. The added agent appears in the resources list in alphabetical order. 4. On the Resources screen, in the Agent column, select the agent you just added. The Configure Resource screen appears. 5. Configure Reporter VM ESX agents by entering values in fields under VMware Configuration (default values are recommended): 29

30 Step 3. Configure Virtualization VMware Resources Status: Select whether or not to monitor ESX activity. Selecting On ensures Reporter monitors your ESX server. URL: This is the path to the ESX server automatically generated based on the IP address. Accept the path provided. User Name: Enter the user name used to log in to the ESX host. Password: Enter the password used to log in to the ESX host. Config Frequency: Select how frequently to gather information on the ESX host. Performance Frequency: Select how frequently to gather information related to performance. Storage Frequency: Select how frequently to gather information related to storage. Collect Resource Pools: Specify whether or not to collect resource pool information for the ESX host. Click Save. This will return you to the Resources screen. 6. On the Resource screen, in the pane at the left, select Virtualization > Assign ESX Hosts. The host assignment screen appears. 7. On the host assignment screen: a. In the Assign By section, near the upper left, ensure the ESX radio button is selected. b. In the ESX Hosts section: i. In the Available field, select the ESX host to be monitored. ii. In the Reporter Data Collector field, select from the pull-down list the agent machine you previously defined for VM-related communication to Reporter. iii. In the Move field, use the down arrow to move items from Available to Selected. To deselect items, use the up arrow to move items from Selected to Available. c. Click Save. The Resources screen appears and the VM resource will be listed alphabetically. Configuring VM Virtual Center Resources 1. Select the Resources link under the Administration folder. The Resources screen appears. 2. From the drop-down list at the upper left, select Virtualization VMware VC Instance. Click Add. The Create New Resource for Agent: VMware VC appears. 3. Enter values for fields on the Create New Resource for Agent: VMware VC screen: Select Agent: Select a node that will communicate to DPX. This node can any machine that has the Reporter agent installed. Note: Selecting the master server is not recommended. 30

31 Step 4. Define Polling Resources Tip: This node does not have to be in the Enterprise. Resource Display Name: Enter a descriptive name for your VC server. VMware VC IP Address: The IP address of your VC server Click Save. The Configure Resource screen appears. 4. On the Configure Resource screen, enter values for your VM VC server: Status: Select whether or not to monitor activity on the VC server. URL: This is the path to the Virtual Center automatically generated based on the IP address. Accept the path provided. User Name: Enter the user name used to log in to the Virtual Center. Password: Enter the password used to log in to the Virtual Center. Discovery Frequency: Select how frequently to monitor Virtual Center clients. Collect Orphaned VMDK: Select whether or not to collect orphaned VMDK files. Click Save. This will return you to the Resources screen, where the Virtual Center will appear in alphabetical order 5. On the Resources screen, in the pane at the left, select Virtualization > Assign ESX hosts. The host assignment screen appears. 6. On the host assignment screen: a. In the Virtual Center Instance section at the top, select a Virtual Center from the pull-down list. b. In the Assign By section, near the upper left, make sure the ESX radio button is selected. c. In the ESX Hosts section: i. In the Available field, select the Virtual Center to be monitored. ii. In the Reporter Data Collector field, select from the pull-down list the agent you previously defined for VMrelated communication to Reporter. iii. In the Move field, use the down arrow to move items from Available to Selected. To deselect items, use the up arrow to move items from Selected to Available. d. Click Save. The Resources screen appears. All the ESX hosts in the Virtual Center will be displayed. Step 4. Define Polling Resources Reporter supports devices that can be polled for status information such as NetApp storage devices. On the Reporter Server, you can define these devices under the Administration folder's Resources screen. 31

32 Step 4. Define Polling Resources To define hosts, click the Resources link under Administration folder. You can create a new resource by selecting the type of device you want to add and then by clicking Add in the upper right. You will need the IP address, the name of the resource, and other parameters, depending on the type of resource. Choose the groups to which you want the device to belong. Assign the license types you want to use on that resource. 32