Reinstall the dedicated server

Reinstallation wipes disks and redeploys a clean operating system. On a HolyCloud dedicated server, the operation is launched from the client area (panel) — plan your backups first.

Prerequisites

• HolyCloud client area access with rights on the server
• Full backup: data, databases, configs (/etc, crontabs, SSL keys)
• List of services to restore (web, mail, VPN)
• Backup IPMI/iLO access if the network fails after install
• Maintenance window communicated to users

Before clicking « Reinstall »

Checklist:

☐ Export SQL databases (mysqldump, pg_dump)
☐ Archive /var/www and /home
☐ Copy /etc/nginx, /etc/apache2, custom systemd units
☐ Lower DNS TTL if IP changes (rare)
☐ Document custom partitions (if you changed the layout)

Quick command from the server (if still accessible):

tar czvf /root/backup-etc-$(date +%F).tar.gz /etc

Transfer the archive off the server (scp, rsync, object storage).

Start reinstallation in the panel

1. Log in to https://manager.holycloud.fr (or URL on your contract).
2. Dedicated servers → select the machine.
3. Installation / Reinstall tab.
4. Choose:

- Distribution (Debian, Ubuntu, Rocky, Proxmox, etc. per catalog)

- Language / keyboard if offered

- Partitioning: automatic recommended unless specific LVM/ZFS need

1. Set root password or attach an SSH key if available.
2. Confirm total wipe warning.
3. Follow the progress bar — typically 15–45 minutes.

During the operation, the server is unreachable. Do not reboot manually via IPMI unless support instructs you.

After reinstallation

SSH access

ssh root@IP_PUBLIQUE

Change the password if auto-generated:

passwd

Initial update

apt update && apt full-upgrade -y
# or dnf upgrade depending on OS

Firewall and hardening

apt install -y ufw
ufw allow 22/tcp
ufw allow 80,443/tcp
ufw enable

Data restore

rsync -avz backup@serveur-backup:/var/www/ /var/www/
mysql < dump.sql
systemctl restart nginx php8.3-fpm mariadb

IP and reverse DNS

The main IP is usually kept. Verify in the panel:

• PTR record (mail reverse DNS)
• Failover IPs reattached if you had any

Special cases

Failure or stuck install

• Install blocked > 1 h: support ticket with server ID and panel screenshot
• No ping after completion: cabling (rare), IPMI console, panel VLAN
• Password refused: panel or IPMI KVM reset

Best practices

• Document installed OS version (cat /etc/os-release).
• Reapply HolyCloud guides (anti-DDoS, monitoring) after restore.
• Automate backups before the next reinstall.

Need help?

Support can relaunch an install, mount a custom ISO (eligible offers), or verify failover IP routing after reinstall.