Hello Joe,
As an example mark inbound replication traffic to a desired DSCP marking (in this case af11) based on the parameters (e.g. NetApp NDMP replication)
ip access-list extended bulk-data
permit ip 10.1.10.0 0.0.0.255 10.2.10.0 0.0.0.255 eq 10000
!
class-map match-any marker-bulk-data
match access-group name bulk-data
!
policy-map qos-inbound-marker
class marker-bulk-data
set dscp af11
class class-default
You need to apply the marker to the interfaces inbound from the datacentre block, or optionally somewhere else such as the port the traffic source is connected to.
e.g.
interface te1/1/1
service-policy input qos-inbound-marker
Once the traffic is marked, you can make decisions on it at the metro link.
class-map match-any match-bulk-data
match dscp af11
!
policy-map qos-outbound-shaper-child
class match-bulk-data
bandwidth percent 75
class class-default
bandwidth percent 25
!
policy-map qos-outbound-shaper-parent
class class-default
shape average 200000000
service-policy qos-outbound-shaper-child
The policy needs to be applied to the outbound interface to the metro link.
interface gi 1/1/1
service-policy output qos-outbound-shaper-parent
This is a very basic policy, that would cover the stated requirement. Obviously if replication is NFS, iSCSI, or some other protocol, or perhaps all replication sources/destinations are in unique subnets, the matching ACL should change accordingly. If there is more than the management and replication traffic, a more complex QoS may be warranted. For example, network management traffic would normally want to be categorised and protected as it traverses the network into it's unique class. I would suggest looking at the Campus QoS Validated design guides and Medianet, for more information on mapping traffic to available hardware queues.