Components and architecture
The Storware Backup and Recovery consists of the following components:
This component manages the entire solution. The server consists of the MariaDB database to track different information about the system such as configuration, permissions, and various metadata. Typically there is one Storware Backup and Recovery server that can work and manage with multiple nodes. The server provides the administrative web UI.
This component is used to manage data movement. The component is responsible among others for performing operations like backup, restore, and mount. Multiple nodes can be connected and managed by the same Storware Backup and Recovery server. Depending on the type of protected systems and data, multiple nodes can be deployed for example for scalability.
The node consists of the following subcomponents:
Data mover that performs backups and restores operations for M365.
This component is responsible for managing the metadata for M365 backup and restoring operations. The cloud server is using SQLite databases to track the metadata of M365 objects. The metadata databases are stored together with the data on the backup destination.
The Endpoint server provides the feature that allows for protecting data in the Continuous Data Protection (CDP) mode for the Windows operating system. The component is managed by the Storware Backup and Recovery system.
The client is a component installed on the Windows operating system. It's responsible for monitoring the filesystem, detecting changes, and protecting data according to the assigned policy.
The endpoint protection supports only IBM Spectrum Protect as a backup destination. This component is delivered as a part of the solution.
The following diagram illustrates the system data flow:
Storware Backup & Recovery components (server, node, and endpoints server) can be installed on the same host.
- The server can be installed on a physical machine or as a virtual machine - externally deployed nodes require network connectivity to the server and backup destinations.
- Nodes may be deployed as physical or virtual systems unless the selected backup strategy requires the node to be installed as a virtual machine on a Hypervisor Cluster (especially with the "disk attachment" export mode).
For detailed deployment scenarios see the following sections:
There are several typical workflows in Storware Backup & Recovery and they result in a set of tasks.
- Export - a task that creates a backup or snapshot and exports data to the staging space
- Store - a task that moves data to the backup destination
- Restore - a task that gets data from a backup provider and puts data in the staging space
- Restore - a task that gets data from a backup provider and puts data in the staging space (if it is a full backup that is being restored residing on the file system backup provider - this task just informs where files are waiting for import task)
- Import - a task that imports data to the virtualization platform and recreates VM
- Restore - a task that gets data from a backup provider and puts data in the staging space (if it is a full backup that is being restored residing on the file system backup provider - this task just informs where files are waiting for the mounting task)
- Mount - mounts backup on the Storware Backup & Recovery Node and either allows user to browse files or exposes backup over iSCSI, so that remote iSCSI initiator can access it)
A task creates a local persisted snapshot of a virtual machine in the hypervisor environment according to a policy that was assigned to the machine. Snapshot retention is managed by the policy settings.