Solved.

With 'differing ownership' as the clue I found the cause of the problem. It turns out that on one node, the account running the SQL services is a member of...

Hi Jeffery

Thanks for your reply.

1) Are you backing up to a network share, a backup drive in the same cluster group as SQL Server or to a share from a...

Hi MothInTheMachine

Echoing the sentiment of some of the other replies, I'm interested to know exactly what your CIO actually wants to achive. Does he/she really care about the size of...

Here's some code that will give you what you want.

SELECTBS1.database_name,

(SELECTsum()/128 from sys.master_files

where ((database_id = DB_ID(BS1.database_name)) AND (type_desc='ROWS'))) as database_size_MB,

ISNULL(DateDiff(minute, BS1.backup_start_date,getdate()) , 99999) as minutes_since_last_backup,

BS1.backup_start_date,

BS1.backup_finish_date,

cast(BS1.backup_size /1024/1024 as int) as backup_size_MB,

BF1.physical_device_name

FROM msdb..backupset...

If you are using SQL 2008 Enterprise Edition, you could try backing up with the native compression enabled. That'll probably drop the backup file size down below 500GB. But from...

Hi river1

The issue you are seeing is definately related to the flow control you have set up in the job.

I suggest you open the job, and check the steps very...

Hi OldHand

1) do i have to activate in the Surface area configuration the xp_cmdshell to use your procedure?

No. Thats not required.

2) Where do you stored this stored procedure?...

I use the following stored proc to delete old backup files as a step within a standard scheduled job.

usage: usp_DeleteOldBackupFiles <path>, <file extention>, <age_hours>

...

Just a thought.....are you backing up to an NTFS 'compressed' directory? If so, you'll have problems with files larger than ~30GB

Cheers

Thanks for your suggestions, but at this stage there really isn't a problem that needs solving. In fact, I'm not aware of any way to reproduce it. I suspect I...

Hi ALZDBA

My first thoughts were also that there was a problem with the SQL Service Broker(SSB). However, in addition to the deadlock events, we also use SSB to notify on...

Thanks egjorda - interesting thought, but in this case I don't think that snapshot isolation is the cause.

The 'issue' started just after midnight with no user intervention, and reverted back...