Proxmox Backup Server
Virtual systems are protected and managed using a dedicated backup platform.
Backup & Recovery
Backups only matter when recovery works.
infrahost protects platforms and virtual systems across separate locations. Retention, protection scope and recovery priority are agreed to match each service.
More than a backup file
A backup strategy needs defined scope, retention and ownership.
A green backup job does not tell you which data is included, how long versions remain available or how quickly a service is expected to return after an outage.
infrahost combines technical backup with an agreed recovery model. We distinguish between platform protection, system recovery and application-specific requirements.
Scope of service
The building blocks of a transparent protection strategy.
Not every service needs the same retention period or recovery time. We design protection around criticality and actual requirements.
Separate locations
Backup copies can be retained outside the production location.
Retention
Daily, weekly or longer-term recovery points are defined individually.
Access protection
Backup access and permissions are separated and kept as restrictive as practical.
Recovery process
Responsibilities and recovery order are clarified before an incident occurs.
Monitoring
Failed backups and capacity issues are monitored technically.
White-label delivery
Backup as part of your own managed service.
You define which systems are protected and what the service includes for your customers. infrahost provides the technical backup infrastructure and assists with recovery.
Reporting and communication can run through your IT company, keeping the backup service part of your overall offering.
- Backup scope by customer and service
- Retention aligned with risk and budget
- Recovery requests through your IT company
- Priority levels for critical systems
- Optional scheduled recovery tests
Operations
During an outage, the prepared recovery order matters.
In a larger incident, not every system can be restored at the same time. We therefore define priorities and dependencies in advance.
Protection scope
We document which systems, data and configurations are actually protected.
Retention
Retention and storage requirements are planned around the required recovery points.
Monitoring
Backup jobs, storage and failures are monitored and reported through defined channels.
Recovery
Recovery order and priority follow the agreed service level and system dependencies.
Transparency
Backup does not automatically provide high availability.
Backup enables recovery but does not prevent every interruption. Very short downtime targets require additional architecture, available replacement resources and an appropriate service level. These elements are planned separately.
Frequently asked questions
Questions about backup and recovery.
For binding details on architecture, scope and service levels, we discuss your specific environment.
Ask a technical questionCan backups be stored across multiple locations?
Yes. Depending on the service and agreement, backups can be retained at a separate infrahost location.
How long are backups retained?
Retention is not one-size-fits-all. It is defined per service based on risk, data volume, compliance requirements and budget.
Who is authorised to request a recovery?
Authorised persons and approval paths are documented in the partner and customer process so data is never restored without clear authorisation.
Are recoveries tested?
Scheduled recovery tests can be agreed. Scope and frequency depend on criticality and the level of assurance required.
Next step
Define backup scope and recovery before an incident occurs.
We discuss systems, data, retention, locations and priorities.