User manual HP MEDICAL ARCHIVE SOLUTION

[. . . ] HP Medical Archive Solution user guide Part number: AG583-96008 Fourth edition: October 2007 Legal and notice information © Copyright 2005, 2007 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. This document contains proprietary information, which is protected by copyright. [. . . ] If CMS database capacity has been expanded since the grid was first installed, the expansion CMSs track a different set of content than the original CMSs. To get an exact count of the total number of object managed by the grid, add the number of objects managed by an original CMS to the number of objects managed by a CMS added in each expansion. For more information on CMS database operation, see page 124. Table 56 Attribute Stored Objects CMS Content Component Attributes Type/Units Count Description Number of objects stored in the database of this CMS. (Includes objects that have been purge from the grid via ILM. ) Number of permanent objects stored and managed by the database of this CMS. (See paragraph above this table for more information. ) Name for the business rules package currently in use. Version number of the business rules package. Number of newly ingested objects with non-ILM processing to be completed. Number of new or existing objects waiting to be processed through the business rules for replication. Chart Text Alarm N/A Managed Objects Count N/A Information Lifecycle Management ILM Implementation Text ILM Version Objects with Post-Processing Pending Objects with ILM Evaluation Pending Text Count N/A N/A DCiN Count N/A 126 Services and Components Table 56 Attribute CMS Content Component Attributes (continued) Type/Units Count Description The number of objects whose ILM business rules cannot be met because the topology or operational state of the grid prevents the rules from being satisfied. For example, when the network connection to a remote site is down copies cannot be made at that site. Number of objects due to be re-evaluated at a scheduled point in the future. When ILM rules dictate that action is to be taken when data reaches a defined age (such as "save one copy to tape"), all objects pass through this queue. Objects in this queue have their ILM evaluation satisfied. Chart Text Alarm ORun Objects with Unachievable ILM Evaluations Objects Marked for ILM Re-evaluation Count N/A Next Deferred Object Reevaluation Time Date and Time When objects whose ILM evaluation is deferred will be evaluated again. Gives administrators an indication of when additional load will be placed on the CMS due to reevaluation. Total number of ILM evaluations that have been performed to date. The value is incremented whenever the ILM is evaluated for an object: for example, when an object is ingested into the grid, when that object's replication is complete, or if an LDR is lost and the grid must assess each object from that LDR to decide which must be replicated to restore the grid. The number of objects whose ILM rules are evaluated per second. Provides an indication of how busy the CMS is. The average time it takes to perform the ILM evaluation for a given object. Allows an administrator to track the amount of work per object over time as ILM rules or grid topology are changed. N/A ILM Evaluations Count N/A ILM Evaluation Rate Objects / second1 N/A Average ILM Evaluation Time Seconds N/A Object Replication Active Replications Count Objects in the process of being replicated. [. . . ] Structured Query Language--an industry standard interface language for managing relational databases. An SQL database is one that supports the SQL interface. Service Status Monitor--a unit of the HP Medical Archive software that monitors hardware conditions and reports to the NMS. Every server in the grid runs an instance of the SSM. [. . . ]