Patent Application
20180284999
Application migration appliances are used to accelerate the transfer of large amounts of data between data centers or other large computer systems, bypassing traditional computer networks, such as the Internet. Traditional computer networks are bypassed due to the networks being too slow to transfer such large amounts of data. The large set of data is exported from the source computer system, such as a source data center, to nonvolatile storage included in the migration appliance. The migration appliance is then physically transported to the location of the target computer system, such as a target data center, where the data is imported from the migration appliance to the target computer system.
Traditional migration appliances are generic transfer devices that transfer block volumes or files and/or file systems in an application-agnostic fashion. A challenge of traditional migration appliances is that the end users or facilitators of the migration have to manage the exporting and importing of the data from and to the business applications and databases, and also perform any needed transformations and formatting of the data. These traditional approaches therefore require more skilled workers to manually perform various import and export functions and, consequently, take additional time to transfer the data to the target computer system in what is often a time-critical environment. A data migration typically involves an application data set. As the term is used in this document, an “application data set” is a set of data utilized by an application program. For example, in a database management system (DBMS), an application data set can be a relational table, hierarchical table, or other type of table depending on the type of DBMS that is being used.
An approach is disclosed that identifies a migration condition at a data migration appliance that is migrating an application data set from a source data center to a target data center. The data migration appliance includes a set of processors, a memory, a nonvolatile storage device, and one or more external interfaces. The approach loads software application utilities that correspond to the application data set onto the data migration appliance. The approach then exports the application data set from the source data center to the nonvolatile storage device in the data migration appliance using one of the software application utilities. After transport of the appliance, the approach imports the application data set stored on the nonvolatile storage device to the target data center using one of the software application utilities.
The foregoing is a summary and thus contains, by necessity, simplifications, generalizations, and omissions of detail; consequently, those skilled in the art will appreciate that the summary is illustrative only and is not intended to be in any way limiting. Other aspects, inventive features, and advantages will become apparent in the non-limiting detailed description set forth below.
This disclosure may be better understood by referencing the accompanying drawings, wherein:
Conventional data migration appliances do not include application-native capabilities because they do not include DBMSs. Conventional data migration appliances typically do not perform any of the functions listed in the above definition of a DBMS. Further, conventional data migration appliances typically do not include the computing resources that would be needed to run a DBMS. These resources, lacking or in sufficient amount in conventional data migration appliances, include the following types of resources: installed DBMS systems installed on the data migration appliance and stand-alone utilities used to provide the functions listed in the previously provided definition of a DBMS.
The approach allows cloud migration customers to directly export and import data to and from the migration appliance using source and target application specific utilities, such as a data warehouse service's remote client. The approach provides a more simplified selection of different transfer mechanisms for complex migration jobs that may involve migration from/to multiple applications. The approach provides a plug-in architecture that allows many types of migrations to be integrated into the migration appliance rather than having separate application-specific migration mechanisms deployed. Consequently, the approach results in reduced on site equipment and resource requirements by minimizing deployment of additional intermediate servers hosting application-specific import/export utilities. Traditional approaches often require execution of migration-specific utilities on production systems that serve as the source or target data center. Often customers either do not want to run migration-specific code on production systems, or they may not be able to deploy code into a closed appliance. Without the application-native extension mechanism, customers would have to provide additional resources and systems for migration code that are external to either the data migration appliance or data source.
As used herein, a “migration appliance” is a hardware appliance used for migrating data. A source/destination application is an application used by a customer which provides data and services; which is to be transferred from a source computer system to a target computer system. A migration-specific utility and/or application is a utility that imports and/or exports data from the source and/or destination application (i.e., exports data from the source computer system to the migration appliance and/or imports data from the migration appliance to the target computer system). An extension is a migration-specific application encapsulated in a format that is specific for the migration appliance.
An embodiment is provided for incorporating the application-native migration capabilities is to provide the appliance with a plug-in based extension mechanism. Following this embodiment, the extensions are installed into a base image, with the description of the command line arguments and mapping of ports that the extension needs. Once the image is compiled, it can be deployed by the engine as an appliance extension. An alternate embodiment would have the extensions implemented as a virtual machine, or as part of the appliance stack.
The approach provides application-native migration features that have the following attributes. The approach presents features to the end user in a list for user selection. By making selections, the user can launch and stop migration utilities that import and export data. The user also has access to the local disk included on the migration appliance, and further has access to a computer network, such as the Internet, over the network adapter included in the migration appliance. A user interface (UI) is provided to list currently running features to allow the end user to pausing or stop a feature from the UI. In one embodiment, the approach provides resource mapping and management by the migration appliance. This resource mapping and management can include mapping/management of storage, network, or the CPU), and can be used to limit and/or control utilization of both the migration appliance's capabilities, and/or the application being accessed.
In another embodiment, separate migration-specific utilities can access the same set of data; such that data can be transferred from one type of application on import to a different type of application on export.
In one embodiment, the migration appliance is provisioned with such application-native export/import utilities that are required for a specific migration job, such as when a customer orders a migration appliance with a particular migration in mind.
In one embodiment, the application-native export/import utilities are stored on the migration appliance in a nonvolatile storage and cannot be altered by the customer.
In one embodiment, the migration appliance allows multiple extensions to be run in parallel, to provide the ability to transfer data from a number of different applications to a single migration appliance simultaneously.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
The corresponding structures, materials, acts, and equivalents of all means or step plus function elements in the claims below are intended to include any structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. The detailed description has been presented for purposes of illustration, but is not intended to be exhaustive or limited to the invention in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the invention. The embodiment was chosen and described in order to best explain the principles of the invention and the practical application, and to enable others of ordinary skill in the art to understand the invention for various embodiments with various modifications as are suited to the particular use contemplated.
As will be appreciated by one skilled in the art, aspects may be embodied as a system, method or computer program product. Accordingly, aspects may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, aspects of the present disclosure may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied thereon.
Any combination of one or more computer readable medium(s) may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. As used herein, a computer readable storage medium does not include a computer readable signal medium.
Computer program code for carrying out operations for aspects of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
Aspects of the present disclosure are described below with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.
The computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
The following detailed description will generally follow the summary, as set forth above, further explaining and expanding the definitions of the various aspects and embodiments as necessary. To this end, this detailed description first sets forth a computing environment in
Northbridge 115 and Southbridge 135 connect to each other using bus 119. In one embodiment, the bus is a Direct Media Interface (DMI) bus that transfers data at high speeds in each direction between Northbridge 115 and Southbridge 135. In another embodiment, a Peripheral Component Interconnect (PCI) bus connects the Northbridge and the Southbridge. Southbridge 135, also known as the I/O Controller Hub (ICH) is a chip that generally implements capabilities that operate at slower speeds than the capabilities provided by the Northbridge. Southbridge 135 typically provides various busses used to connect various components. These busses include, for example, PCI and PCI Express busses, an ISA bus, a System Management Bus (SMBus or SMB), and/or a Low Pin Count (LPC) bus. The LPC bus often connects low-bandwidth devices, such as boot ROM 196 and “legacy” I/O devices (using a “super I/O” chip). The “legacy” I/O devices (198) can include, for example, serial and parallel ports, keyboard, mouse, and/or a floppy disk controller. The LPC bus also connects Southbridge 135 to Trusted Platform Module (TPM) 195. Other components often included in Southbridge 135 include a Direct Memory Access (DMA) controller, a Programmable Interrupt Controller (PIC), and a storage device controller, which connects Southbridge 135 to nonvolatile storage device 185, such as a hard disk drive, using bus 184.
ExpressCard 155 is a slot that connects hot-pluggable devices to the information handling system. ExpressCard 155 supports both PCI Express and USB connectivity as it connects to Southbridge 135 using both the Universal Serial Bus (USB) the PCI Express bus. Southbridge 135 includes USB Controller 140 that provides USB connectivity to devices that connect to the USB. These devices include webcam (camera) 150, infrared (IR) receiver 148, keyboard and trackpad 144, and Bluetooth device 146, which provides for wireless personal area networks (PANs). USB Controller 140 also provides USB connectivity to other miscellaneous USB connected devices 142, such as a mouse, removable nonvolatile storage device 145, modems, network cards, ISDN connectors, fax, printers, USB hubs, and many other types of USB connected devices. While removable nonvolatile storage device 145 is shown as a USB-connected device, removable nonvolatile storage device 145 could be connected using a different interface, such as a Firewire interface, etcetera.
Wireless Local Area Network (LAN) device 175 connects to Southbridge 135 via the PCI or PCI Express bus 172. LAN device 175 typically implements one of the IEEE 802.11 standards of over-the-air modulation techniques that all use the same protocol to wireless communicate between information handling system 100 and another computer system or device. Optical storage device 190 connects to Southbridge 135 using Serial ATA (SATA) bus 188. Serial ATA adapters and devices communicate over a high-speed serial link. The Serial ATA bus also connects Southbridge 135 to other forms of storage devices, such as hard disk drives. Audio circuitry 160, such as a sound card, connects to Southbridge 135 via bus 158. Audio circuitry 160 also provides functionality such as audio line-in and optical digital audio in port 162, optical digital output and headphone jack 164, internal speakers 166, and internal microphone 168. Ethernet controller 170 connects to Southbridge 135 using a bus, such as the PCI or PCI Express bus. Ethernet controller 170 connects information handling system 100 to a computer network, such as a Local Area Network (LAN), the Internet, and other public and private computer networks.
While
The Trusted Platform Module (TPM 195) shown in
After the application data set is exported from source data center 320 to data migration appliance 300, the data migration appliance is physically transported from source location 310 to target location 340 via one or more transportation mechanisms 330 such as ground transportation, air transportation, air transportation, and other transport mechanisms.
When it arrives at target location 340, data migration appliance 300 is physically connected to target data center 340 using one or more physical interfaces, such as cables (e.g., universal serial bus, etc.). Data that is being migrated that now resides on data migration appliance 300 is imported to target data center 350 using one or more software application utilities. If the customer is also migrating to a different application platform, such as to a different DBMS, import utilities installed on data migration appliance 300 might be used to load the application data set onto target data center 350 and also format the data stored in the data migration appliance from the first (source) DBMS format that was used at the source data center to a format used by the second (target) DBMS that is planned on being used at target data center 350.
Taking the ‘generic’ branch, at step 415, the process selects the first application specific utilities (e.g., import/export utilities for specific DBMS, etc.) corresponding to the customer requirements stored in data store 440. At step 425, the process load and installs the selected application specific utilities onto data migration appliance 300. The process determines whether there are more customer requirements to process (decision 430). If there are more customer requirements to process, then decision 430 branches to the ‘yes’ branch which loops back to step 415 to select and then load/install the next application specific utility corresponding to the customer's requirements. This looping continues until there are no more customer requirements to process, at which point decision 430 branches to the ‘no’ branch exiting the loop.
When customized instructions are being processed, then steps 435 through 470 are performed. At step 435, the process receives customer-specific migration requirements from data store 440. At step 445, the process selects the first customer requirement, such as a specific DBMS that might be a new DBMS, experimental DBMS, or a lesser known DBMS. At step 450, the process matches the on-hand application specific utilities from data store 420 with the selected customer requirement. The process then determines whether the application specific utilities were found in data store 420 (decision 455). If the application specific utilities were found, then decision 455 branches to the ‘yes’ branch whereupon, at step 460, the process retrieves the application-specific utilities from an on-hand source (data store 420). On the other hand, if the application specific utilities were not found, then decision 455 branches to the ‘no’ branch whereupon, at step 465, the process retrieves the application-specific utilities from external source (e.g., the Internet, a DBMS provider's website, etc.). At step 470, the process load and installs the selected and retrieved application specific utilities onto data migration appliance 300.
The process determines whether there are more customer requirements to process (decision 475). If there are more customer requirements to process, then decision 475 branches to the ‘yes’ branch which loops back to step 445 to select and then loads and installs the next application specific utility corresponding to the customer's requirements. This looping continues until there are no more customer requirements to process, at which point decision 475 branches to the ‘no’ branch exiting the loop.
At step 480, the entity that prepared the data migration appliance transports the appliance to the source data center to commence migration of the customer's application data set.
At step 540, the process accesses the customer application data set that is being stored at source data center 530 with the access being from the data migration appliance. At step 550, the process selects the customer's first data store in the source data center 530 (e.g., a database, etc.). At step 560, the process runs the application-specific data export utility at the data migration appliance with the export utility exporting the data from the selected data store in source data center 530 to the data migration appliance. The export utility may export the data from a first data format utilized by a source application (e.g., a source DBMS used at the source data center) to a different type of application that is planned on being used at the target data center (e.g., a target DBMS used at the target data center) as supported by data export utility.
The process determines whether there are more data stores to export from the source data center to the data migration appliance (decision 570). If there are more data stores to export, then decision 570 branches to the ‘yes’ branch which loops back to step 550 to select and export the next data store. This looping continues until there are no more data stores to export, at which point decision 570 branches to the ‘no’ branch exiting the loop. At step 580, the entity performing the exporting routine at the source data center transports data migration appliance 300 to the target data center to import data. The data migration appliance, at this point, has the application data set and the utilities stored on a nonvolatile storage device included in the data migration appliance. The export processing shown in
At step 640, the process running at the data migration appliance, accesses the customer data area that has been allocated in target data center 630. At step 650, the process selects the customer's first data store that was exported to the nonvolatile storage device in the data migration appliance (e.g., a database, etc.). At step 660, the process runs the application-specific data import utility on the data migration appliance to import the application data set from the selected data store on the data migration appliance to target data center 630. Similar to the export utility described in
The process next determines whether there are more data stores comprising the customer's application data set stored on the data migration appliance that need to be migrated (imported) to the target data center (decision 670). If there are more data stores to import, then decision 670 branches to the ‘yes’ branch which loops back to step 650 to select and import the next data store using the appropriate import software application utility. This looping continues until there are no more data stores to import, at which point decision 670 branches to the ‘no’ branch exiting the loop. The import processing shown in
Some embodiments of the present invention may include one, or more, of the following features, characteristics, advantages and/or operations: (i) using datastore-provided utilities as plugins; (ii) provides a data migration appliance including: (a) a plurality of input modules including a first input module structured and/or programmed to receive migrating data from a database/data access software solution of a first type, and a second input module structured and/or programmed to receive migrating data from a database/data access software solution of a second type which is different than the first type, (b) a set of output module(s) including a first input module structured and/or programmed to store migrating data from a database/data access software solution of a third type, and (c) a data migration module structured and/or programmed to receive migrating data from any of the input modules of the plurality of output modules and deliver it to any output module of the set of output module(s) to effect data migration; (iii) each different type of database/data access software solution stores the data in an entirely different format, different layout and different structure with respect to physical and/or logical addresses at which the data is stored; (iv) data stored according to each different type of database/data access software solution is not readable by a database engine corresponding to a different type; (v) each different type of database/data access software solution is proprietary to a different entity; (vi) the first and second types are characterized by different communication protocols; (vii) the third type is the same as one of the first or second types; and/or (viii) the third type is different than both of the first or second types.
While particular embodiments have been shown and described, it will be obvious to those skilled in the art that, based upon the teachings herein, that changes and modifications may be made without departing from this invention and its broader aspects. Therefore, the appended claims are to encompass within their scope all such changes and modifications as are within the true spirit and scope of this invention. Furthermore, it is to be understood that the invention is solely defined by the appended claims. It will be understood by those with skill in the art that if a specific number of an introduced claim element is intended, such intent will be explicitly recited in the claim, and in the absence of such recitation no such limitation is present. For non-limiting example, as an aid to understanding, the following appended claims contain usage of the introductory phrases “at least one” and “one or more” to introduce claim elements. However, the use of such phrases should not be construed to imply that the introduction of a claim element by the indefinite articles “a” or “an” limits any particular claim containing such introduced claim element to inventions containing only one such element, even when the same claim includes the introductory phrases “one or more” or “at least one” and indefinite articles such as “a” or “an”; the same holds true for the use in the claims of definite articles.
