Month: August 2015

How to move the SMS_[SITESERVER-FQDN] folder and/or smssqlbkup.log file of the SMS_SITE_SQL_BACKUP_[SITESERVER-FQDN] SCCM component and how to fix the latter when it’s broken (SCCM 2012 R2)?

Posted on Updated on

Attention: this blog post has been written based on SCCM 2012 R2, more precisely with SP1. There is a small chance that this article is not completely true for SCCM 2012 R2 without SP1 or even that the content lies quite far from reality in SCCM 2012 non-R2. What is certainly true is this post doesn’t apply for older SCCM versions (2007 and older) for at least a decent amount.

This blog post’s goal is twofold:

  • Describing how to change the location of the SMS_[SITESERVER-FQDN] folder and/or smssqlbkup.log file of the SMS_SITE_SQL_BACKUP_[SITESERVER-FQDN] SCCM component. Please read the paragraph “How to change the location of the SMS_[SITESERVER-FQDN] folder and/or the smssqlbkup.log file?” to deep-dive into this one.
  • Describing how the SMS_SITE_SQL_BACKUP_[SITESERVER-FQDN] component may be broken, what happens then and how to fix it, even if you didn’t try to change the SMS_[SITESERVER-FQDN] folder and/or the smssqlbkup.log file. See the paragraph “What if the SMS_SITE_SQL_BACKUP_[SITESERVER-FQDN] component is broken?” hereunder for that part.

In both cases it may be useful to start with the introduction paragraph “First some background information on SMS_SITE_SQL_BACKUP_[SITESERVER-FQDN] component…” below. In the case of fixing a broken component (the 2nd goal of this post) I also think it’s worth reading the part about changing the location of the SMS_[SITESERVER-FQDN] folder and the smssqlbkup.log file, because it contains some in-depth details which may be useful to understand how to fix a broken SMS_SITE_SQL_BACKUP_[SITESERVER-FQDN] SCCM component.
Read the rest of this entry »

Advertisements