Comments
Sort by recent activity
Excellent idea!
Thanks! / comments
Excellent idea!
Thanks!
thanks / comments
thanks
Hi Pete,
I don't this will work because Redgate will still processes all log files present in the log directory regardless of the log file timestamp.
What we have done is delay processing of individual log files by 4 hrs based on log file timestamp.
Ex.
We log backup our production database every 30 minutes and copy to standby. Our log ship job runs every hour and only processes the individual log files which are over 4 hrs. We have a custom script which looks at the individual log files in the log directory and grabs files based on filename timestamp to process.
ex. script
Declare int
Set @DelayMins = 240
create table #dir
(
[FileName] varchar(2000)
)
select @cmd = 'dir /B ' + @SourcePath + '*.sqb'
insert #dir exec master..xp_cmdshell @cmd
-- Delete anything which is not a log backup for this database
delete #dir
where [FileName] is null
or [FileName] not like '%.sqb'
or [FileName] not like '%^_log^_%' escape '^'
or [FileName] not like @DBName + '^_log^_%' escape '^'
-- Delete anything that is less than @DelayMins minutes old
delete #dir
where [FileName] > @LastFile
while exists (select * from #dir)
begin
select top 1 @filename = [FileName]
from #dir d
order by right([FileName],20)
if not exists (select 1 from #restores where [FileName] = @filename)
begin
print convert(varchar(25),getdate(),121) + ' Restoring ' + @DBName + ' from ' + @filename
set @StandByFile = 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Backup\UNDO_' + @DBName
-- Restore log
select @cmd = 'master..sqlbackup '
+ ' -SQL restore log '
+ @DBName
+ ' from disk = '''
+ @SourcePath
+ @filename
+ ''' with standby = '''
+ @StandByFile + ''''
exec(@cmd)
end / comments
Hi Pete,
I don't this will work because Redgate will still processes all log files present in the log directory regardless of the log file timestamp.
What we have done is delay processing of indivi...
This would be a great log shipping feature enhancement. / comments
This would be a great log shipping feature enhancement.
As I stated earlier: The debug version does display records now, however the following error appears in the properties section:
Connection Error: SQB Service did not acknowledge receipt of data.(WAIT_TIMEOUT) / comments
As I stated earlier: The debug version does display records now, however the following error appears in the properties section:
Connection Error: SQB Service did not acknowledge receipt of data....
The debug version of xp_sqlbackup.dll seems to have fixed the problem with the GUI client. / comments
The debug version of xp_sqlbackup.dll seems to have fixed the problem with the GUI client.
I am receiving this error after upgrading to 5.1 in the GUI engine.
System.InvalidCastException: Object cannot be cast from DBNull to other types.
at System.DBNull.System.IConvertible.ToInt32(IFormatProvider provider)
at System.Convert.ToInt32(Object value)
at _16._1(SqlConnection , _17 , Int32& , String& , Int32& )
at _16._1(SqlConnection , Int32& , String& )
at _16._1(Server , Int32& , String& )
at RedGate.SQLBackup.Engine.Server._10()
at RedGate.SQLBackup.Engine.Server.RefreshServerInformation()
at RedGate.SQLBackup.Engine.Server.OpenConnection()
Have followed the steps outlined in this posting with no success. (
1): Deleting records in msd tables
(2) removing entries from my documents folder
It appears that this error is only related to the GUI tool and not the master..sqlbackup procedure. All of our scheduled jobs which use this procedure are working. Our GUI is the one having issues with this error. Some of instances have this error and siome do not. Any idea what could be the issue? Any other work arounds? / comments
I am receiving this error after upgrading to 5.1 in the GUI engine.
System.InvalidCastException: Object cannot be cast from DBNull to other types.
at System.DBNull.System.IConvertible.ToInt32(IForm...
For the 8198 error message, make sure that your domain account name for the SQLBackup service exactly matches your what is in the windows domain. Ex. if the account is XXXX\sqlusr in the windows domain, make sure the account for the service mathes the exact syntax.
We discovered this issue since some of our servers use the Latin 1 General Bin collation. We had entered xxxx\SQLUSR for the sqlbackup service which due to our sql server collation was not matching the account in the windows domain. The end result was the sql error 8198.
Changing the service account to exactly match the account in the windows domain solved the issue. / comments
For the 8198 error message, make sure that your domain account name for the SQLBackup service exactly matches your what is in the windows domain. Ex. if the account is XXXX\sqlusr in the windows ...
The link for error 8198 fixed our problem. Bottom line is to make sure that your service account matches your collation. / comments
The link for error 8198 fixed our problem. Bottom line is to make sure that your service account matches your collation.