The NSX Backup & Restore page shows "No Backup present" in the Backup History pane
search cancel

The NSX Backup & Restore page shows "No Backup present" in the Backup History pane

book

Article ID: 425521

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • When viewing the Backup & Restore page in the NSX UI, the Backup History pane shows "No Backup present"
  • Scheduled backups may have successfully completed.
  • Messages similar to the following are seen in the /var/log/syslog file on the NSX manager nodes:

    2026-01-06T11:37:31.224Z  WARN http-nio-127.0.0.1-7440-exec-8 BackupRestoreSFTPServiceImpl 5227 SYSTEM [nsx@6876 comp="nsx-manager" level="WARNING" reqId="d0dd8fe9-####-####-####-a2522db538ca" subcomp="manager" username="[email protected]"] invalid timestamp in backup file.
    java.text.ParseException: Unparseable date: "2025-10-09.tar.gz""
            at java.text.DateFormat.parse(Unknown Source) ~[?:?]

    Note: The date/file noted after "Unparseable date" will be unique to each environment.

Environment

VMware NSX

Cause

The directory structure under the NSX backup folder on the SFTP backup server should look like the following:

cluster-node-backups
inventory_summary

Under each of these folders will be sub-folders named similar to the following:

4.2.3.2.0.25077149-IPv4-49992d42-####-####-####-7a37dc9c3f35-192.168.0.6

Under these folders there should be directories/files names similar to the following:

backup-2026-01-12T00_00_00UTC - under the cluster-node backups parent folder
inventory-2026-01-14T17_28_26UTC.json - under the inventory_summary parent folder

When this issue is present, files named similar to the following will be present:

backup-2025-10-09.tar.gz - under the cluster-node-backups parent folder
inventory-2025-10-09.tar.gz - under the inventory_summary parent folder

The file names are parsed to get the date/time of the backup. These unexpected files are not named correctly and are missing the time part of the file name.

 

Resolution

This is a known issue affecting VMware NSX. There is currently no resolution. 

To workaround this issue, remove the files that are not named correctly.