Abstract: A method and associated systems for backing up a target computer application that comprises identifying and backing up databases and other information repositories upon which the target application depends. The target application is identified and related to a backup requirement that specifies a minimum application-backup frequency. The application's “dependencies” are automatically identified from sources that include configuration files, where each dependency identifies one or more databases or other information repositories that store information upon which the application directly or indirectly depends. If any of these databases or repositories is associated with a backup frequency less than the application's minimum backup frequency, the database or repository is flagged. Each flagged entity's backup schedule is then revised so that the flagged entity's backup frequency is equal to or greater than the application's minimum backup frequency.

Abstract: A method and associated systems for backing up a target computer application that comprises identifying and backing up databases and other information repositories upon which the target application depends. The target application is identified and related to a backup requirement that specifies a minimum application-backup frequency. The application's “dependencies” are automatically identified from sources that include configuration files, where each dependency identifies one or more databases or other information repositories that store information upon which the application directly or indirectly depends. If any of these databases or repositories is associated with a backup frequency less than the application's minimum backup frequency, the database or repository is flagged. Each flagged entity's backup schedule is then revised so that the flagged entity's backup frequency is equal to or greater than the application's minimum backup frequency.

Abstract: A method and associated systems for backing up a target computer application that comprises identifying and backing up databases and other information repositories upon which the target application depends. The target application is identified and related to a backup requirement that specifies a minimum application-backup frequency. The application's “dependencies” are automatically identified from sources that include configuration files, where each dependency identifies one or more databases or other information repositories that store information upon which the application directly or indirectly depends. If any of these databases or repositories is associated with a backup frequency less than the application's minimum backup frequency, the database or repository is flagged. Each flagged entity's backup schedule is then revised so that the flagged entity's backup frequency is equal to or greater than the application's minimum backup frequency.

Abstract: An incompatible software level of an information technology infrastructure component is determined by comparing collected inventory information to a minimum recommended software level. If a knowledge base search finds that the incompatible software level is associated with a prior infrastructure outage event, an outage count score is determined for the incompatible software level by applying an outage rule to a historic count of outages caused by a similar incompatible software level, and combined with an average outage severity score assigned to the incompatible software level based on a level of severity of an actual historic failure of the component within a context of the infrastructure to generate a normalized historical affinity risk score. The normalized historical affinity risk score is provided for prioritizing the correction of the incompatible software level in the context of other normalized historical risk level scores of other determined incompatible software levels.

Abstract: An incompatible software level of an information technology infrastructure component is determined by comparing collected inventory information to a minimum recommended software level. If a knowledge base search finds that the incompatible software level is associated with a prior infrastructure outage event, an outage count score is determined for the incompatible software level by applying an outage rule to a historic count of outages caused by a similar incompatible software level, and combined with an average outage severity score assigned to the incompatible software level based on a level of severity of an actual historic failure of the component within a context of the infrastructure to generate a normalized historical affinity risk score. The normalized historical affinity risk score is provided for prioritizing the correction of the incompatible software level in the context of other normalized historical risk level scores of other determined incompatible software levels.

Abstract: The invention enables server administrators (SAs) to improve their productivity and performance. With the methods and systems described herein, the prior art needed to search for appropriate tools for appropriate tasks is minimized and/or eliminated. Easier scripting and automation that does not require implementation across tools is provided. A consistent logical place is provided for all resources to be used. Standardization of tools enables improvements in service quality. Tools may be provided using one unambiguous authoritative data model, which eliminates data inconsistencies between sources. With the invention, updates to service delivery clients may be delivered more quickly. The invention also reduces costs for developing, deploying, and maintaining a tightly integrated service delivery client. Integration may be provided from the bottom up rather than after the fact.

Abstract: An incompatible software level of an information technology infrastructure component is determined by comparing collected inventory information to a minimum recommended software level. If a knowledge base search finds that the incompatible software level is associated with a prior infrastructure outage event, an outage count score is determined for the incompatible software level by applying an outage rule to a historic count of outages caused by a similar incompatible software level, and combined with an average outage severity score assigned to the incompatible software level based on a level of severity of an actual historic failure of the component within a context of the infrastructure to generate a normalized historical affinity risk score. The normalized historical affinity risk score is provided for prioritizing the correction of the incompatible software level in the context of other normalized historical risk level scores of other determined incompatible software levels.

Abstract: A method and associated systems for backing up a target computer application that comprises identifying and backing up databases and other information repositories upon which the target application depends. The target application is identified and related to a backup requirement that specifies a minimum application-backup frequency. The application's “dependencies” are automatically identified from sources that include configuration files, where each dependency identifies one or more databases or other information repositories that store information upon which the application directly or indirectly depends. If any of these databases or repositories is associated with a backup frequency less than the application's minimum backup frequency, the database or repository is flagged. Each flagged entity's backup schedule is then revised so that the flagged entity's backup frequency is equal to or greater than the application's minimum backup frequency.

Abstract: A method, computer program product, and system for managing tasks for a virtual machine are presented. An amount of resources to perform a task for the virtual machine are identified in response to receiving a request to perform the task for the virtual machine in a set of data processing systems. A set of resources in the set of data processing systems available to complete the task for the virtual machine are identified. A set of priorities for a set of phases of the task are identified. Operations are scheduled on the set of resources to perform the task for the virtual machine based on the set of priorities identified for the set of phases of the task.

Abstract: An incompatible software level of an information technology infrastructure component is determined by comparing collected inventory information to a minimum recommended software level. If a knowledge base search finds that the incompatible software level is associated with a prior infrastructure outage event, an outage count score is determined for the incompatible software level by applying an outage rule to a historic count of outages caused by a similar incompatible software level, and combined with an average outage severity score assigned to the incompatible software level based on a level of severity of an actual historic failure of the component within a context of the infrastructure to generate a normalized historical affinity risk score. The normalized historical affinity risk score is provided for prioritizing the correction of the incompatible software level in the context of other normalized historical risk level scores of other determined incompatible software levels.

Abstract: A method, data processing system, and computer program product for managing images. A processor unit divides an image for a virtual machine into blocks. The processor unit determines whether to compress the blocks prior to transmitting the blocks to a destination for the image. In response to a determination to compress the blocks, the processor unit compresses the blocks to form a compressed set of blocks. The processor unit sends the compressed set of blocks and any uncompressed blocks remaining in the blocks to the destination for the image.

Abstract: A method, data processing system, and computer program product for managing images. A processor unit divides an image for a virtual machine into blocks. The processor unit determines whether to compress the blocks prior to transmitting the blocks to a destination for the image. In response to a determination to compress the blocks, the processor unit compresses the blocks to form a compressed set of blocks. The processor unit sends the compressed set of blocks and any uncompressed blocks remaining in the blocks to the destination for the image.

Abstract: A method, computer program product, and system for managing tasks for a virtual machine are presented. An amount of resources to perform a task for the virtual machine are identified in response to receiving a request to perform the task for the virtual machine in a set of data processing systems. A set of resources in the set of data processing systems available to complete the task for the virtual machine are identified. A set of priorities for a set of phases of the task are identified. Operations are scheduled on the set of resources to perform the task for the virtual machine based on the set of priorities identified for the set of phases of the task.

Abstract: Some demonstrative embodiments of the invention include, for example, devices, systems and methods of operating one or more virtual logical sites. A method may include, for example, running on a server at least one first virtual machine implementing at least part of a first virtual logical site, and at least one second virtual machine implementing at least part of a second virtual logical site interchangeable with the first virtual logical site. Other embodiments are described and claimed.

Abstract: The invention enables server administrators (SAs) to improve their productivity and performance. With the methods and systems described herein, the prior art needed to search for appropriate tools for appropriate tasks is minimized and/or eliminated. Easier scripting and automation that does not require implementation across tools is provided. A consistent logical place is provided for all resources to be used. Standardization of tools enables improvements in service quality. Tools may be provided using one unambiguous authoritative data model, which eliminates data inconsistencies between sources. With the invention, updates to service delivery clients may be delivered more quickly. The invention also reduces costs for developing, deploying, and maintaining a tightly integrated service delivery client. Integration may be provided from the bottom up rather than after the fact.

Abstract: Disclosed are methods and systems for performing a change-over to one or more components of a computing system. As part of a change-over procedure to one or more system components (i.e. software routines) of a production computing system, a clone of one or more production system components of the production computing system may be generated on the same computing platform as the production computing system component is running. According to some embodiments of the present invention, “virtualization” is one technique which may be used to generate and maintain a clone system component or virtual machine.