By recording real-time data changes to two storages, you no longer have to worry about unexpected hardware failures.
Why should you replicate your data?
Backup to hardware failure
We will replicate your server to a disk array in the same location; therefore you don’t have to worry about unexpected hardware problems.
Protection from a local failure
You can also choose to replicate data at regular intervals to another location, so that you won’t be compromised by more extensive data center failures.
Protection of important data
You will appreciate the current state of the data, for example, in databases, whether it is orders for e-shops or mail servers, whose disruption might paralyse the whole enterprise running.
Replicated data are immediately available to you, so that all business processes continue to work without restriction. Replication will ensure even higher availability for your solution.
How can you replicate
As part of synchronous replication, your data will be replicated concurrently, i.e. in real time. The current data will be located on two separate hardware in one data centre. We provide this method of replication automatically to the cloud hosting service.
For even higher availability, choose asynchronous replication for your solution. We create the current copy of the storage in several time intervals and store it on hardware in a separate location – For the Prague MasterDC in Brno and vice versa.
Other data protection options
To restore the infrastructure, a simple replica is not enough. In case pf natural disaster or fatal data centre failure, you will need Disaster recovery. Except for the current copy of data, we will also maintain computing capacity for you in the backup location. As you require, we will develop and implement a plan for the recovery of your IT.
Replication will hold your data if one of the nodes fails. However, if you delete part of the database at hand, unlike backups, it is very difficult to recover data from a replica. This is because any change to the write node is overwritten to the replicated node. Therefore, it cannot be considered a full-fledged advance.