Well, I am afraid it is a bit more complicated ... 7.3.1.1 BSAG: Considerations If you install target expansion adapters on the system, you must configure the onboard adapters as initiators. 7.3.3 BSAG: The whole paragrah "Consderations" is no more there. The only limitation that is mentioned is total number of target HBAs and the rule that all target adapters must be of the same speed: you cannot mix 2-Gb and 4-Gb adapters on the same system The presentation mentions this rule only for target expansion cards: Can I mix expansion target cards in the same system of different speeds (X1130 4G & X1131 8G)? NO But if the rule of speed mix is for all target HBAs, it means - you can use onboard, as long as speed matches. Given that current HBAs are 8Gb/s, we have no way to mix them I'd love if someone from NetApp gave final word.
... View more
Base snapshot name includes filer sysid, so it is quite possible that changing hardware (i.e. getting new sysid) will generate new names for base snapshots. What I am not able to find – how SV base snapshots are structured (it could be described in paper training material which I do not have right now). For SnapMirror snapshot name includes destination sysid, which corresponds to secondary for SV. I do not know what –cleanup snapshots are. My guess would be, those snapshots can be removed, but let’s wait for someone with more SV experience to chime in ☺
... View more
Re. 3 – it is not what the latest ppt (edition 4) says: Can I have target expansion cards installed in the system and still use some of my onboard ports for fibre channel SAN Host connectivity (targets)? It Depends 7.3.2 or greater – Yes 7.3.1.1 or less - No
... View more
Apparently zfs has parameter to force alignment: http://www.solarismen.de/archives/5-Solaris-and-the-new-4K-Sector-Disks-e.g.-WDxxEARS-Part-2.html if you have possibility to verify it and report, would be great!
... View more
Sorry, but that’s completely wrong. Snap reserve never limited how much space snapshots can consume. You can set policy to delete snapshots if snapreseve gets full (which is not default) but it will never cause snapshots to fail.
... View more
Most likely not. Windows SID is built from (at least) two parts – computer/domain SID and RID (Relative ID) that, to put is simple, is just consecutive numbering of objects, e.g. users or groups. Lclgroups.cfg contains just RID for each group; but your file ACLs store full SIDs that include filer SID. New filer most likely will get new SID when you run cifs setup, which means those new groups won’t match ACEs. It is the same as deleting and creating user with the same name – it is still different user from Windows point of view.
... View more
SnapMirror preserves files ACLs but it does not copy share definitions (and their ACLs respectively). Shares has to be setup manually on destination.
... View more
All documentation I have seen (standard DataONTAP set, TR3548 etc) describe configuration with 4 disk HBA ports (usually 2 x dual-port HBAs or onboard ports). I could not find any description about how many HBAs are possible/allowed/recommended and rulses to connect them. E.g. I now have configuration with FAS3140 in fabric MC with 2 X2054A-R6 each. The rules in documentation are - never connect two ports from the same HBA to the same switch; but it is obviously not possible in case of 4 port HBA. Does it mean I am allowed to connect only 4 ports out of 8 available? How should head-to-switch connection look in this case? Thank you!
... View more
Yes, you can add new loop online. If this is onboard HBA, you need to make sure HBA is set to initiator, not target; to change mode you need to reboot filer.
... View more
Default unit for cache age in syststat is minutes, which drops to seconds as required. Values over 60 minutes are not displayed separately.
... View more
It probably is not related to EFI. There was recent thread about zfs alignment issues (I do not have reference, sorry, but search should bring it up). It seems that zfs is using variable block size that is not controllable (or not quite controllable) by user so misalignment is inevitable. To verify try UFS on the same LUN, whether it will exhibit the same alignment pattern. Of course the real question is how much performance impact it has.
... View more
You could try setting zfs recordsize; it is actually recommended if zfs is used for databases with fixed block. It can be set at runtime but will affect only files created after value had been changed.
... View more
Reclaiming space from deleted files is done in background and can take quite some time. Check with “df –Ak” with couple of minutes in between. If available space grows steadily, nothing to worry about – it will be there eventually.
... View more
It is possible (or, at least, close to it) using flexshare. See TR-3832 for details. Basically you can globally disable PAM but enable it for one volume only.
... View more
the documentation wasnt making sense I wonder which documentation do you mean. 1138GB raw CX disk, in raid 5, creates a 976Gb CX LUN (largest you can attach in Ontap 7.3.x), presented to the Vseries as a 854GB raw disk, and 845GB usable after ONTAP formatting, and 721GB after creating an aggregate on it. Could you explain what do you mean under "raw disk" and "ONTAP formatting"? 854GB is exactly 87.5% of 976GB, which means you have created BCS (block checksum) LUN. As explained in documentation, there is a second option, ZCS (zone checksum) which does not have this space overhead. 721Gb is approximately 85% of either 854 or 845 which translates into 10% WAFL reserve and 5% default snap reserve. It is hard to tell whether difference is due to decimal/binary mix without seeing actual numbers.
... View more
There are no changes made on OnTap. This policy grants "Take ownership of files or other objects" privilege to user account. Requested privilege is granted when user logs in and is associated with (inherited by) all processes started within user login session. There are no changes made on file system. So basically you have two ways. Either explicitly grant rights to take ownership to file system objects; or allow user to ignore file system access rights and take ownership anyway. Fsecurity does the former; GPO does the latter.
... View more