Comments
Sort by recent activity
Deepak,
There is a problem in the GUI if you have VERIFY on that it does not clear from the In Progress window. Hopefully fixed in V 6. Not sure about the other problem.
Chris / comments
Deepak,
There is a problem in the GUI if you have VERIFY on that it does not clear from the In Progress window. Hopefully fixed in V 6. Not sure about the other problem.
Chris
This makes it sound like V 6 is further away than possibly expected. I thought that it was in Q2 200(/
Chris / comments
This makes it sound like V 6 is further away than possibly expected. I thought that it was in Q2 200(/
Chris
Priya,
What is the status of Bug Report reference number is SB-3550? Is it part of V 6?
Thanks
Chris / comments
Priya,
What is the status of Bug Report reference number is SB-3550? Is it part of V 6?
Thanks
Chris
Have you looked at the Most Populate Topics VDI error 1010 topic?
Chris / comments
Have you looked at the Most Populate Topics VDI error 1010 topic?
Chris
I am going to make this a feature request then.
if the backup fails because of an out of space issue then please DELETE the incomplete backup file from the disk.
You should be able to know that this was a disk full problem by the error messages that get thrown.
Chris / comments
I am going to make this a feature request then.
if the backup fails because of an out of space issue then please DELETE the incomplete backup file from the disk.
You should be able to know that thi...
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...