How to backup NSX - logo

One of the components of modern and agile environments is Software Defined Network (SDN). Imagine that your Software Defined Data Center (SDDC) dies and you as Administrator of that environment have to recover it to state before crash.

So you as an Admin have a task to make sure that whole SDDC stack including NSX can be recovered after a failure or issue. Besides relying on High Availability provided by hypervisor and/or storage you must be 100% sure that you can recover NSX to state before crash. Today I will guide you through simple yet effective process of configuring NSX and its backup.

NSX backup strategy

As I mentioned above NSX is most likely be part of your SDDC platform which is fast, agile and there are many changes. In order to keep up to constant changes NSX should be backed up as often as possible. From my experience working with Clients who already use NSX in SDDC and IoT environments, NSX backup is as important as any other components.

NSX backup should be done with conjunction with vCenter Server backups and vCenter Server database backups.

Example backup schedule:

  • vCenter Server is backed up on daily basis
  • vCenter Server Database is backed up on daily basis (Full SQL backup) and transaction logs are backed up every hour
  • NSX Manager configuration is backed up every hour

From example above we clearly see that all critical components of environment are backup up at same time. Why do we do it that way? Answer is very simple – if we face issue with more than one component we will be able to recover full SDDC stack to state before crash. From architectural point of view we use terms Recovery Point Objective (RPO) and Recovery Time Objective (RTO). If you don’t know this terms take a look on my Colleague post who described it in details: RPO, RTO, WRT, MTD…WTH?!

How to backup NSX?

One and only supported way to backup NSX is to export whole configuration to FTP or SFTP server. This export consist all settings you configured in NSX – may it be Controllers, Edges, DLRs or firewall rules. All settings are stored in NSX Manager database and in case something must be restored or redeployed it can be done if you have NSX Manager config backup.

  1. Login to NSX Manager appliance.
    How to backup NSX - 1
  2. Click on Backup & Restore.
    How to backup NSX - 2
  3. Click on Change button in FTP Server Settings.
    How to backup NSX - 3
  4. We must provide following information:
    1. IP/Hostname
    2. Transfer Protocol
    3. User name
    4. Password
    5. Backup Directory
    6. Filename Prefix
    7. Pass Phrase

    How to backup NSX - 4

  5. Once all information is provided click Ok.
  6. Click on Scheduling to schedule NSX Manager backups.
    How to backup NSX - 5
  7. Once all settings are configured after few hours you will see that schedule is working.
    How to backup NSX - 6

Summary

As you see from operational point of view configuration of NSX takes few moments. From architectural point of view it is worth to consider how and when do we take NSX backups. I hope you will start to backup NSX now and in case you have some questions feel free to ask them in comments or sent me message.

How to backup NSX?
5 (100%) 5 votes
Wojciech Marusiak
Social Media

Wojciech Marusiak

Senior Solutions Cloud Architect at Consort CT
I am innovative and experienced VMware and Windows Server Engineer with over 10 years in the IT industry specializing in VMware virtualization and Microsoft Server environment.

My experience and skills have been proven by leading vendor certifications like VMware Certified Implementation Expert 6 – Data Center Virtualization, VMware Certified Advanced Professional 6 – Data Center Virtualization Design, VMware Certified Professional 6 - Data Center Virtualization, VMware Certified Professional 6 - Network Virtualization, AWS Certified Solutions Architect - Associate, ITIL V3, VMware vExpert 2014 - 2017 and VMware vExpert NSX 2017 Award.

My blog wojcieh.net - was voted #43 in Top vBlog 2017 contest!
Wojciech Marusiak
Social Media

Latest posts by Wojciech Marusiak (see all)