On Mon, Jun 20, 2005 at 03:50:41PM -0700, Kevin Dalley enlightened us:
> I'm trying to run an archival backup which I run every 6 months or
> so. I hope to have a full backup of everything every 6 months. This
> is in addition to my standard backup, which includes incrementals, run
> almost every
On Monday 20 June 2005 12:03, Anthony Worrall wrote:
>Hi
>
>As anyone tried using something like awstats to display statics
> about how amanda is doing? It would need a script to get the amdump
> file into a format that awstat could be told about i.e. something
> like an xferlog.
>
>Before I start
On Mon, Jun 20, 2005 at 08:17:55PM -0300, Fabricio Luiz Machado wrote:
> Hi.
> Some of my DDS-4 tapes are bad (I/O error).
> So... i?m thinking if these tapes are trustworthy... :-/
> Are there another better solution, that I can trust more than DDS-4 ?
> Maybe DLT ?
DLT has a good track record, b
Hi.
Some of my DDS-4 tapes are bad (I/O error).
So... i´m thinking if these tapes are trustworthy... :-/
Are there another better solution, that I can trust more than DDS-4 ?
Maybe DLT ?
thanks!
Fabricio.
__
I'm trying to run an archival backup which I run every 6 months or
so. I hope to have a full backup of everything every 6 months. This
is in addition to my standard backup, which includes incrementals, run
almost every week day.
It isn't working as I expect.
My daily amanda backup, however, is
On Mon, Jun 20, 2005 at 04:10:56PM -0600, Cam wrote:
> Hi,
>
> On 6/20/05, Stefan G. Weichinger <[EMAIL PROTECTED]> wrote:
> > Sorry to be that dry:
> >
> > The AMANDA documentation also says not to use "localhost".
>
> I'm not using localhost... i'm trying to restore stuff on my box
> aspapp2.f
Hi,
On 6/20/05, Stefan G. Weichinger <[EMAIL PROTECTED]> wrote:
> Sorry to be that dry:
>
> The AMANDA documentation also says not to use "localhost".
I'm not using localhost... i'm trying to restore stuff on my box
aspapp2.foo.com from the tape/index server db1.foo.com. My amanda
access file o
Cam wrote:
> cannot connect to localhost: Connection refused
> amrecover - can't talk to tape server
>
> I'm assuming this is because i'm running the utility as root (not as
> amanda), but iirc, the amanda documentation says i have to be root.
Sorry to be that dry:
The AMANDA documentation als
Hello, Jon, you wrote:
> Actually I meant that to go to sgw, not the list :(
Yeah, I know, all those function-keys ;)
> I'm unclear about what maxdumps should do is some settings.
>
> Suppose I have a general setting of maxdumps of 1, either by
> not specifying it in amanda.conf or by setting i
Hi,
I'm trying to recover some files w/ amrecover on one of my hosts.
Everything goes good w/ the amrecover utility, up until i want to
extract... that part goes like this:
amrecover> extract
Extracting files using tape drive /dev/nst0 on host localhost.
The following tapes are needed: DailySet1
As an FYI here's what I got with my DAT7000 (Quantum) drives
~# mtx load 28 1 ; sleep 160 ; mt -f /dev/nst1 datcompression 2 ;
amtapetype -f /dev/nst1 -t DAT7000_Compressed -e 70G ; mt -f /dev/nst1
rewind ; mt -f /dev/nst1 datcompression 0 ; amtapetype -f /dev/nst1 -t
DAT7000_UnCompressed
Hi
As anyone tried using something like awstats to display statics about
how amanda is doing? It would need a script to get the amdump file into
a format that awstat could be told about i.e. something like an xferlog.
Before I start hacking I thought I would ask if anyone else has already
don
Title: RE: lvm and amanda?
Do you have an SELinux setting of "targeted" on that box? This may be related
to permissions--I must check this.
I have amanda installed on a CentOS box, and I have an RHEL 4 server with a similar RAID volume /dev entries.
Following up on myself... (as usual on
Following up on myself... (as usual on mondays)...
Paul Bijnens wrote:
The good news is that Redhat just fixed this very recently.
in device-mapper-1.01.01-1.RHEL4, which you can install by up2date
or "yum update device-mapper".
https://rhn.redhat.com/errata/RHEA-2005-188.html says:
> [..
Oscar Ricardo Silva wrote:
At 05:02 AM 6/18/2005, you wrote:
Oscar Ricardo Silva wrote:
drwxr-xr-x 2 root root 100 Jun 6 03:58 /dev/mapper
brw-r- 1 root disk 253, 0 Jun 6 03:58 VolGroup00-LogVol00
Maybe I did not sleep very well, or I am missing something obvious
or did not drink
Jon LaBadie wrote:
>>"maxdumps" limits the number of dumper processes per DLE, while
>>"inparallel" limits the overall number of dumper processes running in
>>parallel.
>
> Is that dumper procs per DLE? Or per host?
> Seems to me that any DLE should only have one dumper assigned.
dumper-procs p
I thought I would respond to the various suggestions in one message and
included my original message at the end for reference. I also realized
that I wasn't clear when I displayed the permissions
on /dev/mapper/VolGroup00-LogVol00 device. When the machine boots,
permissions are:
drwxr
On Mon, Jun 20, 2005 at 12:37:11PM +0200, Stefan G. Weichinger wrote:
> Vects wrote:
>
> > I changed inparallel and maxdumps but it didn't help.
> > See below the configuration files of amanda.
> >
> > inparallel 10
>
> > define dumptype global {
> > comment "Global definitions"
> > inde
Vects wrote:
> I changed inparallel and maxdumps but it didn't help.
> See below the configuration files of amanda.
>
> inparallel 10
> define dumptype global {
> comment "Global definitions"
> index yes
> record no
> maxdumps 10
> }
>
> define dumptype act-full {
> global
>
Vects wrote:
I changed inparallel and maxdumps but it didn't help.
See below the configuration files of amanda.
I would like to have the amdump.XX file too,
and maybe the the full amstatus output.
(You may send it to me privately if you don't want to post
the file in the public.)
One "strange
On Sun, 2005-06-19 at 23:50 +0200, Paul Bijnens wrote:
> Vects wrote:
> > I did grep on amstatus output, see below
> >
> > [EMAIL PROTECTED] ~]$ amstatus Full1 | grep dumping
> > comp1:/dev/md0 0 2168626k wait for dumping
> > comp1:/dev/md3 0 7042137k wait for dumping
> > comp2:/dev/md
21 matches
Mail list logo