Backups, snapshots and restoration
A snapshot captures a disk state for rollback. A backup keeps a copy according to a schedule and retention period. File versions and trash are separate mechanisms as well.
What depends on your service
VPS BASIC and PRO
Daily “Daily 7j” option
7 days
VDS
Included daily backup
To be confirmed in your offer
Web hosting
Included daily off-platform backup
4 weeks
Collaborative Suite
Included daily backup
7 days
Dedicated servers and Housing
According to the option or contract
According to the agreed scope
BASIC VPS plans have one manual snapshot and PRO plans have ten. Check your service’s quota before creating a new snapshot. A snapshot must not be treated as an off-platform backup.
Before an operation
Identify the files, databases, configurations and keys needed for recovery. For a running database, prepare a consistent copy or an application-level export. A disk image alone does not guarantee consistency for every application.
Keep an independent copy of essential data and test recovery. Check the date and status of the latest backup; enabling a schedule does not prove that a first backup has completed.
Restore
In VMmanager or Plesk, open the section available for your service, choose the restore point and check what will be replaced before confirming. A restoration can overwrite data created since that point.
For a file in the collaborative Suite, start with versions or trash. Full recovery from UP-NETWORK backups goes through support. For a Managed VDS, also prepare the operation with the team.
If the restoration action is not available or database consistency is at stake, open a ticket. Specify the service, date of the desired restore point and data to recover.
Updated on 3 October 2026. References: VPS, VDS, web hosting, Suite.