I would like to bump this back up as well.

We just experienced the same issue today with our FCI with a single AG.  We manually failed over the SQL...

1. The logs are present, but the part where the system databases are upgraded is missing from the logs for the instance that failed.

2. Correct. It shows that...

I ended up opening a support case with MS. That did not yield a solution as they were not able to determine that the system database upgrade step never...

I apologize. I just saw this response.

I never did get a Microsoft solution to the problem and I just modified the system procedure to solve the issue. Honestly,...

Just posting to keep this alive. I received only one response at the MS forum and it wasn't helpful and didn't address the fact that this definitely appears to...

Thanks for your help with this.

I pushed some transactions through and based on what I can tell, the issue I am seeing is due to the design of the cleanup process.

Basically, with multiple publications on...

Yes. This is how I was debugging and got to where I found that nothing was going to be deleted. Here is the output:

CutoffDate

-----------------------

2011-06-24 13:56:30.107

(1 row(s) affected)

DeleteAllBeforeThisXactseqno

----------------------------------

0x00

(1 row(s)...

I went through and checked this before as noted in my second post, but just to be thorough, I went through the queries again.

immediate_sync allow_anonymous ...

Yes. It is an interesting problem and has been bothering us for a few days now.

That is correct. There are no errors and the purging works fine when...

We are using the default values for the retention period. Immediate sync is false.

Just to be clear, commands are purged just fine for the transactional repliacation by itself, but...