Back when I built this box, I did a "thin provisioning" on the Storage Space because I didn't know any better, creating a 16 TB logical volume with <<<<<<< 16 TB of actual, usable space.
This is biting me in the butt because nothing outside of the Storage Space control panel actually knows how much space I have available, and then things just fail.
So I want to delete the Storage Space and re-create it with thick provisioning (and ReFS), but without losing the backups in the repository. For a single logical volume on a Storage Space pool, there's no disadvantage to thick provisioning, because I can non-destructively increase the size of the volume later when I add or upgrade disks.
What's the correct procedure for doing that? Is it sufficiently safe to:
- Disable all jobs using that repo
- Copy the contents of the Storage Space volume to an external USB drive
- Delete and re-create the Storage Space properly, with original drive letter
- Copy the contents from the external USB drive back to the Storage Space volume, so that all paths remain unchanged relative to yesterday
- Re-enable the jobs
Or is there already a KB article that explains all of this?