Deleting a server

Before you delete a server

Deleting a server removes it from CICDoo and tears down every instance running on it. Projects that use the server are not left pointing at nothing: for each one you choose whether it moves to another server or is deleted.

• The production database on the server is destroyed, whichever choice you make. Moving keeps the project, not its data. Take a backup first if you need the data, see Backups and restore.
• To move projects, you need at least one other server in the workspace. Add it first if needed, see Adding a server.
• Workspace members need the "Delete servers" permission. Moving a project also needs permission to change that project's settings, deleting one needs the "Delete projects" permission, and the "Back up now" button needs backup permission on the production instance.
• The server cannot be deleted while jobs other than teardowns are running on it, such as a backup.

Deleting a server

1. On the Servers page, click "Actions" on the server card.
2. Click "Delete Server". The window shows "Checking what is on this server..." while it loads.
3. Read the list. Under "These projects use this server. Choose, for each one, whether it moves to another server or is deleted.", each project shows which stages use this server and its instances here. A "Production here" badge marks projects whose production instance runs on this server. If no project uses the server, the window says "No projects use this server."
4. For each project, choose one option:
   • Move to: pick the destination in "Choose a server". This is selected by default wherever moving is possible, and the destination is preselected when there is only one other server.
   • Delete project: deletes the whole project. The window lists what else goes with it under "Also deleted, on other servers:" and, for a high availability setup, its app nodes.
5. For each project marked "Production here", check the backup line that appears once you have chosen. It shows when the last production backup was taken, or "No production backup found". Click "Back up now" if you want a fresh one first (see "Backing up before you delete" below).
6. Tick "I understand the production database on this server is destroyed. Moving keeps the project, not its data." for each of those projects.
7. Read the red summary, which spells out how many projects move and where, how many are deleted, how many instances are torn down, and which production instances must be redeployed on their new server.
8. In the confirmation box, type the server name exactly as shown in red in the line above it.
9. Click "Delete server". The button stays disabled until every project has a choice, every production acknowledgement is ticked and the name matches.

Backing up before you delete

1. In the delete window, click "Back up now" on the project's backup line.
2. A message says "Backup started. Delete the server once it has finished." The window now shows that jobs are still running, and the delete stays locked.
3. Close the window with Cancel and wait for the backup to finish. You can follow it on the Queue page, see Deployments and the job queue.
4. Start again from "Delete Server". The backup line now shows the new backup.

What happens after you confirm

• Moved projects: every stage that used this server now points at the destination server. Staging and development instances on this server are torn down and removed; create them again on the new server when you need them. The production instance record is kept and repointed, with auto-restart turned off, and it is not started on the new server automatically. Redeploy it there, then restore your data from a backup if you need it.
• Deleted projects: the whole project is deleted, including its instances on other servers and any high availability app nodes.
• The server: the card shows a "Deleting" badge and the note "Tearing down containers. The server is removed when this finishes." The server disappears once its teardown jobs have finished. If a teardown never completes, the server is removed anyway after about half an hour.

If nothing needs tearing down, the server is removed right away.

Deleting a server that is offline

If the server has not reported to CICDoo for about an hour, or never has, the delete window says so at the top: nothing on it can be backed up or torn down, so the delete only moves and removes records. In that case:

• No production acknowledgement or backup line is shown, because there is nothing CICDoo can reach.
• Instances on the server are removed from the platform, but their containers and data stay on the machine. Clean up or wipe the machine yourself if you still have access to it.
• The server is removed immediately after you confirm.

If the delete is refused

The window or a message tells you what is missing:

• "Jobs are still running on this server, such as a backup. Wait for them to finish before deleting it." Wait for the job on the Queue page, then try again.
• "Add another server to move projects." There is no other server to move to. Add one, or choose "Delete project".
• "You cannot change this project's servers." or "You cannot delete this project." You lack the project permission for that option. Ask the workspace owner, see Member permissions and resource access.

Related: Server actions: deploy, logs and charts, Backups and restore, Restarting, stopping and removing an instance, High availability with app nodes.

If you get stuck, open a support ticket from the Tickets page or the chat widget.