NoSQL databases allow us to redefine the way we interact with data. However, data protection requirements remain the same as for SQL databases.
One of the main ways to protect your data is to back it up regularly. This article will help you protect your data for the most popular NoSQL database – MongoDB.
When you face any issues with SqlBak our support team may ask you to send the Advanced Log. Below is a short tutorial on how to do this.
Starting from SqlBak app version 3 you can backup and restore your PostgreSQL databases. The SqlBak app creates the backups of PostgreSQL databases via pg_dump. Currently, only full database backups can be performed for PostgreSQL Server databases.
Starting from SqlBak version 3 you can backup MySQL Server databases. SqlBak supports two ways to connect to your MySQL databases: phpMyAdmin and TCP/IP. Below you can find a step-by-step tutorial on how to backup your MySQL Server database via a TCP/IP connection. To backup MySQL Server databases, SqlBak uses the mysqldump utility. For now, with SqlBak on Windows, only full MySQL backups are available.
With SqlBak you can create a backup job to run scheduled backups of MySQL, send the backups to their destinations and, if needed, restore them. Below is a step-by-step guide on how to automate your MySQL backups if it’s only accessible via phpMyAdmin.
There are two types of people: people who do back up their files, and people who need to start doing it.
If you are not backing up your MySQL databases yet, you should start before you lose your precious data.
Making backups is necessary, but doing this with large databases may involve high server load and using up storage space. And only creating a backup once a day or once a week could lead to losing hours of work. So how can you make backups more often without overloading the server? Incremental backups can help you with this.
With the help of SqlBak, you can backup your remote SQL Server databases according to your schedule. A standard BACKUP DATABASE command doesn’t work on a remote SQL Server — only scripts can be generated. If there is a choice between script generation or performing backups in *.bak files, it is always recommended to run the standard BACKUP DATABASE command to get *.bak files. Scripts have some drawbacks: they are larger and do not support differential and transaction log backups. A more detailed explanation about remote backups can be found in the following blog post.
Amazon RDS SQL Server is a cloud database from Amazon. The way RDS SQL Server performs backups is the main difference between this and the classic SQL Server. It offers the following: snapshots, restore point-in-time, Export Data-tier Application and native backup to S3 (instead of native T-SQL BACKUP DATABASE construction).