›

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In with Google

Sign In Register
Our Sites

covecube.com 
community.covecube.com 
blog.covecube.com 
wiki.covecube.com 
bitflock.com 
stablebit.com 

Categories

Poll

No poll attached to this discussion.

In order to better support our growing community we've set up a new more powerful forum.


The new forum is at: http://community.covecube.com


The new forum is running IP.Board and will be our primary forum from now on.


This forum is being retired, but will remain online indefinitely in order to preserve its contents. This forum is now read only.


Thank you,


Sharing the ServerFolders folder

Freddan101Freddan101
edited July 2012 in DrivePool
I would like to have one mount pojnt for all DrivePool shares. Would it be ok to share the ServerFolder folder that resides in the pool disk (Z: in my case) and use that as a mount point on the clients?
Share on Twitter

Comments

  • ShaneShane
    Resident Guru
    The WHS wizard will not allow you to do this; it can however still be done by manually creating the share on the server (remote desktop, explorer, Z:, right-click ServerFolders, Properties, Sharing, Share or Advanced Sharing).

    Disclaimer: I'm neither recommending nor recommending against this, I'm just stating how it can be done. If it's just read-only access you're wanting, I don't foresee any problems, but if this "super share" will be writable then you're going to need to be careful not to accidentally break WHS in some way (minor or major).
    Share on Twitter
  • Freddan101Freddan101
    Member
    Exactly, I would like to share it "outside" Drivepool in the OS and the share would be writable. 

    What kinds of problem could I run into? Could I danger folder duplication or something else?
    Share on Twitter
  • ShaneShane
    Resident Guru
    * accidentally deleting or renaming WHS shares (if any) that are under your super share. In theory it shouldn't let you do this without at least a warning, but there's always a chance of blindly hitting "ok" on a warning prompt if you're in a rush. Been there, done that. :)

    * possibility of files/folders acquiring NTFS permissions that prevent normal users of the child shares accessing them. If this does happen, you can use the WHS dashboard to "change and then change back" permissions (and if that doesn't work, you can do it manually).

    * software you've pointed at the super share turns out to be buggy and trashes your 'work project' shared folder instead of saving to your 'meh whatever' shared folder.

    * folder duplication seems to be rather resilient (translation: I haven't broken it yet :p)
    Share on Twitter
  • Freddan101Freddan101
    Member
    Ok, sounds good to me. As long as I'm aware of that a user / application error could accidently delete the shares I should be fine. Maybe I could tighten the NTFS permissions on the top folders for users and Guest and leave full permissions for Administrator and System.

    I.e. folder duplication works regardless of writing data to the share ServerFolders or shares under it?
    Share on Twitter
  • ShaneShane
    edited July 2012 Resident Guru
    Yes, DrivePool's folder duplication operates at the file system level, not the network share level, so whether you're writing a file to \\server\documents or \\server\serverfolders\documents is irrelevant as far as DrivePool's folder duplication is concerned, so long as both map to the same folder at the file system level.
    Share on Twitter
  • Freddan101Freddan101
    Member
    Great, thanks for clearing that up. I will then go ahead with my "super share". :)
    Share on Twitter
Sign In or Register to comment.