Migrating current to new
Posted: Wed Sep 26, 2018 2:09 pm
Hi,
I have been trialling Starwind VSAN Free for nearly 1 month now, and have learnt a lot through trial and error, articles, and good advise from support.
I know have an NFR License, as this is my Dev environment. I know how I want this to work for me, so I just wanted run this migration by you, incase there is anything I might have missed, which could caused a massive headache:
Current setup on each of the 2 Nodes:
1 x 6TB (no RAID)
1 x 6TB (no RAID)
Multiple devices setup (1TB - 2TB in size, total 6) with 10% L1 Cache in write-back mode.
New Setup on each of the 2 Nodes:
4 x 6TB (RAID10)
Multiple devices setup (2TB in size, total 4 to start with) with 10% L1 Cache in write-back mode.
Migration Plan:
1. Confirm all devices are in sync.
2. Stop the Starwind Service on Node 1.
3. Shutdown Node 1, and install additional drives, and setup as RAID10.
4. Powerup Node 1, create new devices, targets, etc. /// or Reverse the replication (see Q3 below)
5. Attach Hyper-V/ESXi Hosts to new targets, and perform VM Storage Migrations. /// may not be required (see Q3 below)
6. Shutdown Node 2, and install additional drives, and setup as RAID10.
7. Powerup Node 2, setup replica bits from Node 1, and allow replication to complete.
8. Attach Hyper-V/ESXi Hosts to new targets. /// may not be required (see Q3 below)
9. All works ok.
Questions:
1. Anything I've missed here?
2. I have 32GB RAM in each node, would be a good idea to go for 20% L1 Cache?
3. Should I replicate in reverse once Node 1 is ready with new RAID10, then do the same again, when i've configured RAID10 on Node 2, which saves me migrating VMs?
I have been trialling Starwind VSAN Free for nearly 1 month now, and have learnt a lot through trial and error, articles, and good advise from support.
I know have an NFR License, as this is my Dev environment. I know how I want this to work for me, so I just wanted run this migration by you, incase there is anything I might have missed, which could caused a massive headache:
Current setup on each of the 2 Nodes:
1 x 6TB (no RAID)
1 x 6TB (no RAID)
Multiple devices setup (1TB - 2TB in size, total 6) with 10% L1 Cache in write-back mode.
New Setup on each of the 2 Nodes:
4 x 6TB (RAID10)
Multiple devices setup (2TB in size, total 4 to start with) with 10% L1 Cache in write-back mode.
Migration Plan:
1. Confirm all devices are in sync.
2. Stop the Starwind Service on Node 1.
3. Shutdown Node 1, and install additional drives, and setup as RAID10.
4. Powerup Node 1, create new devices, targets, etc. /// or Reverse the replication (see Q3 below)
5. Attach Hyper-V/ESXi Hosts to new targets, and perform VM Storage Migrations. /// may not be required (see Q3 below)
6. Shutdown Node 2, and install additional drives, and setup as RAID10.
7. Powerup Node 2, setup replica bits from Node 1, and allow replication to complete.
8. Attach Hyper-V/ESXi Hosts to new targets. /// may not be required (see Q3 below)
9. All works ok.
Questions:
1. Anything I've missed here?
2. I have 32GB RAM in each node, would be a good idea to go for 20% L1 Cache?
3. Should I replicate in reverse once Node 1 is ready with new RAID10, then do the same again, when i've configured RAID10 on Node 2, which saves me migrating VMs?