You have to connect to vfiler you created, not to vfiler0 (physical system). From SnapDrive point of view each vfiler is separate filer which has to be added separately to SnapDrive.
... View more
Yes, you are right. You can also add new shelf online, without downtime. Documentation on support site has step by step instructions how to do it.
... View more
For VSM it should be possible to resync as long as at least one common snapshot is still present. For QSM I am not sure, I have not used it much. In the worst case you need to perform new baseline transfer.
... View more
Groups managed by “groupadm” are not used for quota. They can be considered equivalent of security groups in Windows. For quota groups are taken from local /etc/group, or network based LDAP or NIS backends depending on settings in /etc/nsswitch.conf.
... View more
You can change network used for ACP using “acpadmin configure” command While it is theoretically possible to disable ACP and use e0P as normal interface, I am not sure whether this is really supported configuration. At least, open case with NetApp support to confirm it.
... View more
If interconnect is broken because of controller failure, partner will take over. If interconnect fails first and controller fails later, takeover does not happen, because NVRAM cannot be synchronized so there is no way for a partner to replay it. As soon as interconnect fails you will see message “takeover disabled”.
... View more
I am not sure, really … does search on support site show anything? In normal case there is nothing user needs to configure or adjust. NetApp handles setup of those disks (including cases when mailbox disk becomes unavailable) fully automatically. In those rare cases when user needs to be aware (like head swap) necessary steps are documented. Troubleshooting training may cover them in more details, but I have not attended it myself.
... View more
Both “versions” say exactly the same - when controller fails it cannot compete for mailbox access which is indication for partner to initiate takeover. Whether one individual calls it “stop writing” and another “relinquishes access” is matter of “language skills” ☺ When interconnect fails NetApp is using mailbox disks to verify that partner is still alive. If it is - nothing happens and both partners continue to run as before. If mailbox indicates that partner is not available - takeover is initiated. If this does not qualify as “NetApp behavior” - please explain what you want to know.
... View more
It would be helpful if you ask your question explicitly or at least explain what you think is missing in answers in this thread. As far as I can tell, answers in this thread are as complete as you can get without reading source code.
... View more
Usually it is NDMP backup to tape if anything at all; snapmirror/snapvault are not always available (or are almost always unavailable ☺ ) and majority of configurations have single aggregate anyway, which rather defeats purpose of replication.
... View more
When controller is replaced (keeping old disks) configuration is completely preserved. When the whole filer (meaning controller+disks) is replaced, you usually need to migrate data anyway, so root volume is migrated too. For disaster recovery I would rather make vol0 backup (NDMP, snapmirror, snapvault - whatever is available). Sorry, I simply do not have any experience with configuration backup done this way, nor had I ever feel a need for something like this, although I went through quite a number of head swaps and migrations.
... View more
I mean that one organization which manages one vFiler can configure the same VLAN(s) as second vFiler and potentially will have opportunity to steal sensitive data. vFilers are managed through vfiler0. There is no way administrator who has access only to vfiler != vfiler0 can add additional interfaces to this vfiler. It has to be done through vfiler0. And yes, you have to trust whoever manages vfiler0. Just as you have to trust your cloud provider, your hosting provider and dozens of other providers whose services you use everyday.
... View more
What exactly is missing in standard vol0 snapshots? They provide full backup and can be scheduled … How are you going to use these configuration backups later? I’m really interested, I never was clear what they are useful for ☺
... View more
It was a TSB and it did say “bye”. It is not the first time we see controversial information ☺ I do not have any spare filer where I could test it.
... View more
Actually my experience is exactly other way round - “bye” would initiate hardware reset that wipes out current environment settings while “boot_ontap” makes the persistent. I think there was KB on this but cannot find it right now. Do you have any pointers on difference between “bye” and “boot_ontap”?
... View more
Common reason is mandatory SMB signing on client side which may be required by your local domain policies. Try to enable it on filer: options cifs.signing.enable on Otherwise this really requires more deep troubleshooting. Using network tracing is often the fastest way to do it.
... View more