Big news! The community will be moving to a new platform April 21. Read more.
Big news! The community will be moving to a new platform April 21. Read more.
Absent Member.
Absent Member.
1546 views

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 Likes
1 Reply
Absent Member.
Absent Member.

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
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.