Re: flush-threshold-* parameters - some clarification needed.

2013-03-28 Thread Jean-Louis Martineau

On 03/28/2013 12:55 AM, Kamil Jońca wrote:

Jean-Louis Martineau  writes:


On 03/27/2013 01:02 PM, Kamil Jońca wrote:

Simple:
Say, I have 1 TB disk for vtapes.
I can create 900 vtapes on this disk. But all of dumps have ~500MB, so
only half of disk are used. And only 900 days are remebered.
And I'm curious if I have better utilization for  disk, so I can have
longer period of dumps.

Create 1800 vtapes.
The number of slots should not directly depend on the length of the
tapetype but on the used size of each slots.

But in this case there is a risk to get "no space left on device" when,
in turn, dumps get larger later.
What then?


You monitor the free space and delete older slot if it become close to full.

Jean-Louis


Re: flush-threshold-* parameters - some clarification needed.

2013-03-27 Thread Kamil Jońca
Jean-Louis Martineau  writes:

> On 03/27/2013 01:02 PM, Kamil Jońca wrote:
>> Simple:
>> Say, I have 1 TB disk for vtapes.
>> I can create 900 vtapes on this disk. But all of dumps have ~500MB, so
>> only half of disk are used. And only 900 days are remebered.
>> And I'm curious if I have better utilization for  disk, so I can have
>> longer period of dumps.
>
> Create 1800 vtapes.
> The number of slots should not directly depend on the length of the
> tapetype but on the used size of each slots.

But in this case there is a risk to get "no space left on device" when,
in turn, dumps get larger later.
What then?
KJ
-- 
http://sporothrix.wordpress.com/2011/01/16/usa-sie-krztusza-kto-nastepny/
Think sideways!
-- Ed De Bono



Re: flush-threshold-* parameters - some clarification needed.

2013-03-27 Thread Jean-Louis Martineau

On 03/27/2013 01:02 PM, Kamil Jońca wrote:

Simple:
Say, I have 1 TB disk for vtapes.
I can create 900 vtapes on this disk. But all of dumps have ~500MB, so
only half of disk are used. And only 900 days are remebered.
And I'm curious if I have better utilization for  disk, so I can have
longer period of dumps.


Create 1800 vtapes.
The number of slots should not directly depend on the length of the 
tapetype but on the used size of each slots.



For now, if I understand correctly, I can only do statistical estimate?


Another case:
I create vtapes which are +- DVD size, and it's rather important for me
not to have "tapes" with only some bytes on them.


In other post you said:

--8<---cut here---start->8---
Not sure why you change the disk every days, but it's generally BAD
unless you do full every night.
--8<---cut here---end--->8---

Does this have something common with message at:
http://www.mail-archive.com/[email protected]/msg4.html ?


yes. what is important is to not lose all full backup.



Re: flush-threshold-* parameters - some clarification needed.

2013-03-27 Thread Kamil Jońca
Jean-Louis Martineau  writes:

> Kamil,
>
> The flush-threshold-* are useful for tape device, there is no
> advantage to use them with vtape.
> With a tape, if you don't fill it, there is unused space on it.
> With vtape, if you write 500MB to a 1GB vtape, then the vtape use
> 500MB nothing more, the space is not lost, it can be use by another
> slot.
>
> I do not understand what you want to do.

Simple:
Say, I have 1 TB disk for vtapes.  
I can create 900 vtapes on this disk. But all of dumps have ~500MB, so
only half of disk are used. And only 900 days are remebered.
And I'm curious if I have better utilization for  disk, so I can have
longer period of dumps. 
For now, if I understand correctly, I can only do statistical estimate?


Another case:
I create vtapes which are +- DVD size, and it's rather important for me
not to have "tapes" with only some bytes on them.


In other post you said:

--8<---cut here---start->8---
Not sure why you change the disk every days, but it's generally BAD
unless you do full every night.
--8<---cut here---end--->8---

Does this have something common with message at:
http://www.mail-archive.com/[email protected]/msg4.html ?

KJ


-- 
http://blogdebart.pl/2010/03/17/dalsze-przygody-swinki-w-new-jersey/
Uwolnić słonia !!!



Re: flush-threshold-* parameters - some clarification needed.

2013-03-27 Thread Jean-Louis Martineau

Kamil,

The flush-threshold-* are useful for tape device, there is no advantage 
to use them with vtape.

With a tape, if you don't fill it, there is unused space on it.
With vtape, if you write 500MB to a 1GB vtape, then the vtape use 500MB 
nothing more, the space is not lost, it can be use by another slot.


I do not understand what you want to do.

Jean-Louis

On 03/27/2013 11:41 AM, Kamil Jońca wrote:

Jean-Louis Martineau  writes:


On 03/27/2013 08:58 AM, Kamil Jońca wrote:

Jean-Louis Martineau  writes:


On 03/27/2013 06:39 AM, Kamil Jońca wrote:

(This is duplicate mail, previously sent, but I weren't subscribed)
In some sites there is suggestion, that config:
--8<---cut here---start->8---
#flush-threshold-dumped 100 # (or more)
#flush-threshold-scheduled 100 # (or more)
#taperflush 100
#autoflush yes
--8<---cut here---end--->8---
helps to do better tape utilization.

But how behave amanda in my configuration (+ these four lines above):

I have defined 1gb vtapes, placed onto four hard disks rotated
(ie. first flush go to disk 1, second to 2, third to 3, fourth to 4,
fifth to 1, and so on)

say on first disk are tapes: alfa-1-1 to alfa-1-10
on second:  alfa-2-1 to alfa-2-10
on third: alfa-3-1 to alfa-3-10
on fourth: alfa-4-1 to alfa-4-10

One day dumps takes 1,5GB and goes to tape alfa-1-1 and (partially)
alfa-1-2.

Amanda should not write to alfa-1-2 if the above setting are commented out.
Are you using a holding a disk? It must be larger than a vtape (1gb).

My bad. I forgot to say that I have  runtapes greater than 1.
And my question is what amanda do if above flush settings are not
commmented.

Amanda should not write to alfa-1-2, the backup should stay in the
holding disk.

Yes, I use holding disk.

So far I do not have these lines and amanda writes backup to disk (for
example today backup below):
--8<---cut here---start->8---
-rw-r- 1 backup backup243 Mar 27 16:27 
/var/spool/amanda/vtapes/state
-rw--- 1 backup backup  39436 Mar 27 16:23 
/var/spool/amanda/vtapes/slot8/8.localhost._srv_samba_kopie.2
-rw--- 1 backup backup  33328 Mar 27 16:23 
/var/spool/amanda/vtapes/slot8/9.localhost._var_lib_samba.1
-rw--- 1 backup backup   25797104 Mar 27 16:23 
/var/spool/amanda/vtapes/slot8/00010.localhost._var_spool_news_archive.1
-rw--- 1 backup backup   58407680 Mar 27 16:23 
/var/spool/amanda/vtapes/slot8/3.localhost._home_kjonca_Mail.6
-rw--- 1 backup backup  63076 Mar 27 16:23 
/var/spool/amanda/vtapes/slot8/4.localhost._home_kjonca_Muzyka.1
-rw--- 1 backup backup   16056464 Mar 27 16:23 
/var/spool/amanda/vtapes/slot8/5.localhost._home_kjonca_archiwum.2
-rw--- 1 backup backup   48955192 Mar 27 16:23 
/var/spool/amanda/vtapes/slot8/6.localhost._srv_archiwa.2
-rw--- 1 backup backup  43736 Mar 27 16:23 
/var/spool/amanda/vtapes/slot8/7.localhost._srv_samba.1
-rw--- 1 backup backup  34024 Mar 27 16:23 
/var/spool/amanda/vtapes/slot8/2.localhost._home_kjonca_Drivers.1
-rw--- 1 backup backup  133441876 Mar 27 16:23 
/var/spool/amanda/vtapes/slot8/1.localhost._home_kjonca_Downloads.2
-rw--- 1 backup backup  32768 Mar 27 16:23 
/var/spool/amanda/vtapes/slot8/0.alfa-2-8
-rw--- 1 backup backup  965672960 Mar 27 16:23 
/var/spool/amanda/vtapes/slot7/8.localhost._home_kjonca_Downloads.2
-rw--- 1 backup backup   53746648 Mar 27 16:23 
/var/spool/amanda/vtapes/slot7/6.localhost._home_kjonca.3
-rw--- 1 backup backup  81132 Mar 27 16:23 
/var/spool/amanda/vtapes/slot7/7.localhost._home_kjonca_CalibreLibrary.1
-rw--- 1 backup backup   34692104 Mar 27 16:23 
/var/spool/amanda/vtapes/slot7/2.bambus.kjonca._home.2
-rw--- 1 backup backup  59360 Mar 27 16:23 
/var/spool/amanda/vtapes/slot7/3.localhost._etc.1
-rw--- 1 backup backup 164232 Mar 27 16:23 
/var/spool/amanda/vtapes/slot7/4.localhost._home.1
-rw--- 1 backup backup   19114828 Mar 27 16:23 
/var/spool/amanda/vtapes/slot7/5.localhost._home_f4y.1
-rw--- 1 backup backup  52240 Mar 27 16:23 
/var/spool/amanda/vtapes/slot7/1.bambus.kjonca._etc.1
-rw--- 1 backup backup  32768 Mar 27 16:23 
/var/spool/amanda/vtapes/slot7/0.alfa-2-7
--8<---cut here---end--->8---

As we can see amanda fills two vtapes (slot7 and slot8).
And my experience shows that (WITHOUT flush-* settings mentioned above)
at next run (with this disk) amanda will use next slot. Right?
What amanda do when these flush-* will be set to 100?


They should be written to vtape on the next run or when you have more than 1GB 
(100% of 1gb) of dump on holding disk.

Uncommenting the above setting is useless if you do not use a holding
disk.

Yes, of course.

Did you read the documentation?

Yes. But I do not know which vtape amanda use at some of next run.
(B

Re: flush-threshold-* parameters - some clarification needed.

2013-03-27 Thread Jean-Louis Martineau

On 03/27/2013 11:41 AM, Kamil Jońca wrote:

Jean-Louis Martineau  writes:


On 03/27/2013 08:58 AM, Kamil Jońca wrote:

Jean-Louis Martineau  writes:


On 03/27/2013 06:39 AM, Kamil Jońca wrote:

(This is duplicate mail, previously sent, but I weren't subscribed)
In some sites there is suggestion, that config:
--8<---cut here---start->8---
#flush-threshold-dumped 100 # (or more)
#flush-threshold-scheduled 100 # (or more)
#taperflush 100
#autoflush yes
--8<---cut here---end--->8---
helps to do better tape utilization.

But how behave amanda in my configuration (+ these four lines above):

I have defined 1gb vtapes, placed onto four hard disks rotated
(ie. first flush go to disk 1, second to 2, third to 3, fourth to 4,
fifth to 1, and so on)

say on first disk are tapes: alfa-1-1 to alfa-1-10
on second:  alfa-2-1 to alfa-2-10
on third: alfa-3-1 to alfa-3-10
on fourth: alfa-4-1 to alfa-4-10

One day dumps takes 1,5GB and goes to tape alfa-1-1 and (partially)
alfa-1-2.

Amanda should not write to alfa-1-2 if the above setting are commented out.
Are you using a holding a disk? It must be larger than a vtape (1gb).

My bad. I forgot to say that I have  runtapes greater than 1.
And my question is what amanda do if above flush settings are not
commmented.

Amanda should not write to alfa-1-2, the backup should stay in the
holding disk.

Yes, I use holding disk.

So far I do not have these lines and amanda writes backup to disk (for
example today backup below):
--8<---cut here---start->8---
-rw-r- 1 backup backup243 Mar 27 16:27 
/var/spool/amanda/vtapes/state
-rw--- 1 backup backup  39436 Mar 27 16:23 
/var/spool/amanda/vtapes/slot8/8.localhost._srv_samba_kopie.2
-rw--- 1 backup backup  33328 Mar 27 16:23 
/var/spool/amanda/vtapes/slot8/9.localhost._var_lib_samba.1
-rw--- 1 backup backup   25797104 Mar 27 16:23 
/var/spool/amanda/vtapes/slot8/00010.localhost._var_spool_news_archive.1
-rw--- 1 backup backup   58407680 Mar 27 16:23 
/var/spool/amanda/vtapes/slot8/3.localhost._home_kjonca_Mail.6
-rw--- 1 backup backup  63076 Mar 27 16:23 
/var/spool/amanda/vtapes/slot8/4.localhost._home_kjonca_Muzyka.1
-rw--- 1 backup backup   16056464 Mar 27 16:23 
/var/spool/amanda/vtapes/slot8/5.localhost._home_kjonca_archiwum.2
-rw--- 1 backup backup   48955192 Mar 27 16:23 
/var/spool/amanda/vtapes/slot8/6.localhost._srv_archiwa.2
-rw--- 1 backup backup  43736 Mar 27 16:23 
/var/spool/amanda/vtapes/slot8/7.localhost._srv_samba.1
-rw--- 1 backup backup  34024 Mar 27 16:23 
/var/spool/amanda/vtapes/slot8/2.localhost._home_kjonca_Drivers.1
-rw--- 1 backup backup  133441876 Mar 27 16:23 
/var/spool/amanda/vtapes/slot8/1.localhost._home_kjonca_Downloads.2
-rw--- 1 backup backup  32768 Mar 27 16:23 
/var/spool/amanda/vtapes/slot8/0.alfa-2-8
-rw--- 1 backup backup  965672960 Mar 27 16:23 
/var/spool/amanda/vtapes/slot7/8.localhost._home_kjonca_Downloads.2
-rw--- 1 backup backup   53746648 Mar 27 16:23 
/var/spool/amanda/vtapes/slot7/6.localhost._home_kjonca.3
-rw--- 1 backup backup  81132 Mar 27 16:23 
/var/spool/amanda/vtapes/slot7/7.localhost._home_kjonca_CalibreLibrary.1
-rw--- 1 backup backup   34692104 Mar 27 16:23 
/var/spool/amanda/vtapes/slot7/2.bambus.kjonca._home.2
-rw--- 1 backup backup  59360 Mar 27 16:23 
/var/spool/amanda/vtapes/slot7/3.localhost._etc.1
-rw--- 1 backup backup 164232 Mar 27 16:23 
/var/spool/amanda/vtapes/slot7/4.localhost._home.1
-rw--- 1 backup backup   19114828 Mar 27 16:23 
/var/spool/amanda/vtapes/slot7/5.localhost._home_f4y.1
-rw--- 1 backup backup  52240 Mar 27 16:23 
/var/spool/amanda/vtapes/slot7/1.bambus.kjonca._etc.1
-rw--- 1 backup backup  32768 Mar 27 16:23 
/var/spool/amanda/vtapes/slot7/0.alfa-2-7
--8<---cut here---end--->8---

As we can see amanda fills two vtapes (slot7 and slot8).
And my experience shows that (WITHOUT flush-* settings mentioned above)
at next run (with this disk) amanda will use next slot. Right?

right


What amanda do when these flush-* will be set to 100?


man amanda.conf: search for flush-threshold-dumped and 
flush-threshold-scheduled.
It will not write to the second vtape, it will keep the backup in the 
holding disk.

It will write to the next available vtape on the following run.



They should be written to vtape on the next run or when you have more than 1GB 
(100% of 1gb) of dump on holding disk.

Uncommenting the above setting is useless if you do not use a holding
disk.

Yes, of course.

Did you read the documentation?

Yes. But I do not know which vtape amanda use at some of next run.

The one available when it try to write to a vtape.


(Because tomorrow I will put disk with labels alfa-3-*, on Friday alfa

Re: flush-threshold-* parameters - some clarification needed.

2013-03-27 Thread Kamil Jońca
Jean-Louis Martineau  writes:

> On 03/27/2013 08:58 AM, Kamil Jońca wrote:
>> Jean-Louis Martineau  writes:
>>
>>> On 03/27/2013 06:39 AM, Kamil Jońca wrote:
 (This is duplicate mail, previously sent, but I weren't subscribed)
 In some sites there is suggestion, that config:
 --8<---cut here---start->8---
 #flush-threshold-dumped 100 # (or more)
 #flush-threshold-scheduled 100 # (or more)
 #taperflush 100
 #autoflush yes
 --8<---cut here---end--->8---
 helps to do better tape utilization.

 But how behave amanda in my configuration (+ these four lines above):

 I have defined 1gb vtapes, placed onto four hard disks rotated
 (ie. first flush go to disk 1, second to 2, third to 3, fourth to 4,
 fifth to 1, and so on)

 say on first disk are tapes: alfa-1-1 to alfa-1-10
 on second:  alfa-2-1 to alfa-2-10
 on third: alfa-3-1 to alfa-3-10
 on fourth: alfa-4-1 to alfa-4-10

 One day dumps takes 1,5GB and goes to tape alfa-1-1 and (partially)
 alfa-1-2.
>>> Amanda should not write to alfa-1-2 if the above setting are commented out.
>>> Are you using a holding a disk? It must be larger than a vtape (1gb).
>>
>> My bad. I forgot to say that I have  runtapes greater than 1.
>> And my question is what amanda do if above flush settings are not
>> commmented.
>
> Amanda should not write to alfa-1-2, the backup should stay in the
> holding disk.
Yes, I use holding disk.

So far I do not have these lines and amanda writes backup to disk (for
example today backup below):
--8<---cut here---start->8---
-rw-r- 1 backup backup243 Mar 27 16:27 
/var/spool/amanda/vtapes/state
-rw--- 1 backup backup  39436 Mar 27 16:23 
/var/spool/amanda/vtapes/slot8/8.localhost._srv_samba_kopie.2
-rw--- 1 backup backup  33328 Mar 27 16:23 
/var/spool/amanda/vtapes/slot8/9.localhost._var_lib_samba.1
-rw--- 1 backup backup   25797104 Mar 27 16:23 
/var/spool/amanda/vtapes/slot8/00010.localhost._var_spool_news_archive.1
-rw--- 1 backup backup   58407680 Mar 27 16:23 
/var/spool/amanda/vtapes/slot8/3.localhost._home_kjonca_Mail.6
-rw--- 1 backup backup  63076 Mar 27 16:23 
/var/spool/amanda/vtapes/slot8/4.localhost._home_kjonca_Muzyka.1
-rw--- 1 backup backup   16056464 Mar 27 16:23 
/var/spool/amanda/vtapes/slot8/5.localhost._home_kjonca_archiwum.2
-rw--- 1 backup backup   48955192 Mar 27 16:23 
/var/spool/amanda/vtapes/slot8/6.localhost._srv_archiwa.2
-rw--- 1 backup backup  43736 Mar 27 16:23 
/var/spool/amanda/vtapes/slot8/7.localhost._srv_samba.1
-rw--- 1 backup backup  34024 Mar 27 16:23 
/var/spool/amanda/vtapes/slot8/2.localhost._home_kjonca_Drivers.1
-rw--- 1 backup backup  133441876 Mar 27 16:23 
/var/spool/amanda/vtapes/slot8/1.localhost._home_kjonca_Downloads.2
-rw--- 1 backup backup  32768 Mar 27 16:23 
/var/spool/amanda/vtapes/slot8/0.alfa-2-8
-rw--- 1 backup backup  965672960 Mar 27 16:23 
/var/spool/amanda/vtapes/slot7/8.localhost._home_kjonca_Downloads.2
-rw--- 1 backup backup   53746648 Mar 27 16:23 
/var/spool/amanda/vtapes/slot7/6.localhost._home_kjonca.3
-rw--- 1 backup backup  81132 Mar 27 16:23 
/var/spool/amanda/vtapes/slot7/7.localhost._home_kjonca_CalibreLibrary.1
-rw--- 1 backup backup   34692104 Mar 27 16:23 
/var/spool/amanda/vtapes/slot7/2.bambus.kjonca._home.2
-rw--- 1 backup backup  59360 Mar 27 16:23 
/var/spool/amanda/vtapes/slot7/3.localhost._etc.1
-rw--- 1 backup backup 164232 Mar 27 16:23 
/var/spool/amanda/vtapes/slot7/4.localhost._home.1
-rw--- 1 backup backup   19114828 Mar 27 16:23 
/var/spool/amanda/vtapes/slot7/5.localhost._home_f4y.1
-rw--- 1 backup backup  52240 Mar 27 16:23 
/var/spool/amanda/vtapes/slot7/1.bambus.kjonca._etc.1
-rw--- 1 backup backup  32768 Mar 27 16:23 
/var/spool/amanda/vtapes/slot7/0.alfa-2-7
--8<---cut here---end--->8---

As we can see amanda fills two vtapes (slot7 and slot8). 
And my experience shows that (WITHOUT flush-* settings mentioned above)
at next run (with this disk) amanda will use next slot. Right?
What amanda do when these flush-* will be set to 100? 

> They should be written to vtape on the next run or when you have more than 
> 1GB (100% of 1gb) of dump on holding disk.
>
> Uncommenting the above setting is useless if you do not use a holding
> disk.
Yes, of course. 
>
> Did you read the documentation? 
Yes. But I do not know which vtape amanda use at some of next run. 
(Because tomorrow I will put disk with labels alfa-3-*, on Friday alfa-4-*, 
on saturday alfa-1-*, and on Sunday again alfa-2-*)
>Did you tried it?

I use amanda, but WITHOUT these settings.

KJ


-- 
http://blogdebart.pl/2012/06/24/hiena/
Try to get all of yo

Re: flush-threshold-* parameters - some clarification needed.

2013-03-27 Thread Jean-Louis Martineau

On 03/27/2013 08:58 AM, Kamil Jońca wrote:

Jean-Louis Martineau  writes:


On 03/27/2013 06:39 AM, Kamil Jońca wrote:

(This is duplicate mail, previously sent, but I weren't subscribed)
In some sites there is suggestion, that config:
--8<---cut here---start->8---
#flush-threshold-dumped 100 # (or more)
#flush-threshold-scheduled 100 # (or more)
#taperflush 100
#autoflush yes
--8<---cut here---end--->8---
helps to do better tape utilization.

But how behave amanda in my configuration (+ these four lines above):

I have defined 1gb vtapes, placed onto four hard disks rotated
(ie. first flush go to disk 1, second to 2, third to 3, fourth to 4,
fifth to 1, and so on)

say on first disk are tapes: alfa-1-1 to alfa-1-10
on second:  alfa-2-1 to alfa-2-10
on third: alfa-3-1 to alfa-3-10
on fourth: alfa-4-1 to alfa-4-10

One day dumps takes 1,5GB and goes to tape alfa-1-1 and (partially)
alfa-1-2.

Amanda should not write to alfa-1-2 if the above setting are commented out.
Are you using a holding a disk? It must be larger than a vtape (1gb).


My bad. I forgot to say that I have  runtapes greater than 1.
And my question is what amanda do if above flush settings are not
commmented.


Amanda should not write to alfa-1-2, the backup should stay in the holding disk.
They should be written to vtape on the next run or when you have more than 1GB 
(100% of 1gb) of dump on holding disk.

Uncommenting the above setting is useless if you do not use a holding disk.

Did you read the documentation? Did you tried it?

Jean-Louis




Re: flush-threshold-* parameters - some clarification needed.

2013-03-27 Thread Kamil Jońca
Jean-Louis Martineau  writes:

> On 03/27/2013 06:39 AM, Kamil Jońca wrote:
>> (This is duplicate mail, previously sent, but I weren't subscribed)
>> In some sites there is suggestion, that config:
>> --8<---cut here---start->8---
>> #flush-threshold-dumped 100 # (or more)
>> #flush-threshold-scheduled 100 # (or more)
>> #taperflush 100
>> #autoflush yes
>> --8<---cut here---end--->8---
>> helps to do better tape utilization.
>>
>> But how behave amanda in my configuration (+ these four lines above):
>>
>> I have defined 1gb vtapes, placed onto four hard disks rotated
>> (ie. first flush go to disk 1, second to 2, third to 3, fourth to 4,
>> fifth to 1, and so on)
>>
>> say on first disk are tapes: alfa-1-1 to alfa-1-10
>> on second:  alfa-2-1 to alfa-2-10
>> on third: alfa-3-1 to alfa-3-10
>> on fourth: alfa-4-1 to alfa-4-10
>>
>> One day dumps takes 1,5GB and goes to tape alfa-1-1 and (partially)
>> alfa-1-2.
> Amanda should not write to alfa-1-2 if the above setting are commented out.
> Are you using a holding a disk? It must be larger than a vtape (1gb).


My bad. I forgot to say that I have  runtapes greater than 1.
And my question is what amanda do if above flush settings are not
commmented.

KJ


-- 
http://blogdebart.pl/2009/12/22/mamy-chorych-dzieci/
Wiesz, tryb tekstowy w Linuksie ma się tak do DOSu
jak F-117A do paralotni. (c) Dawid Kuroczko



Re: flush-threshold-* parameters - some clarification needed.

2013-03-27 Thread Jean-Louis Martineau

On 03/27/2013 06:39 AM, Kamil Jońca wrote:

(This is duplicate mail, previously sent, but I weren't subscribed)
In some sites there is suggestion, that config:
--8<---cut here---start->8---
#flush-threshold-dumped 100 # (or more)
#flush-threshold-scheduled 100 # (or more)
#taperflush 100
#autoflush yes
--8<---cut here---end--->8---
helps to do better tape utilization.

But how behave amanda in my configuration (+ these four lines above):

I have defined 1gb vtapes, placed onto four hard disks rotated
(ie. first flush go to disk 1, second to 2, third to 3, fourth to 4,
fifth to 1, and so on)

say on first disk are tapes: alfa-1-1 to alfa-1-10
on second:  alfa-2-1 to alfa-2-10
on third: alfa-3-1 to alfa-3-10
on fourth: alfa-4-1 to alfa-4-10

One day dumps takes 1,5GB and goes to tape alfa-1-1 and (partially)
alfa-1-2.

Amanda should not write to alfa-1-2 if the above setting are commented out.
Are you using a holding a disk? It must be larger than a vtape (1gb).

Jean-Louis


flush-threshold-* parameters - some clarification needed.

2013-03-27 Thread Kamil Jońca
(This is duplicate mail, previously sent, but I weren't subscribed)
In some sites there is suggestion, that config:
--8<---cut here---start->8---
#flush-threshold-dumped 100 # (or more)
#flush-threshold-scheduled 100 # (or more)
#taperflush 100
#autoflush yes
--8<---cut here---end--->8---
helps to do better tape utilization.

But how behave amanda in my configuration (+ these four lines above):

I have defined 1gb vtapes, placed onto four hard disks rotated
(ie. first flush go to disk 1, second to 2, third to 3, fourth to 4,
fifth to 1, and so on)

say on first disk are tapes: alfa-1-1 to alfa-1-10 
on second:  alfa-2-1 to alfa-2-10 
on third: alfa-3-1 to alfa-3-10 
on fourth: alfa-4-1 to alfa-4-10 

One day dumps takes 1,5GB and goes to tape alfa-1-1 and (partially)
alfa-1-2.

Then, there were some later dupms that goes to tapes on disks 2,3,4 and
then I should use again disk 1. 
And does amanda fills alfa-1-2 or takes new tape (say alfa-1-3)?

KJ



-- 
http://blogdebart.pl/2009/12/22/mamy-chorych-dzieci/
Pick another fortune cookie.