HP StorageWorks Reference Information Storage System Administrator Guide T3559-96027 Part number: T3559-96027 First edition: March 2006
Legal and notice information © Copyright 2004-2005 Hewlett-Packard Development Company, L.P. Hewlett-Packard Company makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.
Contents About this guide . . . . . . . . . . . . . . . . . . . . . . . . . Intended audience . . . . . . . . Related documentation . . . . . . Document conventions and symbols HP technical support . . . . . . . Subscription service . . . . . . . Other web sites . . . . . . . . . Providing feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Managing available HTTP portals . . . . . . . . . . . . . . . . . Editing or deleting available LDAP connections . . . . . . . . . . . . Viewing DAS history logs . . . . . . . . . . . . . . . . . . . . . RISS Information view . . . . . . . . . . . . . . . . . . . . . . . . Displaying the RISS Information view . . . . . . . . . . . . . . . . Viewing system and domain information . . . . . . . . . . . . . . Viewing component information . . . . . . . . . . . . . . . . . . Selective Archiving folder . . . . .
Nagios folder . . . . . . . . . . . . . . . . . . . . . . . . . Nagios Info . . . . . . . . . . . . . . . . . . . . . . . . Program Information chart . . . . . . . . . . . . . . . . Process State Information chart . . . . . . . . . . . . . . Process Commands box . . . . . . . . . . . . . . . . Process Commands section . . . . . . . . . . . . . . . Nagios Stats . . . . . . . . . . . . . . . . . . . . . . . Scheduling Queue . . . . . . . . . . . . . . . . . . . . .
Status Grid . . . . . . . . . . . . . . . . . . Displaying specific hostgroups . . . . . . . . Displaying specific hosts . . . . . . . . . . Displaying all services running on specific hosts Displaying specific services . . . . . . . . . External Command Interface . . . . . . . . . . Example: Enabling or disabling notifications . . Example: Adding comments . . . . . . . . . Example: Acknowledging problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding repositories to simple routing rules . . . . . . Removing repositories from simple routing rules . . . . Managing routing filters . . . . . . . . . . . . . . . R0000000 Catchall Repository . . . . . . . . . . Routing filter examples . . . . . . . . . . . . . . Accessing Routing Filters panel . . . . . . . . . . Filtering list of routing rules . . . . . . . . . . . . Adding routing filters . . . . . . . . . . . . . . . Modifying routing filters . . . . . . . . . . . . . Deleting routing filters . . .
Tivoli Storage Manager . . . . . . . . . . . . . . . Gaining access to the RISS backup server . . . . . . . Smart cell data backups . . . . . . . . . . . . . . Separate Group Volumes . . . . . . . . . . . . . . TSM backup terms . . . . . . . . . . . . . . . . . How RISS configures TSM . . . . . . . . . . . . . . How to add and label new media (Web interface) . . . How to add and label new media (command line) . . . How to restore a smart cell . . . . . . . . . . . . .
Browser functionality . . . . . . . . . . . . Multi-user support . . . . . . . . . . . . . Configuring your system for Domino and Lotus Notes . . Requirements for Domino server configuration . . . Installing Email Miner for Lotus Notes . . . . . . . Administering Email Miner for Lotus Notes . . . . . Improving performance in Domino environments Installing and configuring the Lotus Notes plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figures 1 PCC user interface . . . . . . . . . . . . . . . . . . . . 2 User Management view (DAS) . . . . . . . . . . . . . . . 3 Create an LDAP connection . . . . . . . . . . . . . . . . 4 Create a new job . . . . . . . . . . . . . . . . . . . . . 5 Assign a job . . . . . . . . . . . . . . . . . . . . . . . 6 Mapping information . . . . . . . . . . . . . . . . . . . 7 Mapping advanced options . . . . . . . . . . . . . . . . 8 Assign a job to a portal . . . . . . . . . . . . . . . . . .
55 Mailbox store . . . . . . . . . . 56 Deletion settings . . . . . . . . . 57 Initial installation . . . . . . . . 58 Additional Servers installation . . . 59 Upgrade . . . . . . . . . . . . 60 Server Definition . . . . . . . . . 61 Processing options . . . . . . . . 62 Message and Title fields . . . . . 63 Logging options . . . . . . . . . 64 Options . . . . . . . . . . . . 65 Server Status . . . . . . . . . . 66 Specify mail user processing options 67 Import users . . . . . . . . . . .
Tables 1 Document conventions . . . . . . . . . . . . . . . . . . 2 RIM applications for users . . . . . . . . . . . . . . . . 3 RIM applications for administrators . . . . . . . . . . . . 4 Views for common system administration tasks . . . . . . . . 5 Views accessible from left menu . . . . . . . . . . . . . . 6 Smart cell life cycle states . . . . . . . . . . . . . . . . 7 Host status values . . . . . . . . . . . . . . . . . . . . 8 Service status values . . . . . . . . . . . . . . . . . . .
55 Nagios Stats view features . . . . . . . . . . . . . . . 56 Links to Nagios Stats view . . . . . . . . . . . . . . . . 57 Links from Nagios Stats view . . . . . . . . . . . . . . 58 Scheduling Queue view features . . . . . . . . . . . . . 59 Links to Scheduling Queue view . . . . . . . . . . . . . 60 Links from Scheduling Queue view . . . . . . . . . . . . 61 Email Reporter view features . . . . . . . . . . . . . . 62 Links to Email Reporter view . . . . . . . . . . . . . . . 63 Trends view features . .
115 Host Commands section, Host Information view . . . . . . 116 Service Information view features . . . . . . . . . . . . 117 Links to Service Information view . . . . . . . . . . . . 118 Links from Service Information view . . . . . . . . . . . 119 Service Commands section, Service Information view . . . 120 Status Grid view, Hostgroup features . . . . . . . . . . 121 Links to Status Grid view . . . . . . . . . . . . . . . . 122 Links from Status Grid view . . . . . . . . . . . . . . .
About this guide This guide provides information about: • Administering the HP StorageWorks Reference Information System (RISS) • Administering the HP StorageWorks Reference Information System (RIM) Intended audience This guide is intended for: • HP StorageWorks Reference Information System (RISS) administrators • HP StorageWorks Reference Information Management (RIM) administrators Related documentation In addition to this guide, HP provides the following on the documentation CD: • HP StorageWorks Refere
Document conventions and symbols Table 1 Document conventions Convention Element Medium blue text: Related documentation Cross-reference links and e-mail addresses Medium blue, underlined text (http://www.hp.
• • • • • • Technical support registration number (if applicable) Product serial numbers Product model names and numbers Applicable error messages Operating system type and revision level Detailed, specific questions For continuous quality improvement, calls may be recorded or monitored. Subscription service HP strongly recommends that customers register online using the Subscriber's choice web site: http://www.hp.com/go/e-updates.
About this guide
1 RISS overview This chapter describes key concepts involving the HP StorageWorks Reference Information Storage System (RISS) and Reference Information Manager (RIM). This chapter contains these topics: • RISS, page 21 • RIM, page 21 RISS RISS is a fault-tolerant, secure system of hardware and software that archives files and email messages for your organization, and lets you search for archived documents.
RISS overview
2 Platform Control Center (PCC) This chapter describes the Platform Control Center (PCC) tool for monitoring and troubleshooting RISS.
Figure 1 PCC user interface User interface orientation tips Views are often associated with several names or brief descriptions. To orient yourself, pay attention to the different ways a view is characterized. • Link text: A navigation link leading to a view is often the most specific description of the view.
For example, if you print the frame of the Event Log view, the printed page header may be Nagios Log File. • Open the view address (URL) in a browser window by itself, without any frames (without left menu). The browser window title shows the view's HTML name. For example, if you click the Event Log link in a separate window, the window title is Nagios Log File. Views for common tasks Table 4 Views for common system administration tasks Task View Check system health "Overview" on page 30.
Left menu views The left menu provides quick access to many PCC views. The left menu varies depending on how the system is configured. For example, systems not using replication do not have the Replication menu item available. Table 5 Views accessible from left menu Left menu item Description Overview, page 30 View high-level summary of system health. For each host group, shows how many hosts and services have each status value. View status of each host group without details.
Left menu item Description "Host Downtime" on page 64 View scheduled host and service downtimes. Schedule host and service downtimes, disabling notifications during downtimes. "Nagios Info" on page 66 View information about PCC host and service monitor. Control monitoring, check monitoring status, and enable and disable notifications globally for all hosts and services. "Nagios Stats" on page 68 View information about performance of PCC host and service monitoring. Check monitoring performance.
Monitoring and reporting methods System monitoring is reported online with a web-based (HTML) user interface and offline by email to selected contacts. Email reporting provides a subset of information provided online. Hosts and services are monitored by polling. You schedule polling intervals for services, but host polling is purposely kept to a minimum. Depending on the polling interval, there is more or less delay between occurrences on the system and reporting those occurrences in the PCC interface.
Life cycle state Definition Importance CLOSED Cell is full. Cell is available for document search and retrieval, but not storage. If backup is enabled, all cell data was backed up before cell entered this state. normal RESET Cell is being recycled. Stored documents and corresponding management data, such as document indexes, are destroyed during recycling. System administrator determined existing cell data is no longer needed. The RESET state is only set manually.
Table 8 Service status values Status Color Description PENDING Gray Service has not been checked for status since PCC monitoring started. OK Green Service is functioning normally. WARNING Yellow Service might have a problem. UNKNOWN Orange Service status cannot be determined. CRITICAL Red Service is not functioning correctly. Data storage and/or search and retrieval are adversely affected.
Table 9 Overview Status Summary view features Feature Description Host Status Totals Number of hosts: • with each status value (Up, Down, Unreachable, Pending) • with a problem (Down, Unreachable, Pending) • in the system (All Types) Service Status Totals Number of services: • with each service status value (Ok, Warning, Unknown, Critical, Pending) • with a problem (Warning, Unknown, Critical, Pending) • in the system (All Types) Status Summary For . . . Host Group . . .
Displaying services with a specific status In the System Status page, under Service Status Totals, click the status column heading, such as Critical. The Service Detail view appears. See "Service Detail" on page 57 for more information. Displaying specific host groups In the System Status page, under Status Summary for HostGroup, click the Host Group name, such as Smart Cells. The Service Overview view appears. See "Service Overview" on page 61 for more information.
Table 13 System Status view features Feature Description Smart Cell Domain Information • Name and status of domains in the system • Total number of messages currently stored in all domains • Total number of messages that could not be parsed (interpreted) or routed in all domains Messages with malformed message structure (MIME) or unsupported character sets cannot be parsed. They are placed in the catch-all repository with messages that fail to be routed.
Related Views • "Email Reporter" on page 70, configures a periodic email report similar to the System Status view information. • "Displaying the Smart Cell Groups for Domain view" on page 34, provides Store/Index/Indexer Latency graphs for individual smart cell groups.
Table 16 Smart Cell Groups for Domain view features, single group Feature Description smart-cell group ID number Smart-cell group identifier generated automatically by RISS. This number is unique across all systems. Primary • State • Store Rate • Index Rate • Archived • Indexed • Docs Failed • Last Updated IP address of primary smart cell of group. Additional primary smart cell information: • Current life cycle state of smart cell. See "Smart cell life cycle states" on page 28.
Table 19 Application Management view features Feature Description server group title Name of server group currently shown: • ALL Systems: All server groups • MINING Servers: All email mining servers • HTTP Servers: All HTTP portal servers • SMTP Servers: All SMTP portal servers • META Servers: All metaservers • SMARTCELLS Server: All smart cell servers Number If ALL Systems is displayed: • Number of server groups found in the system If specific server group is displayed: • Number of hosts in specific g
Table 20 Links to Application Management view Origin Link left menu Application Management Links from Application Management view: none Starting, stopping, and restarting servers on the system 1. Click the server group. 2. Click one of the following buttons: • Start: Start all systems or hosts in selected server group. • Stop: Stop all systems or hosts in selected server group. • Restart: Stop and immediately start all systems or hosts in selected server group.
Figure 2 User Management view (DAS) The Current Active Jobs section at the top lists all jobs created and assigned to an HTTP portal. Click the job name to edit the job properties, or click Controls to control the job and HTTP portal. The Global configuration section in the middle lists all jobs that can have an HTTP portal assigned to them, all HTTP portals that do not have jobs assigned to them, and all available LDAP connections.
• Click User Management in the left menu. Creating and running DAS jobs The basic flow for creating and running a DAS job from the User Management view: 1. Create an LDAP connection by clicking New LDAP. See Creating LDAP server connections. 2. Create the job by clicking New JOB. When you create a new job, you assign the job a name and an LDAP connection, and set up the job query into the LDAP server. See Creating jobs. 3. Assign the job to an HTTP portal. See Assigning HTTP portals. 4.
4. Click Create. 5. Return to the User Management view and verify that the new LDAP server connection is listed under Available LDAP connection(s). Creating jobs To create a DAS job: 1. In the User Management view, click New JOB. Figure 4 Create a new job 2. Name the job you are creating by entering it in the Job Name box. Click Next Step. Figure 5 Assign a job 3. From the list, select the LDAP connection you want to use with this job.
Figure 6 Mapping information 5. Complete the form by entering the following: • Source LDAP Domain name: Domain to which the users belong. For example: ldaptest.com. • User LDAP Starting Point: Root node where the user accounts are stored. For example: For Exchange, enter cn=Users,dc=ldaptest,dc=com for node Users in domain ldaptest.com. Value must specify relative location in the LDAP tree, including parent nodes and domain name.
Figure 7 Mapping advanced options 7. Complete the advanced options form by entering the following: • Group Name: Not used at this time. • USNChanged: Active Directory's unique sequence number (USN). Active Directory increments the USN for each change in any of its user accounts. When DAS finds a larger USN, it extracts new information. For initial setup, set USNChanged to 1 so DAS extracts all users. Thereafter, do not change this value. • Delete USNChanged: USN in deleted users directory.
• Delete LDAP Filter: Criteria to include or exclude specific users in the LDAP deleted users directory. Add to the default for special cases. For Domino, ignore this field because it is not enabled. • LDAP Query return attributes: List of return attributes. For example: For Exchange, use the default attributes unless your LDAP schema requires mapping changes. For Domino, use the following attributes: uid,sn,modifytimestamp,createtimestamp,cn,givenName,mail,sn,dominouid,dominodn.
1. In the User Management view, click Controls for the job you want to run. The DAS Control Panel displays the status on previous jobs (see "Viewing DAS history logs" on page 45 for more information). Figure 9 DAS Control Panel 2. Complete the form by entering the following: • DAS server IP: IP of the DAS HTTP portal where DAS runs this configuration. • Configuration Enabled: Select Activated to enable it. If not enabled, job cannot be scheduled or started with this console.
2. To edit the job, click Edit and then click Edit again to edit that corresponding section (LDAP connection, job mapping, or HTTP portal assignment). 3. To delete the job, click Delete. Managing available HTTP portals To start, stop, or restart the HTTP portals from the User Management view: 1. In the User Management view, click Controls or start/stop/restart next to Available HTTP Server(s). 2. Use the Application Management view to control the HTTP portals.
• In the RISS Information view, hold your mouse cursor over the system’s name under Appliance Name in the RISS Domain(s) area. A tooltip displays the information. To view information about a domain: • In the RISS Information view, click the name of the domain in the RISS Domain(s) area. Information about that domain appears in the Domain Name area. Viewing component information The lower portion of the RISS Information view shows a list of components in the RISS and each host name.
Table 21 Mining Overview view features Feature Description Exchange Server Information about Exchange server and its status. For servers with more than one domain, select a domain from the pull-down list. For each domain: • Server host name or IP address. • General status of Exchange server. A check icon ( ) indicates normal ) indicates a problem or inactive service. operation. An X icon ( • Name and size of mailbox. • Number of items. Mining Server Information about mining server and its status.
Links from Mining Overview view: none Stopping mining servers Click STOP NOW below server information. Based on number of servers, there is a latency period when stopping servers. NOTE: You can also stop the mining server from the Application Management view. Starting mining servers Click START NOW below server information. Based on number of servers, there is a latency period when starting servers. NOTE: You can also start the mining server from the Application Management view.
Table 23 Replication view features Feature Description Domain Information For each domain configured for replication: • Domain Name: DNS name of domain. • Service: Whether replication is in progress (Running) or not (Stopped). • Between: Names of local and replication systems. First system named is the domain location. Second system named is the remote system where domain is being replicated. • Current Transfer Rate: How many messages and documents are being duplicated per second.
The time before reprocessing schedule changes take effect depends on how your system is configured. By default, the system checks for reprocessing schedule changes every two hours. Contact your HP Support representative if you need this changed. The Reprocessing view displays each domain, whether reprocessing is enabled, and when reprocessing is scheduled, and a history log report. NOTE: Click the domain name to access the RISS Information view and display more information about the domain configuration.
Viewing reprocessing history logs The reprocessing history log shows a list of the last successful reprocessing run for each configured domain. The log includes each domain group, when a domain was reprocessed last, and the number of processed files. This report is based on data from cell groups, which is averaged from the individual smart cells of each group. To display the reprocessing history logs: • Scroll to the bottom of the Reprocessing view.
2. Complete the form to set the retention status and period. 3. Click Save Retention. 4. To ensure that retention is enabled, verify that the domain’s Retention Status check box is selected. If selected, the text Enabled appears next to the check box. Editing repository retention periods Note that when setting the retention period of a repository, if the domain’s retention period is greater than a specific repository’s retention period, the domain’s retention period is applied to that repository.
When you access the Smartcell Cloning view, PCC searches for ongoing cloning operations and loads current data. Only one smart cell can be cloned at a time, so you see the progress of any ongoing cloning operation. Table 25 Smartcell Cloning view features Feature Description Cloning Set up Smart cells whose mirrors are not viable and how many free cells are available. • Source: IP address of smart cell without viable mirror. If all smart cells have viable mirrors, displays “No Broken Groups Found.
System Backup NOTE: This view is available only if a backup system is configured. Access this view by clicking Data Management > System Backup in the left menu. This view provides information about the status of backup servers, and data backups, and direct access to a Tivoli Server Administration web client. Use the backup feature to back up all archived messages, documents, and digital signatures to write-once-read-many times (WORM) media, including optical media.
Table 28 Data Backup panel features, System Backup view Feature Description Library Name of library for data backups. A backup library is a collection of backup volumes. Server Name Server where data backup services run. Files backed up • Proportion of files backed up, expressed as a percentage and as a ratio of total number of files. • Graph of percentage of data files backed up over last 24 hours.
Table 30 Tactical Monitoring view features Feature Description Monitoring Performance Current performance of monitoring processes: • Check Execution Time: Minimum, maximum, and average times to execute a monitoring check • Check Latency: Minimum, maximum, and average durations between time a monitoring check was scheduled and time it was executed • # Active Checks: How many services are monitored • # Passive Checks: Currently not used (all checks are active) Network Health Average health of all hosts a
Displaying problem status of specific hosts Hosts with problem status values are divided into those with acknowledged problems and the rest (unhandled). In the Tactical Monitoring view, click one of the following links: • <#> Acknowledged • <#> Unhandled Problems The Service Status Details view appears. See "Service Detail" on page 57 for more information. See "Example: Acknowledging problems" on page 111 for information about acknowledging problems.
Table 33 Service Status Detail view, Service Status Details chart features Feature Description Host Target hosts. Color coding indicates host health. See "Host and service status values" on page 29. Icons indicate presence of comments ( scheduled downtimes ( ) and/or ). Service Services running on each target host. Color coding indicates service health. See "Host and service status values" on page 29. Status Current status values of services. See "Host and service status values" on page 29. .
Origin Link "Availability" on page 75, for single host View Status Detail For This Host "Creating availability reports" on page 77 View Status Detail For This Host "Alerts History" on page 84 View Status Detail . . . "Notifications" on page 78, for single host or when gray-box heading is Notifications View Status Detail . . . "Service Problems" on page 62 • View Host Status Detail . . .
Host Detail The Host Status Totals and Service Status Totals charts of this view are the same as those of the Status Summary view. See "Overview" on page 30. The Host Status Details chart provides status information about a specific host, all hosts in a host group, or all hosts in the system. Some chart column headings have associated vertical arrows. To sort the chart in ascending order by a given column, click the orange up arrow. To sort in descending order, click the green down arrow.
Service Overview Use this view to see the status of each host in a single host group or all host groups. For each host, this view shows number of services that have each service status value. The Host Status Totals and Service Status Totals charts are the same as those of the Status Summary view. See "Overview" on page 30. The Service Overview For chart provides information about status values of hosts and services in displayed host groups.
Table 41 Links from Service Overview view Destination Link "Service Detail" on page 57 View Service Status Detail . . . "Host Detail" on page 60 View Host Status Detail . . . "Overview" on page 30 View Status Summary . . . "Status Grid" on page 109 View Status Grid . . . Displaying host groups 1. Scroll to the bottom of the Service Overview view. 2. Find the host group's chart, and click the host group's name above the chart, such as Routers for Smart Cells (cr).
Table 42 Links to Service Problems view Origin Link left menu Service Problems "Overview" on page 30 All Problems, in Host Status Totals or Service Status Totals chart "Service Detail" on page 57 All Problems, in Host Status Totals or Service Status Totals chart "Service Overview" on page 61 All Problems, in Host Status Totals or Service Status Totals chart "Status Grid" on page 109 All Problems, in Host Status Totals or Service Status Totals chart "Host Detail" on page 60 All Problems, in Serv
Table 46 Links to Comments view Origin Link left menu Comments Table 47 Links from Comments view Destination Link "External Command Inte rface" on page 110 Add a new host/service comment Adding service or host comments 1. In the Service Comments or the Host Comments section, click the Add new service comment or Add new host comment link ( ). The External Command Interface appears. 2.
NOTE: The only effect of a scheduled downtime is to suppress sending notifications; in particular, services are not disabled during downtimes. Because services are not disabled during downtimes, scheduling a downtime for a host also schedules equivalent downtimes for all its services. When a host is down, its service checks fail, causing the host itself to be checked. A detected host failure leads to a single notification about host being down; no service notifications are produced.
NOTE: When Fixed is not selected, scheduled downtime is flexible: it starts between specified start and end times as soon as a problem is detected (UNREACHABLE or DOWN status value for host, non-OK for service). 4. Click Commit to save changes, or click Reset to clear input fields. A snore icon ( Details. ) appears next to host or service entry in various views, such as Service Status Re-enabling notifications by deleting scheduled downtimes 1. Find downtime. 2.
Some Program Information chart variables appear in the Process Commands box as commands to change current values. Process State Information chart Table 51 Process State Information chart, Nagios Info view Variable Description Process Status Status of monitoring process (Nagios). Should be OK. If not, use the Restart the Nagios process command. See "Process Commands box" on page 67. Process status values are the same as service status values. See "Host and service status values" on page 29.
2. In the Command Options section, click Commit. Table 54 Process commands, Nagios Info view Command link Description Shutdown the Nagios process Shuts down Nagios process. Note: After Nagios is shut down, it cannot be restarted via the web interface. Restart the Nagios process Restarts Nagios process. This is equivalent to sending the process a HUP signal. All information is flushed from memory, configuration files are reread, and Nagios starts monitoring with new configuration information.
Table 56 Links to Nagios Stats view Origin Link left menu Nagios Stats "Tactical Monitoring" on page 55 Monitoring Performance Table 57 Links from Nagios Stats view Destination Link "Service Detail" on page 57 Active Service Checks (# Total) Scheduling Queue Use this view to display and schedule service checks. This view provides information about when each service on each host is scheduled to be checked. The gray-box heading for this view is Service Check Scheduling Queue.
Disabling or enabling service checks Click the X icon ( ) or check-mark icon ( ) to disable or enable service checks, respectively. The External Command Interface view appears, where you confirm enabling or disabling. See "External Command Interface" on page 110. Rescheduling services Click the wristwatch icon ( ) to reschedule service. The External Command Interface view appears.
Related View • "System Status" on page 32 provides similar information to email reports. Table 62 Links to Email Reporter view Origin Link left menu Email Reporter Links from Email Reporter view: none Detailed email reports Detailed email reports provide system status and performance information in an HTML document. The detailed HTML format provides more content and the format is more sophisticated than the text summary report.
• Domain Configuration: For each domain: set size (number of groups that can be created), disabled/enabled state of compliance, backup, replication, and replica count (number of replicas to be created for each group). • Software Versions: Versions of RISS software currently installed, including: • Application: Third-party software package, also called L3. • Installer: RISS installation program.
2. Select NotificationGroups or Members as needed. 3. Click Submit Configuration. Editing reports 1. In the Report Types list, select report. Email report periods appear in the Notification Groups list. 2. Select email report period. Recipients appear in the Members list. 3. To edit the Members list, add email address and click Add, or select email address and click Delete. 4. Click Submit Configuration.
The same color coding is used in both charts: State History and State Breakdowns. See "Host and service status values" on page 29 for more information. The additional value Indeterminate used in these charts generally indicates time the entire system (site) was not operational. In addition to report features described previously, the report view has an input form at the upper right you can use to update the report. After changing report options, click Update to regenerate the report with new options.
Creating trends reports 1. Select a report type: Host or Service. 2. Select a specific host or service. 3. Select report options: • Report Period: Select a predefined period, or select * CUSTOM REPORT PERIOD * and specify custom report start and end dates. • Assume Initial States: Select Yes to assume any undetermined status value is really the First Assumed State. Selecting No is equivalent to selecting Yes, and selecting Unspecified as the First Assumed State.
Table 66 Availability view features, single host or service Feature Description heading • Name of host or service reported on. • Covered report period. Host/Service State Breakdowns Color-coded history chart indicating host/service status value trends over reported time period. This is a reduced version of the corresponding Trends view. Click the bar chart to display the full Trends view. See "Alerts folder" on page 81.
Table 68 Links to Availability view Origin Link left menu Availability "Alerts folder" on page 81 View Availability Report For This Host/Service "Creating availability reports" on page 77 View Availability Report For This Host/Service "Hostgroup Information" on page 98 View Availability Report For This Hostgroup "Host Information" on page 100 View Availability Report For This Host "Service Information" on page 104 View Availability Report For This Service Availability report for single host or
• Report Period: Select a predefined period, or select * CUSTOM REPORT PERIOD * and specify custom report start and end dates. • Assume Initial States: Select Yes to assume any undetermined status value is really the First Assumed State. Selecting No is equivalent to selecting Yes, and selecting Unspecified as the First Assumed State. • Assume State Retention: Select Yes to use last recorded status value before PCC startup as status value assumed for periods when monitoring was down.
Table 70 Notifications view features Feature Description Log File Navigation Day covered by current view. Click the left or right arrow to view notifications from the previous or next day. Host Origin of notification (corresponds to the Host field of notification email). Click link for details. See "Host Information" on page 100. Service Origin of notification (corresponds to the Service field of notification email). Service is N/A (not available) if host is down. Click link for details.
Table 71 Links to Notifications view Origin Link left menu Notification "Service Detail" on page 57 when main heading is Service Status Details For All Hosts View Notifications For All Hosts "Service Problems" on page 62 View Notifications For All Hosts "Alerts History" on page 84 • for all hosts and services • single host • single service View Notifications For: • All Hosts • This Host • This Service "Alerts folder" on page 81 View Notifications For This Host/Service "Availability" on page 75 f
Table 73 Event Log view features Feature Description update form(upper right) To update the Event Log view to change event list order, select the Older Entries First check box , and click Update. Log File Navigation Day covered by current view. Click the left or right arrow to view events from the previous or next day.
Figure 10 Alerts histogram of all service events over one-day period Whenever graph lines for events of different status values overlap exactly, only the most severe status value is indicated. To see an event line that is hidden by overlapping, create a separate histogram for just the hidden status value. For example, the following histogram shows only recovery (OK) events for the same time period.
Figure 11 Alerts histogram of recovery service events over one-day period Table 75 Alerts Histogram view features Feature Description heading • Name of host or service reported on. • Covered report period. Event History Color-coded graph indicating host/service event history over reported time period. See "Host and service status values" on page 29 for information about color coding of status values.
Table 76 Links to Alerts Histogram view Origin Link left menu Alerts Histogram "Alerts folder" on page 81 for specific host or service View Alert Histogram For This Host/Service "Availability" on page 75 for specific host or service View Alert Histogram For This Host/Service "Host Information" on page 100 for specific host View Alert Histogram For This Host "Service Information" on page 104 for specific service View Alert Histogram For This Service Table 77 Links from Alerts Histogram view Desti
Table 78 Alerts History view features Feature Description Log File Navigation Day covered by current view. Click the left or right arrow to view alerts from the previous or next day. alerts Information for each alert, including: • Color-coded status icon (green: normal, yellow: warning, red: failure, orange: unknown). • Time stamp. • Alert type: HOST or SERVICE. • Host identifier. • Service identifier (service alerts only). • Host or service status value.
Table 80 Links from Alerts History view Destination Link When view shows alerts for all hosts and services "Service Detail" on page 57 View Status Detail For All Hosts "Notifications" on page 78 View Notifications For All Hosts When view shows alerts for single host or service "Notifications" on page 78 filtered for host/service View Notifications For This Host/Service "Alerts folder" on page 81 filtered for host/service View Trends For This Host/Service When view shows alerts for single host "Ser
Table 82 Alerts Summary view features, most recent alerts Feature Description Time Time of alert. Alert Type Host or service alert. Host Name of host. Click the host name to display the Host Information view. See "Host Information" on page 100. Service Name of service. Click the service name to display the Service Information view. See "Service Information" on page 104. State Host/service status value. State Type If status condition is HARD or SOFT.
Table 85 Links to Alerts Summary view Origin Link left menu Alerts Summary Table 86 Links from Alerts Summary view Destination Link "Host Information" on page 100 host "Service Information" on page 104 service Creating standard alert summary reports 1. Select a report type under Standard Reports. Only alerts with HARD status conditions are reported. See "Hard and soft status conditions" on page 30. 2. Click Create Summary Report (under Standard Reports).
Table 88 Custom alert summary report types Custom report type Information reported Most Recent Alerts The 25 most recent alerts, with such details as alert time and alert message. Alert Totals Summary information about number of alerts for each host and service status value. Alert Totals By Hostgroup Same as Alert Totals, but totals for each host group. Alert Totals By Host Same as Alert Totals, but totals for each host. Alert Totals By Service Same as Alert Totals, but totals for each service.
You choose the object type to display using the Object Type pull-down list at the upper right. Table 91 View Config view features, hosts Feature Description Host Name Host's name. Example: sc-s2-204-4. Alias/Description Host's long name or description. Example: SmartCellMachines:sc-s2-2044.ourcompany.com. Address Host's IP address. Example: 10.0.204.4. Parent Hosts Host's parents. Example: cr-s0-96-4, cr-s0-96-3.
Table 93 View Config view features, services Feature Description Host Name of host on which service is running. Click link to display configuration information for host. See Table 91 on page 90. Description Description of service. Example: Spine Check. Max. Check Attempts Maximum number of times to check service before a service problem status condition is considered HARD. See "Hard and soft status conditions" on page 30. Normal Check Interval Time between ordinary checks of service.
Table 94 View Config view features, contacts Feature Description Contact Name Contact's name: admin is only contact PCC uses. Alias Contact's long name: Administrator. Email Address Contact's email address: abc@xyz.com. Defined for the system at configuration time. Note: This can be a comma-separated list of email addresses. In that case, what is defined as contact (a single contact, not a contact group - see Table 95 on page 92) represents more than one email destination.
Table 97 View Config view features, commands Feature Description Command Name Command's name. Example: check_ping. Command Line Command itself (its definition). Example: $USER1$/check_ping -H $HOSTADDRESS$ -w 200.0,20% -c 1000.0,60% -p 5.
Table 99 View Cell Space view features Feature Description • • • • Names of hosts in these host groups. SMTP Portals HTTP Portals MetaServer TSC-NAT domains Smart cells of each domain, organized by smart cell group. Information about each smart cell group: • Unique smart cell group identification number (RISS automatically generates ID). • Host names of smart cells in smart cell group, prefixed by P- (primary cell), S(secondary cell), or R- (replication cell). • Each smart cell's life cycle state.
Displaying domain-affiliated smart cells 1. In the View Cell Space view, find the smart cell's domain. 2. Find the smart cell's smart cell group identification number. 3. Click the smart cell's name. The Agent view appears. Displaying unaffiliated smart cells Unaffiliated smart cells are “free” and contain no data. To display unaffiliated smart cells: 1. Scroll to the bottom of the View Cell Space view. 2.
b. From the MBean list, click ProvisionerMBean. The MBean view appears. c. Verify the ProvisionerMasterBackupStatus attribute is set to Master Provisioner. If it is set to Backup Provisioner, return to the View Cell Space view, click the link to the other metaserver, and repeat the previous steps. 3. Determine which smart cells failed and can be restored: a. In the MBean view for the primary controller, click the button next to ListBrokenGroups. Groups that failed and have not been recovered are listed.
Table 103 Links from MBean view Destination Link "Agent view" on page 97 Back to Agent View Array view (you normally do not need to use this view) various Agent view This view shows managed objects (MBeans or JBoss components) currently running on a particular host machine. NOTE: Do not modify settings in this view. For monitoring purposes, you normally do not need to use this view. It is intended only for installers and advanced system administrators.
NOTE: For monitoring purposes, you normally do not need to use this view. It is intended only for troubleshooting and configuration by installers and advanced system administrators.
• "Tactical Monitoring" on page 55 also provides limited information about monitoring performance. Table 109 Links to Hostgroup Information view Origin Link "Overview" on page 30 host group abbreviation, in parentheses, such as (sc). "Service Overview" on page 61 host group abbreviation, in parentheses, such as (sc). "Status Grid" on page 109 host group abbreviation, in parentheses, such as (sc).
Command link Description Schedule downtime for all services in a specific hostgroup Schedules downtime for all services in a particular hostgroup. During scheduled downtimes, Nagios does not send notifications about services. When scheduled downtimes expire, Nagios sends notifications for services as normal. Scheduled downtimes are preserved across program shutdowns and restarts. Scheduling downtime for services does not automatically schedule downtime for the hosts those services are associated with.
Table 112 Host Information view features Feature Description heading Full and abbreviated names of host, and host IP address. For example: • SmartCellMachines:sc-s1-172-1.mycorp.com: Full host name • sc-s1-172-1: Abbreviated host name • 10.0.172.1: IP address • SmartCellMachines:1: First host in host group SmartCellMachines Host State Statistics Amount and percentage of time this host has had each host status value, and total time. See "Host and service status values" on page 29.
Table 113 Links to Host Information view Origin Link "Service Detail" on page 57 specific host name "Service Problems" on page 62 specific host name "Host Detail" on page 60 specific host name "Service Overview" on page 61 Actions icon View Extended Information For This Host ( "Scheduling Queue" on page 69 specific host name "Alerts Summary" on page 86 specific host name "Notifications" on page 78 specific host name "Status Grid" on page 109 specific host name "Service Information" on page 1
Command Link Description Acknowledge a specific host problem Note: This option appears only if the host status is not OK. Acknowledges host problems. Future notifications about problems are temporarily disabled until host changes state (for example, recovers). Contacts for host receive an acknowledgement notification, so they are aware someone is working on the problem. A comment is also added to host. Enter your name and a brief description of your actions in the comment field.
Command Link Description Enable checks of all services on a specific host Enables all service checks associated with specified host. This does not enable checks of host, unless you select the Enable for host too check box. Enter information in the Host Name field. Disable event handler for a specific host Temporarily prevents Nagios from running the host event handler for specific host. Enter information in the Host Name field.
Table 116 Service Information view features Feature Description heading Name of service. Full and abbreviated names of host and host IP address. See "Host Information" on page 100. Service State Statistics Amount and percentage of time service has had each service status value, and total time. See "Host and service status values" on page 29. Service Commands Links to commands that perform actions on service. See "Service Commands section" on page 106, for more information.
Table 117 Links to Service Information view Origin Link "Service Detail" on page 57 service name "Service Problems" on page 62 service name "Scheduling Queue" on page 69 service name "Alerts Summary" on page 86 service name "Notifications" on page 78 service name "Status Grid" on page 109 service name Table 118 Links from Service Information view Destination Link "Host Information" on page 100 View Information For This Host "Service Detail" on page 57 for host View Status Detail For This
Table 119 Service Commands section, Service Information view Command link Description Acknowledge a specific service problem Acknowledges service problem. This option appears only if service status is not OK. When service problem is acknowledged, future notifications about problems are temporarily disabled until service changes state (for example, recovers). Contacts for service receive acknowledgement notifications, so they are aware someone is working on the problem. A comment is also added to service.
Command link Description Re-schedule the next check of a specific service Reschedules next check of service. Nagios requeues service to be checked at specified time. If you select the Force check box, Nagios forces a service check regardless of what time scheduled check occurs and whether or not checks are enabled for service. The following fields are required: • Host Name • Service • Check Time Submit passive check result for this service Submits a passive check result for service.
Deleting all comments for specific services 1. In the Service Comments section, click the Delete all comments link ( Interface appears. ). The External Command 2. In the Command Options section, enter the following information: • Host Name • Service 3. Click Commit to save changes, or click Reset to clear input fields. Status Grid This view provides a high-level summary of hosts and services, organized by host group.
Table 122 Links from Status Grid view Destination Link "Host Detail" on page 60 View Host Status Detail . . . "Service Detail" on page 57 View Service Status Detail . . . "Service Overview" on page 61 View Service Overview . . . "Overview" on page 30 View Status Summary . . . Status Grid view, for all host groups View Status Grid For All Host Groups, when viewing Status Grid for single host group Displaying specific hostgroups Click the host group name, such as Smart Cells.
NOTE: Commands that disable (notifications, status checks, and so on) override commands that enable. For example, suppose you disable checks for a particular service, such as PING, using the Service Information view (Disable checks of this service command), but enable checks for all services using the Nagios Info view (Start executing service checks command). That particular service (PING) is not checked because disabling overrides enabling.
Table 123 Links to External Command Interface view Origin Link "Tactical Monitoring" on page 55 Enabled/Disabled "Comments" on page 63 Add a new host/service comment "Host Downtime" on page 64 Schedule host/service downtime "Nagios Info" on page 66 commands (Process Commands) "Scheduling Queue" on page 69 Actions for specific service "Hostgroup Information" on page 98 commands (Hostgroup Commands) "Host Information" on page 100 commands (Host Commands) "Service Information" on page 104 comm
3 Platform Account Manager (PAM) This chapter explains how to use Platform Account Manager (PAM) to provision and update user accounts.
3. Enter the following: • User Name: Your user name. (You must be a user with administrative privileges to use PAM.) • User Password: Your password. To change your password, use the Preferences in the RISS Web Interface. • PCC NAT Host: Name or IP address of the PCC NAT host. • PCC Admin Name: admin • PCC Admin Password: Password for accessing the Platform Control Center (PCC). 4. Click OK. The PAM window appears (see "PAM window" on page 114).
Table 125 Options menu • Show Users - Determines registered users displayed in the Users panel. Options are: • All Users - Shows all users of the system. • Active Users - Shows only users who are allowed to log in (active Outlook Integration Users and active Non-Outlook Integration Users). • Inactive Users - Shows only users who are not allowed to log in. • Outlook Integration Users - Shows only active and inactive users of the Outlook Integration query system.
Table 133 Panels Click a tab to view corresponding panel for object. All panels have the following parts: • List of (up to 50) objects filtered by Search, Domain, and A-to-Z selections. • Information about object selected in the list. • Apply button: Saves changes made to displayed information. • Reset button: Clears changes made and redisplays current database information.
3. Define the object. 4. Click Add. Viewing PAM objects 1. Click the object tab (for example, click Repositories). Figure 13 Repositories tab 2. Click the Search, A-to-Z, <, <<,>, and >> buttons to display target object in the list. 3. Select target object in the list. 4. To modify selected object, do one or more of the following, and click Apply. • Change values in editable parts of the panel.
2. Click the Search, A-to-Z, <, <<,>, and >> buttons to display target object in the list. 3. Select target object in the list. 4. To modify selected object, do one or more of the following, and click Apply. • Change values in editable parts of the panel. • If selected object is a collectionof other objects: To add or remove member objects in collection, click the Add
Figure 15 Delete objects Adding member objects to collection objects These procedures assume you selected the collection object in the list at the left of the PAM window. See "Viewing PAM objects" on page 117 for instructions. 1. Click Add . (The object type depends on the current panel.) The Select type dialog box appears.
Figure 16 Select User dialog box 2. Select the object to add to collection. Click the Search, All, A-to-Z, <, <<,>, and >> buttons to navigate the list. 3. Click Add. 4. Click Apply. Example: To add user to ACL: 1. Select the ACL in the ACLs panel. 2. Click Add User. 3. Select the user in the Select User dialog box. 4. Click Add in the Select User dialog box. 5. Click Apply in the ACLs panel.
4. Click Apply. Example: To remove user from ACL: 1. Select the ACL in list at the left of the ACLs panel. 2. Select the user in the User entries for this ACLbox. 3. Click Remove User in the ACLs panel, and click Yes to confirm. 4. Click Apply in the ACLs panel. Managing user accounts Use the Users panel to view or change individual user accounts on RISS. Select a set of users to view by selecting Options > Show Users. See Options menu in Table 124 on page 114.
Figure 17 Users panel Table 137 Users panel, PAM window Feature Description object list Users on this system determined by Options > Show Users, and indicated by current panel name. See "Filtering list of users" on page 122. Synchronize this Account If DAS is allowed to update selected user account. See "Viewing non-editable user information" on page 123. UserID Automatically generated identifier for selected user; unique to the system. (Not editable.) User Name (Required.
Regardless of selected set of users, you can create or delete user accounts, or change privileges and identifying information for a given user. Viewing non-editable user information Select Synchronize this Account if you want DAS to update the selected user account. If selected, the User Name, First Name, Last Name, User E-Mail, Mail It To Me E-mail, Mail Server Host IP, and User Status fields cannot be edited. They are synchronized with values on the LDAP server.
2. In the Comment dialog box, click Update. 3. Enter new comments in the Input dialog box, and click OK. The new comment replaces the previous comment. 4. Click OK. The Input dialog box closes. Managing repositories Use the Repositories panel to view, add, or change RISS repositories. You can change which ACLs apply to a given repository. You cannot delete a repository. Accessing Repositories panel Click the Repositories tab.
Figure 18 Repositories panel Table 138 Repositories panel, PAM window Feature Description object list Repositories on system. Repository ID Automatically generated identifier for selected repository. Number is unique to the system. (Not editable.) Name (Required.) Name of selected repository. Access ACL ID ACLs defined for selected repository. Domain Name Domain to which selected repository belongs. (Value is supplied when repository is created.
Filtering list of repositories The object list displays a list of repositories on this system. Only the first 50 items in the list are shown, and the list can be filtered by clicking the Search and A-to-Z buttons. (See "Filtering list of users" on page 122.) Figure 19 Filter repositories Viewing non-editable repository information Under the Access ACL ID feature, double-click an ACL entry to display the ACL dialog box, where you can view (but not modify) the ACL definition.
2. Click Add ACLs. 3. Click to display the Select ACL Entries dialog box, where you can select ACLs and add them to selected repository. 4. Click Apply in the Repositories panel. Removing ACLs from repositories 1. Select repository from the object list. 2. Click Remove ACLs. 3. Select Access ACL ID entry, and click Remove ACLs. 4. Click Apply. Managing ACLs Use the ACLs panel to create or delete an ACL, or change users in a given ACL. Accessing ACLs panel Click the ACLs tab.
Figure 20 ACLs panel Table 139 ACLs panel, PAM window Feature Description object list ACLs on the system. See "Filtering list of ACLs" on page 129. ACL ID Automatically generated identifier for selected ACL. Value is unique to the system. (Not editable.) Name (Required.) Name of selected ACL. See "Viewing non-editable ACL information" on page 129. Description Description of selected ACL. See "Viewing non-editable ACL information" on page 129.
Filtering list of ACLs The object list displays ACLs on this system. Only the first 50 items in the list are shown. To filter the list, click the Search and A-to-Z buttons. (See "Performing basic PAM tasks" on page 116.) Viewing non-editable ACL information The Name feature displays the non-editable name of selected ACLs. The value is supplied when ACL is created. See PCC for User Management DAS information. The Description feature displays the non-editable description of selected ACL.
Managing routing rules Use the Routing Rules panel of the PAM window to create, edit, or delete routing rules, or select the repository associated with a rule. NOTE: Use simple routing rules (see "Managing simple routing rules" on page 133) instead of the Routing Rules panel whenever possible. Extensive use of rules can negatively impact system performance. Accessing Routing Rules panel Click the Routing Rules tab.
Figure 21 Routing Rules panel Table 140 Routing Rules panel, PAM window Feature Description candidate objects List of all routing rules. See "Filtering list of routing rules" on page 131. Routing Rule ID Automatically generated identifier for selected routing rule. See "Viewing non-editable routing rule information" on page 132. Name (Required.) Name of selected routing rule. Domain Domain of selected routing rule. See "Viewing non-editable routing rule information" on page 132.
Viewing non-editable routing rule information Click Routing Rule ID to see automatically generated identifier for selected routing rule. The value is unique to the system, and is not editable. Click Domain to see domain of selected routing rule. The value is supplied when you create the rule and is not editable. Adding routing rules 1. Click New. The Add New Item dialog box appears. 2. Define rule name. 3. Select domain. 4. Select repositories for new routing rule. 5. Define the Routing Rule Info.
Deleting routing rules 1. Select a routing rule in the object list. 2. Click Delete, and click Yes to confirm. Adding repositories to routing rules Click ... to display the Select Repository dialog box, where you select the destination repository. Managing simple routing rules Use the Simple Routing Rules panel to create, edit, or delete simple routing rules, or select the repository associated with a rule.
Figure 22 Simple Routing Rules panel Table 141 Simple Routing Rules panel, PAM window Feature Description candidate objects List of all simple routing rules for selected domain. See "Filtering list of simple routing rules" on page 134. Mail Address (Required.) Mailing address of selected simple routing rule. See "Viewing non-editable simple routing rule information" on page 135. Repository ID (Required.) List of repositories simple routing rule applies to.
Viewing non-editable simple routing rule information Click Mail Address to see the mailing address of selected simple routing rule. This information is not editable here. Supply this value with the New button. The Mail Address is matched against both sender and recipient addresses. It corresponds to Routing Rule Info (TO= . . . OR FROM= . . .) for a routing rule. See "Managing routing filters" on page 135. Click Repository IDs to see a list of repositories to which this simple routing rule applies.
This means a routing filter has two possible uses, based on which domains appear in email addresses: • Filtering emails before simple routing rules try to match them: only rules with the correct email domains are tried. • Routing emails from a specific domain to a specific repository. (In this case, it is typically used to associate an audit repository with an email domain.) After filtering, each email is always checked against routing rules.
Figure 23 Routing Filters panel Table 143 Routing Filters panel, PAM window Feature Description candidate objects List of routing filters for selected domain. See "Filtering list of routing rules" on page 138. Email Domain (Required.) Email domain of selected routing filter (example: mycorp.com). Filter applies to all emails with this domain in the mail header. (Not editable. Value is supplied when filter is created.) Repository ID (Required.
Filtering list of routing rules Click candidate objects to see a list of routing filters for selected domain. Only the first 50 items in the list are shown. To filter the list, click the Search and A-to-Z buttons. (See "Performing basic PAM tasks" on page 116.) Adding routing filters 1. Click New. The Add New Item dialog box appears. 2. Define the Email Domain. 3. Select domain of application for new routing filter. 4. Click ... to select applicable repositories. 5. Click Add. Modifying routing filters 1.
3. Create users johndoe and janechoi for the new employees John and Jane. Use the Users panel to do this. See "Creating marketing department users" on page 139 for instructions. Creating these users will also automatically accomplish the following (provided the ACL & Simple Routing Rule option is enabled in the Create User Options dialog box-the default value): • Create individual repositories for John's email and Jane's email.
When enabled (the default), the ACL & Simple Routing Rule option automatically creates a repository, ACL, and simple routing rule for the new user. This gives the user access to his/her own repository, where all of his/her incoming and outgoing email is routed. 5. Click Apply in the Users panel (PAM window). Creating ACL for managers to access marketing email Use the ACLs panel to give Manager Mark and CEO Betty access to all email to and from members of the Marketing Department. 1. Click the ACLs tab. 2.
4 PST Importer This chapter contains these topics: • • • • PST Importer overview, page 141 Installing PST Importer, page 142 Using PST Importer, page 143 Archive Request file, page 141 PST Importer overview PST Importer allows system administrators to: • Load legacy (pre-RISS 1.0) PST files into RISS. • Scan PST files to ensure RISS finds and archives new messages. • Provide optional “tombstoning” of messages in PST files.
These parameters are supplied in an XML file format generated with Archive Request Loader. Otherwise, provide Archive Request Loader with an XML file created by another method. For a description of each tag and a sample XML file, see "Archive Request file specifications" on page 149.
Using PST Importer This section explains how to use the PST Importer tools and discusses these topics: • Archive Request Loader, page 143 • PST Import Monitor, page 146 Archive Request Loader Use Archive Request Loader to create or validate an Archive Request file. This tool also generates an output log file, detailing issues that occurred during the load process. Before adding a file to PST.
Figure 25 Creating a new file 3. Click Add, and select PST files. Only files in the Select Files To Process list are imported. In the file you are creating, corresponding XML tags are and . 4. To import PST files larger than 150 MB, edit the following setting in RISS PST Importer.ini to reduce performance degradation and increase throughput: [PSTLaunchMgr] MaxProcesses=1 5. If necessary, select PST files you do not want to process, and click Remove. 6.
• Use TNEF: If selected, stores submitted messages in TNEF format. XML tag is . • Distribute To All Recipients: If selected, PST Importer sends a copy of the document to all addresses specified in the message. If unselected, only the owner specified in the Repository box receives the document. XML tag is . If you do not select this setting, HP highly recommends using a repository that is not associated with an active email account.
Parameter Description /i Required. Name of input file to be processed. Replace ArchiveRequestFileName.xml with the full UNC path and XML file name. /o Required. Name of Archive Request Loader log file to which diagnostic and processing information is written. Replace LoadLogFileName.log with the full UNC path and log file name. /c Optional. Parses XML structure in input file for syntax and file accessibility only. No records are added to PST.MDB for processing. /v Optional.
Figure 26 PST Import Monitor 2. PST Import Monitor displays basic data about the PST process status. To view specific processing information, see the following: Item Information area: • Total: Total number of items found in the PST files so far. • Processed: Number and percentage of items processed and submitted to RISS. • Rejected: Number and percentage of items that PST Importer could not process due to errors. The PST Importer log file contains error information explaining why the item was rejected.
PST Import Monitor automatically collects statistics according to the Refresh Interval specified. The default is 10 seconds. You can change the automatic refresh interval to any whole number between 1 and 60 seconds. • To reset a failed process, select Failed under Active Processes to display a list of all failed processes, right-click the failed process, and click Reset, as shown in the following figure.
PST Importer log file Each mining process is assigned a unique PST file and creates a PST Importer log file containing warnings, errors, and completion statistics about the process. The log file is delivered to the repository specified by in the Archive Request file. The log file is sent as an email attachment. Upon successful submittal, the file is deleted. If a mining process terminates and is retried, a separate log file is generated.
Table 144 Tags in Tag Description Version number associated with this Archive Request format. Current version is 1.0. Exchange server used when accessing the GAL for address resolution. Mailbox on Exchange server used when accessing the GAL for address resolution. DNS name or IP address of the RISS SMTP portal used to submit messages to RISS. Port number used with . This setting is optional. The default is 25.
Table 145 Tags in Tag Description Path and file name of imported file. Wildcards are allowed and are expanded prior to processing. UNC paths are supported and highly recommended. Type of import processing to be performed on the . PST is the only processing type supported in current release.
E:\PSTFiles\Persist Search Results.pst PST E:\PSTFiles\ComplianceSearch_001.pst PST E:\PSTFiles\Outlook.
5 Audit Log The Audit Log feature provides a surveillance system log for companies that are required to prove they are adhering to surveillance processes. This chapter describes how to enable the Audit Log feature, grant user access to the repository, monitor status, and set retention periods. For information on performing Audit Log repository queries, see the Audit Log section in the HP StorageWorks Reference Information Storage System User Guide.
Figure 28 Audit Log enabled Setting Audit Log repository retention periods The Audit Log repository behaves like a regulated repository. (See "Editing repository retention periods" on page 52.) The same rules for changing retention settings apply for the Audit Log repositories. The Audit Log repositories are listed under the Other Type tab on the PCC Data Management view Retention page.
6 AMT Account Management Tool (AMT) is a batch tool used to load Exchange users into RISS when the Exchange server is not using LDAP. If the Exchange server is using LDAP, use Dynamic Account Synchronization (DAS) instead. Loading user accounts into the system is a three step process: 1. Export a .csv file containing the Exchange user accounts you are loading into RISS. See Exporting user account information from Exchange. 2. Use AMT to create an XML account file from the exported .csv file.
1. Navigate to the amt/bin directory and double-click amt.bat. The Login dialog box appears. 2. Enter the following: • User Name: Admin • User Password: Admin password • PCC NAT Host: IP address or DNS Name to RISS • PCC Admin Name: admin • PCC Admin Password: Platform Control Center (PCC) Admin password 3. Click OK to log on. 4. In the Account Data Source area of the AMT window, select the From File option. NOTE: Do not select the From Exchange Server option.
7 Backup system administration The optional RISS backup system is the final line of defense in the integrated RISS data-protection strategy. The RISS backup system uses Tivoli Storage Manager (TSM) to create backups of RISS data. This chapter is intended for administrators who use the RISS backup system. It describes the processes involved in accessing the RISS backup server, configuring TSM, and managing smart cells, and contains detailed procedures for maintaining and labeling backup files and media.
The secondary smart cell usually performs this backup. However, the primary cell in the group performs the backup if the secondary cell is unavailable. The smart cell itself initiates the backup. Because this is automatic and does not involve Tivoli’s internal scheduler, the TSM configuration does not include a schedule for smart cell backups. Separate Group Volumes An option for Separate Group Volumes is available in the Backup section of the RISS Master Configuration File.
Figure 30 Policy domain structure How RISS configures TSM The RISS backup server is initially configured with the script /usr/local/tsmBackup/configTiv init from the PCC machine. This script uses the TSM administrative command line interface to connect to TSM, and sends TSM commands that create the TSM objects and configurations that are necessary for backing up RISS data.
connecting element for the server, library, and device. (See the Tivoli Administration Guide on Defining Devices and Paths at http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/ index.jsp?topic=/com.ibm.itsmcw.doc/anrwgd53176.htm.) d. A new device class is defined. The device class name is the same as the library to which it will be connected, except that the string “DC” is added as a prefix (for example, DC.TAPE). (See the Tivoli Administration Guide on Defining Device classes at http://publib.boulder.
Figure 31 Library properties 5. 6. 7. 8. Click the Volumes link to see a list of volumes that are assigned to that library. In the Select Action list, select Add Volumes and click Go. Select None of the volumes are labeled, and then click Next. Select Search for all eligible volumes in the library’s regular slots, and then click Next. Depending on whether or not your library has a barcode reader, select the appropriate option. (See the figure below.
Figure 33 Server process list How to add and label new media (command line) The wizard mentioned in the previous section gathers information to build the necessary Tivoli command. The command can be issued on the command line manually (for example, if the Web interface is not available). The following command (which includes no line break) is equivalent to the procedure that was described previously: LABEL libvol LIB.OPTICAL search=yes labelsource=vollist vollist=OPTICAL.8,OPTICAL.
• http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/index.jsp?topic=/com.ibm.itsmcw.doc/ anrwgd53264.htm • http://publib.boulder.ibm.com/infocenter/tivihelp/topic/com.ibm.itsmcw.doc/anrwrf53237.htm How to restore a smart cell To restore data on a failed smart cell, you need at least one free smart cell. If only one smart cell in a group failed, then clone a smart cell instead. See "Smartcell Cloning" on page 52 for more information about cloning.
Figure 34 Provisioner status 3. Determine which smart cells failed and can be restored: a. In the MBean view for the primary controller, click the button next to ListBrokenGroups. Groups that failed and have not been recovered are listed. Figure 35 List of broken groups b. Copy GroupIDs and Roles of broken groups.
c. Click Back to MBean view. 4. Restore the smart cell: After you determine which smart cell you want to restore, begin the other Provisioner operation, RestoreSmartCellUsingGroupIDAndRole. A smart cell from the Free Pool (the group of unassigned and empty smart cells) is assigned as a restore target. The smart cell begins restoring its data. If the data indexes were not backed up, then the smart cell will rebuild them before coming back online.
b. A copy of the Device Configuration File: This file contains information that is required to read backup data, such as library, path, device, and device class definitions. c. A copy of the Server Options File: This file contains general settings for the server. For more details about these components, please consult the TSM Administrator’s Guide, particularly pages 707 to 709 and pages 721 to 729. TSM Disaster Recovery Manager The Disaster Recovery Manager (DRM) is a function of the TSM Extended Edition.
Example 1. tsm: INTERNAL>query drmstatus tsm: INTERNAL>query drmstatus Recovery Plan Prefix: C:\PROGRAM FILES\TIVOLI\TSM;\SERVER1\RECPLANS\ Plan Instructions Prefix: C:\PROGRAM FILES\TIVOLI\TSM\;\SERVER1\RECINSTR\RPP Replacement Volume Postfix: @ Primary Storage Pools: SP.GROUP.PRI.
b. Back up the device configuration: tsm: INTERNAL>backup devconfig filenames=c:\tsmbackup\devconfig c. Back up the server options file: Copy file C:\Program Files\Tivoli\TSM\server1\dsmserv.opt to c:\tsmbackup. d. Copy these three files to a safe location. 7. Create a list of offsite media to retrieve: a. tsm: INTERNAL>query drmedia * wherestate=vaultretrieve In this example the list will be empty.
i. j. Open a command prompt, change to the directory c:\tsmbackup, and run: RECPLAN.RECOVERY.SCRIPT.DISASTER.RECOVERY.MODE.CMD This restores the database from the tape and starts the server in a new window. It also registers the licenses and marks as “destroyed” the volumes that remain in the server. Run the command: INTERNAL>audit library LIB.OPTICAL command to ensure that the TSM database is consistent with the library volumes. Check in and label two empty volumes.
Backup system administration
8 Configuring Outlook or Lotus Notes This chapter contains information about these topics: • Configuring your system for Exchange and Outlook, page 171 • Configuring your system for Domino and Lotus Notes, page 202 Configuring your system for Exchange and Outlook This section contains information about these topics: • • • • • • • • • • • Configuring user accounts on customer servers, page 171 Installing the Outlook plug-in, page 172 Configuring journal mining, page 176 Configuring mailbox mining, page 177
Table 146 User accounts on customer servers For User type and mailbox location Default last name, user logon (password), alias* Group membership or permissions Mailbox mining Domain user and mailbox on Exchange servers Appuser, appuser (skyline); alias=appuser Administrators, Exchange Domain Servers Journal mining Active Directory user and mailbox on Exchange servers LocalJournalUser, LocalJournalUser (skyline); alias=LocalJournalUser User Dynamic Account Synchronization Active Directory user o
this to False causes the Offline Cache Manager to cache all messages, whether or not attachment(s) exist. This is a user-configurable setting. • EncryptCache=True: Encrypts files in the offline cache location using Microsoft’s Encrypting File System (EFS). The default is True. Depending on the computer’s security settings, only the current user can read files stored in the offline cache. Depending on the Folder options on the user’s computer, files may appear as green in Windows Explorer.
an administrator/diagnostic setting and should be modified only at the direction of support personnel. • ShowSysTrayIcon=True: Indicates to the Offline Cache Manager whether the status icon should be displayed in the system tray. By default, the system tray icon is displayed. This is an administrator/diagnostic setting and should be modified only at the direction of support personnel.
Manually creating other registry settings To repackage the installation for deployment with Software Management Server (SMS) or other client management tool, components must be registered. In the following settings, @ indicates the default for the key specified. Some settings only create the key, and specific values are not created. In addition to registering components, a file association must be created to properly launch the message exporting feature, also known as the Message Export Facility.
8. Click OK. 9. In Outlook, click Search Archive. A browser window with the logon page for the Web Interface appears. If it does not, the DNS names specified previously in the Archive Options panel are incorrect. NOTE: For more information about the Archive Options panel of the Options dialog box, see the “System administrator tasks” section in the RISS Outlook Interface chapter of the HP StorageWorks Reference Information Storage System User Guide.
i. Repeat step b through step h for each Storage Group on the server. 5. Repeat this procedure on other Exchange servers as needed to set up other mailbox stores for journaling. Configuring mailbox mining Mailbox mining, also known as selective archiving, uses rules to archive email from a Microsoft Exchange server to RISS. The system is first queried to determine if the email in a user's mailbox is already archived. If it is, a stub is created in the Exchange server.
9. In the Display name and Form name boxes, enter PERSISTMailItem, and click Publish. 10. After publishing the form, close the form editor without saving the form, and close Outlook. Setting up Information Stores The RISS Scheduler processes events that use data provided by Mail Attender For Exchange. When these Scheduler events are defined, companion rules are inserted in the Mail Attender database. Before Mail Attender can use these rules, information stores must be specified for them.
Figure 37 Settings view button Make sure the “Hide this information store from all selection lists” is checked. The other two boxes should remain unchecked. Click OK when finished. This journal mailbox is now hidden and no processing rules can be applied to it. Figure 38 Mailbox Properties Repeat this process for the SMTP and System Attendant information stores. Set up Auto-Search In the left pane, select the Information Stores root folder.
Figure 39 New Auto-Search The “Edit Automated Search” window will appear. Make sure Search for Mailboxes is selected. Then, click on the Mailboxes tab.
Figure 40 Edit automated search Select the Exchange server whose mailboxes are of interest. Select the mailbox used to query the exchange server. Click OK to complete the setup process and add the search. Every 24 hours the selected server will be searched for mailboxes and the Mailboxes information store will be updated with the results. Automated searches should be added for all servers containing mailboxes of interest.
Figure 41 Scheduling an event To select an event type, click on the down arrow to see what types are supported. Select an event type and click OK. Figure 42 Types of events A window will appear indicating that a companion rule for this event has been created in the Mail Attender for Exchange database. This rule must be edited using the Mail Attender for Exchange console interface in order to add the information stores that should be included in processing the scheduled event.
Enabling a scheduled event The “Schedule Events Maintenance” window appears. After a new event has been created, it must be edited to enable it and set other parameters. Click Edit to bring up the Edit window. The edit window that appears is specific to the selected event type. Each edit window will be examined.
Figure 44 Selective Archiving Event window • Enabled check box: Here is where this event is either enabled or disabled. The default value is disabled. • SMTP Address: Select the SMTP Address check box and enter the RISS Virtual IP (VIP) used for SMTP. The VIP is the internal RISS domain that stores documents and is the same value as the ipToDomainInfo attribute used in Domain.jcml. • Recipient Address: Select the Recipient Address check box and enter @. Replace
After the desired changes have been made, select the Apply button followed by the Close button to finalize the changes. The Advanced button allows changes to be made which override default settings in the RISS.ini initialization file. CAUTION: Any changes made this way should only be done under the supervision of a Hewlett-Packard representative.
• • • • • • • • email. The domain name must correspond exactly to the name specified in Domain.jcml for this system. Note – More than one recipient may be specified by separating the addresses with commas. RISS Domain Name: Select the RISS Domain check box and enter the name of the internal RISS domain to which the email from this journal mailbox should be stored. The Domain Name must match exactly the domain name attribute specified in the Domain.jcml.
Figure 46 Tombstone Maintenance Event window • Enabled check box: Here is where this event is either enabled or disabled. The default value is disabled. • Override: Select the Override check box to be able to change the Enable OWA Support default value from No to Yes. After the desired changes have been made, click the Apply button followed by the Close button to finalize the changes. The Advanced button allows changes to be made which override default settings in the RISS.ini initialization file.
• Override: Select the Override check box to be able to change the Delete Non-Tombstone Items From Exchange Retention default value from No to Yes. After the desired changes have been made, select Apply followed by the Close to finalize the changes. The Advanced button allows changes to be made which override default settings in the RISS.ini initialization file. CAUTION: Any changes made this way should only be done under the supervision of a Hewlett-Packard representative.
Figure 49 Deleting a scheduled event A window will appear asking for a conformation of the delete request. Click Yes to complete the delete process. Click No to abort the delete. If Yes is clicked, a window appears indicating that a companion rule for this event exists in the Mail Attender for Exchange database and asks if it should also be deleted. Click Yes to delete it from the Mail Attender database, or No to leave it in the Mail Attender database.
Figure 50 Rules This brings up the window use for editing rules. The first tab is used for changing the description and category.
Figure 51 Edit Local Rule window The description entered here must match the name of the event setup in the RISS Scheduler. Otherwise, the RISS Launch Manager will fail to complete processing when this rule is executed. The next tab is used to add the information stores. A rule must have at least one information store associated with it. Click Add to add an information store. The “Add Information Stores” window appears.
Figure 52 Add Information Stores window Another tab on the Edit Local Rule window is the Conditions tab. When selected, the edit conditions window opens. Initially the template contains one condition. The rule looks for messages with a Class of IPM.note. CAUTION: Do not remove or change conditions without direct instruction from Hewlett-Packard support personnel. To add a condition to the existing list, click Add. A window containing a list of all the possible conditions appears.
Figure 53 Possible conditions An edit condition window will appear so the specific age condition can be set. ClickOK to complete the addition of the new condition. Two conditions are now required for the rule to be processed. Click OK again to complete the editing of the rule. All editing of the rules are done as shown in the previous example.
Figure 54 Monitoring View window The first area shows the status of the Launch Manager Service. This service launches the enabled events defined in the Scheduler. From this area, you can start or stop the service. You can also set the refresh interval. The Launch Manager Service must be “running” for any event to be scheduled. The second area provides a series of radio buttons that allow the displayed data to be filtered by different categories.
Deleting end-user deleted items on the RISS Mail items may be deleted by the end-user from the Exchange mail store and from the RISS in a coordinated fashion. Exchange 2000 and 2003 support a retention interval on end-user deleted items. If the interval were allowed to lapse, the deleted items would be permanently removed (hard deleted) from the Exchange mail store. To coordinate the deleted items, the delete rule is executed within the Exchange retention interval.
Figure 55 Mailbox store 1. Right click on the Mailbox Store and select properties to bring up a dialog box. 2. Click the Limits tab and assign the values to the Deletion Settings.
Figure 56 Deletion settings Once applied, any subsequent deletions performed on mailboxes contained in the given mailbox store are retained for the number of days specified. Scheduling deletion from RISS To schedule the delete functionality, enable a scheduled event using Scheduler, and establish a corresponding rule using Mail Attender. CAUTION: Contact your HP representative for assistance in deletion configuration. Additionally, note that two Domain.
Creating a Mail Attender rule To create a Mail Attender rule: 1. Under the Folders tab: a. Set the folders to be “All Folders” or another selection. b. Set the following checkboxes: • Include the default “Recover Deleted Items” folder. (Dumpster) • Include all other “Recover Deleted Items” folders. 2. Under the Conditions tab, set the test message keywords. They are OR conditions. Decide what items are eligible to be deleted.
Table 149 CSV Columns Column Number Column Heading Column Value 1 Server Name [MAILBOX_SERVER_NAME] 2 Distinguished Name [MAILBOX_DN] 3 Store IED MAILSTORE_EID] 4 Folder EID [FOLDER_EID] 5 Message EID [MESSAGE_EID] 6 Is In Dumpster [MESSAGE_IN_DUMPSTER] Also at the bottom of the dialog set the following items in the list boxes.
• WinHTTP 5.1 installed or updated. This is provided only with Windows Server 2003, Windows XP SP1, and Windows 2000 Professional SP3. All others must update the server. WinHTTP 5.1 is available for update from MSDN. See MSDN Article KB842773, “Update for Background Intelligent Transfer Service (BITS) 2.0 and WinHTTP 5.1 Windows 2000.” See MSDN Article KB842773, “Update for Background Intelligent Transfer Service (BITS) 2.0 and WinHTTP 5.1 Windows 2003.” • Proxycfg.exe supported by WinHTTP 5.1.
Table 151 Mail Attender rule to delete temporary items in drafts folder General RissDeleteDrafts Information Stores Folders \Drafts Include subfolders Conditions Test Message Keywords Keywords= [MESSAGE_MAPICUSTPROP("PTOWASTATUS",C6448195FCA8CB4BB3E31303AA83C02C)] Test=”Equals” Value=”PTOWATEMP” Actions Report Delete Message Deletion Type=”Hard Delete” Other action settings: Click the “Modify” buttons and set the following checkboxes.
ASP pages Use the ASP section to change the appearance of RISS archived items, and to set the UseProperty Template flag. For OWA RISS, a mail item that is RISS archived will optionally display the RISS icon. The administrator may disable the appearance of the icon by changing the Icon configuration setting. The UsePropertyTemplate flag should be set TRUE for Exchange 2000.
After you enable LDAP for the Domino server, clients and LDAP-enabled applications can query the Domino server and get information about entries in the Domino Directory. 2. Configure journaling. You must configure all Domino servers that interact with the RISS system for journaling by the Domino administrator. See the Lotus Notes documentation for more information. 3. Configure Lotus DIRCAT. Your Lotus Notes environment might include Lotus DIRCAT.
Installing and configuring the Lotus Notes plug-in The HP installer works with the system administrator to update \lotus\notes\Notes.ini on the Notes Client to reference the Notes plug-in by adding the following lines at the end of the file: EXTMGR_ADDINS=nhpclient.dll RISS_DOMAIN_NAME=RISS domain name (for example, csf.store) RISS_HOST_ADDRESS=IP address of the RISS system where domain name and host name define the RISS system used to archive the emails.
A Email Miner version P2.0 for Lotus Notes installation guide This appendix contains the following information. • Overview, page 205 • Architecture, page 205 • Frequently asked questions, page 206 • System requirements and prerequisites, page 208 • Email Miner, page 208 • Installation, page 208 • Error messages, page 211 Overview Email Miner is a Lotus Notes mail administration product that mines documents from mail databases and/or journal databases and places the documents within the RISS architecture.
Frequently asked questions Architecture Table 152 Architecture Question Answer What version of Domino must my servers by running? Email Miner requires that your servers are running 6.x. What files are placed on my Domino server? Email Miner is self-contained within two Lotus Notes databases. There are no other files to be placed on the servers. How does Email Miner work? Email Miner uses a scheduled LotusScript agent to perform all of the processing.
Migration Table 154 Migration Question Answer What must I do when I migrate my servers' operating systems? Nothing. There is only one code-stream for Email Miner. Installation Table 155 Installation Question Answer How do I install Email Miner? An installation database is provided that will perform all of the installation steps. Do I need to physically visit every server? No. All server installations can be performed from your Lotus Notes client.
System requirements and prerequisites System requirements • 256 MB RAM per server • 200 MB free disk space per server • Each server must be running Lotus Notes 6.x Prerequisites • Email Miner agent signer must have 'Run Restricted LotusScript Agents' rights and 'Administrator' rights • Set 'Max LotusScript execution time' to at least 120 minutes.
Figure 57 Initial installation 2. Specify the values • Use Servers to specify the servers where Email Miner is to be installed. NOTE: This field will be automatically populated with the name of the server where the Installation database resides. • Use Managers to specify the entries that are to be placed into the ACL as 'Manager' within the Email Miner databases. NOTE: This field will be automatically populated with the name of the person performing the installation and 'LocalDomainServers'.
Figure 58 Additional Servers installation 2. Specify the values • Use Servers to specify the servers where Email Miner is to be installed. • Use Options to specify the installation options. Select Automatically create replicas if you want to create the Email Miner replicas during the installation. If you do NOT select this option, the Email Miner replicas will not be automatically created and must then be deployed manually.
NOTE: The Email Miner agents that were created during the installation process are not updated during the upgrade process, which will preserve the agent signers. For a Email Miner 'Upgrade', perform the following steps: 1. Select Actions | 1. Email Miner | 3. Upgrade Figure 59 Upgrade 2. Upgrade • Click Upgrade to begin the upgrade. The upgrade process will display the tasks being performed. The results from this process are saved within the installation database.
Table 158 Installation error messages Error number Error message Cause Action ERR0001 Could not find Server Definition for 'xxx' The Server Definition for the specified server ('xxx') cannot be found within Email Miner. Contact HP technical support. ERR0002 You must place the installation database on a domino server The installation database does not currently reside on a server (KitType = 2). Move the installation database to a Domino server.
B Email Miner version P2.
Mail server configuration There are two components for every mail server. • Server Definition The Server Definition defines the characteristics of each mail server. A Server Definition will automatically be created for each mail server during the Email Miner Installation. Each mail server must be included on a Server Definition and if one does not exist, Email Miner will email the administrators of the problem.
Figure 61 Processing options • Use RISS email address to specify the email address for the RISS. • Use Maximum queue size to specify the maximum number of messages that can be queued before no more messages are sent to the RISS. • Use Options to specify the processing options to be used when Email Miner encounters an error while processing. Select Journal to specify that the Domino journal database is to be processed. Use File paths to specify the file path for the inherent journal databases.
Figure 63 Logging options • Use Retention to specify how many days the log documents are to be retained. • Use Type to specify the type of logging that Email Miner should generate Select Summary if you want Email Miner to only report basic information and errors. This will log the start and end times of the Email Miner agent, what processes are schedule to run and with what mail user Email Miner started and ended. Select Verbose if you want Email Miner to log information per mail user processed.
If Email Miner did not finish its execution due to any reason, Email Miner will begin with the mail user listed the next time it starts, it will begin with the mail user listed, and proceed forward until the last mail user is processed. Specify mail user processing options If you want to alter the Email Miner processing, perform the following steps: 1. Select the Server Status Select the Server Status document that you want to affect. 2. Click the button Click found at the top of the view. 3.
Figure 67 Import users • Use Type to specify how Email Miner should locate the mail users. Select By mail server to import the users using the home server names. Select By specifics to import the users using specific group/user names. Use Options to specify the import options. Select Include mail-in databases to import mail-in database documents. Select Include resource databases to import resource database documents.
Figure 68 Synchronize with Address Book • Use Server to the server that is to process the synchronization. There should never be more than one synchronization document per server, because only one will be processed. Multiple synchronization documents are necessary when needing to synchronize multiple domains or to partially synchronize a domain. • Use Domain to specify the name of the domain being synchronized. Email Miner will use this value to qualify the address book documents.
Use Restrictions to specify the mail users to be restricted. 2. Enable the Synchronization Agent You must enable the Email Miner Synchronization agent. If the agent is not enabled, the synchronization process will not occur. Make sure that you specify the server on which the Email Miner Synchronization agent is to run. You may choose any server on which this agent is to run, but it is recommended that you specify the server where the administrators make address book changes.
Figure 70 Creating a mail restriction • Use Status to specify the status of the Mail Restriction. Select Enabled to activate the Mail Restriction. This will allow the Mail Restriction to be processed by the Email Miner agent. Select Disabled to deactivate the Mail Restriction. • Use Title to specify a title for the Mail Restriction. This value does not affect processing. • Use Priority to specify the priority of the Mail Restriction.
• Use Retention method to specify how to determine the age of the documents. Use Secondary retention method to specify the secondary method to be sued in the event that the primary retention field does not exist. • Use Retention type to specify the document retention type. Select # of Days to specify a dynamic age. Use Retention amount to specify the age of the documents. Select Date range to specify a date range (start/end dates). • Use Folders to specify the folders/views to be processed. 2.
Figure 75 Exclude folders • • • • • • Select Select Select Select Select Select Include calendar entries to include calendar entries. Include foldered to include documents that exist in personal folders. Include protect from archive to include documents that are protected from archiving. Include stationery to include stationery documents. Include tasks to include todos. Include non-completed tasks to include tasks that have not been marked as completed.
Email Miner Tombstone agent The Email Miner Tombstone agent creates a tombstone within the documents that have been selectively archived from the mail databases. This tombstone will designate that the document has been successfully sent to the RISS. Error messages Email Miner can generate numerous error messages. Each error message is categorized as either 'expected' or 'unexpected'. An 'expected' error is caused by a configuration problem within Email Miner, the mail databases, or address Book.
Log messages Email Miner could generate various messages that are placed within the log documents. Each log document that contains one of these errors will be marked with an exclamation point. The following table lists the log messages. Table 160 Email Miner log messages Log message number Log message Cause Action ERR0001 Could not find Server Definition for 'xxx' The Server Definition for the specified server ('xxx') cannot be found within Email Miner. Contact HP technical support.
Log message number Log message Cause Action ERR0022 Only have 'xxx' access to mail database for 'yyy' The agent signer does not have sufficient access (where xxx is the access) to the mail database (where yyy is the user name). Alter the ACL of the mail database. ERR0023 Could not find mail database for 'xxx' (yyy) The mail database for a user (where xxx is the user name and yyy is the file path) could not be located. Ensure that the mail database has not been moved/deleted.
Index Symbols PCC views, 23 A Account Manager window, PAM, 114, 116 accounts, user, 113 acknowledging problems host, 103, 111 service, 107, 111 ACLs adding, 129 adding to repositories, 126 filtering list of, 129 removing from repositories, 127 removing users, 129 user profiles, 129 users, adding or removing, 129 viewing information, 126, 129 active smart cell group, definition, 55 address book, Email Miner, 218 Agent view, 97 agents, Email Miner, 223 Alert Histogram view, 81 Alert History view, 84 Alert S
E editing reports, 73 email example of adding a new department, 138 Microsoft Exchange, 171 routing filters, 135 text summary reports, 72 user information, modifying, 123 Email Miner about, 205 address book, synchronizing, 218 administration guide, 213 agents, 223 archiving, 220 description, 21 Document options, 221 error messages, 211, 224 frequently asked questions, 206 importing users, 217 installing, 208 mail server configuration, 214 processing options, 217 restrictions, 220 security, 213 Server Defin
HP StorageWorks Reference Information Storage System definition, 21 HTTP Portals, View Cell Space view, 94 HTTP servers, starting, stopping, or restarting, 35 I importing users, Email Miner, 217 installing Email Miner, 208 Lotus Notes plug-in, 204 Outlook plug-in, 172 PAM, 113 PST Importer, 142 mailbox mining, 177 MBean components Agent view, 97 MBean view, 96 MBean view, 96 MetaServer, View Cell Space view, 94 Microsoft Exchange journal mining, 176 mailbox mining, 177 non-sticky ports, 182 publishing fo
P PAM about, 113 Account Manager window, 114, 116 ACLs panel, 127 adding ACLs, 129 adding ACLs to repositories, 126 adding repositories, 126 adding routing filters, 138 adding routing rules, 132 adding simple routing rules, 135 adding users, 123 Catchall Repository, 136 collection objects, adding members to, 119 comments, user, 123 creating objects, 116 definition, 113 deleting objects, 118 deleting routing filters, 138 deleting routing rules, 133 description, 21 email information, modifying, 123 example o
User Management view, 37 View Cell Space view, 93 View Config view, 89 views, 24, 25 PENDING status value, definition, 29 polling of hosts and services, 28 primary smart cells, 95 printing PCC views, 25, 25 problems view, 62 Process Commands box, 67 Process State Information chart, Nagios Info view, 67 Program Information chart, Nagios Info view, 66 PST Import Monitor, 146 PST Importer about, 141 Archive Request File, 141 Archive Request file, 149 Archive Request Loader, 143 description, 21 features, 141 Fi
scheduling downtime host groups, 99 hosts, 103 rescheduling services, 70 services, 107 viewing, 64 Scheduling Queue view, 69 secondary smart cells, 95 security, Email Miner, 213 selective archiving, 46 Server Definition, Email Miner, 214 servers DAS, configuring, 37 Domino, configuring, 202 Email Miner, 214 Exchange, 46 mailbox mining, 177 mining, 46 starting, stopping, or restarting, 35 service checks host groups, 100 hosts, 103 services, 107 Service Commands section, 106 Service Detail view, 57 Service In
View Config view, 89 view, PCC, definition, 23 W WARNING service status value, definition, 30 web sites HP documentation, 19 HP storage, 19 HP Subscriber's choice, 19 WORM media, backup to, 54 Reference Information Storage System 233
