JP2005056392A - Method and device for validity inspection of resource regarding geographical mirroring and for ranking - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To improve the availability of an entire group, in a computing system group for maintaining a redundant resource at a geographically dispersed location. <P>SOLUTION: For managing a resource in a node operating as one portion of the computing system group that is dispersed geographically, the resource is configured regarding the usage, the availability of the resource is inspected regarding a resource pool, and one of them is selected. The resource includes at least one disk unit which is configured as a disk pool for switching the resource pool. Additionally, the availability of each disk unit is ranked regarding the resource pool, and at least one valid disk unit is selected. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention generally relates to the management of computer resources. More particularly, the present invention relates to resource configuration and accessibility for physically distributed resource pools.

  Recent computer systems that serve enterprise operations, such as large corporate sales or manufacturing operations, are not allowed to be unavailable for extended periods of time. Traditionally, disaster recovery focuses on unscheduled downtime due to, for example, power outages, natural disasters, site disasters, system hardware or software errors, application malfunctions, and deliberate behavior due to vandalism Has been hit. Unscheduled downtime usually results in the loss of computer resources, so that the backup system from the remote recovery site is used and operations are restored. Business interruptions can be long and in some cases days.

  Modern electronic commerce requires continuous system availability and protection from scheduled downtime. During scheduled system (eg, server) downtime or shutdown, the system is intentionally disabled for users (eg, clients). These scheduled downtimes can disrupt system operation and are difficult to adapt. Examples of scheduled downtime / shutdown include installation of new operating system and application software releases, system hardware upgrades, additions, deletions and maintenance, system backup, site maintenance, and programs Application of temporary correction (PTF). A system with “continuous availability” is defined as a system that has neither scheduled interruptions nor unscheduled interruptions.

  One way to improve and enhance system availability uses a clustered system. A cluster is a collection of computer system nodes that are either localized at a single site or distributed across multiple sites and all work together to provide a single integrated computing capability. is there. Clustered systems provide failover and switchover capabilities for computing systems such as database servers or application servers. One or more dedicated backup systems, including current copies (replicas) of resources, that provide the functionality provided on the clustered primary server system in the event of system interruption or site loss Switchover (or failover). Failover can be automated for unscheduled interruptions. In the case of a scheduled shutdown, the switchover can be triggered automatically as part of the scheduled shutdown procedure or manually.

  A cluster resource group is a subset of a cluster and has a large number of members, but typically defines one of those members as the primary member for that cluster resource group. A primary member is a primary access point for the group and hosts resources currently used by the group. Any other member of the group that is appropriately configured to take over the function of the primary member, that is, a node that is appropriately configured to take over the function of the primary member, is a backup member. Called. In one example, a backup member hosts redundant resources. In another example, a backup member can have access to primary resources that are normally hosted by the primary member. If the primary member fails, the backup member assumes the role of the primary member. When the backup member takes over the function of the primary member, the backup member takes over the resource of the previous primary member or changes the redundant resource to be the primary resource.

  In the event of a failover or switchover, a cluster resource service (CRS) that can be part of the server operating system and can run on all systems is the primary system. Provides a switchover from to backup system. This switchover has minimal impact on the application running on the end user or server system. Data requests are automatically rerouted to the backup system (ie, the new primary system). The cluster resource service also provides a means for automatic reintroduction or rejoining of the system to the cluster and restores the operational capabilities of the rejoined system.

  Another way to further improve and enhance system availability involves geographically distributing computing systems as well as computer resources such as data storage units. In such geographically distributed computer systems, different geographic sites have one or more computer subsystems, or nodes, that also control computer resources located at that site. Or can be hosted. Each of a plurality of geographical locations having nodes and resources of a computing system is called a “site”. Multiple sites, including parts of a geographically distributed computing system, generally interact with each other using a data communication system that supports data exchange between all sites and computer nodes located at those sites. Connected. Individual computing nodes that are part of a physically distributed computer system are generally to resources such as data storage devices, printers, and other shared peripheral devices that are co-located with the node. Have direct access. These systems typically maintain redundant resources such as data storage units, which include a copy of the primary resource. Typically, these redundant resources can be quickly configured to become primary resources if needed. Geographically distributed computing systems maintain redundant resources by communicating resource mirroring data from the primary site to another site. Maintaining redundant resources within a group avoids a single point of failure for the operation of that group.

  Data can be stored in a disk pool connected to one or more server systems. A disk pool is a set of disk units, such as a tower of disk units and a redundant array of independent disks (RAID). A disk pool is switched from the primary system to the backup system by switching ownership of the hardware entity containing the disk unit of the disk pool from the primary system to the backup system. However, the disk units in the disk pool must be physically located in the appropriate hardware entity (eg, a tower accessible to the primary system as well as the backup system), and many configurations And hardware placement rules. Users must also follow their configuration and hardware replacement rules when selecting disk units for a disk pool and when selecting primary and backup systems to access the disk pool. I must. Failure to do so may make the disk pool unavailable to the primary and / or backup system when a switchover is attempted or when a failover occurs. In addition, the user must follow these rules when changing the hardware configuration. The user is responsible for understanding and following this configuration and hardware replacement rules in order to properly configure the disk unit and cluster system. However, due to the complexity of the configuration as well as the hardware replacement rules, users may be forced to try and error, resulting in a disk unit that is unusable when a switchover occurs.

  Geographically distributed computing systems introduce additional conditions in the allocation of resources such as disk pools to server systems. Resources such as disk pools are generally assigned to computer systems located at the same physical site. A computer system located at one site is generally unable to host a disk pool, eg, located at another site. A traditional computer resource group generally has all nodes as well as all nodes in that computer resource group have access to all resources assigned to that computer resource group, and Requires resources to be co-located, which limits the flexibility of computer resource groups.

  Thus, when configuring a disk pool, a system and method for ensuring that a set of disks (ie, a disk pool, also known as an ASP) is accessible to a system at the same site. is necessary. Furthermore, there is a need to ensure the selection of valid disk units for configuration within a disk pool.

  Generally speaking, embodiments of the present invention are useful in computing system groups that maintain redundant resources in geographically distributed locations, for example, to improve the availability of the entire computing system group. Systems and methods for use are provided. Resources such as disk units in a disk pool maintained at each site can be switched between a primary system at one site and one or a plurality of backup nodes. Each geographically distant place is called a “site”. A primary system, a backup system (any number), and one or more resources arranged at a given site are configured as a cluster, and the availability of the site can be improved. A cluster is defined as a group of systems or nodes that are located at one site or distributed across multiple sites, where the nodes work together as a single system. Each computer system in the cluster is called a cluster node. Each site in a computing system group can have one or more computing systems or nodes, and the operations of the illustrated embodiment are for a site to operate with only one node. Is acceptable. Each site in the computer system group is a production site that contains primary resources that are used for current operations, or a mirror that contains redundant sources that mirror primary resources located at the production site.・ You can configure as a site. The illustrated embodiment of the present invention facilitates proper validation and ranking of site resources for use by the site cluster or computer node. A set of interfaces is provided for creating, adding, modifying, and deleting nodes in the site's cluster.

  In one embodiment, a mechanism is provided for validating and ranking one or more disk units located within the same site with respect to a specified disk pool. In another embodiment, before configuring a node as a primary node to access a disk pool or as a backup node, the accessibility of the disk units in that disk pool is determined with respect to that node. A mechanism is provided for inspection. In yet another embodiment, in preparation for initiating a switchover between a primary system and a backup system located at a site, the switchable when initiating clustering of multiple nodes at that site A mechanism is provided for validating the disk units in the disk pool.

  Briefly stated, according to the present invention, a system, method, and signal bearing media for managing resources in a system includes a configuration of at least one resource for use by the system. The system is associated with the site that contains the resource. The method also includes checking the availability of the at least one resource with respect to the resource pool. This check includes determining accessibility by the system and verifying that resources are located at the site. The method also includes selecting at least one of the at least one resource for the resource pool based on this check (which may include ranking). Only systems at the same site are checked to ensure that they have access to resources at that site, and the system does not seek access to resources at other sites.

  In another aspect of the invention, the system has a primary system associated with the site and a resource pool connected to the primary system. The system further includes a processor configured to check the availability of at least one resource with respect to the resource pool and to select at least one valid resource with respect to the resource pool. This availability check is performed based at least in part on at least one resource located at the site.

  The foregoing and other features and advantages of the present invention will become apparent from the following more detailed description of the preferred embodiments of the invention, as illustrated in the accompanying drawings.

  The content of the invention relating to the invention is set forth in detail and clearly in the claims which summarize this specification. The above and other features and advantages of the present invention will become apparent from the following detailed description with reference to the accompanying drawings. It should be noted that the leftmost digit of the reference number identifies the drawing in which the reference number first appears.

(Computing System Group)
In the drawings, like numerals are used to refer to like parts, and will be described in more detail below with reference to those drawings. First, referring to FIG. 1, an example of an embodiment of the present invention will be described. A computing system group 100 is illustrated that illustrates the overall system architecture. The computing system group 100 in this example shows two sites, site A 102 and site B 104. Embodiments of the present invention can be implemented using computing system groups having any number of sites between one or more and up to the maximum possible number. The site used in this example is defined as a group of computer nodes that have access to resources located within the physical location of the site. For example, the nodes in site A 102, namely node A 110 and node B 108, have access to the resources in resource pool A 130, ie, resource A 116, resource B 118, and resource Z 120. Similarly, nodes in site B 104, ie, node C 112 and node D 114, have access to resources in resource pool B 132, ie, resource C 121, resource D 122, and resource Y 124. In addition to these resources accessible by multiple nodes at the associated site, site A 102 includes a resource pool E 140 that includes resources that can only be accessed by node A 110 at that site. Resource pool E 140 in this example is not accessible by node B 108 or by nodes located at site B 104. A resource pool that can be accessed by multiple nodes in a site can be configured as a switchable resource pool, so that the node hosting the operation of that resource is different from the same site. It becomes possible to switch to the node.

  Each site in the illustrated embodiment has a number of nodes. Site A 102 is shown having Node A 110 and Node B 108. These nodes are connected via a data communication network 106 that supports data communication between nodes that are part of the same site as well as nodes that are part of different sites.

  In this example, these sites are geographically separated from each other and interconnected by an inter-site communication system 126. The inter-site communication system 126 typically connects the data communication networks 106 included in each faster site. The inter-site communication system 126 of the exemplary embodiment uses a high speed connection. Embodiments of the present invention use various inter-site communication systems 126 such as conventional WAN architecture, landline, terrestrial and satellite radio links, and other communication techniques. Embodiments of the present invention also operate with any number of sites having similar interconnections and constitute a continuous communication network between all nodes at those sites. Furthermore, embodiments of the present invention also include “sites” having computer nodes that are physically close to each other but do not have access to resources in the same resource pool. Sites that are physically close can share a single data communication network 106 and do not include a separate inter-site communication system 126.

  Resources contained within resource pools, such as resource pool A 130 and resource pool B 132, include data storage devices, printers, and other peripheral devices controlled by one node in the group Is included. Within computing system group 100, one node or member is designated as the primary member for that group. A primary member of a group hosts primary resources for the computing group, acts as an access point, and hosts resources managed by the group.

  A node and resource configuration 800 for Site A 102 in an example embodiment in accordance with the present invention is shown in FIG. An example node and resource configuration 800 for Site A 102 is Node A 110, Node B 108, Resource Pool A 130, the first tower of disk units, and the second tower of disk units. Resource pool E 140 is included. The operating system in Node A 110 or Node B 108 can be used to perform cluster management operations. Optionally, the node and resource configuration 800 is a cluster management computer that can be specialized for performing operations related to configuration, modification, maintenance, and other tasks related to the node and resource configuration 820. A system 820 can also be included. The cluster management computer system 820 may be connected to other components of the node and resource configuration 800 via a network, such as the computer system 200 described below with reference to FIG. A computer system can also be included.

  Resource pool A 130 and resource pool E 140 in this exemplary embodiment each include a plurality of disk units, such as a plurality of direct access storage disks (DASD). Resource pool A 130 in this exemplary embodiment includes DASD 11 802, DASD 12 804, DASD 13 806, and DASD 14 808, which are both defined as independent auxiliary storage pools (IASPs). It can be assumed that it is intended. Resource pool E 140 includes DASD 21 810 and DASD 22 812, which may both be intended to be defined as an auxiliary storage pool (ASP). Resource pool A 130 is connected to and can be accessed by Node A 110 and Node B 108. Resource E is only connected to Node A 110 and is therefore only accessible. In this exemplary embodiment, node A 110 is configured as the primary node for resource pool A 130 and node B 108 is the backup node for resource pool A 130 at site A 102. Configuration has been done (i.e., node B 108 has a new primary pool for resource pool A 130 when node A 110 becomes unavailable due to a scheduled or unscheduled shutdown. Become a node).

(Computer nodes and group members)
A block diagram of group member 200, which in one example embodiment is a computer system in accordance with one embodiment of the present invention, is shown in FIG. Group member 200 in this exemplary embodiment is IBM's eServer iSeries server system (eServer and iSeries are trademarks of IBM Corporation in the United States and other countries). Any suitably configured processing system can be used in accordance with embodiments of the invention as well. The computer system 200 has a processor 202 that is connected to a main memory 204, a mass storage interface 206, a terminal interface 208, and a network interface 210. These system components are interconnected by a system bus 212. Mass storage interface 206 is used to connect a mass storage device, such as DASD device 214, to computer system 200. One specific type of DASD device is a flexible disk drive, which can be used when storing data to and reading data from the flexible disk 216.

  Main memory 204 includes application programs 220, objects 222, data 226, and operating system images 228. Although shown here as being resident simultaneously in main memory 204, application program 220, object 222, data 226, and operating system 228 are always fully resident in main memory 204. Obviously, you don't have to be at all, and you don't even have to reside at the same time. The computer system 200 uses a conventional virtual addressing mechanism to allow a program to be a large unit, referred to herein as computer system memory, rather than multiple smaller storage entities such as main memory 204 and DASD device 214. Allows you to behave as if you are accessing a single storage entity. It should be noted here that the term “computer system memory” as used herein refers generically to the entire virtual memory of computer system 200.

  The operating system 228 is a suitable multitasking operating system such as IBM OS / 400 (OS / 400 is a trademark of IBM Corporation in the United States and other countries) operating system and the like. Embodiments of the present invention can use any other suitable operating system. Operating system 228 includes a DASD management user interface program 230, a DASD storage management program 232, and a group user interface program 234. Embodiments of the present invention use an architecture such as an object-oriented framework mechanism that allows instructions for operating system 228 components to execute on any processor in computer system 200.

  Although only one CPU 202 is shown for the computer 202, computer systems with multiple CPUs can be used effectively as well. Embodiments of the present invention incorporate an interface that includes a microprocessor that is used to reduce the processing load on CPU 202, each individually programmed. Terminal interface 208 is used to connect one or more terminals 218 directly to computer system 200. These terminals 218 can be non-intelligent or fully programmable workstations that allow system administrators and users to communicate with computer system 200.

  Network interface 210 is used to connect other computer systems or members of a cluster resource group, such as station A 240 and station B 242 to computer system 200. The present invention handles any data communication connection, including existing analog and / or digital techniques, or data communication connections through future network mechanisms.

  Although the illustrated embodiments of the present invention have been described in terms of a fully functional computer system, those skilled in the art will recognize these embodiments as a flexible disk, such as a flexible disk, as a program product. It will be appreciated that delivery can be via disk 216, CD-ROM, or other form of recordable media, or via any type of electrical transmission mechanism.

  Embodiments of the present invention include an operating system 228 that includes a DASD management user interface program 230 that performs functions related to configuration, operation, and other management functions, including an auxiliary storage pool. A function for selecting one or more DASDs for (ASP) is also included. An ASP is defined as a set of disk units, and an independent auxiliary storage pool (IASP) is a system-independent set of disk units. An IASP can be switched between systems if its disk unit is switchable and conforms to configuration and placement rules. The DASD management user interface program 230 can communicate with the DASD storage management (DSM) program 232, which is a component of the operating system 228 that provides internal support for disk unit management.

(Example of processing flow and software design)
FIG. 3 shows a flowchart 300 of a process for selecting one or more DASDs for an ASP according to an exemplary embodiment of the present invention. In the illustrated embodiment, method 300 illustrates a portion of DASD management user interface program 230 related to the selection of one or more DASDs for an ASP connected to a node located at a site. Can be understood. The method 300 begins at step 310 and waits for an ASP user selection at step 320, for which one or more DASDs will be configured. The user can select an existing ASP or a new ASP. In one embodiment, multiple DASDs and ASPs are selected and processed in parallel. When the user makes an ASP selection, the validity inspector is activated and, at step 330, the validity of all unconfigured DASDs at this node's site and ranking results are provided. Details of an example validity inspector will be described later. The results of the validity inspector are displayed to the user at step 340, including the validity and ranking of each unconfigured DASD for the selected ASP.

  In one embodiment, when selecting a disk unit for a disk pool, the validity inspector checks the rules described below to determine validity. It should be understood that the following rules are exemplary here and that different sets of rules may be followed for other systems. The first rule is to determine and ensure that all selected DASDs are associated and located at the site containing the node performing this method 300. Another rule is that disk units in different disk pools that can be switched separately cannot be in the same switchable entity. For example, separately switchable disk pools cannot have disk units located in the same tower. Yet another rule is that a disk unit that is not to be switched cannot exist in a switchable hardware entity that contains a disk unit for a disk pool that is to be switched. For example, a disk unit that stays with the system (eg, system ASP, ASP 32 of resource pool E 140) involves a disk unit in a switchable disk pool (eg, IASP 33 of resource pool A 130). Cannot exist in the same tower. Yet another rule is that the disk units in a switchable disk pool that will be switched to or from a particular system reside in a hardware entity that those particular systems can access. Specify what must be done. For example, a disk unit that is intended to be switched to a backup system cannot be in a tower that is not accessible to that backup system. Yet another rule is that disk units in the same disk pool must be under a hardware entity in the same power domain (ie, both powered on and off). Other rules, such as those related to system constraints, can also be used to determine the validity of DASD selection.

  In one embodiment, valid DASDs at that site are displayed in a ranked order. The output of the validity inspector will be one of the following: full, valid, warning, and invalid. The output “complete” indicates that the selected DASD is the best DASD for the specified ASP. The output “valid” indicates that the DASD does not have the best ranking, but the DASD can be placed in the specified ASP. The output “warning” indicates that the DASD may be invalid or suspicious for the specified ASP. The output “invalid” indicates that the DASD cannot be placed in the specified ASP. Details regarding the selected DASD as well as other unconfigured DASDs can be obtained from the LdValidityForAsp object (ie, the LdValidityForAsp object 502 described below).

  In one embodiment, the following factors are used for ranking effective DASD selections: First, the disk units for one disk pool are preferably maintained under the same switchable hardware entity. Second, the primary and / or backup system preferably has direct access to the switchable hardware entity (ie, no other entity in between). Third, the disk units for one disk pool are preferably contained within one switchable hardware entity (ie, a switchable hardware entity has more than one IASP). Not included). It should be understood that the above factors are exemplary and other sets of factors can be used for different systems, as will be understood herein.

  In another embodiment, invalid DASD can be displayed in addition to valid DASD. However, the example embodiment method 300 does not allow the user to select and configure an invalid DASD for the selected ASP. In yet another embodiment, each invalid DASD is displayed with one or more reasons that the invalid DASD is an inappropriate choice for the selected ASP. For example, apart from reasons for switchability, invalid DASDs may be invalidated due to capacity, protection, or other system rule violations. The user can change the invalid DASD to a valid DASD according to this invalid reason (eg, physically move the DASD to the appropriate location).

  In step 350, the method 300 waits until the user has selected one or more unconfigured valid DASDs in the ranking order for this ASP. In step 360, the method 300 passes this DASD selection to the DSM sandbox, an object for holding parameters relating to the DASD storage management program 234. The selected valid DASD configuration for this ASP (or IASP) may be completed as is well known in the art at step 370, after which the method 300 ends at step 380.

  In one implementation, method 300 can be implemented using object-oriented programming. An example of a software class design 400 and the role of each software class according to one embodiment of the present invention is shown in FIG. The related object and class methods will be described in more detail later with reference to FIGS. The software classes of the illustrated design 400 are: DASD Management (DM: DASD management) class 405, LdValidityForAsp class 410, ToyAsp class 415, ToyLd class 420, HdwSwitchingCapabilities class 430, SwitchableEntity cluster 435M Resource group management (CRG) class 440 and CRG (Cluster Resource Group) class 445 are included.

  The DASD Management (DM) class 405 provides a user interface for IASP configuration. In one implementation, the DASD Management (DM) class 405 instantiates the IASP configuration by creating an LdValidityForAsp object and an LdAdder sandbox object, and then each object in the sandbox (here: , Called “ToyLd”) (query (ing)). The LdValidityForAsp (ie, Logical DASD Validity For ASP: Logical DASD Validity for ASP) class 410 holds the validity and ranking results for unconfigured DASD in the LdValidityForAsp object.

  The LdAdder (ie, Logical DASD Adder) class 425 provides a selection of proposed DASD as well as ASP. Illustratively, the LdAdder class 425 includes a ToyAsp (ie, Toy ASP: Toy ASP) class 415 that represents the selected ASP and a ToyLd (ie, Toy Logical DASD) class 420 that represents unconfigured DASD. .

  The HdwSwitchingCapabilities (ie, Hardware Switching Capabilities) class 430 provides functions / methods for determining the switchability of the tower where the DASD is physically located. In one embodiment, the HdwSwitchingCapabilities class 430 provides the isParentSwitchable method and supports the SwitchableEntity class 435. The isParentSwitchable method determines whether the entity containing the disk unit can be switched.

  The SwitchableEntity class 435 provides functions / methods for evaluating switchability and includes an isResourceSwitchable function, an isResourceAccessible function, and an evaluateEntity function. The isResourceSwitchable function determines whether the IASP is defined in a cluster resource group (CRG). The isResourceAccessible function determines whether a node in the CRG recovery domain (ie, the primary and backup system at the site containing the resource) can access the resource. The evaluateEntity function determines whether the entity is in the same CRG.

  The CRGM (ie, Cluster Resource Group Management) class 440 provides functions / support for creation, addition, modification, deletion, and other operations related to cluster resource group management. Including. CRG (ie, Cluster Resource Group) class 445 is a user interface for controlling switchover and failover of resources (eg, IASPs) and for configuring nodes and resources in a CRG I will provide a. In one embodiment, the operation instantiation of CRG class 445 includes a query that uses the functions provided in SwitchableEntity class 435.

  A validity inspector object-oriented design 500 for an example validity inspector 330 that operates on nodes according to one embodiment of the present invention is shown in FIG. Also shown in FIG. 6 is an example unconfigured DASD validation and ranking processing flow 600 for a selected ASP that affects a node in accordance with one embodiment of the present invention. Processing flow 600 can be understood as a validation inspector instantiation at step 330.

  The method 600 begins at step 602 and proceeds to step 605 to create an LdValidityForAsp object 502 as well as an LdAdder sandbox 510. The LdValidityForAsp object 502 holds the switchability result, which includes the validity and ranking of the unconfigured DASD located at the site containing this node. The LdAdder sandbox 510 will correspond to the proposed ASP object 545 (eg, resource pool E 140 and resource pool A 130, respectively, of the node and resource configuration 800 when the configuration is performed). ToyAsp 32 545 and ToyAsp 33 545) and software equivalent objects of hardware DASD (eg, ToyLd 505, ie, as shown, DASD 11 802, DASD 12 804, DASD 13 806, DASD 14 808, DASD 21 810 1 ToyLd) per DASD, including DASD 22 812.

  In step 610, the method 600 queries each ToyLd 505 (ie, each unconfigured DASD) in the LdAdder sandbox 510 for configuration to the specified ASP. This query is activated by DASD Management 515 on each ToyLd object 505 via the validToBeInAsp function 520. In step 615, each ToyLd 505 then provides the switching capability of the hardware entity (eg, the parent entity) that physically contains the DASD corresponding to that ToyLd 505, for each corresponding HdwSwitchingCapabilities object 525. Make a query. Hardware entity switching capabilities are provided via the isParentSwitchable function 530.

  The method 600 then queries the SwitchabilityEntity object 535 at step 620 to determine if the resource (ie, the disk pool containing the DASD corresponding to the ToyLd being processed) can be switched. A SwitchableEntity object 535 queries the CRG object 540 to determine whether the resource (eg, ToyAsp 33) is defined in the CRG. For example, for ToyLd DASD 11, the SwitchableEntity object 535 determines whether the resource ToyAsp 33 is defined in the CRG as a switchable IASP (eg, resource 550).

  Next, in step 625, if the resource is switchable (ie, if the resource is an IASP defined in the CRG), the method proceeds to steps 630 and 635 for additional queries. . In step 630, the method 600 queries to see if nodes in the CRG recovery domain 555 (ie, primary and backup systems located at the site containing the resource) can access the resource. And in step 635, method 600 evaluates whether the entity (eg, resource and node system) is defined in the same CRG. For example, a node located at a different site from the resource does not need to access the resource. Subsequently, in step 640, the result of the possibility of switching the unconfigured DASD is returned to the LdValidityForAsp object 502. Returning to step 625 for reference, if the resource is not switchable, method 600 proceeds to step 640 and returns the result of the switchability of unconfigured DASD to LdValidityForAsp object 502. Thereafter, in step 650, the method 600 ends.

  In another embodiment, the operating system 228 of the computer system 200 also includes a cluster user interface program 234 for clustering two or more computer systems in the cluster. . Even in that case, the validity inspector can be activated to perform certain operations of the cluster user interface program 234. An example set of software objects used to check IASP switchability for clustering operations according to one embodiment of the invention is shown in FIG. In general, in each of the following embodiments, a CRGM object 710 invokes one or more functions in a SwitchableEntity object 720 that validates the clustering of operations via the CRG object 730. .

  In one embodiment, when adding a node to the CRG's recovery domain, the CRGM checks whether the proposed new node has access to the DASD in its IASP (s). The CRGM add_node_to_recovery_domain function 712 invokes the isResourceAccessible function 722, passing the parameters including the proposed new node as well as the existing IASP (s). The isResourceAccessible function 722 checks the IASP in the Resource object 732 and the node in the RecoveryDomain object 734 to determine whether the proposed new node has access to DASD in the IASP of the site to which the node belongs. . If the proposed new node has access to the DASD in that IASP, the user will be able to complete this CRGM operation. If the proposed new node does not have access to DASD in the IASP, a warning is displayed to the user configuring the proposed new node.

  In another embodiment, when adding an IASP to a CRG, the CRGM checks to see if all nodes in the specified recovery domain have access to the DASD in the IASP that will be added. To do. The CRGM add_iasp function 714 invokes the isResourceAccessible function 722, passing the parameters including the proposed new IASP as well as existing nodes in the specified recovery domain. The isResourceAccessible function 722 checks the IASP in the Resource object 732 and the nodes in the RecoveryDomain object 734, and all nodes in the specified recovery domain at the resource's site will be added in the IASP Check if you have access to DASD. If so, the user will be able to complete this CRGM operation. If not, a warning is displayed to the user who is configuring the proposed new IASP.

  When adding an IASP to a CRG, the CRGM can also check if any other CRG has the same switchable entity (eg, switchable tower) that contains the IASP. . The CRGM add_iasp function 714 invokes the getEntityes function 724 to retrieve the SwitchableEntity (s) for the proposed new IASP. The CRGM then searches other existing CRGs to determine if any other CRG has the same switchable entity. If no other CRG has the same switchable entity, the user will be able to complete this CRGM operation. If other CRGs have the same switchable entity, a warning is displayed to the user making the proposed IASP addition to the CRG.

  In another embodiment, when starting an IASP CRG (ie, when starting clustering), the CRGM checks for the switchability of that IASP. This additional validation provides potential switchability error detection due to hardware relocation (eg, cable and disk unit movement). This additional validation is also useful for errors caused by improper DASD configuration (for example, when clustering is not activated and the user ignores the configuration warning and configured DASD). Also detect. The CRGM start_clustering function 716 invokes the isResourceAccessible function 722 and passes a parameter containing the existing IASP (s) in the Resource object 732. The isResourceAccessible function 722 checks the nodes in the IASP and RecoveryDomain object 734 in the Resource object 732 and determines whether all nodes at the same site in the recovery domain have access to the DASD in the IASP. To do. If so, the user can complete the CRGM start_clustering function. If not, a warning is displayed to the user attempting a clustering operation.

  Embodiments of the present invention are incorporated within a computer system group 100 that is distributed among multiple geographic locations. The nodes that make up the overall computer system group 100 may be distributed among multiple geographic locations according to any combination. A geographic location, or site, where two or more nodes are located, as described herein, can be configured within a cluster resource group and includes resources located at those sites Can act as part of a recovery domain. Alternatively, a site can have a single node that controls resources at that site. This is because failure of that one node at that site can result in failover to a node at another site, thus maintaining multiple computing system group availability, By not requiring nodes, it is possible to reduce costs. Another advantage of a site with a single computing system node is that the site does not require switchable hardware.

  An example of an initial configuration processing flow 900 according to one embodiment of the present invention is shown in FIG. The illustrated initial configuration processing flow 900 is compatible with a site configuration having a single node and ensures the configuration of a site having multiple nodes with higher availability. The illustrated initial configuration processing flow 900 begins at step 902 and proceeds to step 904 to determine whether the current site has more than one node. If this site has more than one node, processing proceeds to step 908 to configure the node at the site with a recovery domain for resources located at this site. If the site has only one node, processing proceeds to step 906 to configure that node to host the site's resources. After configuration of the site node, processing proceeds to step 910 where processing continues by performing operation of the site node as a member of the computing system group 100.

(Examples of software and hardware not intended to be limited)
Embodiments of the present invention may be embodied as a program product for use with a computer system, such as the cluster computing environment shown in FIG. 1 and described herein, for example. The program product program (s) may define functions of these embodiments (including the methods described herein) and be included on various signal-bearing media. Examples of signal bearing media are not intended to be limiting; (i) write-protected storage media that permanently stores information (eg, a CD-ROM disc readable by a CD-ROM drive, etc.) A read-only memory device in a computer); (ii) a writable storage medium that stores information variably (eg, a flexible disk or hard disk drive in a flexible disk drive); or (iii) a computer Communication media over a computer network or telephone network, including, for example, wireless communication. The last embodiment specifically includes the downloading of information from the Internet or other networks. When this type of signal bearing media carries computer readable instructions carrying the functionality of the present invention, it represents an embodiment of the present invention.

  In general, the routines executed to embody the embodiments of the invention may be embodied as part of an operating system or as a particular application, component, program, module, object, or sequence of instructions. Regardless of whether it is embodied, it can be called a “program” here. A computer program typically consists of a plurality of instructions that are to be translated by a native computer into a machine-readable format and thus into executable instructions. A program also includes variables and data structures that either reside locally to the program or are found in memory or on a storage device. In addition, the various programs described herein can be identified based on the symmetrical application in which they are embodied in a particular embodiment of the invention. However, it is necessary to recognize that the name of any particular program is used for convenience only, and therefore the present invention is not limited to use only in a particular application identified and / or implied by such name. There is.

  In addition, there are innumerable ways to organize a computer program into routines, procedures, methods, modules, objects, etc., as well as program functions between various software layers resident in a general computer. Given the various ways of allocating (eg, operating system, library, API, application, applet, etc.), the following is also apparent. It should be recognized that the present invention is not limited to the specific organization and assignment or program functionality described herein.

  The present invention can be realized in hardware, software, or a combination of hardware and software. A system according to a preferred embodiment of the present invention can be distributed in a centralized or distributed manner within a single computer system, i.e., various elements are distributed across several interconnected computer systems. It is possible to realize in a manner. Any type of computer system or other apparatus adapted for performing the methods described herein is suitable. A general-purpose computer with a computer program that controls the computer system so that when the typical hardware and software combination is loaded and executed, the computer performs the methods described herein. It can be a system.

  Each computer system specifically includes one or more computers and at least one signal bearing media, ie, signals from which the computer carries data, instructions, messages or message packets, and other information. It may include a signal carrier medium that can be read. The signal bearing media can include non-volatile memory such as ROM, flash memory, disk drive memory, CD-ROM, and other permanent storage. In addition, computer media may include volatile storage such as RAM, buffers, cache memory, and network circuitry, for example. In addition, signal bearing media are signals that carry information in temporary state media such as network links and / or network interfaces, including wired or wireless networks, where the computer carries such information. It is possible to include a signal capable of reading a signal to be read.

  While specific embodiments of the invention have been disclosed above, as will be appreciated by those skilled in the art, changes may be made to the specific embodiments without departing from the spirit and scope of the invention. It is possible to do. Accordingly, the scope of the invention is not limited to these specific embodiments. Furthermore, the appended claims are intended to protect all such applications, modifications, and embodiments that fall within the scope of the invention.

  In summary, the following matters are disclosed regarding the configuration of the present invention.

(1) In a method for managing resources in a node: configuring at least one resource for use by a node, wherein the node is associated with a site containing the resource; Performing an availability check of the at least one resource with respect to a resource pool, comprising determining accessibility by the node and verifying that the resource is located at the site And selecting at least one of the at least one resource for the resource pool based on the examination.
(2) the at least one resource includes at least one disk unit, and the method further includes: configuring the resource pool as a switchable disk pool; The method according to (1) above.
(3) The node is a single node located at the site, and the node operates as part of a geographically distributed computing system group. The method described in 1.
(4) the at least one resource includes at least one disk unit, and the method further includes: ranking availability of each disk unit with respect to the resource pool; and Selecting the at least one valid disk unit for the resource pool according to an availability ranking.
(5) The method according to (4), further comprising: providing at least one reason to the user and explaining the validity and ranking of each disk unit.
(6) The method according to (1), wherein the node is a part of a cluster resource group.
(7) The method according to (6), wherein the cluster resource group includes a primary node and at least one backup node.
(8) Further: when adding a node to the recovery domain of a cluster resource group, includes checking for availability of resources in the resource pool, wherein the check includes the node The method according to (6) above, including the determination of being associated with a site including a pool.
(9) Further: when adding a switchable resource pool to the cluster resource group, recovery of the cluster resource group located at the site for each resource in the switchable resource pool The method according to (6) above, including: verifying accessibility by each node in the domain.
(10) The method according to (9), wherein the switchable entity that includes the switchable resource pool is not included in another cluster resource group.
(11) The method according to (6), further including: checking the switchability of the switchable resource pool at the start of clustering.
(12) In a signal bearing medium containing a program that, when executed by a processor, performs an operation relating to the management of resources within a node, said operation is: configuring at least one resource for use by the node. The node is associated with a site containing the resource; checking availability of the at least one resource with respect to a resource pool, wherein the determination of accessibility by the node And performing the check including verification that the resource is located at the site; and selecting at least one of the at least one resource for the resource pool based on the check about It is intended to include, signal-bearing media.
(13) The signal bearing medium according to (12), further including: configuring the resource pool as a switchable disk pool.
(14) The node is a single node located at the site, and the node operates as part of a geographically distributed computing system group. The signal carrier medium described in 1.
(15) The step further includes: ranking each resource with respect to the resource pool; and selecting at least one valid resource with respect to the resource pool according to the ranking result; The signal carrying medium according to (12) above.
(16) The signal bearing medium according to (15), wherein the step further includes: providing at least one reason to the user and explaining the validity and ranking of each resource.
(17) The signal bearing medium according to (12), wherein the node is part of a cluster resource group.
(18) In the above (17), the step further includes: checking the availability of resources in the resource pool when adding a node to the recovery domain of the cluster resource group The signal carrier medium described.
(19) The step further includes: when adding a switchable resource pool to the cluster resource group, for each resource in the switchable resource pool, in the recovery domain of the cluster resource group The signal carrying medium according to (17), including verifying accessibility by each of the nodes.
(20) The step (17) further comprising: verifying that the switchable entity that includes the switchable resource pool is not included in another cluster resource group. The signal carrier medium described in 1.
(21) The signal-carrying medium according to (17), wherein the step further includes: checking the switchability of the switchable resource pool at the start of clustering.
(22) a primary node associated with a site; a resource pool connected to the primary node; and for the resource pool, check availability of at least one resource, and for the resource pool, A processor configured to select at least one valid resource, wherein the availability is checked at least in part on the basis of the at least one resource located at the site; system.
(23) The processor is further configured to rank each resource with respect to the resource pool and to select at least one valid resource with respect to the resource pool according to the ranking. The system according to (22) above.
(24) The system according to (23), wherein the processor is further configured to provide at least one reason to the user and explain the validity and ranking of each resource.
(25) The system according to (22), wherein the resource pool is configured as a switchable resource pool.
(26) The system according to (25), further including at least one backup node connected to the switchable resource pool.
(27) The processor is further configured to check the accessibility of each resource in the switchable resource pool when adding a node to the recovery domain of the cluster resource group. The system according to (25) above, wherein
(28) When the processor further adds the switchable resource pool to the cluster resource group, the recovery of the cluster resource group for each resource in the switchable resource pool The system according to (25), wherein the system is configured to verify accessibility by each node in the domain.
(29) The processor is further configured to verify that a switchable entity that includes the switchable resource pool is not included in another cluster resource group. The system according to (25) above.
(30) The system according to (25), wherein the processor is further configured to check the switchability of the switchable resource pool at the start of clustering.

1 is a block diagram of a computing system group illustrating the overall system architecture of an example embodiment of the invention. FIG. FIG. 2 is a block diagram illustrating group members of the group shown in FIG. 1 in accordance with an example embodiment of the present invention. 6 is a flowchart illustrating a process for selecting one or more DASDs for an ASP, according to an example embodiment of the present invention. FIG. 6 is an explanatory diagram illustrating an example of software class design and the role of each software class, according to an example embodiment of the present invention. FIG. 6 is an illustration showing an object-oriented design of a validity inspector for an example validity inspector, according to an example embodiment of the present invention. 6 is a flowchart illustrating an example unconfigured DASD validation and ranking process for a selected ASP, in accordance with an example embodiment of the present invention. FIG. 6 is an illustration showing an example set of software objects used to check IASP switchability for clustering operations according to an example embodiment of the present invention. FIG. 2 is a block diagram illustrating node and resource configurations for the site of FIG. 1 in accordance with an example embodiment of the present invention. 6 is a flowchart illustrating a process of initial configuration according to an example embodiment of the present invention.

Explanation of symbols

100 Computer System Group / Computing System Group 102 Site A
104 Site B
106 Data communication network 108 Node B
110 Node A
112 Node C
114 Node D
116 Resource A
118 Resource B
120 Resource Z
121 Resource C
122 Resource D
124 Resource Y
126 Communication system between sites 130 Resource pool A
132 Resource pool B
140 Resource pool E
200 Group Member / Computer System 202 CPU / Processor 204 Main Memory 206 Mass Storage Interface 208 Terminal Interface 210 Network Interface 212 System Bus 214 DASD Device 216 Flexible Disk 218 Terminal 220 Application Program 222 Object 226 Data 228 Operating System / Operating System Image 230 DASD Management User Interface Program 232 DASD Storage Management Program / DSM Program 234 Cluster User Interface Program / Group User Interface Program 240 Station A
242 Station B
300 flow / method 330 validity inspector 400 design 405 DASD Management (DM) class 410 LdValidityForAsp Class 415 ToyAsp Class 420 ToyLd Class 425 LdAdder Class 430 HdwSwitchingCapabilities Class 435 SwitchableEntity Class 440 CRGM Class 445 CRG Class 500 design 502 LdValidityForAsp object 505 ToyLd object 510 LdAdder Sandbox 515 DASD Management
520 validToBeInAsp function 525 HdwSwitchingCapabilities object 530 isParentSwitchable function 535 SwitchabilityEntity object / SwitchableEntity object 540 CRG object 545 ASP object / 545 ASP object / 545 ASP
550 resource 555 CRG recovery domain 600 Processing Flow / method 710 CRGM object 712 Add_node_to_recovery_domain function 714 Add_iasp function 716 Start_clustering function 720 SwitchableEntity object 722 IsResourceAccessible function 724 getEntities function 730 CRG object 732 Resource Object 734 RecoveryDomain objects 800 nodes and resource configuration 802 DASD 11
804 DASD 12
806 DASD 13
808 DASD 14
810 DASD 21
812 DASD 22
820 Cluster Management Computer System 900 Processing Flow

Claims (30)

In a method for managing resources in a node:
Configuring at least one resource for use by a node, said node being associated with a site containing said resource;
Checking the availability of the at least one resource with respect to a resource pool, the checking including determining accessibility by the node and verifying that the resource is located at the site ;and,
Selecting at least one of the at least one resource for the resource pool based on the check;
Including methods. The at least one resource shall include at least one disk unit, and the method further includes:
Configuring the resource pool as a switchable disk pool;
The method of claim 1, comprising:   The method of claim 1, wherein the node is a single node located at the site, the node operating as part of a geographically distributed computing system group. . The at least one resource shall include at least one disk unit, and the method further includes:
Ranking the availability of each disk unit with respect to the resource pool; and
Selecting at least one valid disk unit for the resource pool according to the availability ranking;
The method of claim 1, comprising: further:
Provide at least one reason to the user and explain the validity and ranking of each disk unit;
The method of claim 4, comprising:   The method of claim 1, wherein the node is part of a cluster resource group.   The method of claim 6, wherein the cluster resource group comprises a primary node and at least one backup node. further:
When adding a node to the recovery domain of a cluster resource group, includes checking availability of resources in the resource pool, wherein the checking includes a site where the node includes the resource pool The method of claim 6, comprising determining that it is associated with. further:
When adding a switchable resource pool to the cluster resource group, each resource in the switchable resource pool in the recovery domain of the cluster resource group located at the site Verifying accessibility by nodes;
The method of claim 6, comprising:   The method of claim 9, wherein a switchable entity that includes the switchable resource pool is not included in another cluster resource group. further:
Checking the switchability of the switchable resource pool at the start of clustering;
The method of claim 6, comprising: In a signal-bearing medium that includes a program that, when executed by a processor, performs operations related to management of resources within a node, the operations include:
Configuring at least one resource for use by a node, said node being associated with a site containing said resource;
Checking the availability of the at least one resource with respect to a resource pool, the checking including determining accessibility by the node and verifying that the resource is located at the site ;and,
Selecting at least one of the at least one resource for the resource pool based on the check;
A signal-bearing medium. Further the steps are:
Configuring the resource pool as a switchable disk pool;
The signal carrying medium according to claim 12, comprising:   The signal of claim 12, wherein the node is a single node located at the site, the node operating as part of a geographically distributed computing system group. Carrier media. Further the steps are:
Ranking each resource with respect to the resource pool; and
Selecting at least one valid resource for the resource pool according to the ranking result;
The signal carrying medium according to claim 12, comprising: Further the steps are:
Provide the user with at least one reason and explain the relevance and ranking of each resource;
The signal carrying medium according to claim 15, comprising:   The signal bearing media of claim 12, wherein the node is part of a cluster resource group. Further the steps are:
Checking availability of resources in the resource pool when adding a node to the recovery domain of the cluster resource group;
The signal carrying medium according to claim 17, comprising: Further the steps are:
When adding a switchable resource pool to the cluster resource group, the accessibility of each resource in the switchable resource pool by each node in the recovery domain of the cluster resource group Verifying;
The signal carrying medium according to claim 17, comprising: Further the steps are:
Verifying that the switchable entity that encompasses the switchable resource pool is not contained within another cluster resource group;
The signal carrying medium according to claim 17, comprising: Further the steps are:
Checking the switchability of the switchable resource pool at the start of clustering;
The signal carrying medium according to claim 17, comprising: Primary node associated with the site;
A resource pool connected to the primary node; and
A processor configured to check availability of at least one resource with respect to the resource pool and to select at least one valid resource with respect to the resource pool, the availability comprising the site A system in which the at least one resource located in a network is to be examined at least in part on a basis.   23. The processor is further configured to rank each resource with respect to the resource pool and to select at least one valid resource with respect to the resource pool according to the ranking. The system described in.   24. The system of claim 23, wherein the processor is further configured to provide at least one reason to a user to account for the validity and ranking of each resource.   23. The system of claim 22, wherein the resource pool is configured as a switchable resource pool.   26. The system of claim 25, further comprising at least one backup node connected to the switchable resource pool.   The processor is further configured to check the accessibility of each resource in the switchable resource pool when adding a node to the recovery domain of the cluster resource group. 26. The system of claim 25.   The processor further adds, when adding the switchable resource pool to the cluster resource group, each resource in the switchable resource pool in the recovery domain of the cluster resource group. 26. The system of claim 25, wherein the system is configured to verify accessibility by each node.   The processor is further configured to verify that a switchable entity that includes the switchable resource pool is not included in another cluster resource group. 26. The system of claim 25.   26. The system of claim 25, wherein the processor is further configured to check for switchability of the switchable resource pool at the start of clustering.

Images