Complete backup errors while using db studio 7.7.03-23 and db manager 7.6

[Former Member]

Hi All ,

I am trying to do full backup of MaxDB 7.6.03.09 using database studio 7.7.03-23 and database manager 7.6.

My backup device is tape device - /dev/st0. Its a quantum autoloader device.

I have enabled autoloader check box also in backup template while using database studio 7.7.03-23 .

Once I start backup it throwing following error pop-up message:

-

---

-903 Host file I/O error 3,Data backup failed 1,Backupmedium #1 (/dev/st0) Could not open volume 6,Backup error occured,

Error code 3700 "hostfile_error" 17,Servertask Info: because Error in backup

task occured 10,Job 1 (Backup / Restore Medium Task) [executing] WaitingT149

Result=3700 6,Error in backup task occured, Error code 3700 "hostfile_error

-

---

In case of database manager 7.6. its throwing following error pop-up message:

-24988 SQL error[backup_save "Full_Backup_AIO"DATA RECOVERY];-903,Host file I/O error

Any help / pointers would be highly appreciated.

Is dbstudio and dbmanager doesnt work properly with autoloader device ?

*FYI:- I am using SLES 10. In CLI using OS command tar I am able to interact with quantum autoloader device and no issue with backup of some my private files. Thats means at quantum autoloader device side everything is ok.*

Waiting for your reply folks.

thanks

Vikash G.

[markus_doehr2]

If you use the database itself to backup I would not use /dev/st0 but /dev/nst0. If you use st0 the tape will rewind at the end and will overwrite your current backup.

Check if the use "sdb" has write access to the device (ls -l /dev/nst0)

Markus

[Former Member]

Hi Markus ,

Thanks for this prompt reply.

When I attached autolaoder then it was showing device file - /dev/st0

You mean /dev/st0 and /dev/nst0 are qual ?

BTW at my side user and permissions are as below:

ls -l /dev/st0

crw-rw---- 1 root disk 9, 0 Aug 7 12:06 /dev/st0

ls -l /dev/nst0

crw-rw---- 1 root disk 9, 128 Aug 7 12:06 /dev/nst0

You mean I need to assign user "sdb" write access to device in place of user "root" ?

Please help.

Thanks,

Vikash G.

[markus_doehr2]

> Thanks for this prompt reply.

> When I attached autolaoder then it was showing device file - /dev/st0

> You mean /dev/st0 and /dev/nst0 are qual ?

yes. st0 is the default - but it will, as said, rewind automatically - and you don't want that

> ls -l /dev/st0

> crw-rw---- 1 root disk 9, 0 Aug 7 12:06 /dev/st0

>

> ls -l /dev/nst0

> crw-rw---- 1 root disk 9, 128 Aug 7 12:06 /dev/nst0

>

> You mean I need to assign user "sdb" write access to device in place of user "root" ?

Yes. Either take the ownership via "chown" or give everyone read and write access (or put the user sdb in group "disk").

Markus

[Former Member]

Hi Markus ,

I did chmod 666 for both /dev/st0 and /dev/nst0

#ls -l /dev/nst0

crw-rw-rw- 1 root disk 9, 128 Aug 8 10:53 /dev/nst0

1. ls -l /dev/st0

crw-rw-rw- 1 root disk 9, 0 Aug 8 10:53 /dev/st0

After this When I used device file as /dev/st0 then backup has done but #tar tvf /dev/st0 not showing anything

( may be due to rewind or any other reasons )

But when I use device file as /dev/nst0 then its throwing error:-

-

---

-903 Host file I/O error 3,Data backup failed 1,Backupmedium #1 (/dev/nst0)

Wrong file type 6,Backup error occured, Error code 3700 "hostfile_error"

17,Servertask Info: because Error in backup task occured 10,Job 1 (Backup / Restore Medium Task)

[executing] WaitingT133 Result=3700 6,Error in backup task occured, Error code 3700 "hostfile_error"

-

---

Pls help - any pointers.

Thanks

Vikash.

[markus_doehr2]

Make sure you select device type "tape" (not file or pipe) in your medium definition.

Markus

[Former Member]

Hi Markus ,

Thanks.

My device type is "tape" only not file or pipe.

with /dev/st0 backup happens perfect.

with /dev/nst0 backup starts and throw below error :

-

---

-903 Host file I/O error 3,Data backup failed 1,Backupmedium #1 (/dev/nst0)

Wrong file type 6,Backup error occured, Error code 3700 "hostfile_error"

17,Servertask Info: because Error in backup task occured 10,Job 1 (Backup / Restore Medium Task)

[executing] WaitingT133 Result=3700 6,Error in backup task occured, Error code 3700 "hostfile_error"

-

---

Any other reason?

[markus_doehr2]

This is really interesting... I must admit I have no idea...

Markus

[Former Member]

Hi Markus,

Okay,I like it.

What do you say about using dbstudio to take backup on autoloader tape device?

Is it really works or just there one checkbox is there for show.

[Melanie]

Hello!

Actually we do not support backups to norewind tapes. I assume that the error message in knldiag also states that.

The reason why we only support backups to rewind tapes is that a lot of customers had trouble with their norewind tape drivers

which actually did rewind at the end of the backup - and therefore the customers lost their backups.

If you expect the tape to rewind at the end of the backup you can make sure that you change the tape after the backup was created.

Best regards,

Melanie

[Former Member]

Thank you very much Melanie.

It make sense . hmmm ok.

although you have clarfied my doubt but one more help I require.

my backup template is :

name - Full_backup

Backup type - COMPLETE DATA

Device Type - TAPE

Backup Tool - NONE

Device/File - /dev/st0

Size - 819200 MB ( my LTO3 tape size is 800GB )

Overwrite - yes

Block size - 64

autoloader - yes

OS command -

-

---

I started backup as par above template with and without OS command ( tar tvf /dev/st0 ) but no difference I have noticed once backup done even on gui as well as on DBM CLI mode.

major prob- if I run #tar tvf /dev/st0 on linux command prompt after backup done message then it doesnt show contents of tape.:-(

Backup really did or not .???? pls help . where I am wrong.

#mt -f /dev/st0 status works well and below output is :

drive type = Generic SCSI-2 tape

drive status = 1140851200

sense key error = 0

residue count = 0

file number = 0

block number = 0

Tape block size 512 bytes. Density code 0x44 (unknown).

Soft error count since last status=0

General status bits on (41010000):

BOT ONLINE IM_REP_EN

#

I would be really thankful to you Melanie.

Any pointers pls.

Regards,

Vikash G.

[Melanie]

Hello Vikash,

after you created the backup with DBMCLI or DBMGUI or Database Studio, please check with the following command, if you can access the backup:

dbmcli -d <db_name> -u <user>,<password>

> service_connect

> recover_check <medium_name> DATA

> service_release

Does this work?

Regards,

Melanie

[markus_doehr2]

Hi Melanie,

that´s an interesting statement because at the 7.2/7.3/7.4 times we always used no-rewind tapes to do backups... We now use an external backup software but it worked without much problems with those "old" versions.

Good to know that it´s no more supported (or not yet).

Markus

[Melanie]

Hello Markus,

yes, in these old versions, it was still supported.

Now the kernel returns an error message if a norewind tape is detected.

Best regards,

Melanie

[Former Member]

Hi Melanie ,

Not able to open service session so can not check backup also.

./dbmcli on AIO>service_connect

ERR

-24994,ERR_RTE: Runtime environment error

1,Database .M760309 already started (OS error code 11000)

---

./dbmcli on AIO>recover_check Full_Backup_AIO DATA

ERR

-24933,ERR_NOSERVICESESSION: No service session active

[Melanie]

Hello,

we checked file dbm.prt and found the following entries:

2008-08-11 11:58:33 0x000043da INF 283 DBMSrv command recover_check Full_Backup_AIO

...

2008-08-11 12:18:44 0x000043da ERR -24811 DBMSrv ERR_CONNLOST: connection to client lost (error code 10)

Maybe the first recover_check command was canceled and this might have lead to the not stopped service database.

In the meantime the server was rebooted - so now the service database is not running anymore and the

service_connect command did work.

So the question right now is: could you execute the recover_check successfully now?

Could the backup be accessed?

Best regards,

Melanie

[Former Member]

Yes Melanie Handreck .

It works. Thanks.