March 30, 2015 at 12:13 pm
Last friday we added another node to the AG. We haven't added all databases to AG and left some to work it on today. This morning we started seeing the below errors. But they suddently stoppped. Is this something alarming?
Skipping the default startup of database 'xxxx' because the database belongs to an availability group. The database will be started by the availability group. This is an informational message only. No user action is required.
March 30, 2015 at 1:03 pm
as the error says , no user action required. It is telling the particular database is configured in AG and will be started by AG instead when it is tried to bring it up may be cause due to server restart or alter database statement. I would check the status of synchronization
March 30, 2015 at 1:08 pm
That message is expected when a database in an AG is started up (on server restart or failover, for example).
If you see that when you are intentionally restarting a node or initiating a failover, then there's nothing to worry about.
If you see that and you weren't expecting a server restart or failover, then it might be a bit concerning, but only because there was an unplanned restart or failover.
The message itself is benign.
Cheers!
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply