Configuring Veeam Backup & Nextcloud External Storage with S3 Object Storage

For enterprise IT infrastructure directors, systems engineers, and Managed Service Providers (MSPs), protecting corporate virtualization clusters and collaborative file repositories is a cornerstone of operational resilience.

Two open-standard platforms represent the industry benchmark in this domain:

1. Veeam Backup & Replication: The enterprise gold standard for VMware vSphere, Microsoft Hyper-V, Nutanix AHV, and physical server disaster recovery.
2. Nextcloud Hub: The premier private cloud content collaboration platform chosen by organizations seeking sovereign control over their documents and files.

Both systems provide native S3-compatible object storage connectors for secondary capacity tiering and ransomware-proof archiving. However, relying on hyperscalers like AWS S3 for multi-terabyte virtual disk restores (.vbk, .vib) introduces catastrophic egress bandwidth penalties ($0.09/GB) precisely when disaster strikes and you need to restore your data rapidly.

In this guide, we walk through configuring Veeam Scale-Out Backup Repositories (SOBR) with WORM immutability, followed by configuring Nextcloud External and Primary Storage using QuixiCloud M-S3.

---

Part 1: Configuring Veeam Backup & Replication with QuixiCloud M-S3

Veeam leverages S3 object storage within its Scale-Out Backup Repository (SOBR) framework as a "Capacity Tier" for automated offsite tiering and ransomware-proof immutability.

┌─────────────────────────────────┐
│     On-Premise Infrastructure   │
│  • Local Hyper-V / VMware VMs   │
│  • Fast Local Performance Tier  │
└────────────────┬────────────────┘
                 │
                 │ (Automated SOBR Offload via S3 API)
                 ▼
┌─────────────────────────────────┐
│     QuixiCloud M-S3 Vault       │
│  • High-Durability Object Store │
│  • WORM Immutable Object Lock   │
│  • Zero-Egress Recovery Shocks  │
└─────────────────────────────────┘

Step 1: Add a New Object Storage Repository

1. Open the Veeam Backup & Replication Console.
2. Navigate to Backup Infrastructure > Backup Repositories > Click Add Repository.
3. Select Object Storage > Choose S3 Compatible.
4. Specify a descriptive repository name (e.g., QuixiCloud-S3-Capacity-Tier).

Step 2: Configure Service Point & Credentials

• Service Point: https://s3.quixicloud.com
• Region: us-east-1
• Credentials: Click Add and provide your QuixiCloud Access Key and Secret Key.

Step 3: Select Bucket and Enable WORM Immutability

1. Veeam connects to the QuixiCloud endpoint and queries your available buckets. Select your backup bucket (e.g., veeam-disaster-recovery).
2. Create or select a target folder path.
3. Enable Immutability (WORM): Select the checkbox:
   Make recent backups immutable for [30] days.
   • QuixiCloud’s S3 Object Lock compliance engine ensures that even if local administrative credentials are breached by ransomware, the offsite recovery points stored in QuixiCloud cannot be altered, overwritten, or deleted during the retention period.

---

Part 2: Integrating Nextcloud with QuixiCloud S3 Storage

Nextcloud can connect to QuixiCloud M-S3 in two distinct configurations:

1. External Storage App: Mounting specific S3 buckets as collaborative team folders for specific departments.
2. Primary Object Storage: Replacing local disk entirely, allowing Nextcloud to scale to petabytes with zero storage management overhead.

Option A: Mounting S3 via Nextcloud External Storage (Quickest Setup)

1. Log into your Nextcloud administrator console.
2. Navigate to Apps > Enable External Storage Support.
3. Open Administration Settings > External Storage.
4. Click Add Storage > Select Amazon S3:
   • Configuration:
     • Bucket: nextcloud-collaborative-vault
     • Hostname: s3.quixicloud.com
     • Port: 443
     • Region: us-east-1
     • Enable SSL: Checked (True)
     • Enable Path Style: Checked (True)
     • Access Key: Your QuixiCloud Access Key
     • Secret Key: Your QuixiCloud Secret Key
5. Click the checkmark. A green status indicator confirms that your QuixiCloud S3 bucket is active and ready for collaborative file sharing!

---

Option B: Nextcloud Primary Object Storage (config.php)

To configure Nextcloud to store all user files and versions directly on QuixiCloud M-S3, insert the following block into nextcloud/config/config.php:

'objectstore' => [
    'class' => '\\OC\\Files\\ObjectStore\\S3',
    'arguments' => [
        'bucket' => 'nextcloud-primary-storage',
        'autocreate' => false,
        'key'    => 'YOUR_QUIXICLOUD_ACCESS_KEY',
        'secret' => 'YOUR_QUIXICLOUD_SECRET_KEY',
        'hostname' => 's3.quixicloud.com',
        'port' => 443,
        'use_ssl' => true,
        'region' => 'us-east-1',
        'use_path_style' => true,
    ],
],

---

Disaster Recovery Economics: AWS S3 vs QuixiCloud M-S3

The true cost of a backup provider becomes apparent during a full disaster recovery scenario:

| Disaster Recovery Scenario: Restoring 10 TB VM Cluster | AWS S3 Standard | QuixiCloud M-S3 Team Tier | |---|---|---| | Monthly Storage (10 TB) | $230.00 / month | Included in Tier | | Disaster Recovery Restore (10 TB Egress) | $891.00 Egress Penalty! | Included in 2.5× Multiplier! | | WORM Object Lock Support | Yes | Yes (Full S3 Object Lock) | | Predictable Monthly Expense | Variable & Volatile | Flat, Transparent Tier |

Under hyperscaler pricing models, you are penalized with massive bandwidth fees at the exact moment your primary data center suffers a failure. With QuixiCloud, disaster recovery restores are covered by your bundled egress multiplier.

---

Implement 3-2-1 Backup with Ransomware Protection

Adopting the 3-2-1 backup strategy with immutable cloud storage ensures that your organization remains fully insulated from hardware disasters, ransomware extortion, and operational downtime.

Launch your Veeam and Nextcloud S3 storage buckets today at aws.quixicloud.com.