Synchronization of container environments to maintain availability for a predetermined zone

A proactive monitoring-container switching system, the system comprising:

• a first server operating with a first hardware processor and a first hardware memory, said first server executing one or more software containers, said first hardware memory comprising the one or more software containers, said first server and/or the one or more software containers being operated on by one or more remote users, the one or more remote users accessing the first server using a first address identified by a domain name service (DNS) pointer;
• a proactive monitoring subsystem, said proactive monitoring subsystem operable to:
• scan the first server for a plurality of efficiency metrics, the plurality of efficiency metrics comprising:
• a central processing unit (CPU) utilization metric of the first server;
• a memory utilization metric of the first server;
• and
• a number of recurrent errors and recurrent restarts in an error log associated with the first server;
• identify that the first server is exceeding one or more efficiency metrics included in the plurality of efficiency metrics;
• build a new server, said new server operating with a second hardware processor and a second hardware memory;
• move and copy the one or more software containers from the first server to the new server, said move and copy being executed simultaneous to the one or more remote users operating on the first server, upon move and copy the one or more software containers to the new server, the new server replicates the first server;
• test an operation of the new server, said new server comprising a copy of the entirety of the first hardware memory, to determine a health and operability metric of the new server;
• upon identifying that the health and operability metric of the new server, said new server comprising the copy of the entirety of the first hardware memory, is above a predetermined threshold, execute an application programming interface (API) that changes the DNS pointer from a first address that identifies a location of the first server to a second address that identifies a location of the new server;
• and
• automatically switches operation of the one or more remote users to the new server.

A method for proactively monitoring a server cluster, said method comprising:

• monitoring health of a server cluster, said server cluster comprising a plurality of servers, said monitoring comprising:
• identifying a central processing unit (“CPU”) utilization metric for each server included in the plurality of servers;
• identifying a memory utilization metric for each server included in the plurality of servers;
• identifying a number of recurrent errors and recurrent restarts in an error log included in each server included in the plurality of servers;
• identifying that a first server, said first server comprising a first hardware processor and a first hardware memory, included in the server cluster, is exceeding:
• a first predetermined threshold for the CPU utilization metric;
• a second predetermined threshold for the memory utilization metric;
• or
• a third predetermined threshold for the number of recurrent errors and recurrent restarts;
• building a new server within the server cluster, said new server operating with a second hardware processor and a second hardware memory;
• copying an entirety of the first server to the new server included in the server cluster, said copying being executed simultaneously to one or more remote users and one or more remote vendor applications interacting with the first server, upon copying the entirety of the first server to the new server, the new server replicates the first server;
• testing an operation on the new server, said new server comprising a copy of the entirety of the first hardware memory, to determine that a health and operability metric of the new server meets a predetermined health and operability threshold;
• upon identifying that the health and operability metric of the new server, said new server comprising the copy of the entirety of the first hardware memory, meets the predetermined health and operability threshold, calling an application programming interface (API) to change a domain name service (DNS) pointer from a first address that identifies a location of the first server to a second address that identifies a location of the new server;
• and
• automatically switching operation of the one or more remote users and one or more remove vendor applications to the new server.