In System Center 2012 Configuration Manager, the ‘Backup Site Server’ maintenance task may fail if the Backup Destination is set to a network share. An example is below:
When this happens, the following errors are logged:
SMSSQLBKUP.LOG
Error: Backup folder \\MachineName\1234 does not exist or backup service does not have permission to access the folder.
Or
SMSBKUP.LOG
Error: Backup folder \\MachineName\1234 does not exist or backup service does not have permission to access the folder.
If you look at the network share you see that the folder does exists and permissions are correct. So why does it fail? To know more, please download Procmon tool from here and capture a trace on both SQL and ConfigMgr site server with following filters while running the backup:
Process Name is ‘SMSSQLBkup.exe’
Process Name is ‘SMSBkup.exe’
Result is ‘BAD NETWORK NAME’
Screenshot:
Once you see the error(s) mentioned at the start of this post, please stop the trace and look at the result.
If you look closely enough at Path column the backup task triggers a CreateFile operation on \\MachineName\123 which doesn’t exist. The correct path is \\MachineName\1234 . It drops the last character ‘4’ and as a result the backup task fails to complete successfully.
At the moment you can choose to use any of the following three workarounds to get the backup task to work.
1. Create a sub-folder under existing folder and configure the backup task accordingly. For example:
2. Save the files on local drive.
3. Create and use a network share on SQL Server instead.
NOTE This issue is schedule to be addressed in Service Pack 1
Additional information on Backup Site Server task can be found here.
Other links of interest:
The System Center 2012 Configuration Manager Survival Guide (en-US): http://social.technet.microsoft.com/wiki/contents/articles/7075.system-center-2012-configuration-manager-survival-guide-en-us.aspx
System Center 2012 Configuration Manager SDK: http://msdn.microsoft.com/library/hh948960.aspx
Karan Rustagi
Get the latest System Center news on Facebook and Twitter:
App-V Team blog: http://blogs.technet.com/appv/
ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
DPM Team blog: http://blogs.technet.com/dpm/
MED-V Team blog: http://blogs.technet.com/medv/
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: http://blogs.technet.com/momteam/
SCVMM Team blog: http://blogs.technet.com/scvmm
Server App-V Team blog: http://blogs.technet.com/b/serverappv
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: http://blogs.technet.com/sus/
The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/