Remote SQL backups are complicated. We will explain why and show all the available options to make the backups anyway. Continue reading Remote SQL Server backups explained
Category Archives: differential
Backup SQL Server on the network
SQLBackupAndFTP creates standard *.bak files when it runs locally on the same computer where SQL Server is. For remote SQL Server computer backups SQLBackupAndFTP creates backup script files (*.sql). Whenever possible, you should always opt for *.bak backups against *.sql backup files.
Here we will show you how to backup a SQL Server on the network to the standard *.bak file even when SQLBackupAndFTP runs on a different computer from where the SQL Server is. The main requirement, in this case, is that both SQL server and SQLBackupAndFTP have access to the same shared network folder.
Customize backup file name
By default SQLBackupAndFTP stores backups in file names like DatabaseNameYYYYMMDDHHMM.zip (eg Pubs201801011120.zip). But you can also use custom file names if you have such needs Continue reading Customize backup file name
Frequently Asked Questions about SQLBackupAndFTP
Here we tried to answer the most asked questions. If you couldn’t find an answer here you can ask your question on the community forum. If you have an active Full-Service subscription you can contact support.
Continue reading Frequently Asked Questions about SQLBackupAndFTP
How to run SQLBackupAndFTP v11 from a command line
SQLBackupAndFTP runs database backups automatically and most of the users schedule it via windows interface/GUI. But you can also start a backup job manually via a command-line interface. One of the examples, when you may need it, is a complex scheduling scenario when the options provided in the program interface are not enough. In this case you may build more complicated schedule with Windows Schedule. Continue reading How to run SQLBackupAndFTP v11 from a command line
SQLBackupAndFTP v11 – What’s New?
Have you seen our brand-new version 11 of SQLBackupAndFTP? If yes, then you have also noticed that its looks and feels very different from its predecessor (compare features in the new & old versions). That’s right – this release is built from scratch based on our eight-year experience creating SQL Server backup software and close to 1,000,000 installations of the previous versions.
If you have used the old version, this post will help you to quickly grasp the main points that make the new version better. If you are new to SQLBackupAndFTP, you can read this as a quick introduction. Continue reading SQLBackupAndFTP v11 – What’s New?
What are the most common backup strategies?
Choosing a database backup strategy is crucial because it determines how data in your SQL Server database is protected. You can read more about database backup strategies, but here we are going to present you some statistics on how SQLBackupAndFTP users backup their databases. The numbers are based on a sample of about a thousand users. Continue reading What are the most common backup strategies?
How to Restore SQL Server Database from backup
This article shows several ways of how you can restore a SQL Server database backup. In particular, we will consider how to restore a database
Continue reading How to Restore SQL Server Database from backup
Backup and Restore Utility SQLBackupAndFTP
In that blog post let’s talk about one of the crucial questions in the life of every DBA it is SQL Server database backup and restores process, which you can cover using backup and restore utility SQLBackupAndFTP. You can install this tool on your machine or personal computer and it will do all work for you. So here is a short tutorial how you can protect your SQL Server database using backup and restore utility. Continue reading Backup and Restore Utility SQLBackupAndFTP
The log in this backup set begins at LSN, which is too recent to apply to the database
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.