v.7 & Oracle VSS Backup

[srebuccicellularline]

Hi everybody,
I tried to find the solution by myself but at the present I've no idea.

In my infrastructure there are many machines with SAP on Oracle: I'm trying to backup them application consistent but at the present the job fails with this error
VSSControl: failed to freeze guest, wait timeout.

The timeout it's about a minute and an half (1:30 minutes).

With a colleague SAP Expert I've tried to debug the problem

1) The DB is on ARCHIVELOG MODE
2) The timeout expires only with VSS enabled and with the VSS Oracle Writer started

The Event Log says

Volume Shadow Copy Service error: Unexpected error calling routine XML document is too long. hr = 0x80070018, The program issued a command but the command length is incorrect.
.
Operation:
Writer Modifying Modifying Backup Document
Context:
Execution Context: Requestor
Writer Instance ID: {CDC87286-6F0A-473E-A4E3-CEA3ACEE4349}

I've already installed the HotFix for this problem http://support.microsoft.com/kb/2807849/en but it doesn't solve anything.

There is a solution for this problem?

Thanks,

PS At the moment I'm backing up crash consistent and the machine could be reboot and patched in any moment.

[srebuccicellularline]

Hi everybody,
I've found a solution.

Backup Oracle with VSS Writer under Windows
1) Put Oracle in ARCHIVELOG MODE
2) Start Oracle VSS Writer with the sysdba user, mode automatic
3) Start Windows Volume Shadow Copy Service with Local Service, mode automatic
4) Start Microsoft Software Shadow Copy Provider with Local Service, mode automatic

With this settings the job complete successfully and the Event Log now say

VSS-04107: successfully backed up component Oracle Database (FULL)

Additional info :
Oracle VSS writer version 11.2.0.2.0 Production.

I hope my effort could help,

[EBoucq]

Hi,

I have the same problem here.
What do you mean by " Start Oracle VSS Writer with the sysdba user, mode automatic" since sysdba user (which is system) isn't a windows account ?
Thanks
Eric

[Vitaliy S.]

Hi Eric,

Yes, it is a Windows account, I believe Simone meant that the writer service should be started under the user account with SYSDBA privileges.

Thanks!