Hi All,
We have implemented SQL alwayson on A-P cluster environment. The DB size is 390 GB. The fail-over mode is Automatic.
primary DB box: SQL1 (DB file hosted on local disk not on shared disk)
secondary DB box: SQL2 (DB file hosted on local disk not on shared disk)
when we reboot primary DB box, the DB is moving to secondary but DB status is showing recovery pending on secondary node (SQL2). It's taking 2-3 hours to complete recovery on SQL2.
when we reboot secondary DB box (after recovery complete), DB is moving to primary but again DB status is showing recovery pending. It will take 2-3 hours to complete recovery on SQL1.
During the reboot, DB is taking 2-3 hours time for recovery, Just for reboot my customer is not ready to give 3 hours downtime. Please suggest is this is SQL expected behavior or is there any changes required?