All NSX Edge configurations (logical routers and edge services gateways) are backed up as part of NSX Manager data backup.

Taking individual NSX Edge backups is not supported.

If you have an intact NSX Manager configuration, you can recreate an inaccessible or failed Edge appliance VM by redeploying the NSX Edge. To redeploy an NSX Edge, select the NSX Edge, and click Actions > Redeploy. See "Redeploy NSX Edge" in the NSX Administration Guide.

Caution: After restoring an NSX Manager backup, you might need to take additional action to ensure correct operation of NSX Edge appliances.
  • Edge appliances created after last backup are not removed during restore. You must delete the VM manually.
  • Edge appliances deleted after the last backup are not restored unless redeployed.
  • If both the configured and current locations of an NSX Edge appliance saved in the backup no longer exist when the backup is restored, operations such as redeploy, migrate, enable or disable HA will fail. You must edit the appliance configuration and provide a valid location information. Use PUT /api/4.0/edges/{edgeId}/appliances to edit the appliance location configuration (resourcePoolId, datastoreId, hostId and vmFolderId as necessary). See "Working With NSX Edge Appliance Configuration" in the NSX API Guide.
If any of the following changes have occurred since the last NSX Manager backup, the restored NSX Manager configuration and the configuration present on the NSX Edge appliance will differ. You must Force Sync the NSX Edge to revert these changes on the appliance and ensure correct operation of the NSX Edge. See "Force Sync NSX Edge with NSX Manager" in the NSX Administration Guide.
  • Changes made via Distributed Firewall for preRules for NSX Edge firewall.
  • Changes in grouping objects membership.
If any of the following changes have occurred since the last NSX Manager backup, the restored NSX Manager configuration and the configuration present on the NSX Edge appliance will differ. You must Redeploy the NSX Edge to revert these changes on the appliance and ensure correct operation of the NSX Edge. See "Redeploy NSX Edge" in the NSX Administration Guide.
  • Changes in Edge appliance settings:
    • HA enabled or disabled
    • appliance moved from deployed to undeployed state
    • appliance moved from undeployed to deployed state
    • resource reservation settings have been changed
  • Changes in Edge appliance vNic settings:
    • add, remove, or disconnect vNic
    • port groups
    • trunk ports
    • fence parameters
    • shaping policy
    Attention: After upgrading to NSX 6.4.4 or 6.4.5, the default MTU value for newly added trunk interfaces on the edge is incorrectly set to 1500. This issue also occurs after you do a fresh installation of 6.4.4 or 6.4.5. The issue is fixed in 6.4.6. However, to resolve this issue in 6.4.4 or 6.4.5, you must manually change the default MTU value in all the trunk interfaces of the edge to 1600. For more information, see the VMware knowledge base article at https://kb.vmware.com/s/article/74878.