Method and system for tape storage utilization

A method includes detecting, by a computing device, a plurality of transactions on one or more data storage system. The method further includes sequentially recording, by the computing device, the plurality of transactions occurring on the one or more data storage system in sequentially linked and immutable blocks.

BACKGROUND

Aspects of the present invention relate generally to data storage utilization and, more particularly, to a structured arrangement of storage utilization and record keeping of data in storage systems, e.g., server utilization.

In cloud and other storage applications, customer data is stored and retained on servers based on backup policies and agreements with the customer. This data may include pictures, videos, email correspondences and/or other documents. The storage management can be attended through the use of certain management tools, which provide backup and restore services of the data as needed. On the other hand, the storage data can be reported through reporting tools, which reports are provided to the service provider for review to, for example, prepare invoices to the customer.

In cloud and other storage applications, large amounts of data may be stored unnecessarily. For example, hundreds of terabytes of data may be stored even when the server is decommissioned based on a customer request. In such a case, for example, the storage retention does not delete the files along with the decommissioned server due to non-clarity in the decommission request, contractual offerings or due to automatic internal retention maturity policies, etc. In some instances, the backup policy may also be changed per the customer request and the new configuration cannot be adjusted within existing configuration files due to updates in technology or due to the use of unique individual configuration files for such purpose.

In data retention schemes, the service provider can rename existing data files that are to be saved to, e.g., .OLD, and then create a new data file with an existing name. For storage of such .OLD configuration files, the retention of such stored documents may in the gigabytes to terabytes of data. However, the storage reporting tools may not be able to detect such .OLD configuration files. For example, the configuration files may include inactive links, they may have manual scripts that cannot read .OLD configuration files, or there is a missed naming convention, etc.

SUMMARY

In a first aspect of the invention, there is a computer-implemented method including: detecting, by a computing device, a plurality of transactions on one or more data storage system; and sequentially recording, by the computing device, the plurality of transactions occurring on the one or more data storage system in sequentially linked and immutable blocks.

In another aspect of the invention, there is a computer program product including one or more computer readable storage media having program instructions collectively stored on the one or more computer readable storage media. The program instructions are executable to: receive a request to make a transaction associated with data on one or more data storage system; record the request in an immutable block; make a change to the one or more data storage system based on the requested transaction; record the change in a second immutable block that is linked in sequentially to the immutable block; and provide notification of the recorded change to a third party.

In another aspect of the invention, there is system including a processor, a computer readable memory, one or more computer readable storage media, and program instructions collectively stored on the one or more computer readable storage media. The program instructions are executable to: record changes in immutable, sequentially linked blocks associated with a plurality of data storage systems, each of the immutable, sequentially linked blocks include a single transaction that is to take place on the plurality of data storage systems in a sequence in which they take place and are requested; and provide notification of the recorded change including freed up resources on the on the plurality of data storage systems due to the changes.

DETAILED DESCRIPTION

Aspects of the present invention relate generally to data storage utilization and, more particularly, to a structured arrangement of storage utilization and record keeping of data in storage systems, e.g., server utilization. According to more specific aspects of the invention, the method and system described herein facilitate a structured arrangement of all storage utilization, record keeping, and invoicing of the customer for storage utilization using, for example, a smart contract with available storage and configurable items in place. In this manner, implementations of the invention provide an efficient manner of maintaining and tracking of data which is to be stored, even when there are changes to backup policies, customer contacts and/or requests, and/or decommissioning of servers, etc.

In aspects of the present invention, untagged documents that remain in storage can be maintained and tracked even when a server is decommissioned, backup policy changes, and/or changes have been made to nomenclatures of the stored documents, e.g., configuration files. For example, in an aspect of the present invention, the method and system detect when a storage block (e.g., file, data base, log, etc.) is uncoupled due to a full name change as MACD changes are carried out, a copy of the data is made for a backout, or a data block is renamed such that the tag that earlier enabled these to be counted and charged goes with the new copy. In this way, the method and system identify gaps in record keeping in order to ensure all data is properly maintained on the servers, its location is known and the storage space is efficiently utilized.

In aspects of the present invention, the method and system may be implemented as computer program products, computer systems and/or computing devices which provide a technical solution to a problem by automatically addressing storage utilization on servers within a cloud environment. The computer program products, computer systems and/or computing devices have broad applications in maintaining efficiency of storage usage amongst one or more servers. This technical solution can be accomplished through the use of, amongst other features as described herein, blockchain technologies. Specifically, to efficiently manage storage space, specific aspects of the present invention use blockchain technologies to record any changes to storage utilization, and through, e.g., a smart contract, validate or post a time window for automated authorized removal and invoicing to a customer. Accordingly, it is now possible to use the blockchain technologies to record transactions that have occurred on one or more servers.

By way of non-limiting illustration, when a new resource is used or block requested, the blockchain technology is triggered to provide storage resources to enforce a transaction, i.e., maintain records of the transaction. These transactions may include, for example, reallocation of storage resources, deletion of data in storage, renaming of configuration files, etc. Accordingly, by use of the blockchain technology, it is possible to have a centralized authority for maintaining and tracking storage volume on one or more servers, including recording changes of data retention and data deletion due to decommissioning of servers, changes in retention policies, backup policies, etc. Also, the blockchain technology implemented herein provides storage information to different users, including a developer, tester, production team, or other third parties that are using the storage. Also, the blockchain technology enforces discipline that is lacking in resource blocking, maintains proper ownership in data retention, and uses and releases storage resources that need not be held in the data storage systems, e.g., servers. This allows on demand storage usage by freeing up resources that would otherwise be improperly utilized.

The method and system further include a push reporting mechanism for the utilized storage. For example, the push reporting mechanism provides notices to a service provider, indicating amongst other things, low value storage by users, storage utilization, changes to policies, etc. In addition, the smart contracts are defined to enable automated authorized deletion to free space based on different trade-offs. Moreover, the smart contracts include a bid mechanism which can free storage blocks at both high cost and low cost ends and leverage on-demand needs.

It should be understood that, to the extent implementations of the invention collect, store, or employ personal information provided by, or obtained from, individuals, such information shall be used in accordance with all applicable laws concerning protection of personal information. Additionally, the collection, storage, and use of such information may be subject to consent of the individual to such activity, for example, through “opt-in” or “opt-out” processes as may be appropriate for the situation and type of information. Storage and use of personal information may be in an appropriately secure manner reflective of the type of information, for example, through various encryption and anonymization techniques for particularly sensitive information.

Characteristics are as follows:

Service Models are as follows:

Deployment Models are as follows:

Referring now to FIG. 1, a schematic of an example of a cloud computing node is shown. Cloud computing node 10 is only one example of a suitable cloud computing node and is not intended to suggest any limitation as to the scope of use or functionality of embodiments of the invention described herein. Regardless, cloud computing node 10 is capable of being implemented and/or performing any of the functionality set forth hereinabove.

As shown in FIG. 1, computer system/server 12 in cloud computing node 10 is shown in the form of a general-purpose computing device. The components of computer system/server 12 may include, but are not limited to, one or more processors or processing units 16, a system memory 28, and a bus 18 that couples various system components including system memory 28 to processor 16.

Computer system/server 12 typically includes a variety of computer system readable media. Such media may be any available media that is accessible by computer system/server 12, and it includes both volatile and non-volatile media, removable and non-removable media.

Program/utility 40, having a set (at least one) of program modules 42, may be stored in memory 28 by way of example, and not limitation, as well as an operating system, one or more application programs, other program modules, and program data. Each of the operating system, one or more application programs, other program modules, and program data or some combination thereof, may include an implementation of a networking environment. Program modules 42 generally carry out the functions and/or methodologies of embodiments of the invention as described herein.

Computer system/server 12 may also communicate with one or more external devices 14 such as a keyboard, a pointing device, a display 24, etc.; one or more devices that enable a user to interact with computer system/server 12; and/or any devices (e.g., network card, modem, etc.) that enable computer system/server 12 to communicate with one or more other computing devices. Such communication can occur via Input/Output (I/O) interfaces 22. Still yet, computer system/server 12 can communicate with one or more networks such as a local area network (LAN), a general wide area network (WAN), and/or a public network (e.g., the Internet) via network adapter 20. As depicted, network adapter 20 communicates with the other components of computer system/server 12 via bus 18. It should be understood that although not shown, other hardware and/or software components could be used in conjunction with computer system/server 12. Examples, include, but are not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data archival storage systems, etc.

Referring now to FIG. 2, illustrative cloud computing environment 50 is depicted. As shown, cloud computing environment 50 includes one or more cloud computing nodes 10 with which local computing devices used by cloud consumers, such as, for example, personal digital assistant (PDA) or cellular telephone 54A, desktop computer 54B, laptop computer 54C, and/or automobile computer system 54N may communicate. Nodes 10 may communicate with one another. They may be grouped (not shown) physically or virtually, in one or more networks, such as Private, Community, Public, or Hybrid clouds as described hereinabove, or a combination thereof. This allows cloud computing environment 50 to offer infrastructure, platforms and/or software as services for which a cloud consumer does not need to maintain resources on a local computing device. It is understood that the types of computing devices 54A-N shown in FIG. 2 are intended to be illustrative only and that computing nodes 10 and cloud computing environment 50 can communicate with any type of computerized device over any type of network and/or network addressable connection (e.g., using a web browser).

Referring now to FIG. 3, a set of functional abstraction layers provided by cloud computing environment 50 (FIG. 2) is shown. It should be understood in advance that the components, layers, and functions shown in FIG. 3 are intended to be illustrative only and embodiments of the invention are not limited thereto. As depicted, the following layers and corresponding functions are provided:

Hardware and software layer 60 includes hardware and software components. Examples of hardware components include: mainframes 61; RISC (Reduced Instruction Set Computer) architecture based servers 62; servers 63; blade servers 64; storage devices 65; and networks and networking components 66. In some embodiments, software components include network application server software 67 and database software 68.

Virtualization layer 70 provides an abstraction layer from which the following examples of virtual entities may be provided: virtual servers 71; virtual storage 72; virtual networks 73, including virtual private networks; virtual applications and operating systems 74; and virtual clients 75.

In one example, management layer 80 may provide the functions described below. Resource provisioning 81 provides dynamic procurement of computing resources and other resources that are utilized to perform tasks within the cloud computing environment. Metering and Pricing 82 provide cost tracking as resources are utilized within the cloud computing environment, and billing or invoicing for consumption of these resources. In one example, these resources may include application software licenses. Security provides identity verification for cloud consumers and tasks, as well as protection for data and other resources. User portal 83 provides access to the cloud computing environment for consumers and system administrators. Service level management 84 provides cloud computing resource allocation and management such that required service levels are met. Service Level Agreement (SLA) planning and fulfillment 85 provide pre-arrangement for, and procurement of, cloud computing resources for which a future requirement is anticipated in accordance with an SLA.

Workloads layer 90 provides examples of functionality for which the cloud computing environment may be utilized. Examples of workloads and functions which may be provided from this layer include: mapping and navigation 91; software development and lifecycle management 92; virtual classroom education delivery 93; data analytics processing 94; transaction processing 95; and recording and maintaining data storage information 96.

Implementations of the invention may include a computer system/server 12 of FIG. 1 in which one or more of the program modules 42 are configured to perform (or cause the computer system/server 12 to perform) one of more functions of the recording and maintaining data storage information 96 of FIG. 3. For example, the one or more of the program modules 42 may be configured to:

FIG. 4 shows a block diagram of an exemplary environment in accordance with aspects of the invention. In embodiments, the environment includes a plurality of diverse platforms (e.g., servers) 400, a blockchain module 405 and data center storage 410. In embodiments, the plurality of diverse servers 400 may include, e.g., development servers, test severs, production servers, internal or external servers, social media servers, etc., each of which store their data on a database, e.g., within the datacenter storage 410. In embodiments, the data center storage 410 may be a third party service provider which services one or more data storage systems, e.g., databases storing any type of data from the servers. For example, the data stored on one or more data storage systems may include pictures, texts, website content, social media content, music, videos, emails, program applications, etc.

The blockchain module 405 is a solution based around smart contracts with available storage and configurable items in place. In embodiments, the blockchain module 405 is configurable for use with any platform that is utilizing storage, e.g., plurality of diverse servers 400 and data center storage 410. The blockchain module 405 is preferably administered by the third party service provider, which may be the same or different than the third party service provider servicing the data center storage 410. The blockchain module 405 comprises one or more program modules such as program modules 42 described with respect to FIG. 1. The blockchain module 405 includes additional or fewer modules than those shown in FIG. 4. In embodiments, separate modules may be integrated into a single module. Additionally, or alternatively, a single module may be implemented as multiple modules. Moreover, the quantity of devices and/or networks in the environment is not limited to what is shown in FIG. 4. In practice, the environment may include additional devices and/or networks; fewer devices and/or networks; different devices and/or networks; or differently arranged devices and/or networks than illustrated in FIG. 4.

In embodiments, the blockchain module 405 collects information of any transaction occurring on the data center storage 410 together in groups, known as “blocks”. The blocks, when filled, are closed and linked to the previously filled block, forming a chain of data in chronological order. The blocks thus hold batches of valid transactions that are hashed and encoded, with each block including a cryptographic hash of the prior block in the blockchain, linking the two. The linked blocks form a chain. This iterative process confirms the integrity of the previous block, all the way back to the initial block. All new information that follows the previously added block is compiled into a newly formed block that is added to the chain, akin to ledger entries. In this way, the blockchain module 405 uses a data structure that inherently makes an irreversible timeline of data of all transaction when implemented in a centralized nature, and allows information to be recorded and distributed, but not edited. That is, when a block is filled with a particular transaction, e.g., related to the data storage, it is set and becomes immutable. In this way, the records of transactions cannot be altered, deleted, or destroyed. Also, each block in the chain is given an exact timestamp when it is added to the chain, which are linked together via cryptography.

Still referring to FIG. 4, the blockchain module 405 is a distributed database shared among the nodes of a computer network such as the data center storage 410 and plurality of diverse servers 400. The blockchain module 405 stores information electronically in digital format, while maintaining a secure and centralized record of transactions. The information includes, amongst others, any transaction that occurs in the data center storage 410 or requests by the plurality of diverse servers 400 which may affect data stored in the data center storage 410, regardless of the backup tools, types of diverse servers 400 or databases within the data center storage 410, or other technologies.

More specifically, the information recorded by the blockchain module 405 may include any changes to storage utilization, for example, but not limited to:

Accordingly, the blockchain module 405 records all transactions that occur between the data center storage 410 and plurality of diverse servers 400, any changes made to data in the data center storage 410 or any changes to contractual obligations made by any party related to data storage in the data center storage 410. This, in and of itself, will optimize resources by knowing what data is to be retained and what data is to be deleted, and any changes that are made to any of the obligations of the parties as it relates to the data.

Moreover, the blockchain module 405 provides storage information to different users, e.g., the plurality of diverse servers 400 including a developer, tester, production team, or others that are using the storage. This feature provides transparency of all storage transactions and utilization to all of the stakeholders. In addition, the blockchain module 405 provides common storage record keeping, in addition to providing uniform record keeping for internal and external usage purposes. In this way, the blockchain module 405 provides improved storage volume reporting with more accuracy for invoicing, which is updated regularly (e.g., in real-time) and consistently for audit purposes or other reasons. Also, the blockchain module 405 identifies gaps in record keeping in order to ensure all data is properly maintained on the servers, its location is known and the storage space is optimally utilized.

In further embodiments, the blockchain module 405 provides, e.g., publishes, smart contracts to any of the plurality of diverse servers 400. The smart contract is an offer for sale, providing a detailed listing and cost structure of any available resources in the data center storage 410. The smart contract also allows for a bidding process between any of the users of the plurality of diverse servers 400 and the service provider of the data center storage 410 as it relates to data storage, retention, backup policies, etc., based on the above recorded transactions by the blockchain module 405. More specifically, the available resources are provided by the blockchain module 405 as this module knows the available resources and ownership of data in the data center storage 410.

The smart contact can be partially or fully executed (and enforced) without human interaction using the recorded information provided by the blockchain module 405. The smart contract is also recorded in the blockchain module 405, available to any third party. The third party reviews the contract and selects, revises or bids for certain provisions which they desire to enter into with the data center storage 410. These provisions include, amongst other features, retention policies, data storage volume, recording activities, billing activities, time period of contact, etc. Once entered into, the smart contact is recorded in the blockchain module 405, which now knows what additional resources, etc., are being utilized, who owns the resources, e.g., data used in the data center storage 410, and what additional resources remain available. This additional information can be used to update, in real-time, the smart contact, as well as be used to service the data center storage 410 (e.g., decommission servers, backup data, retention policies, etc.) based on the contact provisions.

FIG. 5 shows a flowchart of an exemplary method in accordance with aspects of the present invention. The steps of the method may be carried out in the environment of FIG. 1 and are described with reference to elements depicted in FIG. 4. At step 505, the system receives a request to make a change in the data storage system. This change may be from one or more of the diverse servers 400. The request includes, for example, removal of data, a contractual change in any data retention policy, a backup of data, etc. At step 510, the request is recorded in the blockchain module 405. At step 515, the specified change is made in the data storage system. At step 520, any changes to the data storage system are recorded by the blockchain module 405. It should be understood by those of skill in the art that at step 505, the change can be initiated and made by the data storage system, which would be recorded directly at step 515. These changes can be renaming of files, deletion of files, decommissioning of servers, etc. It should further be understood that any of the recorded changes can be used to automatically generate a smart contact which includes any of the updated resources as already described herein. Also, any of the changes can be pushed through a reporting mechanism to provide notices from or to a service provider, indicating amongst other things, low value storage by users, storage utilization, changes to policies, etc.