Error 200's and query's being invalid

Also the policy that is defined properly in the NBU policies list with the proper query.  Appears it translates the \ to %5C.  I saw %5C in the clients list for the policy above instead of slashes to separate the folders.  So when %5C is in the NBU policy perhaps it translates that to %255C and that causes the query to fail.  So the question would be, how does the clients tab change from slashes to %5C for the query and why does NBU even allow that?

Hello Marianne,

 Thanks for your reply. 

 The backups are running fine.  But this happens only for sometime ( time to time the VIP policies seem to become corrupt) NOT DAILY.  

\ separators seem to be replaced with %CM.  When this happens the query then reports no backups scheduled to run as it’s not finding any VMs to match the query.

1.       How can we prevent this from happening?
2.       If we can’t prevent it, how can we check the validity of the defined query on some interval through some automated process?  Keep in mind we have many VIP policies per master server and more master servers that each handle more number of clients.

Policy that is defined properly in the NBU policies list with the proper query.  Appears it translates the \ to %5C.  I saw %5C in the clients list for the policy instead of slashes to separate the folders.  So when %5C is in the NBU policy perhaps it translates that to %255C and that causes the query to fail.  So the question would be, how does the clients tab change from slashes to %5C for the query and why does NBU even allow that? ( Attached Screenshots)