Quantcast
Channel: All MSA Storage posts
Viewing all articles
Browse latest Browse all 8327

Re: HPE MSA 2050 Replication Errors

$
0
0

Your configuration looks ok but there are many things which actually improve system overall performance which may in turn improve replication as well.

Most important you should always update your MSA all components with latest firmware.

You should utilize both Virtual Pool instead of one Pool.

I hope you are taking advantage of sub-lun auto tier feature as well.

If over commit enabled then 3 internal snapshots will not be full provisioned. So you can save more space. This is important because when you do replication on Thin provisioned volume then only allocated blocks gets copied to another array.

It's important to understand rate of data change and based on that we should set subsequent Replication interval . This is not COW (Cope On Write) technology rather this works with ROW (Redirect On Write) technology

If you are keeping Replication Snap history for each replicated volume then you should consider space consumption, tree structure for those as well. You can keep max 16 replication snap

Refer latest Controller firmware release notes, MSA 2050 best practice white paper and MSA Remote Snap Software White paper to get more tips and suggestion.

 

Note: MSA is entry level Storage Box and we shouldn't expect Deduplication in this. HPE having other high end Storage box like 3PAR and Nimble where Deduplication available

 

Hope this helps!
Regards
Subhajit

If you feel this was helpful please click the KUDOS! thumb below!

***********************************************************************************


Viewing all articles
Browse latest Browse all 8327

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>