LUN space reservation only cares about space in Active File System. If FR is set to 0, then nothing is additionally reserved when snapshot is created. So you can have 100G volume with 100G LUN completely full and still create snapshot. Any attempt to write to LUN fails at this point. ... View more

I think you really should open support case at this point. Assuming everything was connected properly there could be some firmware updates required, and NetApp support is in the best position to check and advice here. ... View more

Well, I mentioned it because of previous statement “could allocate the remaining free space of the volume”. This sounds far too dangerous for me to do without considering all implications. ... View more

“Mixed” means not all disks are properly multipathed. This is exactly what is the case now (even if it is just display issue). Consider it as early warning ☺ I find it quite good system informs you about possible configuration issues. ... View more

You do realize that if you have any snapshot on this volume you are now in much more risk of LUN running out of space? If there are snapshots you should consider setting reasonable FR. ... View more

SMSAP could not delete snapshot because it was busy. It could have been mapped to a host or clone could have been created or it could be locked by snapmirror. It is impossible to tell from below output only. Show “snap list” output from filer where this volume is locate; it could give some hint. ... View more

Accumulating CLOSE_WAITs is normally indication of application bug – local side does not properly close connection after remote side did it. But 150 is not really that much. As connections are apparently to web server, it could be possible to clear them by disabling and re-enabling httpd. But you should really open support case with NetApp as it sounds more like a bug. ... View more

Some disks are shown on the same channel: 5a.03.0 A 6a.03.0 A 3 0 6b.17.11 A 5b.17.11 A 17 11 Which for NetApp means they are not multipathed (actually it is configuration error). Strange, as other disks in the same shelves are OK. I would open case with NetApp support so they investigate it. I must admit I do not have enough experience with SAS shelves to (try to) interpret it. May be others can shed some light here. ... View more

Run storage show disk –p to see which shelves are not multipathed. ... View more

See https://kb.netapp.com/support/index?page=content&id=1010097&actp=search&viewlocale=en_US&searchid=1304417072930 for procedure to move root volume. I myself usually use simple “vol copy” to copy existing root volume onto another one. ... View more

I assume that currently you have small aggregate on rest of SATA disks on controller 2. So you will need to connect external shelf, allocate its disks to controller 2 and move root volume (and any other data) off SATA disks onto new shelf. After that you can destroy old aggregate on SATA disks and re-assign them to controller 1 and add to existing aggregate. It will keep all data and setup of controller 2. ... View more

You can’t combine SATA and FC disks in the same aggregate so you will need at least two of them. It makes no sense to assign both aggregates to one head and leave the second one idle (even assuming it were possible). So the only sensible setup in this case I see is SATA on one controller and FC on another one. I personally would simply go for one RAID_DP with single spare on each side. If you are going to update it makes sense to update to the latest version which is 7.3.5.1 as of now. Aggregate consists of data and parity disks; spare disks are not part of any aggregate. So did you remove parity disk from aggregate or spare from controller (how exactly? Which commands?) ... View more

Is NVMEM battery installed on replacement controller? Link I gave you gives step by step instructions what to do to replace controller. Did you read and follow it? ... View more

Any NetApp HA pair is technically active/active. You need to be more specific in your questions. For SATA it is really RAID_DP. RAID4 will require the same amount of parity disks with drastically reduced reliability and manageability. For FC it is really up to you. Both are possible, RAID4 gives you extra drive but e.g. makes online FW update impossible. ... View more

I would put SATA disks on one head and FC disks on another. Anything else would waste disk space without any benefits. ... View more

Have you actually read document that describes controller replacement? “Remove the controller module, locate the boot device compartment on the underside of the controller module, and then remove the boot device cover. The boot device is to the right of center, near the I/O ports.” It even has picture showing where it is located. ... View more

CF is located on the bottom side under slide cover: http://now.netapp.com/NOW/knowledge/docs/hardware/filer/215-01810_E0.pdf --- With best regards Andrey Borzenkov Senior system engineer Service operations ... View more

Current Data ONTAP versions offer both snapshot autodelete and volume autogrow features. Both help to mitigate this issue – either filer will remove excessive snapshots, or will increase volume size (assuming containing aggregate has free space). ... View more

I wonder if it is possible to hack LDAP server to provide fallback reply in case of unknown UID. ... View more

Are you saying that options cifs.smb2.signing.required on does not  really mean the NetApp server is going to require SMB signing?  Or is  this setting referring to when the SMB2 session is acting as a client,  not a server? According to manual page and tr-3740 it does force signing at least when NetApp is server. Quoting tr-3740: SMB 2.0 signing is never disabled as seen in CIFS/SMB; the possible configurations are either “required” or “not required.” It is still not clear what happens when NetApp acts as client; the only documented option related to this is cifs.smb2.client.enable. It would be even nicer if there were an option to enable signing when the the client or server requires it, but not otherwise As far as I can tell, this is what happens with SMB2 by default ... again at least on server side. ... View more

To my best knowledge UID-to-name mapping is mandatory in mixed multiprotocol environment (see as example description of authentication flow in tr-3490). From your description it looks more like administrative than technical problem, really. Simple question – how will you distinguish between different nancy.users with the same UID coming from different client? May be some clever use of NFSv4 with its identity mapping could help in this case. ... View more

1. Yes, NDMP is the most natural (and effective) way to backup in this case as long as number of files is not very large. 2. I do not think you will be able to restore to simulator because you would need to attach physical tape drives and this is not possible. For disaster recovery the best would be to have snap mirror/snap vault to remote site. Otherwise I have heard rumors (call it town legends) that NetApp dump is compatible with classical Unix counterpart so it is possible to use Unix (the guy spoke about Solaris, but probably Linux utilities do exist as well) “restore” command to recover data. You will probably lose ACLs anyway. You still will need to extract raw dump stream from whatever format BackupExec is using. ... View more

You can use “stats” command to get large number of counters including individual disks. ... View more

That’s correct. But then it makes no difference to GUI – both do exactly the same operation. ... View more