The In Progress tab

The In Progress tab shows the progress of SQL Backup Pro backups and restores for whichever SQL Server instance or database is selected in the Registered SQL Servers pane. You can also see if a backup is being uploaded to hosted storage (SQL Backup Pro 7.3 and later). To update the details, on the View menu, click Refresh Connection.

Transaction log backups currently being copied to a network location (for example, during log shipping) are listed in the Log Copy Queue tab.

Backing up and restoring

An entry is displayed for each database that is currently being backed up or restored.

Any network resilience settings you have selected (on step 4 of the Back Up wizard, step 5 of the Schedule Backup Jobs wizard, or using the DISKRETRYCOUNT and DISKRETRYINTERVAL options) will apply when writing the backup to disk or restoring from the backup.

When the backup or restore completes, the entry is removed from the In Progress tab and an entry is added to the Activity History. For more information, see The Activity History.

You can also use the sqbstatus extended stored procedure to view the active SQL Backup Pro backup and restore processes from within your SQL application (for example, SQL Server Management Studio).

Copying backups to hosted storage

Copying backups to hosted storage is only available in SQL Backup Pro 7.3 and later.

If you select the option to copy a backup to hosted storage (step 3 of the Back Up wizard or step 4 of the Schedule Backup Jobs wizard) or add COPYTO_HOSTED to a backup script, the backup is first written to disk, then added to the queue for uploading to hosted storage.

When a backup is added to the upload queue, it is listed in the In Progress tab with the status Pending. If a backup is split into multiple files, each file is listed separately. When a file is being uploaded, the status changes to Uploading.

The upload schedule

If SQL Backup Pro fails to upload a file to hosted storage, it will try uploading the file again according to the following schedule for up to 24 hours:

Upload attemptUpload attempt is made
22 minutes after the 1st upload attempt failed
34 minutes after the 2nd upload attempt failed
46 minutes after the 3rd upload attempt failed
58 minutes after the 4th upload attempt failed
610 minutes after the 5th upload attempt failed
All subsequent uploads10 minutes after the preceding upload attempt failed

The file status reverts to  Pending between upload attempts. To view information on the cause of the failure, right-click the entry and select Show Log.

To cancel the upload of a file once it has been added to the queue, right-click the entry and select Cancel Upload.

Once a file has been uploaded or the maximum number of retries has been attempted (or if the upload has been cancelled) the entry is removed from the In Progress tab. The Backup Properties for the backup (accessible from the Activity History) are updated to show the status of the file. When all the files in a backup have been uploaded (or the maximum number of retries attempted), the entry in the Activity History is also updated. For more information, see The Activity History.

Changing the upload behavior

You can change the upload behavior by creating and editing registry entries in the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQL Backup\BackupSettingsGlobal\<instance name>

Changes to this registry key will not take effect until you restart the SQL Backup Agent service.

Registry entryTypeDescription
COPYTO:CopyIntervalInMinutesDWORDThe initial interval between upload attempts (2 minutes by default).
COPYTO:MaxCopyIntervalCountDWORDThe number of upload attempts for which the interval to the next upload attempt is increased (5 by default).
COPYTO:ExpiryIntervalInMinutesDWORDThe maximum time to continue with upload attempts (1440 minutes by default).
COPYTO:ThreadCountDWORDThe number of files that can be uploaded simultaneously (5 by default). Maximum value is 10.

The interval between upload attempts after the number of attempts specified by COPYTO:MaxCopyIntervalCount is derived by multiplying COPYTO:CopyIntervalInMinutes with COPYTO:MaxCopyIntervalCount. For example, using the default values, this is 2 x 5 = 10 minutes.

Creating or editing these registry entries will also affect the behavior of the Log Copy Queue.

Didn't find what you were looking for?