Deleting Schedules

• 
  You should be able to find the task as a SQL Server Agent job. The backup portion of the log shipping task will be found on the 'live' database server and the restore portion of the log shipping task will be found on the 'standby' database server.
  
  You could also run the following query on the relevant database to check for the existence of the job:
  
  SELECT * FROM sysjobs a INNER JOIN syscategories b ON a.category_id = b.category_id WHERE b.name = 'Red Gate SQL Backup'

  petey May 01, 2006 20:56

  - 0 +
• 
  Thank you, I found them. I'm actually having another issue now with restoring the database,
  
  this is the statement
  exec master..sqlbackup N'-sql "RESTORE LOG [cdo_suite_dev] FROM DISK = ''D:\SQL Server\Logs\LOG__cdo_suite_dev_*.sqb'' WITH STANDBY = ''D:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\UNDO_cdo_suite_dev.DAT'', ERASEFILES = 14, FILEOPTIONS = 1, MOVETO = ''D:\SQL Server\Processed\''"'
  
  however i keep getting the error
  Restoring cdo_suite_dev (transaction logs) from:
  \SQL Server\Logs\LOG__cdo_suite_dev_20060502_180532.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
  
  
  
  ---
  
  
  The problem is even if the database is not in use (and at this moment i'm not showing any active sessions) But the VDI error 1010 is the one that I'm having the problem width, i'm not sure whats causing it..

  aaoudi May 03, 2006 01:30

  - 0 +
• 
  Could you run the restore command, and while it's running, run sp_who2 from another Query Analyzer session to check what's happening? There should be a 15 second interval between the start of the restore command until it times out.

  petey May 03, 2006 02:21

  - 0 +
• 
  Here you go,
  
  1 sleeping sa . . NULL LOG WRITER 0 0 05/03 01:06:03 1
  2 BACKGROUND sa . . NULL LAZY WRITER 0 0 05/03 01:06:03 2
  3 BACKGROUND sa . . NULL LOCK MONITOR 0 0 05/03 01:06:03 3
  4 BACKGROUND sa . . master SIGNAL HANDLER 0 0 05/03 01:06:03 4
  5 BACKGROUND sa . . master TASK MANAGER 0 4 05/03 01:06:03 5
  6 BACKGROUND sa . . master TASK MANAGER 0 0 05/03 01:06:03 6
  7 sleeping sa . . NULL CHECKPOINT SLEEP 0 0 05/03 01:06:03 7
  8 BACKGROUND sa . . master TASK MANAGER 0 0 05/03 01:06:03 8
  9 BACKGROUND sa . . master TASK MANAGER 0 553 05/03 01:06:03 9
  10 BACKGROUND sa . . master TASK MANAGER 0 0 05/03 01:06:03 10
  11 BACKGROUND sa . . master TASK MANAGER 0 0 05/03 01:06:03 11
  12 BACKGROUND sa . . master TASK MANAGER 0 0 05/03 01:06:03 12
  13 BACKGROUND sa . . master TASK MANAGER 0 16 05/03 01:06:03 13
  14 BACKGROUND sa . . master TASK MANAGER 0 3 05/03 01:06:03 14
  15 BACKGROUND sa . . master TASK MANAGER 0 0 05/03 01:06:03 15
  51 RUNNABLE ali S79586 . cdo_suite_dev SELECT INTO 62 7 05/03 10:04:40 SQL Query Analyzer 51
  52 sleeping ali S79586 . cdo_suite_trs AWAITING COMMAND 0 0 05/03 10:03:16 SQL Query Analyzer - Object Browser 52
  53 RUNNABLE ali S79586 . master EXECUTE 0 0 05/03 10:04:35 SQL Query Analyzer 53
  54 sleeping ali S79586 . cdo_suite_trs AWAITING COMMAND 0 0 05/03 10:03:19 SQL Query Analyzer - Object Browser 54
  55 sleeping VIRTUSAPP\administrator S79586 . cdo_suite_dev AWAITING COMMAND 188 76 05/03 10:04:05 MS SQLEM 55
  56 sleeping NT AUTHORITY\SYSTEM S79586 53 master RESTORE LOG 15 0 05/03 10:04:37 SQBCoreService.exe 56

  aaoudi May 03, 2006 10:03

  - 0 +
• 
  There appears to be 2 connections using the [cdo_suite_dev] database (IDs 51 and 55). These will block any further restores of trx logs.

  petey May 03, 2006 11:37

  - 0 +
• 
  ok i thought about that, and took care of it, now there are no connections to the database but here i tried this ... i set the database to multiuser however i get this message back,
  
  SQL error 4306: The preceding restore operation did not specify WITH NORECOVERY or WITH STANDBY. Restart the restore sequence,
  specifying WITH NORECOVERY or WITH STANDBY for all but the final step.
  
  
  I'm tring to do a restore a log for log shipping, now when i turn the database to Read-Only I get,
  
  SQL error 4306: The preceding restore operation did not specify WITH NORECOVERY or WITH STANDBY. Restart the restore sequence,
  specifying WITH NORECOVERY or WITH STANDBY for all but the final step.
  
  The same thing with and without, what settings should i have on my database, I dont know if i'm missing something or there is something wrong with the APP.. i'm at loss right now.. thanks for all the help so far.

  aaoudi May 03, 2006 12:03

  - 0 +
• 
  The usual restore sequence for trx logs is to restore with no recovery or in standby (read-only) mode, until you want to bring the database online.
  
  If you are trying to set up a read-only database now and want to avoid users connecting to the database while you are applying the trx logs, you could first restore the logs with the norecovery option e.g.
  
  sqlbackup '-sql "RESTORE LOG [cdo_suite_dev] .... WITH NORECOVERY" '
  
  and when the logs have been applied, switch to read-only mode e.g.
  
  RESTORE DATABASE [cdo_suite_dev] WITH STANDBY = ...
  
  However, when you need to apply more logs, you will need to get users off the database first.

  petey May 03, 2006 12:30

  - 0 +

Add comment

Please sign in to leave a comment.