On Wed, Nov 18, 2009 at 16:56:47 -0500, Brian Cuttler wrote:
>
> Yes, I saw what you saw in the gtar report - I can only
> surmize that the error is written in a confusing mannor.
>
> /proc is definitely a directory that contains files that
> are named for process ids that can be found on the sys
Nathan,
Yes, I saw what you saw in the gtar report - I can only
surmize that the error is written in a confusing mannor.
/proc is definitely a directory that contains files that
are named for process ids that can be found on the system.
I've updated the exclude command... we'll see if it helps.
On Wed, Nov 18, 2009 at 16:27:44 -0500, Brian Cuttler wrote:
[...]
> I had an exclude for "./root/proc/*", which may have been invalid
> and found nothing, I've changed it to "./root/proc" and will keep
> my fingers crossed for tonight.
[...]
> > > - Forwarded message from Amanda on Gat0 ---
Frank,
Dustin suggested the same, just checked and to my suprise the
switch was present, up'd it from 1800 to 2400 (seconds).
It was the only DLE in the test though and had progressed to
70% the last time I'd checked. I don't think it was idle...
I had an exclude for "./root/proc/*", which may
Brian Cuttler wrote:
> Amanda users,
>
> The backup of this particular DLE is pretty much hit or miss,
> it'll run great for a week and then fail for a week, I haven't
> been able to disern a pattern nor reason.
>
> The amanda server is old, 2.4.4 on a Solaris/Sparc system,
> the newest client is
On Wed, Nov 18, 2009 at 3:06 PM, Brian Cuttler wrote:
> Other than etimeout, what knobs do I have it 2.4.4 ?
I would think dtimeout would be the knob to tweak. I have no idea if
that was present in 2.4.4 though.
> How did your talk go ? Well attendance ? Interesting questions ?
The talk went w
Hi Dustin,
On Wed, Nov 18, 2009 at 03:02:54PM -0600, Dustin J. Mitchell wrote:
> On Wed, Nov 18, 2009 at 2:50 PM, Brian Cuttler wrote:
> > The backup of this particular DLE is pretty much hit or miss,
> > it'll run great for a week and then fail for a week, I haven't
> > been able to disern a pat
On Wed, Nov 18, 2009 at 2:50 PM, Brian Cuttler wrote:
> The backup of this particular DLE is pretty much hit or miss,
> it'll run great for a week and then fail for a week, I haven't
> been able to disern a pattern nor reason.
It looks like a timeout of some sort. Have you increased the various
Amanda users,
The backup of this particular DLE is pretty much hit or miss,
it'll run great for a week and then fail for a week, I haven't
been able to disern a pattern nor reason.
The amanda server is old, 2.4.4 on a Solaris/Sparc system,
the newest client is a Solaris/x86 with a current version
Mike R wrote:
NOTE: skipping tape-writable test
Tape daily-010 label ok
Server check took 0.410 seconds
The flush worked but I think I screwed up the labeling of the vtapes
in the process
So should I be concerned about this? Are the tapes alright based on the
results of the relabeling an
On 11/18/2009 12:02 AM, Stefan G. Weichinger wrote:
Paul Bijnens schrieb:
On 2009-11-17 02:18, Yadda wrote:
Total Newbie with Amanda. I only want to backup my WinXP PC to an
external USB drive and am lost on how to set this up. Please help!!! :(
Airports are where airplaines land, not a
/usr/sbin/amlabel daily daily-0$i slot $i;
done
Now my amcheck is showing the following
Holding disk /opt/dumps: 1246830 MB disk space available, using 1246730 MB
slot 25: read label `daily-025', date `20091118'
slot 1: read label `daily-01', date `20091109'
slot 2: read la
daily daily-0$i slot $i; done
Now my amcheck is showing the following
Holding disk /opt/dumps: 1246830 MB disk space available, using 1246730 MB
slot 25: read label `daily-025', date `20091118'
slot 1: read label `daily-01', date `20091109'
slot 2: read label `daily-02&#x
What are in those slots?
use 'amlabel' to label them.
Jean-Louis
slot 10: not an amanda tape (Read 0 bytes)
slot 11: not an amanda tape (Read 0 bytes)
slot 12: not an amanda tape (Read 0 bytes)
slot 13: not an amanda tape (Read 0 bytes)
slot 14: not an amanda tape (Read 0 bytes)
slot 15: not an
ect?)
[r...@sigma daily]# su - amanda
-bash-3.2$ /usr/sbin/amflush daily
Scanning /opt/dumps...
20091117010001: found Amanda directory.
20091118010001: found Amanda directory.
Multiple Amanda directories, please pick one by letter:
A. 20091117010001
B. 20091118010001
Select directori
u - amanda
-bash-3.2$ /usr/sbin/amflush daily
Scanning /opt/dumps...
20091117010001: found Amanda directory.
20091118010001: found Amanda directory.
Multiple Amanda directories, please pick one by letter:
A. 20091117010001
B. 20091118010001
Select directories to flush [A..B]: [ALL]
Today
20091117010001: found Amanda directory.
20091118010001: found Amanda directory.
Multiple Amanda directories, please pick one by letter:
A. 20091117010001
B. 20091118010001
Select directories to flush [A..B]: [ALL]
Today is: 20091118
Flushing dumps in 20091117010001, 20091118010001 using ta
What is your tapecycle?
How many vtapes do you have?
What is the output of amcheck?
Jean-Louis
Mike R wrote:
Good day all. I'm a fairly new amanda user, I used the 15 minute
backup guide for my setup. During the first week my backups seemed to
have gone off without a hitch as indicated by the
Good day all. I'm a fairly new amanda user, I used the 15 minute backup
guide for my setup. During the first week my backups seemed to have gone
off without a hitch as indicated by the backup reports. Now beginning on
Monday I've been getting failed backup reports, as follows:
*** A TAPE ERROR
Gunnarsson, Gunnar wrote:
Hi
I'm trying to configure Sun SL48 autloader with Amanda on Solaris 10
10/09 sparc system. SL48 library is connected to our SAN switches and
disk are beeing used and configured on the SAN but I'm not seeing the
the tape driver.
# ls /dev/rmt/
#
# /usr/sbin
20 matches
Mail list logo
