Backup finished with warning

[Perry]

Multiple VM Backup finished with a warning on one VM. Why would this happen:

1/27/2017 1:30:08 AM :: Failed to finalize guest processing. Details: Failed to call RPC function 'Vss.TruncateSqlLogs': Error code: 0x800706d9. Failed to invoke func [TruncateSqlLogs]: There are no more endpoints available from the endpoint mapper.. RPC function call failed. Function name: [BlobCall]. Target machine: [192.168.1.20]. RPC error:There are no more endpoints available from the endpoint mapper. Code: 1753.

[Shestakov]

Hello Perry,
Please provide a support case number as required when posting a question related to the technical error.
Usually it means that transaction log were not truncated for some reason.
Thanks!

[Perry]

Rebooted the VM in question and re-ran the backup. No error this time.

[Shestakov]

NIce to know. Once the issue is back, please contact the support team to find out the issue.
Thanks!

[WinstonWolf]

Hello ,

We have the same error . Windows 2016 Server . Support Ticket Number : 02405025 .

Need help .

Thanks

[Shestakov]

Unfortunately Perry has not shared the case number, so we don't know how the investigation has been finished.
What kind of assistance do you need? Are you not satisfied with the support team performance?
Thanks!

[Mario_JHRZ]

was this related to the windows firewall? did anyone here found out why those warnings occur?

[Shestakov]

Hello Mario,
Do you have the same issue? If yes, please share your support case number.
Thanks

[Edwin009]

This was the reason when i got Code: 1753 error

In vSphere 5.1, Microsoft Volume Shadow Copy (VSS) was introduced to replicate the quiesced state of the operating system or application. If quiescing is enabled for virtual machines running Windows 2003, 2008 or 2012, vSphere Replication creates and removes the virtual machine snapshot to create an application quiesced replica. If vSphere Replication and the backup software try to create or remove a snapshot at the same time, one process fails.

The virtual machine may have a backup snapshot. Whenever vSphere Replication or Host Based Replication (HBR) try to consolidate the disks, it does not add a new redo log to the disks. Later, the backup snapshot is removed and then, whenever HBR tries to consolidate the disks, it adds a new redo log to the disks.

This issue occurs because there is a parent disk open and HBR tries to consolidate the disks during replication.
Resolution
This is not a VMware issue. However, VMware has made code changes in ESXi 5.1 Update 2 to the improve the existing consolidation issue. For more information, see the VMware ESXi 5.1 Update 2 Release Note. You can download the latest release of ESXi 5.1 from the VMware Download Center.

There is a known interoperability issue between VMware vSphere Replication 5.1/5.5 and snapshot-based backup products. When a virtual machine is protected by vSphere Replication and it is also part of a snapshot-based backup job, snapshot conflicts can occur.

To avoid snapshot conflicts and related consolidation issues, perform one of these two options:

Ensure that vSphere Replication protected virtual machines which are also part of a backup schedule do not use quiescing, so that a snapshot will not be taken.

Or

Use a backup solution that is not snapshot-based.