Backup Policy

Introduction

This Backup Policy outlines how Suzko, LLC ("we," "us," or "our") manages data backups for our hosting services, including backup schedules, retention periods, and recovery procedures. Understanding our backup practices helps you make informed decisions about protecting your data.

1. Backup Coverage by Service Type

Backup coverage varies by service type. Review the table below to understand what backups are included with your service:

2. Backup Types

2.1 Full Backups

Full backups capture all data associated with your service at a specific point in time. Full backups are performed:

• Weekly for shared and reseller hosting accounts
• Daily for business hosting accounts
• As configured for VPS and dedicated servers with backup add-ons

2.2 Incremental Backups

Incremental backups capture only changes since the last backup, reducing storage requirements and backup time. Incremental backups are used between full backups where applicable.

2.3 Snapshots

For VPS and cloud services, snapshots provide point-in-time copies of your entire virtual machine state, including:

• Operating system configuration
• Installed applications
• All stored data

Snapshots may be available as an on-demand feature or add-on service.

3. What Is Backed Up

3.1 Included in Backups

Standard backups typically include:

• Website files and directories
• Databases (MySQL, PostgreSQL, etc.)
• Email accounts and messages (where applicable)
• Control panel configuration
• SSL certificates
• DNS zone files

3.2 Not Included in Backups

The following are typically NOT included in standard backups:

• Log files and temporary data
• Cache and session files
• Large media files exceeding quota limits
• Third-party application data not in standard locations
• Custom configurations outside the control panel

4. Backup Schedule

Backup times are approximate and may vary based on system load and data volume. Backups are performed during off-peak hours to minimize impact on service performance.

5. Backup Storage and Security

5.1 Storage Location

Backups are stored:

• On separate storage systems from production data
• In geographically distinct locations when possible
• Using redundant storage (RAID) for reliability

5.2 Encryption

All backups are protected with:

• AES-256 encryption at rest
• TLS encryption during transfer
• Secure key management practices

5.3 Access Controls

Backup access is restricted to:

• Authorized system administrators
• Automated backup and restore processes
• Customer-initiated restores through the control panel

6. Restoration Process

6.1 Self-Service Restore

Many services offer self-service restore through your control panel:

• Plesk: File Manager or Backup Wizard
• Game Servers: Pterodactyl panel backup section
• Databases: phpMyAdmin or database management tools

6.2 Support-Assisted Restore

For full account restores or complex recovery scenarios, contact our support team. Include:

• Your account/service identifier
• Desired restore date and time
• Specific files/databases to restore (if applicable)
• Reason for restore request

6.3 Restoration Time

7. Customer Responsibilities

Our backups are provided as a convenience and should not be your only data protection strategy. You are responsible for:

• Maintaining your own backups: Keep independent copies of critical data
• Testing restores: Periodically verify your backup integrity
• Understanding coverage: Know what is and isn't backed up for your service
• Timely requests: Request restores before retention periods expire
• Add-on services: Purchase additional backup coverage if needed

8. Backup Add-Ons

We offer additional backup services for customers requiring enhanced protection:

9. Limitations and Exclusions

We do not guarantee:

• That all backups will complete successfully every time
• That data can be recovered in all circumstances
• Specific recovery time objectives unless covered by SLA
• Backup availability during system maintenance or outages

We are not liable for:

• Data loss due to customer actions or malware
• Data loss exceeding our backup retention period
• Failed restores due to data corruption at the source
• Consequential damages from backup failures

10. Disaster Recovery

In the event of a major disaster affecting our primary data center, we maintain disaster recovery procedures that include:

• Off-site backup copies in separate geographic locations
• Documented recovery procedures
• Regular disaster recovery testing
• Priority restoration for critical infrastructure

For customers with specific disaster recovery requirements, please contact us about our enterprise backup and DR solutions.

11. Policy Changes

We may update this Backup Policy as our practices evolve. Material changes will be communicated via email or service announcements.

Contact Information

For backup-related questions or to request a restore, please contact us at:

Last updated: January 16, 2026