All posts by Omelchenko Alexander

How to backup remote SQL Server database using SqlBak

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 scripts 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.

Continue reading How to backup remote SQL Server database using SqlBak

How to backup and restore Amazon RDS SQL Server

Amazon RDS SQL Server is a cloud database from Amazon. The way RDS SQL Server performs backups is the main difference between this and 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.
Continue reading How to backup and restore Amazon RDS SQL Server

How to Copy SQL Server Database from Windows to Linux

After Microsoft has launched SQL Server for Linux, even if your main tech stack is tied to Windows Server you may need to copy the database to another SQL Server located on a Linux computer.

For example, this can come in handy if you want to provide developers with a database for testing without buying a Windows Server license. 

There are a few ways to tackle this task. This article examines the following methods to copy SQL Server database from Windows to Linux:

  1. Using T-SQL’s BACKUP DATABASE and RESTORE DATABASE commands;
  2. Generation of T-SQL database script (such as mysqldump);
  3. Creating BACPAC;
  4. SqlBak service.

Continue reading How to Copy SQL Server Database from Windows to Linux

How to automate MySQL databases backups to S3

If you have a database, then you need to back it up regularly, and preferably not manually. To perform regular backups is only half the battle, you also have to consider where to store them. Saving the backups on the same server where MySQL Server is installed isn’t safe, because if it crashes, you will lose everything. Continue reading How to automate MySQL databases backups to S3

MySQL DBMS – /bin/sh: 1: /usr/bin/mysql: not found

If you get one of the following error messages during the setting up of SqlBak on Linux or during the execution of a backup job:

MySQL DBMS – /bin/sh: 1:/usr/bin/mysql: not found
or
MySQL DBMS – /bin/sh: 1:/usr/bin/mysqldump: not found

it means that the SqlBak app could not find the path to the MySQL executables. By default, SqlBak searches for MySQL files in the /usr/bin/mysql directory. Continue reading MySQL DBMS – /bin/sh: 1: /usr/bin/mysql: not found

MS SQL Server DBMS – /bin/sh: 1: /opt/mssql-tools/bin/sqlcmd

If you get the following error message during SqlBak set up on Linux or during a backup job:

MS SQL Server DBMS – /bin/sh: 1: /opt/mssql-tools/bin/sqlcmd

it means that SqlBak app could not find the path to the msql executables. By default, SqlBak searches for mssql files in the /opt/mssql-tools/bin/sqlcmd directory. Continue reading MS SQL Server DBMS – /bin/sh: 1: /opt/mssql-tools/bin/sqlcmd

PostgreSQL DBMS – /bin/sh: 1: /usr/bin/psql: not found

If during setting up of SqlBak on Linux or during a backup job one of the following errors occurs:

PostgreSQL DBMS – /bin/sh: 1: /usr/bin/psql: not found
or
PostgreSQL DBMS – /bin/sh: 1: /usr/bin/pgdump: not found

it means that SqlBak app could not find the path to postgresql executables. By default, SqlBak looks for postgresql files in the /usr/bin/psql directory.  Continue reading PostgreSQL DBMS – /bin/sh: 1: /usr/bin/psql: not found