VSS Writer failures during VM backup of server with Oracle application installed

I am experiencing problems with Hyper-V backups on one of our VMs which has the Oracle application installed.  I use DPM 2012 R2 but have also tried this with Windows backup which fails as well (hence posting it to this forum).  The Oracle VSS Writer is not installed on the server and the VSS writers which fail (timeout) are the following:

System Writer

ASR Writer

Shadow Copy Optimization Writer

WMI Writer

Registry Writer

IIS Config Writer

COM+ REGDB Writer

After initial investigation I have discovered that when the customer runs a script to stop the Oracle processes / services it seems that the WLS_Reports service / processes are causing the problem as when stopped by the script the backups run successfully but when running the backups fail and the above VSS writers timeout (further errors in the thread posted in the DPM forum linked at the bottom of this).  

I have also noticed that when I stop the Hyper-V Volume Shadow Copy Requestor the backup runs successfully but connectivity to the server briefly times out which is not an ideal solution.

When the backups fail I get 2 errors in the application log on the VM:

Event Id 12293, VSS - Error calling a routine on a shadow copy provider {GUID for the Hyper-V IC Software Shadow Copy Provider}.  Routine details PreFinalCommitSnapshots ({GUID}, 5) [hr = 0x800705b4, This operation returned because the timeout period expired.]

Event Id 19, vmicvss - Not all the shadow volumes arrived in the guest operating system.

I also get other errors and symptoms which I have posted in the DPM forum here: Backup fails for a Hyper-V guest with VSS Writer failures using DPM 2012 R2 - Hyper-V guest has Oracle application installed

I know that the fact this server experienced no problems with backups before Oracle was installed and is successful when the WLS_Reports service is stopped would lead people to assume that the cause is related to the Oracle service but I need to know if there is anything from a Windows / Microsoft point of view that I need to be aware of which will help me resolve this issue.  

Thanks

Chris