This will usually end in a longer story so i focus on some key issues:

1) NW can work with any device type that is supported by the OS (disk and 
tape). Avamar can only use its own node/disk system.

2) NW by itself does not dedupe the data - Avamar always uses client-site 
deduplication.

3) NW usually works with fast transport media SAN/LAN while Avamar (due to its 
nature) is ideal for remote offices (slow LAN or WAN).

4) Avamar is complementary to NW (you can use an Avamar system as a NW 
'device'). Due to the technology the other way does not make sense. 

5) NW & Avamar accomplishes NW client-site deduplication.
      - Very easy to implement.
      - Very good performance in backups and recoveries.
      - Caveats: 
           - So far NW does not easily report the protected save set size - 
only the metadata. This is confusing for statistical purposes. Fortunately, NMC 
has good tools to help here.
           - You must respect Avamar's maintenance window (at least 3 hrs) when 
you should not use it for backups.
           - The cloning of deduped save sets is pretty slow. For this purpose 
you should first backup to a standard AFTD (probably on a Data Domain).

+----------------------------------------------------------------------
|This was sent by carsten_reinfeld AT avus-cr DOT de via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------