Comments
Sort by recent activity
We do transaction logs once an hour, so it might have been jobs running at the same time.
So far there has only been this one occasion, so no alarmbells going off yet :-)
Regards,
Martin / comments
We do transaction logs once an hour, so it might have been jobs running at the same time.
So far there has only been this one occasion, so no alarmbells going off yet :-)
Regards,
Martin
:-)
Thanks. I must be blind.
Regards,
Martin / comments
:-)
Thanks. I must be blind.
Regards,
Martin
I have the same issue.
25 Servers imported and 10 of them has SQLBackup running on it.
The CPU will hoover around 65% with a huge cut into memory.
We run with 14 months of backup history.
Regards,
Martin / comments
I have the same issue.
25 Servers imported and 10 of them has SQLBackup running on it.
The CPU will hoover around 65% with a huge cut into memory.
We run with 14 months of backup history.
Regards,
...
Solved (!)
I did copy the "corrupt" backup file to another server to run the verify process again, and this time it went thorugh fine, something I looked upon with a mix of happiness and fear.
It was then I realized that our "verify process" had been running for more than 31 hours... in other words, the verify process was still running when the backup started, and I assume that created a clash with a warning message as a result.
This leaves the question of why the verify process did not complete, but I will investigate that further the next few days.
Thanks for your help.
Regards,
Martin / comments
Solved (!)
I did copy the "corrupt" backup file to another server to run the verify process again, and this time it went thorugh fine, something I looked upon with a mix of happiness and fear.
It w...
Asked before I was thinking!! I fond this (modified now) in the documentation
declare @datestamp varchar(30)
declare @databasename varchar(200)
declare @backuppath varchar(500)
declare @filename varchar(500)
declare @backupstring varchar(1000)
declare @failcount int
declare @failflag int
create table #resultstring (message varchar (2500))
set @failflag = 0
set @backuppath = 'E:\DBBACKUP\SQLBackup\'
set @databasename = 'pubs'
set @datestamp = left(replace(replace(replace(convert(varchar(30), getdate(), 120), '-', ''), ' ', ''), ':', ''), 12)
set @filename = @backuppath + @databasename + '_db_(full)_' + @datestamp + '.sqb'
set @backupstring = '-SQL "BACKUP DATABASE [' + @databasename + '] TO DISK = ''' + @filename + ''' WITH NAME = ''Database (' + @databasename + ') Full'', ERASEFILES_ATSTART = 1, COMPRESSION = 1" -E'
insert into #resultstring
exec master..sqlbackup @backupstring
select @failcount = count(*) from #resultstring
where patindex('%error%', message) > 0
if @failcount > 0 begin
set @failflag = 1
end
else begin
insert into #jobresults (message) values ('Backup succeeded: ' + @databasename)
end
drop table #resultstring
if @failflag = 1 begin
RAISERROR ('Backup failed to complete successfully', 16, 1)
end
Regards,
Martin / comments
Asked before I was thinking!! I fond this (modified now) in the documentation
declare @datestamp varchar(30)
declare @databasename varchar(200)
declare @backuppath varchar&#...