Skip to main content
Site backups protect your files and database before updates, migrations, staging pushes, restores, and unexpected changes. When a backup fails, the cause is usually one of these areas: server disk space, database export, remote storage access, backup schedule/settings, or old backup jobs that need support review. Read this guide to troubleshoot both local backups and remote backups in ORIV before opening a support ticket.

​
What This Guide Covers

This guide helps when:
  • A local site backup fails.
  • A remote site backup fails.
  • A manual backup fails.
  • A scheduled backup does not run.
  • Backup emails report failures even though backups look disabled.
  • A backup fails with Database backup failed or MySQL database backup failed.
  • A remote backup fails even though Google Drive, S3, R2, Backblaze, DigitalOcean Spaces, pCloud, or another provider has free space.
  • Old backups are not deleted as expected.
  • Incremental backups look missing or confusing.
  • Global or bulk backup settings do not match the site-level settings.
This guide focuses on backup creation failures. If your backup was created successfully but the restore failed, follow the restore troubleshooting guide or contact ORIV Support with the restore error.

​
Before You Retry

Before running the backup again, collect the details that explain where the backup stopped.
  1. Open the failed backup entry.
  2. Copy the exact error message.
  3. Check whether the backup was Local or Remote.
  4. Check whether it was Manual or Scheduled.
  5. Note the failed backup date and time with your timezone.
  6. Check the server’s available disk space.
  7. Check whether you recently changed the backup schedule, storage provider, bucket, folder, retention, or exclude paths.
  8. Check whether the same remote provider works on another site.

​
Step 1: Find the Failed Backup Entry

Start from the backup history so you can identify what failed.
  1. Log in to your ORIV Dashboard.
  2. Open the affected Site.
  3. Go to Backups.
  4. Open Previous Backups or the backup history area.
  5. Find the failed backup.
  6. Review the backup type, destination, trigger, date, and error message.
Common errors include:
  • Database backup failed
  • MySQL database backup failed
  • Not enough storage for backup
  • Failed to fetch folder id
  • Failed to add storage provider
  • Missing database name or database password errors
  • S3-compatible upload, bucket, endpoint, or permission errors
If the error changes after retrying, save both the original error and the new error. A provider error followed by a database error can mean the backup is failing at more than one stage.

​
Step 2: Understand Local vs Remote Backup Failures

Local and remote backups can fail for different reasons, but both may still depend on server storage and database export. A remote backup does not mean ORIV can skip local temporary files. ORIV must first create backup files on the server, then upload them to the remote provider.

​
Step 3: Check Server Temporary Disk Space

Many remote backup issues are actually server storage issues. Before ORIV uploads a backup to Google Drive, S3-compatible storage, Cloudflare R2, Backblaze, DigitalOcean Spaces, pCloud, or another provider, the server needs temporary space to create:
  • Database export files
  • File archive files
  • Compressed backup packages
  • Backup metadata
  • Temporary upload files
So a remote backup can fail even when your remote provider has plenty of free space. For example: To check storage:
  1. Open the affected Server in ORIV.
  2. Review disk/storage usage.
  3. Check whether old backups, large uploads, cache files, logs, or temporary files are using space.
  4. Review backup retention settings.
  5. Free up space only when you know the files are safe to remove.
Do not delete unknown files or directories blindly. If you are not sure what is safe, contact ORIV Support or a qualified server administrator before cleanup.

​
Step 4: Review Local Backup Settings and Retention

Local backups use server disk space. If retention is not working as expected, old backups can fill the server and cause new backups to fail.
  1. Open the affected Site.
  2. Go to Backups → Backup Settings.
  3. Review the Local Backup section.
  4. Check whether local backup is enabled.
  5. Check the schedule.
  6. Check the retention or automatic delete setting.
  7. Check whether old backups are still listed in Previous Backups.
Local backup storage issues may happen when:
  • Old backups are not removed by retention rules.
  • Backup retention was changed but old files remain.
  • Local backup is disabled in the dashboard but a stale job still runs.
  • Orphaned backup files remain on the server.
  • A legacy backup job still creates files after settings were changed.
  • Large folders are included because exclude paths were not applied.
If local backup is disabled but disk usage keeps growing, contact ORIV Support. Support may need to check backup jobs, cron entries, and backup directories safely.

​
Step 5: Review Remote Backup Provider Settings

Remote backups can fail because the provider connection, folder, bucket, endpoint, or permissions changed.
  1. Open the affected Site.
  2. Go to Backups → Backup Settings.
  3. Open the Remote Backup section.
  4. Confirm the selected provider.
  5. Confirm the destination folder, bucket, or path.
  6. Confirm the provider connection is still active.
  7. Confirm the provider account has enough storage quota.
  8. Confirm the provider credentials have read and write access.
  9. Save the settings, then run a manual backup test.
Remote provider issues commonly come from:
  • Expired or revoked tokens
  • Changed folder permissions
  • Deleted or renamed destination folders
  • Wrong bucket name
  • Wrong region or endpoint URL
  • Read-only credentials
  • Missing write permission
  • Provider account quota limits
  • Provider-side API outage
  • IP restrictions on the storage token

​
Step 6: Fix Failed to Fetch Folder ID

Failed to fetch folder id usually means ORIV could not access or identify the configured remote folder. This can happen when:
  • The remote folder was deleted, renamed, or moved.
  • The connected account no longer has access to the folder.
  • The provider authorization expired.
  • The selected folder path is no longer valid.
  • The provider API returned a temporary error.
To troubleshoot:
  1. Open the remote backup settings.
  2. Reconnect the remote provider if needed.
  3. Re-select the destination folder or bucket.
  4. Confirm the connected account can open and write to that folder.
  5. Save the settings.
  6. Run a manual backup.
If the next failure changes from Failed to fetch folder id to Database backup failed, continue with the database section below. The backup may have moved past the provider check and then failed during database export.

​
Step 7: Check S3-Compatible Storage Providers

S3-compatible storage includes providers such as Cloudflare R2, Backblaze, DigitalOcean Spaces, Wasabi, Hetzner Object Storage, OVH Object Storage, and other providers that use S3-style credentials. If ORIV cannot add or use an S3-compatible provider, check:
  • Access key
  • Secret key
  • Bucket name
  • Region
  • Endpoint URL
  • Token permissions
  • Bucket permissions
  • Read/write access
  • IP restrictions
  • Provider account quota
  • Provider status page
For errors like Failed to add storage provider, common causes include:
  • The token has limited or read-only permission.
  • The token is restricted to an IP address that does not match the request path.
  • The endpoint URL was copied incorrectly.
  • The bucket name is wrong.
  • The bucket is in a different region.
  • The bucket does not allow write access.
  • The credentials belong to another provider account.
Recommended checks:
  1. Copy the endpoint URL directly from the provider dashboard.
  2. Confirm the bucket name exactly, including spelling and case.
  3. Make sure the token has read and write access.
  4. Remove unnecessary token IP restrictions while testing if your security policy allows it.
  5. Confirm the provider account has available storage.
  6. Try adding the provider again.
Do not send secret keys, access keys, passwords, or private tokens in plain text unless ORIV Support asks you to use a secure method.

​
Step 8: Test a Manual Backup

Manual backup testing helps separate a one-time schedule issue from an active backup failure.
  1. Open the affected Site.
  2. Go to Backups.
  3. Choose the same backup type that failed: Local or Remote.
  4. Start a manual backup.
  5. Wait for the process to complete.
  6. Open the failed entry if it fails again.
  7. Save the exact error message.
Use the result this way:

​
Step 9: Troubleshoot Database Backup Errors

A site backup usually includes both files and database data. If the database export fails, the whole backup may fail. Common database-related errors include:
  • Database backup failed
  • MySQL database backup failed
  • Missing database name
  • Missing or null database password
  • Database connection error
  • MySQL export error
  • Empty database tables
  • Database exists but cannot be exported

​
If You See Database Backup Failed

  1. Retry the backup once after a short wait.
  2. Confirm the site is online.
  3. Check whether the site was recently migrated, cloned, restored, or edited.
  4. Check whether database credentials were changed.
  5. Contact ORIV Support if the error repeats.
Sometimes a database backup failure works on retry. If it fails repeatedly, Support may need to review the database configuration and export logs.

​
If the Database Name Is Missing

A missing database name usually needs support review. Contact ORIV Support and include the site name, server name, exact error, and whether the site was recently migrated, restored, or cloned.

​
If the Database Password Is Empty or Null

A null or missing database password can stop the backup process from finding or exporting the database. Do not manually change database credentials unless you understand the effect on the site. Contact ORIV Support for a safe review.

​
If the Database Has No Tables

If a database is empty, the database backup may fail or be skipped depending on the site state. This can happen when:
  • WordPress installation did not complete.
  • A new site has no database tables yet.
  • A migration or restore did not finish.
  • The site is connected to a different database than expected.
Complete the WordPress installation or contact Support if the database should already contain tables.

​
Step 10: Check Schedule, Global Settings, and Bulk Backup Updates

Backup settings may exist at more than one level. If scheduled backups do not match what you configured globally or in bulk, check the site-level settings.
  1. Open the affected Site.
  2. Go to Backups → Backup Settings.
  3. Review the site-level schedule.
  4. Review the selected provider or local destination.
  5. Review retention settings.
  6. Review file backup exclude paths.
  7. Compare the site-level settings with the global or bulk settings you expected.
  8. Save the settings.
  9. Run a manual backup test.
Check carefully when:
  • Exclude paths were not copied from global settings.
  • The wrong bucket or provider is selected after a bulk update.
  • Scheduled backups stopped after changing settings.
  • No backup notification was received.
  • A site still uses an old storage provider.
  • The dashboard says backups are inactive but remote backup emails continue.
If the settings look correct but the behavior is wrong, contact ORIV Support. This may need engineering review.

​
Step 11: Check Incremental Backup Entries

Incremental backups may appear under a parent full backup. If the child entries are collapsed, it can look like backups are missing.
  1. Open the site’s Previous Backups.
  2. Find the latest full backup.
  3. Expand the full backup entry if an expand option is available.
  4. Review the incremental backup entries under it.
  5. Check the dates and times.
Contact Support if:
  • The latest full backup is older than expected.
  • Incremental backups are not listed.
  • Backups are going to the wrong bucket or provider.
  • The schedule does not match your settings.
  • Manual backups work but scheduled backups do not.

​
Step 12: Compare Failed Sites With Working Sites

If the same remote storage credentials work on one site but fail on another, compare the affected site with a working site. Check:
  • Server free disk space
  • Site size
  • Database status
  • Backup type
  • Selected provider
  • Bucket, folder, endpoint, and region
  • Backup schedule
  • Retention settings
  • Exclude paths
  • Whether the site was recently migrated, cloned, or restored
  • Whether the sites are on the same server
This helps identify whether the issue is provider-wide, server-specific, or site-specific.

​
Step 13: Avoid Risky Manual Cleanup

If storage is full, cleanup may be needed, but removing the wrong files can break a site or remove the only usable backup. Do not blindly delete:
  • WordPress uploads
  • Site directories
  • Database files
  • Backup metadata
  • Server configuration files
  • Unknown folders
  • Files owned by system services
Avoid recursive delete commands unless you fully understand the exact path and impact. ORIV provides full root access and the root password where applicable. For better security, ORIV recommends SSH key-based login instead of password login. Use root access carefully and avoid risky production changes unless you understand the impact. If you are unsure, contact ORIV Support or a qualified server administrator before deleting backup-related files.

​
Troubleshooting by Error or Symptom

​
What ORIV Support Can Check

ORIV Support can help review:
  • ORIV backup settings
  • Site-level backup configuration
  • Backup history and visible backup errors
  • Server storage usage
  • Backup logs and events
  • Local backup retention behavior
  • Remote storage configuration guidance
  • Stale or old backup jobs where support access is needed
  • Cron-related backup issues where support access is needed
  • Database configuration issues
  • Missing database name or database password issues
  • Repeated database export failures
  • Orphaned backup files or backup cleanup issues
  • Confirmed backup bugs that need engineering review

​
What ORIV Support Cannot Guarantee

ORIV cannot guarantee recovery if no successful backup exists. Remote storage providers can also have their own issues, including:
  • API outages
  • Quota limits
  • Expired tokens
  • Revoked credentials
  • Bucket permission problems
  • Endpoint or region changes
  • Folder access changes
  • Account restrictions
If the issue is inside the remote provider account, you may need to review that provider’s dashboard or contact the provider directly.

​
What to Send ORIV Support

To help Support investigate faster, include:
  • Site name
  • Server name
  • Whether the failed backup is Local or Remote
  • Whether it is Manual or Scheduled
  • Remote provider name, if used
  • Exact error message
  • Failed backup date and time
  • Your timezone
  • Screenshot of the failed backup
  • Screenshot of backup settings
  • Whether a manual backup also fails
  • Whether the same provider works on other sites
  • Recent changes to backup settings, schedule, provider, bucket, folder, or exclude paths
  • Server free disk space, if visible
  • Remote provider quota, if relevant
  • Whether the site was recently migrated, cloned, restored, or changed
  • Any database-related error text
Do not send secret keys, passwords, access keys, or private tokens in plain text unless Support asks you to use a secure method.

​
Prevention Tips

  • Keep enough free disk space on your server.
  • Do not rely only on remote storage quota.
  • Review backup retention settings regularly.
  • Use exclude paths for large cache, temporary, or generated folders when appropriate.
  • Test remote storage after changing credentials or tokens.
  • Run a manual backup after changing backup settings.
  • Check site-level settings after using global or bulk backup updates.
  • Keep provider tokens active and correctly permissioned.
  • Avoid read-only tokens for backup destinations.
  • Monitor backup emails and dashboard backup history.
  • Download critical backups before major cleanup.
  • Contact Support before deleting unknown backup files from the server.

​
FAQ

​
Why does a remote backup need local server storage?

ORIV must create the backup archive on your server before uploading it to the remote provider. If the server does not have enough temporary space, the remote backup can fail before upload.

​
My Google Drive or pCloud account has enough space. Why did the backup fail?

Remote quota is only one part of the process. The server also needs enough temporary disk space to create the database and file archives before upload.

​
Why did a database backup fail once and then work later?

A temporary MySQL, server load, or export issue can cause a one-time failure. If the same database error repeats, contact ORIV Support.

​
Why do I still receive remote backup failure emails after disabling remote backups?

There may be stale backup configuration, an old scheduled job, another site using the same provider, or a notification issue. Check site-level backup settings and contact Support if emails continue.

​
Why do the same S3 credentials work on one site but not another?

The affected site may have different settings, server storage, bucket, endpoint, schedule, database configuration, or provider assignment. Compare it with a working site.

​
Can ORIV clean up old backup files for me?

ORIV Support can help investigate backup-related storage usage, retention issues, orphaned backup files, and stale backup jobs. Risky cleanup should be handled by Support or a qualified server administrator.

​
Can ORIV recover my site if no successful backup exists?

ORIV cannot promise recovery if there is no successful backup available. Keep regular local and remote backups and confirm they are completing successfully.

​
Should I use root access to delete backup files manually?

Only use root access if you understand the impact. ORIV provides root access where applicable, but recommends SSH key-based login for security. If you are unsure, contact Support before deleting files.

​
Why do incremental backups look missing?

Incremental backups may be collapsed under a parent full backup. Expand the full backup entry and check whether incremental entries are listed underneath.