Veeam Backups

Organizations that already use Veeam Backup & Replication can include Files.com data in their existing backup and recovery process. This gives the backup team an independent copy managed through the schedules, retention policies, monitoring, and restore procedures it already uses for other systems.

Files.com provides durable storage and recovery options within the platform. Veeam is an optional addition for organizations with their own requirements for externally managed backups. Files.com's Sync feature can also maintain an external copy without a separate backup application.

Veeam's object storage backup jobs read files through the Files.com S3-Compatible Endpoint and retain recovery data in a separate Veeam backup repository. Files.com is the source of the data in this arrangement; the repository is the destination.

Prerequisites

The integration requires support for S3-compatible unstructured data sources and object storage backup jobs, available in Veeam Backup & Replication 13. Licensing depends on the protected data volume and repository type. Community Edition does not support writing unstructured data backups to an object storage repository.

Veeam's unstructured data backup infrastructure includes a backup proxy to transfer the data, a cache repository for working metadata, and a backup repository for the recovery copies. The backup repository resides outside the Files.com data being protected and needs capacity for the initial copy and retained changes.

The backup proxies need HTTPS access on port 443 to the Files.com hostnames used for file transfers. Any Files.com IP restrictions apply to those servers' connections. Access from the workstation running the Veeam console alone does not provide the proxies with access.

Files.com Credentials and Scope

Veeam authenticates with the Access Key ID and Secret Key from a Files.com S3-compatible API key. The key has Enable use with Inbound S3-compatible clients enabled. An ordinary API key value or Files.com password is not the S3 credential pair.

A dedicated non-administrator user allows the backup's access to be managed separately from individual employees. The user's Read folder permission allows Veeam to list and download the selected files, including accessible subfolders. Each source connection is limited to the site and Workspace available to its credentials.

Restore access is separate from read access. Writing recovered files requires permission to upload at the destination, and replacing existing Files.com files requires Full folder permission. A separate restore account allows the routine backup account to retain read-only access.

S3-Compatible Source Connection

Files.com connects to Veeam as an S3-compatible unstructured data source. This is the S3 Compatible object storage source in Veeam's Unstructured Data inventory. An S3 connection under Backup Repositories serves a different purpose: it identifies storage where Veeam writes its own backup data.

The source's account settings use the following Files.com connection values:

Files.com presents the bucket as default for path-style addressing, or the site's custom subdomain for virtual-hosted-style addressing. The bucket name corresponds to the client's addressing style. Folders appear as prefixes within that bucket. For example, the Files.com folder Finance/Invoices corresponds to Finance/Invoices/.

Veeam's source processing settings associate the source with its backup proxies and cache repository. Backup I/O control governs the load the backup places on the source. A lower setting reduces that load at the cost of a longer backup window.

Object Storage Backup Job

An object storage backup job connects the Files.com source to a Veeam-managed backup repository and defines the schedule and retention policy. The source connection determines what Veeam can access; the job's object selection determines which bucket or prefixes it protects. Path selection identifies Files.com folders. Files.com custom metadata is not exposed as S3 object tags for Veeam's tag filters.

The first run creates a full backup. Later runs back up changed objects incrementally. Source volume, rate of change, and transfer capacity affect the backup window. When the selection includes Remote Server Mounts, the backup also depends on access to that remote storage.

The repository retention period determines how long captured versions remain recoverable. Veeam's object version limits, including limits for deleted objects, can remove versions before that period expires. Secondary copies, archives, and immutability are properties of the Veeam backup configuration and its chosen destination.

Recovery Scope

Veeam creates recovery points from the files it reads during backup runs. It does not import the source's existing object version history. A version overwritten or deleted before Veeam captures it is absent from that job's recovery points. A file created and deleted between runs can be missed entirely.

These backups contain file content. Files.com users, folder permissions, custom metadata, Share Links, and Automations are site configuration and need their own recovery arrangements. S3 bucket policies, ACLs, and tags do not represent that Files.com configuration.

Files.com exposes folders as S3 prefixes, so recovery coverage depends on the files captured beneath each prefix. Recovering those files does not establish that empty folder structure was preserved. Hidden folders and folders outside the backup user's access are omitted from recursive S3 listings.

Restoring Files

Veeam supports recovery of individual objects and their captured versions. The selected recovery point determines which file contents are available.

The Copy to option restores files to a separate location. Its destination is a bucket or prefix on an object storage source registered in Veeam's inventory. This can be a separate Files.com folder with appropriate restore credentials or another compatible object storage location. Recovery to another location also provides access to the backup when the original Files.com site is unavailable.

Restore > Keep restores beside the original with a timestamp suffix. Restore > Overwrite replaces the original content. Restores into Files.com are uploads, so destination folder settings and Automations apply to the recovered files as they do to other uploads.

Backup and Restore Validation

A successful connection establishes access, but recoverability depends on the job capturing the intended files and retaining the required versions. A representative recovery test covers nested folders, large files, and filenames used in the source data. Comparing restored contents or checksums with the originals establishes whether those files were recovered intact.

Changes between runs matter as well. Recovering a deleted file and an earlier copy of an updated file, including a same-size update, tests the job's version retention. A restore to the intended disaster-recovery destination also establishes the recovery time and credentials needed when the original source is unavailable.

Veeam's scheduled backup health checks verify backup integrity. Periodic restore tests provide evidence that the recovery process remains usable after changes to the backup software, source access, or destination.

Troubleshooting

Authentication depends on the S3-compatible key pair, Workspace scope, and access from the backup proxies. S3 endpoint troubleshooting covers connection and credential errors. A connection configured as a Veeam backup repository attempts to write Veeam's backup data to Files.com; a source connection belongs in its Unstructured Data inventory.

Missing files can reflect the job's selected prefixes or filters, hidden folders, or the Files.com user's permissions. Veeam job results and Files.com Inbound S3 Logs provide complementary records of the backup activity. For an unresolved error, the Veeam version, job error, request time, and corresponding log entries give Files.com Support the context to investigate.