Emergency Migration
If your source server no longer boots or SSH access is no longer possible, you can rescue the data via rescue mode and transfer it to a new server.
Emergency scenario: This guide applies to servers that are no longer reachable — e.g. due to hardware failure blocking all access.
What is your situation?
| Situation | Approach |
|---|---|
| Linux server no longer boots | Start Linux rescue mode → mount partition → rsync to target |
| Windows server no longer boots | Start Windows rescue mode → robocopy to network share |
| SSH/RDP blocked by misconfiguration | Start rescue mode → repair config or back up data |
| Hardware failure, server won't start at all | Contact support — hardware replacement and migration. |
Linux: Back up data via rescue mode
Start the rescue system, mount the partition, and transfer data via rsync to the target server.
1.Start the Linux Rescue Mode in the PowerPanel. → Starting rescue mode
2.Connect via SSH to the rescue environment
3.Identify your main partition and mount it:
Terminal
lsblk
mount /dev/sda3 /mnt
Transfer the data via rsync to the target server:
Terminal
rsync -avz --progress /mnt/ root@TARGET_SERVER_IP:/
Detailed guide for backing up data in rescue mode: → Backing up data in Linux rescue mode
Windows: Back up data via rescue mode
Start Windows rescue mode and copy data via robocopy to a network share.
1.Start the Windows Rescue Mode in the PowerPanel (password: exactly 8 characters). → Starting rescue mode
2.Connect via VNC on port 5900
3.Open the Command Prompt and initialise the network:
PowerShell
wpeinit
Copy data to the target server:
PowerShell
robocopy "C:\inetpub" "\\TARGET_SERVER_IP\MigrationShare\inetpub" /E /R:2 /W:5
Detailed guide for backing up data in Windows rescue mode: → Backing up data in Windows rescue mode
After the data rescue
Set up the target server and bring it into production.
1.Reinstall all required services on the target server (web server, database, etc.)
2.Transfer configuration files and update paths and IP addresses as needed
3.Import database dumps if they were backed up separately
4.Test all applications before updating DNS records
5.Update DNS records to point to the target server's IP
Hardware failure?
If your server has a hardware defect or won't start at all, our support team is available via the PowerPanel.