Backup in progress over extraordinary long time

[Former Member]

Dear All,

We have two version of SAP ECC 6.0 have SQL2005 as database and ECC 4.6 having SQL 2000 as database.

Now I have scheduled my backup for ECC4.6 development,but it is not taking place.When I checked the log it is giving no history information found.Might still be running.

When I see in DB12 I found the following

Last successful backups :

Full R/3 backup 29 Jun 2008 04:17:08

Differential R/3 backup Not found during past 1 month

Transaction log backup 30 Jun 2008 10:32:22

Full master backup 27 May 2008 02:21:36

Full MSDB backup 27 May 2008 02:25:43

Normally it takes 10-11 to take full backup via cartridge.But why this job is running since so long.Can anyone suggest what went wrong.

Regards,

Ashutosh

[JPReyes · Accepted solution]

You should be able to read the backup logs even if the backup is still active in DB13... so go and have a look....

You can also check this from the SQL enterprise manager.

Regards

Juan

[Former Member · Accepted solution]

Dear Juan,

This is the log I am getting.can you suggest what can be done.

Date Source Message

2008-06-28 15:41:47.00 server Microsoft SQL Server 2000 - 8.00.760 (Intel X86) ...

2008-06-28 15:41:47.03 server Logging SQL Server messages in file 'h:\MSSQL\log\ERRORLOG'.

2008-06-28 15:41:47.03 server Server Process ID is 888.

2008-06-28 15:41:47.03 server All rights reserved.

2008-06-28 15:41:47.03 server Copyright (C) 1988-2002 Microsoft Corporation.

2008-06-28 15:41:47.07 server SQL Server is starting at priority class 'normal'(1 CPU detected).

2008-06-28 15:41:48.17 server SQL Server configured for thread mode processing.

2008-06-28 15:41:48.17 server Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.

2008-06-28 15:41:48.67 server Attempting to initialize Distributed Transaction Coordinator.

2008-06-28 15:41:51.15 server Failed to obtain TransactionDispenserInterface: Result Code = 0x8004d01b

2008-06-28 15:41:51.28 spid3 Starting up database 'master'.

2008-06-28 15:41:52.35 spid3 Recovery is checkpointing database 'master' (1)

2008-06-28 15:41:52.35 spid3 0 transactions rolled back in database 'master' (1).

2008-06-28 15:41:52.67 spid5 Starting up database 'model'.

2008-06-28 15:41:52.67 server Using 'SSNETLIB.DLL' version '8.0.766'.

2008-06-28 15:41:52.67 spid3 Server name is 'SAPSERVER'.

2008-06-28 15:41:52.79 spid9 Starting up database 'pubs'.

2008-06-28 15:41:52.79 spid8 Starting up database 'msdb'.

2008-06-28 15:41:52.81 spid11 Starting up database 'test'.

2008-06-28 15:41:52.81 spid10 Starting up database 'Northwind'.

2008-06-28 15:41:53.14 server SQL server listening on 127.0.0.1: 1433.

2008-06-28 15:41:53.14 server SQL server listening on 10.1.1.27: 1433.

2008-06-28 15:41:53.25 spid5 Clearing tempdb database.

2008-06-28 15:41:53.50 spid10 Starting up database 'DEV'.

2008-06-28 15:41:56.37 spid8 1003 transactions rolled forward in database 'msdb' (4).

2008-06-28 15:41:56.67 spid8 0 transactions rolled back in database 'msdb' (4).

2008-06-28 15:41:56.73 spid8 Recovery is checkpointing database 'msdb' (4)

2008-06-28 15:41:57.06 server SQL Server is ready for client connections

2008-06-28 15:41:57.06 server SQL server listening on TCP, Shared Memory, Named Pipes.

2008-06-28 15:41:57.29 spid5 Starting up database 'tempdb'.

2008-06-28 15:42:47.31 spid10 343 transactions rolled forward in database 'DEV' (8).

2008-06-28 15:42:47.73 spid10 0 transactions rolled back in database 'DEV' (8).

2008-06-28 15:42:47.76 spid10 Recovery is checkpointing database 'DEV' (8)

2008-06-28 15:42:48.03 spid3 SQL global counter collection task is created.

2008-06-28 15:42:48.03 spid3 Recovery complete.

2008-06-28 15:42:52.62 spid51 Using 'xpsqlbot.dll' version '2000.80.194' to execute extended stored procedure

2008-06-28 15:43:43.93 spid53 Using 'xpstar.dll' version '2000.80.760' to execute extended stored procedure '

2008-06-28 15:46:48.87 backup BACKUP failed to complete the command BACKUP LOG [DEV] TO DISK = N'G:\tlog bac

2008-06-28 15:46:48.87 spid53 Internal I/O request 0x46E4B618: Op: Write, pBuffer: 0x10AF0000, Size: 983040,

2008-06-28 15:46:48.87 spid53 BackupMedium::ReportIoError: write failure on backup device 'G:\tlog backup\280

2008-06-28 15:54:14.20 backup BACKUP failed to complete the command BACKUP LOG [DEV] TO DISK = N'H:\tlog bac

2008-06-28 15:54:14.20 spid53 BackupDiskFile::CreateMedia: Backup device 'H:\tlog backup\28June.bak' failed t

2008-06-28 16:21:35.89 backup Log backed up: Database: DEV, creation date(time): 2006/04/21(11:21:11), first

2008-06-28 16:25:30.98 spid87 Using 'xplog70.dll' version '2000.80.760' to execute extended stored procedure

2008-06-29 00:02:54.82 spid101 Tape 'CD19S' (Family ID: 0x2728ff2e, sequence 1) mounted on tape drive 'TAPE1'.

2008-06-29 04:17:08.71 spid101 Tape 'CD19S' (Family ID: 0x2728ff2e, sequence 1) dismounted from tape drive 'TA

2008-06-29 04:17:12.50 backup Database backed up: Database: DEV, creation date(time): 2006/04/21(11:21:11), p

2008-06-29 04:23:30.04 spid100 Tape 'CD19S' (Family ID: 0x2728ff2e, sequence 1) mounted on tape drive 'TAPE1'.

2008-06-29 07:35:39.32 spid100 Tape 'CD19S' (Family ID: 0x2728ff2e, sequence 1) dismounted from tape drive 'TA

2008-06-29 07:35:55.28 backup BACKUP failed to complete the command BACKUP DATABASE [DEV] TO TAPE1 WITH NOIN

2008-06-29 07:36:47.59 spid100 BackupTapeFile::RequestDurable: WriteTapemark failure on backup device '
.\Tap

2008-06-30 10:32:23.21 backup Log backed up: Database: DEV, creation date(time): 2006/04/21(11:21:11), first

Regards,

Ashutosh

Edited by: ashutosh singh on Jun 30, 2008 2:03 PM

Edited by: ashutosh singh on Jun 30, 2008 2:09 PM

[Former Member]

hi

please give full message especially for this line (taken from log given by you) :

> 2008-06-29 07:36:47.59 spid100 BackupTapeFile::RequestDurable: WriteTapemark failure on backup device '
.\Tap

i think the phrase after that will help us to identify the error.

possible error maybe seen:

- cyclic redundancy check (CRC) on tape

- media is write protected

etc.

rgds,

Alfonsus Guritno

[Former Member]

Hi,

You were right.There is some problem with the cartridge device itself.

Thanks to you and Juan.

Regards,

Ashutosh

[Former Member]

Thread assumed closed.