Differences

This shows you the differences between two versions of the page.

--- wiki:cpbackuprestore [2025/07/01 00:06] – guidebeacon
+++ wiki:cpbackuprestore [2025/07/01 00:35] (current) – guidebeacon
@@ Line 33: / Line 33: @@
 ===== Offsite Restore =====
-...
+Follow these steps in the event that the Beacon WHM server needs to be restored off-site.
+Note that image level backups should be periodically taken a few times per year, since any customization done outside of cPanel will not be included in the normal cPanel backups.
+  - Send a copy of the latest image level backup to the facility for restoration.
+  - If restoring fails, an older image could be attempted. If restoring an image is not possible, then the fallback plan would be to perform a fresh WHM install, then restore the latest cPanel backup from Backblaze.
+  - The facility will need to restore the image into their infrastructure somehow. There isn't a standard process for this.
+  - Once the image is restored, the IP will need to be updated on the server. This will need to  be done by the staff at the new site. If remote staff ask for credentials, they will be the same as they were when the image was taken.
+  - Once Beacon has access to WHM, all that needs to be done is to restore the latest cPanel backup from Backblaze.
+  - WHM - Backup - Backup Restoration or just search for "restore"
+  - When performing the restore, pick the most important accounts first. Restoring is likely to take a long time, possibly more than a day.
 ===== Advanced Restore =====
 This section will require use of the shell.
+Updated on 2025-06-30: The information in this section may no longer be relevant due to the change to S3 based backup with Backblaze.
 ==== Limited Disk Space ====