Under Vista SP2 it starts automatically in default browser IE7. And it is really slow. ... View more

Then you probably will be stuck with cluster system in takeover state and degraded mirror forever without any clear path how to get out of this situation. ... View more

Single file size limit is still 16TB. ... View more

It can’t be done online – you need to shut down filers (for extended period of time) which obviously will be disruptive without cluster failover. Basic steps are described here: https://kb.netapp.com/support/index?page=content&id=1011599 Make sure filers own whole shelves, otherwise you may need to reshuffle disks between shelves as non-HA-pair cannot have access to the same storage. You may need to change NVRAM slot, check system configuration guide for your model. You will also need to change HA cabling from MP-HA (or recable if you have FMC). You will also need to remove cluster_remote license to avoid warnings about non-mirrored root aggregate. Otherwise it is relatively straightforward ☺ ... View more

LUN size does not depend on protocol. ... View more

https://kb.netapp.com/support/index?page=content&id=3011274 ... View more

Well … one RC is as good as another one ☺ Why not … ... View more

Those are LUN clones created most likely when host needs to mount snapshot (for backup). This is well known issue with any (backup) software that is using VSS. Unless software provides some means to select VSS provider, it will just use default one, which for NetApp will incidentally be NetApp snapshot … normally they are expected to be removed after backup, but sometimes they stick. In general the only workaround is to disable NetApp VSS hardware provider before starting backup and re-enable it after that. Ugly and racy. Have you tried to contact Symantec regarding this issue? ... View more

Root on 64 bit is supported since 8.0.1. ... View more

Yes, it is possible. It sounds like you already have 8.1 installed so you can just do "vol copy" from 32 to 64 bit; that preserves all snapshots and allows to resume snapmirror later. If not, you can simply ndmpcopy /vol0/etc to new root volume, it should be enough. See https://kb.netapp.com/support/index?page=content&id=1010097 ... View more

Normally I use snapmirror. It still needs downtime, but snapmirror allows incremental updates, so final update can be very small, needing several minutes for final cutover. For NFS there is also "snapmirror migrate" which - with some luck - may even work online. It is licensed product, but may be you could ask your NetApp representative for demo license. You could also make initial copy with "vol copy" and then use host based tools like rsync or robocopy to catch up. Both approaches still need final downtime, just let you to minimize it. True online volume migration is possible either for volumes with LUN under 8.x 7-mode, or using 8.x Cluster mode for any volume. As you are running 7G, neither applies to you. ... View more

I would create aggregate aggr2, create volumes with the same size as volumes on aggr0, and use "vol copy" command to copy content of volumes from aggr0 to corresponding volumes on aggr2. You will need to make sure nobody is changing source volumes, otherwise copy will be incomplete. Once done, you can in principle destroy old volumes and rename new ones to the same name. Or rename old volumes and keep them for some time as safety measure. If you want to move root volume as well, just designate its destination on aggr2 as root volume using "vol options root" and reboot. ... View more

Yes, each controller in HA pair has own set of disks which are taken over by partner if controller fails. Takeover time depends on many factors, but 30 seconds could be considered as rule of thumb average. Hosts are expected to be configured so that they won’t fail (by settings appropriate timeouts, number of retries etc). Please understand that any vendor that offers failure tolerance against path failure will face exactly the same situation – there will be some timeout before host finally gives up on failed path and continues (retries) over remaining ones. Such timeouts are usually in order of 60 seconds. So there is nothing unusual in how NetApp behaves. ... View more

Looks like it cannot find physical device corresponding to LUN. Suspicious is that it is using host name in one place and IP in another. MetaDevice :: 172.16.100.30:/vol/prakash_voting_vol/prakash_voting_vol_3.lun : /dev/sdc, /dev/sdc => 3050A:/vol/prakash_voting_vol/prakash_voting_vol_3.lun Make sure you consistently use either filer host name or filer IP everywhere. ... View more

Do you have any FC HBA in server or any FC driver loaded (like Emulex lpfc)? If yes, make sure FC drivers are unloaded. Otherwise you could enable trace and see if there is some hint there: https://kb.netapp.com/support/index?page=content&id=2012677 ... View more

Can you see this manually added LUN with /opt/netapp/santools/sanlun lun show all? What are the values of default-transport and multipathing-type SnapDrive configuration options? ... View more

I do not expect that anything happens at all. File content does not change and remains in the same state it was before renaming. ... View more

Does igroup on filer exist and is your host IQN included in this igroup? Does host physically see new LUN when it is created and mapped? You can verify by looking in e.g. dmesg output immediately after running snapdrive for messages about new sdXX device. If you manually create LUN on filer and map it to this igroup - does host see this LUN? ... View more

Leave a comment on sdconfchecker page that you cannot use this tool. As long as nobody complaints it will remain this way. Error that you see is far too generic to be able to say anything without detail log analysis. Have you verified that your configuration matches IMT? For a start, you could mention whether you are using iSCSI or FCP. ... View more

Well ... "You are still required to install a DFM management server license key to enable the management server. Please contact your NetApp sales representative to order the DFM management server and associated licenses key. The license key for the management server will appear in the usual location for license keys on the NetApp Support Site. Go to the NetApp Support site at https://now.netapp.com/eservice/SupportHome.jsp and click “My Support” then “Software Licenses”. Locate the serial number for the DFM management server to obtain the license key." ... View more

Have you tried "disk assign xx.xx -s unowned -f"? Otherwise it is possible that you need to remove cluster license and reboot so that disks are no more associated with partner. ... View more