Making scheduled SQL Server database backups with the help of SQLBackupAndFTP you can face with some issues. Here we are going to discuss one of them. Let’s assume you created a scheduled database backup job and made all necessary settings, even clicked “Run Now” button to check the backup job and everything works perfectly. But when a time comes to make a backup according to the schedule you receive the following error message: More…
Working with SQL Server you face a lot of different error messages. Some of them can be solved in a minute, another required more time. In this blog post, we are going to talk about error message like “BACKUP LOG cannot be performed because there is no current database backup.” Here is a full error message:
Msg 4214, Level 16, State 1, Line 1 BACKUP LOG cannot be performed because there is no current database backup. Msg 3013, Level 16, State 1, Line 1 BACKUP LOG is terminating abnormally.
All users who’re working with SQL Server sooner or later face with the following error message:
Msg 4305, Level 16, State 1, Line 1 The log in this backup set begins at LSN 42000000037600001, which is too recent to apply to the database. An earlier log backup that includes LSN 42000000034400001 can be restored. Msg 3013, Level 16, State 1, Line 1 RESTORE LOG is terminating abnormally.
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.
Cannot use the backup file because it was originally formatted with sector size 4096 and is now on a device with sector size 512
The best way to backup your SQL Server databases is to use SQLBackupAndFTP. But if you still backup your SQL Server database with the help of SQL Server Management Studio you can face with the following issue. Cannot use the backup file because it was originally formatted with sector size 4096 and is now on a device with sector size 512. Before to solve this case let’s recreate the same error message. More…
In this article, we are going to discuss how to backup SQL database automatically with the help of SQLBackupAndFTP and SQL Server Management Studio (SSMS). Scheduling the backup process ought to be one of the elements that are vital in the life of any DBA.
This simple procedure will certainly save you lots of time and effort in the future. More…
Sometimes when you backup your SQL Server using SQLBackupAndFTP, SSMS or T-SQL Commands you can face the following issue Cannot Open Backup Device Operating System Error 5(Access is Denied). This has to be the most famous issue in taking SQL Server database backups. There are several reasons for this error and there are various ways to solve it. Some time ago we met this issue and for a time we were creating a backup and discovered a very helpful resolution to the issue. The issue was as described beneath:
Msg 3201, Level 16, State 1, Line 4 Cannot open backup device 'D:\\Adventureworks.bak'. Operating system error 5(Access is denied.). Msg 3013, Level 16, State 1, Line 4 BACKUP DATABASE is terminating abnormally.