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.
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
Now that Microsoft has released SQL Server for Linux, even if your main tech stack is tied to a Windows Server you may want to copy the database to another SQL Server located on a Linux computer. This can come in handy, for example, if you wanted 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 the SQL Server database from Windows to Linux:
- Using T-SQL’s BACKUP DATABASE and RESTORE DATABASE commands
- Generation of T-SQL database script (such as mysqldump)
- Creating BACPAC
- SqlBak service
Below is a short step-by-step tutorial on how to get private keys for OneDrive for Business. Continue reading How to get app keys for OneDrive For Business
Jupyter Notebook is a great tool for data analysis. And one of its greatest features is that you can easily combine runnable code with rich-text annotations. Markdown cells that contain such annotations support both HTML and Markdown syntax. Continue reading Jupyter Notebook Markdown Cheatsheet
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
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
The solutions described in this blog post work for any Linux distribution: Ubuntu, Red Hat, Open SUSE, CentOS, Debian, Oracle Linux etcю However, the package installation commands may differ.
The automatic backup of MySQL Server databases is very important for preventing data loss. In order to properly automate backups, you must follow the following steps:
- Create a database backup
- Zip the backup
- Encrypt the compressed file
- Send the backup to Internet storage using FTP, Dropbox, AWS, Google Drive, etc.
- Receive email notification concerning backup results
- Create a backup schedule
- Delete old backups
That issue may occur if the SqlBak (SQL Server Backup) Windows Service was interrupted by an error. Continue reading How to fix SqlBak “Service failed” error
Basically, to update SqlBak on Linux you need to update the package lists and reinstall or restart the SqlBak application. Below are some examples of how to do it on popular Linux distributions. Continue reading How to Update SqlBak on Linux