And please understand that your problem is not specific to software update. If it fails during NDU, it will also fail in case of controller malfunction. So basically your configuraton is not High Available and it should be your primary concern. Doing "cf takeover"/"cf giveback" is essential step in testing NetApp system configuration for basic HA features before putting it in production.
... View more
For NFS mounting with option “hard” ensure client will never time out and will retry connection to server indefinitely. For LUN (FCP/iSCSI) there are Host Utilities for all supported operating systems which either provide tools to automatically setup necessary parameters or describe how to do it. Notice that you may need to reboot hosts so changed values are actually enabled. CIFS client just reconnects; this normally is transparent for simple file browsing (like Explorer) but may be disruptive for something like database on a CIFS share. In all cases you are responsible for setting up client applications so they do not fail in case of IO pause. In case of hypervisors this translates to – not only hypervisor must have the correct timeouts, but every guest must have correct timeouts as well.
... View more
One more possibility is to use lrep if QSM is an option. This allows to transfer data directly to (removable drive on) PC and then play back on DR site.
... View more
“cf takeover” does shut down services on one controller and boots them on another. So you have some period of service unavailability. Clients must be properly configured (timeouts set etc) to be able continue to wok uninterruptedly, but it does mean some pause before IO can continue. Takeover may theoretically take up 2 minutes so you clients must be prepared to wait this time until services are back.
... View more
1. Loan tape drive. Really, I do not believe it is impossible ☺ 2. If you have enough space on source filer (you will need to store all data that is going to be replicated) it is possible to do “snapmirror to file” (similar to “snapmirror to tape”). This option is available in diag mode only, so you are strongly advised to contact support before doing it.
... View more
This disk containing meta data about the storage systems, e.g. raid groups, configutation and so on. This is the first time I see someone says it. You probably know better being from NetApp, but I was always sure raid group configuration is kept in disk labels on every disk belonging to this raid group and definitely not in mailbox; and I am not sure what other "configuration" you mean. Could be more specific? The simple proof that raid group config is not kept in mailbox is the fact that you can easily destroy mailbox and still have all your aggregates back.
... View more
doing a ifconfig on both c0a and c02, one of the links reports down an the other reports up. That's correct. For single chassis models only c0a is used over internal backplane interconnect and c0b is not used.
... View more
The obvious question - which permissions? There could be at least three disjoint permission sets - Unix, NTFS and NFS v4. NTFS could be changed using fsecurity command invocation (via system-cli). I do not know if it is possible to directly manipulate Unix or NFS v4 permissions.
... View more
Yes, I mean old replication. Quiesce temporary suspends replication without making destination read-write. Break will split relationship and make destination writeable again. Release removes old base snapmirror snapshot from source.
... View more
On source – “snapmirror release S-Filer:S-Vol D-Filer:D-Vol” and manually delete any leftover snapshots. Sometimes “snapmirror release” does not remove them. On destination you will need to clean up snapshots manually.
... View more
This article gives some recommendations how to troubleshoot this error as well as long list of references to other articles. May be, some of them helps. http://www.symantec.com/business/support/index?page=content&id=TECH71644
... View more
You check this on filer, in terminal session. But on Data ONTAP 8.1 it is enabled by default, and I did not have any issue with simulator, that is why I think it is something in your environment.
... View more
Yes, 16 synchronous SnapMirror relationships is the absolute maximum for FAS3210. May be, you could use standard async SnapMirror for some volumes, here upper limit is larger.
... View more
Try to ask on OnCommand System Manager forum. It can be something with Explorer or Windows settings. You can also try another browser, i.e. Firefox, just to verify it.
... View more
If fractional reserve is set below 100%, it is possible that volume will run out of space for new writes to LUN from host. Most operating systems do not expect that disk can suddenly run out of space and do not handle this case gracefully. So you will need to monitor your system for available space and decide in advance what you will do if space becomes dangerously low. Increase volume, delete some snapshots etc. Which amount can be considered “dangerously low” depends on your environment – how heave IO is, what change rate is, possible peaks of activity etc.
... View more
The only idea that I had was related to FSID, which may be different between AFS and snapshots. What NFS version are you using – NFS v3 or NFS v4? Does any of these KB help? https://kb.netapp.com/support/index?page=content&id=2015880 https://kb.netapp.com/support/index?page=content&id=2015819 https://kb.netapp.com/support/index?page=content&id=2011481 https://kb.netapp.com/support/index?page=content&id=2013487
... View more
If availability is primary consideration, it is possible to make one set of LUN available via one pair of controllers, another set of LUNs – via another controller pair and SyncMirror between them.
... View more