Following up from a post I did a while back regarding this specific error within NSX:
“Server failed to respond. HTTP request time out.”
This issue might also cause edges to fail to deploy or other random issues related to NSX. Be sure to check your backups!
This has been an ongoing issue as NSX does not manage the backups or backup location. It only takes and restores backups. There was an issue reading a large number of files(over 100 to be exact) and loading the count of files in the directory where NSX was pointed to backup.
I’m excited to announce that this has been fixed in NSX 6.4.4 release on December 13th 2018! NSX Backups now only create 2 files in the backup directory, a backup file and a checksum file. The backup file now has version info added as a suffix to the end of the file. These files are now sorted by matching prefix specified in backup settings and version suffix, additionally when there are over 100 backups; NSX will only load the latest/newest 100!! This is referenced specially under this page
“Fixed Issue 2018917: High count of NSX backup files causes unpredictable behavior”
The new error message when the 100 backup count is exceeded is:
“Too many backup files in backup folder, reading latest 100 backups. Please move out backup files and keep limited number of files in the backup folder.”
Another bug down 🙂