Cyberbackup 18: Open API and new media contour

Cyberbackup 18: Open API and new media contour

      The key change is the scalability of the management server installation: in version 18.0 it supports up to 60,000 mailboxes and up to 20,000 virtual machines within a single installation.

      This capacity is aimed at large, fast‑growing environments where strict backup windows must be met without fragmenting into multiple independent deployments.

      Support for data sources has been expanded. In the Linux agent, kernels up to version 6.14 have been updated and active ransomware protection has been added: a kernel‑level driver monitors file system operations and, together with an ML model, recognizes characteristic attack patterns. The mechanisms include blocking suspicious processes, terminating connections, component self‑protection, allow/deny lists and automatic restoration of files damaged prior to the point of lockout. Both local file systems and mounted SMB/NFS shares are protected, which is critical for safeguarding network storage and backup repositories.

      Dmitry Antonov, Director of the Backup Systems Department, photo: Andrey Vinogradov

      In virtualization, Proxmox VE and “Alt Virtualization” have been added with support for agentless backup, CBT, LAN‑free and instant recovery. This reduces resource contention inside VMs and speeds up initial protection deployment. At the same time, integration with hardware snapshots on the storage array side has been expanded: Cyber Backup 18.0 supports snapshots on YADRO TATLIN.UNIFIED for VMware environments. Storage‑array‑level snapshots reduce load on hypervisor hosts and network interfaces, speed up copying and eliminate the risk of VM degradation due to delta‑file overflow under high change rates.

      For DBMSs, the first version of multithreaded full backup for PostgreSQL and compatible forks has been introduced. The new mode relies on its own file mechanism, complementing existing BASE_BACKUP schemes and WAL collection via replication slot, and is intended to reduce the backup window for large instances through parallelism.

      In the corporate communications block, support for CommuniGate Pro has been expanded: multi‑server cluster configurations and granular recovery down to mailbox, individual messages and attachments have been added. Integration with Mailion (“MyOffice”) has also been implemented, with full and incremental copies and recovery of mailboxes, messages and calendars; in the first version recovery is available to the original location.

      In management, an open API has been added for working with protection plans and device groups — creation, deletion, parameter changes, enabling/disabling, listing, as well as managing dynamic groups and applying them to devices. The API complements the web console, CLI and bootable media, simplifying automation in large environments and integration with external systems.

      Dmitry Antonov, Director of the Backup Systems Department, Tatyana Dmitrieva, Backup Systems Manager, photo: Andrey Vinogradov

      An introductory MVP version of the new Cyber Media Server has been presented — a media server intended to eventually replace the current Storage Node. The MVP is deployed as a single instance on RED OS 7.3 and supports storing backups on local disks, SMB/CIFS, NFS, iSCSI, FC, S3, in Cyber Storage, YADRO TATLIN.UNIFIED and other hardware/software repositories. A significant innovation is “direct” sending of backups to S3 without deploying Cyber Infrastructure/Cyber Storage, as well as the ability for multiple Cyber Backup installations to centrally share the same storage. The current MVP lacks a GUI, high‑availability configurations, media features (for example, built‑in deduplication), enhanced security, audit/monitoring and tape support; these capabilities are planned on the roadmap for future releases.

      Other changes include: improved compatibility with third‑party deduplication solutions at the .tibx archive level (the ability to disable built‑in deduplication to avoid duplicate operations and ensure correct operation with, for example, YADRO TATLIN.BACKUP with T‑BOOST); refined mechanisms for working with tape libraries (support for cleaning media, write protection, cleaning a selected drive, moving media between pools); added new audit and monitoring events (including monitoring availability of virtualization agents); and an option to disable encryption of backup traffic when transferring to the Storage Node for large‑volume scenarios — in some cases this yields a severalfold increase in throughput and shortens backup windows.

      Taken together, the changes in 18.0 are aimed at protecting tens of thousands of objects in a single installation, accelerating backups of high‑load workloads (virtualization, mail systems, PostgreSQL), increasing resilience to ransomware in Linux environments and simplifying centralized management through the open API and the new media storage tier. The roadmap foresees a stabilization release 18.1 and further development of the Cyber Media Server, the API and support for key platforms in subsequent versions.

Cyberbackup 18: Open API and new media contour Cyberbackup 18: Open API and new media contour

Other articles

Cyberbackup 18: Open API and new media contour

The key change is the scalability of the management server installation: version 18.0 supports up to 60,000 mailboxes and up to 20,000 virtual machines within a single installation.