DATA CENTER MIGRATION TRACKING TOOL

• US 20160191365A1
• Filed: 08/14/2015
• Published: 06/30/2016
• Est. Priority Date: 12/31/2014
• Status: Abandoned Application

• Current Assignee: SingleHop, LLC (Internap Holding LLC)
• Original Assignee: SingleHop, LLC (Internap Holding LLC)
• Inventors: Wakeman, Roger M., Volini, Elizabeth A., Jacobs, Jordan M., Talavera, Ricardo, Pace, Andrew W., Tworek, Lukasz, Davis, Michael A., Wilson, Austin T.
• Application Number:
  US14/826,802
• Publication Number:
  US 20160191365A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 41/0856 by backing up or archiving configuration information
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: H04L 43/10 Active monitoring, e.g. heartbeat, ping or trace-route

Abstract

A system stored in a non-transitory medium executable by processor circuitry for tracking the migration of a plurality of servers between data centers is provided. In one embodiment, the system comprising a job scheduler tool that receives a list of migrating devices that are migrating from an origin data center to a destination data center. A migration database stores migration data for each migrating device, the migration data including information representing a current migration state and past migration states of each migrating device. One or more processors execute migration logic to identify destination information in the destination data center for each migrating device in the list of devices, and an analyze tool checks the current migration state of each migrating device and identifies errors during migration of each migrating device to the destination data center.

Claims

1. A system stored in a non-transitory medium executable by processor circuitry for tracking the migration of a plurality of servers between data centers, the system comprising:

a job scheduler tool that receives notification of a migrating device that has been disconnected in an origin data center and maintains a list of devices that are in transit from the origin data center to a destination data center;

a migration database that stores migration data for each migrating device, the migration data including information representing a current migration state and past migration states of each migrating device;

one or more processors executing migration logic to identify destination information in the destination data center for each migrating device in the list of devices; and

an analyze tool that checks the current migration state of each migrating device and identifies errors during migration of each migrating device to the destination data center.

2. The system of claim 1, wherein the migration database stores configuration data for each migrating device, and the one or more processors executing migration logic automatically apply the stored configuration data for each migrating device to a corresponding hardware device when the hardware device is installed in the destination data center.

3. The system of claim 1, wherein the job scheduler is configured to monitor and route migration of each migrating device in the list of devices.

4. The system of claim 1, wherein one or more processors executing migration logic further determine a plurality of new destination cabinets in the new data center, cabinet units in the new data center, and switch ports for public and private network interfaces for each migrating device.

5. The system of claim 1, wherein the analyze tool further determines whether the migrating devices are pingable and identifies migrating devices as in transit when the migrating devices are not pingable.

6. The system of claim 1, wherein the analyze tool further determines whether the migrating devices have active switches and switch port information and identifies the migrating devices as discovered devices when the migrating devices have active switches and switch port information.

7. The system of claim 1, further comprising a force discovery tool that causes the system to display a manual input interface, wherein the manual input interface enables a user to manually identify the destination information in the destination data center.

8. The system of claim 1, further comprising a remote shut down tool that shuts down migrating devices before migration from the origin data center to the destination data center.

9. The system of claim 8, wherein the analyze tool further determines whether the migrating devices have properly shut down and identifies migrating devices as failed off when the migrating devices have not properly shut down.

10. The system of claim 1, further comprising a migration logs tool that displays log information for each migration state of each migrating device on a graphical user interface.

11. The system of claim 1, further an assignment tool that assigns any errors identified by the analyze tool to a worker or group of workers.

12. A computer-implemented method for monitoring the migration of a server, comprising:

receiving, by one or more processors, a list of migrating devices that are migrating from an origin data center to a destination data center;

stores, in one or more databases, migration data for each migrating device representing a current migration state and past migration states of each migrating device;

identifying, by the one or more processors, destination information in the destination data center for each migrating device; and

analyzing, by the one or more processors, the current migration state of each migrating device to identify errors during migration of each migrating device to the destination data center.

13. The method of claim 12, further comprising identifying, by the one or more processors, the migrating devices as in transit when the migrating devices are not pingable.

14. The method of claim 12, further comprising identifying, by the one or more processors, the migrating devices as discovered devices when the migrating devices have active switches and switch port information.

15. The method of claim 12, further comprising identifying, by the one or more processors, the migrating devices as network failed when the migrating devices have failed to connect at the destination data center.

16. The method of claim 12, further comprising identifying, by the one or more processors, the migrating devices as failed off when the migrating devices have not properly shut down.

17. The method of claim 12, wherein the one or more database store configuration data for each migrating device, and

wherein the one or more processors automatically apply the stored configuration data for each migrating device to a corresponding hardware device when the hardware device is installed in the destination data center.

18. The method of claim 12, further comprising determining, by the one or more processors, new destination cabinets and cab units in the new data center or switch ports for public and private network interfaces for each migrating device.

19. The method of claim 12, further comprising generating, by the one or more processors, migration logs that display log information for each migration state of each migrating device on a graphical user interface.

20. A system for implementing an interface the migration of a server, comprising:

a means for receiving a list of migrating devices that are migrating from an origin data center to a destination data center;

a means for storing migration data for each migrating device representing a current migration state and past migration states of each migrating device;

a means for identifying destination information in the destination data center for each migrating device; and

a means for analyzing the current migration state of each migrating device to identify errors during migration of each migrating device to the destination of data.