Virtual infrastructure recovery configurator
Systems, methods and procedures to capture, format and process configuration information needed for a Managed Recovery Program (MRP) solution that supports orderly handling of virtual machines in an information technology production environment. An MRP automation package is portable and contains all of the required configuration data to bring virtual infrastructure on line in a recovery environment as well as associated scripts that can be executed to automatically process the configuration data.
1. A method for recovering a production environment which includes one or more physical and/or virtual machine infrastructure elements that together comprise one or more data centers, and where a recovery environment provides a managed recovery service for the infrastructure elements, the method carried out in the recovery environment, comprising:
receiving a recovery automation data file containing configuration information for the physical infrastructure elements;
receiving a virtual recovery automation file containing configuration information for the virtual infrastructure elements and a script file containing instructions to be executed in the recovery environment wherein configuration information in the virtual recovery automation file includes configuration information for hosts, networks, datastores, and virtual machines in the data centers;
instantiating a recovery system for hosting one or more available physical machines of the same type as in the production environment, the physical machines allocated from a group of machines such that a number of available physical machines may vary over time;
configuring physical machines in the recovery environment according to the virtual recovery automation file;
instantiating virtual machines in the recovery environment according to the virtual recovery automation file; and
executing the script file within the recovery system to configure the recovery environment.
2. The method of claim 1 wherein the virtual machines in the recovery environment are managed by a hypervisor.
3. The method of claim 1 wherein the virtual recovery automation package further includes specification for recovering physical machines in the production environment as virtual machines in the recovery environment.
4. The method of claim 1 wherein the configuration files are comma separated value files.
5. The method of claim 1 wherein the recovery machines are managed by a Vcenter server and the recovery machines are ESX hosts.
6. The method of claim 1 further comprising:
allocating physical machines from a list of physical machines reported as being available from a recovery service provider; and
executing the scripts on the physical machines thus allocated.
7. The method of claim 3 wherein a target location of the virtual machines in the recovery environment is specified according to the virtual recovery automation file.
8. The method of claim 3 wherein compute specifications including one or more of Central Processing Unit (CPU), Random Access Memory (RAM) or disk storage for virtual machines in the recovery environment are modified and/or specified according to the virtual recovery automation file.
9. The method of claim 8 wherein network configurations of virtual machines in the recovery environment are modified according to the virtual recovery automation file.
10. The method of claim 8 wherein virtual machines in the recovery environment are organized according to the virtual recovery automation file.
11. The method of claim 1 further comprising:
performing specified system checks including at least network and storage verification prior to execution of the script file.
12. The method of claim 1 wherein the virtual recovery automation file specifies configuration changes to be applied to a set of virtual machines in the recovery environment.
13. The method of claim 12 wherein the set of virtual machines to which the specification changes are applied includes all virtual machines in the recovery environment.
14. A data processing system recovery environment for providing a managed recovery service for a production environment which includes one or more physical and/or virtual machine infrastructure elements that together comprise one or more data centers comprising:
a recovery system that includes
one or more physical data processors for providing the managed recovery service that further comprise:
a communication interface and memory for receiving and storing
(a) a recovery automation data file containing configuration information for the physical infrastructure elements;
(b) a virtual recovery automation data file containing configuration information for the virtual infrastructure elements wherein configuration information in the virtual recovery automation includes configuration information for hosts, networks, datastores, and virtual machines;
(c) a script file containing instructions to be executed in the recovery environment;
the physical machines allocated from a group of machines in the recovery environment such that a number of available physical machines may vary over time;
the processor(s) executing one or more programs to
configure the physical machines in the recovery system according to the virtual recovery automation file;
instantiate virtual machines in the recovery system according to the virtual recovery automation file; and
execute the script file within the recovery system to configure the recovery environment.
15. The system of claim 14 additionally comprising:
a hypervisor for managing the virtual machines.
16. The system of claim 14 wherein the virtual recovery automation package further includes a specification for recovering physical machines in the production environment as virtual machines in the recovery environment.
17. The system of claim 14 wherein the configuration files are comma separated value files.
18. The system of claim 14 further comprising:
a vCenter server for managing the physical machines; and
wherein the physical machines in the system are ESX hosts.
19. The system of claim 14 further wherein the physical machines are allocated from a list of physical machines reported as being available from a recovery service provider.
20. The method of claim 1 further comprising, after the step of configuring physical machines:
receiving a report from a recovery automation server that physical machines have been deployed;
copying the virtual recovery automation file to the deployed physical machines; and
executing the script file against the configuration data in the virtual recovery file.
21. A system for providing a managed recovery service for recovering a customer production environment to a recovery environment, the system comprising:
a recovery automation server located in the recovery environment, the recovery automation server comprising a memory for storing a recovery automation package including at least a virtual recovery automation file that includes a virtual recovery automation script file and configuration information for infrastructure elements in the customer production environment, wherein the configuration information further comprises a plurality of configuration files including:
a host configuration file including for each host in the data center a host name, address, data center identifier, and cluster assignment;
a network configuration file including virtual network configurations, virtual switch identifier, addresses, uplinks, and port groups;
a kernel network file including for each virtual host a host name, virtual switch identifier, kernel types, network address, subnet mask, and gateway;
a data store file including information indicating a primary host for the data store, host names, and data store information including capacity, block size, and cluster to which the data store is assigned; and
a virtual machine file including a hostname, operating system, processor specifications and network settings for each of the virtual machines required to be deployed;
the recovery automation server further executing one or more stored programs to:
allocate two or more physical servers from a server farm allocated to the managed recovery service;
allocate one or more data stores;
allocate low-level network functions to enable at least one physical network connection between the physical servers and data stores;
allocate a management server from the server farm;
configure the management server and allocated servers with Internet Protocol (IP) addresses;
connect the management server to the physical servers and data stores using at least one network connection;
subsequent to the steps recited above, the management server to further execute the virtual recovery automation script file to:
register one or more hosts as per the host configuration file;
assign hosts to clusters in a hierarchy as per the host configuration file;
configure virtual networking elements including two or more virtual switches, port groups, uplinks, or virtual machine (VM) kernels from the virtual kernel as per the kernel network file;
configure one or more data stores as per the data store configuration file;
deploy one or more virtual machines by assigning virtual machines to hosts as per the virtual machine configuration file;
preconfigure the virtual machines with processor, memory, and storage attributes as per the virtual machine file; and
power on the virtual machines.