Quest NetVault SmartDisk

Quest NetVault SmartDisk
Quest® NetVault® SmartDisk
version 2.0
Administrator’s Guide
NSD-102-2.0-EN-01 11/09/12
© 2012 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 purchaser’s personal use
without the written permission of Quest Software, Inc.
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, Simplicity at Work, FlashRestore, GigaOS,
and NetVault are trademarks and registered trademarks of Quest Software, Inc., and its
subsidiaries. For a complete list of Quest Software’s 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 #7,814,260; 7,913,043; 7,979,650; 8,086,782;
8,145,864; 8,171,247; 8,255,654; and 8,271,755. Protected by Japanese, E.U., French, and UK
patents 1615131 and 05250687.0, and German patent DE602004002858. Additional patents
pending.
Table of Contents
Chapter 1: Introducing Quest NetVault SmartDisk
•
•
•
•
•
•
5
Quest NetVault SmartDisk – At a Glance ........................................................................ 5
Key Benefits ...................................................................................................................... 6
Feature List ....................................................................................................................... 7
Target Audience ................................................................................................................ 7
Recommended Additional Reading ................................................................................ 7
About Quest Software ...................................................................................................... 8
- Contacting Quest Software .............................................................................................................. 8
- Contacting Quest Support ................................................................................................................ 8
Chapter 2: Integrating NVSD with Your Backup Product
9
• Integration – An Overview ............................................................................................... 9
• Verifying that the Client Ports are Open ......................................................................... 9
• Adding Devices to Your Software Product ................................................................... 10
Chapter 3: Using the Command Line Interface (CLI)
•
•
•
•
11
NVSD CLI – An Overview ............................................................................................... 11
Accessing Command Help ............................................................................................ 12
Using CLI Commands .................................................................................................... 12
Processing Basic Shell Commands .............................................................................. 13
-
Determining the Status of NVSD Services ..................................................................................... 13
Starting NVSD Services ................................................................................................................. 13
Stopping NVSD Services ............................................................................................................... 14
Restarting NVSD Services ............................................................................................................. 14
Viewing NVSD Log Files ................................................................................................................ 14
Dumping NVSD-Related Information to a Compressed File .......................................................... 15
Chapter 4: Configuring NVSD
17
• NVSD Configuration – An Overview ............................................................................. 17
• Using the Config Command Options ............................................................................ 17
4
Table of Contents
• Configuring Garbage Collection ....................................................................................21
- Additional Guidelines ..................................................................................................................... 21
• Extending NVSD Storage Pools .....................................................................................23
- Adding a Volume ............................................................................................................................ 25
- Adding a CIFS Share ..................................................................................................................... 25
• Updating Port Configuration for Communication with Your Software .......................26
- Modifying the Messaging Port ........................................................................................................ 26
- Modifying the Data Port ................................................................................................................. 27
• Enabling or Updating Authentication for WebDAV Access .........................................29
- Disabling Authentication ................................................................................................................ 30
• Changing a User Name or Password (Windows Only) ................................................31
• Reviewing the Existing Configuration ...........................................................................32
Chapter 5: Monitoring Performance
35
• NVSD Performance Monitoring – An Overview ............................................................35
• Viewing NVSD Statistics .................................................................................................35
- Viewing NVSD Statistics in a Terminal Session or Command Prompt .......................................... 35
- Viewing NVSD Statistics in a Browser ........................................................................................... 35
- Reviewing the List of NVSD Statistics ........................................................................................... 36
• Calculating the Deduplication Ratio ..............................................................................42
• Calculating the Reduction in the Storage Footprint ....................................................43
• Monitoring Activity on Configured Volumes ................................................................43
Appendix A: Troubleshooting NVSD
45
• Managing Trace Files ......................................................................................................45
- Using Resource Management ....................................................................................................... 45
- Managing Circular Tracing ............................................................................................................. 49
•
•
•
•
•
•
Windows Installation Succeeds but the Percolator Fails to Connect ........................52
Backup Stalls While Writing to NVBU-Related Media ..................................................53
NVSD Compatibility with McAfee VirusScan ................................................................53
CSD Crashes and Backups Fail on Windows 32-Bit Systems ....................................54
Backups Fail with “Stream has gone down” Message on Windows Systems ..........54
Garbage Collection Fails Repeatedly or Conflicts with Other Operations ................55
Quest NetVault SmartDisk
Administrator’s Guide
5
Chapter 1:
INTRODUCING QUEST
NETVAULT SMARTDISK
1.1.0

Quest NetVault SmartDisk – At a Glance

Key Benefits

Feature List

Target Audience

Recommended Additional Reading

About Quest Software

Contacting Quest Software

Contacting Quest Support
Quest NetVault SmartDisk – At a Glance
Quest NetVault SmartDisk’s (NVSD’s) disk-based backup and datadeduplication option reduces storage costs with its powerful byte-level, variableblock-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 Software
Data Protection 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 NVSD’s 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.
6
Chapter 1
Introducing Quest NetVault SmartDisk
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. 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 tieredstorage deployments.

Shrinks Backup Windows – To shrink backup windows with no additional
impact on protected-server resources, you can schedule NVSD’s postprocess 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, and you can
focus on other critical tasks.
Quest NetVault SmartDisk
Administrator’s Guide
1.3.0
1.4.0
7
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
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 Installation/Upgrade Guide – This guide describes
how to install NVSD.

Quest NetVault SmartDisk Compatibility Guide – This guide lists the
operating systems and versions supported by NVSD.
https://support.quest.com/Search/SearchDownloads.aspx
8
Chapter 1
Introducing Quest NetVault SmartDisk
1.6.0
About Quest Software
Established in 1987, Quest Software (Nasdaq: QSFT) provides simple and
innovative IT management solutions that enable more than 100,000 global
customers to save time and money across physical and virtual environments.
Quest products solve complex IT challenges ranging from database management,
data protection, identity and access management, monitoring, user workspace
management to Windows management. For more information, visit
www.quest.com.
1.6.1
Contacting Quest Software
Email:
info@quest.com
Mail:
Quest Software, Inc.
World Headquarters
5 Polaris Way
Aliso Viejo, CA 92656
USA
Web site:
www.quest.com
For regional and international office information, refer to the web site.
1.6.2
Contacting 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 our Support Portal at
www.quest.com/support.
From our Support Portal, you can do the following:

Retrieve thousands of solutions from the online Knowledge Base.

Download the latest releases and service packs.

Create, update, and review Support cases.
View the Global Support Guide for a detailed explanation of support programs,
online services, contact information, policies. and procedures. The guide is
available at www.quest.com/support.
Quest NetVault SmartDisk
Administrator’s Guide
9
Chapter 2:
INTEGRATING NVSD WITH
YOUR BACKUP PRODUCT
2.1.0

Integration – An Overview

Verifying that the Client Ports are Open

Adding Devices to Your Software Product
Integration – An Overview
NVSD integrates with most products by adding an NVSD Instance to your product
as a backup device (an NVSD Device) that you can target for backups and
restores.
NVSD uses the transmission control protocol (TCP) to communicate with your
product.
2.2.0
Verifying that the Client Ports are Open
Quest Software recommends that you verify that the ports are open between the
backup clients and the system on which NVSD is installed.
To verify that the ports are open, you can use a wget command, a web browser, or
another method of your choice. If the port is open, the command returns the
current status information.
In the following examples, replace <port#> with the applicable port number, and
replace <hostName> with the IP address of the machine on which NVSD is
installed.
To use the wget command:
1. On the system on which NVSD is installed, type:
wget http://<localhost>:<port#>/proc/dedupe/stats.stnz
2. On each client that will target backups to the NVSD Device, type:
wget http://<hostName>:<port#>/proc/dedupe/stats.stnz
10
Chapter 2
Integrating NVSD with Your Backup Product
To use a web browser:
1. On the system on which NVSD is installed, type:
http://<localhost>:<port#>/proc/dedupe/stats.stnz
2. On the system on which the backup server or client software is installed, type:
http://<hostName>:<port#>/proc/dedupe/stats.stnz
2.3.0
Adding Devices to Your Software Product
After you have installed NVSD, you must add it as a backup device in your
software product before you can target it for backups and restores. For more
information, refer to the documentation that came with your backup software.
Note: If you are using NVBU, be aware that NVBU will automatically select a
different device if BRE is selected on the Plugin Options tab of the Configurator
window because NVSD does not currently support the NDMP Backup Restart
Extension (BRE) Interface.
Quest NetVault SmartDisk
Administrator’s Guide
USING
3.1.0
11
Chapter 3:
COMMAND LINE
INTERFACE (CLI)
THE

NVSD CLI – An Overview

Accessing Command Help

Using CLI Commands

Processing Basic Shell Commands

Determining the Status of NVSD Services

Starting NVSD Services

Stopping NVSD Services

Restarting NVSD Services

Viewing NVSD Log Files

Dumping NVSD-Related Information to a Compressed File
NVSD CLI – An Overview
Configuration and administration of NVSD is handled primarily through the NVSD
CLI. Using the smartdisk.sh shell on Linux, UNIX, and Mac OS X, or the
smartdisk.bat shell on Windows, you can perform basic functions such as
accessing help regarding the available commands, and configuring, monitoring,
starting, and stopping NVSD. On Windows, the .bat extension is optional. To
eliminate the need to specify the extension on Linux, UNIX, and Mac OS X, NVSD
uses a symbolic link from smartdisk to smartdisk.sh.
The basic structure is:
…/foundation/bin/smartdisk <command>
Additionally, if you specify a full path on Windows, you can use forward slashes (/)
instead of backward slashes (\). Otherwise, you must use backward slashes.
To simplify the commands and code samples shown throughout this document,
forward slashes are used and the .sh and .bat extensions are not shown.
Additionally, the path to where you installed NVSD is represented by an ellipsis
(…). Replace the ellipsis with the applicable information.
Important: If you are using NVSD on Windows 2008, Windows Vista, or
Windows 7, be aware that you must use a Run as Administrator command
prompt instead of a standard command prompt to execute any of the CLI
12
Chapter 3
Using the Command Line Interface (CLI)
commands. Otherwise, you might receive an Access Denied message, even if
you have administrator privileges.
To use a Run as Administrator command prompt:
1. Click Start, and select Run.
2. On the Run dialog, type cmd, and press Ctrl+Shift+Enter.
3. If you receive a confirmation prompt, click Continue.
The Administrator Command Prompt appears.
3.2.0
Accessing Command Help
1. Initiate a terminal session, or open a command prompt.
2. Type:
…/foundation/bin/smartdisk help
NVSD displays a list of the available options and an explanation of how to
use them.
3.3.0
Using CLI Commands
The following table lists all the commands in alphabetical order. Unless specified
otherwise, the command is available on all systems.
Command
Description
Available on
config
Displays and modifies the NVSD configuration. For more All
information, see Using the Config Command Options.
dump
Places a copy of all relevant files into a compressed file
(for more information, see Dumping NVSD-Related
Information to a Compressed File).
All
help
Displays a complete list of the NVSD commands
supported on the NVSD platform.
All
license
Installs a license key. For more information, refer to the
Quest NetVault SmartDisk Installation/Upgrade Guide.
All
logs
Displays the NVSD logs, which are used for diagnosis.
All
password
Lets you change the name or password (or both) of the
non-privileged user that was stored when you originally
installed NVSD. If you change the non-privileged user
name or password after installation, you must use this
command to change it in NVSD as well.
Windows only
restart
Stops and restarts the NVSD Services. Must be
executed by a Root-Level or Administrator User.
All
Quest NetVault SmartDisk
Administrator’s Guide
3.4.0
Command
Description
start
Starts the NVSD Services. Must be executed by a Root- All
Level or Administrator User.
stats
Displays NVSD statistics that you can use to monitor
NVSD performance. For more information, see Viewing
NVSD Statistics.
All
status
Indicates whether the NVSD Services are running.
All
stop
Stops the NVSD Services.
All
uninstall
Removes the NVSD software binaries. Must be
All except
executed by a Root-Level or Administrator User. For
Solaris and
more information, refer to the Quest NetVault SmartDisk Windows
Installation/Upgrade Guide.
version
Displays the current version of NVSD that is installed.
Available on
All
Processing Basic Shell Commands
The following sections list the common commands that you might use.
3.4.1
Determining the Status of NVSD Services
1. Initiate a terminal session, or open a command prompt.
2. Type:
…/foundation/bin/smartdisk status
If NVSD services are running, NVSD displays:
Percolator slave is listening
If NVSD Services are not running, NVSD displays:
Failed to connect to percolator slave
3.4.2
Starting NVSD Services
1. Initiate a terminal session, or open a command prompt.
2. As the root user or using sudo on Linux, UNIX, or Mac OS X, or as an
administrator on Windows, type:
…/foundation/bin/smartdisk start
NVSD starts the NVSD Services.
Services started ok.
13
14
Chapter 3
Using the Command Line Interface (CLI)
Note: On Windows, you can also start the NVSD Services by clicking Start >
Settings > Control Panel > Administrative Tools > Services and starting
Foundation Services ID <NVSDInstanceID>.
3.4.3
Stopping NVSD Services
1. Initiate a terminal session, or open a command prompt.
2. Type:
…/foundation/bin/smartdisk stop
NVSD stops the NVSD Services. You might see the following message.
Services stopped ok.
Note: On Windows, you can also stop the NVSD Services by clicking Start >
Settings > Control Panel > Administrative Tools > Services and stopping
Foundation Services ID <NVSDInstanceID>.
3.4.4
Restarting NVSD Services
To stop and start the NVSD Services automatically, complete the following steps:
1. Initiate a terminal session, or open a command prompt.
2. As the root user or using sudo on Linux, UNIX, or Mac OS X, or as an
administrator on Windows, type:
3. Type:
…/foundation/bin/smartdisk restart
NVSD stops and restarts the NVSD Services.
Services stopped ok.
.
Services started ok.
3.4.5
Viewing NVSD Log Files
1. Initiate a terminal session, or open a command prompt.
2. Type:
…/foundation/bin/smartdisk logs
NVSD displays the NVSD Logs and all relevant information. When you run
logs without any options, it displays all NVSD log entries.
Quest NetVault SmartDisk
Administrator’s Guide
15
3. To display specific information, use one of the following options:
Logs Option
Description
--file <pathToFile>
Displays the contents of the specified file.
--help
Displays a list of the available options and an
explanation of how to use them.
--last-hours <x>
Displays the records for the specified number of
hours.
--time-interval <yyyy- Displays the records for the specified timeframe.
mm-dd-hhmmss yyyy-mmdd-hhmmss>
You can also view logs via the applicable OS-based location.
3.4.6

To view the logs in Windows, use the Event Viewer.

To view the logs on a Linux-based system, look for messages in the /var/log
directory.
Dumping NVSD-Related Information to a Compressed
File
Use the dump command to place a copy of all relevant files (such as release
information, .cfg files, and log information) into a compressed file, which you can
then forward to Quest Support for evaluation of a case. On Linux, UNIX, and Mac
OS X, this command must be executed by a Root-Level or Administrator User; on
Windows, the amount of information collected increases if a user with
administrative privileges executes the command.
Note: On Windows platforms, executing the dump command includes any
installation-related logs that were created by the same user; therefore, if
installation-related logs are required for collection, the user that executes the
dump command must be the same user that performed the installation.
1. Initiate a terminal session, or open a command prompt.
2. As the root user or using sudo on Linux, UNIX, or Mac OS X, or as an
administrator on Windows, type:
…/foundation/bin/smartdisk dump <PathAndFileName>.tar.gz
NVSD processes the dump command, copies the applicable files to the
specified location, and compacts them into one compressed file.
16
Chapter 3
Using the Command Line Interface (CLI)
Quest NetVault SmartDisk
Administrator’s Guide
17
Chapter 4:
CONFIGURING NVSD

NVSD Configuration – An Overview

Using the Config Command Options

Configuring Garbage Collection




Extending NVSD Storage Pools

Adding a Volume

Adding a CIFS Share
Updating Port Configuration for Communication with Your Software

Modifying the Messaging Port

Modifying the Data Port
Enabling or Updating Authentication for WebDAV Access

4.1.0
Additional Guidelines
Disabling Authentication

Changing a User Name or Password (Windows Only)

Reviewing the Existing Configuration
NVSD Configuration – An Overview
You can use the NVSD CLI config command to perform tasks such as enabling
deduplication, enabling deduplication compression, configuring the deduplication
window, configuring Garbage Collection, and extending NVSD Storage Pools by
adding additional volumes.
4.2.0
Using the Config Command Options
Before using the NVSD CLI config command, note the following:

All times are displayed in the local time for the machine where the NVSD
Instance is installed.

With the --volume and --pool options, be aware that the <path> and <label>
strings are case-sensitive because they identify a specific NVSD Storage
Pool or Volume.

If a configuration-related command fails and displays a message similar to
“Failed to apply configuration,” Quest Software recommends that you use the
config command with the --show option to display the current configuration,
18
Chapter 4
Configuring NVSD
and double-check the case of the specified NVSD Storage Pool or Volume to
ensure that the strings reflect the case-sensitivity.

The NVSD Services must be running before you can use the config
command and most of the options. To view the options that are available, you
can use the --help option while NVSD Services are offline.
The NVSD CLI config command supports the following options:
Config Option
Description
--help
Displays a list of the config command options and
their syntax.
--show
Displays the current values for the NVSD
configuration.
--dedupe-enable
<TRUE|FALSE>
Enables or disables NVSD Deduplication.
Deduplication is disabled for all backup jobs even if
deduplication is enabled for the backup job and the
NVSD Instance is licensed for the NVSD
Deduplication Option.
--dedupe-compression
<TRUE|FALSE>
Enables or disables compression of NVSD-unique
Chunks. Disabled by default, compressing unique
Chunks can reduce their storage footprint up to 50%.
Compression is performed on the unique Chunks
that result from the deduplication process.
Compressing the initial Full Backup for a data set
might take longer than not compressing the unique
data because a large majority of the data is
considered unique. Subsequent Full Backups will
have significantly fewer unique Chunks and will not
experience an increase in the amount of time it takes
to complete the deduplication and compression
process.
--gc-enable
<TRUE|FALSE>
Enables or disables NVSD Garbage Collection.
Garbage Collection is enabled unless you disable it
by using this option. Disabling Garbage Collection
overrides the existing Garbage Collection Window
configuration. When it is disabled, it does not run
even if it is required and the Deduplication Engine is
available. This setting remains in effect (persists)
following a NVSD restart.
Quest NetVault SmartDisk
Administrator’s Guide
Config Option
19
Description
--add|--delete
--dedupe-window
<[Sun|Mon|Tue|Wed|Thu|
Fri|Sat-]HH:MMHH:MM>|<Never|Anytime>
Sets the deduplication window by specifying the
times that deduplication can be performed. By
default, the deduplication window is set to Anytime.
Available parameters include:
 Days of Week – Specifies the days of the week
on which the deduplication process runs. Note
that you can schedule it to run on multiple days,
such as Monday, Wednesday, and Friday.
 HH:MM-HH:MM – Using a 24-hour clock,
specifies the times of day at which the
deduplication process runs.
 Never –Disables the deduplication window.
Backups enabled for deduplication will remain in
the Staging Store in a non-deduplicated state
until the deduplication window is enabled.
 Anytime – Enables the deduplication process to
be run at any time. Deduplication for a backup
data stream begins after the initial 400GB has
been written to the Staging Store, which can
provide nearly inline deduplication performance.
--add|--delete
--gc-window
<[Sun|Mon|Tue|Wed|Thu|
Fri|Sat-]HH:MMHH:MM>|<Never|Anytime>
Sets the Garbage Collection window by specifying
the times that NVSD Garbage Collection has priority
over deduplication. By default, the Garbage
Collection window is set to 18:00 through 06:00 for
every night.
Available parameters include:
 Days of Week – Specifies the days of the week
on which the Garbage Collection process runs.
Note that you can schedule it to run on multiple
days, such as Monday, Wednesday, and Friday.
 HH:MM-HH:MM – Using a 24-hour clock,
specifies the times of day at which the Garbage
Collection process runs.
 Never –Disables the Garbage Collection window.
 Anytime – Enables the Garbage Collection
process to be run at any time.
--dedupe-active-limit
<Unlimited|limit>
Specifies the maximum number of segments that can
be deduplicated simultaneously.
20
Chapter 4
Configuring NVSD
Config Option
--network-capacity
<MBps>
Description
Specifies the capacity, in megabytes per second
(MBps), of the network between the NVSD Device
and the backup clients. The NVSD Random Access
Store (RAS) Controller uses this figure when it
calculates the NVSD Device availability score. The
availability score is calculated by comparing the
current throughput and comparing it to maximum
capacity. The availability score is reported by the
RAS Controller to your backup software.
--stream-limit <limit> Specifies the number of data streams that can be
processed simultaneously.
--add|--update
--volume <path>
[Parameters]
Extends NVSD Storage Pools by adding or updating
existing volumes in the NVSD Storage Pools. For
more information, see Extending NVSD Storage
Pools.
--add|--update
--webdav <port>
[--block-size <bytes>]
[--credentials]
[--preferred-address
<address>]
Modifies the port that the NVSD Device uses to
communicate with the backup clients or NDMP
Devices. For more information, see Modifying the
Data Port.
--add|--update --ndmp
[--port <port>]
[--block-size <bytes>]
[--credentials]
[--preferred-address
<addresses>]
Used in conjunction with --add, modifies the port that
--delete --webdav
<port> [--credentials] the NVSD Device uses to communicate with the
--delete --ndmp --port
<port>
--update --remote-port
<port>
backup clients or NDMP Devices. For more
information, see Modifying the Data Port.
Modifies the port that the NVSD Device uses to
communicate with the backup software. For more
information, see Modifying the Messaging Port.
Quest NetVault SmartDisk
Administrator’s Guide
4.3.0
21
Configuring Garbage Collection
NVSD needs to balance its time between deduplicating new backup streams and
performing Garbage Collecting of unreferenced Chunks from retired backups. If
you are using deduplication and Garbage Collection, Quest Software recommends
that you use following guidelines to establish your settings:

4.3.1
Using your hardware as the guideline, tune the number of deduplication
processes that run in parallel:

For each Staging volume, cap the number of associated deduplicators to
the number of disks in the corresponding RAID, making sure to exclude
parity disks. For example, for a RAID 5 of eight disks, you would set the
cap to 7. For more information, see the description for --dedupe-cap
under Extending NVSD Storage Pools.

Make sure that the overall limit, which is independent from volumes, is
adhered to. Use the --dedupe-active-limit option to specify the maximum
number of segments that can be simultaneously deduplicated to match
the number of CPU cores, up to a practical maximum of 16. For more
information, see the description for --dedupe-active-limit under Using the
Config Command Options.

For new and upgraded installations of NVSD, update the Garbage Collection
window to match the backup window. You might also consider setting
Garbage Collection to start approximately 30 minutes before backups start,
which discourages new deduplication processes from starting and
overlapping with the backup window.

The default Chunk-page size for Garbage Collection is 256MB. Prior to v1.6,
the default was 64MB. The larger Chunk page size supports faster Garbage
Collection counting, due to less Chunk-page metadata input and output. The
default settings of the Garbage Collection window and Chunk-page size are
not changed during upgrades. Generally, Quest Software recommends that
you leave the Chunk-page size at its current setting.
Additional Guidelines
Quest Software recommends that you use the default setting of Anytime for the
deduplication window, and that you adjust the Garbage Collection windows to
match your backup windows. Beginning with v1.6, the default Garbage Collection
window for new installations is from 18:00 through 06:00 every night. As indicated
previously, you might consider setting Garbage Collection to start 30 minutes
before backups start.
To review the current settings, use the following command:
…/foundation/bin/smartdisk config --show
22
Chapter 4
Configuring NVSD
For example, if your backup window is 00:00-04:00, consider setting your
Garbage Collection window to 23:30-04:00. You must first delete the current
setting, and then you can add the new setting:
…/foundation/bin/smartdisk config --delete --gc-window
Sun-18:00-06:00
…/foundation/bin/smartdisk config --add --gc-window Sun23:30-04:00
On average, Garbage Collection needs one-third of each day (or week), which
leaves the remaining two-thirds for deduplication. The Garbage Collection window
indicates when Garbage Collection has priority over deduplication — it does not
mean that Garbage Collection runs only during this time. Garbage Collection
might also run outside the Garbage Collection window.
Deduplication processes are only started within the deduplication window, which is
why Quest Software recommends that you leave this setting at Anytime. Individual
deduplication processes run until they are finished, while Garbage Collection can
be interrupted automatically to start deduplications. By using the per-volume -dedupe-cap, NVSD automatically schedules deduplications to start when it is not
busy receiving backups. Garbage Collection is started only when it is required,
and when it has priority. After retirements (Manifests have been marked for
deletion), Garbage Collection is required. Beginning with v1.6, NVSD also
recognizes that Garbage Collection counting work is required after any
deduplications have completed (new Manifests have been added).
After all deduplications have completed, NVSD waits for five minutes (the default
Inactivity Timeout of 300 seconds) before starting Garbage Collection. This
prevents Garbage Collection from starting and getting interrupted almost
immediately, which would clutter the logs. However, it also means that NVSD is
not performing work during that time (unless it is receiving backups). Therefore, it
is important to the overall deduplication throughput that the Garbage Collection
window is not significantly longer than it needs to be.
Quest NetVault SmartDisk
Administrator’s Guide
4.4.0
23
Extending NVSD Storage Pools
You can extend NVSD physical capacity by adding or updating the volumes
specified for the NVSD Storage Pools. Use the config --add|--update --volume
<path> command to extend the NVSD physical capacity. You can also use the
following additional parameters:
Note: The NVSD Non-privileged User must have access to any volumes that are
added to ensure that configuration changes are successfully applied.
Config Volume Parameters
Description
--volume <path>
Specifies the path for the file-system path of the
volume to be used as an NVSD Storage Pool. You
can specify local drives or Universal Naming
Convention (UNC) paths for Common Internet File
System (CIFS), Network File System (NFS), and
Storage Area Network (SAN). If the volume is on a
mounted file system, make sure that the specified
path is a valid subdirectory on the mounted file
system (and not the mounted directory itself). This
ensures that data is not written to the local directory
if the mounted location is unavailable.
[--volume-size <%>]
Specifies a percentage of the volume that cannot be
used by NVSD.
The value of ((100 - X) / 100) * (total volume size)
is added to the Last Resort Threshold (LRT). In
addition, a small amount of storage is reserved to
complete Garbage Collection. These three
components of reserved storage determine the total
amount of storage set aside that cannot be directly
used by NVSD.
For example, if volume-size is set to 30 and the
volume’s size is 100GB, 70GB is set aside (in
addition to the LRT and Garbage Collection reserve
space) and cannot be used by NVSD.
[--dedupe-cap
<Unlimited|cap>]
Specifies the maximum number of backup segments
for the specific volume that can be deduplicated
simultaneously. Defaults to 4.
[--pool <label>]
Specifies the Label assigned to the Storage Pool.
Defaults to a system-generated numeric label.
Specify an existing Storage Pool label to add the
volume to an existing Storage Pool, or specify a new
name to create a new Storage Pool.
24
Chapter 4
Configuring NVSD
Config Volume Parameters
[--reservation-size
<bytes>]
Description
Specifies the number of bytes reserved by the
processes streaming data into NVSD. A smaller size
results in NVSD having to reserve space more
frequently; a larger size renders more disk space
temporarily unavailable. If the Space.Available
(reported via the show option) is less than the
reservation-size, the volume is considered FULL.
Specifies which Storage Pool Roles the volume is
[--favour
<Staging|Storage|"Chunk available to perform. To specify multiple roles, list
the --favour parameter multiple times. For example:
Index"|"Disk
--favour Staging --favour "Disk
Index"|All|None>]…
Index"
Use in conjunction with --deny to dedicate a volume
to one or more roles.
[--deny
<Staging|Storage|"Chunk
Index"|"Disk
Index"|All|None>]…
Specifies which Storage Pool Roles the volume is
not available to perform. To specify multiple roles,
list the --deny parameter multiple times.
For example:
--deny Storage --favour "Chunk
Index"
Use in conjunction with --favour to dedicate a
volume to one or more roles.
Note: After a volume has been used by NVSD
as a Chunk Index or Content Index (that is,
data has been staged or stored), NVSD
continues to use the volume for this purpose,
even if this parameter is used to deny it.
[--balancing
<Space|Activity|None>]
Instructs NVSD to use the volume with either the
most space available or the least activity occurring.
If used with --favour and --deny, --balancing is
applied last.
Note: The --balancing parameter provides
guidance to NVSD; the NVSD Disk Manager
and Deduplicator make the final decision about
how to allocate space.
[--account <UNC-pathaccount>]
Required for Windows platform when specifying
UNC paths. Specifies the user account with read
and write permissions to the UNC path.
Quest NetVault SmartDisk
Administrator’s Guide
Config Volume Parameters
[--password <UNC-pathpassword>]
4.4.1
25
Description
Required for Windows platform when specifying
UNC paths. Specifies the password for the user
account with read and write permissions to the UNC
path. Note that this password is case-sensitive.
Adding a Volume

To add a new volume that will be used for all roles, enter the following
command:
…/foundation/bin/smartdisk config --add --volume \mnt
/<newNVSDvolume>
The NVSD configuration is updated.
Configuration applied

To add a volume dedicated to the Chunk Store, enter the following
command:
…/foundation/bin/smartdisk config --add --volume
c:/SDStoragePools2/Store --favour Storage --deny Staging
--deny "Chunk Index" --deny "Disk Index"
The NVSD configuration is updated.
Configuration applied
4.4.2
Adding a CIFS Share
To add a CIFS share, enter the following command:
…/foundation/bin/smartdisk config --add --volume
//<IPaddress>/<NVSDvolume> --account <nonpriviledgedUser>
--password <nonprivilegedUserPassword>
The NVSD configuration is updated.
26
Chapter 4
Configuring NVSD
4.5.0
Updating Port Configuration for Communication
with Your Software
By default, NVSD uses port 37452 to communicate with the NVBU Media
Manager and 37453 to communicate with the backup clients that are streaming
data to the NVSD Device. It also uses port 37451 for Inter Process
Communication (IPC) on the loopback interface (but not for remote connections).
Note: If you intend to use different ports (for example, you use a different product,
such as NVBU), Quest Software strongly recommends that you make the
applicable change to the port that communicates with the Media Manager before
you add the NVSD Device to your software; otherwise, you will have to remove the
NVSD Device from your software and add it back in again. You can update the
port that communicates with your software at any time.
If you use Network Data Management Protocol (NDMP) with NVSD, the default
range of communication ports is 37454–38453. NVSD only monitors these ports
when media for an NDMP transfer is requested. If more than one NDMP port is
provided, NVSD first attempts to listen to the first port that you set; if that port is
busy (that is, it is already in use for another NDMP transfer), NVSD checks the
next port in the list. The number of NDMP ports determines how many NDMP
transfers can occur simultaneously. After an NDMP transfer finishes, NVSD stops
listening to the applicable port.
Note that if you use NDMP, the <port> variable can contain any of the following:

One port number (for example, 37454)

A list of port numbers (for example, 37454, 37455, 37456)

A range of port numbers (for example, 37454-37456)

A combination of the preceding options (for example, 37454, 37460, 3747037479)
Note: If you use any option other than the individual port number, use quotation
marks to specify the ports in the command line (for example, --port “37454, 37460,
37470-37479”).
4.5.1
Modifying the Messaging Port
If you want to use a different port, complete the following steps.
1. Initiate a terminal session, or open a command prompt.
2. As the root user or using sudo on Linux, UNIX, or Mac OS X, or as an
administrator on Windows, type:
…/foundation/bin/smartdisk config
Quest NetVault SmartDisk
Administrator’s Guide
27
NVSD displays the list of options and parameters that you can use, including
the section for configuring the remote port.
3. To use a different port, type:
…/foundation/bin/smartdisk config --update --remote-port
<port>
Replace <port#> with the port that you want to use.
4.5.2
Modifying the Data Port
If you want to use a different port to communicate with the clients (including NDMP
Devices) that stream data to the NVSD Device, complete the following steps.
Important: You cannot add a port that already exists. If you try to add an existing
port, you will see a “Failed to apply configuration” message. Before attempting to
add a port, use the config --show command option to view existing information.
1. Initiate a terminal session, or open a command prompt.
2. As the root user or using sudo on Linux, UNIX, or Mac OS X, or as an
administrator on Windows, type:
…/foundation/bin/smartdisk config
NVSD displays the list of options and parameters that you can use, including
the sections for configuring the ports:
config --add|--update --webdav <port> [--block-size
<bytes>] [--preferred-address <address>] [--credentials]
[--authlifetime = <ValueInSeconds>]
config --add|--update --ndmp [--port <port>]
[--block-size <bytes>] [--preferred-address <address>]
[--credentials]
You can use --block-size to define the block size used to read and write
blocks when streaming data to the Staging Store. You can use --preferredaddress to define the primary IP address that clients should use when
communicating with the NVSD Device. You can use --credentials to enable
authentication and define the authorized user and password. You can use
--authlifetime to specify a lifetime value for nonce reuse, which allows
credentials to be reused across multiple connections (NVSD implements a
new nonce for every connection if the value is 0 or is blank).
28
Chapter 4
Configuring NVSD
3. If you are modifying port information for a non-NDMP device, complete any of
the following:

To add a new port, type:
…/foundation/bin/smartdisk config --add --webdav <port#>
Replace <port#> with the port that you want to use.

To remove the original port (the following uses the default), type:
…/foundation/bin/smartdisk config --delete --webdav 37453
4. If you are modifying port information for an NDMP Device, complete any of
the following:

To add new ports, type:
…/foundation/bin/smartdisk config --add --ndmp --port
<port#>
Note: Before using the --add option, you must delete the existing NDMP ports.
Replace <port#> with the port that you want to use. The --port <port#>
segment can contain any of the following:

A single port number:
…/foundation/bin/smartdisk config --add --ndmp
--port 37454

A list of port numbers:
…/foundation/bin/smartdisk config --add --ndmp
--port "37454, 37455"

A range of port numbers:
…/foundation/bin/smartdisk config --add --ndmp
--port "37460-37469"

A combination of the preceding options:
…/foundation/bin/smartdisk config --add --ndmp
--port "37454, 37455, 37460-37469"
Note: To specify more than one port, enclose the port numbers in quotation marks.

To remove the original port for an NDMP Device, type:
…/foundation/bin/smartdisk config --delete --ndmp
Quest NetVault SmartDisk
Administrator’s Guide
29
5. To verify that the new port has been added and the original has been
removed, type:
…/foundation/bin/smartdisk config --show
NVSD displays results similar to the following example for a non-NDMP
device:
[Interface:Data]
Block Size = <blockSize>
Credentials = <Name:MaskedPassword>
Port = <NewPort#, NewPort#>
Authorization Lifetime = <ValueInSeconds>]
Type = WebDAV
NVSD displays results similar to the following example for an NDMP Device:
[Interface:Data]
Port = <NewPort#>
Preferred Contract Address =
Block Size = <blockSize>
Type = NDMP
4.6.0
Enabling or Updating Authentication for
WebDAV Access
If you want to enable authentication for WebDAV access of NVSD for the data
port, complete the following steps to specify the credentials. (NVSD uses digestaccess authentication, specifically RFC 2069.) You can also use this same
procedure to update existing credentials.
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.

If you intend to use the NVBU Use optimised replication between devices that
support this feature option (available for NVBU Data Copy and Duplicate
operations), be aware that WebDAV authentication fails if the configured
credentials are different on the source and destination NVSD Servers. Successful
replication requires that either authentication is disabled on both instances, is
enabled only on the source, or uses identical credentials on the source and
destination NVSD Instances.
1. Initiate a terminal session, or open a command prompt.
30
Chapter 4
Configuring NVSD
2. As the root user or using sudo on Linux, UNIX, or Mac OS X, or as an
administrator on Windows, type:
…/foundation/bin/smartdisk config
NVSD displays the list of options and parameters that you can use, including
the section for configuring authentication:
config --add|--update --webdav <port> [--block-size
<bytes>] [--preferred-address <address>] [--credentials]
[--authlifetime = <ValueInSeconds>]
3. To define the credentials, type:
…/foundation/bin/smartdisk config --update
--webdav <port#> --credentials
Replace <port#> with the port that you are using.
4. When the Username prompt appears, enter the user name that should be
used for access, and press Enter.
5. When the Password prompt appears, enter the password associated with
the specified user name, press Enter, enter the password again when the
Confirm Password prompt appears, and press Enter again.
NVSD displays results similar to the following example:
./smartdisk config --update --webdav 37453 --credentials
Username: NVSDuser
Password:
Confirm Password:
Configuration applied
6. In your backup software, configure the same credentials for backups and
restores to the NVSD Instance.
If you are using NVBU, be aware that authentication is not required to add
NVSD to NVBU, but it is required for performing backups and restores that
use NVSD as the target. For more information on configuring credentials in
NVBU, refer to the Quest NetVault Backup Administrator’s Guide.
4.6.1
Disabling Authentication
To disable WebDAV authentication, complete the following steps.
1. Make sure that no backup or restore jobs are currently active.
2. Initiate a terminal session, or open a command prompt.
Quest NetVault SmartDisk
Administrator’s Guide
31
3. As the root user or using sudo on Linux, UNIX, or Mac OS X, or as an
administrator on Windows, type:
…/foundation/bin/smartdisk config --delete --webdav
<port> --credentials
4. When the prompt appears that asks for the current WebDAV credentials,
enter the applicable name and password.
5. To verify that the port has been defined correctly, type:
…/foundation/bin/smartdisk config --show
NVSD displays results similar to the following example:
[Interface:Data]
Block Size = 32768, B
Port = 37453
Authorization Lifetime = 0
Type = WebDAV
4.7.0
Changing a User Name or Password (Windows
Only)
To change the name or case-sensitive password (or both) of the non-privileged
user on Windows platforms, complete the following steps:
Important: Changing the non-privileged user affects the number of people who
have read- and write-access to the Windows Application log. For more
information, refer to the Authentication Requirements topic in the Quest
NetVault SmartDisk Installation/Upgrade Guide.

The password is case-sensitive.
1. If you are changing a user name, stop the NVSD Services.
For more information, see Stopping NVSD Services.
2. Initiate a terminal session, or open a command prompt.
3. As an administrator on Windows, type the following:
…/foundation/bin/smartdisk password <username> <password>
For example:
…/foundation/bin/smartdisk password NVSDUser NewPassword
4. If you changed the user name, start the NVSD Services.
For more information, see Starting NVSD Services.
32
Chapter 4
Configuring NVSD
4.8.0
Reviewing the Existing Configuration
To review the NVSD configuration, enter the following command:
…/foundation/bin/smartdisk config --show
The NVSD configuration is displayed, including the following details on the
Storage Pool volumes:
[SmartDisk:Volume]
Storage Pool = Store
Location = c:\SDStoragePools2\Store
Disk Manager Index = TRUE
Space.Limit = 100, %
Space.Reservation Size = 1073741824, B
Favour = Storage, Chunk Index, Disk Index
Deny = Staging
Balancing = Activity
Space.OS.Available = 17928032256, B
Space.Available = 15175759872, B
Space.Staging.Status = Not Configured
Space.Staging.Available = 0, B
Space.Staging.Reserved = 0, B
Space.Last Resort = 2752272384, B
Data.Staged = 0, B
Deduplication Activity Cap = 4
Active Operations = 0
Quest NetVault SmartDisk
Administrator’s Guide
[SmartDisk:Volume]
Storage Pool = Staging Pool
Location = c:\SDStoragePools2\Stage
Disk Manager Index = FALSE
Space.Limit = 100, %
Space.Reservation Size = 1073741824, B
Favour = Staging
Deny = Storage, Chunk Index, Disk Index
Balancing = Activity
Space.OS.Available = 3681370112, B
Space.Available = 2607628288, B
Space.Staging.Status = Available
Space.Staging.Available = 2607628288, B
Space.Staging.Reserved = 0, B
Space.Last Resort = 1073741824, B
Data.Staged = 0, B
Deduplication Activity Cap = 4
Active Operations = 0
33
34
Chapter 4
Configuring NVSD
Quest NetVault SmartDisk
Administrator’s Guide
35
Chapter 5:
MONITORING PERFORMANCE
5.1.0

NVSD Performance Monitoring – An Overview

Viewing NVSD Statistics

Viewing NVSD Statistics in a Terminal Session or Command Prompt

Viewing NVSD Statistics in a Browser

Reviewing the List of NVSD Statistics

Calculating the Deduplication Ratio

Calculating the Reduction in the Storage Footprint

Monitoring Activity on Configured Volumes
NVSD Performance Monitoring – An Overview
NVSD provides the ability to monitor its performance and to calculate the following
statistics:
5.2.0

Deduplication Ratio

Disk Space Savings
Viewing NVSD Statistics
You can view NVSD statistics from a terminal session, command prompt, or
browser.
5.2.1
Viewing NVSD Statistics in a Terminal Session or
Command Prompt
1. Initiate a terminal session, or open a command prompt.
2. Type:
…/foundation/bin/smartdisk stats
NVSD displays the statistics described under Reviewing the List of NVSD
Statistics.
5.2.2
Viewing NVSD Statistics in a Browser
In a browser, enter the following URL:
http://<NVSD_Instance_Hostname>:<Backup_Software_Client_Port>/proc/
stats.stnz
36
Chapter 5
Monitoring Performance
For example:
http: // 10.1.0.0:37453/proc/stats.stnz
NVSD displays the statistics in XML format in the browser. For a description of the
statistics, see Reviewing the List of NVSD Statistics.
5.2.3
Reviewing the List of NVSD Statistics
When reviewing the following list of statistics, be aware that a backup job is
divided into a minimum of two segments: Segments contain either data or
metadata and are smaller than 400GB. For example, if the backup data stream is
1200GB, the backup job will have three data segments. One NVSD element is
equivalent to one backup segment.
Note: The list of statistics displayed for the Dedupe:StatusSubsys segment is
affected by the current status of the Chunk Store Daemon (CSD).
Stat Entry
[SmartDisk:Deduplication
Scheduler]
Description
Statistics for the process that
schedules deduplication activity.
Elements.Queued = <No.>
Number of segments awaiting
deduplication.
Data.Queued = <No.>, B
Number of bytes awaiting
deduplication.
Elements.Deduplicating = <No.>
Number of elements or backup
segments currently deduplicating.
Data.Deduplicating = <No.>, B
Total size of elements or backup
segments currently deduplicating.
After all current deduplication
completes, the equivalent amount of
data is removed from the Staging
Store.
Deduplication Available = TRUE
Displays TRUE or FALSE depending
on whether the CSD is available for
deduplication tasks.
Deduplication Enabled = TRUE
Displays TRUE or FALSE depending
on whether the data-deduplication
option is licensed and enabled.
Quest NetVault SmartDisk
Administrator’s Guide
Stat Entry
37
Description
GC Enabled = TRUE
Displays TRUE or FALSE depending
on whether Garbage Collection is
enabled. Disabling Garbage
Collection overrides the existing
Garbage Collection Window
configuration. If disabled, it does not
run even if it is required and the
Deduplication Engine is available.
GC Required = FALSE
Displays TRUE or FALSE depending
on whether Garbage Collection is
needed. Garbage Collection is
required after data has been
deduplicated or retired from storage.
GC Active = FALSE
Indicates whether Garbage Collection
is active.
GC Start In = <No.>
Current number of seconds remaining
before Garbage Collection might start.
This statistic only appears if GC
Required = TRUE. Additionally, even
if the field displays 0, it indicates that
collection can start at the next
permitted opportunity; it does not
indicate that it will.
[SmartDisk:RAS Controller]
Availability Score = <No.>
Statistics for the process that interacts
with your backup software.
Indicates how available a backup
server should consider this NVSD
Device to be. The lower the number,
the less available the NVSD Device is.
Given a choice of two NVSD Devices
to target a backup job to, your backup
software might choose the one with
the higher Availability Score. The
score takes the following into account:
 Number of data streams NVSD is
receiving in or retrieving from the
Staging Store.
 Percentage of available network
bandwidth that these data streams
are using.
38
Chapter 5
Monitoring Performance
Stat Entry
Description
Sent MBps = <No.>
Total megabytes per second (MBps)
across all streams being sent out from
NVSD to your backup software; that
is, when a restore job is being
performed.
Received MBps = <No.>
Total MBps across all streams being
sent to NVSD; that is, when a backup
job is targeted to an NVSD Device.
Machine ID = <3-XXXX-XXX>
Machine ID of the NVSD Instance that
is used to obtain a permanent license
key.
Soft stream limit = <No.>
Current maximum number of data
streams or backups that your backup
software can target to this NVSD
Device simultaneously.
Version = <NVSDversion>
NVSD version
Build Level = <NVSDbuild>
NVSD build
[SmartDisk:Service Manager]
Statistics for the NVSD Task Manager.
Active = 0
Total number of active NVSD
operations.
Active.Read = <No.>
Current number of backup segments
being read.
Active.Write = <No.>
Current number of backup segments
being written.
Active.Delete = <No.>
Current number of backup segments
being deleted.
Active.MkDir = <No.>
Not currently used.
Active.Move = <No.>
Not currently used.
Active.Read Properties= <No.>
Not currently used.
Active.Read Options= <No.>
Not currently used.
Active.Delete Staging= <No.>
Not currently used.
Active.Delete Rollback= <No.>
Not currently used.
Active.Rollback Element= <No.>
Not currently used.
Quest NetVault SmartDisk
Administrator’s Guide
Stat Entry
[Dedupe:StatSubsys]
39
Description
Statistics for the NVSD Deduplication
Processes.
pages = <No.>
Current number of Chunk pages
stored on disk. Chunks are organized
into pages of Chunks. The default size
of a Chunk page is a maximum of
256MB.
chunks = <No.>
Total number of unique Chunks stored
in the Chunk Store of this NVSD
Device.
index_bytes = <No.>
Total number of bytes on disk used by
the Chunk Index.
num.pages = <No.>
num.lcp = <No.>
num.chunks = <No.>
num.pages_max = <No.>
num.lcp_max = <No.>
num.chunks_max = <No.>
num.hits = <No.>
num.misses = <No.>
num.store_misses = <No.>
num.added_pages = <No.>
num.added_lcp = <No.>
num.evicted_pages = <No.>
num.evicted_lcp = <No.>
num.cache_memory = <No.>
For use by Quest Support, if
necessary.
csd.gc_page =<No.>
csd.gc_pages = <No.>
csd.gc_index_ops_done = <No.>
streams = <No.>
Total number of elements or backup
segments that have been
deduplicated.
catalog_bytes = <No.>
Total number of bytes used by a
volume’s catalog.
ondisk_bytes = <No.>
Total number of bytes on disk used by
deduplicated data. Includes the bytes
consumed by the Chunk Store,
Chunk Index, and Manifests.
40
Chapter 5
Monitoring Performance
Stat Entry
Description
gc_reserve_bytes = <No.>
Number of bytes that NVSD must
keep available on a file system to
guarantee that Garbage Collection
can take place. Increases as the size
of the Chunk Store increases.
stream_bytes = <No.>
Total number of bytes submitted for
deduplication.
csd.stream_bytes = <No.>
Total number of bytes submitted for
deduplication since the NVSD
Services were started. When a
backup is retired, the size of the
backups is not deleted from
csd.stream_bytes.
csd.chunk_bytes = <No.>
Total number of bytes of unique
Chunks stored since the NVSD
Services were started.
in_gc = <No.>
Indicates whether Garbage Collection
is currently happening.
csd.gc_state = Not in GC
The phase of Garbage Collection that
is currently occurring.
csd.last_successful_gc = <Time
stamp>
Date and time stamp that indicates
when Garbage Collection was last
completed successfully. Displays
None if collection has not yet
completed.
csd.last_stopped_gc = <Time
stamp>
Date and time stamp that indicates
when Garbage Collection was last
interrupted (for example, by the
deduplication process). Displays None
if collection has not been interrupted.
csd.last_failed_gc = <Time
stamp>
Date and time stamp that indicates
when Garbage Collection last failed to
complete because an error occurred.
Displays None if collection has not
failed.
status = <currentStatus>
Status reported by the CSD; includes
Available, Unavailable, and
NotConfigured. Used to determine
whether the CSD is available for
deduplication tasks and whether
space is available.
Quest NetVault SmartDisk
Administrator’s Guide
Stat Entry
available_bytes = <No.>
[SmartDisk:Disk Storage]
41
Description
Total number of bytes available for
storage of deduplicated data.
Statistics for NVSD Disk Storage.
Index.Location = <…/store>
Location of the Staging Store volume
used for the Content Index.
Index.Fixed = TRUE
Displays TRUE or FALSE depending
on whether the location is fixed
(TRUE) or can be moved to another
location (FALSE) by using the
--favour and --deny options. For more
information on the favour and deny
options, see Extending NVSD Storage
Pools.
Elements = <No.>
Number of elements or backup
segments currently residing in the
Storage Pools.
Data = <No.>, B
Amount of data, in bytes, currently
residing in the Storage Pools.
Data.Committed = <No.>, B
Amount of data, in bytes, that has
completed the write-to-disk process.
Space.Licensed = Unlimited
Maximum number of front-end
terabytes (TBs) that this NVSD
Instance is licensed to protect. (This
information is presented in GBs.) For
more information on the licensing
model, refer to the Quest NetVault
SmartDisk Installation/Upgrade Guide.
This is the maximum amount of data a
single instance of NVSD will store; it is
not the amount of license capacity
purchased.
License.Type = <No.>
Displays 1 for node-tied, 7 for floating,
or 18 for evaluation.
License.Expiration = <No.>
Displays -1 for a permanent license, or
displays the number of days
remaining for the existing license.
License.Dedupe = <No.>
Displays 1 if deduplication is licensed;
otherwise, displays 0.
Space.OS.Available = <No.>, B
Number of bytes available across all
configured NVSD Storage Pools;
reported by the OS.
42
Chapter 5
Monitoring Performance
Stat Entry
5.3.0
Description
Space.Available = <No.>, B
Number of bytes available across all
configured NVSD Storage Pools. For
more information on space allocation,
refer to the applicable topic in the
Quest NetVault SmartDisk
Installation/Upgrade Guide.
Space.Staging.Status =
<CurrentStatus>
Status of NVSD Staging Store;
includes Available, Full, Unlicensed,
and License Exceeded.
Space.Staging.Available =
<No.>, B
Number of bytes available for Staging
Store across all configured NVSD
Storage Pools.
Elements.Staged = <No.>
Number of elements or backup
segments currently residing in the
Staging Store.
Data.Staged = <No.>, B
Amount of data, in bytes, currently
residing in the Staging Store.
Elements.Accumulative = <No.>
Number of elements or backup
segments processed by NVSD since
its implementation.
Data.Accumulative = <No.>, B
Total amount of data, in bytes,
processed by NVSD since NVSD was
installed.
Data.Committed.Accumulative =
<No.>, B
Total amount of data, in bytes, that
has completed the NVSD write-to-disk
process since NVSD was installed.
Calculating the Deduplication Ratio
Use the following calculation to determine the NVSD Deduplication Ratio for the
data that has been protected by NVSD:
stream_bytes / ondisk_bytes = NVSD Deduplication Ratio
Use the following calculation to determine the NVSD Deduplication Ratio for the
data that has been protected by NVSD since the NVSD Services were started:
csd.stream_bytes / csd.chunk_bytes = NVSD Deduplication
Ratio since NVSD were started
For information on viewing NVSD statistics in your backup software, refer to the
documentation that came with your product.
Quest NetVault SmartDisk
Administrator’s Guide
5.4.0
43
Calculating the Reduction in the Storage
Footprint
The NVSD Deduplication Option reduces the storage footprint required to store
the protected data. To calculate the reduction in the storage footprint that NVSD is
currently providing for protected data, use the following calculation:
(ondisk.bytes / stream.bytes) * 100 = NVSD Reduction in
Storage Footprint
5.5.0
Monitoring Activity on Configured Volumes
You can check the current activity level for volumes that are currently configured
for use with NVSD. For example, you might do this to understand why NVSD is not
processing data that you believe is ready for deduplication. By monitoring the
current activity, you can determine whether a significant number of backups are
being written to the volume, which delays deduplication activity. (Data remains
queued for deduplication, and then begins after backup activity is reduced.)
To check the activity level, view NVSD statistics by using either the config --show
command and option (for more information, see Using the Config Command
Options) or by using the
http://<localhost>:<port#>/proc/diskmanager/diskstorage/stats.stnz
command in your web browser.
In the output that is displayed, review the information in the [SmartDisk:Volume]
section to determine the level of activity.
For example:
[SmartDisk:Volume]
Storage Pool = Staging Pool
Location = /usr/smartdisk/diskmanager/stage
…
Favour = Staging
Deny = Storage, Chunk Index, Disk Index
…
Deduplication Activity Cap = 4
Active Operations = 4
The Active Operations value shows the number of NVSD disk-access operations
occurring on the applicable volume. In the preceding example, there are four
active operations on the Staging volume, /usr/smartdisk/diskmanager/stage,
and the Deduplication Activity Cap is set to 4. This means that deduplication of
44
Chapter 5
Monitoring Performance
data staged on this volume starts when the number of active operations on that
volume is fewer than four.
The Deduplication Activity Cap minimizes the amount of disk thrashing that occurs
when performing simultaneous access activities of the Staging volume. If
deduplication of staged data is not taking place on an NVSD Instance during the
deduplication window, you can check the Deduplication Activity Cap and Active
Operations information for each configured Staging volume to determine if activity
is preventing deduplication. (If so, you might want to adjust the backup or
deduplication window to eliminate overlaps.)
You can set an activity cap for a volume by using the --dedupe-cap option with the
config --add|--update --volume <path> command (for more information, see
Extending NVSD Storage Pools).
Quest NetVault SmartDisk
Administrator’s Guide
45
Appendix A:
TROUBLESHOOTING NVSD

A.1.0
Managing Trace Files

Using Resource Management

Managing Circular Tracing

Windows Installation Succeeds but the Percolator Fails to Connect

Backup Stalls While Writing to NVBU-Related Media

NVSD Compatibility with McAfee VirusScan

CSD Crashes and Backups Fail on Windows 32-Bit Systems

Backups Fail with “Stream has gone down” Message on Windows Systems

Garbage Collection Fails Repeatedly or Conflicts with Other Operations
Managing Trace Files
Because system performance can be affected when either the number of trace
files in a directory or the combined size of trace files becomes significant, you can
configure trace management and circular tracing to control these issues. NVSD
includes two features for managing trace files, both of which are enabled by
default:
A.1.1

resourcemanager – This process manages the combined number and size
of all trace files by periodically deleting inactive files. It runs as a persistent,
“start-of-day” process, along with others such as logd and superserver.

Circular tracing – This feature lets you control the number and size of trace
files generated by NVSD processes.
Using Resource Management
Based on how you configure it, the resourcemanager can check the trace files
every minute after NVSD startup. The resourcemanager reads the configured
values at the start of every repeat cycle (for example, every minute), which
ensures that it reads configuration changes that are made while the process is
running.
Using the Modules section in the /foundation/etc/resourcemanager.cfg file and
the ResourceManagement:TraceDelete section in each module’s /etc/trace.cfg
file, you can specify which modules you want the resourcemanager to monitor and
manage.
46
Appendix A
Troubleshooting NVSD
In the following example, the resourcemanager is set to manage the
diskmanager, dedupe, and foundation modules.
[Trace:Delete]
Modules = diskmanager, dedupe, foundation
Several types of trace file are created by NVSD (*.trc, *.buffer, *monitorrecent*.txt,
*monitortrace*.txt), but only certain ones are eligible for deletion by the
resourcemanager. Understanding the naming convention applied to these files is
critical, because it is key to how the resourcemanager determines what to include
or exclude from its eligible list. The following table identifies the naming convention
used for the different files and the different platforms.
File Type
Naming Convention
*.trc
<processName>.<processID>.<threadID>.<sequenceNumber>.trc
*.buffer
<processName>.<processID>.<threadID>.buffer
*monitorrecent*.txt
On Linux, UNIX, and Mac OS X:
monitorrecent.<processID>.<sequenceNumber>.txt
Windows:
monitorrecent.<sequence number>.txt
*monitortrace*.txt
On Linux, UNIX, and Mac OS X:
monitortrace.<processID>.<sequenceNumber>.txt
Windows:
monitortrace.<sequenceNumber>.txt
The resourcemanager only considers trace files as contributing to the totals it
compares against the start and stop thresholds if it identifies them as inactive,
which means that they are not associated with a process that is currently running.
It determines this by comparing the process ID in the trace file name with the list of
IDs for processes that are running on the system at the start of each repeat cycle.
Because the process ID is not used in the file name on all OSs, the
resourcemanager can delete *.trc, *.buffer, monitorrecent*, and monitortrace*
files on Linux, UNIX, and Mac OS X, but it can only delete *.trc and *.buffer files
on Windows, as shown in the preceding table.
A.1.1.a
Specifying Which Modules to Manage
1. Initiate a terminal session, or open a command prompt.
2. Using a text editor, open the resourcemanager.cfg file:
This file is located at: …/foundation/etc/resourcemanager.cfg
3. Locate the [Trace:Delete] section.
4. In the Modules = line, enter the applicable modules.
Quest NetVault SmartDisk
Administrator’s Guide
47
For example:
[Trace:Delete]
Modules = diskmanager, dedupe, foundation
Note: You can specify any module. The resourcemanager only applies trace
deletion to the specified modules if it locates them in the directory in which NVSD
is installed. If it cannot locate a specified module, it generates its own error-level
trace message, but continues to function normally.
A.1.1.b
Configuring the Trace-Delete Option in Specific Modules
To limit the overall number or size (or both) of trace files in an installed module's
trace directory, you can configure the resourcemanager to delete them between
start and stop number and size thresholds. You can set these thresholds via the
ResourceManagement:TraceDelete section of a module's etc/trace.cfg file. If
that section is not present or is invalid, hard-coded defaults will be used.
The ResourceManagement:TraceDelete section in the
<moduleName>/etc/trace.cfg file lets the resourcemanager determine which
trace-delete parameters to apply in the specified module. The defaults are:
[ResourceManagement:TraceDelete]
Enabled = TRUE
Number Start Threshold = 100
Number Stop Threshold = 10
Size Start Threshold
= 1,GB
Size Stop Threshold
= 1,MB
If you change the values and inadvertently render them unacceptable (not present
or invalid), the hard-coded defaults are used instead.
In the preceding example, which shows the defaults, the Trace-Delete functionality
is enabled, and the resourcemanager will start deleting the trace files (oldest first)
that exist in the specified module’s /trace directory when their combined number
becomes equal to or greater than 100 or their combined size becomes equal to or
greater than 1GB. The files will continue to be deleted until their combined number
is reduced to 10 or their combined size reaches or exceeds 1MB.
To modify the values, complete the following steps:
1. Initiate a terminal session, or open a command prompt.
2. Using a text editor, open the trace.cfg file for the applicable module:
This file is located at: …/<moduleName>/etc/trace.cfg
3. Locate the [ResourceManagement:TraceDelete] section.
48
Appendix A
Troubleshooting NVSD
4. Change the values for the Number Start Threshold, Number Stop
Threshold, Size Start Threshold, and Size Stop Threshold values as
appropriate.
The following ranges are acceptable:
Threshold Segment
Minimum
Maximum
Number Start Threshold
1
2147483647
Number Stop Threshold
0
2147483647
Size Start Threshold
1
2147483647
Size Stop Threshold
0
2147483647
For both types of threshold (Number and Size), the start threshold must be
greater than the stop threshold.
The Size threshold entries must use the form <number>,<byteUnit>. The
following byte units are acceptable:
A.1.1.c
Byte Unit Entry
Represents
B
Bytes
KB
Kilobytes
MB
Megabytes
GB
Gigabytes
TB
Terabytes
Disabling Trace Deletion
You can disable trace deletion for all modules or on an individual basis.

To disable it for the NVSD Instance, complete the following steps:
1. Initiate a terminal session, or open a command prompt.
2. Using a text editor, open the resourcemanager.cfg file.
This file is located at: …/foundation/etc/resourcemanager.cfg
3. In the [Trace:Delete] section, delete the value for the Modules =
segment (that is, make sure that it is blank):
[Trace:Delete]
Modules =
To re-enable resource management, enter the applicable module names.

To disable it for a specific module, complete the following steps:
1. Initiate a terminal session, or open a command prompt.
2. Using a text editor, open the trace.cfg file for the applicable module:
Quest NetVault SmartDisk
Administrator’s Guide
49
This file is located at: …/<moduleName>/etc/trace.cfg
3. In the [ResourceManagement:TraceDelete] section, change the value
for the Enabled segment to FALSE:
[ResourceManagement:TraceDelete]
Enabled = FALSE
To re-enable resource management, change the value to TRUE.
A.1.2
Managing Circular Tracing
NVSD uses circular tracing to control the number and size of trace files generated
by NVSD-related processes. Circular tracing, which is based on the maximum
number of messages per file and the maximum number of files per thread, is
enabled by default for all .trc and monitortrace.*.txt files. The following lists the
defaults that are used:
CircularTracingEnabled = TRUE
MaxMessagesPerFile = 500000
MaxFilesToKeep = 10
While the defaults that control tracing are hard-coded in NVSD, you can modify
some of the settings via the trace.cfg file.
You can identify trace files generated by a single thread using the information in
the file name. In general, the file name uses the following format:
<processRelatedName>.<processID>.<threadID>.
<zeroBasedFileSequenceNumber>.<fileExtension>
Note: The monitorrecent and monitortext files do not contain a thread ID on all
platforms, nor do they contain a process ID on Windows.

Even if you disable circular tracing, the file name will contain a sequence number
of 0.
The following table lists the types of trace files that NVSD uses:
Type
Configurable
Description
.buffer
No
The processes that generate these files use
values that ensure there is only one file per thread
with a maximum size of 1MB
monitorrecent*.txt
No
These files, which are generated by the
percolatormonitor, use values that ensure there
are no more than two files present and neither file
exceeds 5,000 messages
50
Appendix A
Troubleshooting NVSD
Type
Configurable
Description
monitortrace.*.txt
No
These files, also generated by the
percolatormonitor, use values that ensure there
are no more than two files present and neither file
exceeds 5,000 messages.
.trc
Yes
The processes that generate these files use
configurable values. The default allows up to
500,000 messages per file and a maximum of 10
files can be present at any time. If you enter an
invalid value, the hard-coded defaults are used
instead.
Configuration information is read once, at startup. (Unlike the settings for the
resourcemanager, changes to the circular-tracing configuration are only applied
after the processes are restarted.) The information is identified in the trace.cfg file
for the relevant module. For example, the trace.cfg file for the diskmanager
module contains information similar to the following:
[TraceToFile:deduplicator]
Level = ERROR
Buffer = ALL
CircularTracingEnabled = TRUE
MaxMessagesPerFile = 2000000
MaxFilesToKeep = 5
[TraceToFile:superserver]
Level = ERROR
Buffer = ALL
[TraceToFile:Fallback]
Level = ERROR
Buffer = ALL
The preceding configuration would result in the following circular-tracing behavior:

Each Deduplicator process thread uses circular tracing with up to 2,000,000
messages per file and allows a maximum of 5 files to be present at any time.

Each superserver process thread uses circular tracing with up to 500,000
messages per file and allows a maximum of 10 files to be present at any time.

Each storageservice (and any other unlisted diskmanager module process)
process thread uses circular tracing with the configured Fallback settings,
which are intentionally excluded in this example, and so use the hard-coded
defaults of allowing up to 500,000 messages per file and a maximum of 10
files to be present at any time.
Quest NetVault SmartDisk
Administrator’s Guide
51
The trace.cfg file for the foundation module might look like this:
[TraceToFile:Fallback]
Level =
ERROR
Buffer = ALL
CircularTracingEnabled = TRUE
MaxMessagesPerFile = 1000000
MaxFilesToKeep = 4
[TraceToFile:ServiceTool]
Level =
ERROR
Buffer = ALL
[TraceToFile:PercolatorSlave]
Level = ERROR
Buffer = ALL
[TraceToFile:logd]
Level = ERROR
Buffer = ALL
CircularTracingEnabled = FALSE
The preceding configuration would result in the following circular-tracing behavior:
A.1.2.a

Each servicetool, percolatorslave, and any other unlisted foundation
module process thread uses circular tracing with the configured Fallback
settings, which in this case allows up to 1,000,000 messages per file and a
maximum of 4 files to be present at any time.

Each logd process thread will trace to a single file without any limitation,
instead of using circular tracing.
Modifying Values for Circular Tracing
As described earlier, circular-tracing information is read once, at startup, so
changes to the circular-tracing configuration are only applied after the processes
are restarted.
To modify circular-tracing values, complete the following steps:
1. Initiate a terminal session, or open a command prompt.
2. Using a text editor, open the applicable trace.cfg file.
3. In the applicable section, change the values for the MaxMessagesPerFile
and MaxFilesToKeep values as appropriate.
The following ranges are acceptable:
1 <= MaxMessagesPerFile <= 2147483647
1 <= MaxFilesToKeep <= 2147483647
52
Appendix A
Troubleshooting NVSD
A.1.2.b
Disabling Circular Tracing
To disable circular tracing, complete the following steps:
1. Initiate a terminal session, or open a command prompt.
2. Using a text editor, open the applicable trace.cfg file.
3. In the applicable section, change the value for the CircularTracingEnabled
segment to FALSE:
CircularTracingEnabled = FALSE
To re-enable tracing, change the value to TRUE.
A.2.0
Windows Installation Succeeds but the
Percolator Fails to Connect
If you install NVSD and the utility indicates that installation completed successfully,
but invoking the smartdisk status command results in a message that indicates
that it failed to connect to the percolator slave, it might be because you created a
non-privileged user whose password needed to be changed before the installation
was attempted.
When you create a non-privileged user, the User must change password at next
login check box is selected by default in some instances (it depends on what
method you use to access the feature that lets you create a user). If you forget to
clear the check box or if you forget to change the password before installing
NVSD, installation appears to succeed.
When this occurs, you must remove NVSD and then reinstall it after completing
either of the following options:

Create a different non-privileged user.

Delete and add the original non-privileged user again.
Note: Logging on as the non-privileged user and changing its password after you
have installed NVSD does not clear this issue.
Another reason that this might occur is because you entered the wrong user name
or password. To update the user name or password after installation, use the
smartdisk password command.
Quest NetVault SmartDisk
Administrator’s Guide
A.3.0
53
Backup Stalls While Writing to NVBU-Related
Media
When the Status of the backup job appears as “Running: (Stalled) Writing to
media” on the Status tab of the NVBU Jobs window, and the Staging status for the
applicable NVSD Instance appears as “FULL” on the Storage tab located on the
Status tab of the NVBU Device Management window, it usually indicates that
NVSD has run out of Licensed Capacity.
At the start of a write, the NVSD Disk Manager verifies that there is still a sufficient
amount of NVSD Licensed Capacity to proceed (that is, that the Licensed
Capacity exceeds the current amount of protected data). If there is Licensed
Capacity available, the write continues to completion. Writes to NVSD are
performed in X-sized units, where X is equal to the reservation-size parameter
described in Extending NVSD Storage Pools. During the write, the Disk Manager
performs a verify after each X bytes is written to determine whether there is
enough usable space available to reserve an additional X bytes. A write will stall if
there is no Licensed Capacity at the beginning of the write, or if at any point during
the write there is not enough available space to reserve X bytes.
For information on increasing the amount of NVSD Licensed Capacity, refer to the
Quest NetVault SmartDisk Installation/Upgrade Guide.
A.4.0
NVSD Compatibility with McAfee VirusScan
If you install NVSD on a Windows system that also runs McAfee VirusScan
Enterprise, problems might occur during data transfers between your backup
software and NVSD. For example, you might see a “Failed SQL insert into log
table” or “2570 0 disk I/O error” message.
If problems do occur, Quest Software recommends that you implement one of the
following workarounds:

Configure McAfee VirusScan to ignore the NVSD installation directory.

Configure McAfee VirusScan to scan only the executable files located in the
NVSD installation directory.

Disable McAfee VirusScan, and use an alternative form of virus protection.
54
Appendix A
Troubleshooting NVSD
A.5.0
CSD Crashes and Backups Fail on Windows
32-Bit Systems
The NVSD CSD supports a Chunk Store of between 1.8TB and 2.5TB on
Windows 32-bit systems (depending on the version of Windows). If this limit is
reached (the system runs out of memory), an assert occurs and NVSD is shut
down. To allow NVSD to restart, backups to be retired, and Garbage Collection to
make space available in the Chunk Store, you must manually edit the
smartdisk.cfg file to disable deduplication, and then enable it again after sufficient
space has been cleared in the Chunk Store.
1. Initiate a terminal session, or open a command prompt.
2. Using a text editor, open the smartdisk.cfg file.
This file is located at: …/diskmanager/etc/smartdisk.cfg
3. To stop deduplication, change the value for the following segment to FALSE:
[Deduplication:Enable]
Value = FALSE
4. After space has been made available, enable duplication.
A.6.0
Backups Fail with “Stream has gone down”
Message on Windows Systems
If the Store volume path and Staging volume path that you specify for NVSD
are network shares, you might encounter an error similar to the following if a
significant amount of load is placed on the share:
Error 2012/02/02 00:48:05 166 <name> Stream has gone down
To avoid this error, adjust the time-out value of the SessTimeout parameter in the
Windows Registry. Modify the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
lanmanworkstation\parameters
SessTimeout=dword:0000012c
Set the time-out value to 300 seconds (5 minutes).
For more information, refer to the following:
http://support.microsoft.com/kb/102067
http://technet.microsoft.com/en-us/library/cc938292.aspx
Quest NetVault SmartDisk
Administrator’s Guide
A.7.0
55
Garbage Collection Fails Repeatedly or
Conflicts with Other Operations
If you have reviewed and processed the guidelines provided in Configuring
Garbage Collection and Garbage Collection continues to fail repeatedly or conflict
with another operation, you can disable it. For more information on disabling the
feature, see the description for the --gc-enable option in Using the Config
Command Options.
56
Appendix A
Troubleshooting NVSD
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising