If the provider is actually policing your traffic, then it's fine not do anything if you don't mind them discarding your traffic when you go above your contracted rate or if you know that your traffic would never go above your contracted rate. An example of the latter would be a front side 100 Mbps (LAN) connection with your backside gig (MAN) connection that's policed to 100 Mbps.
If it's possible that you can oversubscribe the 100 Mbps MAN, and the oversubscription can be due to the SAN traffic, and considering you want to protect your voice, then QoS is a must.
If you only have voice and SAN, you only need to provide the two classes for voice (as you done); also assuming you've allocated enough bandwidth. You can leave off SAN-TRAFFIC, i.e. let it fall into the default.
If you might have other traffic other than voice and SAN, you can go with a policy much like what you have except you can set the SAN bandwidth to a setting to split the bandwidth with your other traffic as you like. The 60% setting doesn't limit SAN to 60% it means it gets 60% if the other 40% is in demand. (Except for LLQ, bandwidth is a floor, not a maximum.) If this is what you intend, that?s find.
However, your policy would assume all the bandwidth of the gig is available so you need to create a hierarchical policy that limits the total to 100 Mbps.
e.g. (12.4 syntax - assumes gig limited to 100)
policy-map DC-DC-EDGE-shape
class class-default
shape average percent 10
service-policy DC-DC-EDGE
