Jump to content
Covecube Inc.


  • Content Count

  • Joined

  • Last visited

Posts posted by Rec0n

  1. On 7/19/2017 at 3:45 PM, Christopher (Drashna) said:
    1. Deactivate the license on the old system
    2. move the drives over to the new system
    3. install the software
    4. activate the license

    That's it.  The software will see the pooled drives and automatically recreate the pool.  Duplication information will be retained, but balancing information won't be.  

    You may want to reset the permissions on the pool, but that depends on if you customized them or not.

    Hi Christopher, is the above still true for the current DrivePool version etc?

    My situation is that I am running a Win10 install (installed on a seperate SSD) on a HP N54 microserver with 4 x additional HDD as the pooled drives. I need to consolidate a couple of other machines that run at home into a single physical machine to lower power usage, so I need to create a couple of virtual machines for that.

    If I simply move the SSD and the 4 x HDD to a new box with plenty of grunt, the transition of the Drive Pool is done as above?


  2. 15 hours ago, Jaga said:

    Macrium Reflect (Free or Paid).  If you don't need the server edition (which is paid software to run on Windows Server), it does a fantastic job with all kinds of backups, custom settings, schedules, recovery media, etc.  Even after I do my next server upgrade to WSE 2016, I'll probably -still- keep all my workstations/laptops on Macrium Reflect.  For me it's largely fire-and-forget, and I check backups by simply looking at the Backup Folder repository to ensure they actually kicked off and completed correctly.  No management console required for that.

    They do have a "Site Manager" package, which is paid software with a 30-day trial, in case you want to investigate that portion of their suite.  I've never used it, but it appears to be a central management and license distribution package, so that you can install/uninstall/manage/etc on connected workstations.


    As far as Veeam's ability to see network shares goes - have you tried mapping to the specific IP\share instead of using NetBIOS naming?  That  fixes the issue in some software.

    Good info Jaga, thanks.

    Do you mean UNC path for the backup? That's what I did...\\servername\backup folder

    Veeam are actually working on this anyway but so far the EASEUS software is doing a great job of backing up with minimum impact on the drive. Impressed so far.

  3. Hey all, I figure I would ask here because smart people use Drive Pool! :)

    I just got rid of WHS 2011 as my home server software due to unacceptable issues, unreliability and boot issues. Obviously it did have a great client PC backup system that worked fairly well where windows 10 does not.

    I am running a drive pool with first level folders that I map various users to on their PCs, so we are not talking high tech here! I gave VEEAM endpoint free a go, but it will not 'see' the network mapped drive I allocated for the backups. The permissions are all OK, just being a pain.
    I am now onto EASEUS ToDo backups which does backup to my 'home server' mapped network drive and seems to be OK, but what else is out there that you rate - free or paid if it is worth the investment - and are there any other Windows 10 friendly ones that would allow me to centrally administer the backups like my WHS software did?

    If I dont find anything better I will probs just stay with the EASEUS solution as it is pretty neat - unless VEEAM support can fix their issue.



  4. :angry:

    Much sadness.....for some reason my OS SSD will not boot now. It is not even recognised as a boot drive. Stoopid HP ProLiant microserver perhaps, but either way I have some diagnostics to do. It boots to my test mechanic HDD just fine. Strange...

    On a positive note, my DP files on my data HDDs are just fine. All I need is a platform that will boot and I will be back in business. I tell you, it is awesome knowing that my data is safe and accessible.


    edit: Tried everything I could think of and got to the stage where a Windows 10 repair install was next. Plugged in the bootable USB stick and the damned thing booted properly! I swear I am going to shift to Linux for this box!! It is driving me nuts. (not really because then I wont have DP....) So frustrating.

  5. Now I have a couple of follow ups that I reckon someone will spot pretty fast!

    Coming from WHS2011, my server folder structure was looking like this below. The main folder in use was the ServerFolders on which had all of my seperate locations as well as the client backup files.



    My issue is, when I try to map the folders as separate locations with their own drive letter again, they are setup differently. It used to be just (\\MYSERVER\FOLDER1), but now when I map them they are (\\MYSERVER\ServerFolders\FOLDER1)

    Firstly, I now needed to go into each individual folder and share it so I could map to it. I shared the main ServerFolders to all users but it didn't propagate down to the folders within.

    Second, can I get rid of the extra folders in the top folder structure and just create new 'user' folders in the root of the Drive Pool I have?

    Obviously I don't want to damage the files at all but I am assuming the pooled drive is going to allow me to just move whatever I want within it with no issues - just a bit nervous because I haven't actually created a new drive pool in the new Win10 environment to be able to see what it should look like.

    #seeking encouragement! :)


    edit:.....good grief...I just got to page 457 of the WGS Windows 10 home server book where it starts talking about DrivePool in detail as the better option. My questions have been answered I believe.
    If anyone has anything to add, feel free, but I can safely create my own top level folders and map to them individually if I need to .... :)


    edited edit: my original mapped drives now work as they did before (I named my server the same as it was) and all I had to do was login again once. Much happiness..

  6. 1 hour ago, Christopher (Drashna) said:

    I totally understand. The idea of losing your data ... is not pleasant, to say the least! 

    But you shouldn't have anything to worry about! 

    I believe I've already responded to that ticket, so you should be good to go! 

    Otherwise, you can always activate the trial license! 

    You have done exceptionally well and I really appreciate it. The measure of an IT choice imo is how well your product is supported, and there are none better than you and the team Christopher. Thank you for making me feel valued!!


  7. Thanks a lot guys. I think I made a great choice with this drive pool product in that case!

    i really appreciate the quick and positive replies. I think I just needed to see it con firmed so I didn’t have to worry about it all until I had time to arrange what I needed. The thought of losing my server data made me feel sick so your posts have lifted me for the day!

    i will report back my success when I am done and look forward to seeing my files again...

  8. Hi team,

    I have just had another let down with my WHS 2011 HP Proliant home server and am over it. I of course run DrivePool on the box but now that the OS SSD is failing to boot I want to know if I can install Windows 10 Pro as the OS and then recover all of my drive pool data?

    My plan would be to disconnect all of the data pool HDD (x 4), install Windows 10 Pro to the OS SSD and then install Drive Pool (assuming that the version for WHS that I purchased will also allow me to use it on Win 10) and then hopefully reconnect all of my data HDDs, reboot and watch the magic happen as DP rebuilds my stuff....Am I dreaming?

    Has anyone migrated their OS to Win 10 and used DP to reassemble and retain their data pool?

    I also plan to use VEEAM Endpoint Backup to cover my client computer backup tasks - if you have feedback for that I would value it.

    TIA for your input, cheers

  • Create New...