IBM-Tivoli-Monitor-解决方案
TSM解决方案
第1章总论1.1 项目建设背景根据XXXXXXXX工程的建设要求，采用备份软件对系统关键应用数据进行集中数据备份。
准备建设和已经建设的数据系统是采用SAN架构技术进行构建的，这些系统担负着众多的极其重要的工作；系统中的数据，更是核心中的核心，数据的安全关系到整个系统能否正常的运行。
所以对数据系统的数据做好数据保护是至关重要的，是保证保障系统的最后一道防线，当各种影响数据安全的情况发生时，能以最短的时间恢复受损的数据。
对数据的保护，有多种方法，包括备份和数据容灾。
目前用得最多、最有效的手段是数据备份。
而备份的方法也很多，有手工备份、自动备份、LAN备份、LAN-Free备份等。
不同的备份方法，其效果不同，主要表现在性能、自动化程度、对现有系统应用的影响程度、管理、可扩展性等方面。
在考虑一个完整的数据备份/恢复解决方案的时候，需要参考以下三点：软件功能强大；架构模块化；应用简单化。
IBM的旗帜产品Tivoli Storage Manager正好符合了上述的三个参考值，而且TSM软件本身就是按照这三个数据保护解决方案的用户参考指数来设计的。
TSM软件拥有最强大、最全面的功能，通过模块化设计的最大的灵活性、最好的使用、配置的最简易性，我们为用户提供的是最低的总体拥有成本。
所以在这里，采用IBM公司先进的TSM软件来实现统一集中并且自动化的备份，亦可以实现异地的容灾备份管理。
1.2备份系统知识1.2．1 为什么要备份由于该系统是关键系统，需要不间断为运行。
即使发生短暂的业务中断，也会导致难以估量的经济和名誉损失。
为此，我们分析以下可能会导致业务系统中断的原因：1．系统硬件故障如数据/系统磁盘的损坏将导致数据不能访问，并进而可能导致应用进程终止或系统停机，甚至系统不能重启动；网卡的损坏可使终端用户无法访问系统服务；CPU或内存的失效则会导致系统的死机；2．应用程序或操作系统出错由于操作系统或应用程序中可能存在不完善的地方，当碰到某种激发事件时，应用程序非正常终止或系统崩溃（只能通过改善程序或系统来解决）；3．人为错误一些人工的误操作，如删除系统或应用文件，终止系统或应用服务进程，也会导致系统服务的无法访问；4．电脑病毒/黑客入侵由于目前的大多数计算机系统均连接在网络上，若缺少有效的防范机制，很容易遭受病毒的感染或黑客的入侵，轻者数据被损坏，重者系统瘫痪（只能通过加强管理杜绝）；5．自然灾害由于一些意外的不可抗拒的因素，如雷击、火灾、洪灾等导致的计算机系统破坏，将会使一般系统的恢复非常困难和耗时，导致业务系统长时间的中断（通过容灾系统来解决）。
IBMMaximo资产管理解决方案建议书_VDPFinal
IBMMaximo资产管理解决⽅案建议书_VDPFinalIBM Maximo资产管理解决⽅案建议书IBM Maximo 资产管理解决⽅案建议书⽬录第1章IBM中国公司简介 (1)第2章为什么需要企业资产管理 (2)2.1 企业资产管理的重要性 (2)2.2 IBM M AXIMO 资产管理解决⽅案简介 (3)第3章IBM MAXIMO 资产管理解决⽅案说明 (4)3.1 全⾯的资产管理 (4)3.2 ⼯作管理 (5)3.3 服务管理 (5)3.4 合同管理 (5)3.5 物资管理 (6)3.6 采购管理 (6)3.7 其它扩展功能 (7)第4章为什么选择IBM 资产管理 (9)第1章IBM中国公司简介IBM，即国际商业机器公司，1911年创⽴于美国，是全球最⼤的信息技术和业务解决⽅案公司，业务遍及170多个国家和地区。
2007年，IBM 公司的全球营业收⼊达到988亿美元。
IBM 与中国的业务关系源远流长。
早在1934年，IBM 公司就为北京协和医院安装了第⼀台商⽤处理机。
随着中国改⾰开放的不断深⼊，IBM 在华业务⽇益扩⼤。
80年代中后期，IBM 先后在北京、上海设⽴了办事处。
到⽬前为⽌，IBM 在中国的办事机构进⼀步扩展⾄26个城市，从⽽进⼀步扩⼤了在华业务覆盖⾯。
伴随着IBM 在中国的发展，IBM中国员⼯队伍不断壮⼤，⽬前已达到14000⼈。
除此之外，IBM 还成⽴了10 家合资和独资公司，分别负责制造、软件开发、服务和租赁的业务。
IBM ⾮常注重对技术研发的投⼊。
1995年，IBM 在中国成⽴了中国研究中⼼，是IBM 全球⼋⼤研究中⼼之⼀，现有200多位中国的计算机专家。
随后在1999年⼜率先在中国成⽴了软件开发中⼼，现有3000多位中国软件⼯程师专攻整合中间件，数据库，Linux 等领域的产品开发。
⼆⼗多年来，IBM 的各类信息系统已成为中国⾦融、电信、冶⾦、⽯化、交通、商品流通、政府和教育等许多重要业务领域中最可靠的信息技术⼿段。
TIM&TAM产品介绍
1.方案中的主要产品介绍1.1.IBM Tivoli Identity Manager1.1.1.IBM Tivoli Identity Manager概述IBM Tivoli Identity Manager提供了一个安全、自动而且基于策略的用户管理解决方案，满足客户无论是在原有的IT环境还是电子商务时代的IT环境下将企业的核心业务展现给客户、供应商、合作伙伴甚至竞争对手的需求。
在现有的业务流程中引入基于Web的管理和自助式服务接口的动机，反应了客户对简化及基于安全策略的自动化用户管理的需求。
Tivoli Identity Manager包含一个工作流引擎，同时利用用户身份信息提供如审计、报告等功能。
IBM Tivoli Identity Manager既可以直接与用户交互，也可以与两种类型的外部系统－身份数据源和访问控制机制直接交互。
身份系统管理需要在各个系统中建立帐号的用户身份的权威数据。
发布系统与访问控制系统直接交互，从而建立用户帐号，提供用户信息以及密码，定义用户的授权信息。
与之相反的是，在访问控制系统中进行的改动能够被发布系统所捕获并报告，然后按照安全策略对这些改动进行评估。
1.1.2.IBM Tivoli Identity Manager产品架构IBM Tivoli Identity Manager的逻辑结构根据功能的不同设计为三层，如下图所示，各个组件分别为：●Web用户界面层●应用层●服务层●LDAP目录●数据库●资源连结器图3-1 逻辑组件结构1.1.2.1.Web用户界面层Web用户界面模块是一组结合在一起的子程序，包括提供用户浏览器的内容和启动applet（同时在客户端和服务器端运行），如工作流设计和表单创建。
Web用户界面是用户浏览器和身份管理应用层的连接层。
在上面的图中，用户交互点有三种类型：终端用户，监督员和管理员。
这些类型仅仅是概念上的，因为IBM Tivoli Identity Manager允许您随意的定义各种权限的不同用户类型。
企业级存储管理解决方案-IBMDL1.doc
企业级存储管理解决方案-IBM DL1 IBM Tivoli Storage Manager 企业级存储管理解决方案武汉佰钧成技术有限责任公司2012年12月目录1 前言(4)2 需求分析(5)2.1 客户环境介绍(5)2.2 客户需求描述(5)2.3 方案设计考虑(6)3 IBM TSM存储解决方案概述(8)3.1 方案简介和产品选型(8)3.1.1 文件级别的备份(8)3.1.2 数据库级别的备份(8)3.1.3 应用级别的备份(9)3.1.4 操作系统级别的备份(9)3.1.5 基于硬件镜像的应用/数据库备份(9)3.2 TSM解决方案架构及功能(10)3.2.1 硬件配置(10)3.2.2 物理拓扑图(11)3.2.3软件配置及部署拓扑图(11)3.3 方案特点(14)4 北京中联云达信息系统服务有限公司数据备份与恢复策略建议(15)4.1 备份与恢复方式及数据流(15)4.2 文件系统备份与恢复策略建议(15)4.2.1 备份策略（永久增量备份）(15)4.2.2 恢复策略（一次恢复）(17)4.2.3 备份/恢复策略举例(17)4.3 数据库备份及恢复策略建议(18)4.3.1 数据库系统数据备份策略(18)4.3.2 Oracle数据库的备份与恢复(19)4.3.3 DB2数据库的数据备份及恢复策略(20)4.3.4 SQL Server数据库的备份(21)4.4 邮件系统的备份与恢复建议(22)4.4.1 Domino邮件系统备份与恢复(22)4.4.2 Exchange 邮件系统的备份与恢复(22) 4.5 SAP系统的数据备份及恢复策略(23) 4.6 操作系统的备份与恢复建议(24)4.6.1 本地TSM服务器系统的恢复(25) 4.6.2 当本地整个计算机系统的恢复(25) 4.7 灾难恢复流程建议(26)4.7.1 TSM备份系统的离线介质管理(26) 4.7.2 TSM备份系统故障保护与恢复(27) 4.7.3 基于TSM的数据容灾方案(28)4.7.4 基于TSM的数据恢复流程(31)5 方案优势总结(32)5.1 全面的解决方案(32)5.2 高性能的数据备份和恢复(32)5.3 集中的监控管理(33)5.4 强大的灾难恢复(35)5.5 数据的安全性(36)5.6 其它优势(36)5.6.1 IBM公司的战略性产品(36)5.6.2 广泛的市场选择和领先的技术优势(37)5.6.3 宽广的平台支持能力(37)5.6.4 磁盘高速缓存的优势(37)5.6.5 更高的数据可靠性(37)5.6.6 介质回收(38)5.6.7 内置关系数据库(38)5.6.8 集中管理(38)5.6.9 永久增量备份(38)5.6.10 瞬时存档/ 快速恢复(39)5.6.11 SAN能力/磁带池(39)5.6.12 支持TCP IP v6, SSL和长文件名(39)5.6.13 高效，自动的报告功能(39)1前言在企业对信息的依赖性越来越强的今天，信息已成为企业的生命源泉。
IBM Tivoli Enterprise Storage Monitoring 2 用户指南说明书
IBM Software Group IBM Tivoli Solutions IBM Tivoli Enterprise Storage Monitoring2 IBM Tivoli Enterprise Storage MonitoringContents2 IBM Tivoli Enterprise storage monitoring4 Common issues in Enterprise Tivoli Storage Management5 Monitoring without a common workspace5 An approach to monitoring without getting lost6 Backup6 Configuration and performance7 Monitoring availability of space7 Co nclusio n IBM Tivoli Enterprise storage monitoring Historically, storage administration monitoring for enterprise organizations has been mainframe-based. Early monitoring was primarily done using manual techniques and was driven by resource constraints — wanting to know how full the disks were, to try to guess when more storage would be needed, or when performance would start to be impacted, so that disk availability and performance were the primary focus of storage management. Storage administrators used storage pooling and data management tools to move data, gain availability and improve performance. Over time, technology improvements — such as increased cache, parallel access volumes (PAVs) and lower cost of storage — reduced those constraints and the amount of manual intervention required to tune the storage environment. As a result, monitoring requirements have evolved. Monitoring today is still centered around performance and availability, but also includes trending and forecasting as well as intelligent analysis. Distributed storage entered the picture with a finite resource referred to as locally attached disk. Storage Area Network, (SAN) configurations with their Fibre Channel fabric topology have now proliferated to extend the local disk concept and share a storage frame with hundreds of distributed systems. SAN configuration, provisioning and security were the initial focus of storage administration in distributed platforms. Monitoring tools were incorporated into the configuration tools, to improve visibility into utilization. While hard constraints were not the driving factor in distributed storage monitoring, exponential growth drove improvements in monitoring in areas of improving efficiencies and identifying data lifecycle requirements. Monitoring today’s distributed environments focuses on performance and life-cycle management of data. The differing paradigms, problemIBM Software Group 3focuses, and personnel involved in both mainframe and distributed platform storage administration have led toseparate tools and “silos” of information that make it difficult to consolidate monitoring and management of storage across the enterprise.For additional information, refer to one of the Tivoli Monitoring manuals at/infocenter/tivihelp/v3r1/index.jsp?toc=/com.ibm.omegamon.stor.doc/toc.xmlThe IBM zSeries® storage monitoring begins withOMEGAMON XE for Storage on z/OS. It provides forvisibility into performance, availability and early indicators of problems for direct access storage disk (DASD), tape, system catalogs, hierarchical storage management (HSM), removable media (RMM) and more. For more detailed or specialized information, additional agents may be added to the Tivoli Monitoring framework, including IBM Tivoli Advanced Catalog Management, IBM Tivoli Advanced Audit for DFSMShsm, IBM Tivoli Advanced Reporting forDFSMShsm and IBM Tivoli Advanced Backup and Recovery for z/OS disaster recovery and compliance management.Distributed systems are defined as all hardware that is not IBM System z. Distributed storage monitoring includes IBM T otalStorage Productivity Center, IBM Tivoli Storage Manager and includes newer technologies.While these systems are highly flexible, it is also important to understand that with flexibility comes an element ofcomplexity. It is important to establish environment standards early in the design and deployment of the Tivoli Monitoringinfrastructure to allow for effective control and management.T oday, many storage administrators remain focused on a single platform, either distributed or mainframe, but that isinexorably changing. Business pressures and consolidations are challenging more storage administrators to be responsible for monitoring multiple platforms and their unique challenges and toolsets. The IBM Tivoli® Monitoring infrastructure has allowed for the integration of monitoring tools for the different platforms. While the objectives of storage administration between mainframe and distributed are aligning, the base toolsets are quite different. The Tivoli Monitoring infrastructure enables the smooth integration of various monitoring tools for the different platforms. The open flexibility of the Tivoli Monitoring framework allows storage administration of these platforms through a single portal.4 IBM Tivoli Enterprise Storage MonitoringCommon issues in IBM Enterprise Storage ManagementA Tivoli Monitoring agent for each system is installed and registered with a Tivoli Enterprise Monitoring Server. The Tivoli Enterprise Portal navigator view is presented by platform and, when expanded, by system. An environment may have three or four different platforms: System z, Linux, UNIX and Microsoft Windows. Under each platform, there may be numerous systems, including IBM z/OS Parallel Sysplexes® and LPARS, Linux systems, various UNIX systems and perhaps hundreds of Windows systems.Storage administrators might need to monitor backups for disaster recovery purposes across multiple platforms. If an application runs on System z and on a distributed platform, both sets of backups will need to be monitored for successful completion. Perhaps the backup on z/OS uses automatic backup, archive and recovery software (ABARS) and ismonitored using IBM Tivoli Advanced Backup and Recovery Manager. Perhaps the backup on the distributed platform uses Tivoli Storage Manager. The backups must occur within a certain timeframe in order to be considered viable for recovery in the event of a disaster.Storage administrators are often held responsible for the performance related to the I/O of applications. There might be performance problems with hardware that is configured in IBM DS8000® using T otal Storage Productivity Center for use on System z. These problems are not easily identified. Monitoring with OMEGAMON XE for Storage on z/OS with knowledge of the hardware configuration may provide insights into performance problems relating to configuration.Storage administrators are typically responsible for theAvailability of space. As application development moves from System z to distributed, there may be instances where data must be sent by ftp between platforms. Storage monitoring to ensure that space is available before it is needed is a key to avoiding space problems before they occur.These examples are not meant to be inclusive of all storagemonitoring needs.Storage management monitoring across platformsUsing the standard Tivoli Enterprise Portal interfaces, cross-platform storage monitoring might require a typical storage administrator to drill down to multiple workspaces and views. Even with the capability of multiple windows, remembering the valid data between workspaces can be a challenge and a manual effort.IBM Software Group 5Monitoring without a common workspace A user can drill down to the distributed platform, find the agent with the data they are interested in monitoring, find the system where the data should be and either screen print it or leave it on the screen. Then, the user can create another window and repeat for the z/OS platform, find the agent containing the requested data and then drill down to the LPAR where the data is displayed and compare the data between the two screens.There’s got to be a better way ….An approach to monitoring and manag-ing enterprise storage without getting lost Using the storage monitoring previously mentioned, along with the OMEGAMON Dashboard Edition (DE) features incorporated into Tivoli Monitoring views and their underlying queries from the Tivoli Monitoring agents into a single common workspace. Adding IBM Tivoli OMEGAMON DE on z/OS to your IBM Tivoli Monitoring infrastructure entitles the use of many features that enhance monitoring from multiple OMEGAMON agents. Tivoli OMEGAMON DE provides a portal through which you can take advantage of an expansive view into your environment. Using Tivoli OMEGAMON DE on z/OS, you can collect metrics from operating systems, middleware, databases, storage, web applications servers and network sources — for integrated performance and availability views in a single screen. OMEGAMON DE provides more sophisticated monitoring with policies. Policies are automated responses to conditions including schedules and interrogation of situation results. Policies can be used to intelligently monitor across platforms, systems and agents. It is designed to help you make decisions more quickly, efficiently and proactively on an enterprise level. Instead of locating data within the physical topology where each system must be located, expanded and the data captured, a Logical View can be defined to combine data from all of the agents where monitoring across platforms and system components are wanted Navigation is simpler and in one place. There is a small drop in performance when running queries from multiple platforms to be displayed on a single workspace, but the choice of navigating to five different screens would probably exceed the delay of the queries. Situations can be written to track the values of specific attributes. Where monitoring values across the various platforms is needed situation correlation can be used. Situation Correlation is when the situation evaluates not just the value of attributes but the condition of other situation conditions that match or not match the conditions coded in them.Using the three scenarios described in the introduction, we explain what views might be combined to solve the sample usage cases.6 IBM Tivoli Enterprise Storage MonitoringBackupFor the application backup scenario that must occur on separate systems, a customized logical view can be created using a query from IBM Tivoli Advanced Backup and Recovery for z/OS that contains backup information from an application that runs on an LPAR. In the same workspace, another view can be created using a query from IBM Tivoli Storage Manager that contains backup information from a system that runs on Linux. Situations or policies can be defined to provide 24-hour monitoring and alerts for both platforms. The resulting workspace is a like single pane of glass instead of multiple screens requiring drill-down to multiple workspaces. The backup from z/OS can be monitored using the workspace “A History of ABM and CBTI Events” from IBM Tivoli Advanced Backup and Recovery manager. The addition of filtering can isolate the backups of interest for a particular application, while the backup using Tivoli Storage Manager on the distributed side can be monitored using the workspace “Schedule” from Tivoli Storage Manager. The exact same query can be used or customized in the new logical workspace.Policies or situations can be defined for each platform to determine if the backup was successful and within the appropriate window and correlated upon the successful monitoring of the other platform.The entire Advanced Backup and Recovery Agent navigator tree can be added to the logical workspace allowing drill-down capability to any additional data as needed. The IBM Tivoli Storage Manager Agent navigator tree item can also be added to the logical workspace. When defined correctly, the situation events defined at the physical view also appearsin the Logical View.Configuration and performanceStorage in an IBM DS8000 may be configured for System z only or also contain storage configured for distributed systems as well. Performance can be affected either by configuration or workload.Selected views from T otalStorage Productivity Center and IBM Tivoli OMEGAMON XE for Storage Views on Application Monitoring or Cache CU Performance and Cache CU Status can be used to see the impact of theconfiguration on the I/O performance on System z.IBM Software Group 7The workspace Volume Data as well as HBA Data fromT otalStorage Productivity Center along with OMEGAMON XE for Storage Application Summary and System-Managed Storage (SMS) Storage Group performance data may aid in the identification of a configuration -related performance problem. With user -specific thresholds and situations defined to raise an event when critical application performance is affected, the user can access a single view of all components involved in the configuration of the storage. The view is not a guarantee that the problem is configuration-related, but the information is a key to identifying solutions. Monitoring availability of spaceIn this scenario, SMS Storage Group Space workspace is viewed for available space along with the distributed platform system monitoring agent. Thresholds provide the visual alert, while situations provide the notification in advance of a potential problem. Using OMEGAMON XE for Storage on z/OS views of SMS Storage Group Space to monitor a Storage Group, volume or a list of volumes in the User DASD Group Space navigator workspaces, monitoring of availability of space can alert the user to shortages before they can have an impact on an application. On the distributed platform, the appropriate agent view is selected for disk storage monitoring. Disk space on a Windows system can be monitored using the Logical Disk Usage view to determine if sufficient space is available for the FTP to complete successfully. Situations can be defined to monitor both platforms at an interval well in advance of critical application runs, allowing enough time to correct a potential space availability issue before it affects critical application processing.ConclusionFor today’s storage administrator who is responsible for monitoring both zSeries and distributed storage, adding IBM Tivoli OMEGAMON DE on z/OS adds to the use of the IBM Tivoli Monitoring infrastructure to customize monitoring across platforms.By having the views on a single logical view, all affected systems can be monitored relative to other platforms, monitoring agents and systems. Multiple views might be desirable depending upon the configuration and platforms involved.Benefits include:• Enhanced visibility across the enterprise of all systems affecting a business application• Improved communications across platform support teams • Simplified problem determination, avoiding costly outages • T aking full advantage of technology resulting in better resource utilization and reduced manpower costs• Improved service and availabilityStay tuned for a more in-depth explanation of how these workspaces are created using the features of IBM Tivoli OMEGAMON DE on z/OS in the IBM Tivoli Monitoring Portal.AuthorVickie Dault, IBM T echnical Storage SpecialistPlease Recycle© Copyright IBM Corporation 2011IBM Global Services Route 100Somers, NY 10589 U.S.A.Produced in the United States of America August 2011All Rights ReservedIBM, the IBM logo, , DS8000, OMEGAMON, Tivoli, zEnterprise, z/OS and zSeries are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at “Copyright and trademarkinformation” at /legal/copytrade.shtml Other company, product and service names may be trademarks or service marks of others.Other company, product and service names may be trademarks or service marks of others.TIW14102-USEN-00。
IBM-TSM-ppt
致道科技
TSM的功能
备份(Backup)——恢复(Restore) 归档(Archive)——调档(Retrieve) 迁移(Migrate)——迁回(Recall)
致道科技
真正的企业级存储管理
ITSM 不仅只是一个备份工具…
Tivoli Storage Manager
LOG
DB
存储/恢复
致道科技
TSM对应用的在线备份管理支持
Tivoli Storage Manager 产品家族
Lotus Domino/Notes Microsoft SQL Server Microsoft Exchange Server Oracle Informix DB2/UDB SAP R/3 Sybase Websphere 数据库
• •
定义灾难保护策略 自动创建灾难恢复计划
– – –
备份卷标列表 配置信息 通过脚本程序进行服务器自动恢复
•
记录/管理在线和非在线的备份介质
Tivoli Storage Manager Sysback+ Tivoli Disaster Recovery Manager=完整的灾难恢复
致道科技
TSM的特性
®
SAP R/3 on AIX TDP for rk
Backup Path
Tivoli Storage Manager Server TSM Server
LAN connections Centralized TSM
Direct attached Storage Devices
Solaris NUMA-Q TANDEM PTX GUARDIA N (ETI)***
ITSM工具介绍
目錄1. 前言 (2)2.ITSM工具淺評 (4)2.1 重量級產品 (4)1. IBM -- Tivoli (4)2. HP—OpenView (5)3.BMC--Remedy (7)4. CA—Unicenter (10)5.福瑞杰- FrontRange (12)2.2 國內產品 (15)6.摩卡—Mocha BSM (15)7.游龙- SiteView ITSM (18)8. 广州忆科--EaseHelp ITSM (20)9.深圳非凡E8.HelpDesk (21)2.3國外其它產品 (23)10．Epicor-Epicor ITSM (23)11. Octopus- Octopus-itsm (24)12. Mansystems—ExpertDesk (24)13. versasrs—versasrs helpdesk (26)14. SysAid—SysAid helpdesk (27)15. ManageEngine ServiceDesk Plus (28)2.4 開源產品 (29)16. OTRS --OTRS Service Desk (29)1. 前言ITIL要实现“软着陆”，ITSM工具必不可少。
我們來看看現在有哪些專門的工具，打著與ITIL相關的軟體能搜到的大大小小有100多個吧，我們也沒有辦法一個個去了解，這里只找一些主流的和能說上名的來做下了解。
ITSM工具大型有Remedy, ServiceDesk, Tivoli, OpenView，國外的比較出名的還有FrontRange,MRO等，還有國內一些比較有名的廠商如摩卡，游龍，廣州憶科等，開源的目前只找到有OTRS。
清單如下：公司產品性質類型國家BMC Remedy 商業大型國外CA ServicePlus Service商業大型國外DeskIBM Tivoli 商業大型國外HP OpenView Service Desk 商業大型國外福瑞杰FrontRange 商業中型/大型國外商業中型/小型國內摩卡摩卡业务服务管理（Mocha BSM）游龙SiteView ITSM 商業中型/小型國內广州忆科EaseHelp ITSM 商業中型/小型國內深圳非凡E8.HelpDesk 商業中型/小型國內Epicor Epicor ITSM 商業中型/小型國外Octopus Octopus-itsm 商業中型/小型國外Mansystems ExpertDesk 商業中型/小型國外中型/小型國外versasrs versaSRS HelpDesk 社區版/商業版中型/小型國外SysAid SysAid HelpDesk 免費版/商業版中型/小型國外ManageEngine ServiceDesk Plus 免費版/商業版OTRS OTRS Service Desk 開源中型/小型國外2.ITSM工具淺評ITSM工具是比較複雜的，而且基本沒法下載到相關產品，我沒法做評測，這里只收集了各大產品的一些信息供了解。
IBM TSM数据存储与备份管理解决方案
IBM TSM数据存储与备份管理解决方案一、概述现在，如何有效地防范系统突发事件，在尽可能低的运作成本和拥有成本的前提下，提高数据的可靠性和可用性，已成为企业信息化工作急需解决的内容和关键性问题。
TSM(Tivoli Storage Manager) 软件是IBM 存储管理经验的结晶。
TSM 是为解决企业级数据及系统安全而设计的备份全面解决方案，为石油、金融、电信等许多大型企业，解决困扰信息技术部门的备份管理问题。
它在节省成本的前提下向您提供有保证的、自动、简单而且灵活的服务。
Tivoli TSM 的管理架构，真正适合企业管理级管理需求，为企业提供高效、自动、可扩展的备份管理体系。
北京××信息技术有限公司（石油地球物理勘探局信息中心）是国内最早应用TSM 的企业之一，并同时把TSM 应用在数据备份和数据管理领域。
在此方面，我们有着非常丰富的使用经验，并且是国内最早在TSM 基础上进行技术开发的企业。
现在，使用TSM 企业备份解决方案可以解决各种数据备份、归档问题；使用瑞飞公司在TSM 基础上开发的Data Management System （DMS ）可以解决石油、数字媒体、金融、电信等各种数据管理系统的海量数据存储管理问题。
TSM 应用案例在机房内，我们将在一台机器(IBM RS/6000 服务器) 上安装Tivoli TSM Server 作为备份服务器，专门伺职备份。
存储设备（磁带库）接在该备份服务器上，在需备份的客户端(UNIX 、WIN/NT 等) 安装TSM Client 端软件。
以下为示意简图：图中AIX 、SUN 、Win/NT 等机器代表了现有的应用系统和一般桌面用户，在上面安装TSM Client 端，它们通过TCP/IP 协议与TSM Server 连接。
TSM Server 可以是专用的服务器，或者是借用业务不繁忙的服务器，可以是IBM AIX 、SUN ，也可以是运行NT 的PC 服务器。
IBM Tivoli Monitoring V6.3.0 快速入门指南说明书
IBM Tivoli MonitoringVersion 6.3.0Quick Start GuideThis guide is intended to get you started with a base configuration for IBM Tivoli Monitoring.National Language Version:To obtain the Quick Start Guide in other languages,print the language-specific PDF from the IBM Tivoli Monitoring V6.3.0Quick Start CD .Product overviewIBM ®Tivoli ®Monitoring monitors and manages system and network applications on a variety of operating systems,tracks the availability and performance of your enterprise system,and provides reports to track trends and troubleshoot problems.The following figure illustrates the architecture of the IBM Tivoli Monitoring softwareenvironment:including installation instructions,see the publications in the following information centers:v IBM Tivoli Monitoring Information Centerv Jazz for Service Management Information CenterThe base architecture of the IBM Tivoli Monitoring software consists of the Tivoli Enterprise Portal Client,and the three server components(Tivoli Data Warehouse,the Tivoli Enterprise Portal Server,and the Tivoli Enterprise MonitoringServer).The architecture also consists of a group of monitoring agents that includes the OS agents such as AIX,Linux, UNIX,and Windows and warehousing agents that collect,summarize,and prune historical data.You can extend the base architecture to integrate with an event server such as IBM Tivoli Netcool/OMNIbus or TivoliEnterprise Console and Jazz for Service Management components and their IBM Tivoli Monitoring extensions.Jazz for Service Management brings together the Open Services for Lifecycle Collaboration(OSLC)community's openspecifications for linking data and other shared integration services,including dashboard,reporting,and security services.The following IBM Tivoli Monitoring components are used with Jazz for Service Management components:v The IBM Infrastructure Management Dashboards for Servers,the IBM Tivoli Authorization Policy Server,and tivcmdCommand Line Interface for Authorization Policy components provide a dashboard interface for displaying events,managed system group status,key OS metrics and for authorizing the servers that users can view in the dashboards.These components are installed and used with the IBM Dashboard for Application Services Hub component of Jazz for Service Management.v Monitoring agent report packages for analyzing historical trends are installed with the IBM Dashboard for Application Services Hub and Tivoli Common Reporting components of Jazz for Service Management.v Integration of IBM Tivoli Monitoring with other products using Open Services Lifecycle Collaboration(OSLC)interfaces for linked data requires the Tivoli Enterprise Monitoring Automation Server component of IBM Tivoli Monitoring,theRegistry Services,and optionally,the Security Services components of Jazz for Service Management.See the Introduction chapter of the IBM Tivoli Monitoring Installation and Setup Guide for more details on the productarchitecture and its components.See Chapter3of the IBM Tivoli Monitoring Installation and Setup Guide for additional installation requirements.With IBM Tivoli Monitoring,you can perform prerequisite checking for monitoring agents before performing aninstallation.See Chapter2in the IBM Tivoli Monitoring Installation and Setup Guide for further details on prerequisitechecking for IBM Tivoli Monitoring agents.IBM Tivoli Monitoring includes a Startup Center to perform a basic installation into either a local or a distributedenvironment configuration.Insert the appropriate IBM Tivoli Monitoring Startup Center CD into the CD-ROM drive of your Windows or Linux system,or access the product from Passport Advantage.See Chapter5in the IBM Tivoli Monitoring Installation and Setup Guide for further details on the Startup Center.components and monitoring agents,and optionally extend the environment to include an event synchronization with an event server,a dashboard environment,a reporting environment,and OSLC-linked data integration See the IBM Tivoli Monitoring Installation and Setup Guide for further installation details,information about configuration options,and adescription of steps to perform after installation.See the following publications for information on configuring IBM Tivoli Monitoring after installation is complete:v IBM Tivoli Monitoring Installation and Setup Guidev IBM Tivoli Monitoring Administrator's Guidev IBM Tivoli Monitoring Tivoli Enterprise Portal User's GuideIBM Tivoli Monitoring Licensed Materials-Property of IBM.©Copyright IBM ernment Users Restricted Rights-Use,duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.IBM,the IBM logo,and ®are trademarks or registered trademarks of International Business Machines Corp.,registered in many jurisdictions worldwide.Other product and service names might be trademarks of IBM or other companies.A current list of IBM trademarks is available on the Web at“Copyright and trademark information”(/legal/copytrade.shtml).Part Number:CF3QAMLPrinted in Ireland。
IBMAPM解决方案咨询
Application Infrastructure Management
应用配置管理
Application Configuration Management
应用运行时管理
Application Real time Management
应用开发管理
Application Development Management
响应时间
关注点：成败 • 批处理交易是否成
功
监控方法 • 监控HTTP层面，终端客户的感受，以及终端响
应时间在网络，客户端，服务段的消耗 • 通过专业的J2EE/.NET应用管理工具，实现对可
用性，性能，以及J2EE资源的全方位管理 • 应用日志监控 • 先明确SOA架构所涉及到的相关中间件和具体
的SOA架构 • 如果SOA架构基于专有的ESB系统, 通过专业的
应用运维管理
Application Operation Management
2
应用系统管理的维度
应用开发管理
应用运维管理
应用系统管理
Application Development
+
Application Operation
=
Apቤተ መጻሕፍቲ ባይዱlication System
Management
Management
11
应用开发对应用监控的支撑（样例分析）- 对比分析
根据以上数据分析： ▪ 采用方案一时，基金最新净值查询交易（纯平台）处理能力约降低10%，应用服务器CPU资源
消耗增加约19%；客户信息查询交易（上主机）处理能力降低约4%，应用服务器CPU资源消耗 增加约5%，网关服务器CPU资源消耗增加约1%，主机CPU消耗增加约9%. ▪ 采用方案二时，基金最新净值查询交易（纯平台）处理能力约降低2%，应用服务器CPU资源消 耗增加约2%；客户信息查询交易（上主机）处理能力降低约8%，应用服务器CPU资源消耗增 加约3.5%，网关服务器CPU资源消耗增加约3.5%，主机CPU消耗增加约7%. ▪ 方案一和方案二对比，基金最新净值查询交易（纯平台）方案一处理能力约低8%，应用服务 器CPU资源消耗增加约20%；客户信息查询交易（上主机）方案一处理能力高约5%，应用服务 器CPU资源消耗增加约1%，网关服务器CPU资源消耗减少约3%，主机CPU消耗低约4%. 综上所述，测试交易监控采用方案二整体性能较好，应用服务器CPU资源消耗增长不明显。主机 由于需要启用CICS TTAPI监控软件，导致主机CPU资源消耗均有所增加，而且方案二需要修改网 关、主机外联（EMUL程序）的程序，增加了一定的资源消耗。
- 1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。
第 1 页 共 9 页 1. ITM集中监控管理解决方案 概述 IBM Tivoli Monitoring可以帮助监测和管理关键的 IT 服务和资源，其中包括操作系统、数据库、应用程序和异构环境。ITM建立在一个轻便、高度可扩展的体系结构基础之上，并且已经完全全球化。它通过一个称为 Tivoli Enterprise Portal (Tivoli Enterprise Portal TEP) 的新型门户界面将不同平台（包括分布式、主机和应用程序系统）的视图合并到一起。TEP 使您可以在单个视图中集成并利用多个可用性管理产品，包括 ITM 5.1、ITM 6.1、IBM Tivoli Composite Application Management、IBM Tivoli Enterprise Console 和 IBM Tivoli OMEGAMON XE 产品。 为了保证应用正常运行的同时实现对重要参数的监控必须考虑管理信息对资源占用情况， Tivoli Monitoring对服务器的监控采用本地代理程序进行数据采集的方式（见下图），这种操作方式解决了传统的SNMP管理协议在进行系统管理时，由于可靠性和资源占用的问题会表现出力不从心。 Tivoli Monitoring采用的是本地代理程序的方式，管理员将需要检查的信息传送给被监测的终端，安装在终端的代理程序就按照所定义的监控周期和门限值定义进行检查。如果正常，就不需要向管理服务器进行汇报，只有设备出现问题时，才将数据传递给管理服务器，并采用声音、警告窗口等多种方式报警，从而大大减少网络上的管理信息。 IBM Tivoli Monitoring 的优点： 通过一个屏幕了解您的整个企业。 使用内置的复杂警报处理功能对问题划分优先级。 IBM Tivoli Monitoring 解决方案通过工作负载、网络和风险信息以及系统日志实时检测失控流程和资源消耗情况。“采取措施”(Take Action) 功能通过运行现有的脚本和从提供的模板创建的脚本来解决重复发生的问题，这样，您就可以把精力集中在其它关键领域上。 第 2 页 共 9 页
“警报”功能不仅仅是设置一个简单的阈值。内置的情形编辑器使您可以创建复杂的阈值、情形和警报――无需编写任何代码。这个功能使您可以通过图表方式合并许多衡量标准，以消除错误的警报。可用动态图表和表格来自定义工作区，这些图表和表格可即时正确地放置情形。 “专家建议”为如何解决已发生的问题提供建议。除了产品提供的情形，您还可以编辑“专家建议”，使之包含专门针对您的环境的解决方案，并为所有人员保留此知识。 IBM Tivoli Monitoring 解决方案使您可以将分散的操作系统信息合并到一个全企业系统性能视图中。这种完整的系统管理方法可以帮助管理不同的操作系统，例如 Windows、Linux、UNIX、中型服务器和主机。 因为 IBM Tivoli Monitoring 解决方案为您提供一个可扩展、可自动化、可定制的解决方案，这样，您就可以妥善进行增长规划。实时报告给您提供有关分布式环境的即时性能信息，而历史报告功能向您显示一段时间里操作系统的性能情况。通过对实时和历史报告进行合并，您可以确定趋势、预测系统行为并制定明智的管理决策来指导未来增长。 IBM Tivoli Monitoring 是一个真正的端到端的可用性管理解决方案，可以有效地管理 Microsoft、Linux、UNIX 甚至I/OS, z/OS 之间的性能和可用性。ITM 还包含一个新的 Tivoli Data Warehouse，“现成地”提供前所未有的报告灵活性，而且易于配置和适于使用。 第 3 页 共 9 页
系统架构和方案 在该平台架构中，我们分为三个层次： 第一层：基础资源采集层，例如服务器、数据库、存储、备份系统、中间件、网络系统监控、应用监控等，我们使用专业的监控产品进行实现，并且将监控数据储存在数据库中，以便历史数据查询； 第二层：功能层，功能层主要包括两大部分数据集中处理层和流程管理服务台，其中数据集中处理层我们主要通过Tivoli Netcool Object Server实现，包括压缩，事件关联，自动化处理等工作，并通过Netcool将事件信息传入历史数据库进行存储。通过统一的事件管理平台来整合基础资源与业务系统之间的逻辑关系，同时由Webtop实现综合监控呈现； 第三层：统一视图：统一视图需要实现以下功能，包括业务服务管理，系统管理，报表分析等。 根据功能架构设计及IBM Tivoli相应产品的功能特点，以下是此次项目的技术实现路线： 第 4 页 共 9 页
系统监控的范围 服务器系统监控 服务器管理针对整个系统中的大量运行关键业务的UNIX,Linux和Windows服务器，帮助提高其整体的对外服务可靠性。IBM Tivoli Monitoring可以将管理人员日常关注的资源对象、故障概率相对较高的资源对象、对应用影响较大的资源对象纳入到它的监控范围，管理人员通过制订监控策略并分发到管理对象上，从而获得对关键资源的7*24的监控能力。IBM Tivoli Provisioning Manager for Software可以实现跨平台环境的管理体系，这既包含Windows桌面机，也包含Unix、Linux服务器。TPM实现对这些不同系统服务器的硬件资产,软件资产扫描,为管理员提供全面,准确的系统软硬件配置信息,便于企业的资产管理。 Tivoli Monitoring可以提供的监控包括： 监控操作系统的主要参数，如CPU利用率、显示系统、用户、空闲时间的比例；交换空间的利用率、虚拟内存的利用率、消息队列的情况等。 第 5 页 共 9 页
监控特定的文件系统，包括文件系统磁盘使用情况、使用率、监控重要的文件的大小等。 监控特定的进程，监控任意关键进程的运行情况和状态变化情况，利用该功能可跟踪操作系统、数据库及用户应用系统的进程，并这些重要进程因意外原因终止时，可根据需要自动重启，并将报警信息写入事件日志。 另外对于IBM System p 服务器提供基于硬件的监控，包括服务器的运行状态和可用性，在同一控制台提供关于AIX,LPAR,CEC和VIOS资源的丰富图形化视图，查看虚拟资源与物理硬件如何映射，实现强大的监控能力和快速体现价值的目的。
数据库监控 数据库监控是整个系统的关键之一，为了加强对这一资源的管理工作，IBM Tivoli Monitoring for Databses(ITM for DB) 提供了大量的数据库监控和管理能力,其中包括Oracle，DB2，Sybase，MSSQLSERVER，Lotus Domino等。 Tivoli Monitoring for Database提供了一组预先定义的数据库监控器，可以监控所有的关键数据库性能比例，从简单的数据库状态到复杂的数据锁、客户端访问情况等的监控，以保证数据库的高可用性和性能。该功能基于IBM Tivoli Monitoring技术，允许用户为每个监控器定义多个事件阈值和自动维护操作。 ITM for DB支持历史性能数据的分析，通过内置的Tivoli Data Warehouse，管理员可以按时间顺序将多个数据库服务器的历史性能信息存储到压缩的历史性能数据库中。这些信息将帮助用户获得资源使用的趋势和模式。这样，用户可对潜在的问题或空间需求心中有数。 在整体分布式系统管理方案中，管理数据库资源十分重要。为了充分了解数据库的状态和性能，分析数据库之下的操作和为了资源也极其关键。Tivoli Monitoring for Database可以将这些系统资源的管理完美地集成于事件管理平台。Object server作为事件处理中心,能够收集所有被管理计算资源的警报和事件，包括数据库、网络和操作系统。Object server的分组和过滤功能显著减少了需要显示和人工干预的事件数。因此管理员就可以高效、有效地将精力集中于最重要的事件。 通过IBM Tivoli的数据库管理软件，可以为数据网系统中的所有数据库系 第 6 页 共 9 页
统提供统一的管理和监控功能。 通过应用最佳做法，消除了数据管理员 (DBA) 面临的确定监测什么、何时监测以及如何解释和处理监测结果的两难局面，从而为集中精力执行更复杂的关键业务任务留出更多时间。IBM Tivoli Monitoring for Databases 提供始终如一的例行监测――在数据库性能以及客户信心降低之前预见并纠正问题。 IBM Tivoli Monitoring for Databases 的特性 提供带有预设阈值和自动纠正措施的监测程序。 提供自动的“现成”值，特别适用于下面这样的新客户：他们需要为确保其数据库的健康状况而捕获的关键指标方面的指导。允许自动处理例行任务，使高级 IT 人员和数据库管理员可以集中精力处理更复杂的问题。 提供单个产品，该产品具有一个一致的体系结构，用来管理不同平台之间的多个数据库。 能够将数据馈送到一个中央存储库，以便跟踪一致性，并预测服务水平协议的违背情况。 在不同 IT 规则之间整合管理系统, 易于集成到一个端到端的管理解决方案中。 提供历史报告和实时报告 IBM Tivoli Monitoring for Databases 的益处 最大限度地提高 IT 人员的生产率和利用率。提供主动确定最重要且相 关的性能问题和事件的能力。 减少对 IT 和 DBA 人员的培训要求。提供针对 IT 资源的集中视图和控制能力，而不考虑其位置。 提供趋势分析数据，以便更好地规划和预测资源利用情况。 消除了使用多家供应商提供的不同产品管理企业的必要。
网络故障监控 Tivoli网络故障监控具有如下特点： 多渠道采集网络故障，典型的包括SNMP trap 、Syslog等 采集模块分布部署，面向未来扩展 采集模块具备健壮性能力，保障数据采集可靠性