Comments
Sort by recent activity
Okay Petey,
Something we will have to watch for in the future. Maybe I should suggest that the backup file be deleted if there is an error in the creation.
Chris / comments
Okay Petey,
Something we will have to watch for in the future. Maybe I should suggest that the backup file be deleted if there is an error in the creation.
Chris
Eddie,
Our situation is that we had enough disk space when the jobs started but we had a number run concurrently and they used up all the disk space. I am looking at the entries for one of the failed backups and it records a Warning 210 system error 112. This is followed by an error 620, SQL error 3013, SQL error 3271 and SQL error 3202. There is a number in the compressed size. The first time the the 241Gb shows a compressed size of 6.9Gb when it would normally be around 19Gb.
These jobs are run as SQL Agent jobs specifying verify. Is there a setting I should be adding to make sure the backup is deleted if it fails in the creation?
Thanks
Chris / comments
Eddie,
Our situation is that we had enough disk space when the jobs started but we had a number run concurrently and they used up all the disk space. I am looking at the entries for one of the fail...
Larry,
You are looking in msdb with your query. Outside of SQL Backup are you trimming the entries in msdb using SQL Server Agent properties/History? If you aren' then this may explain why your query in msdb is returning entries.
Chris / comments
Larry,
You are looking in msdb with your query. Outside of SQL Backup are you trimming the entries in msdb using SQL Server Agent properties/History? If you aren' then this may explain why your que...
I was told it was a cache problem that should be fixed in version 6.
Chris / comments
I was told it was a cache problem that should be fixed in version 6.
Chris
You using a domain account to run the jobs. This happens because SQL Agent has a problem with the domain controller so that it cannot work out who the Windows account actually is. If you stop/start SQL Agent this should be fixed.
Chris / comments
You using a domain account to run the jobs. This happens because SQL Agent has a problem with the domain controller so that it cannot work out who the Windows account actually is. If you stop/start...
Eddie,
Can you mention what new, improved features, will be in V 6 if you are allowed.
Chris / comments
Eddie,
Can you mention what new, improved features, will be in V 6 if you are allowed.
Chris
Thanks Colin.
I know it wont be needed to run on a higher level of SQL or Windows. I will wait for the announcement of version 6's release.
Chris / comments
Thanks Colin.
I know it wont be needed to run on a higher level of SQL or Windows. I will wait for the announcement of version 6's release.
Chris
As I said, it is down for version 5.5 coming soon.
Chris / comments
As I said, it is down for version 5.5 coming soon.
Chris
This is a known issue that should be fixed in 5.5 which is coming soon. It was hoped to be fixed in 5.4 but didn't make it.
Chris / comments
This is a known issue that should be fixed in 5.5 which is coming soon. It was hoped to be fixed in 5.4 but didn't make it.
Chris
Petey,
I had the same problem again this morning. It happens every 2 months. I had removed some DTA data from msdb to make its contents smaller but I had not shrunk msdb. The database is over 1.2 Gb but holds 200Mb of data. Can this problem occur even if the data content of msdb is nowhere near the actual size of msdb? Its also funny that it only happens once every 2 months and I can nothing extra happening on the day it occurs.
Thanks
Chris / comments
Petey,
I had the same problem again this morning. It happens every 2 months. I had removed some DTA data from msdb to make its contents smaller but I had not shrunk msdb. The database is over 1.2 G...