Disaster Recovery
RPO vs RTO: Understanding Backup and Recovery Objectives
What recovery point objective and recovery time objective mean, how to set them for each system, and how they shape your backup design.
Backup security designed for the worst day
Attackers know that backups are the last line of defense, so they look for them first. Backnix is designed so that backup data stays protected even if a server is compromised.
The problem
The problem: backups are a target
Backups contain databases, credentials, personal data and intellectual property in one convenient place. Ransomware groups routinely try to delete or encrypt backups before they encrypt production.
Unencrypted copies
A leaked backup is a data breach.
Shared credentials
If the server can delete its backups, so can whoever controls the server.
Weak admin access
Password-only access to backup consoles is an easy entry point.
The consequence
The consequence: losing the last line of defense
When backups are encrypted or deleted together with production, the organization loses its ability to recover without paying. When backups leak, the incident becomes a privacy breach with legal and reputational costs.
The solution
How Backnix approaches security
Security is part of the architecture, not a setting. Data is encrypted on your server, travels over TLS, is stored encrypted and is accessed with least-privilege credentials.
Client-side encryption
Backups are encrypted before upload with keys that stay under your control.
TLS everywhere
Every connection to the platform and to storage is encrypted in transit.
Least privilege
Agents are designed to write backups without broad permissions to delete history.
Multi-factor authentication
Administrative access to Backnix supports TOTP second factor.
The diagram shows the designed architecture; availability is listed below.
Benefits
Benefits
Breach-resistant backups
Encrypted data is useless without the key.
Ransomware resilience
Immutable storage options and limited agent permissions reduce what an attacker can destroy.
Auditability
Administrative actions are logged.
Technical considerations
Technical considerations
Client-side encryption means the encryption key is critical: if it is lost, the data cannot be recovered by anyone, including Backnix. Store a copy of the key in a password manager or a sealed offline location. Immutability with S3 Object Lock depends on the storage provider and bucket configuration; versioning alone protects against overwrites but not against an attacker with permission to delete versions. Combine encryption, immutability, monitoring and restore tests for a complete strategy.
Availability
Current status of these capabilities
- EncryptionComing soon
Client-side encryption before upload and TLS in transit.
- Backup MonitoringComing soon
Status and alerts for every backup job.
- Backup HistoryComing soon
Versioned history of every backup run.
Status is updated as capabilities are released. See all features.
Related articles
Learn more
Security FAQ
Can Backnix read my backups?
With client-side encryption and keys held by you, the stored data is encrypted and cannot be read without your key.
What happens if I lose my key?
Encrypted data cannot be decrypted without the key. Keep at least one secure copy outside the server.
Do you offer immutable backups?
Immutability depends on S3 Object Lock support of the storage destination. Availability is shown per region and plan.
Ready to protect these systems?
Compare storage plans in USD or BRL. Yearly plans include 50% off the first annual payment.
Talk to us
Get in touch about your environment
Tell us what you need to protect. We will answer by email; nothing is charged.