ENTERPRISE

Back up your data and stop your old service

• Last updated: July 3, 2023

• Read time: 2 Minutes

Once you have set up your Kubernetes cluster and successfully installed Burp Suite Enterprise Edition, you are ready to prepare your old deployment for migration. To migrate safely:

1. Stop all scans on your old deployment.
2. Scale your existing Kubernetes environment down to zero replicas.
3. Create a new database instance.

Stopping your scans

If you attempt to migrate your deployment while scans are running then you risk losing scan data. To disable scanning, open the Agent Settings page by selecting Agents from the settings menu and then set the Enable scanning toggle to off.

Disabling scanning prevents Burp Suite Enterprise Edition from starting any new scans, but does not affect any scans that are currently in progress. At this point, you can either let any in-progress scans finish or cancel the scans manually.

To cancel all scans that are currently running:

• Select Scans to display a list of all current scans.
• Select Scanning from the Filter by menu to display a list of in-progress scans.
• Select the check box at the top of the list to select all running scans.
• Click Cancel from the toolbar at the bottom to cancel all selected scans.

Scaling your environment down

With all scans stopped, you can safely stop running your existing Kubernetes pods. The best way to do this is to scale all pods associated with your existing Burp Suite Enterprise Edition deployment down to zero replicas.

Scaling down to zero replicas means that your pods are no longer active. It also frees up your license, as Each Burp Suite Enterprise Edition license supports one concurrent deployment. However, all configuration and deployment information is preserved so that you can potentially scale the old environment back up if you need to.

There are various tools you can use to manage Kubernetes pods and replicas. If you do not have a preferred management platform, you can scale down all pods in your Burp Suite Enterprise Edition namespace using the following command:

kubectl scale deploy -n <namespace> --replicas=0 --all

Creating a new database instance

Finally, clone your existing database. The safest way to do this is to take a database snapshot and then use that snapshot to create a new instance of your database. You can then point your Kubernetes deployment at this new database instance when you configure the application.

This process means that you can migrate all your data to your new deployment without having to change or delete configuration on your existing database.