Peter,

One thing I use is: The traditional backup schema is most likly always cyclic.
ADSM is not, it always takes care of the changes, new files and takes care of
deleted files, too.
It provides you all the time the ability to restore a "full" backup. How to
achive ? That
are ADSM Server tasks and intelligence , which are known to you. What greatly
helps in this regard is the clever/thinking file and media catalog: the ADSM
database which is actually a relational
database.

Cheers,

    a x e l

"Hough, Peter" wrote:

> I am a great fan of ADSM's incremental forever design. However, I sometimes
> have difficulty explaining the concept to users, particularly those IT
> people who are used to the traditional meaning of an incremental backup
> (i.e. something which has to be used with previous incrementals and a full
> backup).
> Does anyone have any material that they are prepared to share which explains
> the incremental forever concept in an easily understood manner?  Anything
> would be much appreciated since it is bound to be better than my attempts so
> far!!
>
> Peter Hough
> Guardian dr