WooCommerce Backup Strategy on GlassHosting
What to protect
- Database (orders, customers)
- wp-content uploads
- Theme/custom plugin code
Cadence
Automate frequent backups before marketing campaigns and plugin updates. Periodically download an offsite copy. Test restore to staging so you know the process before an emergency.
Measure before you guess
Open the resource graphs on panel.glasshosting.com during a normal play window and during a busy one. Write down approximate CPU and memory percentages alongside how the game felt. That habit turns vague “it lags” reports into actionable upgrades or config tweaks.
If graphs look calm while players stutter, ask whether the issue is client FPS, wifi, or a single loaded farm chunk. If graphs are pegged, stop adding content packs until you either tune view distance/entities or upgrade the GlassHosting plan from the client area.
When to involve GlassHosting support
Open a ticket from billing.glasshosting.com when the platform itself looks wrong: panel cannot start the process, allocations seem missing, or multiple unrelated networks cannot reach the service. Include service name, timestamps, and console excerpts without secrets.
For game-logic questions (plugin conflicts, datapack design), include what you already tried. Skim related knowledgebase articles first—many “outages” are EULA flags, edition mismatches, or whitelist misses.
Store-specific reminders
Always smoke-test cart, checkout, and email after changes. Keep staging separate from production payments. Page caches must exclude personalized shop endpoints. Document DNS and SSL ownership so renewals are not tribal knowledge.
When migrating to GlassHosting, lower DNS TTLs ahead of time, schedule a maintenance window, and keep the old host available briefly for rollback. Ticket support if TLS or mail authentication needs platform confirmation.
Security hygiene worth keeping
Use unique passwords for billing, panel, SFTP, and in-game admin features. Enable two-factor authentication wherever the account system offers it. Op sparingly, whitelist private realms, and rotate credentials if they ever appear in a public screenshot.
During incidents, distrust unsolicited DMs offering “free mitigations” that ask for panel logins. GlassHosting support works through the client area ticket system.
Change windows
Batch non-urgent updates into a weekly maintenance window. Tell players ahead of time. After the window, post a short “what changed” message. Predictability builds trust in GlassHosting communities more than surprise restarts.
Documentation habit
Keep a one-page note with: panel URL, who is lead admin, current game version, last backup name, and the exact join string. When you hand off admin duties, that note prevents accidental reinstalls and wrong-version clients.
Related links: panel.glasshosting.com · billing.glasshosting.com · glasshosting.com.
