Comments
Sort by recent activity
Running the installer over an existing installation will upgrade the service and everything else just fine. The only difference with uninstalling and reinstalling is that the default folder for SQL Backup is simply 'SQL Backup' in version 5 and below, and is 'SQL Backup 6' for version 6.
Thanks. / comments
Running the installer over an existing installation will upgrade the service and everything else just fine. The only difference with uninstalling and reinstalling is that the default folder for SQ...
Using this article as reference, is the SQL Backup service executable (SQBCoreService.exe) already upgraded to version 6? In that case, it's probably the case where only the extended stored procedure has not been upgraded.
If that is the case, see the recommended steps in the above article to address this issue, and also possible workarounds.
Thanks. / comments
Using this article as reference, is the SQL Backup service executable (SQBCoreService.exe) already upgraded to version 6? In that case, it's probably the case where only the extended stored proced...
I may have worded my replies a little ambiguously. Two connections aren't 'really' needed for a restore. The problem is that the connection that issues the ALTER DATABASE [image] SET SINGLE_USER .. command is automatically set as the only user, even though it may not be 'using' the database in question.
SQL Backup requires a connection to issue a backup command, so it will be blocked by the above user (at least until the user disconnects).
Might be useful to have SQL Backup run a user-defined TSQL command before and after processing ... / comments
I may have worded my replies a little ambiguously. Two connections aren't 'really' needed for a restore. The problem is that the connection that issues the ALTER DATABASE SET SINGLE_USER .. comm...
Single user access won't work with SQL Backup restores. The reason is because one connection is used to issue the SQL Backup restore command (yours), and another connection is required to issue a regular T-SQL restore command to work with the virtual device (issued by SQL Backup to the SQL Server engine).
The workaround (though not perfect) would be to run a script prior to the restore to kill all other connections except for yours. / comments
Single user access won't work with SQL Backup restores. The reason is because one connection is used to issue the SQL Backup restore command (yours), and another connection is required to issue a ...
Just to elaborate a little further.
If you set the SINGLE_USER option from within Query Analyzer, it appears that it assumes that you will be accessing that single user database eventually, and disallows any other connections even though you may be connected to another database in QA. This is the connection that is blocking the restore. You can see this by running sp_who while SQL Backup is running, and identify the blocking connection.
The workaround is to disconnect the connection that set the database to single_user mode and start SQL Backup immediately before another user connects or simply set the connection back to multi user and hope SQL Backup connects before any other user.
You mentioned that you are restoring to two servers and only one fails. Was the other set to single user made prior to the restore too? / comments
Just to elaborate a little further.
If you set the SINGLE_USER option from within Query Analyzer, it appears that it assumes that you will be accessing that single user database eventually, and dis...
If you were to create a new SQL Server Agent job, are you able to select the new account as the owner of the job?
Thanks. / comments
If you were to create a new SQL Server Agent job, are you able to select the new account as the owner of the job?
Thanks.
Which account is being used to run the SQL Server Agent service?
As regards e-mail notification, SQL Backup only sends e-mail notifications on the backup/restore tasks that it performs. If the SQL Server Agent job itself fails to run, SQL Backup hasn't even had the chance to start, hence there is no e-mail notifications sent by SQL Backup. In these cases, you will need to use the SQL Server alert mechanisms. / comments
Which account is being used to run the SQL Server Agent service?
As regards e-mail notification, SQL Backup only sends e-mail notifications on the backup/restore tasks that it performs. If the SQL...
Have you updated the owner of the SQL Server Agent job that performs the backup task?
Thanks. / comments
Have you updated the owner of the SQL Server Agent job that performs the backup task?
Thanks.
The error indicates that the SQL Backup Agent service was unable to connect to the local SQL Server instance. Assuming that only the TCP/IP protocol has been enabled on the server side, your options are as follows:
- enable the shared memory protocol
Enable the shared memory protocol for both the server and client configuration.
- change the default port
Using the SQL Server client configuration utility, change the default port to which TCP/IP connections are made on the server.
- use an alias
Set up a TCP/IP alias using the SQL Server client configuration utilities. The alias needs to be identical to the SQL Server instance name, and map it to the correct port number.
- add a SQL Backup registry key
In the registry node HKLM\Software\Red Gate\SQL Backup\BackupSettingsGlobal\<instance name>, add a string value named SQLServerName. Enter the server name/IP address and the port number e.g. 127.0.0.1,1435
The first 3 options are SQL Server options, and would affect other applications running on the server. The last option is a SQL Backup specific option.
Thanks. / comments
The error indicates that the SQL Backup Agent service was unable to connect to the local SQL Server instance. Assuming that only the TCP/IP protocol has been enabled on the server side, your optio...
Yes, there was an error in the original script, but I modified it a couple of minutes later so it should work now. / comments
Yes, there was an error in the original script, but I modified it a couple of minutes later so it should work now.