The database was backed up on a server running version
The best way to protect your database is to make schedule backups. You can do it with the help of SQLBackupAndFTP, SSMS or T-SQL Commands. But when you try to restore your database you can receive some errors. In this article, we will show how to solve the next error: “The database was backed up on a server running version”. You can get this error message during the restoration process. Here is the text of the error message 3169:
Msg 3169, Level 16, State 1, Line 1 The database was backed up on a server running version 13.00.0801. That version is incompatible with this server, which is running version 12.00.4213. Either restore the database on a server that supports the backup, or use a backup that is compatible with this server. Msg 3013, Level 16, State 1, Line 1 RESTORE DATABASE is terminating abnormally.
The most common way to perform SQL Server database backup it to use SSMS or T-SQL Commands. But is it convenient to make backups using T-SQL Commands or SSMS and send them to FTP Server on a regular basis? With the help of 
One of the most popular places for storing SQL Server database backups is Amazon S3. But nowadays there are a lot of ways how to make SQL Server backup and many methods how to send them to Amazon S3. But how much time do you usually spend to do it? With the help of 
Nowadays it is really convenient to make SQL Server backups and send them to store somewhere in the cloud, for example to Box. How much time does it usually take you to make a backup with the help of T-SQL Command or SSMS and then send backups to Box? But what if you need to make a full backup every 24 hours, differential backups every four hours and transaction log backups every 30 minutes, how much time will you spend in this case? Luckily you can do backup SQL Server to Box in 3 minutes with the help of