Hi!
I can't find out why amdump report contains only zeros.
I read some docs, amcheck says "0 problems found",
and amdump itself seems to be working. But nothing
is backed up.
Here is amdump report:
--
Begin forwarded message:
Date: Thu, 10 Jul 2003 16:34:31 +0400 (MSD)
From: [EMAIL PROTECTED] (
Title: 다임클럽 소식
--- 신용카드 연체의 모든것!! ---
신용사회의 척도가 되는 신용카드
사용하실땐 삶의 여유와 풍요로움을 제공 합니다
그러나 무분별한 카드 사용으로 지금은 어떻습니까?
당사는 강남에 위치하구 있습니다
요즘같은 신용사회에 카드연체 한두번 안 당해본 사람 없을 겁니다.
카드연체 되셨다구 넘 고민하지 마시구요
무언가 자꾸 고민하다보면
몸과 마음이 모두 힘들어 집니다
혼자서만 힘들어 하지 마시구요
전화 주십시
Since I have to do a "hot backup" on my Oracle database. I just want to
know if I can do this in Amanda.
1. Bacup / directory
2. Run shell script to switch Oracle into backup mode
3. Backup /d1 directory
4. Run shell script to switch Oracle back into normal.
5. Backup /d2 directory
What do I have
I figured out the problem, I was using the SCSI tapetype instead of the
IDE for the STT8000A. Thanks for the fast response Paul and redirecting
my focus on the tape drive, instead of gzip.
What it should be for IDE:
define tapetype STT8000A {
comment "STT8000A Tape Device"
length 3850 mby
Paul Bijnens wrote:
bao wrote:
Recovery works, but rewinding the "tapes" gives unpleasant error
messages as follows:
DailySet4/data/1.server._home.1 rewind failed: Inappropriate
ioctl for device
rewind with what command? There is a "ammt" that does the right
thing for file driver pseudo
Marc Mengel wrote:
bao wrote:
Hi everyone,
It makes sense that before recovering from a real tape, the tape has
to be rewound.
But for backup to disk (tapeless), the "tape" is just a file on hard
disk, why does amanda
require it to be rewound??
Recovery works, but rewinding the "tapes" give
bao wrote:
Recovery works, but rewinding the "tapes" gives unpleasant error
messages as follows:
DailySet4/data/1.server._home.1 rewind failed: Inappropriate ioctl
for device
rewind with what command? There is a "ammt" that does the right
thing for file driver pseudo tapes.
bao wrote:
Hi everyone,
It makes sense that before recovering from a real tape, the tape has to
be rewound.
But for backup to disk (tapeless), the "tape" is just a file on hard
disk, why does amanda
require it to be rewound??
Recovery works, but rewinding the "tapes" gives unpleasant error
mes
Paul Bijnens wrote:
>
> C. Wilson wrote:
> >
> > amrestore: 0: skipping start of tape: date 20030709 label VOL02
> > amrestore: 1: restoring plate.tech.net._.20030709.0
> >
> > gzip: stdin: not in gzip format
> > Error 32 (Broken pipe) offset 26624+26624, wrote 0
> > amrestore: pipe reader has
Paul Bijnens <[EMAIL PROTECTED]> writes:
> The fake tapedev is still needed, or the other runs of amdump during
> the week would use the tapedev. So your friday cronjob becomes:
>
>ln -s /dev/rmt/0n /dev/fridaytape; amdump Conf; rm /dev/fridaytape
I'm using a changer though and it complains.
C. Wilson wrote:
amrestore: 0: skipping start of tape: date 20030709 label VOL02
amrestore: 1: restoring plate.tech.net._.20030709.0
gzip: stdin: not in gzip format
Error 32 (Broken pipe) offset 26624+26624, wrote 0
amrestore: pipe reader has quit in middle of file.
amidxtaped: time 12.741: amr
First, let me start by saying I don't have much Admin. experience with
Linux. I offered to help a friend get Amanda running on his Linux box
(RedHat 7.2), since I installed it on my Solaris 8 servers without any
problems.
I installed version 2.4.4 and got it configured as a server without any
prob
Albert Hopkins wrote:
I am running amanda-2.4.2p2-4 and and I have a script that does a
amdump $CONF || exit 1
But it appears that amdump always returns status 0. Is there a
(scriptable) way to determine if a dump completed successfully? What I
want to know specifically is if the dumps went to
Hi ALL. Latest (stupid) question:
In getting programs together (using amanda-2.4.4p1) I was unable to get it to work.
The only way my "crack"ed programmer was able to help me get it to compile was to
comment out the
version.info function, which he said was not allocated as external.
Did this:
On Thu, 2003-07-10 at 12:27, Albert Hopkins wrote:
> I am running amanda-2.4.2p2-4 and and I have a script that does a
>
> amdump $CONF || exit 1
>
> But it appears that amdump always returns status 0. Is there a
> (scriptable) way to determine if a dump completed successfully? What I
as root:
I am running amanda-2.4.2p2-4 and and I have a script that does a
amdump $CONF || exit 1
But it appears that amdump always returns status 0. Is there a
(scriptable) way to determine if a dump completed successfully? What I
want to know specifically is if the dumps went to tape or if they went
Hi everyone,
It makes sense that before recovering from a real tape, the tape has to
be rewound.
But for backup to disk (tapeless), the "tape" is just a file on hard
disk, why does amanda
require it to be rewound??
Recovery works, but rewinding the "tapes" gives unpleasant error
messages as fo
Now that I know the date they want to see the database from, I've tried
(twice) to amrestore the files in a safe location, but with no joy.
After setting the host/disk/path/date to restore, I get the following
from amrestore:
---
amrecover> extract
Extracting files using tape drive /dev/nst0 on h
Paul Bijnens wrote:
H.Caglar Bilir wrote:
the problem is, how can i trace this error. i looked at the x
machines' /tmp/amanda directory and found a core file dated as just
after sendsize file and before amandad file. the output on amandad
file is as follows:
I have no recent experience with
H.Caglar Bilir wrote:
the problem is, how can i trace this error. i looked at the x machines'
/tmp/amanda directory and found a core file dated as just after sendsize
file and before amandad file. the output on amandad file is as follows:
I have no recent experience with AIX. Try "file core". S
hello,
we are running amanda for our daily backups on nearly 40 machines.
tape and index server is the same machine and runs 2.4.2p2.
i changed one of the client-only machines from 2.4.2.p2 to 2.4.4p1 and
problems begin. the error is
FAILURE AND STRANGE DUMP SUMMARY:
x hd2 lev 0 FAILED [mis
For a year I've been successfully using an internal HP SureStore 24
DDS-3 drive to back up 5 production servers for Dept. of Ag. It's been
totally reliable.
And for about six months I've been using an internal Seagate DAT
9SP40-000 to back up 3 production servers. It's been reliable as well.
mike
Vincent GRENET wrote:
It clutters amanda report, so I want to get rid of it.
My amanda is 2.4.2p2, my samba is 2.0.7.
I believe samba 2.0.7 did not honour the '-d 0' (debug level 0)
flag correctly. Upgrade to a recent version. You should do it
anyway because there are numerous bugfixes and securit
Hi All.
For all windows shares I back up I get the following, though The backup
works fine:
FAILED AND STRANGE DUMP DETAILS:
/-- localhost //vincent/maintenance lev 1 STRANGE
sendbackup: start [localhost://vincent/maintenance level 1]
sendbackup: info BACKUP=/usr/bin/smbclient
sendbackup: info
Steven J. Backus wrote:
Yes but when your tapes cost $100 each and you only have 14, is
there a better way to do it?
Probably not. If the value of the data is not that much, than
maybe it's not a problem let amanda backup to holdingdisk one
more day either, and do the flush on monday or so?
The au
25 matches
Mail list logo