We have one machine with a very high change rate like this. We are successfully using -incrbydate on weekdays, and a regular incremental every weekend to catch up - exactly as suggested in the TSM manuals. It's made a big difference.
Roger Deschner University of Illinois at Chicago rog...@uic.edu === Allergy Warning: Produced in a facility that processes peanuts. ==== =================== -- warning on a sack of peanuts ==================== On Wed, 27 Oct 2010, Xav Paice wrote: >----- "cory heikel" <chei...@hmc.psu.edu> wrote: > >> I have many clients with an average daily change rate of over 50%. >> Most of these clients take several hours to back up and show a high >> percentage of wait time in the summary table. My question is this: >> Would it make sense for these clients to be backed up full each day >> instead of incremental? >> > >Without more detail, I'd suggest trying an online image backup of some >selected clients and see what difference it makes. You might find, however, >that there are pros and cons for image vs incremental - in terms of storage >used, performance of other operations during backup, and ability to restore >individual files. > >You could also consider using -incrbydate - just so long as you regularly do a >'normal' incremental since -incrbydate misses deleted files and isn't the most >secure option. > >Where is the delay though - have you looked at the instrumentation to >determine if it really is filesystem scanning that is the slow bit? >
