Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

What if the disk of the alwayson read-only node data file is full

2025-03-28 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Database >

Share

Shulou(Shulou.com)05/31 Report--

What this article shares with you is about what to do when the disk of the alwayson read-only node data file is full. The editor thinks it is very practical, so I share it with you to learn. I hope you can get something after reading this article.

Environment:

Sqlserver alwayson architecture

1 master node

1 standby node

1 secondary read-only node

Question:

The disk of the data file and log file of the secondary read-only node is full.

The data files and log files are on the same disk.

Solution:

Add a disk.

1. Modify the location of the file and take effect next time.

Alter database testDb modify file (name = testDb, filename ='G:\ SQL_DATA\ testDb\ testDb.mdf');-- alter database testDb modify file (name = testDb_log, filename ='G:\ SQL_DATA\ testDb\ testdb_log.ldf')

Only the location of the data file is changed here.

2. Disable the sqlserver service of the secondary read-only node

3. Copy the data file on the secondary read-only node to the new disk, and then delete the old data file

4. Enable the sqlserver service of the secondary read-only node.

Wait for the database to automatically recovery on the secondary read-only node

After the recovery is completed, you can see that the alwayson state is still abnormal and the data is still not synchronized.

AlwaysOn Availability Groups connection with primary database established for secondary database 'gbs' on the availability replica' BPM-NEW-DB02' with Replica ID: {b8841279-8139-43f8-ac69-827c302efd43}. This is an informational message only. No user action is required.

The recovery LSN (925328) was identified for the database with ID 5. This is an informational message only. No user action is required.

3369 transactions rolled forward in database 'gbs' (5:0). This is an informational message only. No user action is required.

Recovery completed for database gbs (database ID 5) in 970second (s) (analysis 210572 ms, redo 491239 ms, undo 0 ms.) This is an informational message only. No user action is required.

It needs to be executed on the secondary read-only node:

ALTER DB param option: RESUME

AlwaysOn Availability Groups data movement for database 'gbs' has been resumed. This is an informational message only. No user action is required.

AlwaysOn Availability Groups connection with primary database established for secondary database 'gbs' on the availability replica' BPM-NEW-DB02' with Replica ID: {b8841279-8139-43f8-ac69-827c302efd43}. This is an informational message only. No user action is required.

The recovery LSN (925328) was identified for the database with ID 5. This is an informational message only. No user action is required.

The secondary read-only node begins to chase the primary node log and the synchronization returns to normal.

The above is what to do if the disk of the alwayson read-only node data file is full. The editor believes that there are some knowledge points that we may see or use in our daily work. I hope you can learn more from this article. For more details, please follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Database

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report