system160administration(编辑修改稿)

system160administration(编辑修改稿)内容摘要：

Distributed administration of distributed hardware. Relies on full support resources located in the remote sites or branch offices to perform the support function of systems distributed to those sites. 4 Processes and Activities This chapter provides a detailed discussion of the processes and activities that occur in the System Administration SMF. System Administration Models Determining how best to craft the system administration function within your pany is mainly contingent upon the size, capacities, and capabilities of your architecture and IT staff. Large anizations will obviously deploy a more sophisticated administrative model while smaller anizations will be likely to consolidate functions based upon the amount of work that is required to maintain administrative health. The five basic models discussed in this document are illustrated in Figure 2. These five models essentially take into consideration an anization’s ability to centralize puting resources and the associated administrative functions, as well as its need to distribute some or all of the puting and administrative resources to sites apart from a central data center. C e n t ra l i ze dH a rd w a reC e n t ra l i ze dAd m i n i s t ra t i o nC o s t to D e p l o y / Su p p o r tSophistication of Model SelectedD i s t ri b u t e dH a rd w a reC e n t ra l i ze d /R e m o t e )Ad m i n i s t ra t i o nD i s t ri b u t e dH a rd w a reC e n t ra l i ze d /D e l e g a t e dAd m i n i s t ra t i o nD i s t ri b u t e dH a rd w a reH yb ri d(F o l l o w t h e Su n )D i s t ri b u t e dH a rd w a reD i s t ri b u t e dAd m i n i s t ra t i o n Figure 2. Administrative models with cost/sophistication indicators 10 System A dministration Centralized Administration of Centralized Hardware The first model, centralized administration, is illustrated in Figure 3. As shown in Figure 3, all or most of the operations and support functions are centrally located in a single site, or sites. (Multiple sites are discussed later.) With the maturation of local area, wide area, distributed, and client server puting and their supporting works, more and more anizations have made great strides toward centralizing support for installed resources, applications, and solutions. Bandwidth to remote sites and branch offices is more widely available and affordable. Basic technologies that support branch office puting (transmission protocols, remote access tools, headless servers, and so on) have improved to the point where each branch office no longer needs its own separate support staff. Companies are thus increasingly able to centralize the fundamental support functions required to maintain the availability, reliability, daytoday support, and management of systems that are distributed to the remote sites or branch offices. Centralized administration typically assumes that all or most of the puting systems and resources being managed (administered) are centrally located. While this is increasingly true, there continues to be cases where specific solutions (that is, custom applications, specialized databases, and so on) are not centralized in the corporate data center but instead are distributed to the remote branch or site. This distribution of some applications and databases does not prevent taking a centralized approach to the administrative model. The centralized/remote administration model, described later, acmodates both centralized administration and the distribution of some solutions. Figure 3. Completely centralized architecture Figure 3 shows a model where all puting resources being managed are located centrally in the corporate data center (sometimes also called the puting center or corporate technology center). The administration resources required to perform the tasks and procedures are centrally located at the data center with the puting systems. This model offers the advantage of greater control over all resources, achieved through physically locating everything (systems and people) at a mon site. It also offers reduced costs. Compared to the distributed, remote, and hybrid models, there is a reduction in operating costs because the model does not require maintaining remote data centers to support distributed systems and administrative resources. The centralized Service Management Function 11 administration model assumes that you are managing missioncritical, highavailability systems that require a full data center infrastructure, including highly available power, environmental conditioning, faulttolerance in all data center ponents, and all the security systems appropriate to the deployment. The disadvantage of the centralized administration model is that it requires maintaining highspeed bandwidth to all remote sites, along with the appropriate levels of redundancy and fault tolerance in the work links. If a remote location supports a large number of users, the bandwidth requirements necessary to maintain the performance characteristics required to support your service level agreements can be substantial. One way to resolve the issue of maintaining expensive wide area work (WAN) links to a remote site with a large number of users is to distribute the systems to those sites while continuing to perform management, operation, and administration functions from the central location. The resulting model, called “centralized/remote administration,” is discussed in the next section. Centralized/Remote Administration of Distributed Hardware The centralized/remote administration model, shown in Figure 4, achieves most of the benefits of the pletely centralized model. Most administration continues to be performed at the central location (that is, central data center) thereby retaining the。