Was this page useful?

Backup and Storage

Purpose

This page records the backup and storage model for the Members Hub website.

The aim is to keep disaster recovery, file recovery, working copies, and document storage separate so that each part has a clear purpose.

Backup Strategy

1. Primary Disaster Recovery Backup

Primary backup is handled by Plesk Backup Manager.

Storage:

  • Local Plesk server storage: /var/lib/psa/dumps
  • Remote IONOS HiDrive FTPS storage: ftp.hidrive.ionos.com/WEBSYNC/VPSBACKUP

Backup file example:

  • backup_2604261557.tar

Recommended Plesk schedule:

  • Incremental backups enabled
  • Full backup weekly
  • Maximum full backups stored: 3
  • Store in both server storage and FTPS storage

Backup contents:

  • Configuration
  • Mail messages
  • User files
  • Databases

Recommended options:

  • Exclude log files
  • Do not use multivolume backups unless required by storage limits

Purpose:

  • Restore the server or website through Plesk
  • Main disaster recovery route

2. Plesk Local Storage

Location:

  • /var/lib/psa/dumps

Purpose:

  • Fast local restore through Plesk
  • Short-term convenience copy

Important:

This is not enough on its own because it is stored on the VPS. If the VPS is lost, this storage may be lost too.

3. Plesk Remote FTPS Storage

Location:

  • ftp.hidrive.ionos.com/WEBSYNC/VPSBACKUP

Purpose:

  • Off-server backup storage
  • Main disaster recovery protection

Important:

The FTPS path is not the same as the rsync path. Plesk uses the FTPS view of HiDrive storage.

Known working Plesk settings:

  • FTP server hostname: ftp.hidrive.ionos.com
  • Directory: /WEBSYNC/VPSBACKUP
  • FTP username: comradesclub
  • FTP password: stored only in Plesk
  • Passive mode: enabled
  • FTPS: enabled

4. Manual File-Level Rsync Backup

Script:

  • /var/www/vhosts/coulsdonclubmembers.info/scripts/backup_site_to_hidrive.v1.0.sh

Current status:

  • Available for manual use only
  • Not scheduled by cron

Purpose:

  • Quick file-level mirror of website files
  • Secondary recovery route for individual files

Important:

This is not the main disaster recovery backup. Plesk remote FTPS backup is the main backup route.

5. Codex Hub Live Copy

Script:

  • /var/www/vhosts/coulsdonclubmembers.info/scripts/export_localhost_sync_v1.0.sh

Local server copy:

  • /var/www/vhosts/coulsdonclubmembers.info/codex-hub

Schedule:

  • Every 30 minutes

Purpose:

  • Working copy of essential live site files
  • Comparison against localhost
  • Safe inspection by Codex

Important:

Codex Hub is not a disaster recovery backup. It is a working copy and comparison source.

6. ClubDocs Storage and Sync

Authoritative document storage:

  • IONOS HiDrive: /WEBSYNC/CLUBDOCS

Website mirror:

  • /var/www/vhosts/coulsdonclubmembers.info/httpdocs/user/data/clubdocs

Sync script:

  • /var/www/vhosts/coulsdonclubmembers.info/scripts/sync/pull_clubdocs_v1.0.sh

Schedule:

  • Hourly

Purpose:

  • Pull Club documents from IONOS into the website
  • Run the document link audit

Important:

IONOS ClubDocs storage is the source of truth for documents.

Current Cron Model

Plesk Backup Manager

Plesk manages its own backup schedule.

Cron checker:

0,15,30,45 * * * * /opt/psa/admin/sbin/backupmng

This checks for due Plesk backup tasks. It does not mean a full backup runs every 15 minutes.

Codex Hub Sync

Runs as root:

*/30 * * * * /var/www/vhosts/coulsdonclubmembers.info/scripts/export_localhost_sync_v1.0.sh

ClubDocs Sync

Runs as gallyvps:

0 * * * * /var/www/vhosts/coulsdonclubmembers.info/scripts/sync/pull_clubdocs_v1.0.sh

Custom HiDrive Rsync Backup

Not scheduled.

Available manually:

/var/www/vhosts/coulsdonclubmembers.info/scripts/backup_site_to_hidrive.v1.0.sh

Source of Truth Rules

  • Content pages: live server is the source of truth
  • Club documents: IONOS ClubDocs is the source of truth
  • Technical development: localhost is the development working copy
  • Disaster recovery: Plesk remote FTPS backup is the source of restore
  • Codex Hub: comparison copy, not disaster recovery

Recovery Notes

For full server or site recovery:

  1. Use Plesk Backup Manager.
  2. Restore from remote FTPS storage if local storage is unavailable.
  3. Use the latest successful Plesk backup unless a specific older restore point is needed.

For individual website files:

  1. Check the live site and Codex Hub.
  2. Check the manual rsync mirror if needed.
  3. Restore carefully and compare before overwriting.

For Club documents:

  1. Check IONOS ClubDocs.
  2. Re-run the ClubDocs sync.
  3. Run or review the document audit.

Password Handling

Passwords must not be stored in scripts, documentation pages, Codex notes, or local files.

The HiDrive FTPS password is stored only in Plesk remote storage settings.

Scripts use SSH keys where possible.