SQL Server AlwaysOn AG automatic initialization (12)

when not to use automatic seeding

In some cases, automatic seeding may not be the best choice for initializing secondary replicas. During automatic seeding, SQL Server performs a backup over the network for initialization. This process can be slow if the database is very large or the secondary replica is a remote copy. The transaction logs for these databases cannot be truncated during the backup process, so if the busy database initialization process takes a lengthy time, the transaction log may increase significantly. Before you add a database to an availability group with automatic seeding, evaluate the database size, load, and site distance between replicas.

Automatic seeding will block full backups

During automatic seeding, perform a full backup at the same time. View process information by using the following statement.

Selectr.command,r.wait_type,r.wait_resource,db_name (tl.resource_database_id) as [Database_name],tl.resource_type , tl.resource_subtype,tl.request_mode,tl.request_type,tl.request_status,r.session_id as blocked_session_id, R.blocking_session_idfrom sys.dm_tran_locks as Tljoin sys.dm_exec_requests as Ron tl.request_session_id = R.session_ Idwhere tl.request_session_id = <concerned session>

View the VDI backup line Cheng plug 102

And 102 is waiting for u lock.

SQL Server AlwaysOn AG automatic initialization (12)