Comments
Sort by recent activity
Stopping the SQL Backup Agent service is the recommended way to stop active backups, though it will stop all active SQL Backup backups and restores. If you really must, you can kill the backup job using the 'kill' command in SSMS. Use sp_who2, look for the 'SQBCoreService.exe' process running the 'BACKUP DATABASE' command. There should be a few of those, look for the one with the highest CPUTime and DiskIO values. Kill the corresponding SPID. SQL Backup should show something like this in the log:
SQL error 596: Cannot continue the execution because the session is in the kill state. SQL error 3013: BACKUP DATABASE is terminating abnormally. SQL error 3271: A nonrecoverable I/O error occurred on file "SQLBACKUP_E28DB706-C3A0-4A60-BA2A-0531B0B8932B:" 995(The I/O operation has been aborted because of either a thread exit or an application request.). SQL error 3202: Write on "SQLBACKUP_E28DB706-C3A0-4A60-BA2A-0531B0B8932B" failed: 995(The I/O operation has been aborted because of either a thread exit or an application request.) SQL error 3204: The backup or restore was aborted.
To be sure that the process was stopped 'cleanly', check the msdb..backupset table to ensure SQL Server did not log the backup as a valid backup. If it did, that would be bad. If that was a full backup, it becomes the base for any future differential backups (at least until the next full backup). If it was a log backup, the log chain would be broken because you now have an incomplete backup file. So only do this if you understand the possible consequences and how to address them. / comments
Stopping the SQL Backup Agent service is the recommended way to stop active backups, though it will stop all active SQL Backup backups and restores.If you really must, you can kill the backup job u...
SQL Backup does not support the RESTORE LABELONLY syntax. The workaround is to use the RESTORE SQBHEADERONLY syntax, with the SINGLERESULTSET option and read the 4th line (File number) e.g. EXEC master..sqlbackup '-sql "RESTORE SQBHEADERONLY FROM DISK = [d:\backups\bfile_1.sqb] WITH SINGLERESULTSET"' If there is only a single backup set in that folder, or if the files making up the backup set can be identified via a search pattern, you can use a wildcard search e.g. EXEC master..sqlbackup '-sql "RESTORE DATABASE db1 FROM DISK = [d:\backups\bfile_*.sqb] WITH REPLACE"' If you have multiple backup sets in that folder, and all you want to do is to restore the latest full backup for a particular database, you can use the LATEST_FULL option. SQL Backup will collect all the relevant files and restore them for you, without you having to provide the names of each individual file e.g. EXEC master..sqlbackup '-sql "RESTORE DATABASE db1 FROM DISK = [d:\backups\bfile*.sqb] LATEST_FULL WITH REPLACE"' SQL Backup will look in the d:\backups\ folder, find all files matching the bfile*.sqb pattern, find the latest available backup set for the db1 database, collect all the backup files making up that backup set, and perform the restore. If the name of the restored database differs from the source database, use the SOURCE option to provide the name of the source database e.g. EXEC master..sqlbackup '-sql "RESTORE DATABASE db1_reporting FROM DISK = [d:\backups\bfile*.sqb] SOURCE = [db1] LATEST_FULL WITH REPLACE"' Here, SQL Backup will restore the database as db1_reporting, but will look for backup files created for the db1 database. Note that there are also LATEST_DIFF and LATEST_ALL options to automate restore tasks. / comments
SQL Backup does not support the RESTORE LABELONLY syntax. The workaround is to use the RESTORE SQBHEADERONLY syntax, with the SINGLERESULTSET option and read the 4th line (File number) e.g.EXEC ma...
SQL Backup logs all backup processes, regardless of the settings used. If you can't locate the record, would you be able to locate the SQL Backup log file for the backup process that created the backup file? You can use the SQL Backup GUI on the instance that created the backup to retrieve the log file for that specific backup, or you could look in the folders where the logs are created (default folder is C:\ProgramData\Red Gate\SQL Backup\Log\<instance name>) / comments
SQL Backup logs all backup processes, regardless of the settings used. If you can't locate the record, would you be able to locate the SQL Backup log file for the backup process that created the b...
Yes, please run the query on the instance that created the backup. / comments
Yes, please run the query on the instance that created the backup.
Could you please post the result of this query: EXEC master..sqbdata 'SELECT * FROM backuphistory a INNER JOIN backupfiles b ON a.ID = b.backup_id WHERE name = ''<your backup file name>''' / comments
Could you please post the result of this query:EXEC master..sqbdata 'SELECT * FROM backuphistory a INNER JOIN backupfiles b ON a.ID = b.backup_id WHERE name = ''<your backup file name>'''
Given that script you sent, the backups are not being encrypted in any way. If you run this command from Management Studio: EXEC master..sqlbackup '-sql "RESTORE SQBHEADERONLY FROM DISK = [<your backup file>]"' for any of the backup files that were created using the above script, does it prompt you to enter a password? / comments
Given that script you sent, the backups are not being encrypted in any way. If you run this command from Management Studio:EXEC master..sqlbackup '-sql "RESTORE SQBHEADERONLY FROM DISK = [<your ba...
Have you tried creating the folders (F:\hoit001 and G:\hoit001) and running the restore again? / comments
Have you tried creating the folders (F:\hoit001 and G:\hoit001) and running the restore again?
SQL Backup will not create new folders for the MOVE options, but will create new folders for backup locations and COPYTO/MOVETO locations. So one option would be to create the new folders by backing up a small database to the new folders prior to performing the restore e.g. EXEC master..sqlbackup '-sql "BACKUP DATABASE model TO DISK = [F:\hoit001\dummy_01.sqb], DISK = [G:\hoit001\dummy_02.sqb] WITH INIT"' / comments
SQL Backup will not create new folders for the MOVE options, but will create new folders for backup locations and COPYTO/MOVETO locations.So one option would be to create the new folders by backing...
Do the target folders (F:\hoit001 and G:\hoit001) already exist? Neither SQL Backup nor SQL Server will automatically create the target MOVE folders, you will need to create them manually prior to running the restore. / comments
Do the target folders (F:\hoit001 and G:\hoit001) already exist? Neither SQL Backup nor SQL Server will automatically create the target MOVE folders, you will need to create them manually prior to...
polikuj said:
A backup copy of the data is created and written to the physical backup device during the SQL Server database backup operation. So the message that SQL Backup does not create any temporary files on the system is false.
Could you please post some evidence that SQL Backup creates temporary files while it backs up a database? Thanks. / comments
polikuj said:
A backup copy of the data is created and written to the physical backup device during the SQL Server database backup operation. So the message that SQL Backup does not create an...