SOL90713 Quest NetVault SmartDisk 1.5.1 Installation Upgrade Guide Rev1 0 PDF

NSD-101-1.5.
1-EN-02 12/14/11
Quest
NetVault
SmartDisk
version 1.5.1
Installation/Upgrade Guide
2011 Quest Software, Inc.
ALL RIGHTS RESERVED.
This guide contains proprietary information protected by copyright. The software described in
this guide is furnished under a software license or nondisclosure agreement. This software may
be used or copied only in accordance with the terms of the applicable agreement. No part of this
guide may be reproduced or transmitted in any form or by any means, electronic or mechanical,
including photocopying and recording for any purpose other than the purchasers personal use
without the written permission of Quest Software, Inc.
Disclaimer
The information in this document is provided in connection with Quest products. No license,
express or implied, by estoppel or otherwise, to any intellectual property right is granted by this
document or in connection with the sale of Quest products. EXCEPT AS SET FORTH IN
QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR
THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY
EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL
QUEST BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL
OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS
OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF
THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED
OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties
with respect to the accuracy or completeness of the contents of this document and reserves the
right to make changes to specifications and product descriptions at any time without notice.
Quest does not make any commitment to update the information contained in this document.
If you have any questions regarding your potential use of this material, contact:
Quest Software World Headquarters
LEGAL Dept
5 Polaris Way
Aliso Viejo, CA 92656
email: legal@quest.com
For regional and international office information, refer to the web site (www.quest.com).
Trademarks
Quest, Quest Software, the Quest Software logo, and NetVault are trademarks and registered
trademarks of Quest Software, Inc. in the United States of America and other countries. For a
complete list of Quest Softwares trademarks, see http://www.quest.com/legal/trademarks.aspx.
Other trademarks and registered trademarks are property of their respective owners.
Patents
This product is protected by U.S. Patents # 5,250,687; 7,814,260; 7,913,043; and 7,979,650.
Protected by Japanese, E.U., French, and UK patents 1615131 and 05250687.0, and German
patent DE602004002858. Additional patents pending.
Chapter 1: Introducing Quest NetVault SmartDisk 7
Quest NetVault SmartDisk At a Glance ........................................................................ 7
Key Benefits ...................................................................................................................... 8
Feature List ....................................................................................................................... 9
Target Audience ................................................................................................................ 9
Recommended Additional Reading ................................................................................ 9
About Quest Software ...................................................................................................... 9
- Contacting Quest Software ............................................................................................................ 10
- Quest Support ................................................................................................................................ 10
Chapter 2: Understanding NVSD Architecture 11
NVSD Architecture An Overview ................................................................................ 11
Components .................................................................................................................... 12
- NVSD Instance .............................................................................................................................. 12
- NVSD Storage Pools ..................................................................................................................... 12
- Manifests ........................................................................................................................................ 13
- Processes ...................................................................................................................................... 13
Nondeduplicated Backup Process ................................................................................ 14
Nondeduplicated Restore Process ............................................................................... 15
Deduplicated Backup Process ...................................................................................... 16
Deduplicated Restore Process ...................................................................................... 18
Garbage Collection Process .......................................................................................... 19
Chapter 3: Planning Your NVSD Deployment 21
NVSD Deployment Strategy An Overview ................................................................. 22
Defining Which Data to Deduplicate ............................................................................. 22
- Identifying the Ideal Targets for Deduplication ............................................................................... 22
- Understanding the Cost of Restoring Deduplicated Data .............................................................. 23
- Identifying Targets for Nondeduplication ....................................................................................... 23
- Deduplicating Similar Data Together ............................................................................................. 23
- Separating vs. Combining Deduplicated Data in NVSD Instances ................................................ 23
Table of Contents
4
Determining the Size of the NVSD Deployment ...........................................................25
- Calculating NVSD License Capacity .............................................................................................. 25
- Calculating the Required Number of NVSD Instances .................................................................. 28
- Calculating the Total Required Physical Disk Space for Licensed Capacity ................................. 32
Choosing a Deployment Location for an NVSD Instance ............................................36
- Reviewing Deployment Options for NVSD Nondeduplicated Instances ........................................ 36
- Reviewing Deployment Options for NVSD Deduplicated Instances .............................................. 41
- Reviewing Deployment Options for Disaster Recovery ................................................................. 42
Defining an NVSD Storage Pool Strategy .....................................................................44
- Understanding Space Allocation for NVSD Storage Pools ............................................................ 44
- Understanding the Simplified Management Strategy ..................................................................... 46
- Understanding the Optimal Performance Strategy ........................................................................ 46
Chapter 4: Installing NVSD 49
Installing NVSD An Overview ......................................................................................49
System Requirements .....................................................................................................49
- Software Requirements ................................................................................................................. 49
- Hardware Requirements ................................................................................................................ 50
- Authentication Requirements ......................................................................................................... 51
Installing the NVSD Software .........................................................................................53
- Important Considerations ............................................................................................................... 53
- Installing on Linux or UNIX (Excluding Solaris) ............................................................................. 54
- Installing on Solaris (SPARC, x86, or x86-64) ............................................................................... 57
- Installing on Windows .................................................................................................................... 60
- Installing on Mac OS X .................................................................................................................. 68
Chapter 5: Completing the Installation Process 75
Updating the Storage Pool Directory Structure ............................................................75
Adding NVSD Devices to Your Backup Product ..........................................................75
Protecting the NVSD Unique Identity ............................................................................76
Chapter 6: Licensing NVSD 77
NVSD License Keys An Overview ...............................................................................77
Obtaining the NVSD Machine ID ....................................................................................77
Requesting a License Key ..............................................................................................78
Installing a License Key on Linux, UNIX, or Mac OS X ................................................78
Quest NetVault SmartDisk
5
Installing a License Key on Windows ........................................................................... 79
Chapter 7: Uninstalling NVSD 81
Preserving Data Before Removing NVSD ..................................................................... 81
Removing NVSD from Linux, UNIX (Excluding Solaris), or Mac OS X ...................... 81
Removing from Solaris (SPARC, x86, or x86-64) ......................................................... 82
Removing from Windows ............................................................................................... 82
Chapter 8: Reinstalling NVSD 85
Reinstalling NVSD An Overview ................................................................................. 85
Prerequisites for Reinstalling NVSD ............................................................................. 85
Reinstalling NVSD if identity.cfg is Available ............................................................... 86
Reinstalling NVSD if identity.cfg is Not Available ........................................................ 88
Chapter 9: Upgrading NVSD 91
Checking the Status and Taking the Device Offline .................................................... 91
Upgrading the NVSD Software ...................................................................................... 92
Chapter 10: Troubleshooting NVSD 93
Corrupted or Missing Installfiles Subdirectory Impedes Removal or Upgrade on
Windows .......................................................................................................................... 93
6
7
Chapter 1:
INTRODUCING QUEST
NETVAULT SMARTDISK
Quest NetVault SmartDisk At a Glance
Key Benefits
Feature List
Target Audience
Recommended Additional Reading
About Quest Software
Contacting Quest Software
Quest Support
1.1.0 Quest NetVault SmartDisk At a Glance
Quest NetVault SmartDisks (NVSDs) disk-based backup and data-
deduplication option reduces storage costs with its powerful byte-level, variable-
block-based software deduplication, which packs up to 12 times more protected
data into the same storage area for a 92% reduction in storage footprint. Hardware
costs are reduced by using existing storage infrastructure instead of requiring
specific drives or appliances. Seamless integration with other Quest products,
such as NetVault Backup (NVBU) and vRanger, speeds deployment while
simplified ease-of-use reduces the level of storage expertise required to perform
deduplicated disk-based backups.
To shrink backup windows with no additional impact on protected-server
resources, you can schedule NVSDs post-process deduplication option outside
the backup window.
With NVSD, administrators have increased choices, including the ability to deploy
multiple NVSD Instances to improve load balancing and performance; copy or
move data between NVSD Instances, to VTL, or to tape-based devices to place
redundant backups in offsite locations for failover and disaster-recovery purposes.
Chapter 1
Introducing Quest NetVault SmartDisk
8
1.2.0 Key Benefits
Reduces Storage Costs NVSD reduces storage costs with its byte-level,
variable-block-based deduplication option. This option packs up to 12 times
more protected data into the same storage area with the ability. It
accomplishes this by analyzing smaller amounts of data, thereby avoiding the
problem that occurs when fixed blocks mask changes and store duplicate
data as unique.
NVSD is hardware-agnostic and works on most file systems, so hardware
costs are reduced by using the existing storage infrastructure instead of
requiring you to acquire specific drives or appliances. The ability to add
additional file-system paths easily to NVSD Storage Pools reduces costs by
deferring storage expenditures into new budget periods when costs are lower
or budget restraints may be eased and also ensures that storage does not sit
unused.
Data stored in NVSD can have individual retention policies, which gives
administrators the flexibility to store the most recent copies on disk and move
older data to an offsite location or to less expensive storage. This provides a
foundation for Lifecycle Management, which further reduces costs with tiered-
storage deployments.
Shrinks Backup Windows To shrink backup windows with no additional
impact on protected-server resources, you can schedule NVSDs post-
process deduplication option outside the backup window.
Even if you do not use the optional NVSD deduplication feature, you will still
receive all the advantages of disk-based backup. For example, you can
perform more simultaneous backups with disk than you can by writing
backups to tape in a serial process. Completing your backups faster ensures
that the performance of the application, database, and files servers is not
impacted during business hours by overrunning backup windows.
Maximizes Flexibility Administrators are able to deploy multiple NVSD
Instances to distribute network, disk, and deduplication resources, which
improves load balancing and performance. Shared-storage support provides
the ability to share disk-based backup storage across heterogeneous
platforms, which provides a single data-protection solution.
Speeds Restores NVSD improves restore times because the data is
coming from random-access storage without having to find and mount tapes,
and then search for the correct tape position. The majority of restore requests
come in the first 14 to 30 days after backup. With disk-based backup, you can
minimize downtime with shorter Recovery Time Objectives (RTOs), and you
can focus on other critical tasks.
9
1.3.0 Feature List
Simplified disk-based backup
Byte-level, variable-block software-based deduplication
12-to-1 deduplication ratio
Hardware agnostic
Post-process deduplication
Rapid deployment with existing infrastructure
Seamless integration with other products, such as NVBU and vRanger
Job-level deduplication
Shared-storage support
Easily extendible
Retention-policy support
Heterogeneous-platform support
Web-based Distributed Authoring and Versioning (WebDAV)-authenticated
access
1.4.0 Target Audience
This guide is intended for backup administrators and other technical personnel
who are responsible for designing and implementing a backup strategy for the
organization. A good understanding of the operating system (OS) on which NVSD
is running is assumed.
1.5.0 Recommended Additional Reading
The following documentation is also available:
Quest NetVault SmartDisk Administrators Guide This guide describes how
to configure and work with NVSD.
Quest NetVault SmartDisk Supported Platforms This guide lists the
operating systems and versions supported by NVSD.
https://support.quest.com/Search/SearchDownloads.aspx
1.6.0 About Quest Software
Quest Software simplifies and reduces the cost of managing IT for more than
100,000 customers worldwide. Quests innovative solutions make solving the
toughest IT management problems easier, enabling customers to save time and
money across physical, virtual, and cloud environments. For more information
about Quest, go to www.quest.com.
Chapter 1
Introducing Quest NetVault SmartDisk
10
1.6.1 Contacting Quest Software
For regional and international office information, refer to the web site.
1.6.2 Quest Support
Quest Support is available to customers who have a trial version of a Quest
product or who have purchased a Quest product and have a valid maintenance
contract. Quest Support provides unlimited 24x7 access to SupportLink, Quest
Supports self-service portal. Visit SupportLink at http://support.quest.com.
From SupportLink, you can:
Retrieve thousands of solutions from the online Knowledge Base.
Download the latest releases and service packs.
Create, update, and review support cases.
For a detailed explanation of support programs, online services, contact
information, policies. and procedures, view the Global Support Guide. This guide
is available at: http://support.quest.com.
Email: info@quest.com
Mail: Quest Software, Inc.
World Headquarters
5 Polaris Way
Aliso Viejo, CA 92656
USA
Web site: www.quest.com
11
Chapter 2:
UNDERSTANDING NVSD
ARCHITECTURE
NVSD Architecture An Overview
Components
NVSD Instance
NVSD Storage Pools
Manifests
Processes
Nondeduplicated Backup Process
Nondeduplicated Restore Process
Deduplicated Backup Process
Deduplicated Restore Process
Garbage Collection Process
2.1.0 NVSD Architecture An Overview
NVBU is used as an example throughout this chapter; however, you can use any
product that works with NVSD.
Figure 2-1:
Instance
NetVault SmartDisk Instance
NetVault SmartDisk Storage Pools
Chapter 2
Understanding NVSD Architecture
12
2.2.0 Components
2.2.1 NVSD Instance
A NetVault SmartDisk Instance is comprised of one or more Storage Pools and a
set of processes that perform disk-based backups and byte-level, variable-block
software deduplication. You can deploy a single NVSD Instance on a dedicated
server, or another server or client, and it can accept data streams from
heterogeneous platforms. In addition, you can deploy multiple NVSD Instances to
distribute network, disk, and deduplication resources, which improves load
balancing and performance. When multiple NVSD Instances are deployed,
Storage Pools and processes are not shared across the multiple NVSD Instances.
2.2.2 NVSD Storage Pools
A NetVault SmartDisk Storage Pool is comprised of one or more file-system
volumes, which you can easily extend by adding additional file-system paths. Each
Storage Pool is associated with roles that it can perform. When configuring the
Storage Pool, you can specify the preferred roles or the roles not allowed.
Available roles include the Content Index (also referred to as Disk Index),
Staging Store (also referred to as Staging), Chunk Index, and Chunk Store (also
referred to as Storage). For example, Storage Pool A will be used for the Content
Index and the Chunk Index while Storage Pool B will only be used for the
Staging Store and Chunk Store. Storage Pool A can be comprised of fault-
tolerant disks with good random-access performance, while Storage Pool B is
comprised of fault-tolerant disks with good streaming performance. When NVSD is
analyzing the available Storage Pools, it chooses the optimal Storage Pool to use
based on available space, the defined roles, and the other current activity in the
NVSD Instance.
2.2.2.a Storage-Pool Roles
Content Index The NetVault SmartDisk Content Index role is the index
where the NVSD Instance tracks the data it is currently protecting and
whether it is stored in the Staging Store or the Chunk Store. The Content
Index is relatively small and should reside in a Storage Pool comprised of
fault-tolerant disks with good random-access performance.
Staging Store The NetVault SmartDisk Staging Store role is where all
nondeduplicated data streams are stored, whether they are awaiting post-
processing deduplication or were not selected for deduplication. Data
streams that were selected for deduplication are deleted from the Staging
Store after the post-processing deduplication is completed. The Staging
Store should reside in a Storage Pool comprised of fault-tolerant disks with
good streaming performance.
13
Chunk Index The NetVault SmartDisk Chunk Index role is a list of the
unique Chunks and where each Chunk is stored in the Chunk Store. There is
one Chunk Index per NVSD Instance. The Chunk Index should reside in a
Storage Pool comprised of fault-tolerant disks with good random-access
performance.
Chunk Store The NetVault SmartDisk Chunk Store role is where the
unique Chunks are stored. The Chunk Store should reside in a Storage Pool
comprised of fault-tolerant disks.
2.2.3 Manifests
Stored in an NVSD Storage Pool, a NetVault SmartDisk Manifest is an ordered
list of the Chunks that comprise the data stream. It is used during the
reconstruction of the data stream to ensure that the Chunks are reconstructed in
the correct order. There is one Manifest per data stream.
2.2.4 Processes
Storage Service The NetVault SmartDisk Storage Service listens on a
user-defined port for data flowing to and from NVSD. There is one Storage
Server process per data stream.
Deduplicator The NetVault SmartDisk Deduplicator performs byte-level,
variable-block software-based deduplication by breaking the data streams
into unique Chunks. The Deduplicator uses the Chunk Store Daemon (CSD)
to query the Chunk Index to determine if the Chunk is unique. When a
Chunk is found in the Chunk Index, the Chunk Store Daemon stores the
unique Chunk in the Chunk Store. There is one Deduplicator process per
data stream.
Chunk Store Daemon The NetVault SmartDisk Chunk Store Daemon is
the only process that writes to the Chunk Index and Chunk Store. There is
only one CSD per NVSD Instance. The CSD also manages the Garbage
Collection process.
percolatormonitor The percolatormonitor is a privileged process that
launches and monitors other NVSD Processes.
percolatorslave The percolatorslave is responsible for communication
routing. It routes messages between NVSD Processes on the local machine
and between NVSD and other remote servers.
logd The logd is the logging daemon that creates the NVSD logs and
stores them in an internal database. It also sends them to the applicable
system location, such as the Application log in the Windows Event Viewer.
superserver The superserver is the high-level manager of all other
processes. It coordinates operations, balances the load between file
systems, and schedules deduplication and Garbage Collection.
Chapter 2
14
winservicerunner On Windows, the winservicerunner runs the Windows
Service and launches the percolatormonitor.
2.3.0 Nondeduplicated Backup Process
Figure 2-2:
Back up data
without
deduplicating it
1. After the user initiates a nondeduplicated NVBU Backup that is targeted to an
NVSD Instance, the NVBU Client streams data on the user-defined port to
Storage Service.
2. The Storage Service stores the backup stream from the NVBU Client in the
Staging Store.
3. The Storage Service updates the Content Index to indicate where the
backup is stored in the Staging Store.
4. The Storage Service updates the NVBU Client to indicate that the backup
stream has been successfully stored.
5. The NVBU Client updates the NVBU Server with a Backup Completed job
status.
15
2.4.0 Nondeduplicated Restore Process
Figure 2-3:
Restore data
that was not
deduplicated
1. After the user initiates a restore of a nondeduplicated NVBU Backup that is
targeted to an NVSD Instance, the NVBU Client requests data on the user-
defined port from the Storage Service.
2. The Storage Service queries the Content Index to determine whether the
backup is stored in the Staging Store for nondeduplicated backups or the
Chunk Store for deduplicated backups.
3. The Storage Service retrieves the backup stream from the Staging Store
and streams the data to the NVBU Client.
4. On completion of restoring the backup stream, the NVBU Client updates the
NVBU Server with a Restore Completed job status.
Chapter 2
16
2.5.0 Deduplicated Backup Process
Figure 2-4:
Back up data
and
deduplicate it
1. After the user initiates a deduplication-enabled NVBU Backup that is targeted
to an NVSD Instance, the NVBU Client streams data on the user-defined
port to the Storage Service.
2. The Storage Service stores the backup stream from the NVBU Client in the
Staging Store.
3. The Storage Service updates the Content Index to indicate where the
backup is stored in the Staging Store.
4. The Storage Service updates the NVBU Client to indicate that the backup
stream has been successfully stored.
5. The NVBU Client updates the NVBU Server with a Backup Completed job
status.
A During the user-defined deduplication window, backup data is retrieved from
the Staging Store and sent to the Deduplicator.
17
B The Deduplicator performs byte-level, variable-block software-based
deduplication by breaking data streams into unique Chunks and sending
them to the Chunk Store Daemon.
C The Deduplicator creates a backup-specific Manifest, which is an ordered
list of Chunks that comprise the backup.
D The Chunk Store Daemon sends the unique Chunks to the Chunk Store
for storage and updates the Chunk Index to indicate where each Chunk is
stored in the Chunk Store.
E The Content Index is updated to indicate that the backup is stored in the
Chunk Store.
F The backup data stream is removed from the Staging Store.
Chapter 2
18
2.6.0 Deduplicated Restore Process
Figure 2-5:
Restore data
that was
deduplicated
1. After the user initiates a restore of a deduplicated NVBU Backup that is
targeted to an NVSD Instance, the NVBU Client requests the data on the
user-defined port from the Storage Service.
2. The Storage Service queries the Content Index to determine whether the
backup is stored in the Staging Store for nondeduplicated backups or the
Chunk Store for deduplicated backups.
3. The Storage Service queries the backups Manifest for the first or next batch
of Chunk Names in the backup.
4. The Storage Service queries the Chunk Store Daemon for the location of
the Chunks in the Chunk Store.
5. Using Chunk Names from the Manifest, the Chunk Store Daemon queries
the Chunk Index for pointers to the Chunks in the Chunk Store
6. The Chunk Store Daemon provides the Storage Service with the location of
the Chunks in the Chunk Store.
19
7. The Storage Service retrieves the Chunks from the Chunk Store and
streams the Chunk to the NVBU Client.
Step 4 through Step 7 repeat for each batch of Chunk Names in the
Manifest.
8. On completion of restoring all Chunk Names in Manifest, the NVBU Client
updates the NVBU Server with a Restore Completed job status.
2.7.0 Garbage Collection Process
When backups targeted to NVSD are retired, the data is removed from the backup
database; however, the unique chunks are not automatically removed from the
Chunk Store. The NVSD Garbage Collection process is designed to remove
orphaned chunks from the Chunk Store and reclaim disk space.
Garbage Collection cannot run at the same time as deduplication. During the
configured Garbage Collection window, data waiting for deduplication will be
queued until Garbage Collection has completed. By default, the Garbage
Collection window is from 13:00 through 19:00 on Monday through Thursday;
however, you can revise this (for more information, refer to the Quest NetVault
SmartDisk Administrator's Guide). Outside the Garbage Collection window,
Garbage Collection is only started if no data is being deduplicated or is queued for
deduplication. If data becomes available for deduplication outside the Garbage
Collection window and Garbage Collection is active, Garbage Collection is
stopped and deduplication proceeds.
Garbage Collection does add additional disk-access overhead to NVSD
operations, which reduces performance while it runs. Quest Software
recommends scheduling Garbage Collection on a regular basis to avoid delays
associated with collecting large amounts of data.
Note: If a backup job that uses deduplication is aborted, be aware that the Chunk
Store space used by segments that have already been deduplicated is not
reclaimed until the next Garbage Collection (GC) occurs. Space used by the
Staging Store and license enforcement is reclaimed immediately.
Chapter 2
20
21
Chapter 3:
PLANNING YOUR NVSD
DEPLOYMENT
NVSD Deployment Strategy An Overview
Defining Which Data to Deduplicate
Identifying the Ideal Targets for Deduplication
Understanding the Cost of Restoring Deduplicated Data
Identifying Targets for Nondeduplication
Deduplicating Similar Data Together
Separating vs. Combining Deduplicated Data in NVSD Instances
Determining the Size of the NVSD Deployment
Calculating NVSD License Capacity
Calculating the Required Number of NVSD Instances
Calculating the Total Required Physical Disk Space for Licensed Capacity
Choosing a Deployment Location for an NVSD Instance
Reviewing Deployment Options for NVSD Nondeduplicated Instances
Reviewing Deployment Options for NVSD Deduplicated Instances
Reviewing Deployment Options for Disaster Recovery
Defining an NVSD Storage Pool Strategy
Understanding Space Allocation for NVSD Storage Pools
Understanding the Simplified Management Strategy
Understanding the Optimal Performance Strategy
Chapter 3
Planning Your NVSD Deployment
22
3.1.0 NVSD Deployment Strategy An Overview
An NVSD Deployment Strategy is comprised of multiple components, which you
define prior to installing NVSD. To ensure a successful deployment, complete the
following steps, which are described in detail in subsequent sections:
1. Define the data that you want to deduplicate.
2. Calculate the size of your NVSD Deployment.
3. Define the deployment location of the NVSD Instance.
4. Define a strategy for the NVSD Storage Pools.
NVBU is used as an example throughout this chapter; however, you can use any
product that works with NVSD.
3.2.0 Defining Which Data to Deduplicate
The first step in defining your NVSD Deployment Strategy is determining which
data to deduplicate. Not all data benefits from deduplication; therefore, it is
important to determine which data will be targeted to use NVSDs Deduplication
Option to reduce its storage footprint.
3.2.1 Identifying the Ideal Targets for Deduplication
High deduplication ratios are achieved when multiple generations of the same
data are targeted for the same NVSD Instance. Data that is an ideal target for
deduplication includes the following:
Structured databases, such as Oracle and SQL Server databases that are
protected by Quest NetVault Backup (NVBU) Plug-ins.
Unstructured file-system data, such as data that is stored on File Servers
protected by NVBU Plug-in for FileSystem.
Workstation data, such as desktops and laptops protected by NVBU
Workstation Client.
Virtual Machine (VM) images from the same OS and similar applications,
such as those protected by vRanger or NVBU Plug-ins for VMware and
Hyper-V.
Email servers, such as Exchange and Domino systems that are protected by
NVBU Plug-ins for Exchange and Domino.
Note: While email is an ideal target for deduplication, Single Instance Store (SIS),
such as that provided by Exchange, will reduce deduplicated data; therefore, the
deduplication ratio for the email server will not be as high as other types of data.
23
3.2.2 Understanding the Cost of Restoring Deduplicated Data
While data deduplication reduces storage costs by reducing the storage footprint,
there is a cost incurred during the restore processes. During the restoration of a
deduplicated backup, NVSD has to reassemble the chunks as it restores the data.
This reassembly process, also called rehydration, lengthens the time to restore
the data. Therefore, if the Recovery Time Objective (RTO) is important for a
specific database, email, or file system, you must consider the trade-off between
reducing storage costs and increasing RTO when you identify which data to
deduplicate.
3.2.3 Identifying Targets for Nondeduplication
Data that does not deduplicate well and should not be deduplicated includes:
Encrypted data (this is because the data stream is unique)
Data with demanding RTOs
3.2.4 Deduplicating Similar Data Together
You can increase deduplication ratios by targeting backups from the same
database, file system, or application to the same NVSD Instance. When a backup
is deduplicated and a previous backup from the same database, file system, or
application has already been deduplicated by the NVSD Instance, only the unique
or new chunks that did not exist in the previous backup will have to be stored in
the Chunk Store. If a previously deduplicated backup does not exist in the NVSD
Instance, the majority of the backup is considered unique data, which increases
the number of unique chunks that have to be stored in the Chunk Store.
When targeting backups to NVSD Instances, deduplication ratios will decline if
backups are targeted to random NVSD Instances. Quest Software recommends
that you target backups from the same database, file system, or application to the
same NVSD Instance.
3.2.5 Separating vs. Combining Deduplicated Data in NVSD
Instances
An entire NVSD is licensed as either nondeduplicated or deduplicated capacity.
When the data stored in NVSD is a combination of nondeduplicated and
deduplicated data, two deployment options are available:
Create separate NVSD Instances, one for nondeduplicated data and one for
deduplicated data.
Create a single NVSD Instance in which nondeduplicated and deduplicated
data reside together in the Storage Pools.
Chapter 3
24
3.2.5.a Using Separate NVSD Instances for Nondeduplicated and
Deduplicated Data
When the data targeted for NVSD is a combination of nondeduplicated and
deduplicated data, you can create multiple NVSD Instances: one for
nondeduplicated data and one for deduplicated data. In this case, the
Nondeduplicated Instance is licensed as NVSD Capacity and the Deduplicated
Instance is licensed as NVSD Capacity with Deduplication Option.
This option lets you purchase the Deduplication Option for only the capacity that
will be deduplicated. In this type of deployment, it is your responsibility to ensure
that the correct NVSD Instance is targeted for backup. This ensures that data
intended for deduplication is deduplicated and that data not intended for
deduplication is stored as nondeduplicated data.
Advantages
The Deduplication Option only has to be purchased for deduplicated NVSD
capacity, which is more cost effective.
Nondeduplicated NVSD Instances have lower hardware requirements.
Disadvantages
You must deploy and manage multiple NVSD Instances.
Backups must explicitly target a deduplicated or nondeduplicated NVSD
Instance or Device to ensure that data gets deduplicated or not.
3.2.5.b Using a Single NVSD Instance for Nondeduplicated and
Deduplicated Data
When the data targeted for NVSD is a combination of nondeduplicated and
deduplicated data, you can create a single NVSD Instance.
This option requires that you purchase the Deduplication Option for the entire
NVSD Instance, including the capacity for the backups that are not deduplicated.
Advantages
Simplifies deployment by reducing the number of NVSD Instances.
Backups can target the same NVSD Instance whether or not the backup is
enabled for deduplication.
Disadvantage
The NVSD Deduplication Option must be purchased for both
nondeduplicated and deduplicated NVSD Capacity.
25
3.3.0 Determining the Size of the NVSD Deployment
The second step in defining your NVSD Deployment Strategy is to determine the
size of your NVSD Deployment. To determine the size of your deployment,
complete the following steps, which are described in detail in subsequent sections:
1. Calculate the NVSD Licensed Capacity.
2. Calculate the required number of NVSD Instances.
3. Calculate the total required physical disk space for licensed capacity.
3.3.1 Calculating NVSD License Capacity
NVSD is licensed based on the Logical Capacity or Total Size (before
deduplication) of all backups stored in NVSD.
NVSD provides the ability to deploy multiple instances, which can be targeted for
backup from multiple servers. When calculating the licensed capacity for NVSD,
the capacity across all deployed NVSD Instances must be included. For example,
if two servers are targeting backups to one or more NVSD Instances, the capacity
of the backups from both servers must be included in the calculation.
NVSD Licensed Capacity is not based on the following:
The actual size of the Storage Pool, Staging Store, or Chunk Store.
The actual size of the backups after deduplication.
Before calculating the required NVSD Capacity, ensure that the backups being
targeted to NVSD are compatible with NVSD. For more information, refer to the
Quest NetVault SmartDisk Release Notes.
Calculating NVSD Capacity requires the collection of the following values for each
server that will target backups to NVSD. When inserting these values into the
calculations be sure to include the sum of the values across all servers that will
target backups to NVSD. For example, if NVBU Server 1s Size of Weekly
Backups is 40GB and NVBU Server 2s is 60GB, use 100GB as the Size of the
Weekly Full Backups.
If separate NVSD Instances for Nondeduplicated and Deduplicated Data will be
used, perform the following calculations separately for the backups that will not be
deduplicated versus the backups that will be deduplicated. This enables you to
determine how much NVSD Nondeduplicated capacity needs to be licensed and
how much capacity needs to be licensed for the NVSD Deduplication Option.
If a single NVSD Instance will be used for both nondeduplicated and deduplicated
data, include both the values for nondeduplicated and deduplicated data in the
single calculation.
Note: Be aware of the differences between Growth Rate and Change Rate.
Change Rate refers to the frequency with which blocks change in a volume.
Chapter 3
26
Growth Rate refers to the frequency at which new blocks are added to a volume.
Although Change Rate includes all blocks associated with Growth Rate, Growth
Rate does not necessarily include all blocks associated with Change Rate.
Size of Weekly Full Backups This is the size of all Full Backups that will
be targeted to NVSD. For example, if SQL Server, Exchange, Oracle, and
File System backups will be targeted for NVSD, calculate the total size of all
the Full Backups for SQL Server, Exchange, Oracle, and File System.
Weekly Full Backup Growth Rate This is the average weekly growth rate
of the Full Backups that are included in the Size of Weekly Full Backups
calculation. Weekly Full Backup Growth Rate is critical to determining the
size the NVSD Deployment. For example, the average of all Full Backups is
growing 10% each week. Another method for calculating this is to base it on
annual data growth. For example, an annual growth rate of 100%, or an
annual doubling of data, represents a weekly growth rate of 1.333%.
Weekly Full Backup Retention Period in Weeks This is the number of
weeks that Full Backups are retained in NVSD. Restores are faster when
performed from disk-based media than when performed from tape-based
media. Increasing the amount of protected data that is available on disk-
based media increases the number of restore scenarios that can be
performed from disk-based media. Requiring tapes to be located, retrieved,
and loaded to perform a restore slows down the restore speed and increases
downtime.
Additionally, when performing deduplication, the longer the data is retained in
NVSD, the better the deduplication ratios will be because more duplicate
chunks are found thereby enabling the ability to pack more data into the same
storage footprint. This enables even more protected data to be available via
disk-based media.
To obtain the most ideal deduplication ratios, Quest Software recommends a
retention period of 12 weeks or more.
Size of Daily Backups This is the size of all Daily Backups that will be
targeted to NVSD. For example, if SQL Server, Exchange, Oracle, and File
System backups will be targeted for NVSD, calculate the total size of all
Incremental Backups for SQL Server, Exchange, Oracle, and File System.
Daily Backups are interim backups created between the Weekly Full
Backups. These are anticipated to be Incremental or Differential Backups,
and as such, will generally be much smaller than the Weekly Full Backups.
Daily Backup Growth Rate This is the average daily growth rate of Daily
Backups that are included in the Size of Daily Backups. For example, the
average of All Daily Backups is growing 1% each day.
Number of Daily Backups between Full Backups This is the number of
Daily Backups that are performed between Full Backups. For example, if Full
27
Backups are performed on Sunday and Daily Backups are performed every
day, Monday through Saturday, the Number of Daily Backups is six.
Daily Backup Retention Period in Weeks This is the number of weeks
that Daily Backups will be retained in NVSD. Daily Backups provide the ability
to perform fixed-point-in-time restores, thereby reducing the RTO. Daily
Backups can be retained for the same period as Full Backups, which enables
fixed-point-in-time restores for the entire Weekly Full Backup Retention
Period. Fixed-point-in-time restores are typically performed using backups
taken within the last four weeks. As such, it is possible to retain Weekly Full
Backups for one retention period and Daily Backups for a shorter period. This
allows you access to Daily Backups for a set period, such as four weeks,
while providing you access to Full Backups to a longer period, such as 12
weeks.
3.3.1.a Using the Logical-Capacity Formula
Use the following formula to calculate the total amount of NVSD Capacity that is
required for all servers that will target backups to NVSD.
You can determine the Logical Capacity by calculating the Full Backup Capacity,
calculating the Daily Backup Capacity, and adding the totals.
Total NVSD Capacity to License = Full Backup Capacity + Daily Backup Capacity
Full Backup Capacity
Daily Backup Capacity
Alternatively, you can use the Quest NetVault SmartDisk Sizing Calculator to
perform this calculation. The Quest NetVault SmartDisk Sizing Calculator is
available from your Quest Software representative.
(Size of Weekly Full Backups)
* ((1+ Weekly Full Backup Growth Rate) ^ (Weekly Full
Backup Retention Period + 1)
- 1.0) / (Weekly Full Backup Growth Rate)
(Size of Daily Backups)
* (((1 + Daily Backup Growth Rate) ^ ((Daily Backup
Retention Period + 1)
* Number of Daily Backups between Weekly Backups)) - 1.0)
/ (Daily Backup Growth Rate)
Chapter 3
28
Logical Capacity Calculation Example
100GB = Size of Weekly Full Backups
10% = Weekly Full Backup Growth Rate
12 = Weekly Full Backup Retention Period in Weeks
10GB = Size of Daily Backups
1% = Daily Backup Weekly Growth Rate
6 = Number of Daily Backups between Full Backups
4 = Daily Backup Retention Period in Weeks
Full Backup Capacity
Daily Backup Capacity
In the preceding example, 2.72TB of NVSD Capacity is required. Because NVSD
Capacity is sold in 1TB increments, 3TB of NVSD Capacity must be licensed.
3.3.2 Calculating the Required Number of NVSD Instances
3.3.2.a Determining the Number of Deduplicated NVSD Instances
Three factors determine the number of NVSD Instances with the NVSD
Deduplication Option enabled. If any of these factors are true, you must deploy
multiple NVSD Instances. To determine the total number of NVSD Instances for
the licensed NVSD Capacity with Deduplication Option, perform the following
calculations:
Unique Data Size > 15TB for 64-bit OS and > 5TB for 32-bit OS
Ingest Rate > Maximum Sustained Network Bandwidth
Deduplication Rate < Ingest Rate
(100) * (((1+ .10) ^ (12 + 1) - 1.0) / (.10)) =
(100) * (((1.1) ^ (13) - 1) / (0.1)) =
(100) * (((3.45) - 1) / (0.1)) =
(100) * (2.45 / 0.1) = 2450 GB
(10) * (((1 + .01) ^ ((4 + 1) * 6)) - 1.0) / (.01) =
(10) * (((1.01) ^ ((5) * 6)) - 1) / (0.01) =
(10) * (((1.01) ^ 30) - 1) / (0.01) =
(10)*((1.34)-1) / (0.01) =
(10)*(0.34/0.01) = 340GB
29
The maximum result for the three calculations determines the number of NVSD
Instances that must be deployed. For example, if the Unique Data Size calculation
and the Deduplication Rate indicates that only one NVSD Instance is required, but
the Ingest Rate calculation indicates that two NVSD Instances are required, you
must deploy two NVSD Instances.
Unique Data Size > OS Bit Limit
The Unique Data Size is the amount of unique data that is stored inside the NVSD
Instance. An additional NVSD Instance must be deployed for every 15TB of
unique data on a 64-bit OS and for every 5TB of unique data on a 32-bit OS. Use
the following calculation to determine the number of NVSD Instances based on the
Unique Data Size:
Example:
10% = Weekly Change Rate
If the OS is 64-bit:
460/15360 = .029
Rounded Up to Next Whole Number = 1 NVSD Instance
If the OS is 32-bit:
460/5120 = .089
Size of Weekly Full Backups + ((Size of Weekly Full
Backups * Weekly Change Rate)
* Weekly Full Backup Retention Period)
+ (Size of Daily Backups * (Number of Daily Backups
between Weekly Full Backups
* Daily Backup Retention Period))
100 + ((100 * 0.1) * 12) + (10 * (6*4)) =
100 + ((10) * 12) + (10 * (24)) =
100 + (120) + (240) = 460GB
Chapter 3
30
Ingest Rate > Network Bandwidth
The NVSD Ingest Rate is the rate at which data can be streamed into NVSD.
Because data streams into the NVSD Instance through a user-defined port, the
network bandwidth will limit the speed at which data can be streamed. To ensure
that all backups targeted to an NVSD Instance can complete during the backup
window, you must divide the required ingest rate by the Maximum Sustained
Network Bandwidth to determine the number of required NVSD Instances. Use the
following calculation to determine the number of NVSD Instances based on the
NVSD Ingest Rate and Network Bandwidth:
Example:
8 = Number of Hours in Backup Window
100 = Maximum Sustained NetWork Bandwidth (MB/Sec)
The NVSD Deduplication Rate is the rate at which NVSD deduplicates data. If
NVSD deduplication is configured to run during the backup, the NVSD
Deduplication Rate must be greater than or equal to the Ingest Rate to ensure that
the deduplication process completes before the next weekly backup window
begins.
Use the following to estimate the Deduplication Rates:
1. Determine the Single Core Deduplication Rate:
((Size of Weekly Full Backups * 1024) / (Number of Hours
in Backup Window* 60 * 60))
/ Maximum Sustained Network Bandwidth
((100 *1024) / (8 * 60* 60)) / 100 =
((102400) / (28,800)) / 100 =
3.55 / 100 = .035
Hardware Speed
24 to 36 Month Old Intel Core 1, AMD Athlon or Intel Celeron 10 to 20 MB/sec
12 to 24 Month Old Core 2 Duo, AMD Quad Core Opteron or Dual
Core Xeon
20 to 40 MB/sec
0 to 12 Month Old Desktop or Server Core 2 Duo, Quad Core Xeon
or Quad Core AMD
40 MB/sec or more
31
2. Multiply the Single Core Deduplication Rate by the number of Cores.
Use the following calculation to determine the number of NVSD Instances based
on the Deduplication Rate and Ingest Rate:
Example:
10% = Weekly Full Backup Growth Rate
24 = Number of Hours in Daily Deduplication Window
50 = Deduplication Rate (MB/Sec)
Determining the Required Number of NVSD Instances
The maximum result for the following three calculations determines the number of
NVSD Instances that must be deployed:
Unique Data Size > 15TB for 64-bit OS and > 5TB for 32-bit OS
Example:
Unique Data Size > OS Bit Limit = 1 NVSD Instance
Ingest Rate > Network Bandwidth = 1 NVSD Instance
Deduplication Rate < Ingest Rate = 1 NVSD Instance
The maximum result is one NVSD Instance; therefore, only one NVSD Instance is
required in this example.
(((Size of Weekly Full Backups) + (Size of Daily Backups
* Number of Daily Backups between Weekly Full Backups)) *
1024)
/ (Number of Seconds in Deduplication Window for 6 Days)
/ Deduplication Rate
(((100) + (10 * 6)) * 1024) / (24 * 6 * 60 * 60)) / 50 =
(((100) + (60)) * 1024) / (518400)) / 50 =
((160*1024)/518400)/50) =
(163840/518400)/50) = .0063
Chapter 3
32
3.3.2.b Determining the Number of Nondeduplicated NVSD
Instances
The number of Nondeduplicated NVSD Instances is determined by a single factor:
Ingest Rate > Network Bandwidth
The NVSD Ingest Rate is the rate at which data can be streamed into NVSD.
Because data streams into the NVSD Instance through a user-defined port, the
network bandwidth will limit the speed at which data can be streamed. To ensure
that all backups targeted to an NVSD Instance can complete during the backup
window, you must divide the required ingest rate by the Maximum Sustained
Network Bandwidth to determine the number of required NVSD Instances. Use the
following calculation to determine the number of NVSD Instances based on the
NVSD Ingest Rate and Network Bandwidth:
Example:
8 = Number of Hours in Backup Window
100 = Maximum Sustained NetWork Bandwidth (MB/Sec)
3.3.3 Calculating the Total Required Physical Disk Space for
Licensed Capacity
NVSD is licensed based on the Logical Capacity of the data that it can store.
However, in Deduplicated NVSD Instances, Logical Capacity does not match
Physical Capacity or physical disk space. This is because the NVSD Deduplication
Option packs up to 12 times more protected data into the same storage area for a
92% reduction in the storage footprint.
3.3.3.a Determining the Capacity for Deduplicated NVSD Instances
A Deduplicated NVSD Instance can have a combination of both Deduplicated and
Nondeduplicated data. In this configuration, calculating the total Physical Capacity
((Size of Weekly Full Backups * 1024) / (Number of Hours
in Backup Window* 60 * 60))
/ Maximum Sustained Network Bandwidth
((100 *1024) / (8 * 60* 60)) / 100 =
((102400) / (28,800)) / 100 =
3.55 / 100 = .035
33
or physical disk space is achieved by calculating the Physical Capacity for the
Deduplicated Backups, calculating the Physical Capacity for the Nondeduplicated
Backups, and adding the sums.
Deduplicated Backups
The Physical Capacity or physical disk space required for Deduplicated Backups
in Deduplicated NVSD Instances is equal to the Size of Weekly Full Backups plus
the Unique Data Size. Use the following formula to calculate it:
Example
100GB = Size of Deduplicated Weekly Full Backups across all servers
10% = Weekly Change Rate
10GB = Size of Deduplicated Weekly Daily Backups
Nondeduplicated Backups
Use the following formula to calculate the Physical Capacity or physical disk space
required for Nondeduplicated Backups in a Deduplicated NVSD Instance:
(Size of Weekly Full Backups) +
(Size of Weekly Full Backups + ((Size of Weekly Full
* Daily Backup Retention Period)))
100 + (100 + ((100 * 0.1) * 12) + (10 * (6*4))) =
100 + (100 + ((10) * 12) + (10 * (24))) =
100 + (100 + (120) + (240)) = 560GB
(Size of Nondeduplicated Weekly Full Backups * Weekly
Full Backup Retention Period)
+ (Size of Nondeduplicated Daily Backups * (Number of
Daily Backups between Full Backups * Daily Backup
Retention Period in Weeks))
Chapter 3
34
Example:
10GB = Size of Nondeduplicated Weekly Full Backups
1GB = Size of Nondeduplicated Daily Backups
Total Required Disk Space = Deduplicated Backup Disk Space + Nondeduplicated
Backup Disk Space
560GB + 144GB = 704GB
The Total Required Disk Space is divided into the Staging Store and the Chunk
Store. If you intend to use different file systems or disks for the Staging Store and
the Chunk Store, it is important to know how much of the Total Required Disk
Space will be allocated to the Staging Store versus the Chunk Store. Use the
following calculations to determine this.
Calculating Staging Store Size
The amount of time a Deduplicated Backup remains in the Staging Store is
different than the amount of time a Nondeduplicated Backup remains in the
Staging Store. Therefore, to determine the total disk space required for the
Staging Store, you must calculate the size required for both Deduplicated
Backups and Nondeduplicated Backups.
Total Staging Store Disk Space = Deduplicated Backup Disk Space +
Nondeduplicated Backup Disk Space
Deduplicated Backups
During the NVSD Deduplicated Backup process, backups are initially streamed to
the Staging Store where they remain until the deduplication process is finished.
The Staging Store must be large enough to hold all the Deduplicated Backups
while they await deduplication.
If the deduplication window overlaps the backup window, deduplication and
backups will occur at the same time. Each backup starts deduplicating after the
backup job is finished. Additionally, large backups will be broken into 400GB
segments. Each segment starts to deduplicate after it is received, even if the
backup stream is still being streamed to the Staging Store. Therefore, the
Staging Store only requires space to hold some portion of the total backup size. If
(10 * 12) + (1 * (6 * 4)) =
(120) + (1*(24)) =
120 * 24 = 144GB
35
the Staging Store runs out of space, backups will pause until space becomes
available, such as when a deduplication operation finishes.
The maximum disk space required for the Staging Store is equal to the Size of the
Weekly Full Backups.
Nondeduplicated Backups
Backups that are not deduplicated are streamed into the Staging Store, where
they remain until they are retired. Therefore, calculating the size of the Staging
Store for Nondeduplicated Backups is identical to calculating the required physical
disk space for Nondeduplicated Backups in a Deduplicated NVSD Instance.
Example:
10GB = Size of Nondeduplicated Weekly Full Backups
1GB = Size of Nondeduplicated Daily Backups
Calculating Chunk Store Size
The amount of physical disk space required for the Chunk Store is equal to the
Unique Data Size. To calculate the Unique Data Size or the size of the Chunk
Store, use the following formula:
(Size of Nondeduplicated Weekly Full Backups * Weekly
Full Backup Retention Rate)
+ (Size of Nondeduplicated Daily Backups * (Number of
Daily Backups between Full Backups * Daily Backup
Retention Period in Weeks))
(10 * 12) + (1 * (6 * 4)) =
(120) + (1*(24)) =
120 * 24 = 144GB
Size of Weekly Full Backups + ((Size of Weekly Full
* Daily Backup Retention Period))
Chapter 3
36
Example:
3.3.3.b Determining the Capacity for Nondeduplicated NVSD
Instances
The Physical Capacity or physical disk space required for Nondeduplicated NVSD
Instances is equal to the Logical Capacity because deduplication has been
disabled. The Nondeduplicated NVSD Instance will consume the same amount of
disk space for the Staging Store as Logical Capacity that is being licensed.
3.4.0 Choosing a Deployment Location for an NVSD
Instance
The third step in defining your NVSD Deployment Strategy is deciding where you
want to deploy your NVSD Instances. Whether the NVSD Instance is enabled for
deduplication dictates the available deployment options.
3.4.1 Reviewing Deployment Options for
NVSD Nondeduplicated Instances
You can deploy NVSD Instances that do not have deduplication on the server, a
heterogeneous client, or a dedicated server, and they can accept data streams
from heterogeneous platforms. When multiple NVSD Instances are deployed,
Storage Pools and processes are not shared across the multiple NVSD Instances.
However, you cannot deploy multiple NVSD Instances on the same machine,
whether it is a backup server, backup client, or a dedicated NVSD Server.
The following sections describe several deployment options that you might
consider for deploying NVSD Nondeduplicated Instances. This is not a
comprehensive list. These descriptions use NVBU only as an example.
100 + ((100 * 0.1) * 12) + (10 * (6*4)) =
100 + ((10) * 12) + (10 * (24)) =
100 + (120) + (240) = 460GB
37
3.4.1.a NVSD Nondeduplicated Instance Deployed on a Single NVBU
Server
In the simplest deployment, when only one NVSD Nondeduplicated Instance is
required for an NVBU Domain with a single NVBU Server, the NVSD Instance is
deployed on the single NVBU Server that uses file-system paths accessible by the
NVBU Server for the NVSD Storage Pools. The single NVBU Servers Clients that
target backups to NVSD will stream backup data on a user-defined port to the
NVSD Instance where the backup is stored in the NVSD Storage Pools.
Figure 3-1:
Single NVSD
Instance in
single NVBU
Server
environment
NetVault Backup
Server
NetVault Backup
Client
= Backup/Restore Data Path
NetVault Backup
Client
NetVault Backup
SmartClient
LAN
NetVault SmartDisk
Storage Pools
NVSD
Nondeduplicated
Instance
Chapter 3
38
3.4.1.b NVSD Nondeduplicated Instance Deployed in a Multiple
NVBU Server Environment
In NVBU environments where only one NVSD Instance is required for an NVBU
Domain with multiple NVBU Servers, a single NVSD Instance can accept data
streams from multiple NVBU Servers. In the following example where a single
NVSD Instance is deployed for multiple NVBU Servers, the NVBU Clients from
both NVBU Servers will stream backup data on a user-defined port to the NVSD
Instance that is deployed on one of the NVBU Servers.
Figure 3-2:
Single NVSD
Instance in
multiple NVBU
Server
environment
In NVBU environments where multiple NVSD Instances are required for an NVBU
Domain with multiple NVBU Servers, you can deploy one NVSD Instance on each
of the NVBU Servers, or you can deploy one NVSD Instance on one NVBU Server
and on one or more NVBU Clients. In the following example where two NVSD
Instances are required and there are two NVBU Servers, a single NVSD Instance
is deployed on each of the NVBU Servers. The NVBU Clients from both NVBU
Servers can stream backup data on a user-defined port to either NVSD Instance
that is deployed.
Note: You cannot deploy multiple NVSD Instances on the same dedicated NVSD
Server.
NetVault Backup
SmartClient
NetVault Backup
Client
NetVault Backup
Client
NetVault Backup
Server
NetVault Backup
Client
NetVault Backup
Client
NetVault Backup
SmartClient
LAN
NetVault SmartDisk
Storage Pools
NetVault Backup
Server
NVSD
Nondeduplicated
Instance
39
Figure 3-3:
Multiple NVSD
Instances in
multiple NVBU
Server
environment
NetVault Backup
SmartClient
NetVault Backup
Client
NetVault Backup
Client
NetVault Backup
Server
NetVault Backup
Client
NetVault Backup
Client
NetVault Backup
SmartClient
LAN
NVSD
Nondeduplicated
Instance
NetVault SmartDisk
Storage Pools
NetVault Backup
Server
NVSD
Nondeduplicated
Instance
Chapter 3
40
3.4.1.c NVSD Nondeduplicated Instance Deployed on a Dedicated
Server
In NVBU environments where only one NVSD Instance is required for an NVBU
Domain with one or more NVBU Servers and you want to have the backups
across all the NVBU Servers stored together, you can deploy a single NVSD
Instance on a dedicated server that has no NVBU Server or Client software
installed. In the following example, data from all NVBU Clients will stream backup
data on a user-defined port to the single NVSD Instance that is deployed on the
dedicated server.
Figure 3-4:
Single NVSD
Server in
multiple NVBU
Server
environment
NetVault Backup
SmartClient
NetVault Backup
Client
NetVault Backup
Client
NetVault SmartDisk
Server
NetVault Backup
Client
NetVault Backup
Client
NetVault Backup
SmartClient
NetVault Backup
Server
LAN
NetVault SmartDisk
Storage Pools
NetVault Backup
Server
NVSD
Nondeduplicated
Instance
41
3.4.2 Reviewing Deployment Options for NVSD Deduplicated
Instances
In environments where only one NVSD Instance is required for a domain with one
or more backup servers and you want the backups from all backup servers
deduplicated together, you must deploy a single NVSD Instance on a dedicated
server that has no backup server or client software installed.
Important: You cannot deploy a deduplicated instance on the same machine on
which NVBU Server or Client software is installed.
In the following example, data from all NVBU Clients will stream backup data on a
user-defined port to the single NVSD Instance that is deployed on the dedicated
server.
Figure 3-5:
Single NVSD
Server in
multiple NVBU
Server
environment
In environments where multiple NVSD Instances are required for a domain, you
must deploy each NVSD Instance on its own dedicated server. In the following
example, two NVSD Instances are required and they are deployed on two
dedicated NVSD Servers. The NVBU Clients from both NVBU Servers can stream
backup data on a user-defined port to either deployed NVSD Instance.
Note: You cannot deploy multiple NVSD Instances on the same machine, whether
it be a backup server, backup client, or dedicated NVSD Server.
NetVault Backup
SmartClient
NetVault Backup
Client
NetVault Backup
Client
NetVault SmartDisk
Server
NetVault Backup
Client
NetVault Backup
Client
NetVault Backup
SmartClient
NetVault Backup
Server
LAN
NetVault SmartDisk
Storage Pools
NetVault Backup
Server
NVSD
Deduplicated
Instance
Chapter 3
42
Figure 3-6:
Multiple NVSD
Servers in
multiple NVBU
Server
environment
3.4.3 Reviewing Deployment Options for Disaster Recovery
The data stored in an NVSD Instance is best protected from disaster if you deploy
multiple NVSD Instances in a disaster-recovery scenario.
The primary NVSD Instance will be deployed on the backup server, backup client,
or dedicated NVSD Instance. The secondary NVSD Instance will be deployed on a
dedicated backup server and connected to the primary backup server as a second
NVSD Device. The secondary NVSD Instance will typically be deployed in an
offsite location to provide maximum protection.
The backups that are targeted to the primary NVSD Instance will be copied to the
secondary NVSD Instance as the target for a secondary copy backup or as an
independent Data Copy backup that specifies the primary NVSD Instance as the
source and the secondary NVSD Instance as the destination.
Important: Third-party replication or mirroring technology is not supported for the
replication of the NVSD Storage Pools. Data that is replicated using third-party
technology, including deduplication appliance replication technology, is not
recoverable.
If a failure of only the primary NVSD Instance occurs, you can restore backups
from the secondary NVSD Instance. Primary backups can also be targeted to the
secondary NVSD Instance until the primary NVSD Instance is ready to resume the
primary role.
NetVault Backup
SmartClient
NetVault Backup
Client
NetVault Backup
Client
NetVault Backup
Client
NetVault Backup
Client
NetVault Backup
SmartClient
NetVault Backup
Server
LAN
NetVault Backup
Server
NetVault SmartDisk
Servers
NetVault SmartDisk
Storage Pools
NetVault SmartDisk
Storage Pools
NVSD
Deduplicated
Instance
NVSD
Deduplicated
Instance
43
Figure 3-7:
Multiple Non-
deduplicated
NVSD
Instances
deployed in
disaster-
recovery
scenario
Figure 3-8:
Multiple
Deduplicated
NVSD
Instances
deployed in
disaster-
recovery
scenario
If a complete failure of the production site occurs or a failure of the primary backup
server occurs, a backup server with the identical Machine Name as the primary
backup server in the production site will need to be deployed in the disaster-
recovery site. After the backup server with the identical Machine Name is running
in the disaster-recovery site, the secondary NVSD Instance can be added to the
backup server as an NVSD Device and scanned. After the backups have been
scanned, they can be restored and the secondary NVSD Device can become a
LAN
Disaster
Recovery
Site
Production
Site
Primary
NetVault Backup
Server
Standby
NetVault Backup
Server
NetVault SmartDisk
Server
NetVault SmartDisk
Storage Pools
NetVault Backup
Client
NetVault Backup
Workstation
Client
NetVault SmartDisk
Storage Pools
NetVault SmartDisk
Storage Pools
= DR Data Path
NVSD
Nondeduplicated
Instance
NVSD
Nondeduplicated
Instance
LAN
Disaster
Recovery
Site
Production
Site
Primary
NetVault Backup
Server
Standby
NetVault Backup
Server
NetVault SmartDisk
Server
NetVault SmartDisk
Server
NetVault SmartDisk
Storage Pools
NetVault Backup
Client
NetVault Backup
Workstation
Client
NetVault SmartDisk
Storage Pools
NetVault SmartDisk
Storage Pools
= DR Data Path
NVSD
Deduplicated
Instance
NVSD
Deduplicated
Instance
Chapter 3
44
target for primary backups until the primary backup server is returned to working
order.
Important: An NVSD Device can only be scanned into a backup server that has
the identical Machine Name as the original backup server that performed the
backups.
After the primary backup server is ready to resume the production role, the
secondary backup server is shut down. If backups were targeted to the secondary
NVSD Instance while it performed the role of the primary NVSD Instance, it will
need to be scanned back into the primary backup server.
Note: The primary and secondary backup servers cannot be running at the same
time.
3.5.0 Defining an NVSD Storage Pool Strategy
The fourth step in defining your NVSD Deployment Strategy is defining your
strategy for the NVSD Storage Pools.
3.5.1 Understanding Space Allocation for NVSD Storage
Pools
Before choosing a strategy for your NVSD Storage Pools, consider the following
with regard to how NVSD allocates space in the NVSD Storage Pools:
You can add an unlimited number of Storage Pools to NVSD.
You can add an unlimited number of volumes to each NVSD Storage Pool.
Each NVSD Storage Pool is associated with roles that it can perform.
When configuring a NVSD Storage Pool, you can identify it as a favorite for
specific roles (favour), and you can indicate that it should never be used for
specific roles (deny).
There is no quota specified per-volume of the absolute amount of space
NVSD can use (that is, you cannot say use exactly 100GB). However, you
can specify an amount of physical disk-storage that you want to set aside that
cannot be used by NVSD. This simplifies NVSDs internal space-allocation
policies so that Staging Store and Chunk Store processes can efficiently
share volumes. Each role independently implements and honors the
configured thresholds, which allows efficient parallel-processing without a
requiring a single, centralized space allocator.
Using the volume-size parameter, you can set aside a portion of the volume
so that it cannot be used for NVSD. After the volume is full with NVSD or non-
NVSD data, NVSD will not store anything else on the volume until space is
made available.
45
NVSD uses storage space in each volume up to a threshold amount that
includes space directly set aside using the volume-size parameter, as well
as the Last Resort Threshold (LRT) amount set by NVSD internally.
NVSD first uses a volume for its intended role (for example, Chunk Store or
Staging Store), but it will also use it for other purposes if necessary. Even if
you supply a threshold, NVSD implements an LRT that stops NVSD from
using a volume after there is less than a certain amount of space available
and thus prevents the disk from becoming completely full. The LRT is
calculated to include both a fixed amount of space (1GB) and the space that
would be required to make Garbage Collection possible (that is, the
gc_reserve_bytes parameter). This means that the figure varies in size
depending on the amount of data held in the Chunk Store (typically, you can
expect the gc_reserve_bytes parameter to be at least 1.7GB).
If the LRT is large enough, NVSD properly allocates space when multiple
Staging Store and Chunk Store processes are both writing to a volume that
becomes too full. NVSD maintains an overall idea of how much space is used
both by the Staging Store and the Chunk Store. This allows it to enforce the
licensed amount of capacity and to enforce the LRT and the volume-size
limits.
Licensing is not affected by user thresholds or NVSD's LRT. Licensing
measures the amount of data accepted for protection by the NVSD Instance,
regardless of whether the data has been deduplicated.
The following figure shows a graphical example of how space is organized in
NVSD. This figure assumes all volumes are mapped to one file system.
Additionally, the space reserved for LRT is reserved on a per-volume basis; if your
configuration uses multiple volumes, more LRT space might be allocated.
Figure 3-9:
Space
allocation for
NVSD
Unused space
available for NVSD
Chunk Store
Staging
Store
Garbage Collection
Reserve
LRT
((100-X)/100)*T
Space currently used by
OS, users, and non-NVSD
applications
T=Total space available on an empty file system
X=Volume-size parameter
Chapter 3
46
3.5.2 Understanding the Simplified Management Strategy
If the goal is simplified management, configure a single volume for all required
storage. For example, if you are using a single RAID array, configure a single
RAID 5 or RAID 6 volume, and map all the NVSD Storage Pool roles to a single
file system that is mapped to the RAID array. This provides adequate performance
while minimizing management complexity.
3.5.3 Understanding the Optimal Performance Strategy
Consider the following guidelines when assigning NVSD Storage Pool Roles:
Content Index - Will be relatively small and should reside in a Storage Pool
comprised of fault-tolerant disks with good random-access performance.
Staging Store Should reside in a Storage Pool comprised of fault-tolerant
disks with good streaming performance.
Chunk Index Should reside in a Storage Pool comprised of fault-tolerant
disks with good random-access performance.
Chunk Store Should reside in a Storage Pool comprised of fault-tolerant
disks.
If the goal is optimal performance, using additional disks to increase Input/Output
Operations per Second (IOPS) and aggregate disk bandwidth improves NVSD
performance more than using additional memory.
For example, if you are using a single RAID array, consider configuring four
separate RAID 1 volumes, one for each Storage Pool Role. This separates the IO
workload for each volume across independent RAID volumes. You can tune
performance further by restricting the number of independent disk operations
(reads, writes, and deletes) allowed per volume to two operations, which avoids
disk thrashing. In addition, configure the RAID array to support more bandwidth in
and out of Staging Store.
This strategy is appropriate for NVSD Instances where staging, deduplication, and
restores might occur simultaneously.
Note: RAID recommendations also apply to Storage Area Network (SAN) and
Network Attached Storage (NAS).
Additionally, Linux, UNIX, and Mac OS X systems support use of the noatime
feature for file systems, usually as a mount option. Quest Software recommends
that you enable this feature on your system to improve NVSD performance,
especially for the Chunk Index and Chunk Store volumes. Using this feature can
reduce the number of metadata writes needed to update read-access times for
files.
On Windows platforms, you can disable the New Technology File System (NTFS)
Last Access Update feature, which can reduce disk accesses and increase
47
performance. For instructions on disabling this feature, refer to the documentation
for your specific OS.
3.5.3.a Optimizing Performance While Protecting Against Data Loss
During Power Failures
Although enabling disk-write caches improves NVSD performance, power failures
that occur before modified disk-cache contents have been written to non-volatile
magnetic storage can potentially cause data loss in NVSD. Because of this risk, it
is critical that you understand how your underlying disk technology caches writes
to disk. You can turn off disk-write caching completely, but due to the improvement
in performance that write-caching offers, it is increasingly used despite the risk,
and the risk is mitigated through the use of additional technology. A common
mitigation technique is ensuring that power does not go off. In high-end server
environments, with their uninterruptible power supplies (UPSs) and redundant
power supplies, having unfilled cached writes is less of an issue.
Additionally, drives that employ write-caching have a write-flush feature that
instructs the drive to send pending writes from the cache to the disk immediately.
This command is usually sent before UPS batteries run out (if the system detects
a power interruption) or just before the system is shut down for any other reason.
Finally, most disk array systems use non-volatile random access memory
(NVRAM) to protect data written to disk in case of a power failure. Quest Software
recommends that you review your server and storage vendors product
documentation to understand what steps are taken to ensure that disk writes are
written to non-volatile magnetic storage in case of a power failure.
Chapter 3
48
49
Chapter 4:
INSTALLING NVSD
Installing NVSD An Overview
System Requirements
Software Requirements
Hardware Requirements
Authentication Requirements
Installing the NVSD Software
Important Considerations
Installing on Linux or UNIX (Excluding Solaris)
Installing on Solaris (SPARC, x86, or x86-64)
Installing on Windows
Installing on Mac OS X
4.1.0 Installing NVSD An Overview
Installing NVSD involves the following main steps:
Verifying that the system requirements are in place.
Installing the software.
Updating the Storage Pool structure, if applicable.
Adding the NVSD Devices to your backup product.
Protecting the NVSD identify.
Installing the license key.
4.2.0 System Requirements
4.2.1 Software Requirements
NVSD has the following software requirements:
Windows platforms NVSD has the following requirements on Windows:
Microsoft Visual C++ If it is not already installed, NVSD automatically
installs the applicable portions of the Microsoft Visual C++ 2005 SP1
Redistributable Package. No additional steps are required by you.
Chapter 4
Installing NVSD
50
System-memory requirements Make sure that your Windows system
has at least 2 gigabytes (GB) plus 400 megabytes (MB) for every terabyte
(TB) of data that the Chunk Store must address. If you use a 32-bit
platform, be aware that you are limited to a Chunk Store of 2.5TB of
unique data.
Linux platforms NVSD has the following library requirements on Linux.
Installation might fail if these packages are not installed on the system. For
instructions on installing the required packages, refer to the relevant OS
documentation.
Asynchronous I/O Library Depending on the Linux distribution, make
sure that the libaio.so.1 package is installed in the following directory:
32-bit OS /lib or /usr/lib
64-bit OS /lib64 or /usr/lib64
Some distributions of Linux do not install the Asynchronous I/O Library
package by default. If required, install this package.
Standard C++ Library
NVSD Linux x86_Hybrid and Linux IA64 Builds Make sure that
the libstdc++.so.6 package is installed in the /usr/lib directory. If
required, install the Standard C++ Library package.
NVSD Linux x86_Pure64 Build Make sure that the libstdc++.so.5
package is installed in the /usr/lib64 directory. If required, install the
Compatibility Standard C++ Library package.
4.2.2 Hardware Requirements
NVSD has the following hardware requirements:
Deduplicated NVSD Instances If the NVSD Deduplication Option is
enabled, make sure that the following requirements are met:
CPU requirements CPU requirements vary based on the required
NVSD Deduplication Rate (the rate at which NVSD deduplicates data)
the higher the Deduplication Rate requirements, the higher the CPU
requirements for the machine where NVSD software is installed.
The NVSD Deduplication Rate must be greater than or equal to the Ingest
Rate to ensure that the deduplication process completes during the
backup window or before the next weekly backup window begins. For
more information, see Calculating the Required Number of NVSD
Instances on page 28.
Memory requirements:
Required minimum 2GB
Recommend minimum An additional 400MB per 1TB of NVSD-
unique data
51
Example
10TB of NVSD Unique Data
2GB + (400MB * 10) = 2GB + 4000MB = 6GB
For more information, see Calculating the Required Number of
NVSD Instances on page 28.
Nondeduplicated NVSD Instances If the NVSD Deduplication Option is
not enabled, make sure that the following requirements are met:
CPU requirements Use a machine with a 24-to-36-month-old Intel Core
1, AMD Athlon, or Intel Celeron processor. Quest Software recommends
that you use faster processors for best performance.
Memory requirements The minimum requirement is 512MB.
Network requirement for all NVSD Instances TCP/IP name resolution.
After the machine that will host the NVSD software has been identified, make
sure that the machine can resolve its own host name.
Storage Pool requirements For Storage Pool requirements based on
whether your goal is simplified management or optimal performance, see
Defining an NVSD Storage Pool Strategy on page 44.
For additional information, refer to the Quest NetVault SmartDisk Supported
Platforms document.
4.2.3 Authentication Requirements
Root-level or administrator account for installation Root-level or
administrator credentials are only required for use during the installation
process, removal process, and, if necessary, manually restarting the NVSD
Services.
NVSD Non-privileged Group and User Security group with full NVSD
configuration and monitoring rights.
To create the NVSD Non-privileged Group and Users, follow these
guidelines:
For Linux and UNIX (the following examples use sdusr and sdgrp for
the user and group, respectively):
1. If the non-privileged group does not exist, create it.
2. If the non-privileged user does not exist, create it and add it to the non-
privileged group.
# groupadd sdgrp
# useradd -G sdgrp sdusr
Chapter 4
Installing NVSD
52
3. Define the password for the non-privileged user.
4. If the non-privileged user does exist, add it to the non-privileged group.
For Windows:
On Windows, you are not required to create the non-privileged user prior
to installation. You can enter the applicable information during the
installation process. The installer will verify that the account meets all
applicable system requirements before continuing with the installation
process.
For Mac OS X:
Create the non-privileged user by clicking Apple > System
Preferences > Accounts. On the System Preferences dialog, click
Accounts. Use the Accounts dialog to create a non-privileged user.
Use dseditgroup to add the non-privileged user to an applicable
group. The following example uses sdusr and sdgrp for the user and
group, respectively.
For Linux, UNIX, and Mac OS X platforms:
If your OS does not create a corresponding non-privileged group by
default, create one and add the non-privileged user to it.
After you have created the non-privileged user and group, add your
root-level or administrator account to the same non-privileged group.
UNC path and credentials if using a network share on Windows You
can specify a path that includes a network share, whether it is mapped or
using Universal Naming Convention (UNC). To do so, the parent directory of
the target directory must exist (the target directory does not have to exist yet)
and you must have the access credentials.
4.2.3.a Important Notes Regarding Windows and the Non-Privileged
User
If you are installing NVSD on Windows, be aware that the NVSD installer grants
read- and write-access permission to the specified non-privileged user during the
installation process. This access, which lets NVSD report Windows Events, only
applies to the Application log.
# passwd sdusr
# usermod -a -G sdgrp sdusr
sudo dseditgroup -o create sdgrp
sudo dseditgroup -o edit -a sdusr -t user sdgrp
53
If you change the non-privileged user (via smartdisk.bat password), the same
rights are granted to the new user, and the rights are retained for the original user
because the original user might be assigned to multiple services on the same
system. For the same reason, this access is also retained if you remove NVSD.
The modified registry key is:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
Eventlog\Application
Therefore, if you know that a non-privileged user is not needed for other services,
you should manually update the registry key and user account.
4.3.0 Installing the NVSD Software
You can install NVSD either via the installation CD or the package downloaded
from the web site.
Throughout this document, the path to where you installed NVSD is represented
by an ellipsis (). Replace the ellipsis with the applicable information.
4.3.1 Important Considerations
If you are using NVBU, do not install the product in the same directory as
NVBU is installed. If you have to remove NVBU for any reason, it will remove
NVSD as well if they are installed in the same directory.
Important: If you are using deduplication, you cannot deploy a deduplicated
instance on the same machine on which NVBU Server or Client software is
installed.
If you install NVSD on a double-byte Windows OS and you do not use the
default directories for installation, make sure that the new directories are
created using single-byte characters; installation will fail if you use double-
byte characters.
You cannot install the NVSD binaries (installation files) on an NFS share.
During installation, you will be prompted for the path to the Staging Store or
Staging Path and the Chunk Store or Store Path. You can specify any
supported File System that is listed in the Quest NetVault SmartDisk
Supported Platforms document. However, if you intend to use a third-party
deduplication appliance, filer, or other form of network-attached storage
(NAS) for the NVSD Storage Pools, you must use the network share for the
appliance that is exported via Common Internet File System (CIFS) or
Network File System (NFS) as the target for the Staging Store or Staging
Path. (You can specify one network share for each path during installation; if
you need additional shares for the Storage Pools, you can add them after
installation is finished. For more information, see Completing the Installation
Chapter 4
Installing NVSD
54
Process on page 75.) If the third-party appliance, filer, or NAS will be
performing the deduplication (instead of the NVSD Deduplication Option),
you cannot use the appliances network share as the target for the Chunk
Store or Store Path.
If installation is interrupted or fails for any reason (for example, due to a
power outage), remove the product before attempting to install it again. On
Linux and UNIX systems (excluding Solaris), try executing ./smartdisk.sh
uninstall from /foundation/bin. On Solaris, try executing pkgrm. On all
systems, manually delete the NVSD-related directory and its contents.
4.3.2 Installing on Linux or UNIX (Excluding Solaris)
1. Make sure that you have reviewed the authentication requirements and all
other critical information.
For more information, see Authentication Requirements on page 51 and
Important Considerations on page 53.
2. Log on as root or sudo to root.
3. If you are using the CD, complete the following steps:
a. Insert the CD into the CD-ROM drive, and mount the drive.
b. Initiate a terminal session, and access the CD:
Note: On systems that use automount, installation fails with error message bash:
./install: /bin/sh bad interpreter: Permission denied. To avoid this, mount the
CD manually without the noexec mount option.
4. If you are using the downloaded package, complete the following steps:
a. Using your preferred method, decompress the downloaded file.
b. Initiate a terminal session, and navigate to the smartdisk directory in
which the decompressed files reside.
5. To launch installation, type as root or sudo to root:
With the installation successfully initiated, the setup process begins.
Note: Most prompts revealed during the installation process have a default
selection. These options appear at the end of each prompt, enclosed in brackets
([ ]). To accept a default, press Enter.
cd /cdrom/installation_files/<platform>/SmartDisk/
smartdisk
./install
55
6. When the following prompt appears, type the number that corresponds to the
language version that you want to install, and press Enter.
7. When the following prompt appears, select the applicable option.
y Indicates Yes. To accept the agreement, type y, and press Enter. The
installation process continues without displaying the Transaction Product
Agreement.
n Indicates No. To decline the agreement, type n, and press Enter. The
installation process stops.
d Indicates Display. (This is the default.) To view the agreement, type d,
and press Enter. The Transaction Product Agreement is displayed in
sections with a percentage value shown at the bottom of the screen. This
value accounts for how much of the agreement has been displayed. Each
time you press Enter, more of the agreement is displayed and this value
increases. Continuously holding down the Enter key will scroll through the
entire agreement, and end with the next prompt.
Important: Quest Software requires that you thoroughly review the license
agreement before proceeding with the installation.
8. Monitor the results when the checking mechanism runs that determines if the
required libstdc++ and libaio libraries are installed on the system:
If the required packages are installed on the system, a message appears
and the installation continues.
Sample message:
If the correct version of either the libstdc++ and libaio package is not
installed on the system, an error appears that indicates the missing library
and the installation stops.
Select a Language
1 English
2 JapaneseEUC
3 Chinese Simplified
4 Korean
5 French
6 German
Select Language? [1]:
Have you read and agreed to the terms of the license?
(y = yes, n = no, d = display license) (y n d) [d]: y
libstdc++.so.6 is installed.
libaio.so.1 is installed.
Chapter 4
Installing NVSD
56
Sample error messages:
9. When the following prompt appears, indicate where you want NVSD installed.
10.When the non-privileged-related prompts appear, enter the name of the non-
privileged user and the name of the users group:
11. When the additional location-related prompts appear, indicate where you
want NVSD installed.
Note: Linux, UNIX, and Solaris do not differentiate between local drives and
mounted drives. If you choose to use a mounted drive (for example, using NFS)
for the Staging Path and Store Path, Quest Software strongly recommends that
you use a subdirectory on the applicable drive. This ensures that data is not
written to the local directory if the mounted location becomes unavailable.
12.If you are installing NVSD on Linux, enter y for Yes or n for No when the
following prompt appears:
ERROR: SmartDisk requires libstdc++.so.5 to be installed.
ERROR: Please install the Compatibility Standard C++
Library package.
ERROR: SmartDisk requires libaio.so.1 to be installed on
the system.
ERROR: Please install the appropriate Asynchronous I/O
Access Library package.
Where should SmartDisk be installed? [/usr/smartdisk] :
Non privileged user? : <userName>
you chose <userName>
Non privileged user's group? [<userName>] : usergroup
you chose <userGroup>
Staging path? [/usr/smartdisk/diskmanager/stage] :
.
Store path? (Note: A network share located on a third-
party deduplication appliance cannot be used for the
Chunk Store.) [/usr/smartdisk/store] :
Would you like to configure WebDAV authentication
credentials? (y n) [y]:
57
13.If you entered y, enter the applicable user name and password when the
corresponding prompts appear, making sure to press Enter after each entry.
(The installer will verify that the information you enter is correct.)
Note: For the user name in the WebDAV credentials, NVSD currently supports the
use of any ASCII characters except the quotation mark ("), comma (,), and colon
(:). The are no restrictions for the corresponding password.
14.When the script is finished, verify that it indicates that the installation
completed successfully.
4.3.3 Installing on Solaris (SPARC, x86, or x86-64)
2. Log on as root or sudo to root.
3. If you are using the CD, complete the following steps:
a. Insert the CD into the CD-ROM drive, and mount the drive.
b. Initiate a terminal session, and access the CD:
4. If you are using the downloaded package, decompress the downloaded file
using your preferred method.
For example:
You chose Yes.
WebDAV authentication username?:
Please enter the WebDAV authentication password for
SmartDisk:
Please confirm password:
Starting SmartDisk... success
.
Installation completed successfully.
cd /cdrom/installation_files/<platform>/SmartDisk/
smartdisk
gunzip smartdisk-solaris-x86_<version>-<date>.tar.gz
tar -xvf smartdisk-solaris-x86_<version>-<date>.tar
Chapter 4
Installing NVSD
58
5. To launch installation, type as root or sudo to root:
With the installation successfully initiated, the setup process begins.
6. Enter the number that corresponds to the package you want to install (for
example, 1), and press Enter.
Note: Most prompts revealed during the installation process have a default
selection. These options appear at the end of each prompt, enclosed in brackets
([ ]). To use the default value and continue the process, press Enter.
7. When the following prompt appears, type the number that corresponds to the
language version that you want to install, and press Enter.
8. When the following prompt appears, select the applicable option.
y Indicates Yes. To accept the agreement, type y, and press Enter. The
installation process continues without displaying the Transaction Product
Agreement.
n Indicates No. To decline the agreement, type n, and press Enter. The
installation process stops.
d Indicates Display. (This is the default.) To view the agreement, type d,
and press Enter. The Transaction Product Agreement is displayed in
sections with a percentage value shown at the bottom of the screen. This
value accounts for how much of the agreement has been displayed. Each
time you press Enter, more of the agreement is displayed and this value
increases. Continuously holding down the Enter key will scroll through the
entire agreement, and end with the next prompt.
pkgadd -d smartdisk
The following packages are available:
1 smartdisk SmartDisk
(i386) 001
Select a Language
1 English
2 JapaneseEUC
3 Chinese Simplified
4 Korean
5 French
6 German
Select Language? [1]:
Have you read and agreed to the terms of the license?
(y = yes, n = no, d = display license) (y n d) [d]: y
59
9. When the following prompt appears, indicate where you want NVSD installed.
10.When the non-privileged-related prompts appear, enter the name of the non-
privileged user and the name of the users group:
11. When the additional location-related prompts appear, indicate where you
want NVSD installed.
Note: Linux, UNIX, and Solaris do not differentiate between local drives and
mounted drives. If you choose to use a mounted drive (for example, using NFS)
for the Staging Path and Store Path, Quest Software strongly recommends that
you use a subdirectory on the applicable drive. This ensures that data is not
written to the local directory if the mounted location becomes unavailable.
12.When the following prompt appears, enter y for Yes or n for No:
If you entered n, type y when the following confirmation prompt appears,
and press Enter.
If you entered y, enter the applicable user name and password when the
corresponding prompts appear, making sure to press Enter after each
entry. (The installer will verify that the information you enter is correct.)
Where should SmartDisk be installed? [/opt/smartdisk] :
Non privileged user? : <userName>
you chose <userName>
Non privileged user's group? [<userName>] : <userGroup>
you chose <userGroup>
Staging path? [/opt/smartdisk/diskmanager/stage] :
.
Store path? (Note: A network share located on a third-
party deduplication appliance cannot be used for the
Chunk Store.) [/opt/smartdisk/store] :
Would you like to configure WebDAV authentication
credentials? (y n) [y]:
Do you want to continue with the installation of
<smartdisk> [y,n,?]
Chapter 4
Installing NVSD
60
13.When the following prompt appears, type y, and press Enter:
14.When the installation script is finished, verify that it indicates that the program
started and installation completed successfully.
4.3.4 Installing on Windows
2. Log on as an administrator.
3. If you are using the CD, insert the CD into the drive, and skip to Step 6.
4. If you are using the downloaded package, decompress the downloaded file,
and navigate to the SmartDisk directory in which the decompressed files
reside.
5. To launch the installation wizard, double-click the install.exe file.
6. When the Installation Language dialog appears, select the applicable
language, and click OK to continue.
7. When the Welcome dialog appears, click Next to continue.
8. When the License Agreement dialog appears, review the Transaction
Product Agreement, select I Agree, and click Next.
You chose Yes.
WebDAV authentication username?:
Please enter the WebDAV authentication password for
SmartDisk:
Please confirm password:
Do you want to continue with the installation of
<smartdisk> [y,n,?]
Starting SmartDisk... success
Installation of <smartdisk> was successful.
61
9. On the Non-Privileged User dialog, enter the name and password of the
non-privileged user account that you want to use for NVSD (if the account
does not already exist, the installer will create it for you), the Windows
Domain (if applicable), and click Next.
The installer will verify that the specified account meets all applicable system
requirements (based on your organizations policies) before continuing with
the installation process. If the requirements are not met, the installer will
cancel the installation process before installing any NVSD components.
Figure 4-1:
Non-Privileged
User dialog
Chapter 4
Installing NVSD
62
10.If the user account that you entered in the previous step does not already
exist, select Yes, and click Next when the Preinstall Warnings dialog
appears.
Figure 4-2:
Preinstall
Warnings
dialog
11. On the Select Installation Folder dialog, change the path if you do not want
to use the default.
To use a different directory, type the path in the Folder box, or click
Browse to point to the new location.
To see how much space NVSD will require for the selected installation
directory and files, click Disk Cost, review the information on the
SmartDisk Disk Space dialog, and then click OK to dismiss it. The Disk
Cost information is calculated only for the NVSD software binaries. It does
not include the disk space required for the Staging Store or Chunk
Store. To determine the disk space required for the Staging Store or
Chunk Store, see Calculating the Total Required Physical Disk Space for
Licensed Capacity on page 32.
63
Figure 4-3:
Select
Installation
Folder dialog
12.To continue, click Next.
13.On the Staging Path Folder Configuration dialog, indicate whether you
want to use a Remote or Local directory, and then click Next.
Figure 4-4:
Staging Path
Folder
Configuration
dialog
Note: If you intend to use network shares for both the Staging Path and the Store
Path, be aware that these paths must be unique.

After installation is finished, you can add additional volumes. For more information,
see Updating the Storage Pool Directory Structure on page 75.
Chapter 4
Installing NVSD
64
14.Do one of the following:
If you selected Remote (the default is Local), on the Select Remote
Staging Path Folder dialog, specify the path for the Staging Store (use
the \\server\share format), enter the user name and corresponding
password required to access the remote path, and then click Next.
Figure 4-5:
Select Remote
Staging Path
Folder dialog
If you selected Local, on the Select Staging Path Folder dialog, specify
the file-system path for the Staging Store, and then click Next.
Figure 4-6:
Select Staging
Path Folder
dialog
65
15.On the Store Path Folder Configuration dialog, indicate whether you want
to use a Remote or Local directory, and then click Next.
Figure 4-7:
Store Path
Folder
Configuration
dialog
Note: If you intend to use network shares for both the Staging Path and the Store
Path, be aware that these paths must be unique.

After installation is finished, you can add additional volumes. For more information,
see Updating the Storage Pool Directory Structure on page 75.
Chapter 4
Installing NVSD
66
16.Do one of the following:
If you selected Remote (the default is Local), on the Select Remote Store
Path Folder dialog, specify the path for the Chunk Store (use the
\\server\share format), enter the user name and corresponding password
required to access the remote path, and then click Next.
Figure 4-8:
Select Remote
Store Path
Folder dialog
If you selected Local, on the Select Store Path Folder dialog, specify the
file-system path for the Chunk Store, and then click Next.
Figure 4-9:
Select Store
Path Folder
dialog
67
17.On the WebDAV Authentication Configuration dialog, do one of the
following:
Figure 4-10:
WebDAV
Authentication
Configuration
dialog
If you do not want to configure WebDAV (the default is Yes), select No,
and click Next.
If you want to configure WebDAV (Yes is selected), click Next, enter the
applicable user name and password on the WebDAV Authentication
Credentials dialog, and then click Next. (The installer will verify that the
information you enter is correct.)
Chapter 4
Installing NVSD
68
Figure 4-11:
WebDAV
Authentication
Credentials
dialog
18.When the Confirm Installation dialog appears, click Next to continue.
19.When the Installation Complete dialog appears, click Close to dismiss it.
20.If you are upgrading a Windows installation and a Windows Restart Now or
Restart Later prompt appears, click the applicable button.
If necessary, NVSD automatically installs the supporting Microsoft Visual C++
files into the Global Assembly Cache. If these files are currently in use by
another application, the installer will prompt you to restart the system. This is
standard Windows behavior.
4.3.5 Installing on Mac OS X
1. Make sure that you have created the required non-privileged user and group,
and that you have reviewed all other critical information.
3. If you are using the CD, insert the CD into the drive, and skip to Step 6.
4. If you are using the downloaded package, decompress the downloaded file,
and navigate to the SmartDisk directory in which the decompressed files
reside.
69
5. To launch the installation wizard, double-click the smartkdisk.pkg file.
Figure 4-12:
.pkg file
6. When the Welcome to the Quest NetVault SmartDisk Installer dialog
appears, click Continue.
7. When the Software License Agreement dialog appears, review the
Transaction Product Agreement, and click Continue.
8. When the confirmation prompt appears, click Agree to accept the license
agreement.
Chapter 4
Installing NVSD
70
9. If the Select a Destination dialog appears, select the hard drive on which
you want to install the program, and click Continue.
In some situations, the Apple Installer automatically selects the volume and
does not display this dialog.
Figure 4-13:
Select a
Destination
dialog
71
10.On the first NetVault SmartDisk Setup dialog, perform the following steps:
a. In the User and Group fields, enter the non-privileged user and group.
For more information, see Authentication Requirements on page 51.
b. In the Store volume path and Staging volume path, enter the applicable
locations if you do not want to use the defaults.
Figure 4-14:
NetVault
SmartDisk
Setup dialog
11. Click Continue.
12.If NVSD determines that the user or group is invalid and displays an Alert,
click OK, correct the applicable information, and click Continue again.
Figure 4-15:
Alert message
13.If this is a new installation (not an upgrade), do one of the following on the
next NetVault SmartDisk Setup dialog:
If you do not want to configure WebDAV, clear the Use Credentials check
box, and click Continue.
If you want to configure WebDAV, enter the applicable user name and
password, and click Continue. Note that this name and password might
be different from those entered for the non-privileged user. (The installer
will verify that the information you enter is correct.)
Chapter 4
Installing NVSD
72
Figure 4-16:
NetVault
SmartDisk
Setup dialog
14.If you are performing an upgrade, click Continue when the next NetVault
SmartDisk Setup dialog appears.
Figure 4-17:
NetVault
SmartDisk
Setup dialog
for upgrade
73
15.On the Standard Install on <drive> dialog, click Install to continue.
Note: Change Install Location is not currently supported.
Figure 4-18:
Standard
Install dialog
16.When the Installation was completed successfully dialog appears, click
Close to dismiss it.
Chapter 4
Installing NVSD
74
75
Chapter 5:
COMPLETING THE
INSTALLATION PROCESS
Updating the Storage Pool Directory Structure
Adding NVSD Devices to Your Backup Product
Protecting the NVSD Unique Identity
5.1.0 Updating the Storage Pool Directory Structure
During the installation of the NVSD software, you specified a directory for the
Staging Path and the Store Path. Currently, the following NVSD components are
installed in each of the directories that you specified:
Staging Path (folder)
Staging Store
Store Path (folder)
Chunk Index
Content Index
Chunk Store
Whether your NVSD Storage Pool Strategy dictates that you store the Storage
Pools on a non-local directory structure, such as a third-party deduplication
appliance, filer, or other NAS that is mapped or accessible via UNC, or you want to
implement an optimal performance strategy for your NVSD Storage Pools, you
must update the directory structure for the Storage Pools before you add NVSD
as a device in your backup product.
For more information on strategies, see Defining an NVSD Storage Pool Strategy
on page 44.
For more information on extending NVSD Storage Pools, refer to the applicable
topic in the Quest NetVault SmartDisk Administrators Guide.
5.2.0 Adding NVSD Devices to Your Backup Product
Before you can begin targeting NVSD for backups and restores, you must add an
NVSD Device to your backup product. For more information, refer to the Quest
NetVault SmartDisk Administrators Guide and the documentation that came with
your product.
Chapter 5
Completing the Installation Process
76
5.3.0 Protecting the NVSD Unique Identity
Each NVSD installation of the software binaries creates a unique identity that is
referenced in the NVSD Content Index and your backup product. NVSDs unique
identity is required in cases where the NVSD software binaries will be reinstalled
while retaining the data stored in the NVSD Storage Pools. For more information,
see Reinstalling NVSD on page 85.
To ensure that you can reinstall the NVSD software binaries while retaining the
data stored in the NVSD Storage Pools, protect the NVSD unique identity by
backing up the following configuration file:
/diskmanager/etc/identity.cfg
77
Chapter 6:
LICENSING NVSD
NVSD License Keys An Overview
Obtaining the NVSD Machine ID
Requesting a License Key
Installing a License Key on Linux, UNIX, or Mac OS X
Installing a License Key on Windows
6.1.0 NVSD License Keys An Overview
Each NVSD Instance requires its own permanent license key, which is tied to an
NVSD Machine ID that is unique to each NVSD Instance. If the Total NVSD
Licensed Capacity will be distributed across multiple NVSD Instances, you must
provide the following information for each deployed NVSD Instance when you
request permanent NVSD license keys:
NVSD Instance Machine ID
NVSD Instance Licensed Capacity
NVSD Deduplication
While you can request NVSD license keys as you deploy NVSD Instances, it is
important to understand that the nondeduplicated and deduplicated capacity for all
NVSD Instances must be less than or equal to the Total NVSD Nondeduplicated
and Deduplicated Licensed Capacity that has been licensed.
6.2.0 Obtaining the NVSD Machine ID
Each NVSD Instance requires its own permanent license key, which is tied to an
NVSD Machine ID that is unique for each NVSD Instance.
To obtain the NVSD Machine ID, use the following command:
On Linux, UNIX, or Mac OS X:
On Windows:
/foundation/bin/smartdisk.sh license --querymachineid
\foundation\bin\smartdisk.bat license --querymachineid
Chapter 6
Licensing NVSD
78
6.3.0 Requesting a License Key
To request the permanent license key, complete the following steps:
1. Use the NVSD Machine ID to submit a request at:
https://support.quest.com/LicenseKey.aspx
2. After you receive the license key, install it using the steps provided in the
following sections.
6.4.0 Installing a License Key on Linux, UNIX, or
Mac OS X
1. Log on as the NVSD non-privileged user or administrator member of the non-
privileged group.
2. Initiate a terminal session.
3. Change to the bin directory in the NVSD directory.
4. Enter the license key.
For example:
Note: To avoid potential errors, Quest Software recommends that you use copy-
and-paste functionality to copy the license key from the email to the command
prompt.
The system displays the following message:
cd /foundation/bin
./smartdisk.sh license -t XX-XXXXX-XXXX-XXXXX
License installed successfully
79
6.5.0 Installing a License Key on Windows
2. Open a command prompt by clicking Start > Programs Accessories >
Command Prompt.
3. In the Command Prompt window, change to the bin directory in the NVSD
directory:
4. Enter the license key.
For example:
Note: To avoid potential errors, Quest Software recommends that you use copy-
and-paste functionality to copy the license key from the email to the command
prompt.
The system displays the following message:
cd \foundation\bin
smartdisk.bat license -t XX-XXXXX-XXXX-XXXXX
License installed successfully
Chapter 6
Licensing NVSD
80
81
Chapter 7:
UNINSTALLING NVSD
Preserving Data Before Removing NVSD
Removing NVSD from Linux, UNIX (Excluding Solaris), or Mac OS X
Removing from Solaris (SPARC, x86, or x86-64)
Removing from Windows
7.1.0 Preserving Data Before Removing NVSD
When you remove NVSD from a Windows or Solaris system, the data in the
Staging Store and the Chunk Store is retained after removal of the NVSD
software binaries.
For all other Linux- and UNIX-based systems and Mac OS X, the data in the
Staging Store and the Chunk Store is deleted if the default directory was used
during installation. If you want to retain the data in the Staging Store and the
Chunk Store after you remove the NVSD software binaries, you must move the
Staging Store and the Chunk Store to a secure location before removing the
NVSD software binaries.
If you specified a different file-system path during installation (that is, you did not
use the defaults), the data in the Staging Store and the Chunk Store is retained
after removal of the NVSD software binaries.
7.2.0 Removing NVSD from Linux, UNIX (Excluding
Solaris), or Mac OS X
1. Log on as root (or use sudo) to execute the following command:
The system displays the following:
2. When the confirmation prompt appears, type y, and press Enter.
When the system displays the following, removal is finished:
/foundation/bin/smartdisk.sh uninstall
About to remove IDP installation from /
Are you sure you want to continue? (y n) [n]:
Removal completed successfully
Chapter 7
Uninstalling NVSD
82
7.3.0 Removing from Solaris (SPARC, x86, or x86-64)
1. Log on as root or sudo to root, and type:
When the system displays the following, removal is finished:
4. After the program is removed, delete the directory where NVSD is installed.
7.4.0 Removing from Windows
To remove NVSD from a Windows system, complete the applicable steps.
For Windows Vista, perform the following steps:
2. Do one of the following:
If you are using the CD, insert the CD into the drive.
If you are using the downloaded package, navigate to the SmartDisk
directory in which the decompressed files reside.
3. Double-click the install.exe file.
4. When the Welcome dialog appears, click Finish.
5. When the Installation Complete dialog appears, click Close to dismiss it.
pkgrm smartdisk
The following package is currently installed:
smartdisk SmartDisk
(i386) 001
Do you want to remove this package? [y,n,?,q]
## Removing installed package instance <smartdisk>
This package contains scripts which will be executed with
super-user permission during the process of removing this
package.
Do you want to continue with removal of this package?
[y,n,?,q]
Removal of <smartdisk> was successful.
83
6. After the program is removed, delete the directory where NVSD was
installed.
For all other Windows systems, perform the following steps:
1. Access Control Panel > Add or Remove Programs.
2. In the Currently installed programs list, select NetVault SmartDisk, and
click Remove.
3. When the confirmation message appears, click Yes to continue.
4. After the program is removed, delete the directory where NVSD was
installed.
Chapter 7
Uninstalling NVSD
84
85
Chapter 8:
REINSTALLING NVSD
Reinstalling NVSD An Overview
Prerequisites for Reinstalling NVSD
Reinstalling NVSD if identity.cfg is Available
Reinstalling NVSD if identity.cfg is Not Available
8.1.0 Reinstalling NVSD An Overview
In a standard NVSD installation, the NVSD software binaries are installed on a
volume that is separate from the NVSD Storage Pools. Reinstalling the NVSD
software binaries is required in one of the following scenarios:
NVSD is inoperable because a media failure occurred on the volume where
the NVSD software binaries are installed.
The OS of the machine where the NVSD Instance is running has become
corrupted.
NVSD was removed from a Windows or Solaris machine. During the
uninstall, the software binaries were removed, but the data stored in the
NVSD Storage Pools was left intact.
NVSD was removed from a Linux or Mac OS X machine. Before the software
binaries were uninstalled, the data in the NVSD Storage Pools was preserved
as described in Preserving Data Before Removing NVSD on page 81.
In the preceding scenarios, the data in the NVSD Storage Pools is still intact and
can be used by a new installation of the NVSD software binaries. Each NVSD
installation of the software binaries creates a unique identity that is referenced in
the NVSD Content Index and your backup product; therefore, it is critical that you
use the following procedures to ensure that the new NVSD installation of the
software binaries points to the original NVSD Storage Pools. Failure to follow
these steps will render NVSD unable to read or restore from the original
NVSD Storage Pools.
8.2.0 Prerequisites for Reinstalling NVSD
Ensure that the following prerequisites are met before reinstalling the NVSD
software binaries.
All the original Storage Pool directories, which include the directories for the
Content Index, Staging Store, Chunk Index, and Chunk Store, are available in
their entirety and are not corrupted.
Chapter 8
Reinstalling NVSD
86
All the original Storage Pool directories have been moved or copied to a
different directory via OS commands.
All the original Storage Pool directories, which are now empty, are available
for the new NVSD software binary installation and there is sufficient available
disk space to store all the data that originally resided in these directories.
The original identity.cfg configuration file is available. This file is located in
the following directory:
For Linux, UNIX, or Mac OS X:
/diskmanager/etc
For Windows:
\diskmanager\etc
The same version of the NVSD software is installed that was running on the
original NVSD installation.
8.3.0 Reinstalling NVSD if identity.cfg is Available
If the original identity.cfg configuration file is available, reinstall the NVSD
software binaries by performing the following steps:
1. Ensure that the NVSD non-privileged user account has full access to the
original NVSD Storage Pool directories.
2. Install the same version of the NVSD software that was originally running.
During the installation, make sure that you enter the original values for the
following options:
Non-privileged User Account
Staging Path Folder or Staging Store Directory
Store Path Folder or Chunk Store Directory
For more information, see Installing the NVSD Software on page 53.
3. Update the NVSD Configuration to ensure that the directory structure for the
Content Index, Staging Store, Chunk Index, and Chunk Store matches the
For more information, see Updating the Storage Pool Directory Structure on
page 75.
4. Stop the NVSD Services.
For more information, refer to the Quest NetVault SmartDisk Administrators
Guide.
87
5. Replace the identity.cfg file with the original file.
This file is located is located in the following directory:
/diskmanager/etc
For Windows:
\diskmanager\etc
6. Use OS commands to copy the contents of the original Storage Pool
directories, which were moved to a different directory, back to the original
corresponding directories.
7. Start the NVSD Services.
Guide.
8. If you are using NVBU, complete the following steps:
a. If a media failure occurred on the volume where the NVBU Server
software binaries are installed, thus rendering NVBU Server inoperable,
reinstall NVBU with the identical NVBU Machine Name.
b. If the original NVBU installation is still operational, use the NVBU Console
to remove the corresponding NVSD Device from the Device
Management window by using the Force Removal option.
This changes the device-status indicator for the NVSD Device to Offline.
c. Use the Device Management window in the NVBU Console to add the
new NVSD Instance to NVBU.
d. Right-click the NVSD Device on the Devices tab in the NVBU Console to,
and select Scan.
Scanning an NVSD Device queries all the backups stored on the NVSD
Device and makes them available for restores.
Note: For more information on the preceding substeps, refer to the Quest NetVault
Backup Installation Guide and the Quest NetVault Backup Administrators Guide.
9. If you are using a different product, refer to the documentation that came with
that product.
Chapter 8
Reinstalling NVSD
88
8.4.0 Reinstalling NVSD if identity.cfg is Not
Available
If the original identity.cfg configuration file is not available, reinstall the NVSD
software binaries by performing the following steps:
1. Ensure that the NVSD non-privileged user account has full access to the
original NVSD Storage Pool directories.
2. Install the same version of the NVSD software that was originally running.
During the installation, make sure that you enter the original values for the
following options:
Non-privileged User Account
Staging Path Folder or Staging Store Directory
Store Path Folder or Chunk Store Directory
For more information, see Installing the NVSD Software on page 53.
3. Update the NVSD Configuration to ensure that the directory structure for the
Content Index, Staging Store, Chunk Index, and Chunk Store matches the
For more information, see Updating the Storage Pool Directory Structure on
page 75.
4. Stop the NVSD Services.
Guide.
5. Use OS commands to copy the contents of the original Storage Pool
directories, which were moved to a different directory, back to the original
corresponding directories.
6. Start the NVSD Services.
Guide.
7. If you are using NVBU, complete the following steps:
a. If a media failure occurred on the volume where the NVBU Server
software binaries are installed, thus rendering NVBU Server inoperable,
reinstall NVBU with the identical NVBU Machine Name.
b. If the original NVBU installation is still operational, use the NVBU Console
to remove the corresponding NVSD Device from the Device
Management window by using the Force Removal option.
89
c. Use the Device Management window in the NVBU Console to add the
new NVSD Instance to NVBU.
d. Right-click the NVSD Device on the Devices tab in the NVBU Console to,
and select Scan.
e. Stop the NVBU Service.
f. Stop the NVSD Services.
For more information, refer to the Quest NetVault SmartDisk
Administrators Guide.
g. Run the NVDB Checker using the nvmeddbcheck list command in the
NVBU Command Line Interface (CLI).
h. Use the NVDB Checker output to identify the NVSD identity.
For example, if the output from the NVDB Checker includes an error
similar to:
Failed to locate RAS device object for Mid
770400003a9a164b225fada7380e000001000000
it indicates that the NVSD identity is
770400003a9a164b225fada7380e000001000000.
i. Edit the identity.cfg file to replace the current value for the Identity
field with the one displayed in the NVDB Checker output.
This file is located is located in the following directory:
/diskmanager/etc
For Windows:
\diskmanager\etc
j. Start the NVSD Services.
k. Start the NVBU Service.
l. Use the NVBU Console to remove the original corresponding NVSD
Device from the Device Management window by using the Force
Removal option in the NVBU Console.
m. Right-click the NVSD Device on the Devices tab, and select Force Add to
add the new NVSD Instance to NVBU.
n. Right-click the NVSD Device on the Devices tab in the NVBU Console,
and select Scan.
Chapter 8
Reinstalling NVSD
90
Note: For more information on the preceding substeps, refer to the Quest NetVault
Backup Installation Guide, Quest NetVault Backup Administrators Guide, and
Quest NetVault Backup Command Line Interface Reference Guide.
8. If you are using a different product, refer to the documentation that came with
that product.
91
Chapter 9:
UPGRADING NVSD
Checking the Status and Taking the Device Offline
Upgrading the NVSD Software
9.1.0 Checking the Status and Taking the Device
Offline
Quest Software recommends that you upgrade NVSD when the NVSD Instance is
not currently in use, that is, when it is not involved in a backup or restore
operation, when data is not being deduplicated, and when Garbage Collection is
not running. Quest Software also recommends that you take the corresponding
backup device offline before performing the upgrade. If a job starts while the
NVSD Device is offline and the NVSD Device is the only target for the job, the job
will fail until the device is back online.
To check the status and take the device offline in NVBU, perform the following
steps (for other backup products, refer to the documentation that came with the
product):
1. In the NVBU Console, open the NVBU Device Management window.
For more information on using the NVBU Console, refer to the Quest
NetVault Backup Administrators Guide.
2. On the Devices tab, right-click the applicable NVSD Device, and select
Status.
3. On the Activity tab, make sure that Jobs from this Server Using Device
and Items Deduplicating are both 0, and that Garbage Collection State is
Not in GC.
4. To dismiss the dialog, click OK.
5. On the Devices tab, right-click the applicable NVSD Device, and select
Offline.
6. Repeat these steps for each NVBU Server on which the NVSD Instance has
been added as an NVSD Device.
Chapter 9
Upgrading NVSD
92
9.2.0 Upgrading the NVSD Software
To upgrade your current NVSD installation, perform the following steps:
1. Step through the installation process as outlined in Installing NVSD on page
49.
During the upgrade process, the installation utility will automatically stop and
restart the NVSD Services
2. If you are upgrading a Windows installation and a Windows Restart Now or
Restart Later prompt appears, click the applicable button.
If necessary, NVSD automatically installs the supporting Microsoft Visual C++
files into the Global Assembly Cache. If these files are currently in use by
another application, the installer will prompt you to restart the system. This is
standard Windows behavior.
3. In the interface for your backup product, complete the applicable steps to
bring the device online.
93
Chapter 10:
TROUBLESHOOTING NVSD
Corrupted or Missing Installfiles Subdirectory Impedes Removal or Upgrade
on Windows
10.1.0 Corrupted or Missing Installfiles Subdirectory
Impedes Removal or Upgrade on Windows
The directory in which NVSD is installed on Windows (for example, C:\Program
Files\Quest Software\NetVault SmartDisk) should contain an installfiles
subdirectory. If this subdirectory, or any of its contents, is deleted or moved, any
attempt to uninstall or upgrade NVSD will fail. This subdirectory contains
components that are critical to the removal and upgrade processes.
If this subdirectory was modified, deleted, or moved, you can obtain it from the
original installation package or from the most recent upgrade package. Copy the
subdirectory and its contents to the location in which NVSD is installed (for
example, C:\Program Files\Quest Software\NetVault SmartDisk).
Note: If the package that you used to install or upgrade NVSD is not available, you
can try using a more recent package; however, be aware that this might not work if
the management of upgrades or uninstalls has changed significantly between the
two packages.
Chapter 10
Troubleshooting NVSD
94

SOL90713 Quest NetVault SmartDisk 1.5.1 Installation Upgrade Guide Rev1 0 PDF

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

SOL90713 Quest NetVault SmartDisk 1.5.1 Installation Upgrade Guide Rev1 0 PDF

Încărcat de

Drepturi de autor:

Formate disponibile

NSD-101-1.5.

S-ar putea să vă placă și