Skip to main content

Replace a server or relocate a component

Choose the procedure​

Replace a scanner by installing a new node and then retiring the old one. The interface has no dedicated command that moves a scanner together with its data. Moving Core and its database requires a compatible backup and the restore procedure in Restore a backup. Installing an empty Core does not transfer projects or results.

Replace a scanner server​

  1. Record the old node's modules, version, Core address and settings. Schedule maintenance and preserve necessary data and backups.
  2. Prepare a new server without DerScanner. Install the required scanner set using Core, SAST, DAST and SCA on separate servers and connect it to the existing Core.
  3. Check the new node's role and operation with test tasks. For SAST, check concurrency settings using Multiple SAST agents and concurrent tasks.
  4. During maintenance, pause submission of new scans to DerScanner and let the old node’s running tasks finish. Stop is not a graceful drain mode: scans running on the module may be interrupted.
  5. Retire the old node using Stop or remove components and servers. Keep its data until the replacement has been confirmed to work.

Relocate Builder​

Under Settings → Optional components, remove the previous Builder after reading its removal plan. Select the new server and install/connect Builder using A separate Builder for SAST. Two Builders cannot be registered concurrently for one installation. This procedure does not transfer old build directories.

If the previous Builder server is permanently lost, an administrator can first inspect the plan and then explicitly forget the association on the main server:

dcp module remove builder --server SERVER_ID --forget --dry-run
dcp module remove builder --server SERVER_ID --forget --yes

Replace SERVER_ID with the old server's DCP list identifier. This removes the Builder association in DerScanner without contacting the lost server: its files and service remain there. Use this only for permanent loss, not a temporary SSH failure.

Recovery​

While the old installation is intact, stop the retirement procedure if the new node fails and restore the previous working arrangement. If the old node has already been removed, recover data from a compatible backup. If deleting a Builder record fails, repeat the operation after DerScanner becomes reachable; do not attempt to bypass the existing record with another installation.