i'm having a little trouble with an AIX 5.2 script that i have written and i was wondering if anyone could please offer me some advice on how to append a savevg backup to a mksysb tape, or more importantly where i'm going wrong? i've been trying to get this to work on and off for about a month with no joy now.
here's a cut down version of my script:
the problem that i am having is that if i run this script i get the following error from the restore commands:
restore: 0511-160 Cannot read the backup media
/dev/rmt0.1: There is an input or output error
with the tape rewound, if i run a restore -Tvqf /dev/rmt0 it lists the files in DEV_VG. this made me think that the tape was rewinding before running the savevg command for some reason.
if i change the backups to use the rmt0 device and manually do all my rewinding and fast forwarding with tctl i get the same errors as the restore command gives me.
if i run a /usr/bin/mksysb -ipX /dev/rmt0 then a restore -Tvqf /dev/rmt0 it lists the files in the rootvg. from what i've read a mksysb should put the files on the 3rd segment of the backup. is this correct?
hi,
i'm having a little trouble with an AIX 5.2 script that i have written and i was wondering if anyone could please offer me some advice on how to append a savevg backup to a mksysb tape, or more importantly where i'm going wrong? i've been trying to get this to work for about a month with no... (2 Replies)
--------------------------------------------------------------------------------
Hello, help me please.
I am trying to create a mksysb bakup using nim. I am geting this error, how to correct it ? :
Command : failed stdout: yes stderr: no... (9 Replies)
Every 3 months we have to do backups (smitth mksysb/lsmksysb + tar) on at least 30 workstations. We have to carry around 2 external tape drives to connect to them. It is a pain to do because it takes at least 3 days to do (evening/night shift) and users sometimes complain that there desk is not put... (1 Reply)
In the several backups we do, we do a "smitty savevg" on about 15 different servers at the same time. Typing all the options on the savg screen is kind of long.
Is it possible to invoke the "smitty savevg" backups as command line (aix 4.2) but using all the options we always enter ?
It would... (1 Reply)
Hello,
I use commands savevg & mksysb to do backups on an AIX server.
Frequently, I have a return code 3.
I would know why, but after searches, I did'nt find.
If somebody know ... Tell me.
Thanks.
emetra (2 Replies)
Other then creating a exclude 'all' file. Is there a way to just create a nim savevg resource that contains just the minimum info to restore a vg. The vg's dirs and files are being backed up. -pete (0 Replies)
Hi All,
I need to plan a downtime and need know how much time is required to take mksysb & rootvg on LTO4. Following are vg informations...
# lsvg -l rootvg
rootvg:
LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINT
hd5 boot 1 2 2 closed/syncd N/A
hd6 paging 64 128 2 open/syncd N/A
hd8... (1 Reply)
Hi All,
I need to take the backup of non-rootvg using savevg utility. I would like to know, if I can take the backup without shutting down the application & database. Is it possible to take the savevg backup safely when users are working on the system ?
Regards. (1 Reply)
I am trying to restore files from savevg.
I used to smit restore and gave the file location.
Savevg is taken to a mount point from San storage and not tape back up.
Can I restore just a directory from savevg?
---------- Post updated at 09:43 PM ---------- Previous update was at 09:42 PM... (1 Reply)
Discussion started by: ElizabethPJ
1 Replies
LEARN ABOUT V7
ht
HT(4) Kernel Interfaces Manual HT(4)NAME
ht - RH-11/TU-16 magtape interface
DESCRIPTION
The files mt0, mt1, ... refer to the DEC RH/TM/TU16 magtape. When opened for reading or writing, the tape is not rewound. When closed,
it is rewound (unless the 0200 bit is on, see below). If the tape was open for writing, a double end-of-file is written. If the tape is
not to be rewound the tape is backspaced to just between the two tapemarks.
A standard tape consists of a series of 512 byte records terminated by a double end-of-file. To the extent possible, the system makes it
possible, if inefficient, to treat the tape like any other file. Seeks have their usual meaning and it is possible to read or write a byte
at a time. Writing in very small units is inadvisable, however, because it tends to create monstrous record gaps.
The last octal digit of the minor device number selects the drive. The middle digit selects a controller. The initial digit is even to
select 800 BPI, odd to select 1600 BPI. If the 0200 bit is on (initial digit 2 or 3), the tape is not rewound on close. Note that the
minor device number has no necessary connection with the file name, and in fact tp(1) turns the short name x into `/dev/mtx'.
The mt files discussed above are useful when it is desired to access the tape in a way compatible with ordinary files. When foreign tapes
are to be dealt with, and especially when long records are to be read or written, the `raw' interface is appropriate. The associated files
may be named rmt0, ..., rmt7, but the same minor-device considerations as for the regular files still apply.
Each read or write call reads or writes the next record on the tape. In the write case the record has the same length as the buffer given.
During a read, the record size is passed back as the number of bytes read, provided it is no greater than the buffer size; if the record is
long, an error is indicated. In raw tape I/O, the buffer must begin on a word boundary and the count must be even. Seeks are ignored. A
zero count is returned when a tape mark is read; another read will fetch the first record of the next tape file.
FILES
/dev/mt?, /dev/rmt?
SEE ALSO tp(1)BUGS
The magtape system is supposed to be able to take 64 drives. Such addressing has never been tried.
Taking a drive off line, or running off the end of tape, while writing have been known to hang the system.
If any non-data error is encountered, it refuses to do anything more until closed. In raw I/O, there should be a way to perform forward
and backward record and file spacing and to write an EOF mark explicitly.
HT(4)