I have a decently large Windows fileserver I am trying to back up. Perhaps 24 tb total, but broken down into 4 main data volumes. 2 volumes are approximately 7 tb each, and the other two are aproximately 5 tb each.
All of these volumes will do incremental backups without issue. All will do standard full backups without issue other than taking an incredibly long time to full backup. And 3 of the 4 of these volumes will consistently successfully create synthetic full backups. However, there is one volume or drive that consistently throws a 671 error when trying to do a synthetic full.
I have each of these volumes in their own policy. I'll re-run a non-synthetic standard full backup on the troublesome volume/drive, and though it takes days ( 7+ tb afterall ) , it reports to have run successfully. Then I do an incremental on it. Then try for another synthetic full....and I get another 671.
Before I open up a support case and have it hanging around in their queue while a backup runs for days creating huge logs and looking bad on their "case days open" reports, I thought I'd ask here for ideas.
Anyone have ideas why 3 of 4 volumes on the same server will create synthetic fulls, but one of them will not? The 4 policies I use for the 4 drives/volumes are identical except for the "Backup Selections" wherein I list only the drive/volume.
Master and Media servers are all at NBU 7.5.0.6 as is this Windows client (also at NBU 7.5.0.6)
Thank you.
