BlogVault is a backup and recovery service for WordPress. Its useful distinction is the combination of backups stored away from your hosting account, a separate management dashboard, test restores, staging and migration. The buying decision is whether those controls give you a recovery route that your current arrangement lacks.
This guide is based on official public documentation checked on 13 October 2026. We have not installed BlogVault, timed a backup or performed a restore. Provider descriptions establish documented features; they do not prove that a particular site’s backup is complete or that its recovery will succeed.
Who should consider it?
- A WordPress publisher who wants a recovery copy outside the hosting account and can work within the selected backup interval and retention.
- An owner managing important updates who needs a temporary test copy and an understandable way to review a restore or deployment.
- A store operator prepared to choose the appropriate WooCommerce backup features and test how current order data is preserved.
- A small team that can assign responsibility for monitoring backups, controlling access and checking recovery.
Consider another arrangement if you require your own S3 bucket as the primary backup destination, a permanent staging site, a guaranteed round-the-clock support response, or protection for an entire hosting account rather than one WordPress installation. A backup service also does not replace software maintenance, secure access or an incident-response plan.
What the backup covers, and what to check
BlogVault’s backup feature documentation describes WordPress core, plugins, themes, uploaded media and database tables, including plugin-created tables. After the initial full copy, its incremental process transfers changes. The provider says assembly, encryption and storage happen on its servers, while your site still checks and sends changed data. We have not measured the resulting hosting load.
Review coverage rather than assuming “whole site” means every service you use. Your business mailbox, domain registration, DNS account and documents kept elsewhere need their own recovery arrangements. A functioning WordPress copy cannot recover an inaccessible registrar account or a separate email inbox.
There are also configurable exclusions. BlogVault documents skipping folders from backup sync; that workflow does not support excluding an individual file. Record any exclusions and check whether they contain something you would need after a failure.
Its non-WordPress folder instructions describe adding folders to sync, but another WordPress installation is treated as a separate site. Do not assume that adding the parent folder protects every website in a shared hosting account.
Choose frequency, history and size together
The public plan comparison lists the following limits. These are plan descriptions checked on the date above, not a guarantee of the options in an older subscription.
| Plan | Scheduled backup | Backup history | Website size |
|---|---|---|---|
| Personal | Every 24 hours | 30 days | Up to 20 GB |
| Business | Every 12 hours | 90 days | Up to 50 GB |
| WooCommerce | Hourly, customisable; real-time backup feature | 365 days | Up to 100 GB |
The backup feature table explicitly associates real-time backup with WooCommerce, not Personal or Business. Confirm the required data coverage and current account settings if your site takes orders; a daily backup should not be interpreted as preserving every intervening transaction.
Frequency determines the gap between recovery points. Retention determines how far back you can look when damage is discovered late. Site size determines whether the plan covers the installation. These are separate decisions: a long history does not compensate for a recovery interval that would lose important new work.
For example, an occasional brochure-site edit may be practical to repeat manually. Reconstructing registrations or orders from a busy day is a different problem. Choose around the information you could realistically rebuild, then verify the actual backup schedule and completed tasks.
Managed storage and ownership of an extra copy
BlogVault’s storage description says backups are encrypted in transit and at rest, with nine copies across two providers in EU data centres. Primary storage is managed by BlogVault and included with the service; it is not a customer-selected S3 bucket. These are provider statements, not an independent security audit.
Access to the BlogVault account therefore matters separately from WordPress access. Use a distinct strong password, protect the account’s recovery email and limit who can initiate recovery operations. Keep the owner able to access backups when the person who usually maintains the site is unavailable.
Managed storage is different from exporting a snapshot. BlogVault documents downloading selected backup components, and its help centre also describes exports to Dropbox and Google Drive. The product page uses broader language against customer-owned storage, so confirm which export options are currently available in your account. Do not infer automatic scheduled backup to your own bucket from an export guide.
An independent downloaded copy is only useful if it contains the required files and database, is stored securely and can be restored. Check it before cancelling the service or changing who manages the account.
Recovery when WordPress will not load
The restore feature page describes an Emergency Connector using FTP and database credentials when WordPress cannot run. This is a different route from relying on the WordPress plugin to execute. It is relevant when a broken theme, plugin or installation prevents normal administration.
That still requires an accessible destination and suitable connection details. A backup cannot recreate a cancelled hosting account by pressing a restore button. Keep a secure record of how the authorised operator reaches the host and database; test the recovery arrangement before an outage exposes a missing permission.
BlogVault also documents test restores and selective recovery. A full rollback can replace legitimate work created after the chosen backup; a partial rollback still overwrites the selected files or tables. Read our BlogVault selective restore guide for the scope decision, dependency checks and verification steps.
Staging is temporary, and a merge needs review
The staging feature page describes a copy hosted by BlogVault, on its subdomain, with password protection, search indexing protection, mail blocking and HTTPS. It lists a one-day lifetime on Personal, 30 days on Business and six months on WooCommerce.
Those limits influence the work you can finish. A one-day copy can suit a prepared update test; a multi-person redesign may need more time. Since the copy uses different infrastructure from live, its behaviour is not proof of your host’s performance or every integration’s production configuration.
Deploying back to live is another decision. New posts, form entries or orders may have arrived since the copy was made. Our BlogVault staging and safe merge guide explains how to plan tests and review the file and table scope without treating “merge” as automatic record reconciliation.
Migration does not move every business service
BlogVault’s migration instructions describe selecting a backup, destination URL, connection details and WordPress root directory. They also support selective migration and using a destination server IP before existing DNS points there.
Treat this as a website transfer workflow. Plan the DNS change, email records, certificates and any activity created during the move separately. Check the destination before redirecting visitors, keep the old recovery point and avoid replacing another site’s folder or database. Our WordPress migration checklist covers the wider move.
Support and the owner’s operating role
The current support page lists usual responses of one to three hours on weekdays and 12–24 hours on weekends and holidays, with weekday working hours in India. These are published expectations, not a response guarantee. Do not build an emergency plan around immediate 24/7 human assistance.
Assign someone to notice failed or overdue backups, confirm the last usable recovery point and decide when a restore is appropriate. Record the backup chosen, the affected scope and the checks performed afterwards. Support can help investigate a failure; it cannot decide which of your newer records are acceptable to lose.
Compare the arrangement, then verify before committing
Your host may already provide useful backups and staging. Compare their retention, independent accessibility, restore scope and responsibilities before paying for duplication. A plugin workflow with separately controlled storage or a manual backup may suit an owner who can manage and test recovery. See hosting backups versus an independent backup for that comparison.
- Confirm one completed backup includes the required files and database.
- Check the actual installation size, schedule, retention and exclusions.
- Test a recovery copy using a representative article, media file and important workflow.
- Confirm who can access the service and the host during an outage.
- Review the total invoice, billing period, tax and renewal terms. An advertised discount is not a confirmed renewal price.
Shortlist BlogVault when its managed offsite storage and recovery controls fill a real gap. Choose another route when primary storage under your own control, a permanent staging environment or a different support arrangement is essential. The strongest choice is the one whose recovery process your site has actually passed.
Recorded plan evidence
These separate plan records retain their own observation dates. They are not a current checkout quote or a renewal guarantee; check the billing country, tax and final invoice before buying.
Security & backups · View 1 plan snapshot USD price reference · Checked 2026-10-07
Security & backups · US reference.
1 plan snapshot
| Plan | Initial commitment | Renewal | Advertised rate | Fit & reasons to avoid | Tax & source |
|---|---|---|---|---|---|
 BlogVault · Personal · 1 site, current annual promotionGlobal USD offer | US$49.5012 months term Exact annual amount published | Not confirmedFuture renewal amount and invoice duration not confirmed | US$49.50annual subscription; current 50% promotion | One modest WordPress site needing daily offsite backups and stated retention. Skip when: You need real-time backups, more than 20 GB or staging beyond one day. Read BlogVault guide → | Tax not confirmedChecked 2026-10-07 · recheck dueOfficial price source ↗Limits & who should skip it1 site; 20 GB; daily backups; 30-day retention; 1-day staging; offsite storage and migration; real-time backup on higher tiers. Observed context: Public USD reference; billing country unconfirmed. Country: not confirmed. Current annual promotion US$49.50 against displayed US$99 regular reference. Not verified as first-year-only; renewal unknown. |
How to read these prices
Compare the job, the full initial commitment and the renewal billing basis. Each company appears once. Open Change plan to view every recorded plan and term. Showing a plan does not change your two-plan comparison. The initial view uses a recorded non-trial option where available; it is not a ranking. Feature marks are tied to the documented plan, market, limits and billing conditions. Their check dates are independent from price rechecks. Europe is not one price or tax jurisdiction; select your actual billing country at checkout. These are researched public offers, not checkout quotes or hands-on tests. Currency values are not conversions. Listing order does not depend on commission.
Plans & costs
Compare the full commitment and the work each plan includes. Recorded observations are not a current checkout quote.
Security & backups
USD · US / global observations
BlogVault · Personal · 1 site, current annual promotion
- Initial term & commitment
- Initial term amountUS$49.5012 months termannual subscription; current 50% promotion
- Renewal
Check local tax at checkout
Price observed 2026-10-07 · Recheck due
Plan details & sources
One modest WordPress site needing daily offsite backups and stated retention.
1 site; 20 GB; daily backups; 30-day retention; 1-day staging; offsite storage and migration; real-time backup on higher tiers.
Choose another option if: You need real-time backups, more than 20 GB or staging beyond one day.
Public USD reference; billing country unconfirmed · Check local tax at checkout
Exact annual amount published
Renewal: Future renewal amount and invoice duration not confirmed
Check local tax at checkout
Prices checked 2026-10-07 · recheck dueOfficial price source ↗- Backups & restore: Included. Daily offsite backups; 30-day retention
- Backups & restore, Plan allowance, Tradeoff ↗Features checked 2026-10-07
Observed 2026-10-07 · Recheck due
Official price evidence ↗Recorded prices can change. Check eligibility, taxes and the current full bill with the provider. Different currencies and services are shown separately.
Sources and verification
Editorial review 2026-10-13. Source check dates are recorded separately. Notes describe what each source supports and its limits.
View sources
- BlogVault: backup featuresChecked Core/plugin/theme/media/database coverage, incremental work, offloaded assembly/storage and explicit plan association for real-time backup.
Limits: Provider statements, not an independent performance test. Marketing whole-site scope must be read alongside documented folder exclusions and per-site setup. - BlogVault: folder exclusionsChecked Folders can be skipped from backup sync; individual-file exclusion is not supported in the documented flow.
Limits: Does not establish any actual site exclusions or configuration. - BlogVault: non-WordPress foldersChecked Additional folders can be synced; a folder containing another WordPress installation is handled as a separate site.
Limits: Not evidence that one subscription protects every site in a shared hosting account. - BlogVault: plan comparisonChecked Scheduled frequency, retention and website-size limits for Personal, Business and WooCommerce.
Limits: No account or checkout inspected. Promotional price, tax and renewal are not asserted by this candidate. Text extraction lists unavailable items in some cards; feature table provides the explicit real-time distinction. - BlogVault: data security and storageChecked Provider-managed primary storage, encryption in transit/at rest, EU location, nine copies/two providers and lack of customer-chosen S3 primary storage.
Limits: Provider statements, not a security audit or automatic customer GDPR compliance. Broad Dropbox wording is qualified by separate snapshot-export documentation. - BlogVault: download a backupChecked Snapshot download with selectable files/database components.
Limits: No export tested. A download must be checked for completeness and restorability. - BlogVault: Dropbox backup exportChecked Official help documents selecting a backup and uploading it to a connected Dropbox account.
Limits: Current product storage page uses broader contrary wording. Confirm availability in the account; do not imply automatic primary destination selection. - BlogVault: Google Drive backup exportChecked Official help documents linking Google Drive and uploading a selected backup snapshot.
Limits: Account entitlement and live controls unverified. Does not establish continuous scheduled backup to customer storage. - BlogVault: restores and Emergency ConnectorChecked Emergency Connector uses FTP/database credentials when WordPress cannot run; test and selective restore are documented.
Limits: No restore time, success guarantee or account-independent recovery guarantee. An accessible destination and valid authorised connection details remain necessary. - BlogVault: staging environmentChecked Externally hosted copy, BlogVault subdomain, privacy/mail/HTTPS defaults and 1-day/30-day/6-month staging lifetimes.
Limits: Temporary provider-hosted copy is not infrastructure parity or permanent staging; account settings and other integrations need verification. - BlogVault: migrate to a new host with the same domainChecked Backup/destination/WordPress directory selection, server connection requirements, selective migration and server-IP option.
Limits: Does not move domain registration or business mailboxes or prove a specific migration succeeds; no zero-downtime guarantee repeated. - BlogVault: support availabilityChecked Usual weekday and weekend response times, India-based weekday office hours and prioritisation of urgent failures.
Limits: Published expectations are not a contractual response guarantee; no support request made.