This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

DFS namespaces/folders not available in Storage Manager

What could be wrong, since we cannot see our DFS namespaces/target folders in Storage Manager to be added as policy targets? Server reboot and/or path rebuild did not help.

All traditional fileshares are ok and we have been using them for years. We are planning to migrate data to new server(s) and would like to use DFS from now on. Storage manager is running on one Windows 2008 R2 server and NSM version is 5.2.0.28. NSMProxyUsers-group has full control rights (Share and Security) to target folders. DFS and target folders run on Windows 2012R2 servers.

Any ideas?
Parents
  • On 11/6/2018 7:54 AM, kautium wrote:
    >
    > What could be wrong, since we cannot see our DFS namespaces/target
    > folders in Storage Manager to be added as policy targets? Server reboot
    > and/or path rebuild did not help.
    >
    > All traditional fileshares are ok and we have been using them for years.
    > We are planning to migrate data to new server(s) and would like to use
    > DFS from now on. Storage manager is running on one Windows 2008 R2
    > server and NSM version is 5.2.0.28. NSMProxyUsers-group has full control
    > rights (Share and Security) to target folders. DFS and target folders
    > run on Windows 2012R2 servers.
    >
    > Any ideas?
    >
    >

    kautium,

    DFS namespaces have special requirements (specified here:
    https://www.novell.com/documentation/file-dynamics-60/file-dynamics-6_1_admin/data/dfs.html).
    To summarize:

    * The Proxy Rights Group needs full control on the DFS target share AND
    the root DFS namespace share (on each server hosting the namespace.)

    * If there are multiple links in a DFS target, either only one target
    may be enabled, or the target description must indicate which target is
    preferred for Storage Manager / File Dynamics (explained more completely
    in the documentation linked above.)

    These are commonly overlooked issues when setting up DFS namespaces for
    use with File Dynamics / Storage Manager, so please make sure to read
    through the relevant documentation section and configure these
    namespaces appropriately. Thanks.

    -- NFMS Support Team
  • Thanks. I have read the documentation and we have rights set up as needed, but we still cannot see any DFS targets in Storage manager.

    At what intervall Storage Manager refreshes its list of available policy targets?
Reply Children
  • Just to clarify our situation and configurations a bit more:

    - We have one Windows 2008R2 Storage Manager server running version 5.2.0.28.
    - Storage Manager is configured to use AD group called "NSMProxyRights" that has only one user "NSMProxy".
    - We have configured one DFS namespace with two namespace servers that are both running Windows 2012R2.
    - Both DFS servers have been configured with full control share rights to NSMProxyRights group to this particular namespace.
    - Namespace has several "folders" that have been configured with only one folder target each.
    - Each folder target has been configured with full control share rights to NSMProxyRights group and that group also has full control NTFS rights to target folders.
    - Storage manager services have been restarted and server has been rebooted, but it is unable to see any DFS shares. Traditional shares use the same rights group and those are available and in production as we speak.

    What are we missing, or what could be wrong here?
  • GarethWilson;2492668 wrote:
    this was my issue

    https://forums.novell.com/showthread.php/480318-DFS-cluster-not-being-detected

    are you able to browse the dfs from nsm ?

    I forgot to update this. Yeah, we got this sorted by adding NSMProxy-account to local administrators on file server(s).

    NSM engine service crashed about 30 times while migrating home directories between targets and there was few other issues too, but anyway this is now ok.