SQLBackupAndFTP is a software that backups SQL Server, MySQL, and PostgreSQL Server databases, performs regular full, differential, and transaction log backups, runs file/folder backup, zips and encrypts the backups, stores them on a network or on an FTP server or in the cloud (Amazon S3 and others - we're constantly adding more), removes old backups, and sends an e-mail confirmation on the job's success or failure. SQLBackupAndFTP is ideal for any SQL Server, MySQL, PostgreSQL, Azure SQL, or Amazon RDS SQL database where backups should be sent to FTP, SFTP, FTPS, NAS, local or network folder, Google Drive, Dropbox, OneDrive, Box, Amazon S3 (and any S3-Compatible storage), Azure Storage, Backblaze B2, Yandex.Disk. It is especially useful for any SQL Server versions, including Azure SQL and Amazon RDS SQL, MySQL, and MariaDB or PostgreSQL, since they don't have built-in in tools for backup. With its intuitive user interface and powerful features, it provides a hassle-free way to automate backups, manage schedules, and restore data. While for the majority of the users this is a huge advantage, some specific configurations are not handled. SQL Backup Master 6.3 includes a new feature called backup chain validation that is responsible for generating “invalid backup chain detected” messages.You should not use SQLBackupAndFTP if you want to monitor SQL Server performance and schedule backups online in your browser for a large number of servers - may be suited better for you. This article describes the goal and function of this feature. The goal of backup chain validation is to warn users when other third-party applications could potentially interfere with the SQL Server backup chain. Specifically, when a differential or transaction log backup is started, SQL Backup Master analyzes SQL Server’s backup history table and checks to see if the most recent backup was also created by SQL Backup Master.

If a possible conflict is detected, SQL Backup Master writes an “invalid backup chain detected” message to the log. Such messages can be logged as warnings (default) or errors, depending on backup job settings. Why is it a potential problem if another software tool is also taking SQL Server backups? Note that copy-only database backups are ignored during backup chain validation, as they don’t interfere with the SQL Server backup chain. If a third-party software tool is taking copy-only SQL Server backups, those will not interfere with the backup chain so SQL Backup Master won’t warn about them. If you need to occasionally take a backup outside of SQL Backup Master (i.e. Rocscience Dips 7.016 Rocscience Examine2D 6.05 Rocscience Examine3D 4.0997 Rocscience ExamineTab v2.14 Rocscience Phase2 v8.024 Rocscience RocData 4.

Download SQL Backup Master 6.3.628.0