Backup DC's on Windows Server Standart 2008 R2

[fam_by]

Hello, I have 2 DC on my ESX host's that running MS Windows 2008 R2 Server.
I want to backup them.

I've configured backup job on my Veeam Backup & Replication Server, that also runs on this Esx hosts, to enable application-aware image processing and guest file system indexing and don't enable VMware tools quiescence. I've set Guest OS credentials to my domain admin account credentials.
And then, when I've started this backup job, I've received this error :

Indexing guest file system
VSSControl: GetAvalableIndexVolumes failed
RPC function call failed. Function name: [GetAvailableIndexVolumes]. Target machine: [10.10.0.7].
RPC error:The RPC server is unavailable.
Code: 1722

Freezing guest operating system
VSSControl: IsSnapshotInProgress failed. Transaction logs will not be truncated.
RPC function call failed. Function name: [IsSnapshotInProgress]. Target machine: [10.10.0.7].
RPC error:The RPC server is unavailable.
Code: 1722

What I am doing wrong? Please help me. Other VM's that included in this job backs up correctly with this options.

[Vitaliy S.]

Hello,

It seems like the RPC service on your DC is unavailable. Could you please check it with DC's Windows Event logs if you have any RPC related errors on this VM? By the way, could you tell me if you have the latest VMware Tools installed on this VM?

Thanks!

[fam_by]

Hello. I've checked Windows Event logs - there aren't any errors related to RPC Service.
We hawe ESX hosts with Vsphere 4.1.0, 260247. And of course we have wmware tools that going with this version of hypervisor.

[fam_by]

this is all that I find in my Event Logs.

Code: Select all

/////////////////////////////////////////////////////////////////////////
Log Name:      System
Source:        Service Control Manager
Date:          13.11.2010 10:18:50
Event ID:      7045
Task Category: None
Level:         Information
Keywords:      Classic
User:          Domain Admin
Computer:      DC
Description:
A service was installed in the system.

Service Name:  VeeamVssSupport
Service File Name:  C:\Windows\VeeamVssSupport\VeeamGuestAgent.exe
Service Type:  user mode service
Service Start Type:  auto start
Service Account:  LocalSystem
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
    <EventID Qualifiers="16384">7045</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8080000000000000</Keywords>
    <TimeCreated SystemTime="2010-11-13T07:18:50.453650000Z" />
    <EventRecordID>55423</EventRecordID>
    <Correlation />
    <Execution ProcessID="476" ThreadID="5252" />
    <Channel>System</Channel>
    <Computer>DC</Computer>
    <Security UserID="S-1-5-21-266111420-1449510511-3636319022-19675" />
  </System>
  <EventData>
    <Data Name="ServiceName">VeeamVssSupport</Data>
    <Data Name="ImagePath">C:\Windows\VeeamVssSupport\VeeamGuestAgent.exe</Data>
    <Data Name="ServiceType">user mode service</Data>
    <Data Name="StartType">auto start</Data>
    <Data Name="AccountName">LocalSystem</Data>
  </EventData>
</Event>

/////////////////////////////////////////////////////////////////////////

Log Name:      System
Source:        Service Control Manager
Date:          13.11.2010 10:18:51
Event ID:      7036
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      DC
Description:
The VeeamVssSupport service entered the running state.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
    <EventID Qualifiers="16384">7036</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8080000000000000</Keywords>
    <TimeCreated SystemTime="2010-11-13T07:18:51.156788500Z" />
    <EventRecordID>55424</EventRecordID>
    <Correlation />
    <Execution ProcessID="476" ThreadID="2700" />
    <Channel>System</Channel>
    <Computer>DC</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="param1">VeeamVssSupport</Data>
    <Data Name="param2">running</Data>
    <Binary>56006500650061006D0056007300730053007500700070006F00720074002F0034000000</Binary>
  </EventData>
</Event>

/////////////////////////////////////////////////////////////////////////

Log Name:      System
Source:        Service Control Manager
Date:          13.11.2010 10:19:57
Event ID:      7036
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      DC
Description:
The VeeamVssSupport service entered the stopped state.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
    <EventID Qualifiers="16384">7036</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8080000000000000</Keywords>
    <TimeCreated SystemTime="2010-11-13T07:19:57.283058100Z" />
    <EventRecordID>55425</EventRecordID>
    <Correlation />
    <Execution ProcessID="476" ThreadID="404" />
    <Channel>System</Channel>
    <Computer>DC</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="param1">VeeamVssSupport</Data>
    <Data Name="param2">stopped</Data>
    <Binary>56006500650061006D0056007300730053007500700070006F00720074002F0031000000</Binary>
  </EventData>
</Event>

[Vitaliy S.]

In this case please send the DC's event logs to our support team and let them assist you with the troubleshooting. By the way, could you tell me whether you have the same error on your second DC while doing a backup job?

[fam_by]

Yes, I have this error on all my MS Windows Server 2008 R2 virtual mashines.
Which logs should I send?
PLease tell me.

[Vitaliy S.]

You need to send Windows Event logs (Application and System) from both DCs as well as the corresponding job log from Help->Support Information located in the backup console.

[Vitaliy S.]

Also, please send us Veeam guest agent log files from failing VM , these can be found here:

Code: Select all

C:\ProgramData\Veeam\Backup

[Mike]

For all who read this and are still looking for a solution, disable your windows firewall in 2008 R2 and test it again.
In all my cases this worked, I am testing what to configure in the firewall to get it working, but keep it as secure as possible.

[orion2598]

I thought Veeam v5 was supposed to fix these RPC problems? I'm still getting them on most of my VM's even with the latest version.

[Vitaliy S.]

Hello Greg,

The RPC problems you describe might have a completely different origin, as those errors might be on their own and there is nothing to do with Veeam. If you have those messages, please make sure you don't have any erorrs in Windows Event log. If you do have those, check their Event IDs with Microsoft KB, might be helpful.

Thanks!

[Gostev]

Yep these are some internal guest errors referencing RPC. Something is wrong with this specific guest I think. Thanks!

[fam_by]

Hello.
The problem was in Dynamic ports that uses RPC.
Here are the article http://support.microsoft.com/kb/154596 how to resolve this issue.
Thanks to support.