locked
Why are log files backed up? RRS feed

  • Question

  • My manager wants an explanation for why the log files are backed up when you back up the SCCM site. I am using the backup function in SCCM and it creates the following folder with the logs in them:

    D:\Backup\LOUBackup\SiteServer\SMSServer\Logs

    He wants to know why they can't just be rolled up into the SQL Server DB and only the database backed up. Obviously it's not an option within SCCM to do this and I know there are many processes in SCCM that use the log files. But I would like to understand and explain to him why the log files are going into the backups. Why would they be needed when you restore a site after failure of the server? He doesn't want me to back up SCCM daily because of all these log files that change daily and then have to be backed up by our backup server each day. He doesn't want to run out of space on our backup server. I have Googled this but could not find the answer to why these log files are needed for recovery.

    Wednesday, August 31, 2016 1:15 AM

Answers

  • Side note - You can just backup the SQL database (maintenance plan) and use compression if you like https://stevethompsonmvp.wordpress.com/2013/06/07/sql-server-backup-recommendations-for-configuration-manager/
    • Proposed as answer by Frank Dong Wednesday, August 31, 2016 8:48 AM
    • Marked as answer by Frank Dong Wednesday, September 7, 2016 1:32 PM
    Wednesday, August 31, 2016 1:41 AM

All replies

  • Side note - You can just backup the SQL database (maintenance plan) and use compression if you like https://stevethompsonmvp.wordpress.com/2013/06/07/sql-server-backup-recommendations-for-configuration-manager/
    • Proposed as answer by Frank Dong Wednesday, August 31, 2016 8:48 AM
    • Marked as answer by Frank Dong Wednesday, September 7, 2016 1:32 PM
    Wednesday, August 31, 2016 1:41 AM
  • He doesn't want me to back up SCCM daily because of all these log files that change daily and then have to be backed up by our backup server each day. He doesn't want to run out of space on our backup server.


    It's 2016 and someone cares about less than 200 files which are well below 500MB? I can tell you why the logfiles are backed up: because the product was designed this way.
    Use SQL backup instead as Nick suggested.

    Torsten Meringer | http://www.mssccmfaq.de

    • Proposed as answer by Frank Dong Wednesday, August 31, 2016 8:48 AM
    Wednesday, August 31, 2016 6:06 AM
  • Troubleshooting would be my guess as to why the logs are there. Keep in mend that if you use only SQL back there are still files that need to be backup. Configuration.mof for example.

    Garth Jones

    Blog: http://www.enhansoft.com/blog Old Blog: http://smsug.ca/blogs/garth_jones/default.aspx

    Twitter: @GarthMJ Book: System Center Configuration Manager Reporting Unleased

    Wednesday, August 31, 2016 11:02 AM
  • Yes, he is old fashioned. The log files total 225 MB. It's just that he keeps seeing all these log files listed every day in the backup reports and our backups are growing in size because it keeps historical backups for a period of time (though I have set the retention on these backups so it's not keeping anything older than a month). He wants to know what these log files are used for, and why they are needed for recovery, which I do not understand myself. So until I can answer those questions for him, he won't let me back them up daily. I have been working on trying to zip up the SCCM backup so there will just be 1 file to back up but that is not easy to automate when there are subfolders.
    Wednesday, August 31, 2016 7:18 PM
  • I'd like to just use the SCCM built in backup so I get all the files I need but my manager won't let me do this unless I can explain why each file is needed for recovery. That's what I'm trying to find out here. Why are these files needed for recovery?
    Wednesday, August 31, 2016 7:20 PM
  • I'd like to just use the SCCM built in backup so I get all the files I need but my manager won't let me do this unless I can explain why each file is needed for recovery. That's what I'm trying to find out here. Why are these files needed for recovery?

    They are NOT needed for recovery, they are need for troubleshooting. AKA if your site dies for any reasons the log might tell you why and therefore fix it before / during the restore process. You backup likely have compression turn on and as such they will take almost nothing to store..

    Another options is to edit the afterbackup.bat and zip them as up or delete them.


    Garth Jones

    Blog: http://www.enhansoft.com/blog Old Blog: http://smsug.ca/blogs/garth_jones/default.aspx

    Twitter: @GarthMJ Book: System Center Configuration Manager Reporting Unleased

    • Proposed as answer by Frank Dong Thursday, September 8, 2016 2:15 AM
    Wednesday, August 31, 2016 7:25 PM
  • We are talking about two different log file. CM log files vs SQL (db) log files.

    I assume that mauldlouie is talking about CM log files ( adsysdis.log, adsysdis.lo_, ddm.log, ccm.log, etc). aka text files.


    Garth Jones

    Blog: http://www.enhansoft.com/blog Old Blog: http://smsug.ca/blogs/garth_jones/default.aspx

    Twitter: @GarthMJ Book: System Center Configuration Manager Reporting Unleased

    Wednesday, August 31, 2016 7:29 PM
  • Yes, I am asking about the CM log files, trying to understand why they are needed for recovery.
    Thursday, September 8, 2016 12:17 AM
  • Yes, I am asking about the CM log files, trying to understand why they are needed for recovery.
    They are not needed for recovery. As I said it is for troubleshooting reasons.

    Garth Jones

    Blog: http://www.enhansoft.com/blog Old Blog: http://smsug.ca/blogs/garth_jones/default.aspx

    Twitter: @GarthMJ Book: System Center Configuration Manager Reporting Unleased

    Thursday, September 8, 2016 10:00 AM
  • OK, sorry, I should have said I am trying to understand why they are included in the SCCM backup that the program creates. That's what my manager has been asking me.
    Thursday, September 8, 2016 7:06 PM
  • Its the way the program is designed. It backups the logs for troubleshooting purpose so you reference how all components were functioning before the backup. When you do restore the site and if you have issues, you then have a reference of any issues the site had before the restore. As stated above, they are not required to restore a site, but its there for convenience. 

    You can either take Garth's suggestion and edit the afterbackup.bat to delete them, or zip them up, or use the SQL maintenance guide at the start of the thread.

    Thursday, September 8, 2016 10:29 PM