Oxahost or Nindohost for restoring WordPress on a restricted-access copy

Delegate recovery without granting production access

A small French-speaking organization wants to verify its latest WordPress backup after a maintenance error. The account manager retains hosting access. The acceptance tester receives the necessary files and a database export. They can write to a private destination provided it is separate from public WordPress. The expected result is a page whose text and media match the same restore point, followed by a reference change appearing only on the copy.

Distinguish three permissions: retrieving a copy from the host, reading the delivered files and SQL, and writing to the destination. The person importing data does not need control over account-wide backups, DNS or mailboxes. If the panel cannot delegate exactly the necessary rights, the holder performs extraction. They then transfer both elements through the team’s designated process.

Start with a private directory and empty database using destination-specific credentials. Automatic tasks, forms, webhooks and outgoing relays must remain disabled during the trial. Check protection with one unauthorized and one authorized request. A site accessible merely by knowing its URL remains public even with indexing disabled.

Define what a restore point must provide

WordPress relies on files and a database. Media, theme and plugins reside in files. Content, options and media references are in the database. For recovery after an update, also check code versions. Successfully imported SQL may reference missing files or a plugin version unable to interpret its data.

For each item, record the plan, instance, scope, time and time zone of the selected point. If files and database were captured separately, check consistency using recent media and the page using it. A hash verifies copying of the received bytes. It does not alone confirm consistency of a point or completeness of a backup.

Request a format the technician can review and import without returning to the production panel. Check the archive before transferring it. Exclude production credentials, unnecessary archives and personal data not needed for testing. Assign an identifier to the file/database pair. A missing file or inconsistent pair must stop the process before any staging write.

Oxahost WP Basic and the copy advertised in the plan

WP Basic advertises two WordPress instances, 10 GB SSD and 1 GB RAM, with a file manager, WP Clone and snapshots. These features make a same-account trial plausible if a slot remains free. Measure file, database and temporary-point space before starting the copy. Two advertised instances do not prove that the technician can have access restricted to one or that the copy is private when created.

The WordPress FAQ advertises daily snapshots retained off-site for 30 days and one-click restoration for all plans in this range. It does not detail separate media and SQL downloads, snapshot destination, number of WP Basic restore points or extraction permissions. Oxahost’s cPanel shared-hosting offering documents JetBackup, but its menus are not evidence for the WordPress product examined. The holder must obtain both exportable items or arrange extraction with support before delegating acceptance testing. General terms describe a generally weekly or monthly frequency and indicative retention of 30 to 90 days depending on the plan, without a restoration guarantee. Ask which points are actually accessible for WP Basic and check export rights.

The WordPress site advertises hosting in Tunis except when an external option is selected. Check backup location separately. Help and contact are available in French. The help center advertises continuous chat and technical channels. Confirm the channel and language for a particular intervention. Terms recommend customers retain their own backups and test recovery. A provider backup therefore does not remove the need to check delivered files.

Nindohost Go Site and tools documented in cPanel

Go Site advertises cPanel, WordPress Toolkit Deluxe, one site, 25 GB SSD, five email addresses and daily backup. Nindohost’s restoration guide describes JetBackup in cPanel. For files, it shows selecting a point and items to restore, then queueing them. For a database, it describes downloading a copy from the list. Check that these screens are present for the Go Site account. The guide does not set a retention period applicable to this WordPress plan.

Completed status indicates the task finished. It does not demonstrate that the destination was a copy. Before any file Restore action, identify the path and check whether active files are overwritten. The database guide allows downloading the item and preparing import through phpMyAdmin. Help describes creating a new database and MySQL import. If the account lacks the desired destination, request items from the holder or support and restore elsewhere. Terms require support-generated backups when a shared account exceeds 15 GB. If this clause applies to Go Site, allow intervention time. Keep archives on separate storage.

The plan advertises one site. Toolkit Deluxe access does not establish that a complete independent clone is permitted within this quota. A separate destination allows work to continue if the account does not permit it. Nindohost publishes French help and an English offer page. Telephone and tickets are advertised, with tickets continuously accessible under the terms. The WordPress FAQ states servers in Morocco without establishing the account’s data center or location of all copies.

Compare periods and the test destination’s cost

For Oxahost, the selected reference is the public thirty-six-month cycle displayed at 455.94 TND excluding VAT for WP Basic, equivalent to 12.665 TND excluding VAT per month. The card also displays three free months. Confirm how they affect the end date and next cycle. According to the billing page, at 19% VAT the indicative total is 542.569 TND rounded to the millime. If the 1 TND stamp duty applies, the example reaches 543.569 TND. Check the account currency and fees before selecting an amount.

Oxahost terms describe renewal for an equivalent term at the applicable rate, and billing advertises a renewal invoice fourteen days before expiry. The precise recurring amount does not follow from the displayed promotional equivalent. Check the renewal date and total, the domain included in the first year and its possible renewal price. Staging on another account or host increases the budget if the plan quota is reached.

Nindohost displays 79 MAD per month for Go Site. General terms present public prices excluding taxes. The card specifies neither the actual cycle offered nor the tax-inclusive total. Twelve times the displayed price gives a 948 MAD reference before taxes under this reading, subject to the offered price and cycle. This calculation is not an annual quote. Help describes an invoice generated fifteen days before expiry if the renewal option is enabled, followed by renewal subject to payment. Check the amount in the summary. This option generates the invoice. Help specifies that merely having a saved card does not trigger payment.

Give the technician items they can check

The holder prepares retrieval of files and SQL. They record the database name and check the associated application before export. The technician receives the items and a record describing point identifier, expected files, hashes and SQL format. Do not include production credentials, sending tokens or an entire account export if unnecessary. Check who may read it and how long it must remain available.

The staging account must permit writing to an assigned directory and database. Validate the destination by name, path and marker. Check database format, engine and import limits. If a file is too large for the interface, arrange an authorized method or ask the holder to handle this step. File permissions alone do not allow SQL import. Database permissions alone do not provide media and code.

Do not send the account’s master password to avoid a support request. If an action requires holder permissions, record the action and expected result. Have a hash and readable copy checked after transfer. A refusal due to a missing item must remain visible in the report. Postponing acceptance testing is preferable to completing the pair with an unchecked file from another date.

Replay stops before any write

The mockup provides a file archive and SQL archive from the same point, then two incompatible database variants. The script reads manifests, checks each item’s hash and actually executes SQL in in-memory SQLite. It then compares the stored database reference and media file. The destination name is checked before any work. Production or existing staging is refused to preserve trial reference items. In the folder extracted from the ZIP, run “python -X utf8 exercice.py” and compare the report with “attendu.json.”

Six stops are checked. The mockup refuses production, absent SQL, an altered hash, two different points, an inconsistent media reference and a file outside archive scope. In the inconsistent-media case, manifests nevertheless announce the same point. Database-content checks therefore complement manifest checks. None of the refusals leaves partial staging. Failure can be reported to the holder by identifying the item to retrieve again.

When the pair is correct, the script creates the media and a real SQLite staging database, then changes the fictitious address and checks integrity. It writes a reference title on the copy. A rollback starts again from the same pair in a second folder. The first trial and production reference file remain readable and unchanged during rebuilding. The test runs entirely offline and interprets only the supplied fictitious SQL. Its checks do not validate real panel permissions.

Check the WordPress copy before declaring it usable

At the real destination, record the correct URL, root and database name. Check that WordPress and plugins use these values. Replacing addresses in serialized settings requires a compatible tool and backup. Avoid automatically transferring the configuration file with its secrets. Prepare separate credentials and check that the technician cannot reach production through staging access.

Check the reference page, image with its actual URL and administration access. Check data at a known date, plugin status and ability to write a harmless change on the copy. At the same time, reread the public reference through normal access. If an old cache gives a misleading result, identify the layer and confirm values in a response that has not been reused. Test that the staging form sends no data to a real recipient.

Record evidence in a minimal report. State the chosen point, checked items, staging URL, permissions used and reference result. Separately note what the holder had to do. An automatic restoration finishing in the panel is insufficient by itself. Acceptance testing passes when page, media and write all correspond to the expected destination and the public state remains readable.

Decide whether to continue or rebuild staging

If an item or permission is missing, stop and request the precise expected export. If media and SQL do not match, request a consistent point. Inconsistency may also arise from an environment-dependent path. Check references, filename and storage before changing the pair. If you discover a production write, interrupt the trial and retain the log and affected data before considering correction.

To roll back staging, retain the failed trial while its log is needed. Reimport a verified point into a new authorized destination and repeat the same checks. Any public-site restoration follows a separate agreement and must account for content arriving after the selected point. This article uses no DNS settings and assumes no launch.

WP Basic is a candidate if the advertised copy and necessary exports are available through holder permissions. Go Site is a candidate if the team prefers a documented cPanel route and has an independent destination when quotas require it. The decisive criterion is the ability to deliver two reusable items and prove restoration remains confined to staging. A test-account cost or ticket delay forms part of this choice.

Further reading

• Read the Oxahost profile
• Read the Nindohost profile
• Compare WordPress backup tools
• Download the restricted-access restoration mockup (ZIP)