Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

NetApp Exam NS0-194 Topic 4 Question 37 Discussion

Actual exam question for NetApp's NS0-194 exam
Question #: 37
Topic #: 4
[All NS0-194 Questions]

You are working on a fabric MetroCluster. After a site failure, the plex starts to resync automatically to the aggregate mirror of Aggr1. The plex now shows a status of resyncing. During this process, you experience a slow resync of the SyncMirror plex.

In this scenario, how do you solve the problem?

Show Suggested Answer Hide Answer
Suggested Answer: C

Contribute your Thoughts:

Kanisha
26 days ago
I think option C is the way to go. Tuning the resync speed is the key, and a QoS policy is the perfect tool for the job. Plus, it's probably more elegant than using the storage raid-options command. *winks*
upvoted 0 times
...
Fernanda
27 days ago
Hmm, I'm not sure. Maybe I should just throw the whole fabric MetroCluster out the window and start over. That would solve the problem, right? *laughs*
upvoted 0 times
Ligia
1 days ago
B) Destroy and re-create plex, then run a baseline sync.
upvoted 0 times
...
Lucy
2 days ago
A) Add more disks to the aggregate to add more I/O capacity.
upvoted 0 times
...
...
Malcolm
1 months ago
Option B is the way to go! Destroying and re-creating the plex, then running a baseline sync is the best way to ensure a clean slate. Who needs slow resync when you can just start fresh?
upvoted 0 times
Susana
7 days ago
Option B is definitely the best solution. Starting fresh with a baseline sync is the way to go.
upvoted 0 times
...
...
Stephane
1 months ago
I'm leaning towards option D. Tuning the resync speed using the storage raid-options command seems like a more direct approach. Plus, it's probably faster than setting up a QoS policy.
upvoted 0 times
Bronwyn
1 days ago
Let's go with option D then. It seems like the most straightforward solution in this case.
upvoted 0 times
...
Kristin
10 days ago
I agree, it's a more efficient way to address the slow resync issue compared to setting up a QoS policy.
upvoted 0 times
...
Tegan
11 days ago
Option D is a good choice. It allows you to directly tune the resync speed using the storage raid-options command.
upvoted 0 times
...
...
Barney
2 months ago
I think option C is the way to go. Tuning the resync speed using a QoS policy makes the most sense to me. Adding more disks might help, but that's a lot of work.
upvoted 0 times
I agree, option C seems like the best solution here.
upvoted 0 times
...
Arlen
5 days ago
Yes, using a QoS policy to limit concurrent I/O to the aggregate makes sense for resolving the slow resync issue.
upvoted 0 times
...
Stephanie
29 days ago
I think tuning the resync speed with a QoS policy is the best approach in this situation.
upvoted 0 times
...
Owen
1 months ago
I agree, adding more disks seems like a lot of effort. Option C is a simpler solution.
upvoted 0 times
...
Hyman
1 months ago
Option C is a good choice. Tuning the resync speed with a QoS policy is efficient.
upvoted 0 times
...
...
Reena
2 months ago
I think tuning the resync speed by adding a QoS policy and limiting concurrent I/O to the aggregate is the way to go.
upvoted 0 times
...
Lamar
2 months ago
I disagree, I believe destroying and re-creating the plex with a baseline sync is the best solution.
upvoted 0 times
...
France
2 months ago
I think we should add more disks to the aggregate to increase I/O capacity.
upvoted 0 times
...

Save Cancel