01:20 AM: The Wrong Version Overwrites the Website

An administrator uploads the wrong release, replaces old files, and the application changes the database. The website still opens, but its pages, data, and settings no longer belong to the same version.

The most dangerous response is repeated uploading and database editing. Each attempt can make the original state harder to recover.

01:25 AM: Choose the Date to Return To

The service page shows available offsite recovery dates.

NNS retains recent successful rolling backups and an earlier monthly recovery point. A failed backup never replaces a valid one, and customers see usable dates rather than internal archives.

First Choice: Restore Files and Database Data

If domains, PHP, rewrites, and site settings remain correct, the customer can restore only hosting files and databases.

This mode returns files and data to the selected point without replacing current site settings. It fits failed updates, deleted files, and damaged business data.

Second Choice: Return the Entire Website

If files, databases, and site configuration have all changed, Full Recovery can be selected.

It also restores required operational settings, domain relationships, FTP, database accounts, and states, bringing the website as close as possible to the saved condition.

01:28 AM: Current Data Is Not Overwritten Immediately

NNS first checks that the recovery point is complete.

If files are missing or validation fails, the task stops before the current website is cleared. A damaged backup never replaces readable current data.

01:30 AM: The Website Enters Brief Maintenance

Website access and database writes are paused during recovery.

This prevents uploads, visitor submissions, and background work from mixing new data with the restored state. Service resumes after recovery and validation.

01:40 AM: The Customer Sees a Task, Not a Black Box

The service page displays status and progress. Every task ends in success or failure instead of remaining “running” forever.

A useful error summary allows administrators to resolve the failed stage and restart the task.

Why Must Backup Data Leave the Current Node?

If backup and website data share the same failed disk, both may disappear when recovery is needed.

NNS stores recovery points independently. Even if the original node must be reinitialized, administrators can restore services with valid recovery points to a prepared node.

Pricing and Cooldown

The service page shows whether recovery can begin directly or requires payment. After confirmation or payment, the recovery task is created automatically.

Both recovery modes use the same recovery price displayed on the page. A one-hour cooldown prevents repeated website overwrites.

After Midnight, the Website Still Has a Way Back

NNS Offsite Backup and Recovery is not the sale of an archive. It is a validated path that pauses writes, shows progress, restores data, and returns the website to operation.

The important question is never whether a backup existed yesterday. It is whether the website can return to the correct point today.