Just enable timed in FilerView and set it to use NTP as protocol; as servers specify domain controller(s). Make sure to set correct time zone and manually set time close to “real” before (timed won’t correct very large difference). Something like this: timed.enable on timed.max_skew 30m timed.proto ntp timed.sched hourly timed.servers x.x.x.x,y.y.y.y
... View more
BMC can send some limited information; but full autosupport is sent by Data ONTAP only. BMC is always using Data ONTAP autosupport settings so they must work. Do you have any chance to configure VLAN over FAS2020 LAN ports? Autosupport does not place any noticeable load on interfaces. Alternative is to configure some simple SMTP forwarder on one of you iSCSI hosts.
... View more
You actually request this when ordering, so a new system can be shipped either with or without MP-HA cabling IIRC for a couple of months only MP-HA systems can be ordered
... View more
As far as I can tell, you do not need it in NFS-only environment – if volumes will never be accessed by CIFS clients. Hmm ... another thread raised question about NFSv4 and UTF-8. I could not find any clear explanation whether NFSv4 is using the same convert-to-unicode mechanism as CIFS is; probably yes. So you may need it even in NFS-only for NFSv4; but would be nice if someone from NetApp clarified it. Message was edited by: aborzenkov
... View more
At what level do the alias ip addresses get assigned to the "Data stores?" aggro or volume? You do it on ESX server when you configure NFS datastore.
... View more
If it was a single file restore (snap restore –t file) – yes, it takes long time. Full volume restore (snap restore –t vol) is almost instant. If you have flexclone license you could rather try file clone (see clone command). Like volume clone, destination is available immediately and any long running tasks are started in background.
... View more
Should the exact same network configuration be implemented on both Filers (in case of partner takeover), even though we wont be hosting any CIFS or NFS shares on Filer 1 at this stage or should we configure each Filers's network according to its functional role and the protocols that it will be serving? For takeover to work partner must have access to the same VLANs and interfaces in the same VLANs must be configured to take over partner interfaces. Configuration need not to be physically identical, but IMHO it really simplifies it to keep it the same on both heads. As for other questions - unfortunately the answer really is "it depends". I would avoid using single interfaces as this just adds another SPOF (it can be mitigated by configuring NFO though). Easiest to manage is to just configure all interfaces as single LACP VIF; but this could result in uneven traffic distribution. In any case do not expect to find a silver bullet - whatever you chose, monitor your configuration for overload and possible bottlenecks.
... View more
Technically it will work with a single initiator port in every head; but it is highly recommended to have two ports in every head for MP-HA (MultiPath-HighAvailability) cabling. If this is a new system, it should be already configured and delivered with MP-HA from factory.
... View more
It could be client issue. We once had the problem of too small RPC queue depth on Linux (which is set to 16 by default). Bumping it to 128 did solve the problem. If you have good latency on filer side and low throughput on client side, I’d start checking client settings.
... View more
My understanding of the purpose of adding the alias’s was to enable two ip channels for the NFS traffic to travel on between esx host and SAN controller. The purpose of adding IP alias is to have static load balancing across aggregate ports; this is explained on next page 35 in TR-3749. You should nevere access a single NFS export via more than one IP address and you must access the same NFS export using the same IP address on all ESX servers, otherwise they won't treat it as the same datastore. As shown on p35, half of available datastores is accessed via the first alias and half - via the second alias. Assuming proper switch configuration, this will distribute load between two available links. Which one is better/right method? Personally I would favour stack if supported by switch. Keep in mind, that in case of NFS you will never have truly separate physical switches because NFS does not have any failover capabilities and relies on underlying TCP/IP infrastructure to handle any transmission path errors. So what you actually have is interconnected switches which still represent single fabric; and IMHO it is more error prone and difficult to configure right than just a (logically) single stacked switch.
... View more
It does not look NetApp related to me. Seems that rsync creates file names in UTF-8 encoding but system where you try to read it defaults to ISO-8859-1. In Linux where you see "garbage" try: ls /path/to/mount | iconv -f UTF-8 You should see "normal" file names.
... View more
All control information from NetWorker storage node and NDMP device goes via LAN. This of course includes file index from NDMP device back to NetWorker storage node. This is in addition to data written to tape, which is in dump format as described in KB you mentioned. You can find overview of NDMP architecture in e.g. http://www.ndmp.org/info/spec_summary.shtml. Similar diagrams are available in NetWorker documentation. Detail protocol description is available from http://ndmp.org/ as well. Default NDMP port on NetApp side is 10000; on NetWorker side I guess it is random.
... View more
Most likely the reason is that you installed using single path. After installation connect second path, let system fully detect and configure it (confirm that you actually see two paths to every LUN) and then test boot again.
... View more
Yes. Just snapmirror old destination to new volume and then break SM between old and new destination and resync from source to new destination. It will pick up common snapshot.
... View more
Microsoft? ☺ Go to corresponding KB article on http://support.microsoft.com/ and click “View and request hotfix downloads”. Microsoft also offers Premier support site where you can directly download hotfixes; your company of course has to have premier support agreement with Microsoft.
... View more
Yes, you have to enable software based ownership for multipath to work. Without it second connection is interpreted as partner (because it goes to channel B).
... View more
You can’t use Windows Previous Versions (I really wish we could; I do not know whether this is Windows or NetApp limitation). You can use snapshots but keep in mind that recovery is rather awkward. To recover individual files you need manually map snapshot containing needed file. As there is not catalog to list available file versions, you are left with trial and error. It is possible that there is backup software that integrates and supports use of LUN snapshots on NetApp; those I am aware of (NetWorker, NetBackup, BackupExec) do not. So I would use snapshots more or less for disaster protection and rely on standard operating system level file backup for daily use.
... View more
For me the simplest way would be to replace drives while FAS is switched off and make new install. Alternative would be to switch it on, go via initial setup, replace unused drives (freshly shipped filer has only 3 or 4 drives configured at most), relocate root volume on new disks and the replace the rest.
... View more