Troubleshooting

26 October 2023

The following sections discuss possible scenarios for recovering protection runs from a failed state.

Disk Consolidation Failure

Cause

If you are protecting VMs in the VMC environment, Cohesity will use HotAdd transport mode for backup and recovery. During the backup or recovery operations, virtual disks might be left behind on the SaaS Connector/Hybrid Extender due to environmental issues. As a result, the following errors might occur in the VMware vCenter:

  • VMware might not process the command to release the virtual machines' disk from the SaaS Connector or Hybrid Extender VM.

  • The VM requires disk consolidation, but consolidation fails.

Solution

For the steps to resolve the error, see the KB article.

You can manually test if disks can be HotAdded to the SaaS connector or Hybrid Extender VM. For more details, see KB article.

No Valid Bifrost is Available Error

Backup or recovery fails with the “no valid Bifrost is available” error.

Cause

All the SaaS Connectors in the Connector Group are inoperable due to misconfiguration, manual deletion, or other potential reasons.

Solution

Follow these steps to resolve the error:

  1. Remove the inoperable SaaS Connector from the Connector Group. For details, see Create Connector Groups.

  2. Add the healthy SaaS Connectors to the Connector Group. For details, see Manage Connector Groups.

Unable to Pick a SaaS Connector Error

Backup or recovery fails with the “Unable to pick a SaaS Connector for recovering VM to VMC source”.

Cause

There is more than one ESXi cluster in the VMC on AWS SDDC (software-defined data center), but you have not created SaaS Connector groups for the ESXi cluster.

Solution

Create SaaS Connector Groups for each ESXi cluster that needs to be protected. For details, see Create SaaS Connector Groups.