■ Forthe initialfull backupsofyour clients,use thededuplication storageserver.
For subsequent backups, use load balancing servers.
Do not expect the deduplication storage server to be the media server that is
used for restores to thatclient. If a media server deduplicatesa client backup,
yourrestore settingsmayrequire thatthe mediaserveralso beused forrestores
to that client.
■ Enable client-side deduplication gradually.
If a client cannot tolerate thededuplication processingworkload, be prepared
to move the deduplication processing back to a server.
See “About deduplication performance” on page 32.
About compression and encryption
For compression or encryption, Symantec recommends that you enable them so
theyoccurduring theNetBackupdeduplication process.If youcompressor encrypt
the data before it is deduplicated, deduplication rates are low.
See “About the deduplication configuration file” on page 60.
See “Editing the deduplication configuration file” on page 60.
See “pd.conf file settings” on page 61.
About optimized duplication of deduplicated data
Optimized duplication of deduplicated data reduces the amount of data that is
transmitted over your network.Therefore, youcan useoptimized duplicationfor
off-site storage of data for disaster recovery. It can improve recovery times and
minimize the use of off-site tape storage.
Only the unique data segments are transferred.
See “Configuring optimized deduplication copy” on page 57.
Optimized deduplication copy requirements
Figure 2-3 shows a source deduplication node and a destination deduplication
nodefor optimizeddeduplicationcopy. Therequirementsdescription follows the
figure.
Planning your deployment
About compression and encryption
28