cancel
Showing results for 
Search instead for 
Did you mean: 

MSSQl 2008 DB backup failed

Former Member
0 Kudos

Dear All,

Recently, we have upgraded our SAP system database from MSSQL 2005 to MSSQL 2008R2.

upgrade was completed successfully and everything is working fine, except online backup.

We have scheduled online backup from DB13 and since last two days we are unableto take complete backup .

below is the programm log:

 

Stepname: CCMS-step 1

Command: declare @exeStmt nvarchar(2000) exec pzp.sap_backup_databases @dbList=

"master,msdb,PZP",@r3Db="PZP",@bDev="FULL_BKP",@expDays= 27,@bkupCheck

sum="N",@jobName= "SAP CCMS Full DB Backup of master,msdb,PZP [2014032

1171610-5-220000]",@bkupType="F",@nativeBkup="N",@exeDate = "201403212

20000",@bkupSim = "N",@format = 0,@init = 0,@bkupDb = "master",@unload

= 0,@exeStmt = @exeStmt OUTPUT

Status: (success)

Message: 3014

Severity: 0

Duration: 0 hours(s) 0 min(s) 0 sec(s)

Last msg: Executed as user: NT AUTHORITY\SYSTEM. DBCC execution completed. If DB

CC printed error messages, contact your system administrator. [SQLSTAT

E 01000] (Message 2528) Processed 376 pages for database 'master', fi

le 'master' on file 1. [SQLSTATE 01000] (Message 4035) Processed 3 pa

ges for database 'master', file 'mastlog' on file 1. [SQLSTATE 01000]

(Message 4035) BACKUP DATABASE successfully processed 379 pages in 0.

099 seconds (29.864 MB/sec). [SQLSTATE 01000] (Message 3014). The ste

p succeeded.

<------------- End of Job Step History --------------->

Stepname: CCMS-step 2

Command: declare @exeStmt nvarchar(2000) exec pzp.sap_verify_backups @nativeBku

p = "N",@bkupSim = "N",@bDev = "FULL_BKP",@bkupChecksum = "N",@exeDate

= "20140321220000",@unload = 0,@dbCnt =1,@exeStmt = @exeStmt OUTPUT

Status: (failure)

Message: 2528

Severity: 16

Duration: 0 hours(s) 0 min(s) 0 sec(s)

Last msg: Executed as user: NT AUTHORITY\SYSTEM. Invalid object name '#sqlstmts'

. [SQLSTATE 42S02] (Error 208) DBCC execution completed. If DBCC prin

ted error messages, contact your system administrator. [SQLSTATE 01000

] (Error 2528). The step failed.

<------------- End of Job Step History --------------->

Please help me in this regards,

We have followed following url but didnt succeded

http://scn.sap.com/thread/3526731

Accepted Solutions (0)

Answers (5)

Answers (5)

KITSA
Explorer
0 Kudos

Hello there

Your step1, exec pzp.sap_backup_databases, is successful, so DB Backup is OK.

Your step2, exec pzp.sap_verify_backups, has the error, which means that the verify fails.

Try to backup without a verify, for a start.

Then run report MSSPROCS again to re-create the stored procedures.

Check that you are on the latest Netweaver SPS, so that the BASIS patches are all there.

Kind regards

Sulis

Matt_Fraser
Active Contributor
0 Kudos

Are you able to get a successful backup using the SQL Server tools, bypassing the SAP tools?  Schedule a backup from the Management Studio and see if that works.  This should tell you whether your problem is with SAP or not.

Best regards,

Matt

Former Member
0 Kudos

Hello,

What version is you SAP ECC system?

Maybe you need update yous support packages in your SAP system or run a sql script for adapt new SQL version to SAP system version.

Best regards

João vagarinho

Sriram2009
Active Contributor
0 Kudos

Hi Amol

Apply latest service package and then check the same

Regards

Sriram

Former Member
0 Kudos

Hello Sriram,

Kernel and Support pack level is already updated

Best Regards,

Amol Dounde

Sriram2009
Active Contributor
0 Kudos

Hi

What is service pack of Ms Sql 2008 R2? apply the latest and check

BR

SS

former_member188883
Active Contributor
0 Kudos

Hi Amol,

It looks like permission problem for the user sapservice<SID>.

Please check if there is any permission change to this user.

Regards,

Deepak Kori

Former Member
0 Kudos

Hello Deepak,

I have made the changes,but not yet succeeded.

Regards,

Amol Dounde

former_member188883
Active Contributor
0 Kudos

Hi Amol,

Can you check the solution in thread http://scn.sap.com/thread/1312182

Looks to be issue with backup volume device name having space.

Hope this helps.

Regards,

Deepak Kori

Former Member
0 Kudos

I have already followed the steps mentioned in the threat but nothing found useful