according to acp.domain, it is set to 192.168.245, not to 192.168.254. 192.168.254 would be 16689344. Convert dotted-decimal to 32 bit integer by placing bytes right-to-left and you get option values. I.e. 192.168.254 == 0xc0.0xa8.0xfe => 0xfea8c0 == 16689344. I do not know if it safe to play with these options. But of course we do need some official procedure to change ACP network.
... View more
yes, this is expected. 3560 supports packet distribution by MAC or IP - in both cases all traffic between the same pair of systems will always use the same physical interface (unless interface failed). On NetApp side you could additionally set distribution to round-robin (which is not recommended) or port which will take in account TCP/UDP port. The latter may offer better distribution across aggregate members if traffic is multithreaded. Do not forget that load distribution for incoming traffic (from NetApp point of view) is configured on switch - there is nothing Netapp can do about it; and load distribution for outgoing traffic is configured on NetApp - again, switch does not do anything here. In general load distribution is effective only with large number of clients; but every single client will normally run over dedicated interface.
... View more
dump to remote tape is using rmt protocol that is based on rsh authentication. So you need to add source filer to /etc/hosts.equiv on destination. But that is not how NDMP will work. In case of NDMP you can either backup to locally attached device (tape) or initiate remote backup to another NDMP enabled host. No rsh and/or rmt is used in this case. I do not really understand the second question, but I assume you need to add second controller as BE client. Or add (another) tape drive to second controller. Do not zone the same tape to both controllers unless BE supports drive sharing. Usually it is separately licensed option.
... View more
"It is possible to have the backup server running in a VM...". The VM doesn't see any fc cards yet. "Enterprise" grade backup software supports libraries and tapes connected directly to NDMP host. Backup server itself does not need any direct connection to library in this case; server is using NDMP protocol to control library through filer. Whether BE supportes it, I do not know - you need to check BE documentation.
... View more
Another possibility is to use the same volume names on both sites (which makes it easier in real disaster case). For testing you would clone something_t1a into test_something_t1a and then export as exportfs -o actual=/vol/test_something_t1a /vol/something_t1a For CIFS you would export cloned path instead of original (under the original name). The idea with private storage is quite clever!
... View more
Cisco is apparently setup to tag VLANs on trunk. If you have single VLAN on this aggregate I do not see what is wrong in using port in access mode. If you really need multiple VLANs you need to create matching vlan interface on filer for each one, like vlan create svif0 345 for VLAN number 345 Please notice that version 7.x that you have cannot mix tagged and untagged (native) VLANs on the same physical interface. Of course, you can use it even for a single tagged VLAN, it just adds extra complexity without any advantage. P.S. I am not really sure which interface should be used for VLAN creation in case of multi-level VIFs. I think it is top-level one, but I am really not sure
... View more
Your aggregate is built with 15K RPM disks and spare is 10K RPM disk. By default NetApp won’t allow mixing different speed in the same aggregate due to possible performance impact. If you have no way to replace spare disk with 15K RPM one, you could change raid.rpm.fcal.enable to allow mix. Please post command output inline in message text. I use e-mail to read and reply (and I expect I am not alone); having to click click click through all screens just to see attachment takes far more time than simply answering message.
... View more
The rumours are, future Data ONTAP versions (I have heard about 8.1) will enable 32 => 64 bit conversion in place. I expect in this case all volumes will be retained "as is" together with all space savings.
... View more
SnapDrive can expand file system on physical LUN only on Windows. On Unix SD can expand file system only if this is on top of volume manager by creating another LUN and expanding volume using volume manager.
... View more
Yes, 2020 is just an intermediate unit to move data. There is not much to say about tape install. Check compatibility matrix to make sure your version of Data ONTAP supports your tape drive model, then just connect it to filer. It will be recognized automatically (at least for FC connection; for SCSI you probably need to reboot filer). FC filer port should be in initiator mode. You can find more details about tape management in Tape backup guide.
... View more
You could search NetApp knowledge base, I think there are some articles about this. But it is really simple. 1. Do SM initialize from source volume to FAS2020 2. Do SM initialize from FAS2020 to target volume 3. Do SM resync from source to target volume The point is to do resync. It will pick up common snapshot from step 1 and continue from there.
... View more
Regarding basic => dynamic conversion. When you convert (non-system) basic disk, Windows will create single partition of type 0x42 that covers all available space and create volumes inside this partition that correspond to previously existing partitions; partition table entries for them are removed. This special 0x42 partition will start immediately after MBR and so appear unaligned. But actual volumes should remain aligned after that. That is why I said mbrscan is just a hint. Unfortunately, dynamic disks do not offer any possibility to force particular alignment for volumes (at least, I am not aware of any tool to do it). There is really no compelling reasons to use dynamic disks with modern storage arrays and/or in virtual environment.
... View more
Compare incoming client data amount with disk write amount; this will give a hint whether all disk writes result from clients activity or are generated internally. For host spots - you could use statit to check IO distribution across disks. statit is advanced level command and so not really documented, nor is there any tool to automate analysis. The advantage is, it gives high level overview of filer activity in human readable form. The same data is available as various performance counters using stats command which may be easier to visualize.
... View more
If you search communities, you will find a lot of information how to check for partial writes. Here is link that was posted in one of threads: http://www.vmadmin.info/2010/07/quantifying-vmdk-misalignment.html. mbrscan is just a hint - at the end of day, it is real IO distribution that counts. It is just that in common case misaligned partition is more likely to cause partial writes. And unfortunately there is no publicly available tool to automate perfstat analysis, which is yet one more reason to open support case - they hopefully have more effective ways to deal with amount of information collected by perfstat. Regarding disk vs. net - IMHO disk should match net when averaged across some time interval. Consistent mismatch is one of indications of potential issues.
... View more
rw=@nfs-all-rw,nosuid exports to specified group only; all other clients are denied access. Have you tried ro,rw=@nfs-all-rw,nosuid - effectively giving default read-only to everyone else?
... View more