Deduplication PDF

NetBackup deduplication:
additional usage information

Symantec TECH77575
Revision 7.5A, for NetBackup 7.5

This document supplements the NetBackup 7.5
Deduplication Guide available at the following URL:
http://www.symantec.com/docs/DOC5138
This document is updated periodically.
Legal Notice
Copyright 2010 Symantec Corporation. All rights reserved.
Symantec, the Symantec Logo, and NetBackup are trademarks or registered trademarks of
Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be
trademarks of their respective owners.
The product described in this document is distributed under licenses restricting its use,
copying, distribution, and decompilation/reverse engineering. No part of this document
may be reproduced in any form by any means without prior written authorization of
Symantec Corporation and its licensors, if any.
THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS,
REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT,
ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO
BE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL
OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING,
PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED
IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.
The Licensed Software and Documentation are deemed to be commercial computer software
as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19
"Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights in
Commercial Computer Software or Commercial Computer Software Documentation", as
applicable, and any successor regulations. Any use, modification, reproduction release,
performance, display or disclosure of the Licensed Software and Documentation by the U.S.
Government shall be solely in accordance with the terms of this Agreement.
Symantec Corporation
350 Ellis Street
Mountain View, CA 94043
http://www.symantec.com
Contents
Chapter 1
Introduction
........................................................................... 5
About this tech note ....................................................................... 5
Chapter 2
New features and changes in NetBackup 7.5 ................. 7

New features and enhancements for NetBackup 7.5 ............................. 7
Chapter 3
More about deployment planning ..................................... 9

Currently supported deduplication systems ........................................ 9
About volume management for NetBackup deduplication .................... 10
About virtualized deduplication servers ........................................... 10
Guidelines for which type of deduplication to use ............................... 10
Client deduplication example ................................................... 11
Media server deduplication example .......................................... 13
About the test environment ........................................................... 15
Media server deduplication sizing ................................................... 15
Client data stream speed ......................................................... 16
Data ingest rate on servers ...................................................... 16
Media server CPU and deduplication .......................................... 17
Write speed to disk ................................................................. 19
Media server deduplication sizing example ....................................... 20
Data ingest rate example ......................................................... 20
Media server CPU example ....................................................... 21
Network capacity between the servers ....................................... 21
Performance test results ......................................................... 22
Client deduplication sizing ............................................................. 23
Client CPU and RAM usage ...................................................... 23
Client backup streams ............................................................. 25
About client-side deduplication at remote offices ............................... 25
Chapter 4
Revision history ................................................................... 27

Revision history table ................................................................... 27
Index
.................................................................................................................... 31
Contents
Chapter
Introduction
This chapter includes the following topics:
About this tech note

Note: This tech note is about deduplication integrated into NetBackup; it is not
about PureDisk deduplication.
Some of the sections in this tech note may be updates of sections in the NetBackup
Deduplication Guide. If possible, the new information in such sections will be
identified.
This tech note will be updated periodically. It includes a version number and a
revision history.
Introduction
Chapter
New features and changes

in NetBackup 7.5
New features and enhancements for NetBackup 7.5

The following deduplication features and improvements are included in the
NetBackup 7.5 release.
For more information about these features and enhancements, see the NetBackup
Deduplication Guide for 7.5:
NetBackup 7.5 new features and improvements:
Support for the AIX 5.3, 6.1, and 7.1 operating systems for deduplication servers
and for client-side deduplication.
64-TB support for media server deduplication pools.
Resilient network connections provide improved support for remote office

client deduplication.
iSCSI support for NetBackup deduplication.
Enhancements that improve restore and duplication performance.
Deduplication integrity enhancements.
Windows storage server performance enhancements.

Interprocess communication changes on Windows hosts improve performance
to be similar to UNIX and Linux hosts.
New features and changes in NetBackup 7.5

This change affects upgrades to NetBackup 7.5.
FlashBackup performance improvements.
Backup image delete and import performance improvements.
NetBackup now reserves 4 percent of the storage space for the deduplication
database and transaction logs rather than 10 percent.
A new stream handler for EMC NDMP.
Fibre Channel connections to NetBackup 5020 appliances. Fibre Channel is

supported on x86-64 hosts that run the Red Hat Enterprise Linux 5 or SUSE
Enterprise Linux Server 10 SP1 operating systems.
The performance of the first backup of a remote client can be improved by

seeding the fingerprint cache.
Garbage collection now occurs during regularly scheduled queue processing.

Therefore, the sched_GarbageCollection.log file no longer exists.
Chapter
More about deployment

planning
Currently supported deduplication systems
About volume management for NetBackup deduplication
About virtualized deduplication servers
Guidelines for which type of deduplication to use
About the test environment
Media server deduplication sizing
Media server deduplication sizing example
Client deduplication sizing
About client-side deduplication at remote offices
Currently supported deduplication systems

For currently supported operating systems, see the NetBackup 7.x Operating
System compatibility list at the following URL:
http://www.symantec.com/docs/TECH76648
10
More about deployment planning

About volume management for NetBackup deduplication
About volume management for NetBackup

deduplication
If you use a tool to manage the volumes for NetBackup Media Server
Deduplication Pool storage, Symantec recommends that you use the Veritas
Storage Foundation. Storage Foundation includes the Veritas Volume Manager
and the Veritas File System.
For supported systems, see the Storage Foundation hardware compatibility list
at the Symantec Web site:
http://www.symantec.com/
Note: Although Storage Foundation supports NFS, NetBackup does not support
NFS targets for Media Server Deduplication Pool storage. Therefore, Media
Server Deduplication Pool does not support NFS with Storage Foundation.
About virtualized deduplication servers

Symantec NetBackup supports the media server deduplication option (MSDO) in
virtual environments. Virtual machine requirements should meet or exceed the
server requirements for physical machines as documented in the NetBackup
Deduplication Guide. Symantec has developed and tested using VMware ESX
servers at versions 3.5 and 4.0 and recommends production environments at these
revisions or higher.

The following table provides some very general guidelines for the type of
deduplication to use. Many factors affect backup performance, so read the
information about sizing before deciding whether to use NetBackup media server
deduplication or NetBackup client deduplication.
See Media server deduplication sizing on page 15.
See Client deduplication sizing on page 23.
Table 3-1
Deduplication use cases
Use case
Deduplication type
Remote office backup
NetBackup Client Deduplication Option

(client-side deduplication) or PureDisk

Table 3-1
Deduplication use cases (continued)
Use case
Deduplication type
LAN connected file server
Database backups (if the database can

provide multiple channels or streams)
NetBackup Media Server Deduplication

Option
Virtual machine backup (a client in a VM)
Off-host virtual machine backups (vSphere) NetBackup Media Server Deduplication

Option
Network attached storage devices (NDMP)
NetBackup Media Server Deduplication

Option
Deduplication appliance already deployed
NetBackup OpenStorage option
The data that are provided in this document are averages derived from testing.
The data provide information you can use to help determine the requirements
for your deduplication environment and do not represent a commitment by
Symantec to specific performance objectives.
See Client deduplication example on page 11.
See Media server deduplication example on page 13.
Client deduplication example

Figure 3-1 shows where a network bottleneck occurs without client deduplication
.
Figure 3-2 shows that client deduplication can eliminate a network bottleneck.
11
12

Figure 3-1
Network bottleneck
NetBackup
clients
Bottleneck
NetBackup media
server
Figure 3-2
Client deduplication eliminates network bottleneck
NetBackup
deduplication
clients
No bottleneck!
NetBackup Media Server

Deduplication Pool
(also can be a PureDisk
Storage Pool)
Figure 3-3 shows that client deduplication may be a better solution in a Gigabit
Ethernet (GigE) network than media server deduplication. The figure shows
average performance with 80% deduplication. With client deduplication, backups
for 12 clients are three times as fast as using media server deduplication (282
MB/s versus 94 MB/s).

Figure 3-3
Client deduplication vs media server deduplication in a Gigabit

network
See Guidelines for which type of deduplication to use on page 10.
Media server deduplication example

In fast networks, media server deduplication may provide better overall
throughput. The following two figures show average throughput in a 10 GigE
network with one Linux client and a 90% deduplication rate. The client hosts a
database application that can provide 32 backup streams.
Figure 3-4 shows the average throughput for client deduplication from one to 32
streams at 90% deduplication.
Figure 3-5 shows the average throughput for media server deduplication from
one to 32 streams at 90% deduplication.
The information in these tables shows the following:
The network was not a bottleneck
NetBackup 7.0 client deduplication is optimal at two streams; three or more

does not provide significantly more backup throughput.
13
14

Media server deduplication in a 10 GigE network provides almost 1 GB/s

throughput. Media server deduplication leverages multiple cores and multiple
streams. Therefore, media server deduplication is a better solution for large
datasets in applications such as Oracle.
Figure 3-4
Client deduplication average throughput in a 10 GigE network
Figure 3-5
Media server deduplication average throughput in a 10 GigE network


The following describes the host used for the testing that is described in this
document.
Server pool:
Sun Fire x4600 servers with the following
4 dual-core AMD Opteron processor 8220 (2.8GHz)
16 GB RAM
Dual port Sun NXGE 10 Gbit/s Ethernet cards
Dual port 4 GB FC HBAs, both Qlogic and Emulex
Red Hat Enterprise Linux Server release 5.1
Client pool:
Sun Fire V245 servers with the following:
2 UltraSPARC-IIIi, 1504 MHz CPUs
4 GBs RAM
1 Gbit/s Ethernet connection
Dual port 4 GB FC HBAs, both Qlogic and Emule
SunOS 5.10 Generic_120011-14
Sun Fire x4200 servers with the following:
2 dual-core AMD Opteron processor 2220
8 GB RAM
1 Gbit/s Ethernet connection
SUSE Linux Enterprise Server 10

Because many factors affect performance, the performance affect of deduplication
cannot be specified absolutely. Testing has provided data from which Symantec
can provide guidelines to help you understand deduplication load on the storage
server and on load balancing servers.
15
16

Note: This information is provided as guidance only. It is not a guarantee by

Symantec of specific performance in any environment.
The following are the factors that most affect deduplication performance on media
servers:
The speed at which data streams from the clients.

See Client data stream speed on page 16.
Data ingest rate on the media server.

See Data ingest rate on servers on page 16.
CPU of the media servers.

See Media server CPU and deduplication on page 17.
Write speed to disk on the storage server.

See Write speed to disk on page 19.
See Guidelines for which type of deduplication to use on page 10.

See Media server deduplication sizing example on page 20.
Client data stream speed

The speed at which data can be streamed from the client to the storage server or
load balancing server depends on the client read speed and the network speed.
The clients and the network should be capable enough to support your performance
objectives.
The NetBackup SAN Client option can provide high streaming rates that can
improve the throughput, which may provide better backup throughput on database
application hosts.
Data ingest rate on servers

The data ingest rate is how much data the server can accept at any moment. The
server ingest rate is a function of the number of NICs (LAN) or the number of
HBAs (SAN) on the media server. NetBackup SAN Clients must have their data
deduplicated on the media server.
Table 3-2 shows some possible ingest rates for a 1 GigE network. This table can
help you extrapolate the number of NICs required for your performance objectives.
For example, an ingest rate of 210 MB/s requires at least 2 NICs on the media
server.

Table 3-2
Maximum possible ingest rates for 1 Gbit/s NIC
Number of 1 Gbit/s NICs
Ingest rate
115 MB/s
460 MB/s
Only 85% of network capacity is usable; the rest is lost as noise.

When source deduplication is enabled on clients, data traffic is reduced, perhaps
up to 10 times less data traffic occurs. A single 1 Gbit/s NIC may be sufficient for
ingest.
See Data ingest rate example on page 20.
Media server CPU and deduplication

The deduplication affect on the CPU depends on the following factors:
Clock speed and number of cores. The higher the individual clock speed, the
faster an individual backup stream. The more cores you have, the higher the
aggregated backup throughput.
The deduplication rate, which depends on the type of data. The higher the
deduplication rate, the lower the CPU affect; less data needs to be transferred,
encrypted, or compressed.
The speed at which you stream the data to the server. The faster the stream,
the higher the CPU utilization per core. Each stream is handled by one core.
The number of simultaneous backup streams. The more streams, the more
parallel deduplication calculations are performed and the greater the CPU
affect.
Compression. Compression reduces the throughput rate because CPU cycles

are consumed for compression.
The throughput data in this section are irrespective of network bandwidth. To

achieve best performance, the clients and the network must be able to deliver
enough data to fully use the CPU.
The deduplication services consume approximately 25% of CPU power for all
overhead. The overhead is independent from the backup stream processing.
Deduplication services must reside on the media server that hosts the storage and
cannot be moved to clients or load balancing media servers.
17
18

The following tables provide throughput information for a test environment that
uses Intel Architecture hosts with 2.8-GHz quad core CPUs. AMD and Intel
processor performance is similar.
Table 3-3 shows the average throughput per core.
Table 3-3
Average backup throughput per core with 2.8-GHz quad core CPU
Cores
0% deduplication
100% deduplication
50 MB/s
90 MB/s
Table 3-4 shows the average throughput per quad core CPU both for a storage
server and a load balancing server. (A NetBackup load balancing media server
provides performance similar to a NetBackup media server that hosts the PureDisk
Deduplication Option agent.)
Table 3-4
Average backup throughput per quad core 2.8-GHz CPU
Quad core
CPUs
Storage server
Storage server
Load balancing server Load balancing server
0% deduplication 100% deduplication
0% deduplication
100% deduplication
140 MB/s
275 MB/s
200 MB/s
360 MB/s
275 MB/s
550 MB/s
400 MB/s
720 MB/s
The speed of the throughput for a single stream is an important factor for
application database backups such as Oracle.
Table 3-5 shows the peak throughput per stream both for a storage server and a
load balancing server. (A NetBackup load balancing media server provides
performance similar to a NetBackup media server that hosts the PureDisk
Deduplication Option agent.) Backing up an Oracle database with a single stream
consumes one core of a 2.8-GHz quad core CPU. If the server has eight cores, the
stream consumes 12.5% of the processor.
Usually, Oracle is backed up by multiple parallel streams. On a single quad core
2.8-GHz CPU host with four streams, a stream rate of 90 MB/s saturates all four
cores. The host can back up an Oracle database with four streams at a rate of 360
MB/s (best case). If the media server has two quad core CPUs, the Oracle backup
consumes 50% of the processor but the backup finishes twice as fast as with a
single stream. (As a reminder, these numbers differ for each environment and
depend on the CPU speeds.)

Table 3-5
Approximate peak throughput per single stream on 2.8-GHz quad

core CPU
Number of Storage server

streams
0% deduplication
Storage server
Load balancing server Load balancing server
100% deduplication
0% deduplication
100% deduplication
200 MB/s
115 MB/s
230 MB/s
115 MB/s
The Sun T2000 processor has slower CPU clocks but more cores than Intel or
AMD. The single stream rate is lower, and therefore more streams are required
to achieve throughput similar to Intel and AMD processors. The following table
shows the average performance on a load balancing server.
Table 3-6
Throughput on a Sun T2000 load balancing server processor
Processor
8 streams
32 streams
Sun T2000
115 MB/s
460 MB/s
See Media server CPU example on page 21.

See Client CPU and RAM usage on page 23.
Write speed to disk

The higher the speed the write speed, the better. The required minimum write
speed is 130 MB/s. A write speed of 200 MB/s provided optimal performance in
the test environment.
An important point to remember is that only unique data is written to disk.
Throughput with a 90% deduplication rate is equivalent to writing to disk 10
times faster than backups without deduplication.
19
20


Note: This sizing example is for guidance only. The data provide information you
can use to help determine the requirements for your deduplication environment.
It does not represent a commitment by Symantec to specific performance
objectives.
The following subsections provide information about sizing for the following
example environment:
Total source data
100 TB
Daily data change rate
10%
Backup types
Weekly full, daily incremental
Weekly full window
24 hours
Daily incremental window
10 hours
Retention period
four weeks
The environment uses NetBackup media server deduplication.

See Media server deduplication example on page 13.
See Performance test results on page 22.
Data ingest rate example

The following are the ingest rates that are required to meet the example
environment performance objectives:
Weekly full
100 TB / (24x 3600) = 1213 MB/sec or 4.16 TB/hr
Daily incremental
10 TB / (10x3600) = 291 MB/sec or 1 TB/hr
Because 1 NIC supports up to 115 MB/s (after a 10% performance deduction for
noise or overhead), the following are required for the example environment:
11 NICs for weekly full backups.
At least 3 NICs for incremental backups.

You can spread the NICs across the deduplication servers or use faster HBAs on
the storage server.
See Data ingest rate on servers on page 16.
Media server CPU example

The following table shows the number of cores that are required to meet the
example environment performance objectives:
Table 3-7
Number of cores per ingest rate
Backup type
Ingest rate
Number of quad core processors
Weekly full
1213 MB/s
Daily incremental
291 MB/s
The following deduplication media servers are required:
Four for weekly full backups.
One for incremental backups.
You can use a combination of storage servers and loading balancing servers to
achieve the performance requirements. A storage server with two quad core
processors provides 280-MB/s throughput . A load balancing server with two quad
core processors provides 400-MB/s throughput. In this example, two storage
servers and two load balancing servers provide enough throughput (1360 MB/s)
to accommodate the ingest rate for the weekly full backup.
See Media server CPU and deduplication on page 17.
Network capacity between the servers

The following is the network capacity required to meet the example environment
performance objectives:
21
22

Minimum network capacity required
Table 3-8
Backup
Data
Deduplication
Data transferred
Window
Minimum network
capacity required
Weekly full
100 TB
93-95%
5-7 TB
24 hours
60-85 MB/s
Daily incremental
10 TB
80-90%
1-2 TB
10 hours
29-58 MB/s
The maximum effective transfer rate possible for a 1 Gbit/s NIC is 115 MB/s.
Therefore, a 1 gigabit Ethernet is sufficient bandwidth between the storage servers
and the load balancing servers.
Performance test results

For a four week retention, 48 TB of storage capacity is required.
Two NetBackup deduplication nodes, each managing 24 TBs, are required. Each
node contains the following servers:
One storage server with 2 quad core processors, 24 GBs of RAM, and 3 NICs.
One load balancing server with two quad core processors, 4 GBs of RAM, and
3 NICs.
Note: Each storage server and load balancing server pair is a separate deduplication
node. Deduplication between the two nodes does not occur.
In a Gigabit network, the following table shows the possible performance.
Table 3-9
1 GigE performance
Backup
Backup throughput
Wall clock time
Weekly full
1266 MB/s
23 hours
Daily incremental
812 MB/s
3.59 hours
In a 10 GigE network, the following table shows the possible performance.

Table 3-10
10 GigE performance
Backup
Backup throughput
Wall clock time
Weekly full
1344 MB/s
21.7 hours
Daily incremental
1344 MB/s
2.2 hours


Because many factors affect performance, the performance impact of deduplication
cannot be specified with absolute numbers. Testing has provided data from which
Symantec can provide some general guidelines to help you understand
deduplication load on the clients that deduplicate their own data.
Note: This information is provided as guidance only. It is not a guarantee by
Symantec of specific performance in any environment.
Based on information in the following subsections, Symantec can recommend the
following:
Avoid client deduplication for slow processors or for processors that rely on
more than two streams for maximum performance.
For client deduplication, focus on LAN optimization.
See About client-side deduplication at remote offices on page 25.

See Client backup streams on page 25.
Client CPU and RAM usage

For one data stream and one backup job, client deduplication uses one CPU core.
The following table shows some average usages.
Table 3-11
CPU utilization
Number of cores
Percent used
50%
23
24

Table 3-11
CPU utilization (continued)
Number of cores
Percent used
25%
12.5%
16
< 10%
The backup speed depends on the CPU type and clock speed. Intel and AMD
perform similarly. The new SPARC CPU performs similarly to the AMD and Intel
processors. The following table displays examples of backup speeds for these CPU
types .
Table 3-12
Backup speed
Deduplication rate AMD 2.8 GHz
UltraSPARC III 1.5

GHz
SPARC64 VII 2.52

GHz
0%
80 MB/s
22 MB/s
55 MB/s
90%
120 MB/s
45 MB/s
NA
100%
130 MB/s
70 MB/s
120 MB/s
Average RAM usage on a Linux client is approximately 500 MB. The following
table shows the RAM usage per number of streams; two is the optimal number of
streams for a client.
Table 3-13
Client RAM usage
Number of streams
MBs of RAM used
430
470
580
740
16
1080
32
1870

See Client backup streams on page 25.

Client backup streams

Two backup streams provide the optimal performance for clients.
See Figure 3-4 on page 14.
Table 3-14 shows the backup speed throughput at two streams, with a 25-30%
performance increase from adding the second stream.
Table 3-14
Backup speed and deduplication rate
Deduplication rate
One stream
Two streams
0%
80 MB/s
114 MB/s
90%
120 MB/s
173 MB/s
100%
130 MB/s
~ 200 MB/s


For the NetBackup 7.5, a new resilient network feature lets you configure
NetBackup to use resilient network connections. A resilient connection allows
backup and restore traffic between a client and NetBackup media servers to
function effectively in high-latency, low-bandwidth networks such as WANs. The
use case that benefits the most from a resilient connection is a client in a remote
office that backs up its own data (client-side deduplication).
For more information, see the NetBackup Deduplication Guide for 7.5:
25
26

Chapter
Revision history
Revision history table

Table 4-1
Revision history
Revision
Date
Description
February 1, 2010
Initial version.
February 8, 2010
Changed iSCSI section from supported to not supported as a storage destination.

Version A incorrectly stated that iSCSI was supported.
28
Revision history
Table 4-1
Revision history (continued)
Revision
Date
Description
April 1, 2010
Added CIFS and NFS as files systems that are not supported.
Added information about CPU attributes that are desirable for deduplication to
the following section in the deployment planning chapter: About deduplication
media server requirements.
Added the following to the deployment planning chapter: About deduplication
storage requirements, About deduplication storage capacity, About optimized
duplication of deduplicated data, and About NetBackup deduplication port
usage.
Added the following to the configuration updates chapter: Configuring optimized
duplication of deduplicated data.
Added the following to the operational updates chapter: Optimized duplication
fixes.
Added the following to the troubleshooting chapter: Duplication configuration
script log, Server not found, Database system error (220), Media open error
(83), Media write error (84), Cannot delete a disk pool, and Restoring files
at a remote site.
Also made various edits throughout the document.
July 14, 2010
Added the following to the deployment planning chapter: About deduplication

and SAN Client, About client-side deduplication at remote offices, and
Deployment best practices.
Added the following to the configuration chapter: Configuring optimized
synthetic backups for deduplication, Throttling optimized deduplication traffic,
Setting deduplication storage server attributes, Clearing deduplication storage
server attributes, Viewing deduplication storage server attributes, Setting
deduplication pool attributes, Clearing deduplication pool attributes, Viewing
deduplication pool attributes."
In the configuration chapter, changed Enabling compressing or encryption on
all clients to Enabling compression or encryption.
Added the following to the operational updates chapter: About storage unit
groups for deduplication, Deleting a deduplication server configuration file,
Resetting the deduplication registry, and Specifying the restore server.
Revision history
Table 4-1
Revision
Date
Description
September 24,
2010
The number of this document changed from Tech Note 338123 to TECH77575.
Removed sections from various chapter; they either no longer apply to the
NetBackup 7.0.1 release or were added to the 7.0.1 version of the NetBackup
Deduplication Guide.
Removed the following topics from the deployment planning chapter: About
deduplication storage requirements, About deduplication storage capacity,
About optimized duplication of deduplicated data, and About NetBackup
deduplication port usage, About deduplication and SAN Client, and
Deployment best practices.
Removed the following topics from the configuration chapter: Using an
alternate network interface for the deduplication storage, Configuring
optimized synthetic backups for deduplication, Throttling optimized
deduplication traffic, Enabling compression or encryption, Configuring
optimized duplication of deduplicated data,Setting deduplication storage
server attributes, Clearing deduplication storage server attributes, Viewing
deduplication storage server attributes, Setting deduplication pool
attributes, Clearing deduplication pool attributes, Viewing deduplication
pool attributes, About the deduplication storage server configuration file,
Setting NetBackup configuration options by using bpsetconfig, and
Reconfiguring the deduplication storage server and storage paths.
Removed the following topics from the operational updates chapter:
Optimized duplication fixes, About storage unit groups for deduplication,
About NDMP deduplication, About Windows System State deduplication,
About the optimal number of backup streams, About storage unit groups
for deduplication Performing maintenance manually, Resizing the storage
partition, Deleting a deduplication host configuration file, Resetting the
deduplication registry,Restoring files at a remote site, and Specifying the
restore server.
Removed the following topics from the troubleshooting chapter: Client
deduplication fails, Duplication configuration script log, Server not found,
Database system error (220), Media open error (83), Media write error
(84), About the deduplication host configuration file, Server not found
error, Storage full conditions, Cannot delete a disk pool, and
Deduplication fails after services are restarted or a domain controller is
restarted.
Deleted the troubleshooting chapter (no topics remain).
February 16, 2011 Added a new topic: About storage management for NetBackup deduplication.
April 13, 2011
Changed the Currently supported deduplication systems topic so it points at

the NetBackup 7 Operating System compatibility list.
29
30
Revision history
Table 4-1
Revision
Date
Description
June 20, 2011
Removed the reference to a fix in the Using an alternate network interface for
the deduplication storage topic.
7.1
February 10, 2012 Changed the revision numbering to match the NetBackup release level.
7.5A
February 10, 2012 Removed all information that applied to NetBackup 7.0, 7.0.1, and 7.1. That
information either does not apply to 7.5 or was added to the NetBackup
Deduplication Guide for release 7.5. Added new feature information for 7.5.
Index
B
backup
speed 24
C
client deduplication
guidelines 11
D
data ingest rate
example 20
guidelines 16
deduplication
CPU usage 23
RAM usage 24
sizing guidelines 23
storage management 10
F
file system
Veritas File System for deduplication storage 10
M
media server
sizing guidelines 15
write speed guidelines 19
media server deduplication
CPU example 21
CPU guidelines 17
guidelines 13
V
volume manager
Veritas Volume Manager for deduplication
storage 10

Deduplication PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Deduplication PDF

Uploaded by

Copyright:

Available Formats

NetBackup deduplication:

additional usage information

Revision 7.5A, for NetBackup 7.5

This document is updated periodically.

About this tech note ....................................................................... 5

New features and changes in NetBackup 7.5 ................. 7

More about deployment planning ..................................... 9

Revision history ................................................................... 27

About this tech note

About this tech note

New features and changes

New features and enhancements for NetBackup 7.5

New features and enhancements for NetBackup 7.5

64-TB support for media server deduplication pools.

Resilient network connections provide improved support for remote office

iSCSI support for NetBackup deduplication.

Enhancements that improve restore and duplication performance.

Deduplication integrity enhancements.

Windows storage server performance enhancements.

New features and changes in NetBackup 7.5

This change affects upgrades to NetBackup 7.5.

FlashBackup performance improvements.

Backup image delete and import performance improvements.

A new stream handler for EMC NDMP.

Fibre Channel connections to NetBackup 5020 appliances. Fibre Channel is

The performance of the first backup of a remote client can be improved by

Garbage collection now occurs during regularly scheduled queue processing.

More about deployment

Currently supported deduplication systems

About volume management for NetBackup deduplication

About virtualized deduplication servers

Guidelines for which type of deduplication to use

About the test environment

Media server deduplication sizing

Media server deduplication sizing example

Client deduplication sizing

About client-side deduplication at remote offices

Currently supported deduplication systems

More about deployment planning

About volume management for NetBackup

About virtualized deduplication servers

Guidelines for which type of deduplication to use

Deduplication use cases

Remote office backup

NetBackup Client Deduplication Option

More about deployment planning

Deduplication use cases (continued)

LAN connected file server

NetBackup Client Deduplication Option

Database backups (if the database can

NetBackup Media Server Deduplication

Virtual machine backup (a client in a VM)

NetBackup Client Deduplication Option

Off-host virtual machine backups (vSphere) NetBackup Media Server Deduplication

NetBackup Media Server Deduplication

Deduplication appliance already deployed

NetBackup OpenStorage option

Client deduplication example

More about deployment planning

Client deduplication eliminates network bottleneck

NetBackup Media Server

More about deployment planning

Client deduplication vs media server deduplication in a Gigabit