Master: the operations center
The management layer handles backup policies, scheduling, task queues and operation results. Operators monitor task status and recovery targets through the central interface.
ERABACKUP ARCHITECTURE
From management to data.
Make your architecture visible.
Start with an architecture that separates management, data transfer and storage roles. Plan networks, repository capacity and recovery targets around your workloads.
HOW IT WORKS
Steps that work together.
- 01
Source
VM, cloud or application workload
- 02
Transfer
Platform-specific proxy / node / Job
- 03
Storage
Repository and retention policy
- 04
Recovery
Selected target and application validation
DEFINE YOUR SCENARIO
Data path: the right method for the source
OpenStack/Safir node and Data Mover workflows have different prerequisites from the VMware proxy/VDDK path. OpenShift transfers run through Kubernetes Jobs. Select the appropriate component set during deployment.
Repository: the data destination
Configure repository identity, a reachable HTTPS address and the actual storage pool together. Capacity, active transfers and retention chains are part of operations planning. Management and transfer networks can be designed separately when needed.
Recovery target: the starting point
Discuss new isolated VMs, selected volumes and second-cloud targets before selecting the backup method. Plan disk layout, networking, sufficient capacity and application checks at the target.
High availability prerequisites
Application service and database availability are separate concerns. Scheduler leadership handover is not automatic database primary promotion for every failure. Validate quorum, fencing and shared storage during architecture assessment.
COMMON QUESTIONS
Start with
the right questions.
Does data always pass through the Master?
The data path depends on the selected platform and deployment role. Management and data traffic do not have to follow the same path.
Is replication part of this workflow?
Replication source, relay and target components are planned separately. Do not assume that every replication workflow passes through a repository.
START WITH YOUR INFRASTRUCTURE
Platform Architecture — let’s discuss your needs.
Share your workloads and recovery objectives. Let’s define the technical scope together.
