Backup Software / Backup Terms Glossary / Databases / Replication Server
Replication server is a server that is configured to act either as a source of data for other servers (Master Server), or to receive data from the central server (Slave Server). Replication configuration enables you to improve performance of your applications, increase data security, distribute data geographically, and much more.
It is important to understand difference between replication servers and cluster servers. All clustered servers are supposed to share the same configuration and act as one, while replication servers can be different. Furthermore, in many situations it is recommended to set up Slave Servers differently than the Masters, so when applications interact with the database, they can choose an appropriate server for each task.
A lot of server software – particularly, database management software like MySQL or MS SQL – come with the replication feature out of the box. Database replication is based on tracking all modifications made to the Master Server, and performing identical operations on Slaves, asynchronously or in real time. Before enabling replication, you need to synchronize the Master and all Slaves: this is where Handy Backup comes into play. Our software lets you easily back up databases hosted on the Master Server, and then restore it to Slave Servers. To learn more, please see MySQL Replication.
Version 7.9.10, built on 16 February, 2018. 65.7 MBBackup Software from Novosoft LLC. 249 USD per license.
Setting up replication servers requires you to synchronize two databases first. You can do it for MySQL, Oracle, MS SQL and other DBMS with the help of the Small Server edition of our software. Try free for 30 days!
A common difficulty with backing up databases is that database management systems significantly slow down when exporting large sets of data. This is where replication comes into play: you can set up a replication server and distribute the roles so that the Master Server handles all writing operations and the Slave Server is used for reading and backups.
Another thing that you may want to do to a replication server is change its storage engine. For example, in MySQL there is a general purpose engine called InnoDB which is ACID-compliant, supports transactions and is used by default, and MyISAM which is not transaction-safe and lacks many important features, but excels in data retrieval tasks. A common MySQL Backup scenario includes setting up a Slave replication server, changing the storage engine of all tables to MyISAM, and then using it for backups. To learn more, please see MySQL Backup.
In the following video tutorial you can learn how to back up and restore MySQL databases with Handy Backup.
Note: Instructions in this video suggest that you already have Handy Backup installed on your computer. If you still haven’t done so, don’t hesitate to download it.
Recovering Master database after a data loss event requires you to change your Slave Server to act as a Master (so the application continues working), restore the Master, and then change the configuration back. Recovery scenario is specific to each database management system, but there is a common recommendation that can be used in all cases:
To learn about recovering MySQL databases, please refer to MySQL Recovery.
Version 7.9.10, built on 16 February, 2018
See all terms from Databases...
Backup Terms Glossary
Current glossary explains various terms that you may come across while working with Handy Backup or other backup software.
Handy Backup is a backup utility for Windows Servers and PCs that is famous for its flexibility and ease of use.
The glossary contains 219 terms. The current section Databases contains 19 terms.
Copyright © 2004-2018 Novosoft LLC. All rights reserved. Handy Backup software.
United States, P.O.Box 535, Louisville, OH 44641 Tel.: +1 (707) 703-13-11
Back to Top