ONTAP Discussions

Any issues to start to use a “broken volume “ at the destination?

heightsnj
866 Views

The source-volume S have been snapmirrored and the Destination volume is "D". Now, after the snapmirror relationship got broken off(the relationship has not been deleted), D becomes RW. 

 

At this point, i believe volume "S", and volume "D" are two separated volumes. 

 

My question:

1.   will "D" has any performance impact on the source storage?
2.   Will it cause any issues to use D in the status of "broken-off"?
3.   If the source volume has multiple SM relationships, then how much performance impact will multiple replications have on the source storage?

 

 

1 ACCEPTED SOLUTION

pedro_rocha
816 Views

1.   will "D" has any performance impact on the source storage?

No. Performance on S is dictated by operations on S. So D... D volume sits on an aggregate that delivers the performance of its aggregated disks.


2.   Will it cause any issues to use D in the status of "broken-off"?

no issue. You can use it as a normal volume.


3.   If the source volume has multiple SM relationships, then how much performance impact will multiple replications have on the source storage?

Answer to this is difficult because it depends on several aspects. Some are:

 - do replications occur at the same time? If yes, then more penalties

 - aggr where S is has a lot of drives (many drives delivers better performance and suffers less than a small aggr with the same workload)?

 

View solution in original post

3 REPLIES 3

pedro_rocha
842 Views

S and D are on the same storage system?

heightsnj
841 Views

No, it’s not, on separated clusters 

pedro_rocha
817 Views

1.   will "D" has any performance impact on the source storage?

No. Performance on S is dictated by operations on S. So D... D volume sits on an aggregate that delivers the performance of its aggregated disks.


2.   Will it cause any issues to use D in the status of "broken-off"?

no issue. You can use it as a normal volume.


3.   If the source volume has multiple SM relationships, then how much performance impact will multiple replications have on the source storage?

Answer to this is difficult because it depends on several aspects. Some are:

 - do replications occur at the same time? If yes, then more penalties

 - aggr where S is has a lot of drives (many drives delivers better performance and suffers less than a small aggr with the same workload)?

 

Public