Cache hit – the bigger percentage, the better (100% means all data is served from RAM, which is the fastest component). But it is quite unrealistic. Low cache hit rate would mean mostly random access. I do not think 90% is that bad. 75% is a bit low but again – it depends on workload. Consistent CP time of 95% means your filer barely has time to flush data on disks. You need to further analyze where data comes from (clients or internal activities); maybe you have some hot spots that slow down disk writes. The value itself is not bad but it does not leave much headroom for increasing load.
... View more
For initializing SnapMirror relationship no extra backup software is required. It is also possible - Attach shelf from another site so FAS, initialize SnapMirror locally and then move shelves to another site. It requires downtime to disconnect shelves - Use small FAS like FAS2020 that can be easily transported to another site; we used such method several times. First do SnapMirror from local system to this FAS; then move it to remote site and initialize SM from this FAS to remote filer; finally do resync between sites.
... View more
SM to tape is described in Data ONTAP manuals; it requires (obviously) tape drive connected to FAS. As your system most likely does not have SCSI port, it has to be drive with FC connection. It does not matter whether this drive is in a library or not. You will have to manually load tape. Then on source system do “snapmirror store source_vol tape_name”, move system (and possibly tape drive) to destination system and do “snapmirror restore destination_vol tape_drive”. The effect is the same as after doing “snapmirror initialize –S source:source_vol destination_vol”. If volume does not fit on one tape, you will be prompted to exchange media; you can also specify multiple tape devices in “store” command.
... View more
UID -2 means user is not mapped (IIRC). You need to setup WSFU user mapping service and map some Windows user to root; the you will be able to mount share on behalf of this user as root. See e.g. http://technet.microsoft.com/en-us/library/bb463203.aspx
... View more
Oh, I am awfully sorry, I completely missed the fact that you are using SATA disks ☹ In this case raid group size is limited to 7 disks, you cannot increase it. What you can do is to create RAID_DP without spares (although as mentioned running without spares is not recommended). Default raid group size for RAID_DP is 14 disks.
... View more
SnapCreator apparently is capable of initiating OSSV update from client (although documentation for OSSV mode is rather terse). So looks like push mode is possible?
... View more
aggr create aggr1 -r 9 … see aggr command description for all options. You will need to destroy and re-create aggregate, it is not possible to remove raid group. For SATA disks default raid group size in 8.
... View more
See https://kb.netapp.com/support/index?page=content&id=1012604 for disruptive revert procedure (it tells you about FAS3200 but procedure seems to be applicable to any system. Of course, you won’t need to change SP firmware etc. )
... View more
Filer1 ifconfig vif_NFS-10 (Subnet B IP) netmask 255.255.255.0 partner vif_iSCSI-2-10 mtusize 1500 trusted -wins up Filer2 ifconfig vif_iSCSI-2-10 (Sunet B IP) netmask 255.255.255.0 partner vif_NFS-10 mtusize 1500 trusted -wins up ifconfig vif_iSCSI-1-10 (Subnet B IP) netmask 255.255.255.0 partner vif_NFS-10 mtusize 1500 trusted -wins up I am not sure if such many-to-one configuration is valid; in general is advisable to have configuration as symmetrical as possible unless there are strong reasons to do differently. At least the first error message is likely because of this.
... View more
I am afraid I cannot give any reference, this was from discussions during NetApp training. Office applications create new file version and then move it over original one. CIFS file folding compares file content with previous version in snapshot and discards data that was not changed (replacing it with reference to snapshot). So if you change single character in 4M files without file folding you get 4M in snapshot and 4M in active file system. With folding you hopefully get just 4K extra in snapshot. CIFS file folding can be enabled at any time. It won’t have any effect on existing snapshots, nor on any file that already was changed, only on newly changed files. If may help with SnapMirror by reducing size of snapshots and thus transfer size. Do not forget that it adds additional load (filer now has to physically compare full file content); it means extra CPU, disk load, cache pollution etc. Be prepared to monitor filer to catch performance degradation.
... View more
Snapshot “grows” due to data changes, not due to data additions. After adding 20G of data snapshot size will remain the same (almost because of metadata overhead), but after changing 20G of data size of active file system will not change, but snapshot will appear to “grow” to 20G. I suggest getting file modification time report to see, how many files are changed. You mentioned in another post that most files are office documents. In this case every changed file almost sure implies completely new version with old one possibly frozen in snapshot. Get several consecutive snapshots; compare file modification times to see whether files were changed between snapshots. I suspect sum of changed file sizes will be close to snapshot size. You could also enable audit to get exact report who is accessing files.
... View more
Accidentally hit two articles with completely opposite content. https://kb.netapp.com/support/index?page=content&id=3011977: Does the filer support Etherchannel? states that ip.fastpath will answer on the same physical interface of a trunk that packet came in: With fastpath, the interface, on which the request came in, and the MAC address of the caller is saved on input. The reply is delivered on the same link using the saved src MAC address, except that it is now the dst MAC address. This avoids a route and an arp lookup. If the filer is connected to a switch, the switch will distribute NFS (or CIFS or HTTP) requests as they flow into the filer. Since the filer responds on the same physical interface as the one on which the request was received, there is no need to distribute responses out to the physical links on the trunk. Basically, the filer load-balances over the links of the trunk without having to de-multiplex the traffic out. Non-fastpath traffic and broadcasts are always sent out on one of the links of the trunk. One of the physical links in the trunk is marked as the "primary link" of the trunk. Non-fastpath frames, broadcast frames, etc., are sent on this "primary link." https://kb.netapp.com/support/index?page=content&id=3011178: How does a multimode vif interact with ip.fastpath? clearly explains: Therefore the fastpath-function will only see vif-interfaces as a single interface. ip.fastpath will not be aware of the individual physical ports or 1st level vifs/ifgrps that are members of the top level vif/ifgrp. Which one is correct?
... View more
You can selectively enable AutoSupport forwarding for each type of message in MyASUP; this can be done per-filer or for the whole site. Go to MyASUP for a filer and select Customize Notifications (bottom of page).
... View more
Are they CIFS shares? It is known that many Microsoft applications will create completely new file instead of making changes in-place; that is the reason for file folding option on NetApp. Many users editing many files could well account for this amount of changes.
... View more
It is not necessary a problem and cannot be answered without much more detailed information. But some points - Snapshot “grows” also when you delete data. - Snap reclaimable shows how much space would be freed if named snapshot were deleted. Effectively it shows you how much unique data is contained in snapshot Now in your example consider following scenario First you make snapshot hourly.2 Then you make snapshot nitghly.0 without changing anything Then you delete 20G of data and make snapshot hourly.1 If you look at shapshot “size”, hourly.2 would be zero (nothing has changed) and nightly.0 would be 20G. But if you now run “snap reclaimable nightly.0 hourly.1” it will show you zero bytes, because all data is shared between hourly.2 and nightly.0. Deleting nightly.0 would just shift space accounting to previous snapshot.
... View more