About this plugin
Keep a safe copy.
Revaulta is a WordPress backup and restore plugin developed by Adburbs Digital Agency. It brings backup creation, package verification, local downloads, uploads and recovery into one administration interface, with clear progress and explicit confirmation before restoration.
Create a recovery point before updating a theme, changing plugins or making substantial content changes. Choose the backup scope and follow its progress. Revaulta generates a unique name automatically; use the optional custom name when you want your own label.
When you need an earlier version of supported site content, select a local package or upload a Revaulta archive from your computer, review the checks and confirm the restoration.
Backup the content you need
- Full content backup: combine the site’s prefixed database tables with supported plugins, themes and uploaded media.
- Database backup: save supported WordPress tables and their records in a portable package.
- Files backup: save supported plugin, theme and uploads directories without exporting the database.
- Recognizable backups: automatic unique names, optional custom labels, creation date, scope, size and integrity status.
- Independent copies: download a backup and store a separate copy outside the hosting account.
php, database credentials, caches, symbolic links, host drop-ins, custom wp-content directories and the running Revaulta plugin are excluded. Full content backup refers to the supported content and database scope, rather than a disk image of the entire server.
Verify before restoring
Revaulta verifies package structure, member paths, declared sizes and SHA-256 hashes. Every created backup is verified before being marked complete. Uploaded packages remain pending until their integrity check finishes.
These checks detect missing or changed package data; they do not certify the archive’s author or establish that all application features will work after restoration.
Before applying an incoming package, Revaulta creates a full verified recovery backup of the destination. Supported database records are prepared in staged InnoDB tables. Content is restored in bounded pieces, and database tables are switched after the content phase succeeds.
The currently authenticated destination administrator and session metadata are preserved, along with destination site addresses. Source active plugins and the theme are restored after compatibility checks; Revaulta remains active.
During restoration Revaulta temporarily stores an isolated active-plugin list and uses its shipped recovery code to prevent theme startup, so subsequent requests can reach the recovery engine without creating executable bootstrap files. The public site is placed in maintenance while changes are applied. After successful completion the owned maintenance marker and private recovery descriptor are removed, while the recovery package is retained.
Follow each operation
The administration interface shows real progress, current operation messages, backup status and recent activity. Jobs save their completed steps to private local storage. Pause a running operation and resume it when ready.
If the browser is closed, further steps stop; reopening the administration page lets you resume from saved progress. No autonomous background worker is installed. Restoration cannot be cancelled once destination content writes have begun.
Private local storage
Backups are stored outside the public web document root. Package downloads require an authorized WordPress administrator session and nonce. No cloud account, external storage subscription or remote backup service is required.
Packages contain private website data and are not encrypted; protect downloaded copies and the hosting account that holds them.
Beta release and compatibility
The administration interface follows the current WordPress user language, with English fallback. org and WordPress language updates. This directory package does not bundle translated PO/MO files; available language coverage depends on approved community translations.
This is a beta release; test backup and restoration on an isolated copy before relying on it for a live site. Supported environments require a single-site installation and supported InnoDB schemas. Clean-target migration supports different domains, subdirectories and table prefixes.
Multisite, scheduled backups, cloud storage and central management are not included in this release.
Requirements: PHP ZIP, InnoDB tables, writable WordPress/content roots, database staging permissions and sufficient private disk capacity. Backups must be stored outside the web document root. php if the default external sibling directory is unsuitable.
Content covers plugins, themes and uploads. WordPress core, configuration, symlinks, caches, custom wp-content directories and the running Revaulta plugin are excluded. Restoration retains extra destination files.
Multisite and autonomous scheduled workers are unsupported. An open administrator browser drives jobs; saved progress can be resumed after reopening the page.
Database restores create missing source plugin tables and stage source schemas independently of target column order. Additional destination tables remain intact. URL/path values, serialized/JSON strings, role keys and user capabilities are mapped to the target.
Unsupported table structures and invalid transformations are rejected before activation. Live backups are not transactional snapshots. File and database replacement are not one atomic transaction.
A failed partial restore can leave maintenance active; a verified recovery package is retained. Packages contain private site data and are not encrypted.
Source code
js. These files are served as written; no npm, webpack, minification or JavaScript build step is required. php, is included in this package.
No third-party JavaScript library is bundled.
pot file is the translation template. WordPress loads directory language packs automatically. json mapping preserves historical operation messages; it is not a replacement for WordPress language packs.
Private backup storage is intentionally separate from public WordPress files because archives contain database records and other private site data. Revaulta does not generate or install PHP into mu-plugins, and does not modify its own plugin files. Updates should be installed when no restoration is running or awaiting recovery.