Open Discussion

Expand all | Collapse all

Identify Systems Not Fully Backed up in SCCM

  • 1.  Identify Systems Not Fully Backed up in SCCM

    Posted 04-09-2020 13:32
    Hello All,

    I'm looking to see if there are others that leverage SCCM in managing the Code42 app and its backup service.  Specifically, I'm looking for a way to identify whether or not a Windows endpoint is fully backed up or not.

    If the system is online, it may just need a "kick start" which could be done by stopping and restarting the CrashPlan service.  I envision SCCM would trigger that if it finds that criteria.

    If this can be done, what identifier / file could SCCM read to find the backup status?  There must be something since if something isn't backed up it talks to the CrashPlan server to tell it.  I have Jamf doing this on the Mac side but have yet to find something on the Windows side.

    Thanks for any input

    Joe de la Cruz
    Desktop Systems Administrator

  • 2.  RE: Identify Systems Not Fully Backed up in SCCM

    Posted 04-13-2020 07:42
    Hi Joe,

    What I would do to look for devices that haven't completed backup is to watch the history log or the backup_files.log. In the history log, you'll see notifications when backup completes, and, if it isn't finished, you'll see a number of files that weren't able to back up. The backup_files.log will have more details about which files specifically weren't able to back up in that attempt. There are more details about this on this page on our support site.

    One could have SCCM run a powershell or batch script to parse the file, and then restart the Code42 service if it doesn't find a completed backup. That said, it's not uncommon to see the occasional file logged as failing to back up even in systems that are successfully completing backup regularly.

    Has anyone else made something to do this sort of monitoring?

    Cecilia Stevens
    Solutions Consultant, Professional Services