Can you post the errors you are seeing from each of the jobs on both the Primary and Secondary?  The backup, copy, and restore?

A couple of things you could check:

1. Make sure you are on the Primary server when configuring mirroring
2. Make sure you are restoring the latest Sql Server Transaction log of...

Does the VEEAM backup that runs and produces the I/O messages include Sql Server databases, or, are they separate?   As a start, I would probably review the backup setup you...

I think you may be missing the Virtual IP address for the instance above:

1 x windows cluster ip

1 x SQL server instance virtual ip (missing above)

1 x MSDTC virtual ip...

Have you seen these generate drop and create scripts?  https://www.mssqltips.com/sqlservertip/3441/script-out-all-sql-server-indexes-in-a-database-using-tsql/

I just tested them and I do not see constraints in the results, which is what you are requesting...

CheckDB when running primarily effects IO for the TempDB database and not so much on the database you are running it on.  Try running your query against TempDB while CheckDB...

Yes, that is fair to say and very true.  There could very well be a case where either a login or new job could get missed due to timing of scripts...

Is it possible to use AGs in a way to function exactly as the FCI did (keeping automatic fail over and the ability to manually fail over to patch while...

Hi, Log shipping does these exact steps.  If you have already considered Log Shipping, what different behavior are you looking for?

Every AG I set up had to have it's own listener.  Each Listener has its own static IP and Port number defined when it is created.  I don't see how...

I would start by running a "validate a configuration wizard" to check your network configuration from Failover Cluster Manager from one of the nodes.  From the message, it appears the nodes...

It appears you can simply alter the endpoint and change the IP address instead of recreating the listener:

With this code -

ALTER ENDPOINT [MyEndpoint]

STATE = STARTED

AS TCP (LISTENER_PORT = 5023, LISTENER_IP...

Taking a look at your dropbox, waits #2 and #3 both could point to problem with I/O and slow disks.  Are you reading and writing to fast disks?  Your number...

Just to add, you could make sure the Model database has this setting off so newly created databases do not inherit this setting.

Typically, for an Always-On setup, you will need:  1) Cluster name + IP  2) Nodes with IPs 3) AG Names with IPs 4) Listener Names with IPs