Hi ,
read my scanrio ,
There are 40 databases in alwayson group.
My Steps:
For a patch update I was removed a database from alwayson group, The database name is PRODmainDB.
Suspended data movment in primary server.
Patch update completed.
Resumed data movment on primary server.
Took a full backup of the PRODmainDB database .
Restore the full backup with norecovery in secondary server. Here is a problem raised. When restore process reached 95% I got an error email as ,
Time-out occurred while waiting for buffer latch type 3 for page (1:9), database ID 25
.And some databases are went to suspended mode automatically. But in primary server everything fine. and another email ,
During redoing of a logged operation in database 'ProdDB2', an error occurred at log record ID (290:367:3). Typically, the specific failure is previously logged as an error in the Windows Event Log service. Restore the database from a full backup, or repair the database.
Restore process Completed .
Took a Diff backup in primay DB and retored in secondary with norecovery.
Took a log backup in primary DB and restored in secondary with norecovery.
Added the PRODmainDB to alwayson in primary.
Joined the PRODmainDB in secondary server.
Now I have manually resumed data movement.
Everything is fine now.
My question is,
Why some databases went to suspended mode during restore process?
What is the meaning of the error msgs.?
If I made any mistake How to avoid this in future?