Terminate Users in Logshipping Restoration.
deepakontheweb
Posts: 12
In RedGate SQL Backup v4.6.0.815, Is there any switch or option in logshipping restore command to terminate connected users on read-only standby database?
In SQL Server default logshipping options its very much avilable. While testing I am finding Red-Gate is unable to terminate usres by default.
BTW, is this feature avilable in latest versions?
****************** here is the error code*************
SQL Backup v4.6.0.815
Restoring Logshipping_test (transaction logs) from:
F:\Backups\Move\LOG_(local)_Logshipping_20070622_025403.sqb
VDI error 1010: Failed to get configuration from server. Check that the SQL Server instance is running, and that you have the SQL Server Systems Administrator server role. Error code: (-2139684861: The api was waiting and the timeout interval had
elapsed.)
SQL error 3013: RESTORE LOG is terminating abnormally.
SQL error 3101: Exclusive access could not be obtained because the database is in use.
SQL Backup exit code: 1010
SQL error code: 3101
(10 row(s) affected)
name value
exitcode 1010
sqlerrorcode 3101
filename01 F:\Backups\Move\LOG_(local)_Logshipping_20070622_025403.sqb
(3 row(s) affected)
Server: Msg 50000, Level 16, State 1, Line 6
SQL Backup job failed with exitcode: 1010 SQL error code: 3101
In SQL Server default logshipping options its very much avilable. While testing I am finding Red-Gate is unable to terminate usres by default.
BTW, is this feature avilable in latest versions?
****************** here is the error code*************
SQL Backup v4.6.0.815
Restoring Logshipping_test (transaction logs) from:
F:\Backups\Move\LOG_(local)_Logshipping_20070622_025403.sqb
VDI error 1010: Failed to get configuration from server. Check that the SQL Server instance is running, and that you have the SQL Server Systems Administrator server role. Error code: (-2139684861: The api was waiting and the timeout interval had
elapsed.)
SQL error 3013: RESTORE LOG is terminating abnormally.
SQL error 3101: Exclusive access could not be obtained because the database is in use.
SQL Backup exit code: 1010
SQL error code: 3101
(10 row(s) affected)
name value
exitcode 1010
sqlerrorcode 3101
filename01 F:\Backups\Move\LOG_(local)_Logshipping_20070622_025403.sqb
(3 row(s) affected)
Server: Msg 50000, Level 16, State 1, Line 6
SQL Backup job failed with exitcode: 1010 SQL error code: 3101
Comments
I'm sorry to say that SQL Backup 5 doesn't have an option to automatically boot all connections from a database before restoring to it. I think SQL Server 2005 can do this automatically, but this is a function of SQL Server and not strictly its' backup function.
I had posted a script earlier that might do the trick:
http://www.red-gate.com/messageboard/vi ... php?t=3958
You may try adding this somewhere in your backup job.