Abstract: Rule removal from a data administration system occurs where new rules entered into the system encompass existing rules already in the system. Parameters of existing rules and new rules are compared to determine if any parameters of new rules encompass parameters of existing rules. If so, the existing rule is removed to optimize system performance by reducing process times and minimizing space required to store rules.

Abstract: According to the present invention, there is provided a method, system and program storage device for maintaining an active root filesystem in a storage subsystem comprising a plurality of storage devices. The method, system and program storage device comprise searching root partitions of the plurality of storage devices for a valid root filesystem, the root filesystem including mount points associated with the plurality of storage devices; mounting a root filesystem that is found first as the active root filesystem and mounting root partitions of the plurality of storage devices to the associated mount points within the active root filesystem; and replicating the active root filesystem across the plurality of storage devices in the storage subsystem, wherein the storage subsystem is bootable from any storage device of the plurality of storage devices that includes a replica of the active root filesystem.

Abstract: Rule removal from a data administration system occurs where new rules entered into the system encompass existing rules already in the system. Parameters of existing rules and new rules are compared to determine if any parameters of new rules encompass parameters of existing rules. If so, the existing rule is removed to optimize system performance by reducing process times and minimizing space required to store rules.

Abstract: According to the present invention, there is provided a method, system and program storage device for maintaining an active root filesystem in a storage subsystem comprising a plurality of storage devices. The method, system and program storage device comprise searching root partitions of the plurality of storage devices for a valid root filesystem, the root filesystem including mount points associated with the plurality of storage devices; mounting a root filesystem that is found first as the active root filesystem and mounting root partitions of the plurality of storage devices to the associated mount points within the active root filesystem; and replicating the active root filesystem across the plurality of storage devices in the storage subsystem, wherein the storage subsystem is bootable from any storage device of the plurality of storage devices that includes a replica of the active root filesystem.

Abstract: Disclosed is a server having a plurality of clients coupled to the server at client nodes, and coupled to a plurality of receivers. Events, which may range from a successful completion message to a major error alert, may be generated relating to the server or to the client nodes. A method is disclosed for dynamically selectively distributing the events to particular ones of the receivers, in response to a selective enabling/disabling of the events to each receiver. The method with respect to client nodes comprises: upon opening a session of a client node, the selectively enabled events/receivers relating to the client node are determined. Upon the selective enabling/disabling occurring during the session of the client node, the determined selectively enabled events/receivers relating to the client node are dynamically updated.

Abstract: Disclosed are a method, embodiable in computer readable program code, and a system for providing server-to-server event logging. A server-to-server event message is generated including 1) an event identifier, 2) any text insert pertinent to the event message, and 3) a source trail indicating the origin and history of the event, the source trail comprising an identifier of any server forwarding the event, each identifier separated by a special character, so that the origin and any subsequently transmitting servers may be known. Further, the source trail of a received server-to-server event message is parsed to determine each identifier in the source trail, and the event message transmitted to a receiving server only if the receiving server identifier is absent from the parsed source trail, thus preventing any loops which might cause the event to be repeated.