Skip to content
FibaCloud

DATA PROTECTION / CLOUD BACKUPS

A backup proves its value when you can restore from it.

Protecting server and application data involves more than creating a copy. Define what Cloud Backups captures, how far back you need to recover and how the application will run again. Treat restoration as an operating procedure that needs testing.

FibaCloud platformCloud Backups
From backup copy to a running application
Workload first
Recovery as the central outcomeProtection suited to the dataClear access and retention controls

01 / Overview

Backup is an operating plan, not only a stored copy.

File copies, disk images and database backups address different recovery requirements. Copying the files of a running database does not necessarily produce a consistent backup. Choose a method appropriate to the data, and verify capture, retention and restore capabilities against the selected service scope.

RPO describes the amount of data loss the business aims to tolerate; RTO describes the targeted time to restore service. These are planning objectives, not automatic guarantees from a backup product. Relate them to application dependencies, data volume and measured restore exercises.

01

Recovery as the central outcome

Define the steps from capturing a backup to starting the application. Verify that data can be used, rather than checking only that a file exists.

02

Protection suited to the data

Assess consistency needs for databases, application files and configuration separately. One method should not be assumed to protect every data type equally.

03

Clear access and retention controls

Plan who can access or delete copies. Assess whether an incident affecting production could also compromise the backups.

02 / Architecture

From backup copy to a running application

Illustrative recovery cycle: capture, retain, restore in a separate environment and validate the application. Target durations must be tested for the workload.

Selection guide
Architecture explained
  1. Capture data
  2. Retain copy
  3. Restore data
  4. Verify application
Illustrative recovery cycle: capture, retain, restore in a separate environment and validate the application. Target durations must be tested for the workload.

03 / Selection guide

Four questions that clarify the recovery objective.

Four questions that clarify the recovery objective.
ConsiderHow to decideWhy it matters
ScopeIdentify the files, databases and configuration included in protection.A missing dependency can prevent a recovered application from starting.
Frequency and retentionPlan around acceptable data loss and the need to recover older states.The latest copy may already contain a mistake discovered later.
Independence and accessReview where copies are stored and who can remove them.One incident or loss of access should not defeat every recovery option.
RestorationTest data transfer, application startup and validation time.Recovery objectives need measured procedures rather than assumptions.

04 / Use cases

Situations that need an explicit recovery plan.

01 / Cloud Backups

Server and application data

List application files, configuration and data sources together. Record the dependencies required to rebuild the service.

02 / Cloud Backups

Database workloads

Use a consistent backup method supported by the database. Include post-restore queries and application checks in the procedure.

03 / Cloud Backups

Protection before change

Define a recovery point before releases or data changes. Assess whether newly written data will remain compatible with the previous application version.

Plans & pricing

Compare available configurations

View all pricing
Published product configurations
Storage$/Mo
80 GB$8
640 GB$64
1280 GB$128

Review the current configuration, price and order terms before selecting a service.

05 / From planning to operation

From a saved copy to a verified application.

  1. Inventory the service

    List data and dependencies. Identify priority services and the recovery objectives acceptable to the business.

  2. Validate the method

    Match the service scope to your data types. Document consistency, retention and access settings.

  3. Restore separately

    Practise recovery without overwriting production. Check data integrity and the functions the application needs to perform.

  4. Keep the plan current

    Review failure notifications and update procedures when data structures change. Record the test date and responsible owner.

Questions

A clearer path to your next decision.

Talk to our team
Is a snapshot the same as a backup?

Not always. A snapshot may represent storage at a point in time; independent retention, application consistency and restore scope depend on the service. Evaluate it against the actual recovery requirement.

Does having a backup mean there can be no data loss?

No. Changes between captures, excluded data or failed restoration can still cause loss. Use the defined RPO and measured test results to understand the protection available.

Is copying the files of a running database enough?

It depends on the database and method. Use supported consistency or shutdown procedures, then verify the recovered data rather than assuming the copy is usable.

When should I test restoration?

Test after initial setup, after important application or data changes, and at intervals suited to the business risk. Use a separate environment that protects live data during the exercise.

Go deeper with practical guides.

Connect product decisions with installation, configuration and operating knowledge.

Explore technical tutorials

Technical references

These references explain the technical concepts discussed on this page. Available configurations and service scope are defined by FibaCloud product and order information.

FIBACLOUD / Cloud Backups

Start with your project. Build on the right resources.

Tell us about your application, expected usage and operating requirements. Let’s bring the resource choices together.

Opens live support provided by Tawk.to.