Method and system for restoring historic data of an enterprise

The present disclosure discloses method and data restoration system for restoring historic data of an enterprise. The data restoration system receives a request from a user through a transformation backup server, for restoring historic data from a legacy storage device of a plurality of legacy storage devices, associated with an enterprise, along with metadata associated with the historic data. The metadata is previously extracted and stored in a format recognizable by the transformation backup server. The data restoration system determines format of the historic data based on the metadata and extracts historic data from the legacy storage device, using at least one of the metadata and a predefined execution process associated with the historic data, based on the format of the historic data. Thereafter, extracted historic data is restored to the user. The present disclosure recovers legacy data as when required without large migration or any data conversion.

TECHNICAL FIELD

The present subject matter is related in general to the field of data recovery, more particularly, but not exclusively to method and system for restoring historic data of an enterprise.

BACKGROUND

Today, data is a major aspect in every industry. Storage medias and file formats are of vital importance to store and organize various kinds of data in an effective and efficient manner. Generally, enterprises retain backup data for long term such as, 7 years to 14 years for legal and compliance requirements of business. As data grows, it is archived in to low cost tapes or the storage medias and a copy is retained outside data centres for protection. While the data is retained for several years, technology used for protecting them becomes obsolete which leads to recovery issues. While the technology refresh is a part of any strategic planning, but with the fast-growing technology trends, refresh requirement becomes more frequent.

Today, transformation programs within information technology takes care of technology refresh for future backups, still the information technology would need to retain part of a legacy infrastructure for historical data recovery. This is currently a big challenge, especially for very long-term retention severs. Generally, retaining the legacy infrastructure leads to increase in operational cost and unsupported platform, which always has risks of recovery failures and in turn data loss. There are some existing recovery approaches, which are time consuming, require investment for new system and for upfront data migration to new target media and hence require higher efforts and cost to run it as a migration project. Furthermore, in any backup environment, it is important for backup server to know what it has backed up such as client, media ID, data format, date and time, file attributes, retention details, backup type, linkage to last dependent backup and the like. All these data are stored as metadata in every backup server. To enable recovery from latest backup product, it is important to import meta data from legacy backup environment in a readable format. However, latest backup server does not understand the format of metadata and data written to legacy media by legacy backup system. Some of the media could be multiplexed or written in a special format or encrypted which only that legacy backup server understands.

Currently, dual set of backup infrastructure are maintained in enterprises to address legacy data restoration requests and to address the current and future backup requirements of faster and efficient backup through latest technology. In such systems, legacy backup infrastructure is to be retained till the retention period of last data set. However, such systems result in unsuccessful recoveries at certain time due to old infrastructure. Also, data centre space, cooling and power costs would continue due to parallel set-up. Also, in certain situations, dual set of skilled resource needs be retained which increases work force cost under system maintenance. Further, extended warranty of software and hardware products involved in the legacy backup infrastructure would be required, which would otherwise lead to huge risk of unsupported platform protecting backup data. Moreover, historic data itself can be migrated to new infrastructure upfront. However, end users in such cases have no visibility of what data is retained in legacy setup and hence all requests are manual. Also, it would be a big transformation project by itself depending upon data size, which requires an additional capital investment. Further, few existing technologies includes tools to migrate backed up data from one platform to another. These migrations have challenges in migrating encrypted data and success rate is less. Moreover, once data is attempted to be migrated, integrity of data is not retained as these tools may change format of data from one vender to another. Also, migration requires huge staging storage. In addition, if migration fails, there are chances that the data would be lost forever. Hence, there is a need for an improved system and method for data restore.

SUMMARY

In an embodiment, the present disclosure may relate to a method for restoring historic data of an enterprise. The method comprises receiving a request from a user through a transformation backup server, for restoring historic data from a legacy storage device of a plurality of legacy storage devices, associated with an enterprise, along with metadata associated with the historic data. The metadata is previously extracted and stored in a format recognizable by the transformation backup server. The method comprises determining format of the historic data based on the metadata, extracting the historic data from the legacy storage device, using at least one of the metadata and a predefined execution process associated with the historic data, based on the format of the historic data, and restoring the extracted historic data to the user.

In an embodiment, the present disclosure may relate to a data restoration system for restoring historic data of an enterprise. The data restoration system may comprise a processor and a memory communicatively coupled to the processor, where the memory stores processor executable instructions, which, on execution, may cause the data restoration system to receive a request from a user through a transformation backup server, for restoring historic data from a legacy storage device of a plurality of legacy storage devices, associated with an enterprise, along with metadata associated with the historic data. The metadata is previously extracted and stored in a format recognizable by the transformation backup server. The data restoration system determines format of the historic data based on the metadata, extracts the historic data from the legacy storage device, using at least one of the metadata and a predefined execution process associated with the historic data, based on the format of the historic data, and restores the extracted historic data to the user.

In an embodiment, the present disclosure relates to a non-transitory computer readable medium including instructions stored thereon that when processed by at least one processor may cause a data restoration system to receive a request from a user through a transformation backup server, for restoring historic data from a legacy storage device of a plurality of legacy storage devices, associated with an enterprise, along with metadata associated with the historic data. The metadata is previously extracted and stored in a format recognizable by the transformation backup server. The instructions may cause the processor to determine format of the historic data based on the metadata, extract the historic data from the legacy storage device, using at least one of the metadata and a predefined execution process associated with the historic data, based on the format of the historic data, and restore the extracted historic data to the user.

DETAILED DESCRIPTION

The present disclosure relates to a method and a data restoration system for restoring historic data of an enterprise. In an embodiment, historic data may refer to data associated with the enterprise, which is stored in an old or obsolete format or a system that is, therefore, difficult to access or process. The data restoration system may accept request from a user for restoring historic data associated with the enterprise, along with associated metadata, from a legacy storage device. The historic data may be extracted from the requested legacy storage device using the metadata and a predefined execution process associated with the historic data, based on a format of the historic data. The format of the historic data may be determined to be one of encrypted and standard format. The historic data extracted from the legacy storage device may be restored to the user. In an embodiment, the data restoration system may extract the metadata previously from a legacy backup server associated with the enterprise and store in a format which may be recognized by the transformation backup server. The present disclosure recovers legacy data as when required without large migration or any data conversion.

FIG. 1illustrates an exemplary environment for restoring historic data of an enterprise in accordance with some embodiments of the present disclosure.

As shown inFIG. 1, the environment100comprises a data restoration system101connected through a communication network109to a legacy storage device1071, a legacy storage device1072, and a legacy storage device107N(Collectively referred as plurality of legacy storage devices107) and a legacy backup server108associated with an enterprise. In an embodiment, the plurality of legacy storage devices107may include, but are not limited to, backup storage devices, storage tapes, and any other computing devices. A person skilled in the art would understand that, any other legacy storage devices, not mentioned explicitly, may also be used in the present disclosure. In an embodiment, the plurality of legacy storage devices107may refer to storage equipment which may be outdated, obsolete and unsupported. In an embodiment, the legacy backup server108may comprise a plurality of metadata associated with the plurality of legacy storage devices107and logic associated with the historic data. Further, the communication network109may include, but is not limited to, a direct interconnection, an e-commerce network, a Peer to Peer (P2P) network, Local Area Network (LAN), Wide Area Network (WAN), wireless network (e.g., using Wireless Application Protocol), Internet, Wi-Fi and the like. Further, the data restoration system101is also connected through a communication network110to a transformation backup server103and to a user device105. In one embodiment, the transformation backup server103may be installed on a server with a local database. In an embodiment, the transformation backup server103may refer to a backup server of a current technology platform. In an embodiment, the transformation backup server103may be configured to store the plurality of metadata associated with the legacy backup server108. In an embodiment, the plurality of metadata may refer to a set of data associated with the historic data. In an embodiment, the user device105associated with the users may include, backup clients, workloads, servers, and the like associated with the enterprise. The data restoration system101restores requested historic data from legacy storage devices. In an embodiment, the data restoration system101may include, but is not limited to, a laptop, a desktop computer, a Personal Digital Assistant (PDA), a notebook, a smartphone, a tablet, a server and any other computing devices. A person skilled in the art would understand that, any other devices, not mentioned explicitly, may also be used as the data restoration system101in the present disclosure. The data restoration system101may receive a request from the user device105associated with users, through the transformation backup server103, for restoring historic data from a legacy storage device of the plurality of legacy storage devices107. At the outset, the data restoration system101may extract the plurality of metadata, from the legacy backup server108and store in the transformation backup server103in a format which may be recognizable by the transformation backup server103. In an embodiment, the legacy backup server108may be deactivated after the extraction of the plurality of metadata. Initially, the request for restoring the historic data may be received by the transformation backup server103from the user device105. The transformation backup server103may locate the metadata associated with the requested historic data from the plurality of metadata, stored in the transformation backup server103and may send the request along with the metadata to the data restoration system101. In an embodiment, the metadata comprises a job identification number and a media identification number of the historic data, a plurality of details associated with backed up data, files attributes, a time stamp and a plurality of encryption keys associated with the historic data, details of the legacy storage device from which historic data is requested and details of historic data requested, data format, and client details associated with the historic data. A person skilled in the art would understand that any other metadata, not mentioned explicitly, may also be received in the present disclosure. Further, the data restoration system101may determine a format of the historic data requested based on the metadata. In an embodiment, the format of the requested historic data may comprise encrypted and standard format. Thereafter, the data restoration system101may extract the historic data from the legacy storage device of the plurality of legacy storage devices107using at least one of the metadata and a predefined execution process associated with the historic data, based on the format of the historic data. In an embodiment, the predefined execution process may refer to a process for recovering historic data in any medium. In an embodiment, the predefined execution process may comprise binaries, cmdlets, and daemons processes. The data restoration system101may restore the extracted historic data to the user device105. In an embodiment, the data restoration system101may update a status of user request to the transformation backup server103on restoring the requested historic data to the user device105.

The I/O interface111may be configured to receive the request for restoring the historic data, from the user device105, through the transformation backup server103. The I/O interface111may receive the metadata associated with the historic data from the transformation backup server103. Further, the I/O interface111may provide the historic data from the legacy storage device of the plurality of legacy storage devices107to the user device105.

The information received from the I/O interface111may be stored in the memory113. The memory113may be communicatively coupled to the processor115of the data restoration system101. The memory113may also store processor instructions which may cause the processor115to execute the instructions for restoring the historic data of the enterprise.

FIG. 2shows a detailed block diagram of a data restoration system in accordance with some embodiments of the present disclosure.

Data200and one or more modules209of the data restoration system101are described herein in detail. In an embodiment, the data200may include user request data201, execution process data203, extracted data205and other data207.

The user request data201may comprise the request details from the user device105for restoring the historic data from the legacy storage device of the plurality of legacy storage devices107. The user request data201may also comprise details of the metadata associated with the historic data. The metadata associated with the historic data is located and added to the user request data201by the transformation backup server103, before sending the user request to the data restoration system101. In an embodiment, the metadata may comprise a job identification number and a media identification number of the historic data, a plurality of details associated with backed up data, files attributes, a time stamp and a plurality of encryption keys associated with the historic data, details of the legacy storage device from which historic data is requested and details of historic data requested, data format, and client details associated with the historic data.

The execution process data203may comprise details of the execution processes associated with the historic data. In an embodiment, the execution processes may comprise binaries, cmdlets, daemons and the like to recover the historic data from an encrypted format. In an embodiment, execution processes are used to recover data from any media. A person skilled in the art would understand that any other execution processes, not mentioned explicitly, may also be included in the present disclosure.

The extracted data205may comprise the extracted historic data from the plurality of legacy storage devices107. The extracted historic data is provided to the user device105through which the request was initiated.

The other data207may store data, including temporary data and temporary files, generated by modules209for performing the various functions of the data restoration system101.

In an embodiment, the data200in the memory113are processed by the one or more modules209of the data restoration system101. As used herein, the term module refers to an application specific integrated circuit (ASIC), an electronic circuit, a field-programmable gate arrays (FPGA), Programmable System-on-Chip (PSoC), a combinational logic circuit, and/or other suitable components that provide the described functionality. The said modules209when configured with the functionality defined in the present disclosure will result in a novel hardware.

In one implementation, the one or more modules209may include, but are not limited to a receiving module211, a metadata extraction module213, a format determination module215, a historic data extraction module217and a restoration module219. The one or more modules209may also include other modules221to perform various miscellaneous functionalities of the data restoration system101. In an embodiment, the other modules221may include an execution process determination module for determining the execution process associated with the requested historic data and an update module for updating a status of the user request to the transformation backup server103, on restoring the requested historic data to the user device105.

The receiving module211may receive the request from the user device105of the users, for restoring the historic data from the legacy storage device of the plurality of legacy storage device105, through the transformation backup server103. The receiving module211may also receive the metadata associated with the requested historic data from the transformation backup server103along with the request. In an embodiment, the transformation backup server103may locate the metadata associated with the requested historic data from the plurality of metadata.

The metadata extraction module213at the outset, before receiving any request from the user device105, may extract the metadata from the legacy backup server108associated with the enterprise. The metadata extraction module213may extract the metadata and store in the transformation backup server103in the format recognized by the transformation backup server103.

FIG. 3shows a flowchart for extracting metadata from legacy backup sever in accordance with some embodiments of the present disclosure.

At block301, the metadata extraction module213may obtain the metadata associated with the historic data in text format such as, Comma Separated Values (CSV) format of the legacy backup server108based on a predefined native process of the legacy backup server108. In an embodiment, the predefined native process may comprise instructions specific to the legacy storage device for restoring the historic data. In an embodiment, the metadata associated with the historic data may comprise the job identification number and the media identification number of the historic data, the plurality of details associated with backed up data, files attributes, the time stamp and the plurality of encryption keys associated with the historic data, details of the legacy storage device from which historic data is requested and details of historic data requested, data format, and client details associated with the historic data.

At block303, the metadata extraction module213may convert the metadata associated with the legacy backup server108in a format recognized by the transformation backup server103. In an embodiment, the conversion may include rearranging the table fields to match the format followed in the transformation backup server103.

At block305, the metadata extraction module213may store the metadata in the transformation backup server103, obtained from the legacy backup server108in the converted format of the transformation backup server103.

At block307, the metadata extraction module213may export the metadata from the transformation backup server103for consistency check.

At block309, the metadata extraction module213may check if all the job identification number associated with historic data are available in the transformation backup server103. If all the job identification number are available, the method moves to block311. Alternatively, for the non-available job identification number, the method moves to block313.

At block311, the metadata extraction module213may indicate successful extraction of the metadata for all available job identification number.

At block313, the metadata extraction module213may check if the process from block303to block309for the non-available job identification number is repeated twice. If the process from block303to block309for the non-available job identification number is repeated twice, the method moves to block315. Alternatively, if the process from block303to block309for the non-available job identification number is not repeated twice, the method may repeat the process from block303until the metadata for all the non-available job identification is extracted successfully.

At block315, the metadata extraction module213may allow and alert an administrator to manually enter the metadata associated with the non-available job identification number.

The format determination module215may determine the format of the historic data based on the metadata associated with the historic data. The format determination module215may check and determine if the requested historic data is in one of, the encrypted format or the standard format. In an embodiment, the encrypted format may refer to data in cipher form. In an embodiment, the standard format may refer to data in human readable form.

The historic data extraction module217may extract the historic data from the legacy storage device of the plurality of legacy storage devices107. The historic data extraction module217may extract the historic data using the metadata associated with the historic data, when the format of the historic data is determined to be of the standard format. In such case, the historic data extraction module217may extract the historic data by reading storage tape using native open format. Further, the historic data extraction module217may extract the historic data using the metadata and the predefined execution process associated with the historic data, when the format of the historic data is determined to be of the encrypted format.

The restoration module219may restore the extracted historic data to the user device105.

FIG. 4show an exemplary representation of restoring historic data of an enterprise in accordance with some embodiments of the present disclosure.FIG. 4shows an exemplary representation400of restoring historic data for an enterprise. The exemplary representation400comprises a transformation backup server401of the enterprise, which is coupled to a backup network403. The backup network403is coupled to user device105such as, servers405. The backup network403is also coupled to a local database407. In an embodiment, the transformation backup server401may be configured in the local database407. The transformation backup server401comprises a metadata database409. The transformation backup server401may also comprise a storage server411configured to receive the request from the servers405. Further, the exemplary transformation backup server401is connected to the data restoration system101for restoring the historic data associated with the enterprise from the legacy storage devices107. The legacy storage devices107comprises a tape library413, a legacy backup server415and an offsite storage area417. Initially, the data restoration system101may extract the metadata associated with the enterprise from the legacy backup server415and store in the metadata database409of the transformation backup server401. Consider, the data restoration system101may extract the metadata of tape data stored in the tape library413. For example, the metadata associated with the tape data may comprise the job identification number as “123456T”, the media identification number as “M4562”, file attributes, such as, file type, file permission, file extension etc. Further, timestamp associated with the tape data as “2009-05-1D1T15:48:45”, the encryption key as “TP124”, details of legacy storage device as “tape library 44T” and data format of the tape data as “Digital Audio Tape (DAT)” format.

In an embodiment, the data restoration system101may convert the format of the historic data to the format recognized by the transformation backup server401. In an embodiment, while extracting the metadata, the data format for each media may be captured and updated in the metadata database409. Consider, at an instant, the data restoration system101may receive the request from the servers405for restoring the tape data from the tape library413through the transformation backup server401In an embodiment, the transformation backup server401may locate the metadata of the tape data from the metadata database409and provide the request along with the metadata to the data restoration system101. The data restoration system101may determine the format of the tape data based on the metadata. In an embodiment, the format of the requested historic data comprises encrypted and standard format. In an embodiment, the encrypted format may refer to encoded form of data, where encoding may be performed using encryption technique. A person skilled in the art would understand that any encryption techniques may be used in the present disclosure. In an embodiment, the standard format may refer to any readable format of historic data. In the present case, the format of the tape data is determined to be DAT format based on the metadata. For instance, the data restoration system101determines the format of the tape data to be in encrypted format based on the metadata. In such case, the data restoration system101may extract the tape data from the tape library413using the predefined execution process associated with the tape data. In an embodiment, the predefined execution process is used for recovering data from any medium. In an embodiment, the predefined execution process may comprise binaries, cmdlets and daemons processes. For instance, the data restoration system101may initiate the daemon process associated with the tape data to recover the tape data. The data restoration system101may restore the extracted tape data from the tape library413to the servers405. Further, the data restoration system101may update the status of the request from the servers405to the transformation backup server401, on restoring the requested tape data to the servers405.

FIG. 5illustrates a flowchart showing a method for restoring historic data of an enterprise in accordance with some embodiments of present disclosure. As illustrated inFIG. 5, the method500includes one or more blocks for restoring historic data of an enterprise. The method500may be described in the general context of computer executable instructions. Generally, computer executable instructions can include routines, programs, objects, components, data structures, procedures, modules, and functions, which perform particular functions or implement particular abstract data types.

At block501, the request from the user is received from the receiving module211, through the transformation backup server103, for restoring historic data from the legacy storage device of the plurality of legacy storage devices107, associated with the enterprise. The request is received along with metadata associated with the historic data. The metadata associated with the historic data is previously extracted and stored by the metadata extraction module213in the format recognizable by the transformation backup server103.

At block503, the format of the historic data is determined, by the format determination module215, based on the metadata.

At block505, the historic data is extracted, by the historic data extraction module217, from the legacy storage device, using at least one of the metadata and a predefined execution process associated with the historic data, based on the format of the historic data.

At block507, the extracted historic data is restored, by the restoration module219to the user.

FIG. 6illustrates a block diagram of an exemplary computer system600for implementing embodiments consistent with the present disclosure. In an embodiment, the computer system600may be used to implement the data restoration system101. The computer system600may include a central processing unit (“CPU” or “processor”)602. The processor602may include at least one data processor for restoring historic data of an enterprise. The processor602may include specialized processing units such as, integrated system (bus) controllers, memory management control units, floating point units, graphics processing units, digital signal processing units, etc.

Using the I/O interface601, the computer system600may communicate with one or more I/O devices. For example, the input device may be an antenna, keyboard, mouse, joystick, (infrared) remote control, camera, card reader, fax machine, dongle, biometric reader, microphone, touch screen, touchpad, trackball, stylus, scanner, storage device, transceiver, video device/source, etc. The output device may be a printer, fax machine, video display (e.g., cathode ray tube (CRT), liquid crystal display (LCD), light-emitting diode (LED), plasma, Plasma display panel (PDP), Organic light-emitting diode display (OLED) or the like), audio speaker, etc.

In some embodiments, the computer system600consists of the data restoration system101. The processor602may be disposed in communication with the communication network609via a network interface603. The network interface603may communicate with the communication network609. The network interface603may employ connection protocols including, without limitation, direct connect, Ethernet (e.g., twisted pair 10/100/1000 Base T), transmission control protocol/internet protocol (TCP/IP), token ring, IEEE 802.11a/b/g/n/x, etc. The communication network609may include, without limitation, a direct interconnection, local area network (LAN), wide area network (WAN), wireless network (e.g., using Wireless Application Protocol), the Internet, etc. Using the network interface603and the communication network609, the computer system600may communicate with a legacy storage device6141, a legacy storage device6142and a legacy storage device614N(plurality of legacy storage device614) and a legacy backup server615. Further, the computer system600may also communicate with a transformation backup server616and a user device617. The network interface603may employ connection protocols include, but not limited to, direct connect, Ethernet (e.g., twisted pair 10/100/1000 Base T), transmission control protocol/internet protocol (TCP/IP), token ring, IEEE 802.1a/b/g/n/x, etc.

The communication network609includes, but is not limited to, a direct interconnection, an e-commerce network, a peer to peer (P2P) network, local area network (LAN), wide area network (WAN), wireless network (e.g., using Wireless Application Protocol), the Internet, Wi-Fi and such. The first network and the second network may either be a dedicated network or a shared network, which represents an association of the different types of networks that use a variety of protocols, for example, Hypertext Transfer Protocol (HTTP), Transmission Control Protocol/Internet Protocol (TCP/IP), Wireless Application Protocol (WAP), etc., to communicate with each other. Further, the first network and the second network may include a variety of network devices, including routers, bridges, servers, computing devices, storage devices, etc.

In some embodiments, the processor602may be disposed in communication with a memory605(e.g., RAM, ROM, etc. not shown inFIG. 6) via a storage interface604. The storage interface604may connect to memory605including, without limitation, memory drives, removable disc drives, etc., employing connection protocols such as, serial advanced technology attachment (SATA), Integrated Drive Electronics (IDE), IEEE-1394, Universal Serial Bus (USB), fiber channel, Small Computer Systems Interface (SCSI), etc. The memory drives may further include a drum, magnetic disc drive, magneto-optical drive, optical drive, Redundant Array of Independent Discs (RAID), solid-state memory devices, solid-state drives, etc.

The memory605may store a collection of program or database components, including, without limitation, user interface606, an operating system607etc. In some embodiments, computer system600may store user/application data606, such as, the data, variables, records, etc., as described in this disclosure. Such databases may be implemented as fault-tolerant, relational, scalable, secure databases such as Oracle or Sybase.

In some embodiments, the computer system600may implement a web browser608stored program component. The web browser608may be a hypertext viewing application, for example MICROSOFT® INTERNET EXPLORER™, GOOGLE® CHROME™, MOZILLA® FIREFOX™, APPLE® SAFARI™, etc. Secure web browsing may be provided using Secure Hypertext Transport Protocol (HTTPS), Secure Sockets Layer (SSL), Transport Layer Security (TLS), etc. Web browsers608may utilize facilities such as AJAX™, DHTML™, ADOBE® FLASH™, JAVASCRIPT™, JAVA™, Application Programming Interfaces (APIs), etc. In some embodiments, the computer system600may implement a mail server stored program component. The mail server may be an Internet mail server such as Microsoft Exchange, or the like. The mail server may utilize facilities such as ASP™, ACTIVE™, ANSI™ C++/C#, MICROSOFT®, .NET™, CGI SCRIPTS™, JAVA™, JAVASCRIPT™, PERL™, PHP™, PYTHON™, WEBOBJECTS™, etc. The mail server may utilize communication protocols such as Internet Message Access Protocol (IMAP), Messaging Application Programming Interface (MAPI), MICROSOFT® exchange, Post Office Protocol (POP), Simple Mail Transfer Protocol (SMTP), or the like. In some embodiments, the computer system600may implement a mail client stored program component. The mail client may be a mail viewing application, such as APPLE® MAIL™, MICROSOFT® ENTOURAGE™, MICROSOFT® OUTLOOK™, MOZILLA® THUNDERBIRD™, etc.

An embodiment of the present disclosure helps enterprises to recover legacy data as when required without large migration or data conversion project.

An embodiment of the present disclosure keeps data integrity intact till its retention period.

An embodiment of the present disclosure supports heterogeneous legacy system.

An embodiment of the present disclosure eliminates cost for staging area.

An embodiment of the present disclosure reduces time in restoring data by directly writing back to requested server.

An embodiment of the present disclosure enables restoration of all formats of media with encryption and multiplexed streams as well.

An embodiment of the present disclosure with help of meta data conversion enables users to explore data backed up using legacy systems.

An embodiment of the present disclosure eliminates upfront data migration required from old medias to new storage or tape media.

An embodiment of the present disclosure eliminates legacy infrastructure and resources required to support legacy backup servers for any future data migration and restoration.

An embodiment of the present disclosure eliminates use of expensive third-party restoration specialists and servers for restoration and migration services.

An embodiment of the present disclosure recovers data without converting data format by leveraging native processes and hence better success rate is achieved.

The described operations may be implemented as a method, system or article of manufacture using standard programming and/or engineering techniques to produce software, firmware, hardware, or any combination thereof. The described operations may be implemented as code maintained in a “non-transitory computer readable medium”, where a processor may read and execute the code from the computer readable medium. The processor is at least one of a microprocessor and a processor capable of processing and executing the queries. A non-transitory computer readable medium may include media such as magnetic storage medium (e.g., hard disk drives, floppy disks, tape, etc.), optical storage (CD-ROMs, DVDs, optical disks, etc.), volatile and non-volatile memory devices (e.g., EEPROMs, ROMs, PROMs, RAMs, DRAMs, SRAMs, Flash Memory, firmware, programmable logic, etc.), etc. Further, non-transitory computer-readable media include all computer-readable media except for a transitory. The code implementing the described operations may further be implemented in hardware logic (e.g., an integrated circuit chip, Programmable Gate Array (PGA), Application Specific Integrated Circuit (ASIC), etc.).

Still further, the code implementing the described operations may be implemented in “transmission signals”, where transmission signals may propagate through space or through a transmission media, such as, an optical fiber, copper wire, etc. The transmission signals in which the code or logic is encoded may further include a wireless signal, satellite transmission, radio waves, infrared signals, Bluetooth, etc. The transmission signals in which the code or logic is encoded is capable of being transmitted by a transmitting station and received by a receiving station, where the code or logic encoded in the transmission signal may be decoded and stored in hardware or a non-transitory computer readable medium at the receiving and transmitting stations or devices. An “article of manufacture” includes non-transitory computer readable medium, hardware logic, and/or transmission signals in which code may be implemented. A device in which the code implementing the described embodiments of operations is encoded may include a computer readable medium or hardware logic. Of course, those skilled in the art will recognize that many modifications may be made to this configuration without departing from the scope of the invention, and that the article of manufacture may include suitable information bearing medium known in the art.

REFERRAL NUMERALS