The question about the 'force-bump' and the 'force-no-bump'
2007-09-27 03:34:09
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.
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
- The question about the 'force-bump' and the 'force-no-bump',
Takashi Kurakata <=
|
|
|