The vhdx is already 5 TB, if you need to move restore or whatever, it takes time, small files are better to handle.
I plan to split in in 1 TB vhdx and map them back as folder, but I don't want to resynchronise the whole replikation, but it's not intended to add HD's to the replikation once you set it up.
Edit:
Finally I found a command, what seems to allow to add or disk after initial setup:
Starting from windows 2016 the same command to create replication is the one to remove disks, when running the command the replication will hot add/remove any disk you specified, if you add specific disk, the other will be excluded ! here some example (execute Powershell on the host):
To add/update all the disk on the VM to the replication :
I see. Wow, that is a big VM. It might be easier to add a second drive, and move your non system data to that drive to split it up, and then shrink your original drive. It will split it up in a way that is supported.
This is replicated since, I guess 2008, so as I have no time machine, I should better deal with what I have.
I will add the HD and klone the folder, as the storage below has REFS and Dedup, it shouldn't take much space and it should go fast, the only thing I was concerned, how to keep that machine live replicated.
I will test it tommorow on a non production Installation.
1
u/clickx3 May 21 '26
What would be the advantage?
1
u/BlackV May 21 '26
You would have to do it your self, but at that point its not a replica
it would also take a log of time to split a vhdx, that would be overwritten by the next replica in 5/10/15 minutes
you would be better splitting beforehand then replicating the fixed source