Method for assuring compatibility and method for securing data within a distributed computer system

• US 20030163804A1
• Filed: 12/30/2002
• Published: 08/28/2003
• Est. Priority Date: 02/23/2000
• Status: Abandoned Application

• Current Assignee: Siemens AG
• Original Assignee: Siemens AG
• Inventors: Hahnefeld, Dirk, Zoeller, Georg, Burke, Wolfgang, Schoepf, Johannes, Stryczek, Bernhard, Laghi, Giovanni, Frank, Claus-Andreas
• Application Number:
  US10/204,510
• Publication Number:
  US 20030163804A1
• Time in Patent Office: Days
• US Class Current: 717/170
• CPC Class Codes: G06F 15/177 Initialisation or configuration control processor initialisation G06F9/4405
• CPC Class Codes: G06F 9/4405 Initialisation of multiprocessor systems

Abstract

The invention relates to a method for assuring compatibility between the software units activated in partial computer systems (system A, system B) belonging to a distributed computer system, said software units each comprising their respective version of software codes and/or data. Once a compatibility test has established compatibility, a compatible non-activated software unit is activated on its partial computer system and the corresponding previously activated software unit is deactivated. The invention also relates to a method for securing data within a distributed computer system with several partial computer systems, for blocking access to the data, for securing common data and for deactivating the data access block are carried out according to the current status of the data securing option.

Claims

1. A method for ensuring the compatibility between software units which are activated in computer subsystems (System A, System B) which belong to a distributed computer system and each have one version standard of software code and data, during system initialization of at least one such computer subsystem, with the following steps being carried out:

a) after finding an incompatibility between a software unit which is activated in a first computer subsystem and at least one software unit which is activated in a further computer subsystem, further software units which have not been activated and which exist on the respective computer subsystems are compared-with one another for compatibility,

b) in the event of compatibility being found from the comparison, a compatible software unit, which has not been activated, is activated in its computer subsystem, and the corresponding, previously activated, software unit is deactivated.

2. The method as claimed in claim 1, characterized in that the system initialization is carried out on a system new start, and/or when restarting the system.

3. The method as claimed in claim 1 or 2, characterized in that version numbers of the software units which exist in a computer subsystem are entered in a list, with the version number of an activated software unit being stored in first place in the list.

4. The method as claimed in claim 3, characterized in that the version number of a software unit is entered in the list by setting a version attribute (GCS).

5. The method as claimed in one of the preceding claims, characterized in that the version numbers of software units which are entered from the second place in the list are sorted in an ascending sequence on the basis of the time since they were last updated.

6. The method as claimed in one of the preceding claims, characterized in that that software unit which has the latest version standard of the compatible software units which have not been activated is always selected for activation of a compatible unactivated software unit.

7. The method as claimed in one of the preceding claims, characterized in that compatibility between software units which are activated in computer subsystems is ensured automatically during the system initialization of at least one such computer subsystem.

16. The method as claimed in one of the preceding claims, characterized in that said method is used in a switching system which has at least two computer systems (CP, SSNC).

8. A method for data back-up within a distributed computer system having a number of computer subsystems (System A, System B) within which a data back-up is initiated in each computer subsystem after a software change, and is synchronized in the respective computer subsystems at synchronization points which are defined in the data back-up procedure, with the following steps being carried out as a function of the current state of the data back-up procedure:

a) a data back-up of data which other computer subsystems cannot access is carried out in each computer subsystem,

b) a data access block is activated in each computer subsystem,

c) a data back-up of data which other computer subsystems can also access is carried out in each computer subsystem, and

d) the data access blocks are deactivated.

9. The method as claimed in claim 8, characterized in that, for synchronization of the data back-up, the computer subsystems are informed at the synchronization points that the data back-up which has in each case been initiated in a computer subsystem has reached a status which is defined for continuing the data back-up.

10. The method as claimed in claim 8 or 9, characterized in that the synchronization points are defined by time intervals.

11. The method as claimed in claim 8 or 9, characterized in that the synchronization points are implemented in the form of points defined in the software code.

12. The method as claimed in one of claims 8 to 11, characterized in that, after the data back-up, the version standard of the backed-up data is stored in the respective computer subsystem.

13. The method as claimed in one of claims 8 to 12, characterized in that the version standard of the backed-up data is stored by setting a version attribute (GCS), which is stored in the respective computer subsystem.

14. The method as claimed in one of claims 8 to 13, characterized in that the data back-ups which take place in the respective computer subsystems are controlled from a central point by means of control software.

15. The method as claimed in one of claims 8 to 14, characterized in that information relating to rejected changes to the data to be backed up is held temporarily in a record file during the data access block, in order to allow the changes to the data to be carried out once the data access block has been canceled.