I have setup a Windows 2008 R2 server and installed SQL Server 2008 application files in C drive. The Windows server is used to store SCCM 2007 DB, it has C, D, E (CD-ROM) and F drives.

The SCCM 2007 DB is located in D drive and I have enabled the "Backup ConfigMgr Site Sever" in SCCM. I checked that the SCCM Site backup was successful. However, I noticed that SCCM have created the F:\SMS_<SCCM Host Name> folder in the server with the following files:

F:\SMS_<SCCM Host Name>\bin\x64\smssqlbkup.exe

F:\SMS_<SCCM Host Name>\Logs\smssqlbkup.lo_

F:\SMS_<SCCM Host Name>\Logs\smssqlbkup.log

F:\SMS_<SCCM Host Name>\srvacct\srvacct.XXX (XXX is the site name)

How do I relocate this F:\SMS_<SCCM Host Name> to C or D drive ? I checked the "Backup ConfigMgr Site Sever" in SCCM and I have not reference F drive at all and I don't know how SCCM will "find out" the F drive by itself.

Hi,

Create a txt file with the name NO_SMS_ON_DRIVE.SMS and place it on each partition you don't want that SCCM creates its folders/files then remove that content under F: and wait the next backup cycle or force it (as you like).

Yes I agree with Gharbi, you will have to create a test file NO_SMS_ON_DRIVE.SMS  and also yo can configure the backup location

I am facing exactly same issue. I have disabled SCCM Backup task. Placed the no_sms_on_drive.sms file in the drive and forcefully deleted the SMS_SiteServerName folder. But after sometime this folder gets re-created.

I need to relocate this file to another drive.

Kindly suggest.

If you run a registry search on the DB server for the location of the log (X:\SMS_(HOSTNAME)), you may find a few entries that did not get changed.  Change them to the desired drive and the log will appear there instead.

For me the two were -- 

HKLM -> SYSTEM -> SMS -> Tracing -> SMS_SITE_SQL_BACKUP_(HOSTNAME) --> TraceFileName

HKLM -> SYSTEM -> ControlSet002 -> SMS_SITE_SQL_BACKUP_(HOSTNAME) --> ImagePath (changing this one is what finally made the log file move)

Hope this helps!

Sean

Hi Wyatt,

You need to stop the "backup service", move the folder to the wished location, change a registry named value for the service (i.e. the value that stores the location for the binaries), change another registry named value (for the location of smssqlbkup.log) and then start the service.

However, at the server side a manual change (again in the registry) must occur too or you will experience Site Status messages complaining about the backup service location being non-existent.

It's a good idea to wrap the whole procedure by a stop of the site component manager service (in the beginning) and a start (at the end).

For a whole explanation about this topic, read my blog post:

https://windoh.wordpress.com/2015/08/06/how-to-move-the-sms_siteserver-fqdn-folder-andor-smssqlbkup-log-file-of-the-sms_site_sql_backup_siteserver-fqdn-sccm-component-and-how-to-fix-the-latter-when-its-broken-sccm-2012-r2/

The post targets SCCM 2012 R2, but I guess most of it is also valid for SCCM 2007.

Ciao!

Padre Pedro

• Edited by PadrePedro 17 hours 53 minutes ago

NO_SMS_ON_DRIVE.SMS only works for the first (clean) install of the "backup component".

If you just delete the SMS_SiteServerName folder (while the service is down of course), SCCM Site Component Manager (running on the site server) detects the "backup component" isn't running. It's trying to start up the service, but of course that fails (because the binaries aren't there anymore). Then SCCM Site Component Manager tries to reinstall the "backup component" and it does that on the location as known by the site server (yes, the site server ALSO contains a path to the "backup component's" location!). That's why the folder gets back, even when you use NO_SMS_ON_DRIVE.SMS files (at this reinstall point those files are ignored).

What you should do, is changing the "backup component's" location as known on the database server (through the registry) after MOVING the folder to the wished, new location. Then you start the backup service again. SCCM Site Component Manager will still see something's wrong, but at the same time it won't attempt a reinstall. To get rid of the messages telling you something is wrong (as it detects the location as known by the site server isn't valid anymore), you should change that site server side location too (again through the registry).

OR

You don't change the location as known on the database server after deleting the folder, but you do change the location as known on the site server. Then SCCM Site Component Manager triggers a reinstall to the new location.

Please read my blog post about this topic for more information and details:

https://windoh.wordpress.com/2015/08/06/how-to-move-the-sms_siteserver-fqdn-folder-andor-smssqlbkup-log-file-of-the-sms_site_sql_backup_siteserver-fqdn-sccm-component-and-how-to-fix-the-latter-when-its-broken-sccm-2012-r2/

Greetings,

Padre Pedro

Hi Wyatt,

You need to stop the "backup service", move the folder to the wished location, change a registry named value for the service (i.e. the value that stores the location for the binaries), change another registry named value (for the location of smssqlbkup.log) and then start the service.

However, at the server side a manual change (again in the registry) must occur too or you will experience Site Status messages complaining about the backup service location being non-existent.

It's a good idea to wrap the whole procedure by a stop of the site component manager service (in the beginning) and a start (at the end).

For a whole explanation about this topic, read my blog post:

https://windoh.wordpress.com/2015/08/06/how-to-move-the-sms_siteserver-fqdn-folder-andor-smssqlbkup-log-file-of-the-sms_site_sql_backup_siteserver-fqdn-sccm-component-and-how-to-fix-the-latter-when-its-broken-sccm-2012-r2/

The post targets SCCM 2012 R2, but I guess most of it is also valid for SCCM 2007.

Ciao!

Padre Pedro

• Edited by PadrePedro Thursday, August 06, 2015 1:49 PM

Hi Wyatt,

You need to stop the "backup service", move the folder to the wished location, change a registry named value for the service (i.e. the value that stores the location for the binaries), change another registry named value (for the location of smssqlbkup.log) and then start the service.

However, at the server side a manual change (again in the registry) must occur too or you will experience Site Status messages complaining about the backup service location being non-existent.

It's a good idea to wrap the whole procedure by a stop of the site component manager service (in the beginning) and a start (at the end).

For a whole explanation about this topic, read my blog post:

https://windoh.wordpress.com/2015/08/06/how-to-move-the-sms_siteserver-fqdn-folder-andor-smssqlbkup-log-file-of-the-sms_site_sql_backup_siteserver-fqdn-sccm-component-and-how-to-fix-the-latter-when-its-broken-sccm-2012-r2/

The post targets SCCM 2012 R2, but I guess most of it is also valid for SCCM 2007.

Ciao!

Padre Pedro

• Edited by PadrePedro Thursday, August 06, 2015 1:49 PM

Hi Wyatt,

You need to stop the "backup service", move the folder to the wished location, change a registry named value for the service (i.e. the value that stores the location for the binaries), change another registry named value (for the location of smssqlbkup.log) and then start the service.

However, at the server side a manual change (again in the registry) must occur too or you will experience Site Status messages complaining about the backup service location being non-existent.

It's a good idea to wrap the whole procedure by a stop of the site component manager service (in the beginning) and a start (at the end).

For a whole explanation about this topic, read my blog post:

https://windoh.wordpress.com/2015/08/06/how-to-move-the-sms_siteserver-fqdn-folder-andor-smssqlbkup-log-file-of-the-sms_site_sql_backup_siteserver-fqdn-sccm-component-and-how-to-fix-the-latter-when-its-broken-sccm-2012-r2/

The post targets SCCM 2012 R2, but I guess most of it is also valid for SCCM 2007.

Ciao!

Padre Pedro

• Edited by PadrePedro Thursday, August 06, 2015 1:49 PM

Hi Wyatt,

You need to stop the "backup service", move the folder to the wished location, change a registry named value for the service (i.e. the value that stores the location for the binaries), change another registry named value (for the location of smssqlbkup.log) and then start the service.

However, at the server side a manual change (again in the registry) must occur too or you will experience Site Status messages complaining about the backup service location being non-existent.

It's a good idea to wrap the whole procedure by a stop of the site component manager service (in the beginning) and a start (at the end).

For a whole explanation about this topic, read my blog post:

https://windoh.wordpress.com/2015/08/06/how-to-move-the-sms_siteserver-fqdn-folder-andor-smssqlbkup-log-file-of-the-sms_site_sql_backup_siteserver-fqdn-sccm-component-and-how-to-fix-the-latter-when-its-broken-sccm-2012-r2/

The post targets SCCM 2012 R2, but I guess most of it is also valid for SCCM 2007.

Ciao!

Padre Pedro

• Edited by PadrePedro Thursday, August 06, 2015 1:49 PM