I decided to use our standard "1 full plus 9 differential" schedule.  The
main reason I chose this is to minimize the amount of meta-data written to
the AFTD on the NetWorker server.  Running a full backup every day, you
won't write any more data to the Avamar storage node, but NetWorker will
have to index every file on the client every day.

For every file "backed up", NetWorker stores a 100-200 byte file on the
NetWorker local AFTD.  This doesn't sound like a lot until you start backing
up millions of files every day.


On Fri, Jul 3, 2009 at 3:48 AM, JKK <johannes.karlsson AT skyrr DOT is> wrote:

> Hi.
>
> Those of you who have been using Avamar to de-duplicate data into
> networker, how do you configure your schedules?
>
> Do you treat the de-dup backups the same as the regular non-de-dup
> networker backups in respect to incremental and Full?
>
> Johannes
>
> To sign off this list, send email to listserv AT listserv.temple DOT edu and 
> type
> "signoff networker" in the body of the email. Please write to
> networker-request AT listserv.temple DOT edu if you have any problems with 
> this
> list. You can access the archives at
> http://listserv.temple.edu/archives/networker.html or
> via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
>

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER