Jump to content

Christopher (Drashna)

Administrators
  • Posts

    11572
  • Joined

  • Last visited

  • Days Won

    366

Posts posted by Christopher (Drashna)

  1. I believe you do need to remove the failed/missing disk before it will start re-duplicating the remaining data (should be *all* of it in that scenario). But as long as you have a copy of the data, it will try to duplicate it when it makes a duplication pass.

     

     

    When DrivePool makes a duplication pass, it compares the files. If it notices that one of the files doesn't match the other two, it would generate a warning and let you know. At that point, you can decide what to do.

  2. The actual pool should be fine. All the files are stored on normal NTFS volumes. and worst case, you can access files in the hidden "PoolPart.xxxx" folders. So the data should be fine.

     

    As for the software, try doing a clean reinstall when you are able to:

    http://wiki.covecube.com/StableBit_DrivePool_Q3017479

     

    That will clear all the settings, and files for DrivePool, and should allow you to install it without any issues.

     

     

    And just to re-emphasize: We are very very protective of your data. Disaster recovery was one of the top considerations for DrivePool when Alex initially designed it. As long as the drives are intact, (as in recognized by the system, and the partitions still there, and NTFS), then you can recover your pool. Even if that means reinstall the OS, or moving the drives to another system.  We value your data as much as you do, and have done everything in our power to make sure that DrivePool will *never* just "eat" your data.

  3. Glad to hear it. Performance is one of those things that we definitely take seriously and is a big thing for our products.  :)

     

    But WantStuff, have you disabled SMB Signing on your 2012 R2 Essentials Box? If not, you may want to do so. It may get you a bit more speed. :)

    Namely, SMB signing prevents "man in the middle" attacks. But if this is at home, a MITM attack means you're already screwed... And it adds additional overhead to each and every packet sent, slowing down network traffic. 

    It's entirely up to you whether you want to do this or not, but I do personally. But I also am going to be spending the money on ESET File Security soon (NOD32 doesn't install on Server SKUs, and Endpoint Protection is $$$$, while file security is like $45/year, give or take).

    http://mctexpert.blogspot.com/2011/02/disable-smb-signing.html

     

     

    And yeah, WHSv1 had some serious performance issues. I have a huge long thread at We Got Served about it, and a list of possible fixes... It was that bad.

  4. @x-ares-x:

    Yes, that is fine. you're router is adding it's name as a "dns suffix", and that may be normal for it.

    But yes, make sure you add the TCP port "27515" to the allowed list for your firewall, on the client. That or...

     make sure that the DrivePool.Service.exe file is added to the list of exceptions on both machines.

     

     

    @sspell: I used to use Symantic for firewall... till I discovered it's a bit overzealous, as you're noting. 

    Make sure you add said port the the "allow" list, as a network Service, If you haven't already.

  5. I'm sorry to hear about the hardware failure, that's never fun to deal with. :(

     

    And depending on how old that card is, I would see about RMAing it. Worst case, so you can resell it (as new, even) and recoup some of your cost (or just add it so you have more eSATA ports, etc).

  6. You cannot encrypt the DrivePool drive, but you CAN encrypt the disks in the pool. 

     

    The BitLocker setting that otispresley mentions is specifically for that purpose in fact.

     

     

    However, you will need to unlock each disk before the pool will become available. And you'll have to do this each time you reboot. And the simplest way to accomplish this is to encrypt the system drive as well. That is the only way to automatically unlock the encrypted drives. And if you don't have a TPM module on your motherboard (95% chance that you don't, they're not standard).... then you'll need to use the password/usb drive method to encrypt/unlock the system.

  7. DrivePool will see the Storage Space as one gigantic drive.  In fact, Storage Spaces works so low level, that nothing but it sees the individual drives.

     

     

    And yes, you'd want to move the data off of the Storage Space before breaking it. After you break it, I believe you'll have to initialize the disks (just like a brand new disk).

     

    Additionally, if you have enough spare drives (to equal the capacity of the "Space"), you may be able to add the Storage Space to a new pool, and add the additional drives to the Pool as well, then move Storage Space's content into the hidden "PoolPart.xxxx" folder. In that folder, it would be considered part of the pool, and subject to duplication and balancing. You could then duplicate the entire Pool. Once that's done, you could just break the STorage Space, which will cause a "Missing disk" error in DrivePool, which you can then just remove the now missing disk and add the individual disks into the pool.

  8. Do you mean backing up to the pool, or backing up of the pool. 

     

    If you mean "of" the pool, DrivePool does not support VSS (Volume Shadowcopy Service). That means it doesn't support Windows Backup right now. You can, however, backup the individual drives.

    If you mean "to" the pool, it should backup to the pool just fine. 

×
×
  • Create New...