SCCM ConfigMgr Backup Failed with Error SQL Backup Failed Error Code 2

In some scenarios it's OK to take SCCM Full backup. Do you agree? Generally, I'm not in favour of taking full backup and I agree that we should take only SQL backup.

2
Advertisement

The success of SCCM/ConfigMgr backup will become very critical just before the start the migration process. As I mentioned in the SCCM/ConfigMgr CB migration checklist here, we need to make sure that we should have at least two good copies of SCCM backup. But, SCCM backup failed with error code #2 and the error code 2 refers back to “2 (0x2) =  The system cannot find the file specified.” just few days before my server upgrade.

SQL server is on a remote box and the backup share is accessible from remote SQL server. However, for some reason SQL server was not able to access backup share on the CAS box. The backup has failed because it could complete the following operation “Backup Failed  Error message – ERROR: CopyFile to \\ACNCAS\CASBackup\CASBackup\SiteDBServer failed.” I checked the following logs at remote SQL box as well as on CAS box but everywhere it was giving error code #2.

SMSSQLBKUP.LOG(D:\SMS_ACNCAS.ACN.com\Logs)

ERROR: Failed to backup \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy3\MSSQL\Data\CM_CAS.mdf up to \\ACNCAS\CASBackup\CASBackup\SiteDBServer: ERROR: CopyFile to \\ACNCAS\CASBackup\CASBackup\SiteDBServer failed: [error code: 2, error message: The system cannot find the file specified.].
Failed to copy file(s) \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy3\MSSQL\Data\CM_CAS.mdf.
Error: Backup Failed  for Component - CM_CAS.
Updating the database status to [CM_CAS:Failed;].
Error: BackupComplete failed... ERROR: CopyFile to \\ACNCAS\CASBackup\CASBackup\SiteDBServer failed: [error code: 2, error message: The system cannot find the file specified.]
Sql backup failed. Please see previous errors.

SMSBKUP.LOG

Waiting On SQL Backup for component CM_CAS to complete...
Error: SQL Backup failed for component CM_CAS
ERROR: Failed to backup SQL component CM_CAS. Error = ERROR: CopyFile to \\ACNCAS\CASBackup\CASBackup\SiteDBServer failed: [error code: 2, error message: The system cannot find the file specified.]
Error: Backup Failed  for Component - CASBackup\SiteDBServer\SMSbkSQLSiteDB.dat.
Waiting On SQL Backup task status...
ERROR: SQL Backup task failed. Error message - ERROR: CopyFile to \\ACNCAS\CASBackup\CASBackup\SiteDBServer failed: [error code: 2, error message: The system cannot find the file specified.]
STATMSG: ID=5052 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=ACNCAS.ACN.com SITE=CAS PID=8244 TID=6684 GMTDATE=Wed Mar 08 11:34:12.838 2017 ISTR0="\\WS3SQL05" ISTR1="CM_CAS:Failed;" ISTR2="ERROR: CopyFile to \\ACNCAS\CASBackup\CASBackup\SiteDBServer failed: [error code: 2, error message: The system cannot find the file specified.]" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
Error: SQL Backup failed...
ERROR: SQL Backup task failed. Error message - ERROR: CopyFile to \\ACNCAS\CASBackup\CASBackup\SiteDBServer failed: [error code: 2, error message: The system cannot find the file specified.]
Info: Starting asynchronous BackupComplete...
Info: Asynchronous BackupComplete finished.
ERROR: BackupComplete failed. Error message - ERROR: SQL Backup task failed. Error message - ERROR: CopyFile to \\ACNCAS\CASBackup\CASBackup\SiteDBServer failed: [error code: 2, error message: The system cannot find the file specified.]
SMS_SITE_BACKUP failed. Please see previous errors.
Raised backup task failure alert.
Solution :- SQL Backup failed for SCCM/ConfigMgr
The resolution was very easy and it was a restart of both the servers. Restarted the SQL and CAS servers. After the restart, we have initiated the backup again. Yapee! The SCCM backup worked fine. CAS server was able to complete the backup successfully without any error.
SMSBKUP.LOG
Waiting On SQL Backup for component CM_CAS to complete..
Sleeping for 30 seconds...
Backup Succeeded  for Component - CASBackup\SiteDBServer\SMSbkSQLSiteDB.dat.
 SMSSQLBKUP.LOG
Updating the status to (backup completed)
SQL Backup completed - Wed Mar 08 13:23:43 2017
 Tip:-
Why am I taking full backup not the SQL one? I Agree, in most of the cases, I would suggest to go with SQL backup. In some scenario’s, in case, if we may not have full control on SQL box and you have custom MOF files etc… then, it’s better to take full backup. SQL backup and SCCM/ConfigMgr FULL backup are equally supported by Microsoft/SCCM PG.

2 COMMENTS

  1. hi,
    we have tried the above steps , but it did not helped . Also tried on another share drive but the problem is same

LEAVE A REPLY

Please enter your comment!
Please enter your name here