Backup  &  Disaster Recovery

 Expect the best. Prepare for the worst.

Odoo image and text block

Disaster Recovery

No one expects data corruption or loss, but it is far less expensive to maintain a backup than to have to re-create it from scratch. 

GMX TEC Cloud provides automatic backup solutions!

What's included

Backup storage on the GMX TEC Cloud
can simplify backup and restore,
automate and customize schedules and target specific data.

 Why Move Backup and Disaster Recovery To The Cloud?


Discover issues in your IT environment before they have a significant impact. We offer a great toolset of monitoring and alerting tools.


Quickly recover the data you need to meet recovery time objective. Great reflexes and time efficiency.


Restore files, apps and virtual servers when needed, and promote business resiliency through option like automated backup and disaster recovery testing.

Backup and Restore

 Protect data without the need for expensive on-site hardware and administrative overhead. Cost-effective data recovery enabled by an enterprise-grade multi-region public cloud infrastructure.

Disaster Recovery (DR)

 Eliminate the need to replicate your production system in full at a secondary company managed data center. Take advantage of cloud-based systems to enable enterprises to store replicated virtual machines to multiple different storage regions for even greater protection and redundancy.


 Streamlining the archival process lowers cost and eliminates reliance on tape, which is an error-prone and manual process.

Test and Development

 Test/Dev replicated systems can be instantly spun-up as needed, on demand, with no dedicated hardware or software for greater flexibility and speed.

Data Analytics

 Analyze backed up data to understand risks and challenges around dormant data, storage growth, and data classification. A cloud storage model can increase visibility into existing data which can then be better leveraged for additional business value.

Converged Architecture

 Converge multiple workloads together in a ‘single pane of glass’ while gaining the assurance that your data, stored on the public cloud infrastructure, adhere to global data privacy regulations.

Basics of disaster recovery planning

Recovery Time Objective


The recovery time objective (RTO) is the maximum tolerable length of time that a computer, system, network, or application can be down after a failure or disaster occurs.

There are three primary ways to reduce the recovery time of servers:

  • Have the servers in affinity groupings that logically go together, either by tiers or by service or application support.  

  • Integrating the orchestration and replication tools for administrative efficiency

  • Thoroughly and routinely perform failover tests. Perfect the boot order, re-ip addressing, and scripts well ahead of when an outage occurs. Have the failover push-button ready.

Recovery Point Objective


The recovery point objective (RPO) is the age of files that must be recovered from backup storage for normal operations to resume if a computer, system, or network goes down as a result of a hardware, program, or communications failure. The RPO is expressed backward in time (that is, into the past) from the instant at which the failure occurs, and can be specified in seconds, minutes, hours, or days. It an important consideration in disaster recovery planning (DRP).

The RPO gives systems designers a limit to work to. For instance, if the RPO is set to four hours, then in practice, off-site mirrored backups must be continuously maintained – a daily offsite backup on tape will not suffice.

Figure 1: Ratio of cost to RTO/RPO

Because smaller RTO and RPO values often come with an increase in complexity, the associated administrative overhead follows a similar curve.




Define RPO and RTO






Manage Sensitive Data



Test Plan Regularly

Before designing a DR plan, we conduct a thorough risk assessment to 
analyze the systems being utilized and identify any potential threats to 
your mission-critical operations.

This step is critical because it is where we determine what kind of DR plan is required. 
GMX can guarantee that your organization will be 
up-and-running again quickly using the most immediate solution there is.

GMX will help you determine who needs to do what in the event of a disaster. 
How you access your data and resume activities during an interruption in business continuity
should be determined beforehand and communicated to all employees,
 to avoid the inevitable confusion that sets in during a disaster. 

Every organization has sensitive data, whether it be proprietary resources, 
sensitive employee records, or customer account information. 
A good DR plan should ensure that all confidential data and information is regularly backed up, 
properly secured, and immediately recoverable when the plan is activated.

Once you have a DR plan in place, we will assist in testing it regularly. 
The more comprehensive the test, the better it will work.

See for yourself how easy it is to use.
Sign up for a proof of concept, by typing "POC" in the contact form.
Begin you backup in minutes.

Multi-Site / Multi-Region Architecture  

GMX TEC introduces a  multi-region architecture that can provide higher availability than deploying to a single region.
 If a regional outage affects the primary region, you can use Traffic Manager to fail over to the secondary region.
This architecture can also help if an individual subsystem of the application fails.

There are several general approaches to achieving high availability across regions and we
are going to explore them together.


Know more about our competitive Pricing Package

Implement a recovery strategy

Implementation & Testing  

GMX TEC offers a full package on recovery strategies.

Some of the practices include :
1. Regular tests on backups to confirm accuracy and tests on data recovery procedures to guarantee data availability. 
2. Regular testing that helps you catch problems that updating software can introduce in otherwise correctly functioning backups and restores. 
3. Deployment of backup hardware and software while performing the initial backup of the entire data store. 
4. Creating a schedule of regular full backups and incremental data backups. 
5. Move backup data off-site (either via tape storage, network links to offsite storage, or Internet-based offsite storage).