"John R. Jackson" wrote:
>
> >What shows an error occurred? ...
>
> By "error" I meant you didn't see all the entries in amrecover that you
> expected to see. There isn't anything in the sendbackup*debug file to
> indicate what went wrong (or even that anything did go wrong). The more
> usefu
>"John R. Jackson" wrote:
> > >What are the complete contents a typical /tmp/amanda/sendbackup*debug
> > >file for one of the failed runs?
> >Don't have any from a failed run. Below is my only sendbackup*debug
> >file, which is from the successful run.
> >
> ># cat /tmp/amanda/sendbackup*debu
"John R. Jackson" wrote:
>
> >... (How do i put a tape back to inactive status? I tried
> >re-labeling, but couldn't: "tape is active".)
>
> Either use "-f" on amlabel, or use amrmtape.
Worked, thx.
> >Don't have any from a failed run. Below is my only sendbackup*debug
> >file, which is from
.net/fom-serve/cache/1.html because calling
them both "FAQ" is confusing.
Though she's more than i can handle at the present, for the future,
thank u for keeping amanda free and well-supported.
george herson
hi. If you're running Linux and want to buy a disaster recovery cdrom
that includes amanda, the book _Linux Problem Solver_ by Brian Ward, No
Starch Press, includes one.
george herson
Nicki Messerschmidt wrote:
>
> Hi folks,
> I'm runnig several Amanda hosts and an Amanda
"John R. Jackson" wrote:
>
> >I got all nine items of my /home/amanda directory archived, unlike when
> >amdump ran it with option --listed-incremental
> >/usr/local/var/amanda/gnutar-lists/dellmachine_home_amanda_0.new. What
> >does this mean?
>
> I don't know what it means yet, except that ta
"John R. Jackson" wrote:
>
> >In a test, i removed the --listed-incremental /usr/amanda_0.new
> >option, and tar archived all my files, just how i like it. Why does
> >Amanda put that option there? ...
>
> Ummm, because that's required to do incremental backups. :-)
>
> >And is it feasib
"John R. Jackson" wrote:
>
> >Is the actual (eg, tar) command used by amdump recorded? Where?
>
> /tmp/amanda/sendsize*debug and /tmp/amanda/sendbackup*debug on the client.
>
> > george
Thanks. I didn't know that because the sendsize*debug files i looked
inside didn't have the tar options b
"John R. Jackson" wrote:
>
> >But I just archived that dir to disk using tar and it got all the files
> >fine.
>
> And did you do it the same way Amanda does, i.e. with all the listed
> incremental type flags it hands to GNU tar? That's where a lot of the
> problems are, not in just basic tar o
"John R. Jackson" wrote:
> >But i have a question as to why, according to a tar on the tape afterwards,
> >only four out of the nine items in the directory to dump were actually
> >backed up. ...
>
> What version of GNU tar are you using? If it's not at least 1.13.17
> (and probably 1.13.19 wo
st and last lines).
> Amanda allows five minutes per disk. If that's not enough, crank up
> the etimeout value in amanda.conf.
>
> >george herson
>
> John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
g result for /home/amanda in
dellmachine response]"
What causes missing results?
My disklist is "dellmachine /home/amanda root-tar".
thx,
george herson
"John R. Jackson" wrote:
> >Thanks for your advice below (setting changerfile) as I am much further
> >
s return
^C'ing out and retrying produces much the same thing. What could be
wrong? I have very simple setup: 1 machine as both client and server, with
1 tape drive with 1 slot. I have just "dellmachine /boot root-tar" in
disklist.
thank you,
george herson
"John R. Jack
reason not to do it this way, besides the security issue of having to load
nfsd on my internet-connected PC?
thx alot,
george herson
"John R. Jackson" wrote:
> >(/usr/adm/amanda/changer-status-clean: No such file or directory):
>
> The Amanda changers now want to store thre
chg-manual:
(/usr/adm/amanda/changer-status-clean: No such file or directory):
rewinding
amlabel: no tape online
# mt -f /dev/nht0 status shows:
IDE-Tape (type code 0) ?
File number=0, block number=0.
mt_resid: 0, mt_erreg: 0x0
mt_dsreg: 0x200, mt_gstat: 0x0
General status bits on (0):
thank u,
george herson
hange to the regular
> expression to tell them apart.
>
> Grumble, mutter, ...
>
> >george herson
>
> John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Ok, thanks.
# mt -f /dev/nht0 status WITHOUT the tape:
/dev/nht0: Input/output error
# mt -f /dev/nht
sid: 0, mt_erreg: 0x0
mt_dsreg: 0x200, mt_gstat: 0x0
General status bits on (0):
-> loaded <>
Might that "(type code 0) ?" indicate a problem?
# cat amlabel.20010501135216.debug shows:
amlabel: debug 1 pid 11047 ruid 507 euid 507 start time Tue May 1 13:52:16
2001
thank you,
geo
wn tape drive type (type code 0)
File number=0, block number=0.
mt_resid: 0, mt_erreg: 0x0
mt_dsreg: 0x200, mt_gstat: 0x0
General status bits on (0):
-> loaded <>
-> rewind /dev/nht0
The tape, drive, and /dev/ht0 are known to work, with tar.
Suggestions? Thanks alot,
george
18 matches
Mail list logo