Quantcast
Channel: StableBit DrivePool
Viewing all articles
Browse latest Browse all 864

Migrating pool to new machine: sanity check

$
0
0

Hi

 

Appreciate if someone could give me feedback that the process I'm about to follow will work ok.

 

I'm currently moving my server duties from a machine running WHS11 to a new machine running win10 (I don't need domain controllers, client backups etc etc yet).

 

Old WHS11 machine has 4 drives all drivepooled and mapped as P:  Covecube scanner also running.

 

steps to take:

 

1. Install stable releases of drivepool and scanner on W10. Enable 30 day licences.

2. On WHS11 machine deactivate licences for Drivepool and Scanner

3. Transplant 4 drives to new W10 machine.

4. Add the 4 drives to drivepool.

5. Somehow, automagically, drivepool will recognise the old drivepool settings from the WHS11 machine and recreate same drivepool (as P:) ???

6. Check for consistencies/anomalies, correct as required.

7. Run scanner adding drives as required. Not sure if scanner will have to recheck all drives (currently being reported as healthy under WHS11). I assume it will have to.

8. Enable licences etc.

9. Be happy!

 

Is that it?

 

As a follow on I have installed Hyper-V within the W10 setup. That is working just fine. Question: Will the various VMs I create be able to see the pool as one large pool as well as read/write/delete?

 

many thanks

Edward


Viewing all articles
Browse latest Browse all 864

Trending Articles