I have a scenario where i have two datacenters with two core switches each. Backup solution is hosted in one of the DC. Eventhough i have 1Gbps dark fiber links, it is almost utilized to 980Mbps and we are facing serious performance issues with bussiness applications.
I would appreciate if someone can help me with a solution to limit the backup traffic on the WAN links.
I can do class-map for identifying the backup traffic based on the destination IP address.
Would "priority" MQC command help in this regard? I can give a priority of say 750Mbps to the genuine traffic , so that it is always guaranteed. Whenever genuine traffic is not much backup can takeover the free bandwidth.
Please help me.
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
No, the backup-traffic class bandwidth set to 20 percent, in theory, will guarantee a minimum of 20%. More can be used if it's not otherwise being used (which is often a good thing, otherwise available bandwidth goes unused).
Because unused bandwidth can be used with such a configuration, you might even decrease the bandwidth percentage for the backup traffic. You might go to a little as 1%. You do need to consider whether the backup traffic obtains enough bandwidth to complete in a required time window, if there's one.
I would also recommend enabling FQ in class-default, and if there's more than one backup flow, enabling FQ in its class too (if supported by the IOS version).