alwayson只读节点数据文件的磁盘被写满该怎么办

本篇文章给大家分享的是有关alwayson只读节点数据文件的磁盘被写满该怎么办，小编觉得挺实用的，因此分享给大家学习，希望大家阅读完这篇文章后可以有所收获，话不多说，跟着小编一起来看看吧。

环境：
sqlserver alwayson架构
主节点1个
standby节点1个
辅助只读节点1个

问题：
辅助只读节点的数据文件和日志文件的磁盘被写满。
数据文件和日志文件在一个磁盘上。

解决办法：
增加一块磁盘。

1、修改文件的存放位置下次启动生效

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

这里只更改数据文件位置。

2、关闭辅助只读节点的sqlserver服务

3、把辅助只读节点上的数据文件拷贝到新的磁盘上，然后删除老数据文件

4、开启辅助只读节点的sqlserver服务。
等待辅助只读节点上数据库自动进行recovery

recovery完成后，可以看到alwayson状态还是不正常，数据还是没有同步。

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 (7249:925328:1) 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 970 second(s) (analysis 210572 ms, redo 491239 ms, undo 0 ms.) This is an informational message only. No user action is required.

需要在辅助只读节点上执行：

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 (7249:925328:1) was identified for the database with ID 5. This is an informational message only. No user action is required.

辅助只读节点开始追主节点日志，同步恢复正常。

以上就是alwayson只读节点数据文件的磁盘被写满该怎么办，小编相信有部分知识点可能是我们日常工作会见到或用到的。希望你能通过这篇文章学到更多知识。更多详情敬请关注蜗牛博客行业资讯频道。