Problem with ontape
Posted in 2009
Topics: Backup & Restore, Server Administration, Platform-Specific Issues
Hello,
Subject: Problem to make a full level 0 backup of my Database with
ontape -s.
I use Informix Dynamic Server Version 7.31 on a Linux Suse 10
distribution.
I want to make a level 0 backup on a tape on Server test4.
Here`s an extract of my onconfig file:
TAPEDEV /dev/st0 #Tape device path
TAPEBLK 128 #Tape block size (Kbytes)
TAPESIZE 20000000 #Maximum amount of data to put on tape (Kbytes)
The Read/Write Permissions for ontape:
-rwsr-sr-x 1 root informix 1330659 Nov 7 16:08 ontape*
When i was trying to run ontape -s -L 0 i receive the following
message after pressing return to continue:
Could not write archive tape.
And then after a few seconds there is an abnormal system hang-up and i
must restart the system.
I tried this on several Linux Suse 10 Servern, with different tapes and
with different tape units.
It`s every time the same problem: I receive the message "could not
write archive tape" and a few moments later the system hang-up.
After this i try to do a remote backup from test1 (another Linux Server
with tihe same IDS and SUSE Version as test4)
to test4 and i adjust the onconfig file like this:
TAPEDEV test4:/dev/st0 #Tape device path
With this configuration it works, but the tape unit is still at the
Linux Suse System (which is here test4).
Why works it when i approach the system remote from remote and why i
receive an system hang-up end when i try the same thing directly on the
Linux Suse Distribution ?
(With tar i can write to tape without any trouble.)
Any suggestion is welcomed.
Heinz
--
WESTFLEISCH eG * Hauptsitz: Brockhoffstr. 11, 48143 Münster
Amtsgericht Münster: Gen.-Reg. 307
Aufsichtsratsvorsitzender: Heinz Westkämper
Vorstand: Dirk Niederstucke, Peter Piekenbrock, Josef Lehmenkühler, Dr.
Bernd Cordes, Dr. Helfried Giesen
Hinweise: Es können nur Mails bis 30 MB empfangen werden.
PowerPoint-Dateien müssen in eine ZIP-Datei gepackt werden.
--------------------------------------------------
Heinz Weitkamp wrote:
> Hello,
>
> Subject: Problem to make a full level 0 backup of my Database with
> ontape -s.>
> I use Informix Dynamic Server Version 7.31 on a Linux Suse 10
> distribution.
> I want to make a level 0 backup on a tape on Server test4.
>
> Here`s an extract of my onconfig file:
> TAPEDEV /dev/st0 #Tape device path
> TAPEBLK 128 #Tape block size (Kbytes)
> TAPESIZE 20000000 #Maximum amount of data to put on tape (Kbytes)>
> The Read/Write Permissions for ontape:
> -rwsr-sr-x 1 root informix 1330659 Nov 7 16:08 ontape*
>
> When i was trying to run ontape -s -L 0 i receive the following
> message after pressing return to continue:
> Could not write archive tape.
>
> And then after a few seconds there is an abnormal system hang-up and i
> must restart the system.
> I tried this on several Linux Suse 10 Servern, with different tapes and
> with different tape units.
> It`s every time the same problem: I receive the message "could not
> write archive tape" and a few moments later the system hang-up.
>
> After this i try to do a remote backup from test1 (another Linux Server
> with tihe same IDS and SUSE Version as test4)
> to test4 and i adjust the onconfig file like this:
>
> TAPEDEV test4:/dev/st0 #Tape device path>
> With this configuration it works, but the tape unit is still at the
> Linux Suse System (which is here test4).
> Why works it when i approach the system remote from remote and why i
> receive an system hang-up end when i try the same thing directly on the
> Linux Suse Distribution ?
>
> (With tar i can write to tape without any trouble.)
>
> Any suggestion is welcomed.
>
> Heinz
>
-rwsr-sr-x 1 root informix 1330659 Nov 7 16:08 ontape*
Why have this sort of permissions?? Apart from the security aspect, it is not like a plain tape device which is what TAPEDEV really
expects.
Try changing the permissions to something that a tape device has :
ls -l /dev/rmt
total 0
crw-rw-rw- 2 bin bin 205 0x013000 Jan 30 2006 0m
crw-rw-rw- 2 bin bin 205 0x013080 May 4 2005 0mb
crw-rw-rw- 2 bin bin 205 0x013040 Mar 25 2008 0mn
crw-rw-rw- 2 bin bin 205 0x0130c0 May 4 2005 0mnb
crw-rw-rw- 2 bin bin 205 0x013000 Jan 30 2006 c1t3d0BEST
crw-rw-rw- 2 bin bin 205 0x013080 May 4 2005 c1t3d0BESTb
crw-rw-rw- 2 bin bin 205 0x013040 Mar 25 2008 c1t3d0BESTn
crw-rw-rw- 2 bin bin 205 0x0130c0 May 4 2005 c1t3d0BESTnb
crw-rw-rw- 1 bin bin 205 0x013001 May 4 2005 c1t3d0DDS
crw-rw-rw- 1 bin bin 205 0x013081 May 4 2005 c1t3d0DDSb
crw-rw-rw- 1 bin bin 205 0x013041 May 4 2005 c1t3d0DDSn
crw-rw-rw- 1 bin bin 205 0x0130c1 May 4 2005 c1t3d0DDSnb
Not sure when you say "System hangs" you mean IDS or Suse.
If it is Suse then ... problem is with Suse.