HDI Initial Configuration v1-0

Installing and Configuring HCP Anywhere
and Hitachi Data Ingestor

HDI Single Node and HDI-VM Initial Configuration
© Hitachi Vantara Corporation 2018. All rights reserved.

Module Objectives
 Upon completion of this module, you should be able to:

• Use the integrated management GUI system configuration wizard to set up
initial parameters
• Use the integrated management GUI service configuration wizard to:
 Integrate with Hitachi Content Platform (HCP) and tenant using Management API
(MAPI)
 Create file system and namespace
 Integrate with active directory
 Create a common internet file system (CIFS) share and configure permissions
• Edit the migration task
• Configure the front-end network
HDI Single Node and HDI-VM
Integrated Management GUI

HDI Integrated Management GUI With Firefox
 To open the HDI integrated management console using Mozilla Firefox, you may need to change the
configuration of the web browser
 Introduce the URL: about:config
 Search the parameter: security.tls.insecure_failback_host and add the management IP of Hitachi
Data Ingestor (HDI)

HDI Single Node Integrated Management GUI
1. Open a browser and connect to the Integrated

Management GUI using one of the following:
https://IP_HDI/admin/
2. Log in using the following strings:
User ID = admin
Password = chang3me!

Change Admin Password

Provisioning Wizard
In the Provisioning Wizard select Manual Settings for:

• HDI Single
• HDI Virtual Machine
• HDI remote server (RS) local managed (allowed in v6.1.1)
Select Next, if you want to manage it centrally from HCP Anywhere:

• HDI remote server (RS)
• HDI Single Node
• HDI Virtual Machine

System and Service Configuration Wizards
 There are 2 initial configuration wizards in the HDI single node and HDI VM:
• System Configuration Wizard (for HDI parameters)
 HDI Name
 Management Network IP
 DNS Server
 Time / NTP
• Service Configuration Wizard (for HCP integration)

 HCP Tenant Integration
 File System and Namespace creation,
 Versioning, Migration Task configuration, CIFS, NFS configuration, First Share
 Active Directory Integration

System Configuration Wizard
There are 2 main wizards:

• System Configuration Wizard (HDI parameters)
• Service Configuration Wizard (HCP integration)
1. After selecting Manual Settings, the System

Configuration Wizard displays.
2. After setup is completed, HDI will be restarted.
3. It is possible to reopen HDI through: Action >

Configuration Wizards.

• DNS is very important in evaluating

the HCP and tenant names on
every access
• Be careful with the configuration of
Time settings, and specify a NTP
server
• If there is a time difference of more
than 5 minutes with the Domain
Controller, it means it cannot
connect to the active directory
0 © Hitachi Vantara Corporation 2018. All rights reserved.

The HDI system now restarts.

Service Configuration Wizard – Introduction
After restarting and logging into the system, the Service

Configuration Wizard displays.

Service Configuration Wizard – HCP Settings
HDI tests the connection with HCP.
Specify the HCP replica of the primary.

In case of an error of the primary HCP the HDI swaps to
the secondary

Service Configuration Wizard – Resource
Settings
• If you select Automatically, it creates a file

system as big as entire free space is
available on the HDI disk
• If you select Manually, you can specify the
size of the file system

Service Configuration Wizard – Create File
System
• Hard quota of the namespace that is created

in the tenant (using MAPI)
• Cache settings are file system settings

• Refers to the size of file system

System
Activates versioning in HCP for the

namespace. Users have .history in
the shares to recover files
• From version 6.1 theThe Migration Task settings

Schedule schedule
is Hourly controls the visibility under
the .history folder for the
• A Maximum duration end of 0 user
means Noalltime
(Not dates on
Limit for the Migrationwhich
Task aexecution
migration occurred
will be shown) and
indirectly sets a prune-time
for the versioning in the
namespace (the oldest
date under .history)

System
• Do not start the absolute path of shared directory with “/”.

It is automatically added
• To keep the Share directory field empty means to share
the root of the file system
• The exported name of the share is share01. This name
cannot be repeated in the HDI (even in other file systems)

System
• By default, the root_squash mechanism is active

• A root connection to the NFS export is changed to
anonymous
• Sometimes it is required to disable the root_squash
(Application access from UNIX to this export)
Anonymous Mapping: Not applicable
• If you share a directory (Not the root of the file system,

see the previous slide), the advanced ACL
configuration of the new directory created displays at
the bottom of the window
• After creation of the folder, you cannot change the
ACL using GUI, but you can change it using CLI
(Refer to the CLI module)

Service Configuration Wizard – CIFS User
Authentication Settings
• Mark Custom settings to have visible

User Mapping
• Put the FQDN name of a domain

controller, not the IP
• The relative identifier (RID) is part of the

user and group security identifier (SID) of
windows
• HDI generates an automatic user
mapping SID to user identifier (UID) or
group identifier (GID) using the RID

Service Configuration Wizard – CIFS User
Authentication Settings
• Add the NetBIOS domain name
Settings to add the

User Mapping for
each Domain

RID Mapping Table
 HDI is organizing the authentication with AD via the relative identifier (RID), which is an extension to
the SID
 The Relative ID (RID) is part of the user SID and group SID in windows:
C:\Users\jose> whoami /USER
USER INFORMATION Relative ID (RID)
----------------
User Name SID
=============== ==============================================
OLYMPUS\jose S-1-5-21-2024051209-889329542-929705000- 123658
 As HDI is an UNIX based system, the CIFS protocol windows security identifiers (SIDs) needs to be
translated into UNIX UIDs and GIDs
 HDI translates UID or GID as:

• Lowest number selected as domain range in the HDI + User RID = UID
• Lowest number selected as domain range in the HDI + Group RID = GID
RID Mapping Table
 If we establish a mapping table: OLYMPUS: 1.000.000 – 1.999.999
In windows the user OLYMPUS\jose has (SID S-1-5-21-2024051209-889329542-929705000- 123658)

In the HDI the UID of OLYMPUS\jose = 1.000.000 + 123.658 = 1.123.658
In windows the group OLYMPUS\hdigrp has (SID S-1-5-21-2024051209-8893245667-9245605000- 523759)

In the HDI the GID of OLYMPUS\jose = 1.000.000 + 523.759 = 1.523.759

Service Configuration Wizard – Completion

Custom Schedule

The .History Folder
 HDI .history folder of every share or export is made up of top level folders
• Each folder represents the DATE_TIME of an executed migration task (backup to the
HCP)
• This folder is equivalent to the mountpoint of a file system snapshot
 The individual .history folder is a dummy folder
 .history is made available through the network share

• File system can have multiple shares with different permissions
• Number of shares impacts the overall architecture
• Each .history top level folder needs to be mounted with each share

File Restoration From Previous Versions .History
 HDI creates a directory under .history (as name the date) for each migration task execution to the HCP
 User can access old versions of files in .history/<date+time>/<original path>/, and can restore the files
to their current working directory
HDI Read Only HCP

Dir1
.history
Dir1 (share) File3
Current Version: 2017 11 05
… 2017 11 05
2017 12 18
File2
Dir1 Current Version: 2017 11 05
Dir1
file3 File 1
File1’ Current Version:
file2 file1 Version Nº2:
4 KB 2017 12 18
File1’
4 KB
Version Nº1:
2017 11 05
6 ・・・
Using the Period to Hold
 Using the traditional period to hold, the number of directories

under .history is given by:
Number of migration tasks every day x Period to hold (in days)
 For example:
• Migration task period scheduled: Every 8 hours (3 times every day )
• Period to hold: 7 days
• After 7 days we have 21 subdirectories under .history
 With an elevated period to hold, can be memory consuming in HDI and

can slow down the opening of .history
Custom Schedule

Custom Schedule
 Reduce the number of date folders under .history

• Automated pruning
• Accelerates system restart and the access to .history by users
 Make .history behave more like snapshot scheduling

• Reduced complexity for users
• Fewer folders to search through

Custom Schedule
Select Custom schedule

HDI Custom Schedule – Example

HDI Custom Schedule – Example
Hourly
Rapid
15-Min

HDI Custom Schedule – VSS
Compatible with volume

shadow copy services
(VSS)

Integration With Active Directory After Initial
Configuration

HDI AD Integration After Configuration Wizard
 On completion of service configuration wizard:

 It is possible to change the configuration of HDI integration with active
directory
 Select Access Protocol Configuration

Modify Configuration
 CIFS > Modify Configuration

Change Authentication Mode

Active Directory Method
 Restart CIFS services after selection of Active Directory

authentication option

User Mapping Setup
 As HDI is a UNIX based system, the CIFS protocol windows security identifiers (SIDs)
need to be translated into UNIX UIDs and GIDs
 HDI is organizing the authentication with AD via the relative identifier (RID) which is an
extension to the SID

Restart CIFS Services
 Restart CIFS services

HDI Under Computers
 HDI will appear in Computers

Access Control

Share Settings – Access Control

Share Settings – Access Permissions
Set the default
permissions of every
new file and new
directories created
under this share
(or subdirectories)
Owner Group Everyone

Directory Creation – ACL Permissions

Directory Creation – ACL Permissions
These permissions
affect only the root
of this share;
they determine
whether you can
map this share.

No Root Squashing for Network File System
Disable the root squashing

protection mechanism.
In some applications (running as root
in UNIX systems), verify the root
ownership of files after creation

HDI Single Node Integrated Management
GUI Exploration After Initial Configuration

Resulting Configuration

CIFS Shares

Edit Shares or Add New Shares

Active File Migration

Overview of Active File Migration
 If a user modifies the file during migration process then migration task
finishes with exceptions
 Active File Migration (AFM) feature appears in HDI v6.1 and enables:
• Protecting active files, which ended in transferring error and were
unprotected, in the current HCP-HDI replication system
• Successful migration during working hours, it means user’s active files are
protected

Active File Migration Workspace
 Workspace: Additional disk is used for storing differential data during

task migration
• Workspace usage table:
File System Size Workspace

< 4GB 0GB
4GB < Size < 20GB Size /2 ( round down )
20GB < Size < 17TB 10GB
17TB < Size < 256TB 25GB
256TB < Size 50GB
• Most common size for the workspace: 10GB

• In the HDI cluster or HFSM, it can be another LU
Architecture of Active File Migration
 HDI creates a stabilized image (snapshot) of the active file system and migrates files from the
stabilized image. If a file has been updated after starting the migration task, the original data
(differential data) is stored in the workspace
• The image is invisible and inaccessible for users
1. Create a stabilized file system.
Client
Volumes Namespace
I/O UFM
Stabilized
File system
image
Work Object versions
space
3. For updated files, the original data 2. Transfer files from the
is stored In the workspace stabilized image.

Active File Migration Control
 In HDI single, the definition of the

workspace and the use of AFM is
automatic
 AFM uses snapshot technology which

can impact the migration performance
(and the I/O performance from users in
the migration period)
 With the CLI command arcactmigctl,

you can enable or disable AFM function
on a file system, and also you can adjust
the workspace size
• You can select another LU for the
workspace in HDI cluster with HFSM

Resulting Configuration
Active Migration is enabled,

10GB - proposed size for the file system
30GB - reserved for the snapshot taken in every
migration to HCP
20GB - effective size of the file system

Active Migration Reserves 10GB

HDI Single Node – Edit Migration Task

Edit Migrations Tasks
You can have more than one migration task

over the same file system with different
policies:
• Migrate only this path
• Migrate files with extensions and so on
• Time of modification and so on

Edit Migrations Tasks
From v6.1 you can execute Migrate Immediately,

and Disable Task without editing the task.

HCP Namespace System-Backup Creation
 A configuration backup namespace with name - system-backup is also automatically

created in the specified tenant. It contains a backup for the configuration of HDI

Change the Stubbing Threshold

Set Stub Threshold
 By default the stub threshold is 10%, which means that HDI will delete (stub) files from
cache when less than 10% free space remains in the file system
 To change this threshold, connect the HDI using BMC, KVM console or SSH using
“service” as user
 To display current threshold:
• sudo arcreplimitget --file-system <File System Name>
 Set the new stub threshold when the used space is above 60% means, when the free
space is below 40%:
• sudo arcreplimitset --rest-size 40% --file-system <File System Name>

Module Summary
 In this module, you should have learned to:

• Use the integrated management GUI system configuration wizard to set up
initial parameters
• Use the integrated management GUI service configuration wizard to:
 Integrate with Hitachi Content Platform (HCP) and tenant using Management API
(MAPI)
 Create file system and namespace
 Integrate with active directory
 Create a common internet file system (CIFS) share and configure permissions
• Edit the migration task
• Configure the front-end network
Questions and Discussion

Module Review
1. Describe the active file migration.
2. The cache size should be higher than the namespace size. (True or
False)

HDI Initial Configuration v1-0

Uploaded by

Document Information

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

HDI Initial Configuration v1-0

Uploaded by

Copyright:

Available Formats

Installing and Configuring HCP Anywhere

and Hitachi Data Ingestor

© Hitachi Vantara Corporation 2018. All rights reserved.

 Upon completion of this module, you should be able to:

© Hitachi Vantara Corporation 2018. All rights reserved.

© Hitachi Vantara Corporation 2018. All rights reserved.

1. Open a browser and connect to the Integrated

© Hitachi Vantara Corporation 2018. All rights reserved.

© Hitachi Vantara Corporation 2018. All rights reserved.

In the Provisioning Wizard select Manual Settings for:

Select Next, if you want to manage it centrally from HCP Anywhere:

© Hitachi Vantara Corporation 2018. All rights reserved.

• Service Configuration Wizard (for HCP integration)

© Hitachi Vantara Corporation 2018. All rights reserved.

There are 2 main wizards:

1. After selecting Manual Settings, the System

2. After setup is completed, HDI will be restarted.

3. It is possible to reopen HDI through: Action >

© Hitachi Vantara Corporation 2018. All rights reserved.

• DNS is very important in evaluating

0 © Hitachi Vantara Corporation 2018. All rights reserved.

The HDI system now restarts.

1 © Hitachi Vantara Corporation 2018. All rights reserved.

After restarting and logging into the system, the Service

2 © Hitachi Vantara Corporation 2018. All rights reserved.

HDI tests the connection with HCP.

Specify the HCP replica of the primary.

3 © Hitachi Vantara Corporation 2018. All rights reserved.

• If you select Automatically, it creates a file

4 © Hitachi Vantara Corporation 2018. All rights reserved.

• Hard quota of the namespace that is created

• Cache settings are file system settings

5 © Hitachi Vantara Corporation 2018. All rights reserved.

Activates versioning in HCP for the

• From version 6.1 theThe Migration Task settings

6 © Hitachi Vantara Corporation 2018. All rights reserved.

• Do not start the absolute path of shared directory with “/”.

7 © Hitachi Vantara Corporation 2018. All rights reserved.

• By default, the root_squash mechanism is active

• If you share a directory (Not the root of the file system,

8 © Hitachi Vantara Corporation 2018. All rights reserved.

• Mark Custom settings to have visible

• Put the FQDN name of a domain

• The relative identifier (RID) is part of the

9 © Hitachi Vantara Corporation 2018. All rights reserved.

• Add the NetBIOS domain name

Settings to add the

0 © Hitachi Vantara Corporation 2018. All rights reserved.

 HDI translates UID or GID as:

 If we establish a mapping table: OLYMPUS: 1.000.000 – 1.999.999

In windows the user OLYMPUS\jose has (SID S-1-5-21-2024051209-889329542-929705000- 123658)

In windows the group OLYMPUS\hdigrp has (SID S-1-5-21-2024051209-8893245667-9245605000- 523759)

2 © Hitachi Vantara Corporation 2018. All rights reserved.

3 © Hitachi Vantara Corporation 2018. All rights reserved.

4 © Hitachi Vantara Corporation 2018. All rights reserved.

 The individual .history folder is a dummy folder

 .history is made available through the network share

5 © Hitachi Vantara Corporation 2018. All rights reserved.

HDI Read Only HCP

 Using the traditional period to hold, the number of directories

Number of migration tasks every day x Period to hold (in days)

 With an elevated period to hold, can be memory consuming in HDI and

8 © Hitachi Vantara Corporation 2018. All rights reserved.

 Reduce the number of date folders under .history