Just to see, I created new directories and modified my script and tried it again. So, maybe the folder permissions are not correct? I check permissions and everything looked good. So, I verified that the ‘C :\backup\key’ directories did exist, and that they were spelled correctly in my script.
My first thought was: The directory path must be wrong. Verify that you have write permissions, that the file path is valid, and that the file does not already exist. 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.When running that script, I was immediately greeted with the following error:Ĭannot write into file ‘C :\backup\key’. While for the majority of the users this is a huge advantage, some specific configurations are not handled. 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. 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.
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.
0 kommentar(er)
