Backup overview
Your two sites, backed up beyond the server.
Waiting for verified backup status from the server.
Protected sites
Latest activity
Backup schedules
How these backups work
The first successful account run creates the encrypted baseline. Later account runs upload new and changed file data. Daily database-only runs create a fresh, full SQL export of the current live database for each site, without uploading site files or unrelated databases.
All successful restore points from at least the last three months are retained. Retention is applied after a successful backup and verification. Off-site jobs are independent of the local WHM backup schedule.
Schedule changes are managed on the server. This page reports the active configuration.
GGHyd activity
Select an account to load its off-site backup logs.
This view shows a bounded portion of the off-site service log. Local WHM logs are managed separately.
Backblaze B2
Awaiting statusBackup data is encrypted before upload. The website does not display application keys or repository passwords.
Your private backup destination
- Create a private Backblaze B2 bucket.
- Create an application key restricted to that bucket, with read and write access.
- Save the key securely and provide it using the administrator’s protected setup process.
- The service must verify the connection and first backup before an off-site restore point is available.
Do not paste application keys into chat or into backup logs. This page does not currently accept credentials.
Private access activity for this backup dashboard. Collection starts when analytics is enabled; earlier visits are not included. IP addresses do not identify a person or establish whether traffic is a bot.
IP and recent-event details are limited. Aggregate activity counts include all recorded requests; unique IP counts reflect retained details.
Daily access
IP activity
Recent sign-in activity
Records are kept for 30 days on this server. Page views count loads of the dashboard page, not visits to either store. Rejected verification checks and rate limits show blocked requests; they do not prove malicious intent.
Prepare a recovery download
Choose the download contents, then a verified restore point.
A download you can inspect first
Each prepared export is a separate archive for review or recovery on an isolated host. Database downloads contain SQL files.
Prepared downloads expire after 48 hours. The service permits up to two stored exports and limits preparation to one request per account per hour.
Deleting a prepared export removes that download. The retained backup restore points remain available.