Symantec NETBACKUP 7 User Manual
Symantec NetBackup™ Deduplication Guide
Release 7.0
20654102
Symantec NetBackup™ Deduplication Guide
The softwaredescribed inthis bookis furnishedunder alicense agreementand maybe used
only in accordance with the terms of the agreement.
Documentation version 7.0
PN: 20654102
Legal Notice
Copyright © 2009 Symantec Corporation. All rights reserved.
Symantec, the Symantec Logo, Veritas, 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 DOCUMENTATIONISPROVIDED "ASIS" AND ALLEXPRESS ORIMPLIED 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 LEGALLYINVALID. SYMANTEC CORPORATIONSHALL NOT BELIABLE 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 LicensedSoftware andDocumentation aredeemed tobe commercialcomputer software
as definedin FAR 12.212 and subject to restricted rights asdefined inFAR Section52.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, displayor disclosure of the Licensed Software and Documentation bythe 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
Technical Support
Symantec Technical Support maintains support centers globally. Technical
Support’s primary role is to respond to specific queries about product features
and functionality.The Technical Support group also creates contentfor our online
Knowledge Base. The Technical Support group works collaboratively with the
other functional areas within Symantec to answer your questions in a timely
fashion. Forexample, theTechnical Supportgroup works with Product Engineering
and SymantecSecurity Response to provide alerting services andvirus definition
updates.
Symantec’s maintenance offerings include the following:
■ A range of support options that give you the flexibility to select the right
amount of service for any size organization
■ Telephone and Web-based support that provides rapid response and
up-to-the-minute information
■ Upgrade assurance that delivers automatic software upgrade protection
■ Global support that is available 24 hours a day, 7 days a week
■ Advanced features, including Account Management Services
For information about Symantec’s Maintenance Programs, you can visitour Web
site at the following URL:
www.symantec.com/techsupp/
Contacting Technical Support
Customers with a current maintenanceagreement may access Technical Support
information at the following URL:
www.symantec.com/techsupp/
Before contacting Technical Support, make sure you have satisfied the system
requirements that are listed in your product documentation. Also, you should be
at thecomputer on which the problem occurred, incase itis necessaryto replicate
the problem.
When you contact Technical Support, please have the following information
available:
■ Product release level
■ Hardware information
■ Available memory, disk space, and NIC information
■ Operating system
■ Version and patch level
■ Network topology
■ Router, gateway, and IP address information
■ Problem description:
■ Error messages and log files
■ Troubleshooting that was performed before contacting Symantec
■ Recent software configuration changes and network changes
Licensing and registration
If yourSymantec product requires registration or a licensekey, accessour technical
support Web page at the following URL:
www.symantec.com/techsupp/
Customer service
Customer service information is available at the following URL:
www.symantec.com/techsupp/
Customer Service is available to assist with the following types of issues:
■ Questions regarding product licensing or serialization
■ Product registration updates, such as address or name changes
■ General product information (features, language availability, local dealers)
■ Latest information about product updates and upgrades
■ Information about upgrade assurance and maintenance contracts
■ Information about the Symantec Buying Programs
■ Advice about Symantec's technical support options
■ Nontechnical presales questions
■ Issues that are related to CD-ROMs or manuals
Maintenance agreement resources
If you want to contact Symantec regarding an existing maintenance agreement,
please contact the maintenance agreement administration team for your region
as follows:
Additional enterprise services
Symantec offers a comprehensive setof services that allow you to maximize your
investment in Symantec products and to develop your knowledge, expertise, and
global insight, which enable you to manage your business risks proactively.
Enterprise services that are available include the following:
customercare_apac@symantec.comAsia-Pacific and Japan
semea@symantec.comEurope, Middle-East, and Africa
supportsolutions@symantec.comNorth America and Latin America
Symantec EarlyWarning Solutions
Managed Security Services
Consulting Services
Educational Services
To access more information about Enterprise services, please visit our Web site
at the following URL:
www.symantec.com
Select your country or language from the site index.
These solutions provide early warning of cyber attacks, comprehensive threat
analysis, and countermeasures to prevent attacks before they occur.
These servicesremove theburden ofmanaging andmonitoring securitydevices
and events, ensuring rapid response to real threats.
Symantec Consulting Services provide on-site technical expertise from
Symantec andits trustedpartners. SymantecConsulting Servicesoffer avariety
of prepackaged and customizable options that include assessment, design,
implementation, monitoring,and managementcapabilities. Each is focused on
establishing andmaintaining the integrity and availability of your IT resources.
Educational Services provide a full array of technical training, security
education, security certification, and awareness communication programs.
Contents
Technical Support ..... ..... ..... .... . .... . .... . .... ..... ..... .... . .... . .... ..... ..... .... . .... . .... . .... ..... ... 4
Chapter 1 Introducing NetBackup deduplication .. .... . .... . .... ..... ..... .. 11
About NetBackup deduplication ... ..... .... . .... . .... . .... ..... ..... .... . .... . .... ... 11
About NetBackup deduplication options ..... .... . .... . .... . .... ..... ..... ... 12
How deduplication works ... . .... ..... ..... .... . .... . .... ..... ..... .... . .... . .... 14
Chapter 2 Planning your deployment ... ..... .... . .... . .... . .... ..... ..... .... . .... . . 17
Planning your deduplication deployment .... .... . .... . .... . .... ..... .... . .... . ... 17
About the deduplication storage type . .... . .... . .... . .... ..... ..... .... . .... . .... . .. 19
About the NetBackup Media Server Deduplication Option .... . .... . .... . .... . 19
About deduplication servers ..... .... . .... . .... ..... ..... .... . .... . .... . .... ..... 21
About deduplication nodes .... ..... .... . .... . .... ..... ..... .... . .... . .... . .... ... 22
About deduplication server requirements ..... ..... .... . .... . .... . .... ..... . 23
About media server deduplication limitations ..... .... . .... . .... ..... ..... 23
About NetBackup Client Deduplication .... ..... ..... .... . .... . .... . .... ..... ..... .. 24
About client deduplication host requirements ..... .... . .... . .... . .... ..... 25
About client deduplication requirements ... . .... ..... ..... .... . .... . .... . ... 25
About client deduplication limitations . ..... .... . .... . .... . .... ..... ..... .... 26
About NetBackup Deduplication Engine credentials ..... .... . .... . .... . .... ... 26
About the network interface for deduplication ... . .... . .... ..... ..... .... . .... . .. 27
About firewalls and the deduplication hosts .... . .... . .... ..... ..... .... . .... . .... 27
About scaling deduplication .... . .... . .... . .... ..... ..... .... . .... . .... . .... ..... ..... . 27
About compression and encryption . .... . .... . .... . .... ..... ..... .... . .... . .... . .... 28
About optimized duplication of deduplicated data . .... ..... .... . .... . .... . .... . 28
Optimized deduplication copy requirements ..... .... . .... . .... . .... ..... .. 28
Optimized deduplication copy limitations . ..... .... . .... . .... ..... ..... .... . 31
About deduplication performance . . .... . .... ..... ..... .... . .... . .... . .... ..... ..... . 32
How file size may affect the deduplication rate . .... . .... ..... ..... .... . ... 33
Replacing the PureDisk Deduplication Option with Media Server
Deduplication on the same host ... . .... . .... . .... ..... ..... .... . .... . .... . .... . 33
Migrating from PureDisk to the NetBackup Media Server
Deduplication option ... . .... ..... ..... .... . .... . .... ..... ..... .... . .... . .... . .... . 34
Migrating from another storage type to deduplication ... . .... ..... ..... .... . . 35
Contents8
Chapter 3 Provisioning the storage ... ..... .... . .... . .... . .... ..... ..... .... . .... . .... . 37
About provisioning the storage . . .... . .... ..... ..... .... . .... . .... . .... ..... ..... .... . 37
About deduplication storage requirements .... .... . .... . .... ..... ..... .... . .... . . 37
About deduplication storage capacity .... ..... .... . .... . .... . .... ..... ..... .... . ... 38
About the deduplication storage paths ... ..... ..... .... . .... . .... . .... ..... ..... ... 38
Chapter 4 Installing deduplication ... ..... ..... .... . .... . .... . .... ..... .... . .... . .... . . 41
About installing deduplication .... . .... . .... ..... .... . .... . .... . .... ..... ..... .... . ... 41
About the deduplication license key .... ..... .... . .... . .... . .... ..... ..... .... . .... . . 42
Licensing NetBackup deduplication . .... . .... . .... ..... ..... .... . .... . .... . .... ..... 42
Replacing the deduplication storage server host computer ... . .... ..... ..... . 42
Uninstalling media server deduplication . .... ..... ..... .... . .... . .... . .... ..... ... 44
Chapter 5 Configuring deduplication . ..... .... . .... . .... . .... ..... ..... .... . .... . .... 47
Configuring deduplication ... ..... .... . .... . .... . .... ..... ..... .... . .... . .... ..... ..... 47
Configuring a deduplication storage server . .... ..... ..... .... . .... . .... ..... ..... 48
About deduplication pools . .... ..... ..... .... . .... . .... . .... ..... ..... .... . .... . .... . .. 49
Configuring a deduplication pool . . .... . .... . .... ..... ..... .... . .... . .... . .... ..... .. 50
Media server deduplication pool properties ..... .... . .... . .... . .... ..... .... 50
Configuring a deduplication storage unit .... . .... ..... ..... .... . .... . .... . .... .... 52
Deduplication storage unit properties . .... ..... .... . .... . .... . .... ..... ..... . 53
Deduplication storage unit recommendations ... ..... ..... .... . .... . .... . .. 54
Enabling client deduplication . ..... .... . .... . .... . .... ..... ..... .... . .... . .... . .... ... 56
Configuring backups . .... ..... ..... .... . .... . .... . .... ..... .... . .... . .... . .... ..... ..... . 56
Configuring optimized deduplication copy ... ..... ..... .... . .... . .... . .... ..... ... 57
Configuring optimized deduplication copy behavior .... . .... . .... ..... ..... ... 57
Adding a load balancing server . . .... . .... . .... ..... ..... .... . .... . .... ..... ..... .... . 58
About the deduplication configuration file . . .... . .... ..... ..... .... . .... . .... ..... 60
Editing the deduplication configuration file .... .... . .... . .... . .... ..... ..... .... . 60
pd.conf file settings . .... . .... . .... ..... .... . .... . .... . .... ..... ..... .... . .... . .... . 61
Reconfiguring the deduplication storage server and storage
paths ..... .... . .... . .... . .... ..... ..... .... . .... . .... ..... ..... .... . .... . .... . .... ..... . 63
Chapter 6 Managing deduplication ... .... . .... . .... . .... ..... ..... .... . .... . .... . .... . 65
Managing deduplication servers . .... . .... . .... ..... ..... .... . .... . .... . .... ..... .... 65
Changing deduplication storage server properties ... ..... .... . .... . .... . . 66
Deleting a deduplication storage server . . .... . .... ..... ..... .... . .... . .... ... 67
Determining the deduplication storage server state ... ..... .... . .... . .... 67
Getting the storage server configuration .... . .... . .... ..... ..... .... . .... . .. 68
Editing a storage server configuration file . . .... . .... ..... ..... .... . .... . ... 68
Setting the storage server configuration .... ..... ..... .... . .... . .... ..... .... 70
Deleting a load balancing server configuration file . . .... . .... ..... ..... .. 70
Removing a load balancing server .... . .... . .... ..... ..... .... . .... . .... ..... .. 70
Viewing deduplication storage servers . . .... . .... . .... ..... ..... .... . .... . ... 72
Viewing deduplication storage server attributes ... ..... ..... .... . .... . ... 72
Resetting the deduplication registry . ..... .... . .... . .... . .... ..... ..... .... . .. 73
Managing NetBackup Deduplication Engine credentials .... . .... . .... ..... ... 74
Adding NetBackup Deduplication Engine credentials .... . .... . .... ..... . 74
Changing NetBackup Deduplication Engine credentials . . .... ..... ..... . 75
Deleting credentials from a load balancing server . ..... ..... .... . .... . ... 75
Determining which media servers have deduplication
credentials .... . .... . .... . .... ..... ..... .... . .... . .... . .... ..... ..... .... . .... . .. 76
Managing deduplication disk pools . .... . .... . .... ..... ..... .... . .... . .... . .... ..... . 76
Changing deduplication disk pool properties .... . .... . .... . .... ..... ..... .. 76
Changing the deduplication pool state .... . .... ..... ..... .... . .... . .... . .... . 77
Changing the deduplication disk volume state . . .... . .... ..... ..... .... . ... 77
Deleting a deduplication pool .... ..... .... . .... . .... . .... ..... ..... .... . .... . ... 78
Determining the deduplication pool state ..... .... . .... . .... . .... ..... ..... . 78
Determining the deduplication disk volume state ... .... . .... . .... . .... ... 79
Viewing deduplication disk pools .... . .... ..... ..... .... . .... . .... . .... ..... ... 79
Monitoring deduplication activity ... ..... .... . .... . .... ..... ..... .... . .... . .... . .... 80
Monitoring the deduplication rates ... . .... . .... . .... ..... ..... .... . .... . .... . 80
Viewing disk reports ... .... . .... . .... . .... ..... ..... .... . .... . .... . .... ..... ..... .. 81
Monitoring deduplication processes ..... .... . .... . .... . .... ..... ..... .... . ... 83
Monitoring deduplication logs .... .... . .... . .... . .... ..... ..... .... . .... . .... ... 83
Monitoring deduplication storage capacity and usage ... . .... . .... ..... ..... .. 87
About deduplication capacity and usage reporting .... ..... ..... .... . .... 87
About deduplication container files . ..... ..... .... . .... . .... ..... ..... .... . ... 89
Viewing capacity within deduplication container files . .... ..... ..... .... 89
Deleting backup images .... . .... ..... ..... .... . .... . .... . .... ..... ..... .... . .... . .... . .. 90
Disabling deduplication for a client . ..... .... . .... . .... . .... ..... ..... .... . .... . .... 90
About maintenance processing .... . .... ..... ..... .... . .... . .... ..... ..... .... . .... . .. 90
9Contents
Chapter 7 Troubleshooting ... . .... . .... . .... ..... ..... .... . .... . .... ..... ..... .... . .... . .... 93
Troubleshooting installation issues . .... . .... . .... . .... ..... ..... .... . .... . .... ..... 93
Installation on SUSE Linux fails .... . .... . .... . .... ..... ..... .... . .... . .... . .... 93
Troubleshooting configuration issues . . .... . .... ..... ..... .... . .... . .... ..... ..... . 94
Cannot configure deduplication storage server . ..... .... . .... . .... ..... ... 94
The disk pool wizard does not display a volume . .... . .... ..... ..... .... . .. 95
Troubleshooting operational issues . .... . .... . .... . .... ..... ..... .... . .... . .... ..... 95
Verify that the server has sufficient memory . .... ..... ..... .... . .... . .... . 95
Backup jobs fail ... . .... . .... . .... ..... ..... .... . .... . .... . .... ..... ..... .... . .... . .. 96
Contents10
Volume state changes to DOWN when volume is
unmounted .... ..... .... . .... . .... . .... ..... ..... .... . .... . .... ..... ..... .... . .. 96
Errors, delayed response, hangs . ..... ..... .... . .... . .... . .... ..... ..... .... . ... 97
Viewing disk errors and events . ..... ..... .... . .... . .... ..... ..... .... . .... . .... . .... . 97
Deduplication event codes and messages ..... ..... .... . .... . .... ..... ..... .... . ... 97
Chapter 8 Disaster recovery . . .... ..... ..... .... . .... . .... ..... ..... .... . .... . .... . .... .... 103
Preparing for disaster . . .... . .... ..... .... . .... . .... . .... ..... ..... .... . .... . .... . .... . 103
Moving images off-site ... . .... ..... ..... .... . .... . .... . .... ..... .... . .... . .... . .... ... 103
Recovering from a deduplication storage server disk failure . .... ..... ..... 104
Recovering from a permanent deduplication storage server
failure .... ..... .... . .... . .... . .... ..... ..... .... . .... . .... . .... ..... ..... .... . .... . ... 105
Recovering the storage server after NetBackup catalog recovery . .... . ... 107
Chapter 9 Deduplication architecture ... .... . .... . .... ..... ..... .... . .... . .... . .... 109
Deduplication server components ... ..... ..... .... . .... . .... ..... ..... .... . .... . ... 109
Media server deduplication process . ..... .... . .... . .... . .... ..... ..... .... . .... . .. 111
Deduplication client components . ..... ..... .... . .... . .... . .... ..... ..... .... . .... . 114
Deduplication client backup process . .... . .... . .... . .... ..... ..... .... . .... . .... .. 114
About deduplication fingerprinting ... ..... .... . .... . .... . .... ..... ..... .... . .... . 117
Data removal process .... . .... . .... . .... ..... ..... .... . .... . .... . .... ..... ..... .... . ... 118
Index . . .... ..... ..... .... . .... . .... ..... ..... .... . .... . .... . .... ..... ..... .... . .... . .... . .... ..... ..... .... . .... . .... . .. 119
Chapter
Introducing NetBackup deduplication
This chapter includes the following topics:
■ About NetBackup deduplication
About NetBackup deduplication
The proprietary Symantec PureDisk deduplicationtechnology powersNetBackup
integrated deduplication.Symantec packagedPureDisk into modular components.
The components plug-in to NetBackup through the NetBackup OpenStorage
framework.
With thesecomponents, Symantec NetBackup provides the deduplication options
that let you deduplicate data everywhere, as close to the source of data as you
require.
Deduplication everywhere provides significant return on investment, as follows.
■ Reduce the amount of data that is stored.
1
■ Reduce backup bandwidth.
Reduced bandwidth can be especially important when you want to limit the
amount of data that a client sends over the network. Over the network can be
to a backup server or for image duplication between remote locations.
■ Reduce backup windows.
■ Reduce infrastructure.
Deduplicate on NetBackup clients
Deduplicate on NetBackup media
servers
Deduplicate on disk appliances by
using the OpenStorage option
Deduplicate using NetBackup
PureDisk, including at remote
offices
Introducing NetBackup deduplication
12
About NetBackup deduplication
About NetBackup deduplication options
Deduplication everywhere lets you choose at which point in the backup process
to perform deduplication. NetBackup can manage your deduplication wherever
you implement it in the backup stream.
Figure 1-1 shows the options for deduplication.
Table 1-1 describes the options for deduplication.
Figure 1-1
NetBackup deduplication
About NetBackup deduplication
13Introducing NetBackup deduplication
Table 1-1
NetBackup Client
Deduplication Option
NetBackup MediaServer
Deduplication Option
Appliance deduplication
NetBackup deduplication options
DescriptionType
With NetBackup client-side deduplication, clients deduplicate
their backup data and then send it directly to the storage
destination. A media server does not deduplicate the data.
NetBackup Client Deduplication is a useful deduplication
solution if a client host has unused CPU cycles or if the load
balancing servers are overloaded.
See “About NetBackup Client Deduplication” on page 24.
NetBackup clients send their backups to a NetBackup media
server, whichdeduplicates thebackup data.A NetBackupmedia
server hoststhe NetBackup DeduplicationEngine, which writes
the data to the storage and manages the deduplicated data.
NetBackup MediaServer Deduplicationis auseful deduplication
solution if a client does not have enough CPU cycles to
deduplicate its own data.
See “About the NetBackup Media Server DeduplicationOption”
on page 19.
The NetBackup OpenStorage option lets third-party vendor
appliances function as disk storage for NetBackup.
The disk appliance provides the storage and it manages the
storage. A disk appliance may provide deduplication
functionality. NetBackup backs up and restores client data and
manages the life cycles of the data.
Appliance deduplication is a storage optimization or reduction
strategy. It reduces the storage that you may require.
See “How deduplication works” on page 14.
Conversely, NetBackupintegrated deduplicationreduces storage
requirements and provides other benefits that a disk appliance
deduplication solution cannot.
See “About NetBackup deduplication” on page 11.
A CB D E A QB D L
Client files
to back up
A CB D E Q L
File 1 File 2
Data written
to storage
Introducing NetBackup deduplication
14
About NetBackup deduplication
Table 1-1
PureDisk deduplication
How deduplication works
Deduplication is a method of retaining only one unique instance of backup data
on storage media. Redundant data is replaced with a pointer to the unique data
copy. Deduplication occurs on both a file level and a file segment level. When two
or more files are identical, deduplication stores only one copy of the file. When
two or more files share identical content, deduplication breaks the files into
segments and stores only one copy of each unique file segment.
Deduplication significantly reduces the amount of storage space that is required
for the NetBackup backup images.
Figure 1-2 is a diagram of file segments that are deduplicated.
NetBackup deduplication options (continued)
DescriptionType
NetBackup PureDisk is a deduplication solution for
bandwidth-optimized backups of data in remote offices. You
can use PureDisk to reduce the amount of backup data that is
stored in a datacenter by NetBackup.
You use PureDisk interfaces to install, configure, and manage
the PureDisk servers, storage pools, and client backups. You do
not use NetBackup to configure or manage the storage or
backups.
PureDisk has its own documentation set.
See the NetBackup PureDisk Getting Started Guide.
A PureDisk storage pool can be a storage destination for both
the NetBackup Client Deduplication Option and the NetBackup
Media Server Deduplication Option.
Figure 1-2
File deduplication
About NetBackup deduplication
The following list describes how NetBackup derives unique segments to store:
■ The deduplication engine breaks file 1 into segments A, B, C, D, and E.
■ The deduplication engine breaks file 2 into segments A, B, Q, D, and L.
■ The deduplication engine stores file segments A, B, C, D, and E from file 1 and
file segments Q, and L fromfile 2. The deduplication engine does not store file
segments A, B, and D from file 2. Instead, it points to the unique data copies
of file segments A, B, and D that were already written from file 1.
More detailed information is available.
See “Media server deduplication process” on page 111.
15Introducing NetBackup deduplication
Introducing NetBackup deduplication
16
About NetBackup deduplication
Chapter
Planning your deployment
This chapter includes the following topics:
■ Planning your deduplication deployment
■ About the deduplication storage type
■ About the NetBackup Media Server Deduplication Option
■ About NetBackup Client Deduplication
■ About NetBackup Deduplication Engine credentials
■ About the network interface for deduplication
2
■ About firewalls and the deduplication hosts
■ About scaling deduplication
■ About compression and encryption
■ About optimized duplication of deduplicated data
■ About deduplication performance
■ Replacing thePureDisk Deduplication Option with Media Server Deduplication
on the same host
■ Migrating fromPureDisk to the NetBackup Media Server Deduplication option
■ Migrating from another storage type to deduplication
Planning your deduplication deployment
Table 2-1 provides an overview of planning your deployment of NetBackup
deduplication.
Planning your deployment
18
Planning your deduplication deployment
Table 2-1
Determine the storage type
Determine which type of
deduplication to use
Determine the requirements for
deduplication hosts
Determine the credentials for
deduplication
Deployment overview
Where to find the informationDeployment task
See “About the deduplication storage type”
on page 19.
See “Aboutthe NetBackupMedia ServerDeduplication
Option” on page 19.
See “About NetBackup Client Deduplication”
on page 24.
See “About deduplication servers” on page 21.
See “About deduplication server requirements”
on page 23.
See “About client deduplication host requirements”
on page 25.
See “About the network interface for deduplication”
on page 27.
See “About firewalls and the deduplication hosts”
on page 27.
See “About scaling deduplication” on page 27.
See “About deduplication performance” on page 32.
See “About NetBackup Deduplication Engine
credentials” on page 26.
encryption recommendation
Determine the requirements for
optimized duplication
Determine the storage
requirements and provision the
storage
See “About compression and encryption” on page 28.Read the compression and
See “About optimized duplication of deduplicated
data” on page 28.
See “About provisioning the storage” on page 37.
See “About deduplication storage requirements”
on page 37.
See “About deduplication storage capacity”
on page 38.
See “About the deduplication storage paths”
on page 38.
About the deduplication storage type
19Planning your deployment
Table 2-1
Replace a PDDO host or migrate
from PDDO to NetBackup
deduplication
Migrate from other storage to
NetBackup deduplication
Deployment overview (continued)
Where to find the informationDeployment task
See “Replacing the PureDisk Deduplication Option
with Media Server Deduplication on the same host”
on page 33.
See “Migratingfrom PureDiskto theNetBackup Media
Server Deduplication option” on page 34.
See “Migrating from another storage type to
deduplication” on page 35.
About the deduplication storage type
The deduplication storage type depends on the destination for the deduplicated
data, as follows:
■ The disk storage that is attached to a NetBackup media server.
If you use this destination, use this guide to plan, implement, configure, and
manage deduplicationand the storage. When you configure the storage server,
select Media Server Deduplication Pool as the storage type.
■ A PureDisk storage pool.
If you use a PureDisk storage pool, use the PureDisk documentation to plan,
implement, configure, and manage the storage.
NetBackup deduplication requires that PureDisk be at release 6.6 or later.
See the NetBackup PureDisk Getting Started Guide.
After you configure the storage, use this guide to configure backups and
deduplication in NetBackup. When you configure the storage server, select
PureDisk Deduplication Pool as the storage type.
You can use one or both of the destinations for NetBackup deduplication.
About the NetBackup Media Server Deduplication Option
NetBackup MediaServer DeduplicationOption existsin theSymantec OpenStorage
framework. A storage server writes data to the storage and reads data from the
storage; the storage server must be a NetBackup media server. The storageserver
hosts the core components of deduplication. Thestorage server also deduplicates
the backup data. It is known as a deduplication storage server.
Planning your deployment
20
About the NetBackup Media Server Deduplication Option
For a backup, the NetBackup client software creates the image of backed up files
as for a normal backup. The client sends the backup image to the deduplication
storage server, which deduplicates the data. The deduplication storage server
writes the data to disk.
See “About deduplication servers” on page 21.
The NetBackup Media Server Deduplication Option is integrated into NetBackup.
It uses the NetBackup administration interfaces, commands, and processes for
configuring andexecuting backups and for configuring and managing the storage.
Deduplication occurswhen NetBackup backs up a client toa deduplicationstorage
destination. You do not have to use the separate PureDisk interfaces to configure
and use deduplication.
The NetBackup Media Server Deduplication Option integrates with NetBackup
application agentsthat are optimized for theclient streamformat. Agents include
but are not limited to Microsoft Exchange and Microsoft SharePoint Agents.
Figure 2-1shows NetBackupmedia serverdeduplication. The deduplication storage
server isa mediaserver onwhich thededuplication corecomponents areenabled.
PureDisk
Plug-in
PureDisk
Plug-in
NetBackup
client
NetBackup
Deduplication
Engine
PureDisk
Plug-in
NetBackup
client
NetBackup
client
NetBackup
client
PureDisk
deduplication
pool
Media server
deduplication
pool
Deduplication storage
server
Load
balancing
servers
PureDisk
Plug-in
About the NetBackup Media Server Deduplication Option
21Planning your deployment
Figure 2-1
NetBackup media server deduplication
More detailed information is available.
See “Deduplication server components” on page 109.
See “Media server deduplication process” on page 111.
About deduplication servers
Table 2-2 describes the servers that are used for NetBackup deduplication.
Planning your deployment
22
About the NetBackup Media Server Deduplication Option
Table 2-2
Deduplication storage
server
Load balancing server
NetBackup deduplication servers
DescriptionHost
One hostfunctions asthe storageserver for a deduplication node;
that host must be a NetBackup media server. The storage server
does the following:
■ Writes the data to and reads data from the disk storage.
■ Manages that storage.
The storage server also deduplicates data. Therefore, one host
both deduplicates the data and manages the storage.
Only one storage server exists for each NetBackup deduplication
node.
You can use NetBackup deduplication with one mediaserver host
only: the media server that is configured as the deduplication
storage server.
You can configure other NetBackup media servers to help
deduplicate data. They perform file fingerprint calculations for
deduplication, and they send the unique results to the storage
server. These helper media servers are called load balancing
servers.
See “About deduplication fingerprinting” on page 117.
You configure load balancing servers when you configure the
deduplication storage server. Also, you can add a deduplication
server later to a deduplication node.
Load balancingservers alsoperform restoreand duplicationjobs.
Symantec recommends that you add load balancing servers only
after the storage server reaches maximum CPU utilization. For
more information about how to use load balancing servers, see
the following Symantec tech note:
http://entsupport.symantec.com/docs/338123
About deduplication nodes
A mediaserver deduplication node is a deduplication storageserver, loadbalancing
servers (ifany), the clients that arebacked up,and the storage. Each nodemanages
its own storage. Deduplication within each node is supported; deduplication
between nodes is not supported.
Multiple mediaserver deduplication nodes can exist. Nodes cannot share servers,
storage, or clients.
About the NetBackup Media Server Deduplication Option
About deduplication server requirements
All hosts that are used for deduplication must be NetBackup 7.0 or later. Hosts
include the master server, the media servers, and the clients.
The computer’sCPU andmemory constrainhow manyjobs canrun concurrently.
23Planning your deployment
Table 2-3
Deduplication server minimum requirements
RequirementHardware
CPU
Operating system
CPU speed is the mostimportant factor for performance. Minimum
CPU speed should be 2.2 GHz.
The deduplication storage server should have a minimum of 4 CPU
cores. Symantec recommends eight cores.
Symantec recommends Intel, AMD, and Sun SPARC processors (in
order of effectiveness).
Symantec recommends 4 GBs of memory minimum.RAM
The operatingsystem mustbe a supported 64-bit operating system.
For supported systems, see the NetBackup Release Notes.
Note: Symantec recommends that you do not use the master server as a
deduplication storageserver. Master server activity and media server deduplication
activity on the same host degrades performance.
Note: Symantec recommends that you do not use an existing media server for
deduplication. Similarly, Symantec recommends that you do not repurpose older
host hardware for deduplication.
About media server deduplication limitations
NetBackup media server deduplication and Symantec Backup Exec deduplication
cannot reside on the same host. If you use both NetBackup and Backup Exec
deduplication, each product must reside on a separate host.
NetBackup deduplicationcomponents cannotreside onthe same host as a PureDisk
Deduplication Option (PDDO) agent. Therefore, you cannot use the same media
server for both NetBackup deduplication and as a PDDO host.
You cannot upgrade to NetBackup 7.0 or later a NetBackup media server that
hosts a PDDO agent. If the NetBackup 7.0 installation detects the PDDO agent,
Planning your deployment
24
About NetBackup Client Deduplication
the installation fails. To upgrade a NetBackup media server that hosts a PDDO
agent, you must first remove the PDDO agent.
See the NetBackup PureDisk Deduplication Option (PDDO) Guide.
Deduplication within each media server deduplication node is supported; global
deduplication between nodes is not supported.
About NetBackup Client Deduplication
With normal deduplication, the client sends the full backup data stream to the
media server.The deduplication engine on the media serverprocesses the stream,
saving only the unique segments.
With NetBackup Client Deduplication, the client hosts the PureDisk plug-in that
duplicates the backup data. The NetBackup client software creates the image of
backed up files as for a normal backup. Next, the PureDisk plug-in breaks the
backup image into segments and compares them to all of the segments that are
stored inthat deduplicationnode. The plug-in then sends only theunique segments
to the NetBackup Deduplication Engine on the storage server. The engine writes
the data to a media server deduplication pool.
Client deduplication does the following:
■ Reduces network traffic. The client sends only unique file segments to the
storage server. Duplicate data is not sent over the network.
■ Distributes some deduplication processing load from the storage server to
clients. (NetBackup does not balance load between clients; each client
deduplicates its own data.)
Figure 2-2shows client deduplication. The deduplicationstorage serveris a media
server on which the deduplication core components are enabled.
PureDisk
Plug-in
NetBackup
deduplication
client
NetBackup
PureDisk
Deduplication
Engine
PureDisk
Plug-in
PureDisk
deduplication pool
Media server
deduplication pool
PureDisk
Plug-in
NetBackup
deduplication
client
PureDisk
Plug-in
NetBackup
deduplication
client
Deduplication storage
server
About NetBackup Client Deduplication
25Planning your deployment
Figure 2-2
NetBackup client deduplication
About client deduplication host requirements
About client deduplication requirements
More detailed information is available.
See “Deduplication client components” on page 114.
See “Deduplication client backup process” on page 114.
The operating system must be a supported 64-bit operating system.
For supported systems, see the NetBackup Release Notes.
All hosts that are used for client deduplication must be NetBackup 7.0 or later.
A media server deduplication pool or a PureDisk deduplication pool must be
configured. Storage units must be configured for the deduplication pool.
Planning your deployment
26
About NetBackup Deduplication Engine credentials
About client deduplication limitations
Client deduplication does not support multiple copies per job. For the jobs that
specify multiple copies, the backupimages are sent to the storage server and may
be deduplicated there.
Client deduplication does not support encryption.
Client deduplicationis not tolerant of high latency networkconnections. Therefore,
Symantec recommendsthat youuse NetBackupPureDisk forremote officebackups.
About NetBackup Deduplication Engine credentials
The NetBackup Deduplication Engine requires credentials. The deduplication
components use the credentials when they communicate with the NetBackup
Deduplication Engine.The credentials are for the engine, notfor the host on which
it runs.
You enter the NetBackup Deduplication Engine credentials when you configure
the storage server.
The following are the rules for the credentials:
■ For user names and passwords, you can use characters in the printable ASCII
range (0x20-0x7E) except for the following characters:
■ Asterisk (*)
■ Backward slash (\) and forward slash (/)
■ Double quote (")
■ Left parenthesis [(] and right parenthesis [)]
■ The user name can be up to 127 characters in length. The password can be up
to 100 characters in length.
■ Leading and trailing spaces and quotes are ignored.
■ The user name and password cannot be empty or all spaces.
Record and save the credentials in case you need them in the future.
Caution: You cannot change the NetBackup Deduplication Engine credentialsafter
you enter them. Therefore, carefully choose and enter your credentials. If you
must change the credentials, contact your Symantec support representative.
About the network interface for deduplication
About the network interface for deduplication
If the server host has more than one network interface, by default the host
operating system determines which network interface to use. However, you can
specify which interface NetBackup should use for the deduplication traffic.
To use a specific interface, enter that interface name when you configure the
deduplication storage server.
Caution: You cannot change the network interface after NetBackup configures
the deduplication storage server. Therefore, carefully enter the properties.
About firewalls and the deduplication hosts
If firewalls exist between the various deduplication hosts, open ports 10082 and
10102 between those hosts. Deduplication hosts are the deduplication storage
server, the load balancing servers, and theclients that deduplicate their owndata.
About scaling deduplication
27Planning your deployment
You can scale deduplication processing to improve performance by using load
balancing servers or client deduplication or both.
If youconfigure load balancing servers, those servers also perform deduplication.
The deduplication storage server still functions as both a deduplication server
and as a storage server. NetBackup uses standard load balancing criteria to select
a load balancing server for each job. However, deduplication fingerprint
calculations are not part of the load balancing criteria.
To completelyremove the deduplication storage server from deduplicationduties,
do the following for every storage unit that uses the deduplication disk pool:
■ Select Only use the following media servers.
■ Select all of the load balancing servers but do not select the deduplication
storage server.
The deduplication storage server performs storage server tasks only: storing and
managing the deduplicated data, file deletion, and optimized duplication.
If youconfigure client deduplication, the clientsdeduplicate their own data. Some
of the deduplication load is removed from the deduplication storage server and
loading balancing servers.
Symantec recommends the following strategies to scale deduplication:
Planning your deployment
28
About compression and encryption
■ For theinitial full backups of yourclients, use the deduplication 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 that client. If a media server deduplicates a client backup,
your restoresettings may require that the media serveralso beused for restores
to that client.
■ Enable client-side deduplication gradually.
If a client cannot tolerate thededuplication processing workload, 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
they occurduring theNetBackup deduplication process. If you compress orencrypt
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, you can use optimized duplication for
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
node for optimized deduplication copy. The requirements description follows the
figure.
Host A
PureDisk
Plug-in
NetBackup
Deduplication
Engine
PureDisk
Plug-in
Deduplication node A (source)
Deduplication node B
(destination)
PureDisk
Plug-in
Host B Host C
NetBackup
Deduplication
Engine
PureDisk
Plug-in
Host D
Host D is configured as a load balancing server for
node A
PureDisk
Plug-in
Host E
About optimized duplication of deduplicated data
29Planning your deployment
Figure 2-3
Optimized duplication copy example
The following are the requirements for optimized duplication:
■ The source images must be on a NetBackup media server deduplication pool.
■ The destinationdisk storage can be another MediaServer Deduplication Pool
or aPureDisk Deduplication Pool. The destination storage unit cannot be the
same as the source storage unit.
If thedestination is a PureDiskDeduplicationPool, thePureDisk environment
must be at release level 6.6 or later.
■ At least one media server must be common between the source deduplication
node and the destination, as follows:
■ If the destination is another Media ServerDeduplication Pool: Configure
a server in the destination deduplication node as a load balancing server
for the source storage server.
For example, Figure 2-3 shows two deduplication nodes. Host D from the
destination node is configured as a load balancing server for the source
node. It is the common host. The following Storage Server Configuration
Wizard screen shows the load balancing servers that are configured for
deduplication node A:
Planning your deployment
30
About optimized duplication of deduplicated data
■ If the destination is a PureDisk Deduplication Pool: Configure a media
server that accesses the PureDisk Storage Pool Authority host as a load
balancing server for the source storage server.
To use more than one media server for the optimized copy operation, each
additional one must be common between them .If you select more than one,
NetBackup balances the optimized copy job load among them.
■ All of the media servers that are selected in the destination storage unit must
be common with the source storage server.
In the storage unit for the destination disk pool, select Only usethe following
mediaservers. Then, select the media server or media serversthat arecommon
to both the source storage server and the destination storage server.
For example, the following figure shows the destination storage unit media
server selection for the optimized duplication that is show inFigure 2-3. Host
D is the only common host, so it is selected in the destination storage unit.
Loading...