[prev in list] [next in list] [prev in thread] [next in thread] 

List:       amanda-users
Subject:    The question about the 'force-bump' and the 'force-no-bump'
From:       "Takashi Kurakata" <t.kurakata () gmail ! com>
Date:       2007-09-27 7:35:33
Message-ID: d75cd1870709270035q667f0b34x48a3fed91d10b5af () mail ! gmail ! com
[Download RAW message or body]

Hi all

I think about the backup schedules as follow:

1st full backup(LV0)
2nd partial backup(LV1)
3rd partial backup(LV1)
4th partial backup(LV1)

'force', 'forcd-bump', and 'forcd-no-bump' each option of the amadmin
command had been executed specifying it before the
amdump command was executed.

1st
 $ amadmin DailySet_HD force rh5cli /var/test
 $ amdump DailySet_HD

2nd
 $ amadmin DailySet_HD force-bump rh5cli /var/test
 $ amdump DailySet_HD

3rd
 $ amadmin DailySet_HD force-no-bump rh5cli /var/test
 $ amdump DailySet_HD

4th
 $ amadmin DailySet_HD force-no-bump rh5cli /var/test
 $ amdump DailySet_HD

When the dumpcycle was '1 week' , the backup level was as follows:
1st full backup(LV0)
2nd partial backup(LV1)
3rd partial backup(LV1)
4th partial backup(LV1)

But the dumpcycle was '0', the backup level was as follow:
1st full backup(LV0)
2nd partial backup(LV1)
3rd full backup(LV0)
4th full backup(LV0)

In this case, is it a specification of amanda that the full backup is
executed because dumpcycle is 0 even if option 'force-no-bump' is executed?

Your prompt reply would be greatly appreciated.

Thanks in advance.

[Attachment #3 (text/html)]

Hi all<br><br>I think about the backup schedules as follow:<br><br>1st　full \
backup(LV0)<br>2nd　partial backup(LV1)<br>3rd　partial \
backup(LV1)<br>4th partial backup(LV1)<br><br>&#39;force&#39;, &#39;forcd-bump&#39;, \
and &#39;forcd-no-bump&#39; each option of the amadmin command had been executed \
specifying it before the  <br>amdump command was executed. <br><br>1st <br>&nbsp;$ \
amadmin DailySet_HD force rh5cli /var/test<br>&nbsp;$ amdump \
DailySet_HD<br><br>2nd<br>&nbsp;$ amadmin DailySet_HD force-bump rh5cli \
/var/test<br>&nbsp;$ amdump DailySet_HD<br><br>3rd<br> &nbsp;$ amadmin DailySet_HD \
force-no-bump rh5cli /var/test<br>&nbsp;$ amdump DailySet_HD<br><br>4th<br>&nbsp;$ \
amadmin DailySet_HD force-no-bump rh5cli /var/test<br>&nbsp;$ amdump \
DailySet_HD<br><br>When the dumpcycle was &#39;1 week&#39; , the backup level was as \
follows: <br>1st　full backup(LV0)<br>
2nd　partial backup(LV1)<br>
3rd　partial backup(LV1)<br>
4th partial backup(LV1)<br>
<br>But the dumpcycle was &#39;0&#39;, the backup level was as \
follow:<br>1st　full backup(LV0)<br>

2nd　partial backup(LV1)<br>

3rd　full backup(LV0)<br>

4th full backup(LV0)<br><br>In this case, is it a specification of amanda that the \
full backup is executed because dumpcycle is 0 even if option &#39;force-no-bump&#39; \
is executed?<br><br>Your prompt reply would be greatly appreciated. <br><br> Thanks \
in advance.<br>



[prev in list] [next in list] [prev in thread] [next in thread]