Disclaimer
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.
Liability Disclaimer
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.
Posting
Since I don't know what your router is, or what IOS it's running, unable to be precise, but the following will work on many Cisco ISRs.
I have Cisco 2821 with 12.4 (3h).
Okay, pre-HQF QoS - the policy I showed will work on that.
Likely that shouldn't be too difficult to accomplish, but I would caution about giving highest priority to backup/replication traffic.
Can you please elaborate why you are advising caution over hishest priority to backup/replication traffic? Answer must be something obvious but I am not clear.
Sure, any time you give priority to one kind of traffic, it's often at the expense of other traffic. If the traffic is "bulk" or bandwidth greedy, it will usually take full advantage of priority to bandwidth.
If you're talking about like real-time video, that should have priority.
If you're talking about streaming video, that should have enough bandwidth for its average bandwidth, and sufficient buffering to avoid drops during bursts.
If you're talking about background replication, unless there's a time constraint, it often only works well with low priority. If there is a timing constraint, i.e. the replication has to complete within a certain amount of time, often the streaming bandwidth approach is fine.
