I installed SQLBackupAndFTP about Christmas last year to automate my SQL Express backups. I never got around to fully testing it and testing a restore. When I decided to try to automate the backups again today realised that the service had been running in the background but failing to backup as the destination archive disk was full.
I tried editing the destination path but it still threw the same error reporting the old destination path.
I tried deleting that destination and adding a new one with the new path, same.
I tried un-installing the program with the delete back job data option ticked and re-installing, then setting a new Job, Same error. It is still trying to backup to the old now unused local archive disk.
Screenshots at:
As and update I tried searching the registry for X:\MSSQL\Backup and it only found an entry for SSMS.
Hi Leon_Coles,
It seems that the X:\MSSQL\Backup folder is used as your temporary folder and it can be changed at the “Temporary folder” section.
SQLBackupAndFTP works in the following way:
- Creates a backup file into a temporary folder
- Compresses the backup file into the temporary folder
- Removes the backup file after the compression
- Sends the compressed backup file to the selected destination places
- Removes the compressed backup file from the temporary folder
To resolve the issue, please set a temp folder that has enough free space to store the backup files and the compressed backup files at the same time.
If you have any other questions, please let us know.
Thank you and sorry for the inconvenience.