Comments
Sort by recent activity
Hi,
You can restore a backup from one server to an existing or new database on a different server using the Restore wizard (in v6.5 and v7+) or the Schedule Restore Jobs wizard (v7+ only).
To restore a backup to a different server using the Restore wizard:
- On step 1 select Browse for backups to restore from the drop-down list.
- Then specify the server you want to restore the backup to.
- Click Add files to open the File Browser and browse for backup files to restore. Backups stored on the server you are restoring to are displayed. You can view backups stored on another server by selecting the server from the drop-down list, or clicking Add server to add another server.
- Proceed through the rest of the wizard as normal.
Further information, including how to restore from a different server using the Schedule Restore Jobs wizard, is available here: http://www.red-gate.com/supportcenter/Content/SQL_Backup/help/7.1/SBU_BackUpRestoreNetworkShare
Finally, if you would like to evaluate SQL Backup 7, you can download a free trial from our website here: http://www.red-gate.com/products/dba/sql-backup/
I hope that helps.
Thanks,
Marianne / comments
Hi,
You can restore a backup from one server to an existing or new database on a different server using the Restore wizard (in v6.5 and v7+) or the Schedule Restore Jobs wizard (v7+ only).
To resto...
Hi Chris,
The version number in the About box refers to the version of the user interface, whereas the version number in the Server Properties dialog refers to the version of the server components.
I'll update the announcement to reflect this. Thanks for bringing this to our attention.
Marianne / comments
Hi Chris,
The version number in the About box refers to the version of the user interface, whereas the version number in the Server Properties dialog refers to the version of the server components....
Unfortunately there was a minor issue with our release process yesterday. This has been fixed and the Backup and Restore Bundle now includes SQL Backup 7.1.
Thanks again for bringing this to our attention.
Marianne / comments
Unfortunately there was a minor issue with our release process yesterday. This has been fixed and the Backup and Restore Bundle now includes SQL Backup 7.1.
Thanks again for bringing this to our at...
Hi Chris,
Thanks for bringing this to our attention. It should be sorted out soon.
Cheers,
Marianne / comments
Hi Chris,
Thanks for bringing this to our attention. It should be sorted out soon.
Cheers,
Marianne
Hi Chris,
Could you try upgrading again? Version 7.1 should be available now.
Thanks,
Marianne / comments
Hi Chris,
Could you try upgrading again? Version 7.1 should be available now.
Thanks,
Marianne
Hi,
Thanks for your post. When using the extended stored procedure, the parameters must be surrounded by one set of single quotes, so any variables inside the command must be surrounded by two sets of single quotes (or square brackets). If your database name includes spaces, you should surround it with square brackets, rather than two pairs of single quotes. Your command should look like this (replacing variables and WITH options as required): execute master..sqlbackup '-sql "BACKUP DATABASE [database name] TO DISK = ''C:\Backups\<AUTO>.sqb'' WITH CHECKSUM, THREADCOUNT = 3" '
(The disk location is surrounded by two sets of single quotes, whereas the BACKUP command is surrounded by one set of double quotes. The entire parameter is surrounded by one set of single quotes.)
There is more information about using the extended stored procedure here: http://www.red-gate.com/supportcenter/Content/SQL_Backup/help/7.1/SBU_UsingStoredProc and examples of SQL Backup syntax here: http://www.red-gate.com/supportcenter/Content/SQL_Backup/help/7.1/SBU_Toolkit_syntax_egs
If this doesn't help, can you post the exact command you are using?
Thanks,
Marianne / comments
Hi,
Thanks for your post. When using the extended stored procedure, the parameters must be surrounded by one set of single quotes, so any variables inside the command must be surrounded by two sets...
Hi Chris,
SQL Backup 7.1 will be released soon. We are expecting to release version 7.2 towards the end of Q3.
Cheers,
Marianne / comments
Hi Chris,
SQL Backup 7.1 will be released soon. We are expecting to release version 7.2 towards the end of Q3.
Cheers,
Marianne
Hi Chris
Apologies for not getting back to you sooner. This feature will not be in the next release of SQL Backup (7.1) but we are considering it for version 7.2.
I will add you to the list of users to be notified when this change is made.
Cheers,
Marianne / comments
Hi Chris
Apologies for not getting back to you sooner. This feature will not be in the next release of SQL Backup (7.1) but we are considering it for version 7.2.
I will add you to the list of user...
Hi
Thanks for both your forum posts. Can I check whether you added the sqbsetlogin stored procedure before calling it with blank values?
If the SQL Backup Agent Service was set to use SQL Server authentication when SQL Backup 6 was installed, the stored procedure will not have been added. If the sqbsetlogin stored procedure was used to change to SQL Server authentication later, it may have been dropped after use (as per the instructions in the forum post you refer to and Security Model (http://www.red-gate.com/supportcenter/Content/SQL_Backup/help/7.0/SBU_SecurityModel). In both these cases you would need to add the stored procedure again before being able to call it.
If this is the case, try adding the stored procedure:
execute master..sp_addextendedproc sqbsetlogin , 'xp_sqlbackup.dll'
Then call the stored procedure with blank values to use Windows authentication:
execute master..sqbsetlogin '', ''
Cheers,
Marianne[/code] / comments
Hi
Thanks for both your forum posts. Can I check whether you added the sqbsetlogin stored procedure before calling it with blank values?
If the SQL Backup Agent Service was set to use SQL Server au...
Hi,
It's the latter case: jobs that are scheduled to run at the same time are highlighted in the timeline as conflicting schedules to warn you of the demand on your server's processors and I/O. This may cause jobs to take longer to run.
Cheers,
Marianne / comments
Hi,
It's the latter case: jobs that are scheduled to run at the same time are highlighted in the timeline as conflicting schedules to warn you of the demand on your server's processors and I/O. Thi...