Moving to Another Server

99 vues Markdown

Moving WISECP to another server means taking a backup on the old one and restoring it on the new one. Everything travels together: files, database and uploads. The parts that need your attention are the licence, the cron job and the domain.

Opening the Screens

Both ends of the move are in the panel. Take the backup from Backup and Restore under Settings › Security. Restore it from the same screen on the new server, once WISECP is installed there.

What Moves and What Does Not

A full backup holds three parts, and the restore screen lets you choose which of them to bring back.

DatabaseClients, services, invoices, orders, tickets, settings. Everything the panel remembers.

FilesThe installation itself: core, modules, themes, configuration.

UploadsLogos, attachments, images and anything else uploaded through the panel.

Three things do not travel inside the archive and are handled separately. The licence is tied to the domain and the address it runs on. The cron job lives in the server's own scheduler. DNS decides when visitors start reaching the new machine.

Before You Start

The new server meets the requirementsSame list as a fresh installation. Check it before moving anything, not after.

Your licence can be movedThe licence is locked to a domain or an address. If either changes, arrange the new one in advance so the panel is not locked out on arrival.

A quiet windowOrders, payments and tickets that arrive on the old server after you take the backup are not in the archive.

Tasks

Move the Installation

On the old server, put the site into maintenance mode so nothing new arrives.
Take a full backup and download the archive.
Install WISECP on the new server and let it finish.
Upload the archive and restore it, choosing every part.
Add the cron job on the new server.
Sort out the licence for the new address if it changed.
Point DNS at the new server, then turn maintenance mode off.

Check the Move

Log in, open a client, open an invoice, and confirm an uploaded logo still appears. Then watch the automation screen for a minute to confirm scheduled tasks are running on the new machine.

Things to Watch

Restoring replaces everything, not only what is missing

A restore returns every table to the state it had in the archive. It is not a merge. Anything recorded on the target after the backup was taken is gone. That is why the move ends with DNS rather than starting with it.

The uploads part may already be inside the files part

When files and uploads were backed up together, uploads sit inside the files archive rather than in one of their own. The restore screen works this out and only offers the parts the archive really contains, so trust the options it shows rather than the list of what was selected at backup time.

Restore runs even when a safety backup could not be taken

If the backup system is off or its pre-check fails, the restore still goes ahead and records that no safety copy exists. It is a fact you will want to read afterwards, not a stop. Take your own copy first if going back matters.

One at a time

A restore will not start while a backup is running. While a restore is going, no other restore, deletion or download is accepted. A backup taken while files are being rewritten would carry half-old contents.

Cet article vous a-t-il été utile ?

Merci pour votre retour !

Besoin d'aide supplémentaire ?

Notre équipe d'assistance est disponible 24h/24 pour tout ce que vous ne trouvez pas ci-dessus.

Nous contacter Ouvrir un ticket