Backup · Snapshot · Offsite · DR

BACKUP POLICY

Your data is protected with a multi-layer backup architecture. Transparent retention policy, RPO/RTO targets and a clear restore process.

Backup Architecture

Daily, weekly, snapshot and offsite layers keep your data redundant and accessible.

Daily Backup

Automated full image backup every night. Production data is protected on a regular schedule.

Weekly Backup

Weekly consolidated backups for long-term restore points and archive protection.

Snapshot

Point-in-time snapshots for fast rollback, test cloning and protection before critical changes.

Offsite Backup

A second copy in a geographically separate location. Extra protection against data center risks.

Data Retention Policy

Retention periods are defined transparently by backup type.

Backup Type Retention Period Description
Daily 7 days Full system backups for the last 7 days
Weekly 4 weeks Weekly full backups for long-term restore
Monthly 3 months Monthly archive copies for compliance and audit

Disaster Recovery

Measurable targets for data loss and downtime in disaster scenarios.

RPO — Recovery Point Objective

≤ 24 hours

Daily backups allow up to 24 hours of acceptable data loss. Snapshots can reduce this to 1 hour.

RTO — Recovery Time Objective

≤ 4 hours

Standard restore operations complete within 4 hours. Emergency response targets 1 hour.

Backup Process

Your data is protected step by step through the backup pipeline.

Data

Production server and disk data

Snapshot

Point-in-time consistency

Storage

Encrypted backup storage

Offsite Copy

Geographically redundant second location

Data Restore Process

Clear, traceable steps from restore request to handover.

  1. Submit a Request

    Open a request via the client panel or support ticket. Specify the server and backup date.

  2. Select Restore Point

    Confirm the appropriate daily, weekly or snapshot restore point together with our team.

  3. Verification and Approval

    Our technical team validates backup integrity and confirms full or partial restore scope.

  4. Restore Operation

    The selected backup is restored to the target server or an isolated environment. You are kept informed throughout.

  5. Test and Handover

    After access and service tests are complete, the system is handed over to you.

Frequently Asked Questions

Basic backup infrastructure is standard on cloud server plans. Advanced backup, extended retention and offsite copies can be enabled as options.

Daily backups are full images taken every night for short-term restore. Weekly backups are kept longer for archive purposes.

A snapshot is an instant copy of disk state at a specific moment. Ideal for quick rollback before updates, migrations or critical changes.

A copy of backups is transferred to a geographically separate location from the primary data center for additional protection.

RPO (Recovery Point Objective) is acceptable data loss window; RTO (Recovery Time Objective) is how long until the system is operational again.

Daily backups are kept for 7 days, weekly for 4 weeks, monthly archives for 3 months. Custom retention is available for enterprise projects.

Standard restore operations typically complete within 4 hours. Priority response can reduce this to 1 hour in emergencies.

Yes. You can request partial restore at file, folder or database level instead of a full server restore.

Yes. Backups are encrypted in transit and at rest; only authorized systems and staff can access them.

OwnHost backup infrastructure provides strong protection; however we recommend customers also maintain their own backups for critical data.

Build a backup plan for your cloud server

Explore our cloud server plans or contact our team for custom backup requirements.

View Cloud Server