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

Can migrate files to our NAS but can't browse them

We have a NAS and a Nasuni appliance. Although we can migrate files to shares on these devices, their shares no longer show up in the Storage Resource list (and rebuilding/discovering doesn't find them.) The only way I was able to get a new policy that had the Nasuni as its target was to export a policy we already had, then re-import it with a new name. Or, in one case, I created a group policy with one of our little local test shares as the target, edited the XML to have the Nasuni shared path in there instead, then re-imported it.

We have a DFS set up with both the Nasuni and NAS associated to it, and the NSMProxy group has delegation rights. And I don't believe anything with the configuration of NSMProxy rights has changed.

We upgraded our NSM to v4.0.0. We can't say 100% for sure that our resource list went wrong after that, since the list seems to stick around until it's rebuilt etc. - but it's a possibility. Any thoughts? We're open to suggestions. I can get around it by doing the export, editing the XML, then importing again, but it's a bit awkward.
  • 0
    On 10/24/2014 12:06 PM, kborecky wrote:
    >
    > We have a NAS and a Nasuni appliance. Although we can migrate files to
    > shares on these devices, their shares no longer show up in the Storage
    > Resource list (and rebuilding/discovering doesn't find them.) The only
    > way I was able to get a new policy that had the Nasuni as its target was
    > to export a policy we already had, then re-import it with a new name.
    > Or, in one case, I created a group policy with one of our little local
    > test shares as the target, edited the XML to have the Nasuni shared path
    > in there instead, then re-imported it.
    >
    > We have a DFS set up with both the Nasuni and NAS associated to it, and
    > the NSMProxy group has delegation rights. And I don't believe anything
    > with the configuration of NSMProxy rights has changed.
    >
    > We upgraded our NSM to v4.0.0. We can't say 100% for sure that our
    > resource list went wrong after that, since the list seems to stick
    > around until it's rebuilt etc. - but it's a possibility. Any thoughts?
    > We're open to suggestions. I can get around it by doing the export,
    > editing the XML, then importing again, but it's a bit awkward.
    >
    >

    kborecky,

    Please make sure of the following:

    1. The NAS device needs to be joined to your domain/forest.

    2. The NSMProxyRights group needs to be a member of the local
    Administrators group on that NAS device's computer object. Depending on
    the NAS device's architecture, it may also need to be equivalent to 'root'.

    3. The 'dNSHostname' attribute on the computer object needs to be
    populated with the fully-qualified DNS domain name for the NAS device;
    this is often left with a null value by default when NAS devices are
    joined to a domain.

    4. If this is not a NetApp or EMC Celerra / Isilon NAS device, add the
    following string (no quotes) to the 'Description' attribute on the
    computer object: "***SRExperimentalNASDevice***".

    5. Make sure the NSMProxyRights group has "Full Control" on each CIFS
    share you want NSM to manage on the NAS device. "Write" is insufficient.

    Once all of that is done and verified, rebuild your Storage Resources list.


    -- NFMS Support Team