Discovery, consolidation, and archival of multiple operating system software licenses

A server software repair method. The method comprises copying a software license file associated with a software deployment, saving the software license file to a discrete directory, repeating these steps at predetermined intervals to form an archive. The method further comprises retrieving the software license file from the archive and redeploying the software license file with a software deployment.

CROSS-REFERENCE TO RELATED APPLICATIONS

Not applicable.

REFERENCE TO A MICROFICHE APPENDIX

Not applicable.

BACKGROUND

Maintenance, upgrade, and replacement of servers and other computer network components may result in the loss of the software licenses to continue using various software programs. Also, inventorying and correlating the number of software deployments across multiple servers may result in a loss of association between a particular program and the license for its use. These losses represent a financial liability as licenses need to be repurchased from a vendor or as penalties may be owed to the vendor for unauthorized use of the software.

SUMMARY

In an embodiment, a server software repair method is disclosed. The method comprises copying a software license file associated with a software deployment and saving the software license file to a discrete directory. The method further comprises repeating the steps of copying the software license file and saving the software license file to the discrete directory at predetermined intervals to form an archive. The method further comprises retrieving the software license file from the archive and redeploying the software license file with a software deployment.

In an embodiment, a license file discovery and archive device for a server system is disclosed. The system comprises a processor, and a memory having an application stored there that is executed by the processor. When executed the processor identifies vendor-specific server software files on a server system, locates vendor-specific software license files on each server of the server system, copies the vendor-specific software license files, saves the vendor-specific software license files to a common location and repeats the previous steps at intervals to form an archive.

In an embodiment, a server software license archiving method is disclosed. The method comprises identifying server software license files, locating the software license files on a server, copying the software license files, and saving the software license files to a common directory. Additionally, the archiving method is repeatable for plurality of license files and at different intervals in order to form an archive.

A server system software license management method comprises identifying license file markers for software deployed on a server system, locating files containing the license file markers, copying the identified license files and any file associated therewith, and saving all the copied files to a common location. Also, the license management system comprises repeating the steps at predetermined intervals to form an archive and accessing the archive to restore a license file and associated files to at least one server in the server system.

DETAILED DESCRIPTION

Broadly, computer and communications networks comprise a series of servers configured for continuous hosting and sharing of computer processing power to facilitate transmitting data among users. The servers contain various software packages that are installed and then activated or deployed to control the function of the server. Exemplary functions include a database server, a file server, a mail or electronic-mail server, a print server, a web or Internet server, a gaming server, a telecommunications server, or any other server, without limitations. Generally, the software functionality is dependent on an authorization, hereinafter a license, from the software vendor to the server operator or provider. In certain applications, the software vendors may require an electronic file version of the license to be stored on the server for deployment and use of that software package.

However, servers are designed for modular installation and removal in order to quickly adjust to user demand, as well as for maintenance, repair, and replacement. These processes likely involve the removal and reinstallation of software packages on a server, including the associated license file. Also, due to various events, there is potential for the removal of a software package or deployment from one server and redeployment of that software package on a new server. As the number of servers and software deployments change, the number of associate license files may likewise change. Also the license file may be corrupted, altered, or lost during these operations. The loss of a license or the net reduction in licenses compared to software deployments on servers is a liability to the operator. Purchasing surplus licenses is an unfavorable expense for a provider, but unlicensed software deployments may result in the provider owing the vendor a penalty for an unlicensed deployment or a new license. Additionally, the vendors may audit an operator's software licenses to verify that all the deployments are licensed if the vendor feels that the operator is not demonstrating sufficient care in tracking the licenses. Generally, a vendor will not penalize a provider if the provider retains possession of the license that is recovered from a corrupted, altered, or lost deployment of the vendor's software package, even if the provider cannot redeploy the software and the license. Thus, for an operator it may be financially advantageous to be able to identify, locate, preserve and track the inventory of software licenses, including those that are partially damaged in order to avoid additional vendor derived costs and penalties.

It is understood that vendors have unique text, codes, or scripts that they use within their software and license files. Generally, the software vendors or their agents will assist an operator in installing their software but, in order to streamline this process the vendors may install several packages. Deployment of the selected packages is dependent on the presence of the license. Thus, the software includes an instruction or command, that when executed by a computer processor accesses the license to verify the packages are authorized for operation or deployment. Further, the license files may include text, executable algorithms, or encryption keys that may be stored in binary form in the file or in other associated files. The present disclosure teaches a device and method for discovering and archiving the license files by identifying license files, locating the software license files, copying or relocating the license files to a common location, copying the files at regular intervals and forming an archive or history log of the software installation associated with each license.

For example, a discovery and archiving device consists of a discovery engine and an archiving engine. The discovery engine has components for identifying license markers, locating license files based on the license markers, and copying the license files. The archiving engine has components for saving the copied license files to a common library, logging information about the copied license files in the library, and tracking the changes in the saved license files and the logged information. In some configurations, the archiving engine may include a re-activation component configured to activate the discovery engine at prescribed intervals and thereby produce an archive. Alternatively, the engines of the discovery and archiving device are implemented as a processor executing software. More specifically, a device comprises software modules that consist of a command stored on a memory and when executed by a processor transforms the modules into the engines for carrying out a discovery and archiving method.

For example, identifying the specific text, codes, or scripts facilitates locating the license files as installed on the server. Identifying the license files by the unique text, codes, scripts, any executable commands or files therein as license markers of a software deployment. These license markers may be utilized to conduct a directory and registry search to locate the license files and any additional files that are associated with the license files. The associated files comprising the encryption keys or binary information may be separate from the license file itself or stored. For example, once the license files for all the vendors are located, the license files are copied to a common directory on a separate server to permit the operator to preserve the license if the software package or the server fail or are otherwise lost. It is understood that data regarding the software package, the deployment, the location of the license and the server it was located on may comprise a portion of the information that is copied to the new directory.

In another example, copying the license files from the respective servers to a common directory, initiates archiving the licenses. Archiving the licenses comprises saving the copied license files to the common directory at predetermined or prescribed intervals. Also, the data regarding the software package, the deployment, and the location of the license is concurrently saved to the new directory and stored in its own file to create an archive log. The archive log includes time/date stamps and other relevant data in order to timeline or otherwise accurately account for the duration of a software deployment and its association with a given license. The archiving of the licenses facilitates archive analysis, such that information regarding the software package, the deployment, the license, the location of the license, and other associated data may be recalled for license recovery or restoration.

Referring now toFIG. 1, a discovery and archive system100is illustrated. The system100comprises a server network102. The server network102comprises a plurality of physical computers104dedicated to providing one or more services to users by running one or more vendor-provided software packages. Also, the server network102comprises an operator computer106for controlling the physical computers104and operation thereof. A discovery and archiving device110is in communication with the server network102, including physical computers104and operator computer106. The discovery and archiving device110comprises a discovery engine120and an archiving engine130. The discovery engine120comprises a marker identifying component122for identifying unique indicators of at least one software license. The discovery engine120also comprises a marker locating component124for locating the identified license markers installed on server network102. Further, the discovery engine120comprises a license-file copying component126. The license-file copying component126produces a copy of the server network located license-files.

The archiving engine130further processes the copy of the server network located files in communication with the discovery engine120and the server network102. The archiving engine130comprises a license-file recording component132for relocating and saving the copied license files. In certain configurations, the license-file recording component132records the license-file copies onto the operator computer106via the server network102. The data-logging component134takes data relevant to the located and copied license-files, and likewise records the data to the operator computer106via the server network. Without limitation, the data-logging component134records data in a file and associates the file with the copied license-files. The data-logging component134records data into a file regarding the date, the time, the version or installation of the software package, the number of deployments, the number of licenses, the number of license-files with each license, the version and other information relevant to the deployment and operation of a software package, without limitation. The archiving component136manages the copied and stored license-files based on the data-logged information to form an operator accessible archive, including a log of changes associated with each license-file. The archiving component136upon creating the archive is also configurable to locate a specific license and the data-logged information based on operator determination or differential conditions. In some configurations, the archiving component136may include a reactivation component configured to activate the discovery engine at prescribed intervals.

Referring now toFIG. 2there is illustrated a discovery archiving system200wherein the engines of the discovery and archiving device are implemented as a computer system having a processor executing software. More specifically, a device comprises software modules that consist of a command stored on a non-transitory memory and when executed by a processor transforms the modules into the engines for carrying out a discovery and archiving method. For example, the discovery and archiving system200may be implemented as processor208executing software modules in communication with the server network202. The discovery and archiving device210comprises the operator computer206in communication with or comprising a non-transitory computer-readable memory211, having the software modules located thereon. The non-transitory computer-readable memory211comprises the discovery module220, the archiving module230, and the license-file archive240. The discovery engine120illustrated inFIG. 1corresponds with the discovery module220inFIG. 2. Thus, every engine component122-126corresponds directly with a module program222-226. Likewise, the archiving engine130illustrated inFIG. 1corresponds with the archiving module230inFIG. 2. Thus, every engine component132-136corresponds directly with a module program232-236. The license-file archive240is configurable and operable as a database for sequentially storing the license-files and the data-logs for the operation of the discovery and archiving system200and the operator computer206. Additionally, the license-file archive240may be analyzed, and selectively manipulated, for example by the archiving module230, any program232-236therein, or by an operator access to the operator computer206, in conjunction with instructions executable by the processor208. Further exemplary systems, computers, devices, and the operation thereof according to the present disclosure, will be described hereinbelow.

Referring now toFIG. 3, there is illustrated a discovering and archiving method300configurable for discovering and archiving software licenses on a server network. Generally, the discovering and archiving method300relates to the sequential combination of discrete two method components: license discovering320and license archiving330. Also, each method component of the discovering and archiving method300may be executed a plurality of times, either sequentially or in parallel. The license discovering320may be operated independently for example to identify and locate a license or licenses on a server system, including lost or corrupted licenses. The license discovering320comprises the steps of identifying license markers322, locating the license markers324, and copying the license files326. The license archiving330may be operated independently for example to archive a known license, including inactive or decommissioned licenses. The license archiving330comprises the steps of storing a license file332, logging license data334, and archiving the license and data336. In combination, license discovery320provides the license archiving330the licenses and associated files to facilitate the construction of an archive thereof, as well as the continued updating, maintenance, and management thereof.

The license discovering320is a method to identify licenses by vendor-specific markers, locate the licenses and all associate files by the vendor-specific markers, and to create a copy of the licenses and all associated files. Identifying license markers322comprises analyzing the operation of a vendor's software and the software's means of accessing the license information during deployment, for example on a server network. Identifying license markers322may comprise determining the vendor-specific file type, for example a text file, an executable file, a registry file, an encryption file, or a file querying the binary for information. Identifying the license markers322by determining the vendor-specific file type may comprise specific analysis or “finger printing” of the software packages installed on a server network, to track the file directories accessed during the deployment of a given software program. Also, identifying license markers322comprises finding conserved patterns or conventions in a vendor's licenses, software, filenames, filetypes, executables, coding, and other related information. Identifying license markers322may also comprise identifying markers or other information for the exclusion of unrelated vendor files. In some operations, identifying license markers322comprises identifying a population or plurality of licenses that are correlated to a plurality of software deployments from a single vendor. Identifying license markers322may include assembling a script or other temporary file that identifies the markers in a vendor-specific fashion.

Locating license markers324comprises searching the server directory, registry, and other locations for the licenses, all associated files, and license-specific data based upon the identified markers. As noted previously, the marker may be the file itself or a component thereof. Additionally, locating the license markers324comprises locating the files associated with the vendor-specific licenses, the licenses files, software deployment, general data related to the licenses, and data indicative of the licenses' statuses. As noted herein, it is possible that the locating license markers324comprises finding a first file that contains commands or symbolic links to access a second file. Locating license markers324comprises likewise locating the second file or files. Acknowledging that license files may comprise a text file, an executable file, a registry file, an encryption file, or a file querying the binary for information, it may be necessary to conduct more than one pass to locate license markers324, particularly if that information is in a second file. For example, locating license markers324that were linked to second files such as registry files or binary files, may be located during a second pass through the file directory. In some cases, locating license markers324comprises a search through the operating system directory in order to locate all associated or symbolically-linked files. Still further, locating license markers324may comprise locating multiple installations and multiple deployments of the same software package and the same license. Locating license markers324comprises locating the inactive installations, the active deployments, and the licenses associate with each in a vendor-specific manner. Further, locating the license markers324comprises finding any files with data regarding the software version the license is correlated, the date of installation, the frequency of operation or access, and other general data. More specific data, such as the dates of validity of the license or the dates of operation of the license in conjunction with a software deployment are part of the method of locating license markers324. Thus, locating license markers324comprises finding all the files that are indicative of a license on a server network, a server directory, or finding any files that are linked to the marker containing files, linked to a vendor's software whether active or inactive, contain data related to the software, and contain data indicative of the license's status. Without limitation by theory, locating license markers324comprises locating the license files that are group of the files that are related to a license or are likely related to a license.

Copying license files326is the reproduction of files that contain the identified and located license markers. Further, copying license files326comprises copying the all the file data in the license files and associated files, including the linked files. Copying the license files326may be concurrent with the locating the license markers324. In other instances, copying the license files326may be asynchronous such that registry files and binary files or information may be relocated prior to copying. Further, copying license files326comprises copying data related to or indicative of the license, such as the data regarding the software version the license is correlated with the date of installation, the frequency of operation or access, and indicative of the licenses active/inactive status. Copying license files326may comprise generating a script or temporary file that is operator accessible. Alternatively, copying license files326comprises creating a directory of the copied files that is operator accessible.

The method of license archiving330comprises storing license files332as copied, in a common directory that is on a computer in communication with the server network. Also, license archiving330comprises logging license data334in a vendor-specific manner. Further, archiving license and data336comprises regular compiling the license files and the logged data with the historical information, for example from the common directory, such that a historical determination of each license may be generated.

Storing license files332comprises creating a common directory, for example on an operator server or an operator computer that is in communication with the server network. It may be understood that the operator server or operator computer are not a portion of the server network. Without limitation by theory, storing license files332isolated from the server network may prevent corruption of the stored files by network errors or faults and prevents the accidental deletion, over-writing, re-formatting and other potential means for losing data on a server network. Storing the license files332is conducted at regular intervals, for example daily or weekly. Also, storing the license files332may comprise creating a series of common directories, for example each directory is associated with a vendor specific software package, or a license-specific software deployment.

Logging license data334comprises compiling the vendor-specific and the license-specific data that is associated with the license files. Also, logging license data334comprises creating data files or data logs. The logging license data334may be executed concurrently or asynchronously with respect to storing license files332. Further, logging license data334comprises creating a common directory, for example on an operator server or an operator computer that is in communication with the server network. It may be understood that the operator server or operator computer are not a portion of the server network. Likewise, logging license data334isolated from the server network may prevent corruption of the created data files or data logs by network errors or faults and may prevent the accidental deletion, over-writing, re-formatting and other potential means for losing data on a server network. Logging the license data334is conducted at regular intervals, for example daily or weekly. Also logging license data334may comprise creating a series of common directories, for example each directory is associated with a vendor specific software package, or a license-specific software deployment and the logged data.

Archiving license and data336comprise saving a copy of the common license and data directories at a regular interval in a common directory. Archiving license and data336accordingly provides a plurality of copies of the license files and the data files such that each common directory provides a “snap-shot” or a capture of the status of the server network, deployed software, the associated licenses, and the license data. Alternatively, archiving license and data336comprises compiling the stored licenses and logged data at a regular interval, in a common directory. Archiving license and data336accordingly provides a plurality of files that illustrate the changes of the license files and data files thereby tracking the changes or lack thereof, in the status of the server network, deployed software, the associated licenses, and the license data. Also, archiving the license and data336comprises including time and date information, hereinafter interval data, with each common file. Without limitation by theory, the interval data provides a means to verify the license files and logged data from a historical standpoint or in the instance of the loss of that information from the server network. Archiving the license and data336further comprises saving the license, associated files, and data off the network, for instance in a license-file archive240as illustrated inFIG. 2.

Also, archiving the license and data336comprises an automated initiation of the identifying license markers322. For example, the archiving license and data336may be done at intervals with respect to the storing license files332and the logging license data334. The completion of the archiving license and data336may be configurable to initiate the discovering and archiving method300. Still further, during the archiving license and data336steps, it may be identified that the interval has extended beyond a predetermined point, such that the discovering and archiving300method is needed to update the archives. Alternatively, it may be identified that a license file or logged data is incomplete, corrupted, missing, or otherwise failed to incorporate into the license-file archive. Thus, reinitiating of the discovering and archiving300method provides for an automated license management method.

Referring now toFIG. 4there is illustrated an alternate method for managing licenses400installed on a server network. Generally, managing licenses400comprises discovering and archiving300, including license discovering320and license archiving330as disclosed hereinabove to form and update at license file archive440. Additionally, managing licenses400includes archive retrieving450, network redeploying460, and redeployment verification470. In generally, managing licenses400is utilized for redeploying or re-using an operator owned license. For example, in the case of a server decommissioning, the licenses that were archived from that device may be utilized with software that is installed on a new server. Also, in the instance of a server fault, reset, or other loss of the software installed thereon, the licenses that were archived from that server may be utilized to redeploy any software packages that are reinstalled. Likewise, in the event of a complete loss of software package information and license information, the archive may be retrieved to illustrate to a vendor: the status, version, and deployments of particular licensed software packages. Additionally, managing licenses400may be utilized to inventory the licenses and software deployments for auditing purposes, software upgrades, and other purposes, without limitation.

For example, archive retrieving450comprises accessing the license file archive440and retrieving the archive for a particular license. The license file archive440comprises the common directory including all the files and the associated data for the vendor-specific software package. Additionally, if needed the interval data from copying, storing, and archiving the license data is available. Retrieving the license450archive also provides an operator with information to provide a vendor during the reinstallation of the associated software packages.

Network redeploying460comprises reinstalling or reinserting the archived files into the server directory in order to authorize the software deployment. The archived license files and data logs provide the directory locations, as well as any of the registry locations, the encryption keys, the symbolic links, and the binary files for network redeploying460. Additionally, the data logs provide information regarding the version and the dates installed in order to facilitate the deployment of the correct software packages.

Redeployment verification470comprises verifying that the software accesses the installed archival information as newly installed or reinstalled in the server directory. Additionally, redeployment verification470comprises providing the vendor with the new information regarding the software and the server operation. Still further, the redeployment verification470comprises demonstrating the inventory of valid licenses, the inventory of software installations, the inventory of software-license deployments, and in certain instances, the operator's ability to redeploy the archived license without vendor penalty. Also, redeployment verification470may initiate discovering and archiving300in order to update storing files or archiving files in view of the redeployment of an archived license.

In a further configuration of the license managing400, retrieving the archive450comprises inventorying the licenses. Inventorying the licenses may include determining the number of licenses compared to the number of software installations and the number of software deployments. Additionally, inventorying the licenses by retrieving the archive450comprises determining the status, including expiration dates for the licenses as found in the logged data. In this configuration of license400managing, network redeploying460comprises adding, removing, or changing the software packages based on the logged data in order to avoid vendor penalties. In certain instances, archived licenses may be redeployed while others are decommissioned and removed from usage. Likewise, an archived license version may be upgraded or altered. As described herein, the redeployment verification470comprises verifying that the software accesses the archival licenses as newly installed or reinstalled in the server directory. Additionally, redeployment verification470comprises providing the vendor with the new information regarding the software and the server operation. Still further, the redeployment verification470comprises demonstrating the inventory of valid licenses, the inventory of software installations, the inventory of software-license deployments, and in certain instances, the operator's ability to redeploy the archived license without vendor penalty. Additionally, redeployment verification470may initiate discovering and archiving300in order to update storing or archiving licenses and data logs in view of the decommissioned or redeployed license. Reinitiating discovering and archiving300may provide the operator additional insurance that the most recent information is now recorded off the network, and is accessible by the operator's computer system or operators servers.

FIG. 5illustrates a server-based computer system980suitable for implementing one or more embodiments disclosed herein. The server-based computer system980includes a processor982, which may be referred to as a central processor unit, a computer processor unit, or a CPU. The processor982at is in communication with memory devices including secondary storage984, read only memory (ROM)986, random access memory (RAM)988, input/output (I/O) devices990, and network connectivity devices992. The processor982may be implemented as one or more central processor units or chips.

The secondary storage984is typically comprised of one or more disk drives or tape drives and is used for non-volatile storage of data and as an over-flow data storage device if random access memory988is not large enough to hold all working data. Secondary storage984may be used to store programs which are loaded into random access memory988when such programs are selected for execution. The read only memory986is used to store instructions and perhaps data which are read during program execution. Read only memory986is a non-volatile memory device which typically has a small memory capacity relative to the larger memory capacity of secondary storage984. The random access memory988is used to store volatile data and perhaps to store instructions. Access to both read only memory986and random access memory988is typically faster than to secondary storage984. The secondary storage984, the random access memory988, and/or the read only memory986may be referred to in some contexts as computer readable storage media and/or non-transitory computer readable media.

The network connectivity devices992may take the form of modems, modem banks, Ethernet cards, universal serial bus (USB) interface cards, serial interfaces, token ring cards, fiber distributed data interface (FDDI) cards, wireless local area network (WLAN) cards, radio transceiver cards such as code division multiple access (CDMA), global system for mobile communications (GSM), long-term evolution (LTE), worldwide interoperability for microwave access (WiMAX), and/or other air interface protocol radio transceiver cards, and other well-known network devices. These network connectivity devices992may enable the server-based processor982to communicate with the Internet, one or more intranets, and one or more users. With such a network connection, it is contemplated that the server-based processor982might receive information from the network, or might output information to the network in the course of performing the above-described method steps. Such information, which is often represented as a sequence of instructions to be executed using server-based processor982, may be received from and outputted to the network, for example, in the form of a computer data signal embodied in a carrier wave.

The server-based processor982executes instructions, codes, computer programs, scripts which it accesses from hard disk, floppy disk, optical disk, such that these various disk based systems may all be considered secondary storage984, or read only memory986, random access memory988, or the network connectivity devices992. While only one server-based processor982is shown, multiple server-based processors may be present. Thus, while instructions may be discussed as executed by a processor, the instructions may be executed simultaneously, serially, or otherwise executed by one or multiple processors. Instructions, codes, computer programs, scripts, and/or data that may be accessed from the secondary storage984, for example, hard drives, floppy disks, optical disks, and/or other device, the read only memory986, and/or the random access memory988may be referred to in some contexts as non-transitory instructions and/or non-transitory information.

In an embodiment, the server-based computer system980may comprise two or more computers or servers in communication with each other that collaborate to perform a task. For example, but not by way of limitation, an application may be partitioned in such a way as to permit concurrent and/or parallel processing of the instructions of the application. Alternatively, the data processed by the application may be partitioned in such a way as to permit concurrent and/or parallel processing of different portions of a data set by the two or more computers or servers. In an embodiment, virtualization software may be employed by the server-based computer system980to provide the functionality of a number of servers that is not directly bound to the number of computers in the server-based computer system980. For example, virtualization software may provide twenty virtual servers on four physical computers. In an embodiment, the functionality disclosed above may be provided by executing the application and/or applications in a cloud computing environment. Cloud computing may comprise providing computing services via a network connection using dynamically scalable computing resources. Cloud computing may be supported, at least in part, by virtualization software. A cloud computing environment may be established by an enterprise and/or may be hired on an as-needed basis from a third party provider. Some cloud computing environments may comprise cloud computing resources owned and operated by the provider or another enterprise, as well as cloud computing resources hired and/or leased from a third party provider.

In some contexts, the secondary storage984, the read only memory (ROM)986, and the random access memory (RAM)988may be referred to as a non-transitory computer readable medium or a computer readable storage media. A dynamic RAM embodiment of the RAM988, likewise, may be referred to as a non-transitory computer readable medium in that while the dynamic RAM receives electrical power and is operated in accordance with its design, for example during a period of time during which the computer980is turned on and operational, the dynamic RAM stores information that is written to it. Similarly, the processor982may comprise an internal RAM, an internal ROM, a cache memory, and/or other internal non-transitory storage blocks, sections, or components that may be referred to in some contexts as non-transitory computer readable media or computer readable storage media.