Am 06.11.18 um 19:18 schrieb Chris Nighswonger:
This seems to work:
amplot /var/backups/campus/log/amdump.1
Running under the amanda user.
However, the issue now is the attempt to write the output to the X11 terminal:
gnuplot: unable to open display ''
gnuplot: X11 aborted.
Not sure what
On Tue, Nov 06, 2018 at 01:18:15PM -0500, Chris Nighswonger wrote:
> This seems to work:
>
> amplot /var/backups/campus/log/amdump.1
>
> Running under the amanda user.
>
> However, the issue now is the attempt to write the output to the X11 terminal:
>
>
> gnuplot: unable to open display ''
>
in the
holding area and believe it help to improve performance as there were few files
and fewer file creates/accesses/deletes later on.
From: Chris Nighswonger
Sent: Tuesday, November 6, 2018 2:38 PM
To: Cuttler, Brian R (HEALTH)
Cc: ned.danie...@duke.edu; amanda-users@amanda.org
Subject: Re: dumporder
To: ned.danie...@duke.edu
Cc: amanda-users@amanda.org
Subject: Re: dumporder
ATTENTION: This email came from an external source. Do not open attachments or
click on links from unknown senders or unexpected emails.
This seems to work:
amplot /var/backups/campus/log/amdump.1
Running under the amanda
On Tue, Nov 06, 2018 at 13:18:15 -0500, Chris Nighswonger wrote:
> However, the issue now is the attempt to write the output to the X11 terminal:
>
>
> gnuplot: unable to open display ''
> gnuplot: X11 aborted.
>
> Not sure what all that's about. So I'm doing a bit of hacking on the
> gnuplot
This seems to work:
amplot /var/backups/campus/log/amdump.1
Running under the amanda user.
However, the issue now is the attempt to write the output to the X11 terminal:
gnuplot: unable to open display ''
gnuplot: X11 aborted.
Not sure what all that's about. So I'm doing a bit of hacking on
Nighswonger
Gesendet: Dienstag, 6. November 2018 17:51
An: brian.cutt...@health.ny.gov
Cc: amanda-users@amanda.org
Betreff: Re: dumporder
Digging around a bit, it appears that it might be a reference to a
file which is missing. From amplot.g, line 62 we see:
# file title has the parameters
On Tue, Nov 06, 2018 at 11:50:57AM -0500, Chris Nighswonger wrote:
> Digging around a bit, it appears that it might be a reference to a
> file which is missing. From amplot.g, line 62 we see:
>
> # file title has the parameters that this program needs
> load 'title'
> plot"run_queue" title
u need to provide the name of the amconfig. I believe it reads
> amanda.conf.
>
> -Original Message-
> From: Chris Nighswonger
> Sent: Tuesday, November 6, 2018 11:51 AM
> To: Cuttler, Brian R (HEALTH)
> Cc: amanda-users@amanda.org
> Subject: Re: dumporder
>
On Tue, Nov 06, 2018 at 11:42:16AM -0500, Chris Nighswonger wrote:
> The amplot utility is new to me. Here is what it says when I attempt to run
> it:
>
> root@scriptor:~# amplot
> /var/log/amanda/server/campus/amdump.20181106020001.debug
> Displaying graph on the screen, for next graph :
I think you need to provide the name of the amconfig. I believe it reads
amanda.conf.
-Original Message-
From: Chris Nighswonger
Sent: Tuesday, November 6, 2018 11:51 AM
To: Cuttler, Brian R (HEALTH)
Cc: amanda-users@amanda.org
Subject: Re: dumporder
ATTENTION: This email came from
ote:
>
> It has been a while, title might be the org string from amanda.conf?
> I'm sorry, it has been years since I ran it regularly.
>
> -Original Message-
> From: Chris Nighswonger
> Sent: Tuesday, November 6, 2018 11:42 AM
> To: Cuttler, Brian R (HEALTH)
> C
: dumporder
ATTENTION: This email came from an external source. Do not open attachments or
click on links from unknown senders or unexpected emails.
The amplot utility is new to me. Here is what it says when I attempt to run it:
root@scriptor:~# amplot
/var/log/amanda/server/campus/amdump.20181106020001
nning a bunch of
> large dumps to start off with could constrain dumping later on.
>
>
> -Original Message-
> From: owner-amanda-us...@amanda.org On Behalf
> Of Chris Nighswonger
> Sent: Tuesday, November 6, 2018 11:02 AM
> To: amanda-users@amanda.org
> Subjec
, 2018 11:11 AM
To: Chris Nighswonger ; amanda-users@amanda.org
Subject: RE: dumporder
ATTENTION: This email came from an external source. Do not open attachments or
click on links from unknown senders or unexpected emails.
Chris,
There is an amplot utility that I used to run a lot, it would show
On Behalf
Of Chris Nighswonger
Sent: Tuesday, November 6, 2018 11:02 AM
To: amanda-users@amanda.org
Subject: Re: dumporder
ATTENTION: This email came from an external source. Do not open attachments or
click on links from unknown senders or unexpected emails.
On Mon, Nov 5, 2018 at 1:31 PM Chris
On Mon, Nov 5, 2018 at 1:31 PM Chris Nighswonger
wrote:
>
> Is there any wisdom available on optimization of dumporder?
>
After looking over the feedback from Brian and Austin and reviewing
the actual sizes of the DLEs, I ended up with this sort of thing:
inparallel 15
On 11/5/2018 1:31 PM, Chris Nighswonger wrote:
Is there any wisdom available on optimization of dumporder?
This is personal experience only, but I find that in general, if all
your dumps run at about the same speed and you don't have to worry about
bandwidth, using something like
is
actually reasonable.
From: owner-amanda-us...@amanda.org On Behalf
Of Chris Nighswonger
Sent: Monday, November 5, 2018 1:31 PM
To: amanda-users
Subject: dumporder
ATTENTION: This email came from an external source. Do not open attachments or
click on links from unknown senders or unexpected
Is there any wisdom available on optimization of dumporder?
Kind regards,
Chris
on where I can find this information?
Thank you.
Johan
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Johan Booysen
Sent: 22 July 2008 17:07
To: amanda-users@amanda.org
Subject: RE: dumporder parameter
Hi,
No worries - I thought maybe my question
Johan Booysen wrote:
Another question:
How can I verify that those DLE entries were in fact only dumped after
05:00? In the Amanda email report I can see when the backups completed,
and can more or less work out from that when writing to tape started for
them. But I'd like to check when they
[mailto:[EMAIL PROTECTED]
Sent: 23 July 2008 12:35
To: Johan Booysen
Cc: amanda-users@amanda.org
Subject: Re: dumporder parameter
Johan Booysen wrote:
Another question:
How can I verify that those DLE entries were in fact only dumped after
05:00? In the Amanda email report I can see when
On 2008-07-22 10:37, Johan Booysen wrote:
Hi,
I got no reply so apologies if it was a stupid question. I'm now simply
using dumporder Ssss, and Amanda seems to be dumping disklist entries
starting from largest to smallest, which will work just fine for me.
I'm doing level 0 backups each night
On Tue, Jul 22, 2008 at 09:37:17AM +0100, Johan Booysen wrote:
Hi,
I got no reply so apologies if it was a stupid question. I'm now simply
using dumporder Ssss, and Amanda seems to be dumping disklist entries
starting from largest to smallest, which will work just fine for me.
I'm doing
When I backup I would like all my larger size files to be put on the first
part of the tape and work down to the smaller size files toward the end of
the tape. This I believe and hope will provide better tape usage.
If large size files are dumped last to tape there is a good chance that it
will
Amanda get the size of all the backup files and then figure the
order that it will write to tape?
Amanda does an estimate of each DLE, and from those figures
decides on which dumps to choose first (dumporder).
2) will Amanda get the size of the tape and then figure the order that it
will write
I have a question about the dumporder parameter in amanda.conf.
I want to back up 4 servers. The volumes of data on disk are as
follows:
Server1
/dir1 298G
/dir2 74G
/dir3 66G
Server2
/dir4/backups/backup1 57G
Server3
/dir5/backups/backup2 28G
Server4
/dir6/backups/backup3
Hello,
I have a question about the dumporder parameter. To what are the two bandwidth
options (B and b) related? Client/Server connection (e. g. 1Gbit)? Or the real
bandwith between server and client?
I have a client that is connected by a 1Gbit LAN-card to it's subnet in our
branch office
Jean-Louis Martineau schrieb:
bandwidth estimation is done using the previous backup of the DLE,
You can get the 'dump rates' with: amadmin config info
Would be cool if this short info could be added to the dumporder option of the
amanda.conf manpage. I didn't found this information.
Thanks
bandwidth estimation is done using the previous backup of the DLE,
You can get the 'dump rates' with: amadmin config info
Jean-Louis
Marc Muehlfeld wrote:
Hello,
I have a question about the dumporder parameter. To what are the two
bandwidth options (B and b) related? Client/Server connection
$ 20.4GB
server5 C$ 2.97GB
server5 D$ 13.7GB
If you run the backup on these servers single threaded it takes about
10 hours to backup. I've changed inparallel to 8 and maxdumps to 8
also. The dumporder is sssSsssS. In the latest test, the backup
completed in 8 hours and 41 minutes. I'm using amanda
On Tue, 8 Jul 2003 at 11:21am, Bob Zahn wrote
I'm trying to set up the options in amanda.conf to improve the
performance (this equates to shortest time to backup) of these five
Windows NT/2K servers:
server1 C$ 2.19GB
server1 D$ 35.6GB
server2 C$ 1.58GB
server2 D$ 12.9GB
server3 C$
server3 D$ 11.6GB
server4 C$ 1.3GB
server4 D$ 20.4GB
server5 C$ 2.97GB
server5 D$ 13.7GB
If you run the backup on these servers single threaded it takes
about 10 hours to backup. I've changed inparallel to 8 and maxdumps
to 8 also. The dumporder is sssSsssS. In the latest test, the
backup completed
$ 20.4GB
server5 C$ 2.97GB
server5 D$ 13.7GB
If you run the backup on these servers single threaded it takes
about 10 hours to backup. I've changed inparallel to 8 and maxdumps
to 8 also. The dumporder is sssSsssS. In the latest test, the
backup completed in 8 hours and 41 minutes. I'm using
On Tue, 8 Jul 2003 at 1:46pm, Bob Zahn wrote
This is in response to Gene's and Joshua's additional quesitons:
1. I'm only running one Samba server and that's on the amanda host server.
You'll want to look at your dumprates before and after increasing
maxdumps. 8 may lead to too much
On Tuesday 08 July 2003 14:46, Bob Zahn wrote:
This is in response to Gene's and Joshua's additional quesitons:
1. I'm only running one Samba server and that's on the amanda host
server.
2. Sorry, disklist looks like:
amanda1 //server1/C$ pc-tar 3 ge0
amanda1 //server1/D$ pc-tar 4 ge0
amanda1
Hello Roland,
Try this patch.
Jean-Louis
On Sat, Dec 08, 2001 at 12:03:29AM +, Roland E. Lipovits wrote:
Roland E. Lipovits [EMAIL PROTECTED] wrote:
Int the logfile and the report, there are many lines saying
| WARNING driver Unknown dumporder character '
The dumporder line
On Sat, Dec 08, 2001 at 10:55:27AM -0500, Jean-Louis Martineau wrote:
Try this patch.
I guess I should try this patch with the too short dumporder-string
again, right?
Regards,
Lipo
--
They that can give up essential liberty | Roland E. Lipovits
to obtain a little temporary safety
On Sat, Dec 08, 2001 at 01:51:21PM -0500, Jean-Louis Martineau wrote:
I guess I should try this patch with the too short dumporder-string
again, right?
Right, it will work with a long dumporder-string but I will
appreciate if you can test my patch.
Ok, tested with too short dumporder
Hi,
I've tried the new amanda-2.4.3b1, with a amanda.conf file
which had the new keywords (dumporder autoflush) in it,
taken from example/amanda.conf.
Int the logfile and the report, there are many lines saying
| WARNING driver Unknown dumporder character '
The dumporder line in amanda.conf
Roland E. Lipovits [EMAIL PROTECTED] wrote:
Int the logfile and the report, there are many lines saying
| WARNING driver Unknown dumporder character '
The dumporder line in amanda.conf is:
| dumporder sssS # specify the priority order of each dumper
Any ideas why this warning is shown
42 matches
Mail list logo
