If you want to revert volume to snapshot you need to use “sdcli snap restore_volume”, not “sdcli snap restore”. ... View more

SD GUI will basically duplicate the whole LUN from snapshot, so yes, observed behavior is normal. If you want to do full volume revert to previous snapshot you can do it using SD command line utility (sdcli.exe). Do not forget that reverting volume will irrecoverably delete all snapshots after the one you revert to. ... View more

The easiest way - just connect old shelves to new head. Then all data is immediately available. If you will be replacing disk shelves as well – SnapMirror, vol copy, ndmpcopy from old to new filer. SnapMirror allows incremental transfers so downtime is minimized; others require source be offline (no data changing) for the whole duration of copy. ... View more

Load distribution is implemented by host multipath software. I am curious how zoning and/or port sets are related to it ☺ ... View more

Connection of shelves via FC switches is supported only in fabric MetroCluster, in which case you need 4 (not 2) switches, only specific models with specific firmware versions are supported and there is precise step by step procedure how switches are configured. Anything else may work but definitely does not agree with “best practice” ☺ Could you be more specific what you attempt to do? ... View more

When a file name is “converted” to UTF-X on CIFS access, it is suggested this is a "one time" conversion, and the name of file also converted on disk. Is this correct? That is what convert_ucode is for. If you have it set to off, the filename is converted everytime a CIFS client accesses it That's not what I have learned. AFAIK name is converted on first access and stored persistently. If name can't be stored (e.g. because volume/qtree is read-only) conversion fails and access i sdenied. ... View more

Normally when host disappears from fabric, fabric sends so called State Change Notifications; those who receive them are supposed to re-query fabric and discover that host is not present there anymore. If host is not present it hardly can be considered still logged in … Login mentioned in bug text (probably, meaning PLOGI) is just one of steps in establishing connection between two FC nodes. So it hardly can be called “an fcp problem” ☺ ... View more

My guess is that there is some NetApp Snap software that attaches to  volumes with LUNs on them at the volume/qtree level, and performs some  type of LUN snapshot mangement/read/writes. My best guess is that the reason was SnapDrive (for Windows) which used SMB to manage LUNs and so required LUN name in UNICODE. It is not clear whether HTTP(S) access method still has the same requirement or not. UNICODE conversion was in general required to provide CIFS access; well known puzzle is file in snapshot which cannot be accessed from CIFS even though the same file in AFS can and permissions were not changed. ... View more

Reallocation is very unlikely to be useful if deduplication is enabled. Standard reallocation moves blocks on flexvol level – old block versions are left in snapshots (if any) which results in snapshot size growth. Physical reallocation moves blocks on aggregate level and adjusts pointers in flexvol to new blocks. So from the flexvol point of view nothing changes and snapshot sizes do not increase. Downside is, your snapshots potentially become more fragmented, so if they are heavily used (trivial example is delayed backup verification in SME) it may cause performance impact as well. Unfortunately it all is somewhere between art and black magic but nowhere near science ☺ ... View more

It could also be possible by using host based mirroring; if volume manager is already in place, it could even be done without any downtime. ... View more

That’s true (except that previous versions does not work with block access anyway). Does it (previous versions from snapshots) work with other vendors for SMB? Celerra in the first place (given we discuss VNX)? ... View more

Well … I guess, NetApp answer to this would be snapvault, For me one of main downsides of NetApp snapshots is inability to switch between them – volume restore wipes out everything after restore point; and file restore is unacceptable slow (which I still do not understand why) and not really viable for may files. CLARiiON can switch between available snapshots without losing them. Not sure about Celerra, I do not have experience with their snapshot implementation. ... View more

Performance is degraded on a Volume, Share (CIFS / NFS), or LUN. Define "performance" ... Snapshots are NOT configured for the volume. As usual with "universally true" statements, this is not necessarily true. The real answer is - it depends. The point of reallocation is to increase sequential read efficiency. Sequential read is often (although not always) result of backup activity. Said backups are often (although not always) done by first snapshotting data and then reading snapshots. If reallocation is planned in advanced and run regularily, impact on snapshot growth can be mitigated. Another consideration is physical reallocation which does not inflate snapshots. Yet another case is transient snapshots (which exist only to make backup). ... View more

lrep_reader.exe -f IDCNJSAN01 -q /vol/chicago_retail -o F:\sv_init@0 ILCHIFSV03:D:\ snapvault start -S laptop:D:\sv_init /vol/chicago_retail/chicago_retail This command backs up content of directory D:\ on Windows host ILCHIFSV03. Is it what you intend to do? From your description I understood that your primary is filer, not Windows host. Is it correct? In any case, you have to specify qtree in lrep_reader command, not just a volume path; -q refers to secondary qtree which will be destination for SV, not to primary path that is being backed up. It has to match qtree that you will give in snapvault start later. ... View more

You can boot FAS as far as maintenance boot or load diagnostic. Diag can be used to verify hardware. Documentation is available on NOW. It is not possible to fully boot DataONTAP without hard disks and configured root volume. ... View more

Go to My Autosupport for device, in lower right corner there is Customize Notification link. ... View more

For source it can may be possibly controlled using options snapmirror.access, although your target should really not try to connect to e0M. For target I do not think it is possible at all. It just tries to connect to source; which (outgoing) interface is used is determined by routing tables. If your source is on a network that happens to be reachable via e0M, there is nothing filer can do about it. ... View more

Internal disks are SAS not FC; so they are connected to another, SAS, adapter. SAS shelves have independent numbering (OK, in case of 2020 you cannot connect any external shelf, still rule applies). ... View more

If you mean “effective security style of a file” – you can’t. That is how mixed security style works – it remembers last change of ACLs, so to make it remember Windows ACLs you need to do it from Windows. It may be possible to use smbclient from Unix to simulate Windows access though. In general mixed security is almost never what people really want. ... View more

There is synergy (http://synergy.netapp.com) that can import existing NetApp configuration and generate some diagrams, but I am afraid full functionality is available for certified NetApp partners only. ... View more

Loops are named according to FC adapter. So disk on a loop connected to FC adapter 0b will be 0b.NN, where NN is computed from shelf number. In case of multipath system arbitrarily selects which path is used to name disk. So some will appear on 0a, some on 0b. You can use “storage show disk –p” to display both pathes. ... View more

Yes, you have to manually set IDs on DS14 shelves. They must be unique within a loop (or, better, stack, as MP-HA has strictly speaking two loops) because they determine physical disk address on AL. Usually you start with 1 (0 is not allowed) and go up as you add shelves. Your cabling example is correct. ... View more