Hi- New deployment part of a migration from 2010. 2013 made up of one CAS/MBX server, 2 MBX servers, all Hyper-V. All part of a DAG with dynamic quorum. I was shortsighted in planning and need to have more space on my DB volumes.
I can see two options: expand the current volume (It's not on SCSI, so I will have to shut down the server first), or
Create a new volume and move the DB to it.
If I expand the volume the DB is on, I came across one article saying it was important to put the node in maintenance mode first. This moves the database to another DAG member. Unfortunately, all three DAG members have the same issue. There is not enough disk space to move the DB to another member.
Do I really need to do this first? Isn't the point of a DAG to ensure services are still running if a member goes offline? Couldn't I just make sure the active DB is NOT on the server I'm shutting down? And can't I just reseed (update) the DB copy after I bring it back up?
Creating a new volume seems straight-forward enough.
Any advice or opinions?
Thanx
You should never, never doubt what nobody is sure about. -Willy Wonka