Backup and Disaster Recovery

This administrator guide is scoped to the File Service databases only:

• file-service/file_data.nsf
• file-service/file_admin.nsf

Back up application data from these databases using Domino-native backup procedures suitable for live NSF data. See HCL Domino: Backing up the Domino server. In containerized deployments, treat containers as ephemeral and back up only the persistent storage locations that hold these NSF files.

In scope for this guide

1. file_data.nsf (user file metadata, folders, share/link/access-request records, upload state).
2. file_admin.nsf (configuration profile, audit logs, delete-user-data requests, storage reports).
3. File Service deployment/configuration artifacts needed to restore this service instance (for example Compose/Kubernetes manifest files and environment configuration used by this service).

Out of scope for this guide

Global Domino platform/system documents and infrastructure-wide backup policies are defined in the broader Domino operations runbook. This includes server-level and cross-product backup scope such as system databases, transaction-log policy, DAOS-wide policy, and other stack components.

Operational requirements

1. Use backup tooling/processes that are safe for live Domino NSF data; avoid ad-hoc file copies of open databases.
2. Keep at least one offsite copy and follow the 3-2-1 principle in your platform runbook.
3. Run periodic restore tests for file_data.nsf and file_admin.nsf to verify recovery procedures.