%BACKUP-I-BTCROUT messages during disk-to-disk backup

[Rene Heeres]

When doing a disk-to-disk backup I get informational messages several times, these messages are:
%BACKUP-I-BTCROUT, routine Write error detected, output Status, Call RESTORE_ERROR
%BACKUP-I-VALUE_TRACE_D, Decimal trace value 420

HELP/MESSAGE does not give a clue. Can anybody help? What is happening?

[Art Wiens]

Perhaps this explanation from "The Wizard" describes your situation:

http://h71000.www7.hp.com/wizard/wiz_9053.html

HTH,
Art

[Art Wiens]

It's not your exact error message, but it may be a general indication pointing to ODS-5.

[David B Sneddon]

Rene,

The messages are informational and looking at the
source listings tends to indicate that the
BTCROUT messages are trace or debug type output
that should probably not appear and may well just
have been left in due to a conditional build of
that version of BACKUP.
The 420 equates to
%SYSTEM-F-MEDOFL, medium is offline.
At what point in the backups do the messages appear?

Regards
Dave

[Rene Heeres]

The disk I made the backup of is an ODS-2 disk. The disk has Oracle (v. 8.1.7.4) databasefiles on it.

The point at which the messages appeared was somewhere during the backup (about halfway):
.
%BACKUP-S-CREATED, created $1$DGA337:[ORACLE.DB_MSW]MSW_AXAPTA_03.DBS;1
%BACKUP-S-CREATED, created $1$DGA337:[ORACLE.DB_MSW]MSW_AXAPTA_IND_03.DBS;1
%BACKUP-I-BTCROUT, routine Write error detected, output Status, Call RESTORE_ERROR
%BACKUP-I-VALUE_TRACE_D, Decimal trace value 420
%BACKUP-S-CREATED, created $1$DGA337:[ORACLE.DB_MSW]MSW_BHAIC1_1.DBS;1
%BACKUP-S-CREATED, created $1$DGA337:[ORACLE.DB_MSW]MSW_BHAIC1_2.DBS;1
%BACKUP-I-BTCROUT, routine Write error detected, output Status, Call RESTORE_ERROR
%BACKUP-I-VALUE_TRACE_D, Decimal trace value 420
%BACKUP-S-CREATED, created $1$DGA337:[ORACLE.DB_MSW]MSW_BHAIC1_7.DBS;1
.

The backup completed succesfully. At the moment we have the disk mounted and started the database on it and it seems to be working fine. I still wonder what happened.
Could there be a problem with the filestructure, I used ANALYZE/DISK and DFU VERIFY and they both reported no errors?

[David B Sneddon]

Since the disks involved are DGA devices is it
possible that the connection is being temporarily
lost? ... which would result in the MEDOFL status
being returned.
Can you monitor the state of the disks during
the backup to see if they are briefly going into
mount verify?
You should see this if you have another session
with REPLY/ENABLE.

Dave

[Rene Heeres]

Before the disk-to-disk was started we did restart the HSG80-controllerpair on which this disk is defined. There was at least half an hour between the restart of the controllers and the start of the disk-to-disk backup.

Could this restart, although it happened half an hour earlier, have anything to do with the messages that I got? Before starting the backup a SYSMAN io SCSI/Auto was performed to configure the disk and to verify the paths.

What are the chances that the copied data is in someway corrupted? Should I worry about that? The Oracle database on it (just used for querying) started without any problem.

[David B Sneddon]

I am not familiar with the HSG80. Since the backup
does not report any "errors" I would assume that
the backup is OK. I don't think the HSG80 reboot
would cause a problem unless it was done during
the backup, which it wasn't. The best thing to
do would be to have another session active with
REPLY/ENABLE or check the operator log to see if
any of the disks go into mount verify for a short
time.

Dave

[Martin P.J. Zinser]

Hi Renee,

how about the error counter on the target disk,
did this increase maybe? How about the ports on your FC switch, are these all clear?

Greetings, Martin

[Rene Heeres]

There are no errors on the target disk. I did see a path switch on the target disk ($1$dga337:) and also on the source disk ($1$dga760:) did go offline (Mount verify) twice for a very short while (0,2s).

Could this be the cause of the messages?
Does backup have a problem with a disk going into Mount Verify?