Have you initialized compliance clock? You must do it before SnapLock can work. Otherwise it is correct – you have to set file read-only, after which current access time becomes retention period. No_atime_update is always on for snaplock volumes, so you can only set it manually. If no atime is ever set, default retention period will be used. It is not wise to play with compliance, there is no way to destroy aggregate in compliance mode until retention time has expired. Better take simulator for this. ... View more

Use “igroup remove –f …” command ... View more

Get a look at http://cmpg.netapp.com<http://cmpg.netapp.com/ ... View more

Cleaning up disk I found tr3599 which is titled "REALLOCATE BEST PRACTICES GUIDE " Now it is marked confidential and I am not able to find it on fieldportal (which does not mean anything, it is near to impossible to find anything on purpose there). It is dated 2007 so I guess I have it from old partner portal. It does not contain anything excitingly new that was not already covered in various discussions; the main value is, it represents official NetApp position about use of reallocation. I'd love to see it updated to include new physical/aggregate reallocation. Anyone knows if newer version exists or why it was removed? ... View more

Is there a good way to split up that 4293GB of disk space into 2 or 4 volumes, which then on will contain a lun presented to esx? I am not sure I really understand a question. You just creates FlexVols on this aggregate (like you already did) and then create LUNs inside these FlexVols. Or could you explain in more details what you intend to do? ... View more

however de-clustering a clustered machine will result in a breach of license I am really curious - in which respect? Could you point to a document that explains it? And what implication does it have - will NetApp refuse to provide service in this case or what exactly happens? ... View more

Returning to your original question - SMVI (Snap Manager for Virtual Infrastucture) does offer efficient backup of VM data files and offers single filer restore as well. One gotcha in your case - NT is not on the list of support guest operating systems ... with all implications. Any chance to update NT to something more up to date that is supported? You could also manually create snapshots of NFS datastore; this will capture VMDKs in crash-consistent state. For single file restore present (Flex-)clone of VMDK in snapshot to the same or another VM as additional disk. This is effectivelly what SMVI does anyway, just that it automates it for you. ... View more

Yes, you can remove particular tape alias: storage unalias { alias | -a | -m | -t } After all aliases are removed the first tape found will get st0. Tape aliases are used in backup management systems (e.g. when NetWorker auto-configures NDMP storage node, it will populate device names with tape aliases). If aliases were removed as soon device disappeared and recreated again, device could be renumbered (i.e. the same alias assigned to the different physical device) which would play havoc with tape management. And losing devices in SAN is not that uncommon (misconfiguration, accidental cable pull, power loss, library reboot – pick your favorite). ... View more

Use “storage unalias” to remove aliases for no more existing tapes and “storage alias” to name your new tape. Or zone tape off, remove all aliases and zone it again in. NetApp remembers aliases for tapes even if tape is no more visible. Removing them automatically would be fatal actually. ... View more

Especially annoying is the fact that the iGroups are not stored in the root volume and cannot be brought back from snapshots. Hmm ... do you know, where there are stored? ... View more

OSSV-WASTST1:c:\Program Files\NetMeeting contains space which splits argument in two; so snapvault release command just sees OSSV-WASTST1:c:\Program Try to either take the whole string in double quotes or explicitly quote space using backslash as well. Either “OSSV-WASTST1:c:\Program Files\NetMeeting” Or OSSV-WASTST1:c: Program\ Files NetMeeting ... View more

I'm pretty sure this is incorrect Just curious, what exactly your this refers to. ... View more

Max raid group size for SATA disks is 16 (RAID_DP) with 14 being default. So there is no way to put two SATA shelves in one raid group. Depending on how much spare you want 14 or 13 would be fine IMHO (26 or 27 disks in two rg with 2 or 1 spare). If you already have spares available, go for 14 and two full shelves. Keep in mind that max aggregate size on 7.x is 16TiB; this includes all disks in 7.2 and below and only data disks on 7.3. So look up disk size in storage management guide and compute max possible aggregate size based on it. ... View more

See documentation for protocolaccess. You can selectively disable use of some protocols used to manage NetApp (like ssh, http and several others) for specific hosts, networks or interfaces. ... View more

I am not sure I really understand the question. You can use any configured interface for management activities (as long as you did not explicitly disable it). The idea behind e0M is to offer relatively low cost management interface that could be physically separated from other traffic; most people would rather not spend the full 1Gb/s interface just for this task. But it does not mean that management must be exclusively done via e0M. Of course if e0M port fails you lose access to RLM. To provide redundant console connect serial port to terminal concentrator or just to COM port of nearby server. And if you want to be able to remotely power cycle filer, install PDU with remote control capabilities. Some companies offer the whole range of console/power gadgets with single management layer, SSO etc. But to reiterate – any standard management task on DataONTAP can by default be done via any configured interface. ... View more

It says fixed in 7.3.3. Do you know what actually has been fixed and did you have a chance to verify it? I do not remember seeing anything explicit about it in RN or documentation; browsing 7.3.3 manuals now, the statement that fractional reserve cannot be changed for file or none guaranteed volumes did disappear. As for original problem ... well, it was a bug, because even in 7.2.5.1 manual quite clear stated that FR is fixed to 100% unless volume guarantee is none. ... View more

Not that I know of. On user level you see just the same (single) aggregate; whether it consists of one or two mirrored plexes is mostly irrelevant. ... View more

filer1> options stats No such option stats filer1> options stats.archive.max_disk_space_percent stats.archive.max_disk_space_percent 2 ... View more

Ontap 7.2.6.1 effectively broke this functionality Guess what? It is not a bug, it is a feature https://now.netapp.com/cgi-bin/bol?Type=Detail&Display=280845 : Vol clone incorrectly allows fractional reserve to be set to 0 and  guarantee to be set to 'none' or 'file' ... View more

Both plexes are written simultaneously; failure of one plex is handled transparently, there is no need for manual intervention. ... View more

I believe it should be option stats.archive.max_disk_space_percent. ... View more

Are you sure you are connecting to correct port on LAN controller? No joking – I spent over half an hour trying to find out why port did not come up. Unfortunately labels on LAN controller are almost unreadable and I tend to forget where port numbering starts. ... View more

You can shrink NetApp FlexVol at any time, there is no problem. As for LUN – Windows 2008 supports shrinking of partition; see http://technet.microsoft.com/en-us/library/cc731894.aspx for conditions when it may not be possible. If you have SnapDrive license, newer versions (last one is 6.2) support shrinking of LUNs and I would recommend using SD for it. If you do not have SD, you may still be able to manually shrink partition as described in the above article and then shrink LUN on NetApp side. I did not try it myself to be honest, so you are advised to test it in non-production environment first. Another possibility – again, if you have SnapDrive – to go thin provisioning route. You need SD because it can reclaim unused space in file system so that LUN physically takes up exactly as much space as is logically used. --- With best regards Andrey Borzenkov Senior system engineer Service operations ... View more

It is not the same. LUN may be 100% free from host’s point of view, but 100% full from filer point of view. There is ZAPI call lun-get-occupied-size which looks like it does provide this information (not tested): Size occupied by the LUN in the Active FS in bytes. I am not aware of any CLI option (even in diag mode) that would return the same. ... View more