Solved
Our DB team wants to upgrade our largest and most active sql server.
I would like to convert it to vvol architecture prior to the upgrade. Can it be converted live like a storage vmotion or would I need an outage window?
- ty again jase
Forum Discussion
- thank you all!
- Happy to help!
- be sure to use protection groups to snap all of the volumes for a database at the same time in the sql server. this way you will get consistent snaps of all of the volumes with database files and log files on them. dbas usually have them spread across multiple disks.
- hello mjacobson - I regularly migrate VMFS -> vVols -> VMFS in my lab and it is just a storage vMotion!
- Depends on how your SQL Server is consuming disks. VMDK? Storage vMotion Clustered VMDK? Storage vMotion, but you'll have to bring down some (VM) nodes & repoint after moving. pRDM? Power off and Storage vMotion or create new (empty disks) and overwrite from the pRDM/snaps and still true if clustering in having to bring nodes down and repoint vRDM? Storage vMotion, but still true if clustering in having to bring nodes down and repoint
- jase covers more SQL use cases, i assumed non-clustered VMFS. thanks jmccarty!
- yes non clustered, just vmfs
- What's a good snap policy for sql servers in general? sql on vvol is fairly new to me, i'm still trying to figure out best practices.
- the one in question is 24tb
- Really depends on your RPO requirements, your data change rate, and your capacity.
