Jump to content
Covecube Inc.

Umfriend

Members
  • Content Count

    931
  • Joined

  • Last visited

  • Days Won

    48

Posts posted by Umfriend

  1. What you can do is deactivate the license on the old machine, build/install the new one and active the license there. Write down or somehow copy the license key. Deactivating the key will not delete any files in the Pool. I think the Pool remains accessible just read-only perhaps.

  2. What I think I know and would do is : Yes, you can use the C:\ drive as part of the Pool. The OS itself won;t be in the Pool but part of the Pool will be written to the hidden Poolpart.* folder that will be placed on the C drive. Personally, I would consider doing it with a separate partition as it makes it easier to backup/restore/reinstall the OS itself.

    It is in fact possible to use one SSD with x2 duplication (even though I consider it a bug and would not do it). You would have to split the x2 Pool first into two x1 Pools and then create a Hierarchical Pool consisting of the x1 Pools and let that Pool have x2 duplication. You'd be doing a lot of seeding. The SSD would have to have two partitions, each would serve as SSD cache for the x1 Pools. Haven't done it, it has been written in the forums, I would not do it. AFAIK, there is no immediate/delayed duplication option in DP (but I could be wrong).

    Does Plex use Hardlinks? I don;t know Plex nor understand what hardlinks are but DP does not support them as I read on this forum. Still, many use Plex so some setup must be successful.

    Anyway, that is going to be a nice server (and network)! GL.

  3. How did you get it in?

    Some here use DP together with 3rd party parity software, I believe SnapRaid is most popular. Perhaps that would work for you but I would not be able to advise on how to do that.

  4. That ain't easy.

    Best thing for you, IMHO, is to have two Pools, one for the old drives and one for the new. Then copy from old Pool to new. Power off machine and disconnect all old drives.

    I realise this is different from what I suggested before but at that time I was not aware you wanted to have the old drives as sort of a backup. Also, this way the usefullness of the old drives as a backup will fade over time, I would expect, as it does not track changes/new files.

  5. With future products I would say the expectation is they will be there at some point.

    It is not that hard to find non-Helium drives as all helium drives I've seen explicitly advertise this. So if it is not stated then it is not Helium.

    Also, typically, if you can afford it, it is not a Helium-filled drive.

  6. If you use x2 duplication and want to use the SSD Optimizer plug-in, you'll need two SSDs (or play around with hierarchical Pools, then you can do it with one SSD (or at least that has been written here, I actually consider that a bug and maybe it is "solved" but I could tell you how to do it.)). And yes, I imagine that if you do it will make a difference when you upload that much provided that there is no other bottleneck (1Gb Lan for instance).

    On Clouddrive as a backup: No idea.

  7. So I think it is a matter of use case and personal taste. IMHO, just use one Pool. If you're going to replace the 5900rpm drives anyway over time anyway. I assume you run things over a network. As most are still running over 1Gbit networks (or slower), even the 5900rpm drives won't slow you down.

    I've never used an SSD Optimizer plugin but yeah, it is helpful for writing, not reading (except for the off-chance that the file you read is still on the SSD). But even then it would need a datapath that is faster than 1Gbit all the way.

    What you could do is test a little by writing to the disks directly outside the Pool in a scenario that resembles your usecase. If you experience no difference, just use one Pool, makes management a lot easier. If anything, I would more wonder about duplication (do you use that?) and real backups.

  8. 5 minutes ago, gd2246 said:

    Not true, you nailed it! :D

    A bit by accident as I did not really expect that simple thing to make such a difference. Anyway, you are welcome.

    What you say about the "Other", yeah, that is part of it. Donnow whether it can lead to more serious consequences but stopping the DP Service when you want to do your own file tranfers is best practice.

    Now to nitpick, SnapRAID is not a backup. Sure, it may save you from HDD failure to some extent but not against accidental deletions, theft, fire, simultaneous multiple HDD failure (and you got a few). If you value your data, you might consider a real solution. You wouldn't want to lose your personal copy of the entire interweb (91TB, uhm, wow!) :D

  9. BTW, if you move files among pooled-drives, I think it is strongly advised to stop the DrivePool Service (and restart it or reboot when done). Also, I realise it is painfully slow for you (and I have no clue as to what would be the cause of that) but in my experience, DP is really a fire-and-forget program. I wouldn't care if it took a month so to say, it works just fine while it is balancing.

  10. ltmgtfy:

    :D

     

    Anyway, if you must, I would recommend to read that thread first, especially the 3rd post. Moreover, IMHO it'd be beteer to split the OS drive into two partitions and only add the non-OS partition to the Pool (again, only if it really benefits you to use OS HW in the Pool).

     

    Edit: I should read better, the post I referred to is not quite what you ask. In any case I think the answer remains the same: Yes you can, questionable whether you should.

    Also, the actual OS install (say windows, the Program Files and Users folders etc) will not then end up *in* the Pool.

×
×
  • Create New...