Hi there,
As you've experienced service disruption at a client site, I would suggest you should log a support case with our support centre, and ask for clarification of the documentation and correct steps to avoid an outage in the future.
I've brought this issue and this thread to the attention of the writer of that KB article.
Hi. thank you for reply.
that URL maybe for internal only.
I can't access that URL with partner level.
Yes. I will try this --exclude="command=netstat" today.
But what if Tech center need "netstat" , so I shoud find the main reason. ^^
I will post after running perfstat with exclude "netstat"
Hi All,
I have deployed the Ontap Select 9.3 in our setup. assigned the IP details to ontap select. I can able to access the ontap select administrator console from web client. As I added the ESXi hypervisor host without vcenter. SO I create the new cluster, enter the cluster details and next step needs to select the ESXi host but there is no ESXi host discovered. So kindly help me to deploy the ontap select. For your information find the below ontap select and ESXi details, also find the attached screenshot.
Ontap Select - 9.3
ESXi version - 6.5
Vcenter server - NA
Regards,
Manikandan S
Can we able to recover Volumes from netapp 7M post a deletion (no snap ,no snapmirror )
Any option likve VRQ in 8.3 ?the version is 8.1.X
The only known way is aggregate snapshots.
Hi savander,
apologies for that I did not check the availability of the KB article.
Sometimes perfstat can fail for various reasons, such as network latency or really high load on the controllers too, so it's important to understand what is causing it for sure.
In case the netstat output is needed by support, you might look into disabling some other unneeded collection for that perfstat; however support will be able to guide you in what to collect if you need to perform a partial collection.
Just for clarification, what Giacomo is refering to is this:
Hmmmmm,
Thank you very much Sebastian.
Now we'll attempt to have some official answer by support on the sequence that you're suggesting, and on which I completely agree as suspected after that fault.
My best regards,
We have a system that is configured as follows:
FAS8020, DataONTAP : 8.3.2 P2 HDD size 2.0TB SATA
Name Node Type used% Available Used Total Volume Count Disk Count
System_A_aggr01 System_A Std 2 51.38TB 1.01TB 52.39TB 2 42
System_A_root System_A Std 32 2.83TB 1.32TB 4.15TB 1 5
System_B_aggr01 System_B Std 2 51.38TB 1.01TB 52.39TB 2 42
System_B_root System_B Std 32 2.83TB 1.32TB 4.15TB 1 5
Only 1 spare drive per system. All HDD used.
Client has decided they want to increase the number of spares by reducing the root aggregate from 5 to 3 HDD. There is one SVM defined and although there is only a small amount of data on it they would prefer to preserve that if possible.
What is the best way to achieve this? Worse case is trashing the system and rebuild it, but we'd prefer not to if we can avoid it
Is it possible to drop disks out of an aggregate providing there is sufficent remaining capacity to hold the data on the reduced number of disks?
My experience of DataONTAP is very limited so any guidance will be very much appreciated.
Many thanks
Chris
There is no way to remove data disks from aggregate. It is possible to convert RAID_DP into RAID4 by removing one parity disk (but RAID4 is frowned upon today). Alternatively you can build new aggregate (it can use minimal number of disks initially, even 2, so you can utilize existing spares) and relocate root volume to this aggregate, then destroy original root aggergate. Relocating root volume is possible non-disruptively in your case (but see http://community.netapp.com/t5/Data-ONTAP-Discussions/Epsilon-and-root-move-from-an-aggregate-to-anoter/m-p/138789#M30619 for caveats).
Thanks for the swift reply. I'll review the procedure. If I used the two spares to make a new aggregate I guess you can simply add a 3rd disk later after the original root aggregate has been deleted and more drives become available?
Otherwise I would need to delete the data aggregate to release sufficient disks to make a new one. That isn't a major problem as the small amout of data that exists (<1GB) can easily be copied elsewhere.
Chris
wrote: I guess you can simply add a 3rd disk later after the original root aggregate has been deleted and more drives become available?
Correct. You can both go from RAID4 to RAID_DP as well as add more data disks.
I think there is an option in new ONTAP versions where the volume is not actually deleted until x hours later.
I think it can be set to X as well. If I remember correctly its 6 hour by default.
So it all depends on how fast you are .
hi
if you only have that snapmirror base snap: i would say that you need to run it more frequently or increase the volumes size, not much way around it.
if you have multiple snapshots and not just the base one of snapmirror. you can enable sanp auto-delete, but that's a risk as it might get to the base snapshot at the end and break the snapmirror.
Gidi
one more thing.
if you do willing to re-initialize your system (both nodes) and upgrade to 9.2+, you can use ADP. and gain around 4.5TB more then the raid DP>RAID4 conversation (so around 8.5 TB saving in total from what you have now)..
https://kb.netapp.com/app/answers/answer_view/a_id/1030450
Gidi
Hi,
AS per knowledge you can't recovery deleted volume on the 7-mode without aggreagate snapshot.
There is options C-dot after 8.3
cdot::>vserver show -fields volume-delete-retention-hours
you can set retenation hours for if you delete volume between retention hours you can recover the volume.
Thank you,
Sandilyan
In worst case scenarios, recovery by third party providers such as Kroll Ontrack or Drive Savers may be possible (at the expense of availability of other volumes) - this KB article outlines the options, but we do not provide endorsement of any of their services.
Hi,
In 7-mode system there is no way to get deleted volumes back without aggregate snapshots.
Mostly, aggregate snapshots using for a SyncMirror purpose, you should check it.
I'd like to send this to the powers that be in the ONTAP 9.3x product line:
Please stop making these drastic changes to OCSM.
They are disruptive, annoying, and painful.
I like the the tree view on the left in 9.3. However, many items are not arranged in such manner, case in point, volumes.
When you look at volumes, they display only in the main OCSM frame. There are no details, or commands available, unless you expand the volume (in the main frame), and then find the small print link at the bottom right of the expanded paragraph, "Show more details".
Then you get a new main frame with commands split between some shortcuts at the top left, and a menu at the top right.
And if you try to view volume info quickly, this arrangement will not allow it. You must go back to the tree view and start over.