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.
DATA PROTECTION / CLOUD BACKUPS
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.
01 / Overview
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.
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.
Assess consistency needs for databases, application files and configuration separately. One method should not be assumed to protect every data type equally.
Plan who can access or delete copies. Assess whether an incident affecting production could also compromise the backups.
02 / Architecture
Illustrative recovery cycle: capture, retain, restore in a separate environment and validate the application. Target durations must be tested for the workload.
Selection guide03 / Selection guide
| Consider | How to decide | Why it matters |
|---|---|---|
| Scope | Identify the files, databases and configuration included in protection. | A missing dependency can prevent a recovered application from starting. |
| Frequency and retention | Plan around acceptable data loss and the need to recover older states. | The latest copy may already contain a mistake discovered later. |
| Independence and access | Review where copies are stored and who can remove them. | One incident or loss of access should not defeat every recovery option. |
| Restoration | Test data transfer, application startup and validation time. | Recovery objectives need measured procedures rather than assumptions. |
04 / Use cases
List application files, configuration and data sources together. Record the dependencies required to rebuild the service.
Use a consistent backup method supported by the database. Include post-restore queries and application checks in the procedure.
Define a recovery point before releases or data changes. Assess whether newly written data will remain compatible with the previous application version.
Plans & pricing
Scroll horizontally to view all columns.
| 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
List data and dependencies. Identify priority services and the recovery objectives acceptable to the business.
Match the service scope to your data types. Document consistency, retention and access settings.
Practise recovery without overwriting production. Check data integrity and the functions the application needs to perform.
Review failure notifications and update procedures when data structures change. Record the test date and responsible owner.
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.
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.
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.
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.
Connect product decisions with installation, configuration and operating knowledge.
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
Tell us about your application, expected usage and operating requirements. Let’s bring the resource choices together.