xneelo or TailoredHosting for checking WordPress media backups

A visible media library can hide two problems

On Monday, an association imports a magazine’s archives and illustrations for a new series into WordPress. On Tuesday, the homepage, galleries and first pages display correctly. The team prepares the domain change and receives confirmation that the database has been backed up. It still needs to demonstrate that a private copy can recover every expected file at the chosen point and fit in the planned space, even during extraction.

The problem appears if Tuesday’s database knows about new attachments while the file copy dates from Sunday. The restored page may retain the image’s title, alternative text and dimensions. It may even display a thumbnail served by the old site’s CDN. When that URL disappears or the cache expires, the fault surfaces on the page and in download links. A restoration must work without this access to the origin.

The comparison covers xneelo Web Hosting Basic in South Africa and TailoredHosting WP Starter DirectAdmin in Kenya. At xneelo, the public procedure lets you choose a file or directory and a new destination. At TailoredHosting, the daily SQL backup point can be newer than the weekly file point. In both cases, validation concerns the same imported batch, dates actually available and peak space required for an isolated restoration.

Plan price and available space during testing

xneelo lists Basic at ZAR 99 including VAT per month, with 15 GB SSD, three databases and one SFTP account. Twelve monthly payments at the displayed rate total ZAR 1,188 including VAT before domain and any overage. The billing guide advertises a 3% discount for some annual payments. Check the cycle available with your payment method. The provider charges ZAR 20 per extra GB according to its documentation. Its example of an account at 19 GB totals ZAR 179 for Basic. Before temporarily leaving a large ZIP on the account, ask when usage is measured and what amount would appear on the invoice.

xneelo’s policy also sets 200,000 entries per account and 50,000 per directory on shared hosting. The scope includes web files, directories and messages, for example. This policy states that exceeding limits can cause files or folders to be excluded from the backup system. It treats database storage separately, with a 5 GB limit per database. For Basic, therefore record disk usage, entry count and database slots already occupied before reserving a destination.

TailoredHosting lists WP Starter DirectAdmin at KES 3,360 excluding tax for the first twelve months, then KES 4,200 excluding tax per year, with no setup fee. With 16% VAT if applicable to the invoice, the calculation gives KES 3,897.60 then KES 4,872 including VAT. The plan advertises 40 GB and 250,000 inodes per account, including files, directories and emails. The product table states one DirectAdmin account and no built-in staging. Advertised free migration covers an account under 10 GB. Ask which size is counted before relying on it to move the photo library.

Deadlines matter if switchover spans several weeks. xneelo’s terms require one calendar month’s notice to cancel. TailoredHosting states renewal for the same term, a reminder at least 14 days before expiry in its terms, at least 30 days’ written notice of a renewal-price change and possible suspension after a five-day grace period for nonpayment. Record cancellation and renewal dates in the schedule together with how long the old host must remain reachable. Prices were recorded on November 10, 2026 in their displayed currencies.

Freeze what the copy must recover

Prepare a list of expected media from source files and pages to migrate. Identify each attachment with a stable editorial marker, such as the report name and image number. An import may reassign WordPress identifiers. Therefore retain the link between the original identifier, destination identifier and relative path used after import. For a project also moving posts, choose examples from featured images, gallery blocks and direct download links.

In the imported WordPress site, identify the attached-file path and sizes described in metadata. Record at least the path, byte size, format, image dimensions and a SHA‑256 hash for checked files. Include the large original if WordPress created a scaled version, a recent thumbnail, an editorial crop and an old file still in use. For variants generated during import, establish the reference after validating their appearance in the imported copy.

First compare this reference with the source batch. An expected original already missing from the imported site reveals an import anomaly that no later backup can repair. Conversely, a gallery may have changed file URLs while displaying the correct image. Document this change before freezing the destination path and hash. If some images are stored in an object service, inventory them separately with their own recovery method. An export of the WordPress directory alone may omit them.

Immediately after import acceptance testing, record a common marker for SQL, the media archive and manifest. If possible, reserve a short window without new uploads or regeneration. State the time zone and time of the last validated media item. A second export after uploads resume may include files unknown to the first SQL or miss new links. Keep each set in a separate folder outside the account and associate artifact hashes with it.

Choose the two backup points to restore

xneelo states daily backups of the user directory and MySQL databases, retained for up to two weeks. In Restore Backup, choose the file date, select the media directory and request a new directory. The panel also allows restoring to the original location with overwrite. Choose the separate destination and verify that it remains inaccessible to the public before placing files there. For SQL, select a new database if the quota of three allows. If all three slots are occupied, plan an isolated external database and check how to retrieve the desired point.

For WP Starter DirectAdmin, TailoredHosting states a weekly off-site account backup and daily off-site database backup. The listing advertises 14-day retention for both. The full weekly copy includes files, databases and email present on the platform at capture time. The daily point covers databases alone. Sunday and Tuesday in the example may therefore correspond to two different states. Ask in the ticket for each date, included directories and the possibility of receiving files or restoring them to another destination. The policy says a database can be restored alone. It specifies that restoration overwrites data in the chosen scope and allows requesting a partial scope. Wait for destination confirmation before any operation.

A common date displayed in a panel leaves capture times and ongoing uploads unresolved. Check files in the restored destination against the manifest and match SQL to the chosen batch. If the host’s point lacks an original or crop, restart from the pair exported after import. If that also lacks it, retrieve the original from its source, recreate the required variant in the isolated copy and produce a new manifest after checking.

Open media while blocking fallback to the source

Prepare an isolated copy with its own database, credentials and private access. Block email sending and jobs liable to trigger synchronization. Serve pages and media from the test destination. For a few representative pages, check the responding domain in browser requests. A block preview or HTTP 200 response from an external URL does not prove the file was recovered. Open originals and the sizes actually requested by the browser from the restored destination.

Check size, dimensions and hash on the recovered file. Two archives can show the same file count and names while containing an older version. Identical size does not distinguish two different images. In PowerShell, Get-FileHash with the SHA256 algorithm calculates a file’s hash. On Linux, use sha256sum on the restored file. Compare the value with the reference manifest. For a modest photo library, compare hashes throughout the entire tree. For a large corpus, compare all paths and sizes, check hashes for the imported batch and record the exact scope of checking on other files.

Also test a gallery on mobile, an attachment present before import and an item added at the very end. Compare thumbnail cropping and open downloads offered by the page. Regenerating sizes can make a page usable again. Where a manual crop or proprietary transformation mattered to publication, compare the result with the visual reference before accepting it and retain a record of regenerated variants.

Measure peak bytes and entries

Record total account occupancy immediately after import and before uploading the archive. Separate media, other site files, caches, messages and SQL according to the host counter’s scope. Then measure the compressed archive, its extracted tree and expected temporary files. Add only items present simultaneously. If the archive remains on an external disk and only the file stream reaches the copy, it is not part of the account’s peak.

On xneelo, take an example with 10 GiB already occupied, a 2 GiB ZIP, 4 GiB extracted and 1 GiB temporary. The peak reaches 17 GiB, two above Basic’s 15 under the billing guide’s binary convention. Moving the ZIP brings the example to exactly 15 GiB. This leaves no room for unexpected files. With an external copy, the account retains its initial 10 GiB. The scenario measures the difference from the included allowance. It predicts neither a write prohibition nor an invoice amount for a brief peak.

On WP Starter DirectAdmin, imagine 170,000 entries already in place, 85,000 in the extracted tree and 5,000 temporary. The total reaches 260,000 even before counting the archive if it is on the account. This overage is possible with 25 GB used out of the advertised 40. Moving a one-entry ZIP changes the result little. Moving the entire test tree outside the account frees entries. On xneelo, add a measurement of the largest directory because one folder may exceed 50,000 entries while the total remains below 200,000.

A local tree measurement helps explain the peak. The panel counter remains the account reference, particularly for email and how the provider counts folders. Record values before transfer, during extraction and after deleting only working files. Set a separate reserve in bytes and entries for unexpected tasks, then compare the peak plus that reserve with applicable limits. If the copy fits only by deleting media still needed, change the test destination.

Replay the fault before deciding

The offline exercise supplies a small fictional-media batch, archive points and a manifest. The program recreates each copy in a temporary folder, loads references from the fictional catalog and opens recovered files. The first test pairs a recent database with the weekly archive. The gallery file and its thumbnail are missing. The second uses an archive containing all paths and preserving sizes. The replaced thumbnail is detected by its hash.

The third test extracts the pair created after import. All manifest files become readable again and their hashes match. The program measures their bytes and extracted files and folders. Separate budgets using the hypothetical volumes stated in the examples exceed the disk allowance, account entry count or per-directory limit. The simulation repeats with a destination outside the account. Measurements of the small batch are real, while hosting-scale values are model inputs.

Record the recovered point, affected media item, path, measurements before and at peak, destination and decision in your acceptance test. If a single crop is missing, the page depending on it still needs validation. If a file has the right name but wrong hash, associate it with the correct version before rerunning the check. On a public site, also check pages and request origins in WordPress, a step outside the exercise.

• Extract the ZIP into an empty folder. With Python 3.10 or later, run python recette.py.
• Compare the thumbnail’s path, dimensions, byte count and hash. Check results for the weekly, substituted and intact copies.
• Enter your figures into the budgets. If the folder, inodes or disk reach the limit, move the entire test copy before rerunning.

Choose according to where the copy fits

xneelo Basic is suitable if the batch fits with headroom within the disk allowance and below both entry thresholds, and the team wants to request a restored directory itself. For a compact photo library, the panel reduces dependency on a ticket. Before choosing this route, check that you can use a separate database and retrieve a point after the last upload. The one-calendar-month notice period enters the coexistence-period calculation.

TailoredHosting WP Starter DirectAdmin offers a larger disk allowance and a 250,000-inode threshold. It is suitable if the team can keep an independent post-import export and then mount a separate copy when the account cannot hold the duplicate. The daily database point may help recover a recent change. For files, request the actual weekly point and its scope, and plan a fallback if the ticket cannot deliver a usable copy without overwrite.

If a burst of small files or thumbnail generation saturates the chosen hosting, test outside the account. The old site must remain available for the planned validation period, but the test must work without it. On both offers, the independent archive taken after import is valuable primarily for its ability to restore the complete batch. The plan price is a selection factor once recovery conditions are verified.

Authorize switchover with dated evidence

Ask the editorial owner to approve tested pages, crops and downloads. Ask the technical owner to date the SQL and media pair, attach the manifest result and show both headroom measurements on the actual destination. Keep the provider backup-point or independent-archive identifier and private-copy path so the same configuration can be retested.

If new media arrived since testing, record the delta at freeze time and prioritize checking files it adds or replaces. If the point’s date is unknown, a used file remains unreadable or the peak leaves no reserve, postpone switchover. Preserve the active site’s data during correction and keep a recent export within the team’s reach.

After the change, revisit a short selection of uncached pages and check media URLs, featured images and download links. Keep the validated manifest with the recovery batch. The next incident can then be compared against a dated, checked list, helping identify which files to reimport and which backup point to choose.

• Record the last validated media item and SQL and archive dates.
• Compare paths and hashes on the isolated destination.
• Measure peak disk usage, entry count and, at xneelo, the largest directory.
• Decide and record the result before changing the domain.

Further reading

• Read the xneelo profile
• Read the TailoredHosting Kenya profile
• Compare WordPress backups
• Download the media restoration test procedure (ZIP)