I would start by reviewing the error in the EVENT VIEWER

If your packages won't work, compare the IS_TRUSTWORTHY setting for the original DB and the restored DB.
This setting is off by default on the restored DB.
Not much on...

Have you turned off the T-LOG backup job while trying to sync. This can cause synching to fail in my experience.
How often is the T-log being taken.

These are normally VM Backups that also backup the DB or something like COMMVAULT.

Thanks

I have worked in an environment that was setup in the way JP10 is describing.

2 FCI clusters + STANDALONE DR server.
Each FCI cluster having a AOAG replica.

Sorted was having a moment!!!

Jeff,

Very useful information. I didn't know that.

Thanks.

Talib

Whoops didn't read page 2 of this post T1117 already mentioned.

SQL Learner - VKG (12/31/2016)

---

And this is what we do on production environment :

1. 4 tempdb datafiles on Primary File Group with exactly same size (1024 MB) and same autogrowth...

DECLARE @ServerName NVARCHAR(256) = @@SERVERNAME

DECLARE @RoleDesc NVARCHAR(60)

SELECT @RoleDesc = a.role_desc

FROM sys.dm_hadr_availability_replica_states AS a

JOIN sys.availability_replicas AS b

...

Does the database have an owner if so which account is it.

OK Grant, I might finally start looking @Extend Events.

I have been avoiding it. Wish me luck.

I would try the default trace, if your qucik enough you may get some information of what caused the files to grow and at what time.

I set it up to run every minute. So it was continually looking to see if it was the PRIMARY or SECONDARY.