FILESTREAM database recovery
FILESTREAM stores varbinary(max) content in an NTFS container while SQL Server maintains transactional relationships and metadata in the database. Copying the MDF without the container—or copying container files outside database consistency—can separate rows from their binary content.
Understand the symptom
The container is not an ordinary user folder. Internal paths and identifiers connect stored blobs to table rows, while the transaction log coordinates creation, modification, and garbage collection. Recovery must align relational metadata, logs, and container contents at a compatible point in time.
What you may see
The MDF references a FILESTREAM filegroup path that is unavailable.
Relational metadata is readable while corresponding stream files are missing or corrupt.
Files may not match the checkpoint and log state of the copied database.
External changes bypass SQL Server's transactional management.
Protect the source
Container names and hierarchy are managed by SQL Server.
Consistency repair may prioritize database structure over retaining every damaged stream.
New transactions can change container and log state.
Do this now
Prevent writes, cleanup, backups, and maintenance on the affected database.
Preserve MDF, NDF, LDF, FILESTREAM containers, logs, configuration, and backups.
Keep names, hierarchy, timestamps, permissions, and volume context intact.
Save error logs, DBCC output without repair, server version, paths, and last known good time.
NEPFOSYS process
NEPFOSYS maps database files, filegroups, logs, container roots, and available backups.
Database and FILESTREAM state are aligned on protected copies using compatible SQL Server context.
Rows and requested binary objects are checked together rather than as disconnected files.
A clear next step
Start a case with the exact symptoms, incident timeline, prior attempts, encryption details, and the files that matter most. NEPFOSYS will route the case to the appropriate DFW intake or nationwide mail-in path.
Start with a case reviewQuestions, answered
Individual files may be visible, but names and transaction relationships are managed by SQL Server and may not identify their rows.
The database can remain incomplete or fail because the filegroup is part of its defined storage.
Not on the only copy. Repair can remove inconsistent references or data to restore structural consistency.
DFW local · Nationwide mail-in