Well, I have not tried it myself and I do not have systems to test. But I expect that if previous state was clean shutdown of both partners, it should work. I appreciate of someone with hardware available could test and report. ... View more

Yes, after clean shutdown it should be OK. ... View more

“takeover -f” or “forcetakeover”? Part of problem is, it is not known whether NVRAM is clean. So user is responsible for any potential data loss … ... View more

Interesting. My experience is that normally NetApp does not ship power supplies without clarification. May be for some extra premium conditions … ☺ ... View more

Yes, I did it several times. Which file do you mean? You basically need the content of ASUP E-Mail to process it. ... View more

7.3 does not count parity disks against total aggregate capacity, so upgrading will help. It will allow to add several disks more than was possible in 7.0. ... View more

NDMP will work with any directly attached tape as long as it is supported and correctly recognized by NetApp. Technology does not really matter (SCSI, FC, SAS). ... View more

In 8.1 autosupport is sent more frequently, to overcome message size limitation which could prevent weekly messages from being delivered. I do not think it is possible to change it. I do not like “HA group” subject either, but all my systems are HA pairs so it does not bother me much. This change has to do with 7/cluster mode unification, where autosupport for the node is not necessarily sent from the same node (even for 7 mode). ... View more

sanlun is 32 bit program so you need 32 bit libHBAAPI.so. ... View more

I checked QLogic and it appears that libHBAAPI 64 bit is part of at least QConvergedConsole CLI. It seems like new management suite, replacing SAN Surfer. ... View more

It is possible that client does not support sec=none or is configured to request sec=sys always. Tracing connection between Data ONTAP and filer is the easiest way to tell. ... View more

Thank you for bug reference! ... View more

That won’t work. vol copy is block-for-block copy and requires target version to be the same (or possibly higher). User ndmpcopy instead. It won’t preserve existing snapshots though. ... View more

Yes, usually 32 bit programs runs just fine in Linux x86_64 environment. You may want to verify, which libraries are required and install extra 32 bit versions, which may not be normally present on 64 bit systems. The problem is, if program that requires it is 64 bit, it will not work with 32 bit libraries; you need 64 bit version. Hmm … I was looking for libHBAAPI for QLA couple of days ago. So you say it is part of CLI which is 32 bti only? Not good. OTOH libHBAAPI should be vendor independent. There is native Linux implementation that could even be included in your distro (I know that SLES11 provides it). You will need just backend, which in case of QLA is provided as separate package (search for HBAAPI). ... View more

Thanks for clarification. For some reasons I thought SM and SV behave differently with regard to /vol/volname/- syntax. ... View more

1. You can move data into qtree from host; mount volume and use standard host commands to move files around. 2. Use the syntax /vol/vol-name/- to reference whole volume as SnapVault source. SnapVault destination must be qtee. ... View more

What baffles me though, is the distinction between 'random writes' & 'random overwrites' - in a context of WAFL there should be no difference between these two. Well ... just random commuter's thoughts (you have to do something on the way ) First let's accept that Flash Pool accelerates writes. This sounds plausible at least for some workloads (e.g. under heavy sustained random read workload). Now to benefit from Flash Pool CP should be considered complete as soon as data is on SSD. OTOH Flash Pool is just a cache, is not it, so data at some point must be moved to rotational disks. So we by design have some delay. If block is rewritten after it had been saved to SSD but before it was copied onto rotational disks. we effectively saved at least one disk IO. This is blurred by snapshots, where we obviously cannot just through away unsaved blocks. But it is still good as marketing argument ... View more

I am curious how you can execute "disk show -v" on head that is waiting for giveback? Otherwise that sounds like OC SM specific bug. There are likely not many users who do takeover/giveback using GUI ... ... View more

Keeping in mind that the snapmirror source for this volume is also 600GB. There is volume size and there is filesystem size. They are not necessarily the same, especially when we talk about SnapMirror destination. Check fs_size_fixed volume option and "vol status -b" output ... OCSM may default to showing filesystem size (as this is what clients actually see). ... View more

Disk firmware update is initiated as soon as disk is assigned to filer. Labels are upgraded automatically if disk is part of aggregate. Standard recommendation when moving disks between filers is to make disks spare (zeroing spares before is extra bonus). I do not think shelf firmware is updated automatically when new shelf is connected; it should be updated during boot though. If you are removing all volumes anyway, you can simply destroy aggregate, it is easier. No need to mess up with unsupported commands in diag level. ... View more

Capital `S' (-S) for source, not small `s'. ... View more

2. Are you using a LUN?  If not, you should always have FR = 0. If you are not using a LUN, FR is not relevant at all 3. Are you sure you'll never be taking a snapshot?  If you are assured of this, you should always have FR = 0 Another case is deduplication (A-SIS). And snapshots are indirectly used by other features (vol copy, flexclone, snapmirror, snapvault, ...). Otherwise the same as above - as long as no snapshots - FR setting is completely irrelevant. ... View more