Hello gurus,   One of client storage FAS 2552 aggregate shows 99% and we have moved some volumes to other aggregate now. This is old storage and what is the recommended approach by netapp in order to increase aggregate space.    Can we remove few disks and put high capacity disks in it and form a new aggr ? What is recommended practise in this case   Disk details 00.0  to 00.3 --> 381.3GB 520B/sect    00.4 to 00.23 -- >  1142.3GB 520B/sect         ... View more

I want to migrate data from am Windows2012 server to a NetApp CIFS share.   robocopy \\winserver\source \\vserver\destination /MIR /COPYALL /XO /FFT   It does the initial copy without errors. In the second run I ant to copy only changed files, but robcopy incorrectly recognizes everythig as changed and does the whole job again. Between two Windows servers robocopy works as expected. Only modified files are transferred in the second run.   Anybody else with this problem?   Holger Zickner ... View more

Hello. I am writing because I have one question. Is there a function that allows only 'specific ip' to be accessed when using the cifs function in Netapp 7-mode? Settings such as /etc/exports for NFS. If there is a document related to it, please help me. ... View more

System info: FAS2720 running ONTAP 9.7P17, with 2 x DS212C expansion shelves with 3.5" 10 TB SAS disks. 8 of the disks on the base unit are root/data partitioned disks and are hosting RAID-TEC root aggregates. The expansion shelves have single-partitioned disks.   What I want to do: make a data aggregate out of all the disks in order to maximize spindles. All the expansion shelf disks are showing as spare and owned by node 1, with their root and data fields showing as unowned. By default, I can't create that aggregate because the 8 base unit disks hosting the root aggregates have a different partition scheme than the rest. Therefore, I'm trying to make the other disks have the same root/data partitioning as those 8 disk. But it's not working.   After disabling disk autoassign, here's what I'm doing for the first disk : ::> storage disk create-partition -source-disk 1.0.1 -target-disk 2.0.1   This initially works: "storage disk show ..." shows 2.0.1 with root/data partitions owned by node 1. If I switch to the aggregate creation GUI, I now see one more disk in the relevant row than I did prior. All good. However, after a few minutes, if I do "storage disk show ..." again, I see that 2.0.1 has lost its root/data ownership. ONTAP appears to have silently reverted my "storage disk create-partition ..." command.   To test this, I did "storage disk create-partition ..." on all the relevant disks as quickly as possible, then created an aggregate, which worked. However, after that, "storage disk show ..." showed nothing in the aggregate field for those disks. Also, while I was able to create volumes on it via the CLI (after assigning it to the correct SVM), I was unable to in the GUI because the aggregate didn't appear in the list.   I'm stumped at this point! Anyone? ... View more

    I need a netapp technical document that says 'no problem' with disabling SSH default port in 7-mode or default port coming out of port scan.   Is there anyone who can help me with the above? ... View more