VPM configuration appears to be missing after installing a new VPM policy.
This issue was opened as a bug B#187168, and had been resolved in :
Note that upgrading to the SGOS versions above will not restore the old VPM policy. The missing policy will still be gone.
Blue Coat recommends that the VPM policy is restored from a recent backup.
Alternative work around is copy/paste XML-VPM code from the child ProxySG to the ProxySG that is having the issue.