Before becomes a place you can return to.
Keep a weekly whole-server backup rhythm, then create a deliberate restore point before an important change. FocalShift Ai keeps every captured state tied to the server it came from—and keeps the consequence of returning visible.
One repeats each week. One waits for your decision.
Recurring protection and a deliberate pre-change restore point solve different problems. The selected FocalShift Hardware server remains the scope for both.
Keep a whole-server rhythm moving.
When enabled, FocalShift maintains a rolling weekly backup set for the selected Hardware server. The current member experience describes automatic capture as non-interrupting.
Turning the setting on or off begins with the next backup cycle.
Not a menu of tiny undo buttons.
A FocalShift Hardware restore point represents the selected server as a whole. It is not a WordPress page revision, an individual plugin backup, a single-file browser, or a database-row undo.
The exact contents and current recovery path should be confirmed before a consequential restore.
Explore Managed WordPress →Capture first. Move only after the point exists.
A started action is not yet an available restore point. The relationship between the point and the change should stay clear.
Planning guidance only. This interaction does not create or verify a restore point.
Recovery does not merge the past with everything that happened after it.
Restoring from a whole-server point rebuilds the selected server from that captured state. Later server work may no longer be present.
The whole-server state represented by the selected restore point.
Work and changes that may have been created after the point.
The reviewed Backups page lists and creates restore points but does not expose a visible restore control. Confirm recovery availability and the correct path in the Hardware experience or सपोर्ट हब.
The server returning is the start of verification—not the end.
Customers do not experience a server. They experience the website, its address, and every connected action that should work next. Review the business path without pre-passing a single checkpoint.
Off is not just a quieter switch.
Turning weekly backups off changes the next backup cycle. The current FocalShift confirmation warns that existing automatic backups may be removed.
Illustration only. This control never changes a server or backup setting.
The recurring weekly protection remains enabled for its next configured cycle.
Protection is a setting. Recovery is a prepared decision.
Backups sit inside a wider Hardware practice. Each adjacent tool keeps a distinct responsibility and none proves the others are configured.
Give important change a known point before it.
Add FocalShift Hardware to any paid plan, keep the weekly rhythm visible, and create a deliberate restore point before the moment matters.