Dave Smith
asked on
Exchange server 2010 VM (vSphere) - VSS broke in VM?
Failed to prepare guest for hot backup. Error: RPC function call failed. Function name: ISsnapshot in progress) Target machine x.x.x.x. RPC error, The RPC server is unavailable. Code 1722. Error: RPC function call failed. Function name: (ISSnapshotinprogress). Target machine x.x.x.x. RPC error. The ROC server is unavaialble. Code 1722
I ran vssadmin list writers, none of the writers are in an error state.
Another expert has recommended that the VSS may be broke - can anyone help to troubleshoot this issue?
I took a snapshot with quiesce checked and memory unchecked.
It failed to take the snap shot and returned with the following error:
An error occurred while saving the snapshot. msg.snaps.hot.error - quiesce-rror - view error.
I ran vssadmin list writers, none of the writers are in an error state.
Another expert has recommended that the VSS may be broke - can anyone help to troubleshoot this issue?
I took a snapshot with quiesce checked and memory unchecked.
It failed to take the snap shot and returned with the following error:
An error occurred while saving the snapshot. msg.snaps.hot.error - quiesce-rror - view error.
Last Comment
ASKER
Yes they have backed up successfully before;
This is not a new backup implementation.
The datastore sits on a SAN running RAID6
This is not a new backup implementation.
The datastore sits on a SAN running RAID6
Okay, to get you over the intiial "no backup" issue you can turn off the VSS-Application Aware feature of the Backup Job, this will at least get you backups, while you investigate.
A plaster (or bandaid)...
Okay, SAN and RAID6, could possibly be slow, based on usage, number of VMs on the LUN etc
We've also seen multiple VMs being backed up at the same time, cause this sort of issue with broadcast storm against a datastore (e..g slow)
A plaster (or bandaid)...
Okay, SAN and RAID6, could possibly be slow, based on usage, number of VMs on the LUN etc
We've also seen multiple VMs being backed up at the same time, cause this sort of issue with broadcast storm against a datastore (e..g slow)
ASKER
Cheers.
Can you advise on how I would turn of the VSS application aware in Veeam?
Can you advise on how I would turn of the VSS application aware in Veeam?
ASKER
I have another exchange server that's backing up so the database is backing up at least.
So you think this could be hardware related?
So you think this could be hardware related?
if its on the same SAN and Datastore ?
same OS verson, same version of Exchange and patch level ?
disable application processing in the Veeam Job, and see if that helps.
same OS verson, same version of Exchange and patch level ?
disable application processing in the Veeam Job, and see if that helps.
ASKER
Yes same hardware/OS and patch level.
Is disabling app processing a viable long term fix?
Is disabling app processing a viable long term fix?
it will give you backups, but it will not clear flush your Exchange logs.
I would say no, as a long term fix, but will give you backups
I would say no, as a long term fix, but will give you backups
ASKER
Thanks. So as a long term fix, what would you recommend?
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
The error you are getting suggests RPC is blocked by windows firewall or similar, there is a script at https://gallery.technet.microsoft.com/Testing-RPC-Connectivity-e0ab4901 that you can test RPC with,
This article from Veeam may also help https://www.veeam.com/kb1174
To start with you can just restart the RPC service, It's not a problem with VSS because it hasn't got that far, Veeam asked the server if VSS was running via a remote procedure call and the server did not reply.
This article from Veeam may also help https://www.veeam.com/kb1174
To start with you can just restart the RPC service, It's not a problem with VSS because it hasn't got that far, Veeam asked the server if VSS was running via a remote procedure call and the server did not reply.
ASKER
Hello, thanks for this.
I will go ahead and restart the RPC service on the Exchange server.
However, there are two services that relate to RPC. Remote procedure call (RPC) locator and Remote Procedure Call (RPC).
Which one should I restart or should I restart both?
I will go ahead and restart the RPC service on the Exchange server.
However, there are two services that relate to RPC. Remote procedure call (RPC) locator and Remote Procedure Call (RPC).
Which one should I restart or should I restart both?
Locator shouldn't be running, RPC starts it when needed. Doesn't matter if you stop and start both though.
ASKER
Thanks again,
Will restarting the service have any effect on the users or should I schedule it for out of hours?
Will restarting the service have any effect on the users or should I schedule it for out of hours?
ASKER
Cheers everyone! Opened up a new question in regard to the RPC service.
Cheers
Cheers
Exchange
Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.
213K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
is this a new backup implementation ?
and what is the underlying datastore supporting the VMs ?