What is cloud backup?
Cloud backup transfers recoverable copies of primary data to a different storage layer on a schedule or in response to events. The source can be a virtual-machine volume, database, Kubernetes Persistent Volume, filesystem, SaaS application or configuration repository. The goal is to return to an accepted point after deletion, corruption, a security incident or an infrastructure outage.
With PortvMind Cloud Backup you create and track backups from the panel and restore the point you choose.
Start with a data and dependency inventory
Planning begins by listing the systems that require protection. Alongside databases and files, consider virtual-machine definitions, Kubernetes manifests, secrets and key management, DNS, network rules, application images and external-service dependencies. Separate data that can be reproduced from its source from data that exists in only one place.
Assign a business owner, technical owner, data class, change rate and recovery priority to each asset. Customer transactions and archived logs do not necessarily need the same frequency or retention. Assets without a defined criticality are either protected at unnecessary cost or below the real requirement.
How should RPO and RTO be defined?
RPO is the most data loss you can accept. More frequent backups mean less loss. You set the frequency to match the work.
RTO is how quickly you want the service back. Restore starts from the panel; the time depends on data size and the point you select.
Snapshots and Backup
A snapshot is a point-in-time image of your volume, used for a fast rollback. Backup schedules and stores copies of your servers, volumes and Kubernetes PVC resources, then restores the point you choose from the panel.
Object Storage stores backup files and archives through an S3-compatible API. Scheduled protection and restore from the panel come with Backup.
The 3-2-1 approach and access separation
The 3-2-1 approach keeps several copies of critical data in different places. On PortvMind Cloud you take scheduled copies with Backup and keep archives in Object Storage.
Keep backup access separate from production access. Set who can create and restore backups with console permissions.
Backup frequency and retention policy
You set backup frequency and retention to match the work. Daily, weekly or monthly points can be kept; longer retention costs more.
Schedule, retention and restore target are set in the panel for each resource type. For database workloads, use Backup together with Block Storage.
How does restore work?
Restore the backup you select from the panel. Confirm the application starts and the data is in place.
Be clear about who creates and restores backups. Update frequency and retention as the workload grows.
How should backup architecture be evaluated on PortvMind Cloud?
PortvMind Cloud Backup is used with Block Storage volume and Kubernetes PVC backup scenarios. Object Storage is an S3-compatible destination for application backups and archives. Plan the source, recovery point and restoration path for each data type across Compute, Block Storage, VKE, Backup and Object Storage.
Choose backup frequency to match the work. Restore starts from the panel; the time depends on data size.
Frequently asked questions about Cloud Infrastructure
What is cloud backup?
Cloud backup stores scheduled copies of your servers, volumes and application data. With PortvMind Cloud Backup you create and restore those copies from the panel.
What is the difference between RPO and RTO?
RPO is the data-loss interval you can accept. RTO is how quickly you want the service back. You set the frequency; restore starts from the panel.
Is a snapshot a backup?
A snapshot is a point-in-time image of your volume, used for a fast rollback. Use scheduled Backup jobs for lasting protection.
What is the 3-2-1 backup rule?
It recommends keeping several copies of critical data in different places. On PortvMind Cloud you take scheduled copies with Backup and keep archives in Object Storage.
How often should backups be tested?
Choose backup frequency to match the work. Restore starts from the panel; after the application starts, confirm the data is in place.
Research sources
Technical explanations are based on the primary sources below.
- Contingency planning guide for information systems
Coordinating asset priorities, recovery planning, testing and operational responsibilities.
- Publisher
- NIST
- Type
- Standards and public guidance
- Accessed
- Data backup options and the 3-2-1 approach
The baseline three-copy, two-media and one-offsite-copy approach.
- Publisher
- CISA / US-CERT
- Type
- Standards and public guidance
- Accessed
- Periodic recovery testing
Validating backups through periodic restoration and comparing results with RPO and RTO objectives.
- Publisher
- AWS Well-Architected Framework
- Type
- Official technical documentation
- Accessed