NQRust Backup and Restore

Your backup is only as good as your next recovery.

Protect Linux and Windows systems, keep copies on disk, tape, or S3-compatible storage, and recover the exact files and versions you need from one control plane.

01Linux and Windows
02Full, Differential, and Incremental
03Disk, Tape, and S3-Compatible Storage
04WebUI and Scriptable Console
01

NQRust Backup and Restore

Recovery Readiness

Can your team find the right data when the request arrives?

NQRust brings the answers into one operational workflow:

  • Protected systems and jobs are visible.
  • Recovery points and file versions are searchable.
  • Storage and media relationships are cataloged.
  • Original and alternate restore destinations are supported.
02

NQRust Backup and Restore

When something breaks, can your team answer these five questions?

A completed backup job is useful. A clear recovery path is what keeps the business moving.

  1. What is protected right now?
  2. Which version can we recover?
  3. Where is that copy stored?
  4. Who is allowed to restore it?
  5. How will we prove it worked?
NQRust turns scattered backup tasks into a recovery-ready system: policy, storage, catalog, and restore working together.
03

NQRust Backup and Restore

One workflow for the complete protection journey

Define what matters before the incident, place each copy where it belongs, and give operators a guided path to the required data.

1. Protect by policy

Select clients and files, then combine scheduled or on-demand jobs with full, differential, incremental, Virtual Full, or Always Incremental workflows.

2. Retain where it fits

Use pools, retention, pruning, recycling, copy, and migration jobs across disk, tape, and configured S3-compatible storage.

3. Find through the catalog

Browse jobs, directories, files, versions, media, and storage relationships through catalog metadata instead of searching volumes manually.

4. Restore where needed

Recover selected files or directories to the original system, an alternate path, or another configured client, with controlled replace behavior.

What the operator sees

Job history, available versions, a browsable file tree, restore destination, replace policy, and the resulting recovery job.

What NQRust coordinates

The Director controls the job and catalog. Normal backup and restore payload moves directly between the protected system and the Storage Daemon.

04

NQRust Backup and Restore

Make backup decisions around recovery—not around tool limitations

Recover precisely

Bring back the data that is actually needed

Search cataloged recovery points, choose the required version, and restore selected files or directories without treating every request as a full-system exercise.

Relevant capabilities:

  • File selection
  • Version browsing
  • Alternate restore path
  • Supported ACL and metadata preservation

Match retention to risk

Put each copy on the storage that fits its purpose

Keep operational recovery copies on disk, use managed tape for removable-media strategies, and add configured S3-compatible storage for an external destination.

Relevant capabilities:

  • Disk volumes
  • Tape and changers
  • S3-compatible targets
  • Copy and migration jobs

Run mixed infrastructure centrally

Apply one operating model across distributed systems

Coordinate Linux and Windows clients from a central Director, with optional integration paths for specialized workloads and network-storage environments.

Relevant capabilities:

  • Linux clients
  • Windows clients
  • Windows VSS
  • Optional workload plugins

Keep control and automate

Make daily operations visible and repeatable

Use the WebUI for routine administration and the scriptable console for automation, while named consoles, profiles, and ACLs restrict commands and resources.

Relevant capabilities:

  • WebUI
  • Scriptable console
  • Job messages
  • Command and resource ACLs
05

NQRust Backup and Restore

Explore NQRust through the use case that matters to you

You do not need to redesign every backup workflow at once. Start with one representative system and prove the restore.

Linux and Windows file protection

Centralize recurring protection for file servers, shared data, application files, and configuration.

Disk plus tape retention

Combine directly accessible disk copies with managed tape pools and automated libraries.

External object storage

Add a configured S3-compatible destination without operating an object-storage service inside NQRust.

Remote and branch systems

Coordinate protection across the network, subject to the required connectivity and security design.

NAS and SAN workflows

Use NDMP paths for validated network-storage devices and supported recovery scenarios.

Virtualization integrations

Explore release-specific plugin paths for VMware, Hyper-V, and Proxmox after compatibility has been confirmed.

Start small. Prove recovery. Expand with evidence.
One client, one policy, one storage destination, and one meaningful restore are enough to begin.
06

NQRust Backup and Restore

Control without turning backup into a black box

Open foundation

The AGPLv3-licensed core, inspectable configuration, and plugin interfaces give teams visibility into how the platform operates and room to extend it.

Storage choice

Disk, tape, and configured object-storage paths allow recovery speed, retention, location, and cost to shape the design.

Central orchestration, direct data path

The Director coordinates policy and catalog updates while normal file payload moves between the protected client and storage.

Architecture overview

People and automation
        |
WebUI and Console
        |
Director <----> PostgreSQL Catalog
        |
        +---- job and policy control ----+
                                          |
Protected Client <==== backup data ====> Storage Daemon
Linux / Windows                          Disk / Tape / S3

PostgreSQL stores catalog metadata. Backup payload remains on the media managed by the Storage Daemon.

Security capabilities you can review

Security is configured and validated for each deployment—not hidden behind a marketing claim.

  • Configurable TLS for service and console connections
  • Configurable client-side signing and encryption
  • Director command- and resource-level ACLs
  • Administrative and read-only WebUI roles
  • Job messages and command auditing
  • Supported ACL and extended-attribute preservation
07

NQRust Backup and Restore

What customers usually ask next

01Which systems can I protect?

The deploy-ready path in this release focuses on an Ubuntu-based server with Linux and Windows client bundles. Exact operating-system and workload versions are confirmed for the selected release.

02Can I recover individual files?

Yes. Browse cataloged jobs and versions, select files or directories, and restore them to the original or an alternate destination.

03Which storage targets are available?

Configured destinations include disk or file volumes, tape and automated libraries, and S3-compatible storage through the available integration.

04How is access controlled?

Named consoles, profiles, and Director ACLs restrict commands and resources. The WebUI also provides administrative and read-only roles.

05Can components be separated?

Yes. Director, PostgreSQL catalog, clients, and Storage Daemons have distinct roles and can be placed according to network, security, and storage needs.

Have a question about your environment?

Bring the operating system, workload, or storage target you want to explore.

08

NQRust Backup and Restore

Do not take a backup claim on faith. Prove a restore.

Bring one representative workload and one recovery question. See the path from protection policy to restored data using your success criteria.

What the recovery proof covers

  1. Connect a representative client
    Linux or Windows, using the security profile chosen for the exercise.
  2. Define and run the policy
    Set the fileset, schedule or on-demand job, backup level, pool, and destination.
  3. Explore the recovery points
    Review job history, browse versions, and select meaningful data.
  4. Restore to an alternate location
    Verify the recovered files, metadata, job result, and elapsed recovery time.
  5. Leave with evidence
    Document what worked, what needs adjustment, and the next production step.

Start the conversation

What would you like to recover first?

A short discovery call is enough to identify the most useful demo or proof-of-concept path.

  • Name
  • Business email
  • Organization
  • Current backup or recovery challenge
Compatibility, security configuration, storage integration, and workload-specific capabilities are validated for the target release and environment. No universal performance or recovery-time claim is implied.