What exactly does tapecycle do ? I have in my config
dumpcycle 2 weeks # the number of days in the normal dump cycle
runspercycle 10 # the number of amdump runs in dumpcycle days
# (2 weeks * 5 amdump runs per week -- just weekdays)
tapecycle 14 tapes # the number of tapes in rotation
I have 22 tapes labelled and in my tapelist - last night's backup used #14
and asked for #15 for tonight. From what I've read before, amdump will use
the last tape in the tapelist marked reuse (incidentally, every tape in my
tapelist is marked reuse - is that correct ?) so what exactly does the
tapecycle parameter do ? If there are less than tapecycle tape in the
tapelist will it force amdump to ask for a new one ?
A second (actually, third) before I lick the envelope :-)
I've got a large holding disk so I may well change runspercycle to 14 and
run amdump every day and then run amflush on Monday in order to have as many
backups as possible (and people may sometimes do some work at weekends). If
I do that and the amount of data in the two holding directories on Monday is
small enough, is it OK to amflush ALL to one tape or am I better off
flushing each day to a separate tape, which would give the same nett result
as if the tapes had been put in the drive over the weekend ?
Regards,
Niall O Broin
