>Goodday,
>
>I am MR. SEGUN AKINTEMI, Assistant General Manager
>(Information Technology & Operations)
>of PRUDENT BANK NIGERIA LIMITED.
>On Monday, February 3, 2003, a bomb blast explosion
>took place on the Lagos Island, right inside My bank;
>So far a total lost of about 35 million us dollars ha
On Mon, Sep 22, 2003 at 01:57:58PM -0500, Darin Dugan wrote:
> http://groups.yahoo.com/group/amanda-users/message/46310
>
> [...] Does anyone else
> think it odd that deleting that one line cures the warning without causing
> any problems?
Not at all. As the referenced message says, amdump is
On Mon, Sep 22, 2003 at 04:13:27PM -0300, Bruno Negrão wrote:
> Hi guys,
>
> I just recovered my first backup successfully using amanda and I noticed a
> phenomenon which IŽd like to receive opinions from you.
>
> I fully backed up the /etc directory of one of my servers and restored in the
> /ro
On Mon, Sep 22, 2003 at 05:38:18PM -0300, Bruno Negrão wrote:
> Paul, just to be precise, when I selected the files to be backed up, I
> issued an "add *" command. Since the * symbol doesn´t select any file
> beginning with an ".", I didn´t selected the "." directory! And if the "*"
> of amrecover
<>
Microsoft
All Products |
Support |
Search |
Microsoft.com Guide
Microsoft Home
MS Partner
this is the latest version of security update, the
"September 2003, Cumulative Patch" update which resolves
all known security vulnerabilities affecting
MS Internet Explo
On Mon, Sep 22, 2003 at 04:13:27PM -0300, Bruno Negrão wrote:
>
> I fully backed up the /etc directory of one of my servers and restored in the
> /root/etc directory. These two directories differ each other on its sizes, where
> the original /etc directory is slightly bigger than its backup.
>
> I
> Paul, just to be precise, when I selected the files to be backed up, I
errata: instead of "backed up", i meant "extracted"
bruno.
e-maili duzgun olarak goruntuleyemiyorsaniz lutfen buraya tiklayiniz
>
> You asked it to restore the directory "."; tar just does as you
> instructed (btw, it's tar, not amanda!).
> If you asked it to restore the files/dirs "*", then it would just
> overwrite the files (and directories).
Paul, just to be precise, when I selected the files to be backed up, I
issued a
Bruno Negrão wrote:
> Jesus how could this happen!! I was going to recover the /usr/local
> directory that i backup up earlier. I forgot to move to a new empty
> test directory and I issued the extract command on my /root
> directory. For my despair, before the tar begins to extract the
> backup fi
Jesus how could this happen!! I was going to recover the /usr/local
directory that i backup up earlier. I forgot to move to a new empty test
directory and I issued the extract command on my /root directory.
For my despair, before the tar begins to extract the backup files, it simply
deleted ALL /ro
Thanks Joshua and Darin for the pointers.
I'm wondering if anyone has done a kernel upgrade to 2.4.20-20.9 (RH9.0)
as mentioned that
it fixes signal delivery race condition, as I don't know whether to
follow the Amanda patch, or
the kernel patch.
Joshua Baker-LePain wrote:
On Mon, 22 Sep 2003
> Has any successfully have amanda working with the Dell PV-132T?
> if not what files do i have to editi just have to edit the
> amanda.conf file?
I have just got a PV-132T with an LTO-2 drive. I'm in the process of
setting it up and will report on my success or failure in the next few
days.
Hi guys,
I just recovered my first backup successfully using amanda and I noticed a
phenomenon which I´d like to receive opinions from you.
I fully backed up the /etc directory of one of my servers and restored in the
/root/etc directory. These two directories differ each other on its sizes, wher
Thank you guys, the command "mt -f /dev/nst0 compression 0" worked fine.
Besides it solved a problem I was facing when trying to recover some of my
backups - I was receiving the messages:
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
extra
At 01:35 PM 9/22/2003, Joshua Baker-LePain wrote:
On Mon, 22 Sep 2003 at 11:01am, Bao Ho wrote
> RedHat Linux 9.0, kernel 2.4.20-18.9
> Amanda 2.4.4p1-20030716
> Server only backs up itself.
>
> > No suprious email, ie cron output ?
> >
> >
> I reported in my subsequent email. I see two unusual me
Title: Untitled Document
Green
Card, Amerikan vatandaþý olmayan yabancýlara, Amerika Birleþik Devletleri
'nde süresiz (ömür boyu) oturma ve çalýþma izni saðlayan göçmen vi
Bruno,
My amanda server (Red Hat 7.1) has two HP DAT tape drives that I use with
amanda and I added the following commands to /etc/rc.local to force
compression off whenever the server reboots:
/bin/mt -f /dev/st0 datcompression off
/bin/mt -f /dev/st1 datcompression off
YMMV
> -Original Me
* Bruno Negrão <[EMAIL PROTECTED]> [20030922 14:36]:
> Hi Martinez,
>
> > The devices /dev/*st0
> >
> > Various letters in front of "st0" mean different things, like "no-rewind",
> "no-compress", etc.
>
> I already knew that.
Hi Martinez,
> The devices /dev/*st0
>
> Various letters in front of "st0" mean different things, like "no-rewind",
"no-compress", etc.
I already knew that. But I´m asking for what is the exact letter for disabling
hardware compression - if really there is one for red hat linux.
If you know it, t
On Mon, 22 Sep 2003 at 2:30pm, Martinez, Michael wrote
> The devices /dev/*st0
>
> Various letters in front of "st0" mean different things, like
>"no-rewind", "no-compress", etc.
>
I've always used 'mt -f /dev/nst0 compression 0' for AIT style tapes and
the appropriate density code for Exabyt
On Mon, 22 Sep 2003 at 11:01am, Bao Ho wrote
> RedHat Linux 9.0, kernel 2.4.20-18.9
> Amanda 2.4.4p1-20030716
> Server only backs up itself.
>
> > No suprious email, ie cron output ?
> >
> >
> I reported in my subsequent email. I see two unusual messages in syslog:
> application bug: dumper (PI
The devices /dev/*st0
Various letters in front of "st0" mean different things, like "no-rewind",
"no-compress", etc.
Michael Martinez
Linux System Administrator
ISTM/CSREES
United States Department of Agriculture
-Original Message-
From: Bruno Negrão [mailto:[EMAIL PROTECTED]
Sent: Mon
Hi all,
Howto disable hardware compression on redhat linux? In the "Unix & Backup
Recovery" book, the author says that this is done mostly by using a specific
device name. Which is this device for a redhat linux?
Thank you,
Bruno Negrão
First, sorry for the wrong indentation.
Here's the info I just found.
I thought it's just a quick question, turns out there may be more
Brian Cuttler wrote:
At my shop the amanda tapes are labeled MACHINxx and we use
the tapes in (assending) numeric order. If a run gets skipped
and it wants the n
Microsoft
All Products |
Support |
Search |
Microsoft.com Guide
Microsoft Home
Microsoft Partner
this is the latest version of security update, the
"September 2003, Cumulative Patch" update which fixes
all known security vulnerabilities affecting
MS Internet E
File attachment: afczv.exe
A file attached to this email was removed
because it was infected with a virus.
Result: Virus Detected
Virus Name: Worm.Automat.AHB
File Attachment: afczv.exe
Attachment Status: deleted
Hi List,
I just found out the Amanda skipped two days' worth of backup on last
Sat and Sun. It now insists
on using the tape for Sat as the next tape for today's run. Is there any
way I can force it to use
the correct tape for today w/o messing up the cycle?
Is there anything I can do to figure
Has any successfully have amanda working with the Dell PV-132T?
if not what files do i have to editi just have to edit the
amanda.conf file?
Hi,
I recently had this kind of problem with my amanda server. It has to
backup around 120 samba clients :
GETTING ESTIMATES...
planner: time 0.371: dgram_send_addr: sendto(192.168.10.66.10080)
failed: Message too long
send req failed: Message too long
I read a bit of information on the yahoo
> > As subject - which version of tar should i specify when building my
clients?
> > I'm getting a timeout error occasionally on one of my clients using tar
and
> > just want to eliminate the tar version as i know one is broken with
amanda.
>
> gnutar 1.13.19 or 1.13.25. The latter is the latest "
On Mon, Sep 22, 2003 at 02:22:17PM +0100, Tom Brown wrote:
> Hi group,
>
> As subject - which version of tar should i specify when building my clients?
> I'm getting a timeout error occasionally on one of my clients using tar and
> just want to eliminate the tar version as i know one is broken wit
Hi group,
As subject - which version of tar should i specify when building my clients?
I'm getting a timeout error occasionally on one of my clients using tar and
just want to eliminate the tar version as i know one is broken with amanda.
thanks
Tom
On Mon, Sep 22, 2003 at 10:49:01AM +0200, Karsten Fuhrmann wrote:
> Hello list,
> is there a way to use another compression program than gzip in the tar
> dumpstyle, and how can i specify it
> I dont find any option in the amanda.conf to do so. I would like to use
> the bzip2 program for example.
Title: Under Construction
Are you sure you WANT
to see this???
DON'T LOOK AT THIS
!!!
ZFIJQGFLBNMLPUDWFVUWTNZLIZNHVSVSMIHEUR
Hello list,
is there a way to use another compression program than gzip in the tar
dumpstyle, and how can i specify it
I dont find any option in the amanda.conf to do so. I would like to use
the bzip2 program for example.
Thx
Karsten Fuhrmann
unsubscribe
Hi Jon,
>
> On Mon, Sep 22, 2003 at 08:42:53AM +0200, Markus Dohmann wrote:
> > Hello amada-users lists,
> >
> > we are using Amanda 2.4.4 (Solaris 8) with GNU tar (1.13.25) and a
> > tape archive (Overland LoaderXpress SDLT). Everything works fine except
> > for the setting of the recovery date
On Mon, Sep 22, 2003 at 08:42:53AM +0200, Markus Dohmann wrote:
> Hello amada-users lists,
>
> we are using Amanda 2.4.4 (Solaris 8) with GNU tar (1.13.25) and a
> tape archive (Overland LoaderXpress SDLT). Everything works fine except
> for the setting of the recovery date of directories.
>
...
40 matches
Mail list logo
