Full backup won't start

general discussion
1

Hi,

I’m trying to do full backup files of a windows 10 but won’t start. I put traces but only see:

2026-09-25 18:48:31: Sending file “urbackup\www”
2026-09-25 18:48:31: Sending file: urbackup\www/index.htm
2026-09-25 18:48:31: Sending file: urbackup\www/index.htm done
2026-09-25 18:48:32: Sending file “urbackup\www/images/urbackup.png”
2026-09-25 18:48:32: Sending file: urbackup\www/images/urbackup.png
2026-09-25 18:48:32: Sending file: urbackup\www/images/urbackup.png done
2026-09-25 18:48:35: Sending file “urbackup\www/fonts/glyphicons-halflings-regular.woff2”
2026-09-25 18:48:35: Sending file: urbackup\www/fonts/glyphicons-halflings-regular.woff2
2026-09-25 18:48:35: Sending file: urbackup\www/fonts/glyphicons-halflings-regular.woff2 done
2026-09-25 18:48:50: msg=START BACKUP FULL

In client:
2026-09-25 18:56:00: WARNING: Parent directory not found in MFT. Was probably deleted.
2026-09-25 19:00:40: WARNING: Parent of file with FRN 15199648742902108 (Name “003600000008095C575C1330”) with FRN 281474976710685 not found. Searching via MFT as fallback.
2026-09-25 19:00:40: WARNING: Parent directory not found in MFT. Was probably deleted.
2026-09-25 19:00:40: WARNING: Parent of file with FRN 15199648742902108 (Name “003600000008095C575C1330”) with FRN 281474976710685 not found. Searching via MFT as fallback.
2026-09-25 19:00:40: WARNING: Parent directory not found in MFT. Was probably deleted.
2026-09-25 19:00:40: WARNING: Parent of file with FRN 19421773393561842 (Name “00450000000808F2088FE8A2”) with FRN 281474976710685 not found. Searching via MFT as fallback.
2026-09-25 19:00:40: WARNING: Parent directory not found in MFT. Was probably deleted.
2026-09-25 19:00:40: WARNING: Parent of file with FRN 19421773393561842 (Name “00450000000808F2088FE8A2”) with FRN 281474976710685 not found. Searching via MFT as fallback.
2026-09-25 19:00:40: WARNING: Parent directory not found in MFT. Was probably deleted.
2026-09-25 19:05:41: WARNING: Parent of file with FRN 107523441103645055 (Name “017E00000002A97F2CE0E634”) with FRN 281474976710685 not found. Searching via MFT as fallback.
2026-09-25 19:05:41: WARNING: Parent directory not found in MFT. Was probably deleted.
2026-09-25 19:05:41: WARNING: Parent of file with FRN 107523441103645055 (Name “017E00000002A97F2CE0E634”) with FRN 281474976710685 not found. Searching via MFT as fallback.
2026-09-25 19:05:41: WARNING: Parent directory not found in MFT. Was probably deleted.
2026-09-25 19:05:41: WARNING: Parent of file with FRN 41658296553355481 (Name “009400000002B8D934A4BB40”) with FRN 281474976710685 not found. Searching via MFT as fallback.
2026-09-25 19:05:41: WARNING: Parent directory not found in MFT. Was probably deleted.
2026-09-25 19:05:41: WARNING: Parent of file with FRN 41658296553355481 (Name “009400000002B8D934A4BB40”) with FRN 281474976710685 not found. Searching via MFT as fallback.
2026-09-25 19:05:41: WARNING: Parent directory not found in MFT. Was probably deleted.

But can’t see file of output and I check that the backup of files doesn’t starts.
Any help?

2

Those warnings are probably not the problem. They come from the part of the client that keeps watching the NTFS change journal between backups, not from the backup itself. They’re only warnings, and the client carries on. The file names (24 hex characters) look like files in the hidden $Extend\$Deleted folder, where Windows 10 parks files that were deleted while still open, so the client can’t find their parent folder. That’s harmless.

Your log shows the client did receive the start command (msg=START BACKUP FULL). A full file backup then creates a VSS snapshot and indexes the whole drive, which doesn’t show up in the client log at the default log level. So it’s worth checking:

  • Activities page on the server: is there a full file backup for this client, and does it say “Indexing”? On a big drive, indexing can take a while.
  • Logs → Live log for this client on the server: shows what the server is waiting for.
  • If it seems stuck: run vssadmin list writers in an admin command prompt on the client. Any writer that isn’t in the “Stable” state with “No error” can block the snapshot. Restarting the “Volume Shadow Copy” service or rebooting usually clears it.