Jump to content
Covecube Inc.


  • Content Count

  • Joined

  • Last visited

  • Days Won


Posts posted by Umfriend

  1. So AFAIK, everything DP reports wrt space is in terms of actual disk space. Assume a Pool of 2 x 10TB drives, x2 duplication except for one folder named UDF (UnDuplicated Files).
    - Pool is empty and shows 20TB free
    - Save a 1TB file to the Pool. The Pool will show 2TB Duplicated and 18TB free.
    - Save 2 100GB files to UDF (two files because one would complicate a bit and cause Unusable for duplication, now one is on one drive, the other on the other). Pool will show 2TB duplication, 0.2TB unduplicated and 17.8TB free.

    A duplicated file is indeed seen as a single file _assuming_ you access the file through the Pool / DP. However, a x2 duplicated file is stored on two HDDs. Each has a hidden PoolPart.* folder within which the file resides. If you access the HDDs directly, you can see two files. In the above example, if you pulled one HDD (so it is still working) and put it into another PC, then yes, on that PC you can simply navigate to the PoolPart.* folder and find all your, duplicated, files (unduplicated is a matter of chance of course). DP stores everything in plain NTFS so that is nice from a recovery point of view.

    Now assume one of the 10TB drives crashes, hard. DP will put the Pool in read-only mode. You will add a new 10TB HDD to the Pool and remove (through the GUI) the faulty one. At that time, DP will check for duplication and find none are duplicated even though most should be. DP will then re-duplicate. Non-duplicated files stored on the faulty HDD are lost (barring recovery and/or actual backups).

    I guess that's basically it.

  2. Use remove. You can move through Explorer but if you do that you need to stop the drivepool service first. Moreover, once you start DP service, it may try to rebalance files back to other drives so you need to turn of balancing to prevent that from happening. Also, if you have duplication then you want to disable that first. Yes, it will all take some time but it has, AFAIK, never failed. Quick and dirty though... not that failsafe sometimes. And even cutting/pasting will take quite some time.

  3. 12 hours ago, easyrider said:

    I would still like to access the data on the single drives...

    In that case, remove the drive letters but map the drives to folders within the Pool. I don;t know exactly how that works but it can be done and has been discussed here in the fora.

  4. Somewhere on the map, left side, you can find an option "Mark all sectors unscanned" or something. That will kick off a new one typically. Start check does not do anything, I think, if according to the settings no drive needs to be scanned. You want Automatic Scanning Enabled (press that button until it says that). AFAIK, the scan time is set at the start of it scanning, not the end of it.

  5. Just a heads-up: Are you aware of the differences between WSE2019 and WSE2016? WSE2019 basically misses everything that made it sort of a SOHO-OS.

    If by "have an unlimited number of users back up to my server?" you mean the client backup function of WSE you're SOL. It is gone.

    AFAIK, Clouddrive (and I don't use it and know nothing about it) is a single user app. It does not allow multiple users to access/write the data. Check that first.

  6. On 4/13/2020 at 1:27 AM, puulima said:

     BUT: to the right of the "start check" and "stop check" buttons - the button is: "Start / stop automatically"

    t may be you actually want to press that button. It may then say "Automatic Scanning Enabled". Then you are good to go.

    It should scan again according to: Settings -> Scanner settings .-> Scanner.

    DP and Scanner are still actively supported and they are developing other stuff. It's just that they don;t come round these forums much as I see it. For actual support one can contact them through https://stablebit.com/Contact.

  7. I would suggest, again, a reboot.

    I am pretty sure you can kill the Scanner GUI through task manager. Scanning is a background process run by a service and should continue (check with ResMon). Then restatrt the Gui. My guess is it will be responsive.

  8. Know nothing about VMs bit could you simply reboot WHS? Scanner will be closed and resume where it left after boot ( it may say 0% but thatiis because Scanner expresses as part to be done when restarted. You can look at the disks' map to see this).

  9. I can help with some of these as I migrated to WSE2016 about 18 months ago (from WHS2011).
    1. I redirected all to my Pool and all goes well. You may get a message for certain folders like File History or somesuch (as DP does not support VSS/Shadow copies) but it should be fine.
    2. No clue, but together with 3, 4 and 6), I set up a hierarchical pool. So I have some HDDs as Pool A, x1 duplication, other HDDs as Pool B, x1 duplication, and then created a Pool C consisting of Pools A and B, x2 duplication. That way, I know that each file is write twice, once to some set of HDDs and the other to the other set of HDDs. I then backup only one set of these HDDs. I use the standard WSE16 Server Backup software and it does BMR as well.

    What I am unsure about is whether it is possible to have WSE16 Server backup write over the network in some way (q2, 3 and 6(?)) and I really doubt it will be able to write to a Pool, even if located in the same machine. Again because of VSS support. Moreover, I am *pretty* sure it will be impossible (or very very hard) to actually do a BMR from a Pool.

    What *might* work is if you use WSE Backup to a huge HDD in the same machine and then sync with the NAS? I'd do a recovery simulation though and again, you'd have to build a big BMR recovery HDD I would think.

    If your entire Server won't fit on a single backup HDD, then consider the following:
    1. Use WSE Server Backup for the boot/OS drive and related partitions only. Write to a HDD that is in that Server. Periodically swap it out for another HDD and rotate offsite.
    2. Use some sort of syncing software to sync the data between the Server and the NAS.

    I am not sure x2 duplication on both machines makes a lot of sense. I would have it one the Server, not the NAS. Also, even with syncing software, the use of Hierarchical Pools may be very helpful.

    Hope it helps.

  10. Yeah, so now you have

    Drive A + B = Pool X (with x1 duplication)

    Pool X + Drive C = Pool Y (with x2 duplication)

    You can choose to store files in Pool X (and then they will not be duplicated and present on Drive A and B )

    Or store them in Pool Y (and then they will be duplicated and present on Drive A/B for one instance and Drive C for the other instance).

    So you need to move the files from Pool X to Pool Y.

    The best way to do this is to "seed" them. You would:
    1. Stop the DrivePool service
    2. In drive A, locate the hidden Poolpart.* folder. The top level shows (part of) Pool X. Locate the hidden PoolPart.* folder within the first, that is (part of) Pool Y. Move files from the outer/first Poolpart.* folder to the inner/second PoolPart.* folder
    3. Do the same for drive B
    4. Start DrivePool service.

    DP will now, for Pool Y, find a shitload of unduplicated files and start a duplication run, in this case copying such files from drives A/B to drive C.

    Not sure what OS you use but you may need to keep in mind that shares do not automatically follow (i.e. in WSE2016 I would move ServerFolders through the WSE2016 dashboard, even if that takes a long time).

    As an aside, I would actually create three Pools. Pool X = Drives A/B, Pool Y = drive C and Pool Z = Pool X and Pool Y. I think it makes it easier to manage when adding/replacing drives. Only Pool Y would have x2 duplication. The procedure above still holds.

  • Create New...