"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

Products

• VMware SDDC Manager
• VMware NSX

Issue/Introduction

• Post Upgrade of NSX to 4.2.0 or 4.2.1, NSX cannot enable Schedule Backup nor modify Backup Configurations. If the Backup Configuration was saved before the upgrade, then manual backup works on the same SFTP server details. The following error is experienced when attempting to edit the backup configuration:
  "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 code: 29111)" 

         

• The following error is seen in /var/log/proton/nsxapi.log

BackupAsyncStatus [BackupStatus [status=URI_NOT_FOUND, statusDetail=Specified uri '<path to tmpdir cluster backup file>' not found., remoteUri=<sftp remote uri path>, errorCode=null, startTime=1725568161583, endTime=1725568164220]; responseBody=null]

• Issue is only seen in NSX versions 4.2.0 or 4.2.1. Earlier versions of NSX can back up to the same SFTP server.

Verify the following items:

1. Backup directory path is valid.
2. SFTP server disk has enough available space for back-ups
3. Directory path length is not beyond 256-characters
4. For Windows SFTP servers, verify the Windows OS Version
5. For Windows SFTP Servers, ensure long path has been enabled: NSX-T backups are failing with error "either bad directory path or sftp server disk full"

Environment

VCF 5.2.x
NSX 4.2.0.x and 4.2.1.x
SFTP platform: OpenSSH on Windows

Cause

NSX Scheduled backup was created before NSX Upgrade. The original file attributes copied during the upgrade can cause Windows Server SFTP (any version) to be rejected with "Bad message" error.

Resolution

The is a known issue that is fixed in version 4.2.2 and later.

If you cannot upgrade and a workaround is needed, please open a case with Broadcom Support for assistance.

See Creating and managing Broadcom support cases for details on opening a case.