Is this an HA pair? /etc/rc /etc/hosts but if your nfs clients are mapped via hostname, they need to unmount and remount to new name. Too be honest with you, depending on how critical your environemnt is, bringing down a filer to change the host name, other than just to set it to business naming standard, doesn't add much value. You have to weigh Risk Factor vs End goal in my opinion... It can all be done
... View more
I find it easier to do at a global level than per snapmirror relationship. You need to do something like this set-naoption replication.throttle.enable on and set-naoption replication.throttle.enable off Create two scripts and create AT jobs in windows to schedule it. Enjoy!
... View more
What type of filer do you have. Also, if you have at-fcx you will see something like Shelf 1: AT-FCX Firmware rev. AT-FCX A: 38 AT-FCX B: 38
... View more
Ok fellow DFM PA users, I need some clarification b/c i'm coming up empty a little.. We are seeing two different latency numbers when I'm viewing a particular issue Under the system storage summary view in PA, if we look at Avg Latency by per protocol, we see an issue with cifs starting lets say 1.5 hours earlier, then if we were looking at the volume level latency for cifs by optype. So, what is the difference between those two views and which is more reliable for troubleshooting cifs latency. When I look at it on the filer level i usually do something like stats show -n 50 -i 1 volume:*:cifs_read_latency volume:*:cifs_write_latency I think the one in system summary view is - stats show -n 50 -i 1 cifs:*:cifs_latency Any explaination is greatly appreciated it. Thanks
... View more
Try this.. but you will get everything.. invoke-nasnmpwalk .1.3.6.1.4.1.789.1.1.2.0 I tried to do invoke-nasnmpwalk -RAW but that didn't give us anything..
... View more
Steven, I know we can tell the API, but can you imagine building a role for all of PS toolkit and different scenarios... Just not my cup of tea, that's all
... View more
Only reason to go to 4.5 is if you plan on in the future to goto powershell 4.0 which isn't necassary. Stick with 4.0 that's just my opinion
... View more
IMHO, You're fighting a losing battle.. Why on earth would you want to do this. the powershell cmdlets let you do many things so the optimal solution is for someone who knows what they are doing in powershell and netapp and then you wll be all set Just my opinion of course
... View more
This is an interesting topic.. I've done this before with straight powershell for netapp to determine which lunID's are mapped to igroup and lun. I like how you did the mssql piece
... View more
This is known as a mixed mount which are wonderful. Just get the UID from the unix users and add them to the passwd file. Are these other users AD as well, b/c if so you want to make sure your unix id nad AD account matches
... View more
You shouldn't need to write your own cmdlet. You can use the API cmdlets to grab this info Look at get-navol and look at clonechildren property. Should be all done for you..
... View more
You need to create the replica volume, restrict it and then initialize the snapmirror in order for it to become a mirror. To quickly identify all your mirrored volumes, you can do it in powershell with the ontap toolkit - get-navol | ? {$_.raidstatus -match "read-only"}
... View more
Also, refer to this thread - https://communities.netapp.com/thread/32808 Doesn't appear SMB 3.0 will ever be supported in 7-mode. It's only for cDOT.
... View more
I could be wrong, but it's my understanding that SMB 3.0 isn't fully supported until 8.2. Also, 8.1.1 is very buggy to begin with, so you should look to upgrade Your last statement lists CIFS as SMB disabled, do you mean signing?
... View more
Like i've said, I've done it for volume based, on a windows box but it's more trouble than it's worth. For example, you can have multi-level alerting setup where at x amount of latency it kicks off perfstat. Let's say you set your perfstat for 6x5, well that takes a long time, and your volume could again get into the state where it tries to kick off another perfstat. If you have an operationis staff, I would make sure you setup multi-level alerting and then have the ops staff kick off the perfstat once they get an email for that specific volume. I can try to dig up my perfstat script, but in my opinion, you are swimming up river, especially with volume. What are your counters and thresholds?
... View more
Just a word of caution with kicking off perstat from alarm triggers. I've done this in the past from windows, but it really depends on what counter you are using to kick off the perfstat. For example, if you use volume:nfs_write_latency, if you a large performance problem and it causes write latency across multiple volumes, perfstat will try to kick off X times. I think you have to have system level counters in order to have this affective. As for your setup, mine was a little different, all windows, on single host so it was a little easier
... View more
Ok, so here is a quick high level We have a VSM that is managed currently at the filer level with snapmriror.conf file. We are implementing snapvault, but we are only implementing the management of the policy from the mirror to the vault So for example Our snapvault looks like /vol/mirror/- /vol/sv_mirror/snapvault_qtree We import this into PM dataset that we custom design a policy and schedule for it. Our primary data volume, we select NONE because it's on a mirror and we know we can't take a snapshot of the read-only volume. We then setup the transfer to back up and then retention. Now, this works 100% on schedule, but does not work on-demand. It fails, b/c protection manager is continuing to try to take a snapshot on the primary mirror. This is frustrating b/c we tell it in the policy not to do it. Here is the error from the job Volume_SV: Could not create snapshot for volume 'filera:/sv_voltest_m' (274). Reason: Snapshot operation not allowed on a read-only volume It's like there is a bug b/c we don't want it to take a snapshot on primary b/c we know it's a read only. We just want it to do a transfer and then take a snapshot. Am I missing something? We are running OCUM 5.2 p2
... View more
