How to troubleshoot cloud forest recovery issues

Overview

This article describes common issues observed during Forest Recovery operations in cloud environments and provides guidance on how to resolve them.

Backup and recovery failures

• Timeouts: May occur when the number of Guardian job workers is insufficient for large environments. Increase the maximum worker count (default: 64 > recommended: 120) under Service Settings > Performance. Learn more: Job Execution Settings.
• Insufficient Disk Space: Backup jobs require at least 30 GB of free space per domain controller. Verify available capacity before running backups.
• Cloud Region Deployment Failures: Some Azure regions (for example, East US) may have temporary resource quota limitations. Switch to an alternate region (e.g., East US 2 or West US 2) if deployment fails.

Connectivity and DNS issues

• DNS Lookup Failures: Ensure recovered DCs can resolve both internal and external names. Update conditional forwarders if required.
• vCPU Quotas: Azure subscriptions have regional limits for virtual CPUs. Distribute recovery sites across multiple regions or request a quota increase.
• Authentication Errors: Verify that recovery credentials have sufficient rights and that WinRM is enabled on the target servers.

Best practices

1. Maintain separate storage locations for backups to prevent data conflicts.
2. Monitor Cayosoft Guardian job logs for “The operation has timed out” and investigate network latency.
3. Regularly test recovery plans using isolated virtual networks.