Simplest way to move target to different drive letter?

[wallewek]

I was setting up StarWind on my two-server HA lab cluster for the first time, and screwed up.

I was following the document "StarWind Virtual SAN Installation and Configuration of HyperConverged 2 Nodes with Hyper-V Cluster", which is quite good actually.

Both servers are configured identically, and both have matching large F: drives, which I was planning to use for the cluster and witness CSV targets. Unfortunately, I got mixed up somehow, and when I created the targets, I used the wrong (much smaller) partition and drive letter on one of the servers. I didn't notice until after I had already set the storage to CSV and migrated a test Hyper-V VM into it.

Now I need to move the storage and witness targets to the other drive letter on one of the servers.

If I understand correctly, I could probably stop everything, edit the iSCSI targets, move the files and folders to the right partition, edit something in the StarWind configuration file, and maybe get away with it. But it sounds like a really good opportunity to screw up even worse.

What's the simplest way to move the targets to a different physical partition and drive letter? Would it make more sense to stop the Hyper-V VM and export it somewhere, delete the targets (do I need to un-CSV them first?), recreate them in the right partition, re-HA them and restore the VM?

This seems like a fairly common thing to need to do, but I don't see it documented.

-- Ken

[Sergey (staff)]

Hello, Ken! Thank you for your question. Try to do the following:
- stop StarWindService from Services or running "net stop starwindservice" from Command Prompt;
- move the folder, containing StarWind image file to the right partition;
- update .swdsk file, located in the folder with StarWind image file. Change the path to a new one;
- edit .cfg file, located in C:\Program Files\StarWind Software\StarWind by default (update the path);
- start StarWindService;
- Fast Synchronization will be initiated. Let it sync;
- Do the same for the second node.
And don't forget to make backups!

[wallewek]

Thanks Sergey, this worked perfectly. In this case I didn't need to change the other server, as only one had misplaced storage.

And I have to say, I really appreciate all the in-line documentation in those configuration files. Very nicely done!

-- Ken

[Sergey (staff)]

Hello, Ken. Thank you for this feedback. Happy to help you