d-something-I-shouldn't-have restores are handled by the Network
Appliance's snapshots, our backups are mostly for minor disaster
recovery (disk failure and the like) and we only need tapecycle >
runspercycle.
Tommy McGuire
ing
>> >characteristics:
>> > Full backup every Wednesday on a different weekly tape
>> > Differential backup on Thurday, Friday, Monday, and Tuesday
>> > Full backup on the last Wednesday of each month which is then
>> > archived for a year
Monthly" on the last Wednesday of the month.
>
>Does this sound like my configuration will do what I want? Or do I have
>something really messed up? Any comments or suggestions would be
>appreciated.
Comments or suggestions? You are trying to swim upstream.
Tommy McGuire
y is amcheck pushing so many requests at the
>client service? How many requests per minute should I allow for? And
>(total newbie-ness, sorry) how can I restart inetd with the added '-r'
>switch properly without *rebooting* the box? Can it just be started by
>hand "safely?"
>
>Thanks for any guidance!
>
>Jim
>
>
>
>
>
>
Tommy McGuire
stubborn to fix it. Tar is simply not a general-purpose replacement for
>something that backs up a whole filesystem without trashing the read
>dates on files - and in much less time.
>
Tommy McGuire
of tapes in rotation
[...]
(For yours, dumpcycle would be 4 weeks and runspercycle would be however
often in that time that you ran the Monthly configuration; once/week for
us.) Then in the dumptypes:
[...]
record no
skip-incr yes
[...]
The "record no" prevents updating /etc/dumpdates and the skip-incr
limits it to full dumps.
Tommy McGuire
