vPlus 7.0
  • Welcome to vPlus!
  • Overview
    • Main Features
    • Support Matrix
    • Components and Architecture
    • Typical Scenarios
    • Licensing
    • Product Life Cycle
  • Deployment
    • Component Requirements
    • Supported Platforms Requirements
    • Sizing Guide
      • Small
      • Medium
      • Large
    • Installation
      • Quick Installation Using All-in-one Script
      • Installing vPlus Offline
      • Adding vPlus Nodes
    • Initial Configuration
    • Backup Destinations
      • File System
        • Synthetic File System
          • XFS
          • DD Boost
        • isoLayer (Synthetic)
        • File System
          • Virtual Data Optimizer (VDO)
        • Catalogic Software vStor
      • Deduplication Appliances
        • Huawei OceanProtect
        • HPE StoreOnce
        • Exagrid
        • Neverfail HybriStor
      • Object Storage
        • Alibaba Cloud OSS
        • AWS S3 or S3-compatible
        • Ceph Rados Gateway
        • Cloudian S3
        • Wasabi
        • Google Cloud Storage
        • IBM Cloud Object Storage
        • Microsoft Azure Blob Storage
        • Nutanix Objects
        • OpenStack SWIFT
        • Oracle Cloud Infrastructure Object Storage
        • Scality RING
      • Tape Pools
    • High Availability
      • 2 Node Cluster
      • 3 Node Cluster
    • Common Tasks
      • Staging Space Configuration
      • Enabling HTTPS Connectivity for Nodes
      • LVM Setup on vPlus Node for Disk Attachment Backup Mode
      • Full Versions of libvirt/qemu Packages Installation
      • SSH Public Key Authentication
      • Enabling HTTP(S) Proxy for vPlus
  • Protecting Virtual Environments
    • Virtual Machines
      • Nutanix Acropolis Hypervisor (AHV)
      • Red Hat Openshift Virtualization
      • Red Hat Virtualization
      • oVirt
      • Oracle Linux Virtualization Manager
      • Oracle VM
      • Proxmox VE
      • KVM/Xen
      • OpenStack
      • OpenNebula
      • Virtuozzo
      • Citrix Hypervisor (XenServer)
      • XCP-ng
      • Huawei FusionCompute
      • SC//Platform
    • Cloud
      • Amazon EC2
      • GCP GCE
      • Azure Cloud
    • Containers
      • Red Hat OpenShift
      • Proxmox VE
    • Backup & Restore
  • Protecting Microsoft 365
    • Microsoft 365 Organization Management
      • Configure Microsoft 365 Access
      • Add Microsoft 365 Organization Manually
      • Add Microsoft 365 Organization Using the Setup Assistant
      • Account Auto-synchronization
    • Backup & Restore
    • Suppoted Sharepoint Templates and Limitations
  • Protecting Applications
    • Applications
      • PostgreSQL
      • DB2
      • Relax and Recover - ReaR
      • Git
      • oVirt/RHV/OLVM
      • Kubernetes/OpenShift etcd
    • Backup & Restore
  • Protecting Storage Providers
    • Storage Providers
      • File System
      • Ceph RBD
      • Nutanix Files
      • Nutanix Volume Groups
    • Backup & Restore
  • Administration
    • Dashboard
    • Virtual Environments
      • Instances
        • Backup On-Demand
        • Restore On-Demand
        • Snapshot Management
      • Virtualization Providers
      • Backup SLAs
        • Policies
        • Schedules
      • Snapshot SLAs
        • Policies
        • Schedules
      • Recovery Plans
        • Policies
        • Schedules
      • Mounted Backups (File-level Restore)
    • Storage
      • Instances
        • Backup On-Demand
        • Restore On-Demand
      • Infrastructure
      • Backup SLAs
        • Policies
        • Schedules
      • Snapshot SLAs
        • Policies
        • Schedules
      • Mounted Backups (File-level Restore)
    • Microsoft 365
      • Instances
      • Organizations
      • Backup SLAs
        • Policies
        • Schedules
      • Download
    • Applications
      • Instances
      • Execution Configurations
      • Backup SLAs
    • Reporting
      • Virtual Environments
      • Storage
      • Microsoft 365
      • Applications
      • Notifications
      • Audit Log
    • Nodes
      • Instances
      • Node Configurations
    • Access Management
      • Users
      • Groups
      • Roles
      • OS Credentials
    • Settings
      • Global Settings
      • Internal DB Backup
      • Notification Rules
      • Mailing Lists
      • Endpoints Global Settings
    • Upgrade
    • CLI Reference
    • CLI v2 Reference (technical preview)
  • Integration
  • Troubleshooting
    • How to Enable vPlus DEBUG Mode
    • Collecting Logs
    • External Log Targets
    • Disaster Recovery
  • Known Software Issues and Limitations
  • Glossary
Powered by GitBook
On this page
  • Server
  • Node
  • Architecture
  • Components deployment
  • Typical workflows
  1. Overview

Components and Architecture

PreviousSupport MatrixNextTypical Scenarios

The vPlus consists of the following components:

Server

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 vPlus server that can work and manage with multiple nodes. The server provides the administrative web UI.

Node

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 vPlus 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:

Cloud agent

Data mover that performs backups and restores operations for M365.

Cloud server

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.

Architecture

The following diagram illustrates the system data flow:

Components deployment

vPlus 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:

Typical workflows

There are several typical workflows in vPlus and they result in a set of tasks.

Backup

  • 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 to filesystem

  • Restore - a task that gets data from a backup provider and puts data in the staging space

Restore to a virtualization platform

  • 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

Mount (file-level restore)

  • 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 vPlus Node and either allows user to browse files or exposes backup over iSCSI, so that remote iSCSI initiator can access it

Snapshot

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.

Virtual Environments
Microsoft 365
Applications
Storage Providers