Use this when the installed operating system cannot take the current package and the agent has to move, as in Install Mikiri WAF Updates. Install the new server from Getting started. Do not copy a package built for the old distribution onto the new one.
One license key belongs to one installed Filter. Using it on two Filters at the same time violates the EULA. Remove the Filter package from the old server before the new Filter starts with that key.
The key is the cluster. After the old Filter is removed, the new Filter with the same key receives the settings already stored for that cluster through API. Confirm the key first, as described in License verification.
Filter settings, request and response rules, the block list, MLC settings behavioral models are stored for the cluster and are not files you copy between servers. PostgreSQL for that cluster stays with API. If the API server is the one being replaced, move the database with the API, using the layout in Fault-tolerant operation of API when you need a second copy while you switch.
On the new Filter, before DNS changes:
curl -i http://%WAF SERVER%/mikiri-waf-test
The answer is 403 the event is on the attacks page in WMC. If it is not, follow A test request is not blocked. Then place the site again with Inline protection or Traffic copy. Keep waf_host_dm on until the attacks page shows no mass false blocks.