Hi Stefan et al,...
...and at first, thanks for all the input - much appreciated! :)
On Tue, 9 Mar 2004 11:17:26 +0100
Stefan G. Weichinger [EMAIL PROTECTED] wrote:
Wrong syntax there ...
Doesn't amcheck complain ??
Not really, everything seems to be fine, though I made some
Hi
I am trying to get amanda backup from windows machines up and running,
currently without any success:
I have tried three hosts two windows machines and one unix box and both
windows boxes fail.
The log of amcheck -c looks like this:
Amanda Backup Client Hosts Check
Sorry, for this non-amanda question:
Does anybody know if there is a good RedHat 9 users mail-list
Bill
On Thu, 11 Mar 2004 at 1:40pm, Tim Krieglstein wrote
The log of amcheck -c looks like this:
Amanda Backup Client Hosts Check
WARNING: snap1: selfcheck request timed out. Host down?
WARNING: wins4: selfcheck request timed out. Host down?
Client check: 3
On Thu, 11 Mar 2004 at 8:04am, Bill Clery wrote
Sorry, for this non-amanda question:
Does anybody know if there is a good RedHat 9 users mail-list
https://www.redhat.com/mailman/listinfo/redhat-list/
--
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University
What are the files needed for a Disaster Recovery on the backup server??
Thanks in Advance...
Todd E. Zenker
CNE-GSFC
NASA Goddard Space Flight Center
Raytheon
Mailstop 200.1
http://cne.gsfc.nasa.gov
https://webdrive.gsfc.nasa.gov
On Thu, 11 Mar 2004 at 10:43am, todd zenker wrote
What are the files needed for a Disaster Recovery on the backup server??
I think what you mean is what files do you need in order to save the
complete current state and history of the backups, although I'm guessing
as your request was overly
Thanks Joshua.
I figured that is what is needed in order to recover my backup server. I'm
familiar with Tivoli Disaster Recovery.
Thanks again.
At 11:01 AM 3/11/2004, Joshua Baker-LePain wrote:
On Thu, 11 Mar 2004 at 10:43am, todd zenker wrote
What are the files needed for a Disaster
Hi Joshua
The client in your disklist (the first column) for 'doze boxes backed up
via samba needs to be a *nix box with smbclient installed. When amanda
contacts the *nix box, that box will then initiate the smbclient
connection to the 'doze box.
Thanks for the hint. It did the trick.
.:-)
here's my relevant configuration on amanda.conf:
dumpcycle 7
daysrunspercycle 5
tapecycle 6 tapes
runtapes 1
tpchanger chg-disk
tapedev file:/amandavtapes (this is a entire disk)
my virtual tapes are: (amtape daily show)
slot 2: date 20040311 label daily2
slot 3: date 20040311 label daily3
slot
When I run amcheck Diaria I get this message:
amcheck-server: could not get the changer info: badly formed result from charge: "YPBINDPROC_DOMAIN: Domain not bound"
And I can´t label de tapes with amlabel Diaria Diaria01 slot 1
...
The tape changer I use is "/usr/local/libexec/chg-disk"
20040311 label daily2
slot 3: date 20040311 label daily3
slot 4: date 20040311 label daily4
slot 5: date 20040311 label daily5
slot 6: date 20040310 label daily6
slot 1: date 20040311 label daily1
thx,
Sergio
--
Frank Smith [EMAIL PROTECTED]
Sr
Joshua Baker-LePain wrote:
I think what you mean is what files do you need in order to save the
complete current state and history of the backups, although I'm guessing
as your request was overly terse. If that's right, you need:
the config dirs (where your amanda.confs are)
the infofile dirs
when recovering a file/folder?
just to clarify, I'm just trying to find the best way to have 1 yr of
backup.
Frank
my virtual tapes are: (amtape daily show)
slot 2: date 20040311 label daily2
slot 3: date 20040311 label daily3
slot 4: date 20040311 label daily4
slot 5: date
I'm reading some somewhat large (14-18GB) images off of AIT3 tapes, and
it's taking *forever*. Some crude calculations show it coming off the
tape at around 80 KB/s, whereas it was written out at 11701.6 KB/s. The
tapes were written in variable block size mode. What's the best way to
read
Joshua Baker-LePain wrote:
I'm reading some somewhat large (14-18GB) images off of AIT3 tapes, and
it's taking *forever*. Some crude calculations show it coming off the
tape at around 80 KB/s, whereas it was written out at 11701.6 KB/s. The
tapes were written in variable block size mode.
On Thu, 11 Mar 2004 at 2:21pm, Jonathan Dill wrote
I would try amrestore -c to just dump the image off the tape, and then
do the uncompress and extraction separately, but you will need enough
disk space to do it. Worst case, you could try amrestore -r and use
dd bs=32k skip=1 if=dump-file
--On Thursday, March 11, 2004 2:30 PM -0500 Joshua Baker-LePain
[EMAIL PROTECTED] wrote:
[snip]
Maybe I should try dd with bs=16M? But will that pad the output file
with an unacceptable-to-tar chunk at the end since the tapefile is
unlikely to be an exact multiple of 16M?
In my experience,
Hmm. Check also mt status to make sure the drive thinks that the
blocksize is 0 if not change it with mt blksize. The files will be
perfectly fine with bs=16M. gzip and/or tar will probably give a warning
bitching about the nulls at the end, but it won't have any effect on the
restore, the
On Thu, 11 Mar 2004 at 8:34pm, Gerhard den Hollander wrote
I am assuming the disk you are writing to, the machine the tape drive is
attached to and the machine on which the amrestore is running are all the
same ?
Yep.
If not, your network might be the bottleneck.
I was originally doing
On Thu, 11 Mar 2004 at 2:52pm, Jonathan Dill wrote
Hmm. Check also mt status to make sure the drive thinks that the
blocksize is 0 if not change it with mt blksize. The files will be
perfectly fine with bs=16M. gzip and/or tar will probably give a warning
bitching about the nulls at the
On Thu, Mar 11, 2004 at 01:54:19PM -0500, Sergio Pereira wrote:
On Thu, 2004-03-11 at 12:11, Frank Smith wrote:
--On Thursday, March 11, 2004 11:46:16 -0500 Sergio Pereira [EMAIL PROTECTED]
wrote:
Hi list,
I'm starting to play win amanda (2.4.4p2) on rh9 and using external hard
Have you taken a look around in /proc/scsi? /proc/scsi/scsi should give
you some basic information, and the subdir for your driver should give
more details, such as what transfer rate the drive is negotatiated at,
for example /proc/scsi/aic7xxx/0 for an Adaptec 2940 series. Perhaps
there was
On Thu, Mar 11, 2004 at 03:29:23PM -0500, Joshua Baker-LePain wrote:
But 4M works. ?? And to add insult to injury, that's going at about
70K/s.
What about our old oft occuring observations on scsi devices,
Writing through that cable uses different wires than reading.
--
Jon H.
On Thu, 11 Mar 2004 at 4:08pm, Jon LaBadie wrote
On Thu, Mar 11, 2004 at 03:29:23PM -0500, Joshua Baker-LePain wrote:
But 4M works. ?? And to add insult to injury, that's going at about
70K/s.
What about our old oft occuring observations on scsi devices,
But isn't 1 goat/week
Hi all,...
...after still having some weird issues with my backup runs not
running as expected (scheduled) running chg-scsi, I was playing
around with the debug files a little, and here's the result (see
attached: scsidebug): basically, after START SCSI_LoadUnload,
messages like
---snip---
26 matches
Mail list logo
