From this alteraforums post:
If you have setup or hold violations for data paths going to or from the derived clock domain and the derived clock uses global routing, then try nonglobal routing.
There is a large delay associated with the global buffer. This delay contributes to clock skew for cross-domain data paths. The clock skew might be less with nonglobal routing than with global routing.
Nonglobal routing will cause some skew for paths within the derived-clock domain. In the post for design guideline #3, see the discussion of on-die variation for nonglobal routing in clock paths.