Incremental backup fail with status code 1
Hello, I have a big problem with my system state incremental backups on two clustered servers ending with status 1, which only the full backup ending with status 0.
Master Server Version 8.1.2 - Windows server 2016
Media Server Verion 8.1.2 - Linux 3.10.0-693.17.1.el7.x86_64
Client Version 8.1.2 - Windows server 2016
I performed the procedures for vss verification and found no failure.
can you help me?
Attached some logs
Thank you very much in advance
The problem is a moving target. It was noted by others that they could address the issue for a short while or a fair while, one to 'n' backup jobs, before the same problem began appearing again but for other so called critical files. If you look back at the link I posted earlier, I did provide a short script to help identify the backup jobs that report a particular error code. So I guess you could write a different script to filter out those jobs with that error code and thus boil down the list of status 1 partial backup jobs down to a list of true partial status 1 that need to be checked / addressed / fixed - but this script would be quite large and complex.
What gets me is... how are we supposed to know whether a missing critical file really is a critical or not... what this whole problem says to me is that I can never again really trust my BMR aware backups of Windows Server 2016... because I can never know whether any one given backup job is really missing something that really is critical. IMO this simply isn't good enough, and customers should not have to put with this - no matter which vendor is the root cause (and IMO, AFAICT, the root cause is Microsoft).
At then end of the day, until Microsoft fix it, then we are all just going to have to accept partial status 1 incremental backups of Windows Server 2016 nodes that include the System_State:. Not nice, AFAICT there's nothing else any of us can do, except keep chasing our tails.
Some options / mitigations / tasks might be :
1) filter those backup from your daily reporting / stats
2) cease taking incremental System_State backups of Windows Server 2016, and instead - for all Windows Server 2016 backup clients - take daily full backups of C: + System_State:
3) simply cease taking incremental backups of System_State: of all Windows Server 2016 nodes
4) add an entry in your IT Service "risk register" that acknowledges the problem / risk
5) regularly test BMR recovery of one or more Windows Server 2016 backup clients
.
Anyone else care to add anything ?
