Comments
Sort by recent activity
Try restarting the SQL Backup Agent service for that SQL Server instance. / comments
Try restarting the SQL Backup Agent service for that SQL Server instance.
When you say it didn't work, do you mean the authentication step failed, or that the transfer process failed entirely, or the file was transferred but there was no difference in speed? Thanks. / comments
When you say it didn't work, do you mean the authentication step failed, or that the transfer process failed entirely, or the file was transferred but there was no difference in speed? Thanks.
Try deleting the instance from the list of registered servers, then add the instance but this time select '1 week' for the amount of native backup and restore history to import. Is the activity history then displayed correctly? / comments
Try deleting the instance from the list of registered servers, then add the instance but this time select '1 week' for the amount of native backup and restore history to import. Is the activity hi...
Could you please provide the steps to reproduce the error? I created a job to back up some databases to run every 15 minutes. After some scheduled runs, I modified to schedule to back up every 45 minutes, which pushed the next run time to after the earlier scheduled run time. The schedule was still enabled within SSMS. Thanks. / comments
Could you please provide the steps to reproduce the error?I created a job to back up some databases to run every 15 minutes. After some scheduled runs, I modified to schedule to back up every 45 m...
You first need to install the SQL Backup server components on the SQL Server instance you want to restore the database on. Next, you need to run the restore using the SQL Backup extended stored procedure e.g. EXEC master..sqlbackup '-sql "RESTORE DATABASE att2000SQL FROM DISK = [c:\db.sqb]"'<br>The command you ran failed because SQL Server does not recognize SQL Backup-created backup files. / comments
You first need to install the SQL Backup server components on the SQL Server instance you want to restore the database on. Next, you need to run the restore using the SQL Backup extended stored pr...
SQL Backup uses its own compression engine to compress backups, and does not depend on SQL Server's compression support. You can use SQL Backup to create compressed backups on SQL Server 2000 instances and all subsequent versions. The only time SQL Backup relies on SQL Server's compression engine is when you need to compress TDE-enabled databases. In these cases, SQL Backup's compression engine is unable to decrypt and compress the TDE-enabled backup data effectively, and thus relies on SQL Server's support to compress TDE-enabled databases. / comments
SQL Backup uses its own compression engine to compress backups, and does not depend on SQL Server's compression support. You can use SQL Backup to create compressed backups on SQL Server 2000 inst...
Hi, no, it's not possible to upload to 2 different cloud storage providers using SQL Backup at this time. / comments
Hi, no, it's not possible to upload to 2 different cloud storage providers using SQL Backup at this time.
It isn't possible to set up two SQL Backup Agent services to serve a single SQL Server instance. There would be a conflict with the inter-process communication objects used for the SQL Backup extended stored procedure and the SQL Backup Agent. You would probably need to use third-party tools that can detect when a new backup file has been created, and upload the files to the appropriate cloud storage provider. / comments
It isn't possible to set up two SQL Backup Agent services to serve a single SQL Server instance. There would be a conflict with the inter-process communication objects used for the SQL Backup exte...
A common cause is when the connection to the network share is lost during the copying process. When SQL Backup then reattempts to copy the file at a later time, it detects the incomplete file and chooses not to overwrite it. To resolve this, use the option to overwrite existing files in the COPYTO location in the backup command via the FILEOPTIONS parameter. If you are not currently using the FILEOPTIONS parameter, then add FILEOPTIONS = 4 to the backup command. If you are already using FILEOPTIONS, add 4 to the current value. For more details, please see the FILEOPTIONS section in the help file (https://documentation.red-gate.com/sbu/scripting-sql-backup-pro/the-backup-command) / comments
A common cause is when the connection to the network share is lost during the copying process. When SQL Backup then reattempts to copy the file at a later time, it detects the incomplete file and ...
It appears that the database cannot be restored to its original location, because the path/folders do not exist on this machine. Try running this command: EXEC master..sqlbackup '-sql "RESTORE FILELISTONLY FROM DISK = [<backup file name>]"'to see where SQL Server will attempt to create the database files in. Create those folders first if possible. If not possible, then use the MOVE options to create the database files in a new location e.g. EXEC master..sqlbackup '-sql "RESTORE DATABASE mydb FROM DISK = [<backup file name>] WITH MOVE [mydb_data] TO [<fully qualified data file name>], MOVE [mydb_log] TO [<fully qualified transaction log file name>] " ' / comments
It appears that the database cannot be restored to its original location, because the path/folders do not exist on this machine. Try running this command:EXEC master..sqlbackup '-sql "RESTORE FILE...