NAS Platform v13 4 Backup Administration Guide MK-92HNAS007-15 PDF

Backup Administration Guide
Hitachi Virtual Storage Platform Gx00 and Fx00 with NAS

Modules
Hitachi NAS Platform
Release 13.4
MK-92HNAS007-15
March 2018
© 2011, 2018 Hitachi, Ltd. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including copying and
recording, or stored in a database or retrieval system for commercial purposes without the express written permission of Hitachi, Ltd., or
Hitachi (collectively “Hitachi”). Licensee may make copies of the Materials provided that any such copy is: (i) created as an essential step in
utilization of the Software as licensed and is used in no other manner; or (ii) used for archival purposes. Licensee may not make any other
copies of the Materials. “Materials” mean text, data, photographs, graphics, audio, video and documents.
Hitachi reserves the right to make changes to this Material at any time without notice and assumes no responsibility for its use. The Materials
contain the most current information available at the time of publication.
Some of the features described in the Materials might not be currently available. Refer to the most recent product announcement for
information about feature and product availability, or contact Hitachi at https://support.hitachivantara.com/en_us/contact-us.html.
Notice: Hitachi products and services can be ordered only under the terms and conditions of the applicable Hitachi agreements. The use of
Hitachi products is governed by the terms of your agreements with Hitachi.
By using this software, you agree that you are responsible for:
1. Acquiring the relevant consents as may be required under local privacy laws or otherwise from authorized employees and other
individuals; and
2. Verifying that your data continues to be held, retrieved, deleted, or otherwise processed in accordance with relevant laws.
Notice on Export Controls. The technical data and technology inherent in this Document may be subject to U.S. export control laws, including
the U.S. Export Administration Act and its associated regulations, and may be subject to export or import regulations in other countries. Reader
agrees to comply strictly with all such regulations and acknowledges that Reader has the responsibility to obtain licenses to export, re-export, or
import the Document and any Compliant Products.
Hitachi is a registered trademark of Hitachi, Ltd., in the United States and other countries.
AIX, AS/400e, DB2, Domino, DS6000, DS8000, Enterprise Storage Server, eServer, FICON, FlashCopy, IBM, Lotus, MVS, OS/390, PowerPC, RS/6000,
S/390, System z9, System z10, Tivoli, z/OS, z9, z10, z13, z/VM, and z/VSE are registered trademarks or trademarks of International Business
Machines Corporation.
Active Directory, ActiveX, Bing, Excel, Hyper-V, Internet Explorer, the Internet Explorer logo, Microsoft, the Microsoft Corporate Logo, MS-DOS,
Outlook, PowerPoint, SharePoint, Silverlight, SmartScreen, SQL Server, Visual Basic, Visual C++, Visual Studio, Windows, the Windows logo,
Windows Azure, Windows PowerShell, Windows Server, the Windows start button, and Windows Vista are registered trademarks or trademarks
of Microsoft Corporation. Microsoft product screen shots are reprinted with permission from Microsoft Corporation.
All other trademarks, service marks, and company names in this document or website are properties of their respective owners.
Backup Administration Guide for Hitachi NAS Platform ii

Contents
Preface ...............................................................................................................v
Related Documentation........................................................................................v
Accessing product documentation.....................................................................viii
Getting help....................................................................................................... viii
Comments...........................................................................................................ix
Chapter 1: About NDMP backup support........................................... 10

Standard NDMP configuration........................................................................... 10
Storage management applications.....................................................................11
Enabling and disabling NDMP........................................................................... 12
About NDMP user name, password, and version.............................................. 14
Specifying an NDMP user name and password................................................ 14
Enabling and disabling NDMP devices..............................................................15
Modifying NDMP device access configuration ..................................................17
About NDMP with snapshots............................................................................. 21
Configuring NDMP snapshot options.................................................................22
Configuring backup and restore of migrated data..............................................26
Locally migrated data................................................................................... 26
Externally migrated data...............................................................................28
NDMP environment variables............................................................................ 31
Direct............................................................................................................ 31
EXCLUDE.....................................................................................................31
EXTRACT.....................................................................................................32
FILESYSTEM............................................................................................... 32
FUTURE_FILES...........................................................................................32
HIST............................................................................................................. 33
LEVEL.......................................................................................................... 33
NDMP_BLUEARC_AWAIT_IDLE.................................................................33
Contents
Backup Administration Guide for Hitachi NAS Platform 3
NDMP_BLUEARC_EMBEDDED_HARDLINKS........................................... 33
NDMP_BLUEARC_EXCLUDE_MIGRATED................................................ 35
NDMP_BLUEARC_EXTERNAL_LINKS.......................................................36
NDMP_BLUEARC_INCLUDE_ONLY_MIGRATED......................................36
NDMP_BLUEARC_TAKE_SNAPSHOT....................................................... 37
NDMP_BLUEARC_USE_CHANGE_LIST....................................................37
NDMP_BLUEARC_USE_SNAPSHOT_RULE............................................. 37
Contents
Preface
This guide provides information about configuring the server to work with NDMP, and
making and managing NDMP backups. This guide also includes information about
Hitachi NAS Synchronous Image Backup. Note that some features apply only to
individual platforms and may not be applicable to your configuration.
Virtual Storage Platform G400, G600, G800 and Virtual Storage Platform F400, F600, F800
storage systems can be configured with NAS modules to deliver native NAS functionality
in a unified storage platform. The unified VSP Gx00 models and VSP Fx00 models
automatically form a two-node cluster in a single chassis upon installation, with no
external cabling required.
Related Documentation
Release Notes provide the most up-to-date information about the system, including
new feature summaries, upgrade instructions, and fixed and known defects.
Command Line References

The Command Line Reference provides information on the commands used to manage
your system, and includes relevant information on the operation of your hardware and
software. Depending on the model of your server or cluster node, refer to the Command
Line Reference that is appropriate for your system.
■ NAS Module Server Command Line Reference
■ Command Line Reference for models 4060, 4080, and 4100
■ Command Line Reference for models 3080, 3090 and 4040
Backup Administration Guide for Hitachi NAS Platform v

Administration Guides
■ System Access Guide (MK-92HNAS014)—Explains how to log in to the system, provides
information about accessing the NAS server/cluster CLI and the SMU CLI, and
provides information about the documentation, help, and search capabilities available
in the system.
■ Server and Cluster Administration Guide (MK-92HNAS010)—Provides information about
administering servers, clusters, and server farms. Includes information about
licensing, name spaces, upgrading software, monitoring servers and clusters, and
backing up and restoring configurations.
■ Storage System User Administration Guide (MK-92HNAS013)—Explains user
management, including the different types of system administrator, their roles, and
how to create and manage these users.
■ Network Administration Guide (MK-92HNAS008)—Provides information about the
server's network usage, and explains how to configure network interfaces, IP
addressing, name and directory services.
■ File Services Administration Guide (MK-92HNAS006)—Explains about file system
formats, and provides information about creating and managing file systems, and
enabling and configuring file services (file service protocols).
■ Data Migrator Administration Guide (MK-92HNAS005) —Provides information about the
Data Migrator feature, including how to set up migration policies and schedules.
■ Storage Subsystem Administration Guide (MK-92HNAS012)—Provides information about
managing the supported storage subsystems (RAID arrays) attached to the server/
cluster. Includes information about tiered storage, storage pools, system drives (SDs),
SD groups, and other storage device related configuration and management features
and functions.
■ Snapshot Administration Guide (MK-92HNAS011)—Provides information about
configuring the server to take and manage snapshots.
■ Replication and Disaster Recovery Administration Guide (MK-92HNAS009)—Provides
information about replicating data using file-based replication and object-based
replication, provides information on setting up replication policies and schedules, and
using replication features for disaster recovery purposes.
■ Antivirus Administration Guide (MK-92HNAS004)—Describes the supported antivirus
engines, provides information about how to enable them, and how to configure the
system to use them.
■ Backup Administration Guide (MK-92HNAS007)—Provides information about
configuring the server to work with NDMP, and making and managing NDMP backups.
Note: For a complete list of Hitachi NAS open source software copyrights and
licenses, see the System Access Guide.
Backup Administration Guide for Hitachi NAS Platform vi

Hardware References
■ Hitachi NAS Platform 3080 and 3090 G2 Hardware Reference (MK-92HNAS017) —
Provides an overview of the second-generation server hardware, describes how to
resolve any problems, and replace potentially faulty parts.
■ Hitachi NAS Platform and Hitachi Unified Storage Series 4000 Hardware Reference
(MK-92HNAS030)—Provides an overview of the Hitachi NAS Platform Series 4000
server hardware, describes how to resolve any problems, and how to replace
potentially faulty components
■ Hitachi NAS Platform System Manager Unit (SMU) Hardware Reference (MK-92HNAS065)
—This document describes the usage and replacement instructions for the SMU
300/400.
Best Practices
■ Hitachi USP-V/VSP Best Practice Guide for HNAS Solutions (MK-92HNAS025)—The
practices outlined in this document describe how to configure the system to achieve
the best results.
■ Hitachi Unified Storage VM Best Practices Guide for HNAS Solutions (MK-92HNAS026) —
The system is capable of heavily driving a storage array and disks. The practices
outlined in this document describe how to configure the system to achieve the best
results
■ Hitachi NAS Platform Best Practices Guide for NFS with VMware vSphere (MK-92HNAS028)
—This document covers best practices specific to using VMware vSphere with the
Hitachi NAS platform.
■ Hitachi NAS Platform Deduplication Best Practice (MK-92HNAS031)—This document
provides best practices and guidelines for using deduplication.
■ Hitachi NAS Platform Best Practices for Tiered File Systems (MK-92HNAS038)—This
document describes the Hitachi NAS Platform feature that automatically and
intelligently separates data and metadata onto different Tiers of storage called Tiered
File Systems (TFS).
■ Hitachi NAS Platform Data Migrator to Cloud Best Practices Guide (MK-92HNAS045)—
Data Migrator to Cloud allows files hosted on the HNAS server to be transparently
migrated to cloud storage, providing the benefits associated with both local and cloud
storage.
■ Brocade VDX 6730 Switch Configuration for use in an HNAS Cluster Configuration Guide
(MK-92HNAS046)—This document describes how to configure a Brocade VDX 6730
switch for use as an ISL (inter-switch link) or an ICC (inter-cluster communication)
switch.
■ Best Practices for Hitachi NAS Universal Migrator (MK-92HNAS047)—The Hitachi NAS
Universal Migrator (UM) feature provides customers with a convenient and minimally
disruptive method to migrate from their existing NAS system to the Hitachi NAS
Platform. The practices and recommendations outlined in this document describe
how to best use this feature.
■ Hitachi Data Systems SU 12.x Network File System (NFS) Version 4 Feature Description
(MK-92HNAS056)—This document describes the features of Network File System
(NFS) Version 4.
Backup Administration Guide for Hitachi NAS Platform vii

Accessing product documentation
■ Hitachi NAS HDP Best Practices (MK-92HNAS057)—This document lists frequently asked
questions regarding the use of Hitachi Dynamic Provisioning.
■ Hitachi Multi-tenancy Implementation and Best Practice Guide (MK-92HNAS059)—This
document details the best practices for configuring and using Multi-Tenancy and
related features, and EVS security.
■ Hitachi NAS Platform HDP Best Practices (MK-92HNAS063)—This document details the
best practices for configuring and using storage pools, related features, and Hitachi
Dynamic Provisioning (HDP).
■ Hitachi NAS Platform System Manager Unit (SMU) Hardware Reference (MK-92HNAS065)
—This document describes the usage and replacement instructions for the SMU
300/400.
■ Brocade VDX 6740 Switch Configuration for use in an HNAS Cluster Configuration Guide
(MK-92HNAS066)—This document describes how to configure a Brocade VDX 6740
switch for use as an ICC (intra-cluster communication) switch.
■ File System Snapshots Operational Best Practice (MK-92HNAS068)—This document
provides operational guidance on file system snapshots.
■ Virtual Infrastructure Integrator for Hitachi Storage Platforms Operational Best Practice
(MK-92HNAS069)—This document provides operational guidance on Hitachi Virtual
Infrastructure Integrator for the HNAS platform.
■ Hitachi NAS Platform Replication Best Practices Guide (MK-92HNAS070)—This document
details the best practices for configuring and using HNAS Replication and related
features.
■ Hitachi Virtual SMU Administration Guide (MK-92HNAS074)—This guide provides
information about how to install and configure a virtual System Management Unit
(SMU).
■ Hitachi NAS Platform to Hitachi Virtual Storage Platform Unified Gx00 Models Migration
Guide (MK-92HNAS075)—This best practice guide describes how to perform a data-in-
place migration of the Hitachi NAS Platform and Virtual Storage Platform (VSP) Gx00
File solution to the VSP Gx00 platform.
Accessing product documentation

Product user documentation is available on Hitachi Support Connect: https://
knowledge.hitachivantara.com/Documents. Check this site for the most current
documentation, including important updates that may have been made after the release
of the product.
Getting help
Hitachi Support Connect is the destination for technical support of products and
solutions sold by Hitachi. To contact technical support, log on to Hitachi Support Connect
for contact information: https://support.hitachivantara.com/en_us/contact-us.html.
Backup Administration Guide for Hitachi NAS Platform viii

Comments
Hitachi Community is a global online community for Hitachi customers, partners,

independent software vendors, employees, and prospects. It is the destination to get
answers, discover insights, and make connections. Join the conversation today! Go to
community.hitachivantara.com, register, and complete your profile.
Comments
Please send us your comments on this document to
doc.comments@hitachivantara.com. Include the document title and number, including
the revision level (for example, -07), and refer to specific sections and paragraphs
whenever possible. All comments become the property of Hitachi.
Thank you!
Backup Administration Guide for Hitachi NAS Platform ix

Chapter 1: About NDMP backup support
The storage server supports Network Data Management Protocol (NDMP), an open
standard protocol for network-based backups, with two significant advantages:
■ It enables a storage management application to control backup and recovery on
another device without transfer of the backup data across the network.
■ NDMP backups can preserve security settings in a mixed protocol environment,
including virtual volume and quota information.
Standard NDMP configuration

Important: The NAS module architecture does not support the direct
attachment of tape drives or autochangers. LAN-free backup is available only
on the Hitachi NAS Platform.
Figure 1 Standard NDMP configuration
In the diagram, the storage management application sends backup instructions to the
server, which makes a backup copy of data onto tapes in the tape library. The data
travels through the Fibre Channel (FC) network, not the Ethernet network. Details of the
backup data are sent to the storage management application, which initiates recovery of
the data if necessary.

Storage management applications
NDMP transfers data between disks and tapes attached to the same server. Data can
also be transferred between two separate NDMP servers over an Ethernet connection (in
NDMP this is known as a three-way backup or recovery):
Some common applications of NDMP include:

■ Backing up (or recovering) data on a server to (or from) a FC-attached NDMP tape
library.
■ Backing up (or recovering) data on a server without a tape library to (from) a second
storage server that has a tape library attached.
■ Using a utility, such as Accelerated Data Copy (ADC) or Data Replication to copy file
systems between storage servers.
While the server supports backups done over network protocols such as NFS or CIFS,
only NDMP will preserve security settings in a mixed protocol environment, including
virtual volume and quota information.
When using NDMP, the server uses snapshots to backup data consistently and without
being affected by ongoing file activity. Snapshots also facilitate incremental backups.
However, if so desired, data can be backed up without using snapshots.
Storage management applications

The storage server acts as an NDMP server, operating with leading storage management
applications. It supports NDMP Version 2, 3 and 4. The storage server implementation of
NDMP can back up and restore:
■ Both Windows and UNIX files from a single storage management application.
■ The full attributes of each Windows and UNIX file (including Windows ACLs), saving
and restoring whole volumes and preserving all file attributes.Usig NDMP Backups
The server supports recovery of single files or subdirectories, associated lists, or
complete backup images. The Direct Access Recovery (DAR) mechanism can be used,
provided the Storage Management Application supports it. DAR allows NDMP to go
directly to the correct place in the tape image to find the data, rather than reading the
whole image. This can dramatically reduce recovery times.

Enabling and disabling NDMP

The NDMP Configuration page allows you to specify NDMP configuration information
for a cluster or for the currently managed server, including NDMP user name, password,
version, and port. NDMP processing status can be started or stopped at any time.
Procedure
1. Navigate to Home > Data Protection > NDMP Configuration to display the NDMP
Configuration page.
2. Enter the storage server’s NDMP configuration settings.

Field/Item Description
NDMP Settings
User Name The user name cannot be more than 20 characters long and
cannot contain the following characters: \ / < > " '
Password By default, the password is ʺndmpʺ. The password cannot

be more than 20 characters long.
Version By default, the storage server uses NDMP version 4 for

NDMP backup and recovery; if required, it can be configured
for version 2 or 3 of the NDMP protocol.
Note: Both incremental data replication and ADC

require NDMP version 3 or 4. Set NDMP to
version 2 only if required by your backup
software.
Port The NDMP port number. By default, port 10000 is used.
apply Apply the changes made to the NDMP Settings.
NDMP Server Status
Current Status: The options are:

■ start - Enable NDMP server.
■ stop - Disable NDMP server and terminate any NDMP
operations in progress.
Enable NDMP The options are:

Server At Boot:
■ enable - Enable NDMP server at boot time.
■ disable - Disable NDMP server at boot time.
3. Start or stop the NDMP process.
Caution: Read this caution before following instructions to start and

stop! Clicking stop terminates all NDMP processes immediately, leaving
any tapes in use in an untidy state. It may also confuse the storage
management application. To help avoid this, you can terminate NDMP
transfers using the storage management application before clicking stop.
■ To stop NDMP processing, click stop. If any NDMP operations are in progress
when you click stop, those operations will be aborted.
■ To start NDMP processing, click start.
4. Enable or disable the NDMP process at Boot.

■ To automatically enable NDMP processing at Boot, click enable.
■ To automatically disable NDMP processing at Boot, click disable.

About NDMP user name, password, and version
About NDMP user name, password, and version

A storage management application must successfully authenticate a configured NDMP
user before starting a backup or recovery.
Note: Any user with NDMP user name and password knowledge can access
an NDMP-enabled storage management application to access data on the
system. Therefore, customer support recommends taking measures to keep
the information secure.
An administrator can specify two types of users:

■ NDMP Primary User. For an NDMP primary user, an account user name and password
provide full access to the files on the system, supporting most backup, recovery and
replication activities.
■ Restricted NDMP Users. The SSC command ndmp-ruser can create less trusted NDMP
Restricted Users with access to a restricted set of files (and possibly devices). An
administrator could assign these user names to various users to allow them to use
the accelerated data copy (ADC) utility to copy data within limited areas of the file
systems. The SSC command ndmp-ruser-pwd can also change the password for a
selected restricted user.
For more information about ndmp-ruser and ndmp-ruser-pwd, see the Command
Line Reference.
Specifying an NDMP user name and password
Procedure
1. Navigate to Home > Data Protection > NDMP Configuration to display the NDMP
Configuration page.

Enabling and disabling NDMP devices
2. Enter the required information NDMP settings:
NDMP Settings
User Name The user name cannot be more than 20 characters long and
cannot contain the following characters: \ / < > " '
Password By default, the password is ʺndmpʺ. The password cannot

be more than 20 characters long.
Version By default, the storage server uses NDMP version 4 for

NDMP backup and recovery; if required, it can be configured
for version 2 or 3 of the NDMP protocol.
Note: Both incremental data replication and ADC

require NDMP version 3 or 4. Set NDMP to
version 2 only if required by your backup
software.
Port The NDMP port number. By default, port 10000 is used.
apply Apply the changes made to the NDMP Settings.
NDMP Server Status
Current Status: The options are:

■ start - Enable NDMP server.
■ stop - Disable NDMP server and terminate any NDMP
operations in progress.
Enable NDMP The options are:

Server At Boot:
■ enable - Enable NDMP server at boot time.
■ disable - Disable NDMP server at boot time.
3. Click Apply to save your changes.

NDMP backup devices, such as tape libraries and auto-changers, require special
configuration. The server monitors its Fibre Channel (FC) links periodically and
automatically detects the presence of backup devices. Because the server may be
connected into a Storage Area Network (SAN) shared with other servers, it does not
automatically make use of backup devices it detects on its FC links.

Procedure
1. Navigate to Home > Data Protection > NDMP Device List to display the NDMP
Device List page.
Item/Field Description
EVS:Device Displays the EVS or EVSs allowed to use the device, and the ID of
Name the device. This ID is generated by the system and cannot be
changed.
To configure your storage management application to work with
an NDMP device, in the storage management application you
must specify the device name of each autochanger/tape drive
you want the application to use.
WWN Node Displays the WWN (World Wide Name) and LUN ID of the Fibre
(LUN) Channel node.
Manufacturer Displays the manufacturer and model of the device, if detected.

(Model)
Serial Number Serial number of the device.
Allow Access Displays if access is allowed to the device. If access is not

allowed, then NDMP will not attempt to use the corresponding
device.
Note: An NDMP device must be assigned to an EVS

before access can be allowed to the device.
If access is not allowed to a device, fill the checkbox next to the

device, and click allow access.
To deny access to a device, fill the checkbox next to the device,
and click deny access. A request to deny access will be rejected
if an NDMP client has opened the device. The backup
application configuration should be changed to avoid use of the
device before denying access.

Modifying NDMP device access configuration
Status Current status of the selected device.
2. To enable/disable access to devices:

■ Click deny access to disable access to a device, which prevents NDMP from
attempting to use the device
Note: While an NDMP server has the device open, a deny access
request will be rejected. Therefore, the storage management
device before the current configuration process.
■ Click allow access to enable access to a device, which allows NDMP to use the
device.
Note: Before using an NDMP device, you must first allow access to it,
then it must be assigned to an EVS. NDMP Devices are assigned to an
EVS using the NDMP Device Access Details page described in
■ Click forget to remove the selected device from the list (only available for devices
that have been disconnected from the FC).
■ Click Refresh Status to discover any changes in the Fibre Channel connection;
that is, to find any newly attached devices and discover whether any previously
discovered devices that are no longer accessible. If new devices are plugged into
the Fibre Channel, use Refresh to identify them.

NDMP backup devices, such as tape libraries and auto-changers, require special
configuration. The server monitors its Fibre Channel (FC) links periodically and
automatically detects the presence of backup devices. Because the server may be
connected into a Storage Area Network (SAN) shared with other servers, it does not
automatically make use of backup devices it detects on its FC links.
Procedure
1. Navigate to Home > Data Protection > NDMP Device List to display the NDMP
Device List page.

2. The following table describes the fields in this page.
ID Displays the server-assigned device identifier.
Allow Indicates if device access is allowed (Allow) or denied (Deny).
Note: An NDMP device must be assigned to an EVS

before access can be allowed to the device.
If access is not allowed to a device, click allow access
to enable access.
To deny access to a device, click deny access. A
request to deny access will be rejected if an NDMP
client has opened the device. The backup application
configuration should be changed to avoid use of the
device before denying access.
EVS Indicates the specific EVS to which the device is assigned, or

indicates that the device is assigned to all EVSs.
To change the device assignment, select the EVS to which you
want to assign the device, or select All EVS to assign the device
to all EVSs hosted by the server/cluster, and click reassign.

Tape devices can be shared among EVSs under the following
conditions:
■ The EVSs must be within the same cluster.
■ The tape device is not shared with another Hitachi server.
■ The tape device is not shared with another storage device.
Notes:
■ If the device is to be shared between this server
and another non-clustered server, additional
sharing logic is required. Some backup
applications automatically allow such sharing
without any extra configuration. For other backup
applications it is necessary to use the SCSI
Reserve/Release protocol, which can be enabled
using the ndmp-option reserve_devices CLI
command.
■ When one EVS is currently using a tape device,
any attempt to use it through a different EVS will
prompt a notification that the device is currently
in use (that is, the operation will not be queued).
■ When a tape device is currently assigned to a
specific EVS (but not to All EVS), any attempt to
access it through a different EVS will prompt
notification that the device has not been found.
Hardware This section displays hardware-related details about the device,

Details including:
■ Device Type, which can be either tape drive or autochanger.
■ Manufacturer (Model), which are the device manufacturer
and model detected when the device is discovered.
■ Version, which indicates the version of the firmware currently
on the device, if it was detected when the device was
discovered.

Device This section displays identification information about the device,

Identification including:
■ NDMP Device Name, which displays the name by which the
device can be addressed by the server.
To configure your storage management application to work
with an NDMP device, in the storage management
application you must specify the device name of each
autochanger/tape drive you want the application to use.
■ Location, which displays the name of the autochanger that
holds the drive and the position of the drive in the
autochanger. For example, the location of the first drive in
autochanger /dev/mc_d0l0 is /dev/mc_d0l0 : 1.
■ Serial Number, which indicates the device’s serial number, if
it was detected when the device was discovered.
■ Fibre Channel Address, which indicates the device’s Fibre
Channel node name.
■ LUN, which indicates the LUN identifier for the device.
When the NAS Manager cannot determine the location of a
tape drive, it displays *unknown*. When this occurs, check for
the following conditions and follow the troubleshooting
instructions:
■ The tape library is offline.
■ The autochanger does not support the server’s mechanism
for querying the tape drive location, or the autochanger has
not been set up to accept this query. Where this is the case,
compare the serial numbers of the tape drives with displays
available in the tape library to verify the drive locations.
■ The autochanger and a tape drive within it are attached to
different servers. In this case, use the tape drive serial
numbers to match the device name shown by one server
with the location shown on the other.
Note: Devices will not be available or visible if

access to them has not been enabled.

About NDMP with snapshots
3. The following Actions are available:

■ Click deny access to disable access to a device, which prevents NDMP from
attempting to use the device
Note: While an NDMP server has the device open, a deny access
request will be rejected. Therefore, the storage management
device before the current configuration process.
■ Click allow access to enable access to a device, which allows NDMP to use the
device.
Note: Before using an NDMP device, you must first allow access to it,
then it must be assigned to an EVS. NDMP Devices are assigned to an
EVS using the NDMP Device Access Details page described in
■ Click forget to remove the selected device from the list (only available for devices
that have been disconnected from the FC).
■ Click Refresh Status to discover any changes in the Fibre Channel connection;
that is, to find any newly attached devices and discover whether any previously
discovered devices that are no longer accessible. If new devices are plugged into
the Fibre Channel, use Refresh to identify them.
About NDMP with snapshots

The server uses snapshots to backup data consistently and without being affected by on-
going file activity.

Configuring NDMP snapshot options
The following options should be considered when planning a backup strategy:

■ Back up automatically created snapshots.
When backing up a file system that is being actively updated, a snapshot of the file
system is much more likely to produce a fully consistent image than backing up the
live file system. As a result, NDMP is configured by default to automatically create a
snapshot for backup.
■ Back up pre-created snapshots
A backup can be taken from a specific snapshot that has been created by a rule or
created spontaneously by user request:
■ To back up the latest snapshot created under a snapshot rule, use the
environmental variable NDMP_BLUEARC_USE_SNAPSHOT_RULE.
■ To back up the latest snapshot created spontaneously by user request, request a
specific snapshot by explicitly including the snapshot name in the path to back up.
Where the path is based on a CIFS share name, indicate the snapshot using /
~snapshot/snapshot_name; for paths based on an NFS export name, indicate
the snapshot using/.snapshot/snapshot_name. CIFS shares and NFS exports
may also include a snapshot name.
■ Backing up databases and iSCSI Logical Units
The internal structures of Databases and iSCSI LUs are tightly coupled with the state
of the client software (database manager/iSCSI Initiator) that is controlling the files.
For example, backing up such files during a client operation may produce
inconsistencies in the backup that would prevent recovery.
Therefore, any backup of databases and iSCSI LUs must ensure that files are in a
consistent state at the time of back up. Snapshots can be used to achieve this.
Snapshot rules provide the most convenient mechanism, as this avoids having to
explicitly specify the name of the snapshot used.
Note: When configuring snapshot rules, ensure that snapshots have a

sufficiently long shelf life, and before initiating a backup, verify that the
snapshot is not scheduled to be replaced during the anticipated time of
the backup, as such replacement would cause the backup to fail.
For more information on backing up and restoring iSCSI LUs, refer to the File Services
Administration Guide.

To configure NDMP snapshot options:
Procedure
1. Navigate to Home > Data Protection > NDMP History and Snapshots.


clear All When necessary, you can clear the records of completed
tape-based backups and either scripted or command
line-based incremental accelerated data copies (ADCs).
Clearing the history does not affect replication
operations (replication history is managed separately) or
data migration operations (migration is not an
incremental operation). When performing incremental
backups, the server uses the records of old backups to
determine the date and time after which it must back up
modified files. If you have lost a backup for any reason,
you can clear the records, which forces the next backup
to be a full backup instead of an incremental backup.
Note: To force a full backup for replication,

delete the snapshot that was automatically
created at the start of the last replication
Automated Snapshot Do not automatically create snapshots, but backup

Use from the live file system - This option causes a backup
to be performed from the live file system (no snapshot is
taken).
Automatically create snapshots (recommended) - This
option causes a snapshot to be taken, then the backup is
performed from that snapshot. Note that this option
does not affect replication snapshot usage.
Note: If a backup path explicitly contains a

snapshot reference, the system does not take
a new snapshot, regardless of this setting.
Automated Snapshot By default, NDMP keeps the snapshot to make

Deletion incremental backups more accurate. In the Automated

Snapshot Deletion section, select whether to delete the
snapshot:
■ Delete snapshot after use deletes an automatic
snapshot after completion of the backup for which it
was taken. To prevent accumulation of unneeded
snapshots, select this option for full backups or if the
file system is changing very rapidly.
■ Delete snapshot after next backup deletes an
automatic snapshot after it has been used as the
basis of a new incremental backup. With an exception
for full backups, this option supports “incremental”
backup schedules based on the immediately
preceding backup.
■ Delete snapshot when obsolete deletes an
automatic snapshot upon next backup at the same
level. For example, a snapshot taken for a full backup
will only be deleted when the next full backup is
completed. This option supports “differential” backup
schedules based on a common base backup.
Note: Snapshots initiated by the Microsoft

Volume Shadow Copy Service (VSS) may
not be deleted by rule. These snapshots
should be managed through the
application that requested the snapshot.
You can, however, delete these snapshots
through the Snapshots page.
Automated Snapshot Determines number of days (1 to 80) to keep snapshots

Retention before auto-deletion.
Usually, the system deletes automatically created
snapshots according to the rule selected in the previous
step; however, after a sequence of backups using
automatically created snapshots is stopped, snapshots
may be left over. The maximum retention time provides
a way of tidying up in these circumstances.
Note: This setting applies to snapshots

automatically taken by replications. Set the
retention time to be long enough to make
sure that a snapshot from a replication copy
is not deleted until after the next successful
copy is complete. This means that the
maximum time set here must be longer than
the time taken to run two replication copies,
including the interval between the replication

Configuring backup and restore of migrated data
copies and the time required to make the
copies.
2. Click Apply to save your changes.
Configuring backup and restore of migrated data

There are several ways to configure backups of data that has been migrated by Hitachi
NAS data migration features. For more information on the Data Migrator to Cloud cloud
providers and features, see the Data Migrator Administration Guide. The configuration
varies depending on the data migration mechanism used and the desired backup
behavior.
Locally migrated data

Backup and restore of data sets that contain data migrated to other local Hitachi NAS file
systems are affected by the following NDMP environment variables:
■ NDMP_BLUEARC_EXCLUDE_MIGRATED
■ NDMP_BLUEARC_INCLUDE_ONLY_MIGRATED
■ NDMP_BLUEARC_REMIGRATE
Environment variable D* S* Backup Restore
NDMP_BLUEARC_EXCLUDE_MIGRATE n y Migrated files are Migrated files cannot be

D not included in the restored.
backup data.
n Migrated files are Depends on

included in the NDMP_BLUEARC_REMIGR
backup data ATE.
NDMP_BLUEARC_INCLUDE_ONLY_MIG n y Only migrated files Depends on

RATED are included in the NDMP_BLUEARC_REMIGR
backup data. ATE.
n Normal files and Depends on

migrated files are NDMP_BLUEARC_REMIGR
included in the ATE.
backup data.

Locally migrated data
Environment variable D* S* Backup Restore
NDMP_BLUEARC_REMIGRATE y y Migrated files are The recovery target file

marked as such in system is checked for a
the backup data. configured migration path.
If one exists, the file is
immediately migrated.
The file data is never
written to the primary file
system. If no migration
path is configured, a
normal file is created.
n Migrated files Migrated files are

appear as normal converted to normal files.
files in the backup
data.
Note: In the table, D* - Default and S* = Setting
Note that in most cases, NDMP Data Management Applications automatically use the
environment variables that were specified on backup when restoring. It is recommended
that you consider the desired restore behavior when specifying the backup variables.
Other than in exceptional circumstances, use the same environment variables on restore
as those specified at backup.
The variables to use for standard use cases are:
■ Only backup non-migrated data
● NDMP_BLUEARC_EXCLUDE_MIGRATED = y
● Other variables are ignored
■ Only backup migrated data, automatically migrating on recovery
● NDMP_BLUEARC_INCLUDE_ONLY_MIGRATED = y
● NDMP_BLUEARC_EXCLUDE_MIGRATED = n
● NDMP_BLUEARC_REMIGRATE = y
■ Backup all data, migrated files automatically migrated on recovery
● NDMP_BLUEARC_INCLUDE_ONLY_MIGRATED = n
● NDMP_BLUEARC_EXCLUDE_MIGRATED = n

Externally migrated data

Backup/restore of data sets that contain data migrated to external servers are affected
by the following NDMP environment variables:
■ NDMP_BLUEARC_REMIGRATE
■ NDMP_BLUEARC_INCLUDE_ONLY_MIGRATED
■ NDMP_BLUEARC_EXTERNAL_LINKS
■ The CLI command: migration-recreate-links-mode
Note that NDMP_BLUEARC_EXCLUDE_MIGRATED has no effect on externally migrated
files.
Defaul Effect on
Environment variable t Setting backup Effect on restore
NDMP_BLUEARC_INCLUDE_ n y Only Depends on

ONLY_MIGRATED externally NDMP_BLUEARC_EXTERNAL_LI
migrated NKS/migration-recreate-
files are links-mode.
included in
the backup
data.
n Normal Depends on
files and NDMP_BLUEARC_EXTERNAL_LI
externally NKS/migration-recreate-
migrated links-mode.
files are
included in
the backup
data.
NDMP_BLUEARC_REMIGRAT y y Externally Depends on

E migrated NDMP_BLUEARC_EXTERNAL_LI
files are NKS/migration-recreate-
marked as links-mode..
such in the
backup
data.
n Externally Externally migrated files are

migrated converted to normal files.
files appear
as normal
files in the
backup
data.

Defaul Effect on
Environment variable t Setting backup Effect on restore
NDMP_BLUEARC_EXTERNAL remigr ignore Externally Externally migrated files

_LINKS ate migrated cannot be restored.
files are not
included in
the backup
data.
recreate_lin Only the The recovery target file system

ks metadata is checked for a migration
for the path. If a path exists, an
externally external link is created (see the
migrated CLI migration-recreate-
file is links-mode command). There
included in is no restore of user data. If a
the backup migration path does not exist,
data. a link is not created.
remigrate The The recovery target file system

metadata is checked for a migration
and user path. If a path exists, an
data of the external link is created (see the
externally CLI migration-recreate-
migrated links-mode command), and
file are the user data is written to the
included in external link. The user data is
the backup never written to the local file
data. system. If a migration path
does not exist, a normal file is
created.
migration-recreate-links- test- always- No effect Creates a link. Does not check

mode before recreate- if the link is pointing at
- links anything.
recrea
te
test-before- No effect If an existing file (migrated or

recreate otherwise) exists, delete it, and
then create a new link to the
migration target and write the
user data to it.
■ Note that in most cases, NDMP Data Management Applications automatically uses
the environment variables that were specified on backup when restoring. It is
recommended that you consider the desired restore behavior when specifying the
backup variables. Other than in exceptional circumstances, use the same
environment variables on restore as those specified at backup.

■ migration-recreate-links-mode is set per EVS and not per NDMP operation. It

applies to restore only; therefore, it must be set on the EVS that hosts the recovery
target file system.
■ Do not use NDMP_BLUERC_EXTERNAL_LINKS = recreate_link with migration-
recreate-links-mode = test-before-recreate. This configuration could lead
to data loss.
■ When using NDMP_BLUEARC_EXTERNAL_LINKS = remigrate, the operation is
unsuccessful if the migration path at restore is the same path as when the backup
was made. This prevents accidental data loss when copying data between filesystems.
It is therefore not possible to recover migrated data to the same filesystem that is the
source of the backup using this method. An alternative is to restore to a different
location (if no migration path is configured there, migrated files are converted to
normal files) and then copy the data into the original location.
The settings to use for standard use cases are:
■ Only backup non-migrated data:
● NDMP_BLUERC_EXTERNAL_LINKS = ignore
● Other variables are ignored
■ Only backup migrated data, automatically migrating on recovery:
● NDMP_BLUEARC_INCLUDE_ONLY_MIGRATED = y
● NDMP_BLUERC_EXTERNAL_LINKS = remigrate
● migration-recreate-links-mode = test-before-recreate
■ Backup all data, automatically migrating data on recovery:
● NDMP_BLUERC_EXTERNAL_LINKS = remigrate
● migration-recreate-links-mode = test-before-recreate
■ Backup non-migrated data, preserve links to migrated data (requires recovery of data
at migration target by another mechanism):
● NDMP_BLUERC_EXTERNAL_LINKS = recreate_link
● migration-recreate-links-mode = always-recreate

NDMP environment variables
NDMP environment variables
You can use NDMP environment variables to modify backup actions. The storage
management application generates most of these variables and supports configuration
of additional variables. They are invoked from the Replication Rules: Add Rules page.
Direct
Possible value Notes
y or n Used on recovery to request Direct Access Recovery (DAR).

May be used to recover a subset of a full backup. If the storage
management application supports DAR, the recovery will position
the tape to the start of the required data rather than reading a
complete backup image to find the data. This saves time in
recovery of single files and similar operations.
The Storage Management Application may control the setting of
this variable, based on either the setting of a user interface
option, or on an assessment of the likely efficiency of using DAR;
however, in some cases, it may be necessary to explicitly set
DIRECT=y.
EXCLUDE
Comma-separated Specifies files or directories to exclude from a backup. By

list of files or default, none are excluded.
directories
When specifying a file or directory, type either:
■ A full path name, relative to the top-level directory specified
in the backup path. The path name must start with a
forward slash (/). An asterisk (*) can be typed at the end as a
wildcard character.
■ A terminal file or directory, which is simply the last element
in the path. The name must not contain any forward slash (/)
characters, but it may start or end with the wildcard
character *.
For example:
ENVIRONMENT EXCLUDE “/dir1/tmp*,core,*.o”

EXTRACT

This command excludes all files and directories that:
■ Start with the letters tmp in the directory /dir1
■ Are called core
■ End with the characters .o
The command is case-sensitive if backing up an NFS export but
not if backing up a CIFS share.
EXTRACT
y or n The default value y causes a recovery operation to extract files

from a file list rather than recovering the whole backup.
FILESYSTEM
Name of directory The Storage Management Application sets the FILESYSTEM

to back up variable to the name of the path to be backed up.
FUTURE_FILES
y or n Enables back up of files created after the start of the current

backup. With NDMP version 2, the inode number that identifies a
file can be reused during a backup, thereby causing the backup to
fail. By default, therefore, only files created before the start of the
backup are backed up. To override this behavior, set
FUTURE_FILES=y.

HIST
HIST
y or n The default value y causes file history information to be sent to the

storage management application. This enables the display and
recovery of the contents of a backup.
LEVEL
0 – 9, or i The default value is 0 (full backup). If the value is set to 4, an

incremental backup is taken based on the most recent previous
backup of the same FILESYSTEM with level 0, 1, 2, or 3. If the value
is set to i, an incremental backup is taken based on the most
recent previous backup of the same FILESYSTEM of any level.
NDMP_BLUEARC_AWAIT_IDLE
y (default) or n By default, the data management engine imposes an interlock to

prevent NDMP backups and accelerated data copies (ADCs) from a
replication destination while a replication copy is actively writing
data.
This is intended for installations that replicate to a particular
volume, then back up from that same volume. However, as the lock
is held at a volume level, it may be desirable in the case of
directory-level replication to override this action.
To make use of this replication interlock, specify y on both the
replication that is intended to do the waiting and the replication
that is waited upon.
NDMP_BLUEARC_EMBEDDED_HARDLINKS
Possible
value Notes
y or n Used to enable or disable inline hard linked file support. Set the value
to y to enable, or n to disable. For backups, inline hard linked file

NDMP_BLUEARC_EMBEDDED_HARDLINKS
Possible
value Notes
support is set to n (disabled) by default, but for multi-stream
operations, such as replications and accelerated data copies (ADCs)
between servers, the default is overridden and inline hard linked file
support is enabled. By default, replication and ADC operations use
multiple data streams, so for those operations, inline hard linked file
support is used by default.
When enabled, inline hard linked file support causes NDMP to back up
hard linked files with both file data and file metadata inline (in a single
data stream), which reduces the amount of memory the server needs
to manage the data.
Set to n to disable inline hard linked file support, which causes file
metadata and file data to be sent in two data streams. Disabling inline
hard link file support maintains backup compatibility with older
systems or releases.
Inline hard linked file support may not be enabled using the ndmp-
option command. Rather, the command used to invoke NDMP must
request inline hard linked file support.
Note: Existing programs that can read NDMP data streams

for releases prior to release 6.1 will not be able to read
backups or recover from backups created using inline hard
linked file support.
If a replication fails part way through, it will not be possible to restart

replication if the server is downgraded to a release prior to release
6.1.
Using this option with replications and ADCs

When multi-streamed replication or ADC operations are started, this option is enabled.
Starting in release 6.1, replication and ADC operations are multi-streamed by default,
meaning that this option will be enabled by default for those operations.

NDMP_BLUEARC_EXCLUDE_MIGRATED
Using backups
When backing up a file system:
■ When the embedded hard link option is enabled, the data for each hard linked file is
included in the data stream wherever a path to that file is included.
When enabled, the embedded hard link option increases the amount of data backed
up, because multiple copies of the hard linked file data are included. However, it
reduces the complexity of managing the backup.
Also, note that enabling the embedded hard link option reduces the memory
requirements needed to keep track of all the hard links.
■ When the embedded hard link option is disabled, paths to hard linked files are
included without any data in the main part of the backup and a single copy of the
hard link file data is included at the end of the backup.
This reduces the amount of data backed up, because only a single copy of the hard
linked file data is included.
Recommendations for usage with backups

■ If the backup contains many (more than a few hundred thousand) hard linked files,
you should enable this option, because it reduces the memory overhead. Note that,
where the backup includes many millions of hard linked files, enabling this option
may allow the backup to complete where it would not complete if the option is
disabled.
■ If the backup contains a relatively small number of hard linked files each containing a
large amount of data, you should disable the option.
■ If there is a chance that the backup may need to be restored on an older version of
software, you should disable this option.
NDMP_BLUEARC_EXCLUDE_MIGRATED
y or n Indicates whether backups or replications will include files whose

data has been migrated to secondary storage.
If set to y, the backup or copy will not include files whose data has
been migrated to another volume using the Data Migrator facility.
The default n specifies that migrated files and their data will be
backed up as normal files. The backup/copy retains the
information that these files had originally been migrated.

NDMP_BLUEARC_EXTERNAL_LINKS
NDMP_BLUEARC_EXTERNAL_LINKS
ignore, Controls what happens when a replication operation encounters

recreate_link, a cross volume link (a link to a file that has been migrated to an
or remigrate external server).
■ If set to ignore, the replication operation copies only the files
on the primary (migrated files are not copied). Use this setting
when files have been migrated because they are less useful,
so they are not replicated in order to save time.
■ If set to recreate_link, the replication operation copies
only the details of the cross volume link. The cross volume
link is recreated on the destination if the relevant external
migration data path is in place and the migrated file is
accessible. Use this setting when the replication is between
storage servers or clusters on the same site, and there is a
single external migration target server.
Note: Do not use the default test-before-

create setting of the migration-create-
links-mode CLI command if you use this option.
■ If set to remigrate, the replication operation copies the file
contents but marks the file as having been externally
migrated. The destination re-migrates to secondary storage if
there is an existing data migration path. Use this setting when
the replication is between a main site and a disaster recovery
site, where the disaster recovery site includes a similar data
migration configuration. This is the default.
NDMP_BLUEARC_INCLUDE_ONLY_MIGRATED
Possible
value Notes
y or n Indicates if backups or ADC copies will exclude files whose data has not
been migrated to secondary storage.
If set to y, the backup or copy includes only those files whose data has
been migrated to another volume using the Data Migrator facility.
The default n indicates that files whose data has not been migrated be
backed up like normal files.

NDMP_BLUEARC_TAKE_SNAPSHOT
NDMP_BLUEARC_TAKE_SNAPSHOT
Possible
value Notes
y or n This variable is used to override the default behavior with respect to

taking a file system-level snapshot during NDMP backup.
By default, HNAS server will take the file system-level snapshot during
NDMP backup.
This option also applies to the file-level NDMP replication, which is
configured through the File Replication Rules of the NAS Manager.
NDMP_BLUEARC_USE_CHANGE_LIST
Possible
value Notes
y or n Indicates whether incremental backups or replications will use a

changed object list to direct the search for changed files; otherwise, it
will have to search the entire directory tree looking for changed files.
When using the changed object list, the search only passes through
those directories that contain changed files.
Where a relatively small proportion of the file system includes
directories containing changed files, the use of changed object lists may
significantly reduce incremental backup and replication time;
however, processing of the changed object list itself may take
considerable time. Therefore, where file changes exist in many
directories, its use is not recommended.
The default setting for this option can be set using the CLI ndmp-
option change_list_incr command.
NDMP_BLUEARC_USE_SNAPSHOT_RULE
Possible
value Notes
Snapshot rule Causes NDMP to back up the latest snapshot created under a
name specified snapshot rule. This can be used to backup a snapshot taken
at a specific time; for example, for databases.
If set, NDMP does not create or delete snapshots.

NDMP_BLUEARC_USE_SNAPSHOT_RULE
Possible
value Notes
Note: Following a successful backup, the snapshot should

not be deleted until after the operation has completed. In
addition, the snapshot should be kept around long enough
to support incremental backups.

Hitachi
Corporate Headquarters Regional Contact Information
2845 Lafayette Street Americas: +1 866 374 5822 or info@hitachivantara.com
Santa Clara, CA 95050-2639 USA Europe, Middle East, and Africa: +44 (0) 1753 618000 or info@emea@hitachivantara.com
www.HitachiVantara.com | community.HitachiVantara.com Asia Pacific: + 852 3189 7900 or info.marketing.apac@hitachivantara.com

NAS Platform v13 4 Backup Administration Guide MK-92HNAS007-15 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

NAS Platform v13 4 Backup Administration Guide MK-92HNAS007-15 PDF

Uploaded by

Copyright:

Available Formats

Backup Administration Guide

Hitachi Virtual Storage Platform Gx00 and Fx00 with NAS

Backup Administration Guide for Hitachi NAS Platform ii

Chapter 1: About NDMP backup support........................................... 10

Command Line References

Backup Administration Guide for Hitachi NAS Platform v

Backup Administration Guide for Hitachi NAS Platform vi

Backup Administration Guide for Hitachi NAS Platform vii

Accessing product documentation

Backup Administration Guide for Hitachi NAS Platform viii

Hitachi Community is a global online community for Hitachi customers, partners,

Backup Administration Guide for Hitachi NAS Platform ix

Standard NDMP configuration

Figure 1 Standard NDMP configuration

Chapter 1: About NDMP backup support

Some common applications of NDMP include:

Storage management applications

Chapter 1: About NDMP backup support

Enabling and disabling NDMP

2. Enter the storage server’s NDMP configuration settings.

Chapter 1: About NDMP backup support

Password By default, the password is ʺndmpʺ. The password cannot

Version By default, the storage server uses NDMP version 4 for

Note: Both incremental data replication and ADC

Port The NDMP port number. By default, port 10000 is used.

apply Apply the changes made to the NDMP Settings.

NDMP Server Status

Current Status: The options are:

Enable NDMP The options are:

3. Start or stop the NDMP process.

Caution: Read this caution before following instructions to start and

4. Enable or disable the NDMP process at Boot.

Chapter 1: About NDMP backup support

About NDMP user name, password, and version

An administrator can specify two types of users:

Specifying an NDMP user name and password

Chapter 1: About NDMP backup support

2. Enter the required information NDMP settings:

Password By default, the password is ʺndmpʺ. The password cannot

Version By default, the storage server uses NDMP version 4 for

Note: Both incremental data replication and ADC

Port The NDMP port number. By default, port 10000 is used.

apply Apply the changes made to the NDMP Settings.

NDMP Server Status

Current Status: The options are:

Enable NDMP The options are:

3. Click Apply to save your changes.

Enabling and disabling NDMP devices

Chapter 1: About NDMP backup support

Manufacturer Displays the manufacturer and model of the device, if detected.

Serial Number Serial number of the device.

Allow Access Displays if access is allowed to the device. If access is not

Note: An NDMP device must be assigned to an EVS

If access is not allowed to a device, fill the checkbox next to the

Chapter 1: About NDMP backup support

Status Current status of the selected device.

2. To enable/disable access to devices:

Modifying NDMP device access configuration

Chapter 1: About NDMP backup support

2. The following table describes the fields in this page.

ID Displays the server-assigned device identifier.

Allow Indicates if device access is allowed (Allow) or denied (Deny).

Note: An NDMP device must be assigned to an EVS