VCF Brownfield Import fails with error "Failed to configure NSX Backup schedule for NSX Managers"
search cancel

VCF Brownfield Import fails with error "Failed to configure NSX Backup schedule for NSX Managers"

book

Article ID: 429010

calendar_today

Updated On:

Products

VMware SDDC Manager

Issue/Introduction

  • During brownfield import for VI Workload domain, "Install and Configure VLAN Backed NSX for Domain #####" fails on subtask "Configure NSX Backup Schedule".
  • This issue affects both Management domain NSX-T managers and VI workload NSX-T managers during the brownfield ingest of VI Workload.
  • SDDC UI shows the failure as below,

  • /var/log/vmware/vcf/domainmanager/domainmanager.log on SDDC Manager has error as below,

Caused by: com.vmware.vapi.std.errors.InvalidRequest: InvalidRequest (com.vmware.vapi.std.errors.invalid_request) => {
    messages = [],
    data = struct => {error_message=One of: 1. invalid directory path; 2. sftp server disk is full; 3. Check if the directory path length is beyond 256-character limit on Windows server, httpStatus=BAD_REQUEST, error_code=29111, module_name=backup-restore},
    errorType = INVALID_REQUEST

  • NSX-T manager UI backup will show SDDC server's default path. As below,

Environment

  • VMware Cloud Foundation 5.2.x
  • VMware NSX 4.2.0.x, 4.2.1.x

Cause

NSX backup configuration is not saved when backup is configured from SDDC UI because the original file attributes passed is not preserved on Windows Server SFTP (any version)

Resolution

This issue is resolved in the versions below:

Proceed with either of the below options to upgrade the environment:

  • Option A:
    • Perform an upgrade to VCF 5.2.2.

If upgrade is not an option and a workaround is needed, please open a case with Broadcom Support (Creating and managing Broadcom support cases) for assistance.

Additional Information

"One of: 1. invalid directory path; 2. sftp server disk is full; 3. Check if the directory path length is beyond 256-character limit on Windows server" error observed when modifying NSX Backup configuration