Sql-server – AlwaysOn Availability Groups log_send_rate

What it means is that the computer object of the cluster (within Active Directory) will have the same set of the permissions as the user that created the cluster (and in turn, the cluster computer object).

This cluster computer object will then be the security context when a cluster service or application needs to have a computer object created.

Think of it like this: Joe creates a cluster and the cluster computer object is Cluster1. When a computer object of the cluster needs to be created, it will be under the context of Cluster1. And Cluster1 will have the permission set of Joe.

Take a look at a blog post I wrote on this very topic (SQL Salt). Maybe that will shed a little more light on this. When you create a listener, for instance, auditing AD will show that it is the cluster computer object that is actually creating the listener computer object.

In many environments this elevated security for computer objects may be undesirable. Therefore you can pre-stage these objects within AD. The end result should be the same.

No, this is not possible with Availability Groups. Any incurred delays are usually from things like network, secondary replica log block flush, etc. There's no way that I can think of to turn that knob and create more of a time gap.

It sounds like if you want to take this "delayed transactions" approach, Log Shipping may have actually been the best solution there. Or you could just deal with point-in-time restores in the (hopefully corner) case of data manipulation errors. Ideally that wouldn't be happening all that frequently, and you should already have point-in-time restores as part of your operational capability, so you wouldn't need to incur any other additional technology of processes to accomplish this.