Jump to content

Search the Community

Showing results for tags 'DriveBender'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Covecube Inc.
    • Announcements
  • StableBit Cloud
    • General
  • StableBit Scanner
    • General
    • Compatibility
    • Nuts & Bolts
  • StableBit DrivePool
    • General
    • Hardware
    • Nuts & Bolts
  • StableBit CloudDrive
    • General
    • Providers
    • Nuts & Bolts
  • Other
    • Off-topic
  • BitFlock
    • General

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 1 result

  1. I'll start by saying that this isn't a "how do I migrate from DriveBender to DrivePool" post; I'm aware that that's already been covered. In a nutshell, my question boils down to something like "how do you organize your pool?" I'm not really asking a specific question expecting a 'correct' answer; I'm hoping to hear a couple of different ideas and suggestions regarding pool file organization. I apologize if this has been discussed before [it probably has], but I just haven't found those discussions yet. And I realize that on some level, this has nothing to do with drive pooling, except that in my case I'm considering migrating from one pooled structure to a different pooled structure with different capabilities. Background: I've been using DriveBender for several years, and I've had a lot of frustration with it recently. I always seem to have issues with 2+ drives at the same time -- it's never isolated to a single disk failure. It's happened enough that I don't believe it's coincidence. In addition, DriveBender rarely brings up all my mount points on the first "try" after a reboot or DriveBender upgrade. I usually have to keep rebooting several times before they will all come up. So, I've started researching alternatives, and DrivePool (+Scanner) looks extremely promising. I've just started a 30-day trial running DB and DP side-by-side with different physical disks. DriveBender and DrivePool seem to have different basic approaches when it comes to pools and mounts. DriveBender and DrivePool are similar in that they both support multiple pools consisting of one or more disks each. DriveBender then supports multiple mount points (drive letter or network share) within each pool. As far as I can tell, DrivePool doesn't have a similar structure; it just uses a single drive letter mount point per pool. I have the following setup with DriveBender: - 1 DriveBender pool - 7 physical disks (HDDs ranging from 1TB to 4TB) - 8 drive-letter mount points: M: (music), P: (photos), T: (TV and movies), U: (user files -- "my documents") etc. I like being able to separate these different types of files into different drive letters, while still using the same pool of physical disks. Using DrivePool, I started creating a similar structure of subdirectories on the pool drive, but I'm not crazy about it so far: \backup \docs \music \photos \software \video \tv \movies Once I get comfortable with it, I intend to remove the drive letters from the individual pooled drives so they don't show up in Windows Explorer -- I only want to access the drives via the pool (with duplication). I've seen some mention of using Windows' mount-point folder paths to do something like this, but I can't seem to find that thread again. So: what works for you? Thanks!
  • Create New...