How can we help you today? How can we help you today?
DonFerguson
Activity overview Badges (0) Posts (47) Comments (160)

Comments

Sort by recent activity
Matthew Flatt wrote: Hi, This seems like a strange issue, would you be able to send some SQL Backup log files which contain the error and the restore job prior also? If you could send them to support@red-gate.com quoting reference F0019058 that would be great. Thanks, I already precisely know why this happens. This is a request to allow a MOVETO to self recover when it does. The reason it happens is because I am log shipping a very large amount of databases and have configured things differently than the way the GUI wants to. I am using a RobyCopy process at the destination to move the files with the /M flag. The problem is one of timing. When SQL Backup finishes creating a .sqb file it closes it and then seconds later writes the LSN information. If the RoboCopy process happens to grab the file at the right time between when the file is initially closed and the time the LSN information is written in, then SQLBackup will retry and often subsequently succeed at writing the LSN. The problem is that since RoboCopy copied the file to the destination and the log shipping restore command is also successful at the target, it gets moved to it's final destination. In the meantime the file gets the Archive bit turned back on at the source side from the original backup with the LSN update. When this happens, RoboCopy copies the file once again to the destination. But when it restores the file and tries to move it, an error is thrown and it remains in the original destination. So in this case I need to have a way to tell it to go ahead and move this file with overwrite if necessary. That's how I manually fix the issue whenever I need to. I have tried to adjust the timing to minimize this as much as possible, but it still happens occasionally. The problem with the GUI config is that it needs to be set up on a database by database basis, and since I'm log shipping hundreds of databases, that doesn't work for me. The files where the failure occurs do not have LSN information in them. But they get overwritten by same files that do. So I don't currently have samples to send you, but since I already know how this happens, I don't feel it is necessary. / comments
  1. Community
  2. SQL Backup Previous Versions
  3. Log Shipping MOVETO failures
Matthew Flatt wrote: Hi, This seems like a strange issue, would you be able to send some SQL Backup log files which contain the error and the restore job prior also? If you could send them to sup...
0 votes
The broken link issue self resolved.  Likely it was fixed prior to you trying to reproduce it.  Thanks. / comments
  1. Community
  2. Redgate Monitor
  3. SQL Monitor 8.0.17 download link missing
The broken link issue self resolved.  Likely it was fixed prior to you trying to reproduce it.  Thanks.
0 votes
Installing 8.0.13 resolved the issue.  Thanks. / comments
  1. Community
  2. Redgate Monitor
  3. SQL Monitor Time is Incorrect Since Update 8.0.10
Installing 8.0.13 resolved the issue.  Thanks.
0 votes
Thanks for promptly confirming and creating an SRP. Yes, I can confirm that workaround is valid, but I look forward to this being fixed soon to avoid a rollback. / comments
  1. Community
  2. Redgate Monitor
  3. SQL Monitor Time is Incorrect Since Update 8.0.10
Thanks for promptly confirming and creating an SRP.Yes, I can confirm that workaround is valid, but I look forward to this being fixed soon to avoid a rollback.
0 votes
Me too.  Since upgrading to 8.0.11.14888, I noticed that alerts now appear to be in UTC time. / comments
  1. Community
  2. Redgate Monitor
  3. SQL Monitor Time is Incorrect Since Update 8.0.10
Me too.  Since upgrading to 8.0.11.14888, I noticed that alerts now appear to be in UTC time.
0 votes
With 8.0.12 comes a new problem.  Now I can't access alerts from the tiles on the dashboard.  This seems to hold true for systems on a different base monitor as well as on the primary.  I get the following: Sorry, this page cannot be found. This may be a mistake with SQL Monitor or you may have typed an invalid URL. If you think this is a problem with SQL Monitor please tell us. Return to Global Overview / comments
  1. Community
  2. Redgate Monitor
  3. SQL Monitor Time is Incorrect Since Update 8.0.10
With 8.0.12 comes a new problem.  Now I can't access alerts from the tiles on the dashboard.  This seems to hold true for systems on a different base monitor as well as on the primary.  I get the f...
0 votes
Rather than creating a custom sp_delete_backuphistory procedure, I found that simply adding the following indexes tremendously speeds up the backup history cleanup process. It also makes the SQLBackup code that retrieves the LSN information much more efficient. USE [msdb] CREATE NONCLUSTERED INDEX [idx_physical_device_name] ON [dbo].[backupmediafamily] ( [physical_device_name] ASC ) CREATE NONCLUSTERED INDEX [ix_media_set_id] ON [dbo].[backupset] ( [media_set_id] ASC This will hopefully resolve or at least mitigate the deadlock issue. / comments
  1. Community
  2. SQL Backup Previous Versions
  3. Deadlock Breaks Log Shipping
Rather than creating a custom sp_delete_backuphistory procedure, I found that simply adding the following indexes tremendously speeds up the backup history cleanup process. It also makes the SQLBa...
0 votes
Is SQL Backup set up to delete old entries in the backup and restore history tables in the msdb database? If this is set, the deletion process runs after every process, which may contribute to the deadlock issue. Actually no. But it turns out the a regularly scheduled execution of the sp_delete_backuphistory procedure was occurring at the same time the deadlocks were. So I have shuffled the schedule of that so it doesn't run at the same time the transaction logs run. I am using SQL 2005 and this procedure takes about 3 minutes to complete. It is set to delete everything older than 30 days and runs nightly. I may be able to create a custom version of this procedure (using a new name of course) that doesn't hold locks while it deletes the records. This may be a viable work around on my end, but the fact that the LSN information doesn't get recorded in the backup file when this happens, should still be fixed on your end. Another option might be to sort on file name instead of LSN information when using a wild card restore. / comments
  1. Community
  2. SQL Backup Previous Versions
  3. Deadlock Breaks Log Shipping
Is SQL Backup set up to delete old entries in the backup and restore history tables in the msdb database? If this is set, the deletion process runs after every process, which may contribute to t...
0 votes
Good to hear. / comments
  1. Community
  2. Redgate Monitor
  3. Major 7.1.4 Installation Bug (Can't set Base Monitor)
Good to hear.
0 votes
It looks like the download link now downloads a file named SQLMonitorWeb_7.0.11.7625; however, despite the name it is still version ..7623. I did a file compare between the 7623 and the 7625 version and they are identical. If 7623 is the latest version that's fine, I guess. But with the 7623 version installed, the SQL Monitor web page still shows that an upgrade is available. / comments
  1. Community
  2. Redgate Monitor
  3. SQLMonitorWeb_7.0.11.7625 download link broken
It looks like the download link now downloads a file named SQLMonitorWeb_7.0.11.7625; however, despite the name it is still version ..7623. I did a file compare between the 7623 and the 7625 versi...
0 votes
Total activity
280
Last activity
Member since
Following
0 users
Followed by
0 users
Votes
0
Subscriptions
73