HITACHI v7.6 Content Platform Anywhere Enterprise Installation Guide

HITACHI v7.6 Content Platform Anywhere Enterprise

Specifications

• Product: Hitachi Content Platform Anywhere Enterprise v7.6
• Installation Guide: Edge Filer Installation Guide for AWS
• Description: This guide explains how to install and configure HCP Anywhere Enterprise Edge Filer on an AWS platform.
• Document Code: MK-HCPAE016-00
• Date: December 2023

Product Usage Instructions

• Chapter 1. The HCP Anywhere Enterprise Edge Filer

• Technical Specifications

  • For detailed technical specifications, refer to the documentation provided.

• Port Requirements

  • Ensure that the necessary ports are open for communication. Refer to the specific port requirements outlined in the documentation.

• Browser Requirements

  • Supported browsers may vary. Check the compatibility list provided in the documentation for optimal performance.

• License Types

  • Understand the different license types available and choose the one that best suits your needs. Contact Hitachi Vantara LLC for further information.

• Chapter 2. HCP Anywhere Enterprise Edge Filer Planning

  • Before installation, carefully plan out the deployment of the Edge Filer to ensure a smooth setup process.

• Chapter 3. Installing the HCP Anywhere Enterprise Edge Filer in an AWS Environment
  Follow the step-by-step instructions provided in this chapter to successfully install the Edge Filer on an AWS platform.

• Chapter 4. Initial HCP Anywhere Enterprise Edge Filer Configuration

  • Configure the HCP Anywhere Enterprise Portal as a precondition before setting up the Edge Filer. Then proceed with the initial setup of the Edge Filer as detailed in this chapter.
  • Additionally, load a Trusted CA Certificate to ensure secure communication with the Edge Filer.

Frequently Asked Questions (FAQ)

1. Q: Are there any specific network requirements for installing the Edge Filer?
   A: Yes, ensure that the necessary ports are open for communication between the Edge Filer and other components. Refer to the documentation for detailed port requirements.

2. Q: How can I obtain additional licenses for HCP Anywhere Enterprise?
   A: Contact Hitachi Vantara LLC for information on acquiring additional licenses and to understand the different license types available.

Hitachi Content Platform Anywhere Enterprise

Edge Filer Installation Guide for AWS
This book describes how to install and configure HCP Anywhere Enterprise Edge Filer on an AWS platform.

MK-HCPAE016-00 December 2023

© 2023 Hitachi Vantara LLC. 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 Vantara LLC (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 Vantara LLC 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 Vantara LLC.
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 and Lumada are trademarks or registered trademarks of Hitachi, Ltd., in the United States and other countries.
• AIX, AS/400e, DB2, Domino, DS6000, DS8000, Enterprise Storage Server, eServer, FICON, FlashCopy, GDPS, HyperSwap, IBM, Lotus, MVS, OS/390, PowerHA, PowerPC, RS/6000, S/390, System z9, System z10, Tivoli,
• z/OS, z9, z10, z13, z14, 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, Microsoft Edge, the Microsoft corporate logo, the Microsoft Edge 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.
• Copyright and license information for third-party and open source software used in Hitachi Vantara products can be found in the product documentation, at
• https://www.hitachivantara.com/en-us/company/legal.html or https://knowledge.hitachivantara.com/Documents/Open_Source_Software.

Preface

About this document
Hitachi Content Platform Anywhere Enterprise Edge Filers (HCP Anywhere Enterprise Edge Filers) seamlessly combine collaboration capabilities, local storage, cloud storage, and data protection functionality in a single, cost- effective package. This document describes how to install and perform the initial setup of HCP Anywhere Enterprise Edge Filer on an AWS platform.

Document conventions
This document uses the following typographic convention:

• Indicates text in a window, including window titles, menus, menu options, buttons, fields, and labels. Example: Click OK.
• Indicates emphasized words in list items.

Italic| Indicates a document title or emphasized words in text.
Monospace| Indicates text that is displayed on screen or entered by the user. Example: pairdisplay -g oradb

Intended audience
This document is intended for HCP Anywhere Enterprise users from a Windows or macOS PC.

Accessing product downloads

• Product software, drivers, and firmware downloads are available on Hitachi Vantara Support Connect: https://support.hitachivantara.com/.
• Log in and select Product Downloads to access the most current downloads, including updates that may have been made after the release of the product.

Getting Help

• Hitachi Vantara Support Connect is the destination for technical support of products and solutions sold by Hitachi Vantara. To contact technical support, log on to Hitachi Vantara Support Connect for contact information: https://support.hitachivantara.com/en_us/contact-us.html.
• Hitachi Vantara Community is a global online community for 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.

Chapter 1. The HCP Anywhere Enterprise Edge Filer

HCP Anywhere Enterprise Edge Filers seamlessly combine collaboration capabilities, local storage, cloud storage, and data protection functionality in a single, cost-effective package. HCP Anywhere Enterprise Edge Filers are available as virtual appliances: V Series HCP Anywhere Enterprise Edge Filers are software-based gateways running on a hypervisor, such as ESXi or KVM, or in a cloud, such as AWS. HCP Anywhere Enterprise Edge Filers replace file servers and other traditional file storage solutions with a single, cloud- integrated and cost-effective solution.
HCP Anywhere Enterprise Edge Filers:

• Incorporate Intelligent caching technology.
  Dynamically cache files from a secure HCP Anywhere Enterprise Portal to the HCP Anywhere Enterprise Edge Filer.

• Deliver unlimited file access to office users, with visibility to all organizational files centralized in the cloud, either private or public.

• Share files across your network and provide users with collaboration across offices and endpoints with no local storage restraints.

• Synchronize folders across your network and the cloud, including keeping the main storage on the cloud with stubs saved on the edge filer. A stub is a file with a tiny footprint that contains the metadata about the file, such as the file name, size, and modification date. Only the folder and file metadata and not the actual file content is saved locally.

• The HCP Anywhere Enterprise Edge Filer is managed using a web-based interface or centrally through the HCP Anywhere Enterprise Portal. The HCP Anywhere Enterprise Portal also allows users to sync content between the

• HCP Anywhere Enterprise Portal and the HCP Anywhere Enterprise Edge Filer, as well as between HCP Anywhere Enterprise Edge Filers located in different branch offices.

• The HCP Anywhere Enterprise Edge Filer connects to a HCP Anywhere Enterprise Portal to provide users with LAN speed access to all their home folders and shared folders on the HCP Anywhere Enterprise Portal. Local user accounts are mapped to the equivalent user accounts in the cloud, so that each user sees only his or her personal view of the cloud files. Users can access locally stored, synced copies of the folders they are allowed to access on the HCP Anywhere Enterprise Portal.

• The main storage is on the HCP Anywhere Enterprise Portal in the cloud with stubs saved on the HCP Anywhere Enterprise Edge Filer. A stub is a file with a tiny footprint that contains the metadata about the file, such as the file name, size, and modification date. Only the folder and file metadata and not the actual file content is saved locally. This results in the cost of storage being significantly lower. Also, systems with many file changes, where only some of the files are required locally, don’t over use bandwidth between the cloud and HCP Anywhere Enterprise Edge Filer. Only the required files are passed across the wire.

• When a user accesses a file stub, the file is downloaded and opened without delay, and where possible, large files are streamed from the cloud so they can be accessed faster. After the download has completed, the file is unstabbed. Any changes to the file are synced back to the HCP Anywhere Enterprise Portal. Folders that are always required can be pinned, in which case the files in the folders, and not the stubs, are stored on the HCP Anywhere Enterprise Edge Filer.

Technical Specifications

Port Requirements
Firewall ports opened for managing the HCP Anywhere Enterprise Edge Filer user interface:

Firewall ports opened to the HCP Anywhere Enterprise Portal:

Anywhere Enterprise Portal IP addresses.
995| TCP| outbound| CTTP. Communications with HCP Anywhere Enterprise Portals.
8443| TCP| outbound| —

Firewall ports opened to the HCP Anywhere Enterprise Portal backend storage when Direct Mode is set for the storage node in the HCP Anywhere Enterprise Portal:

Firewall ports opened for Active Directory:

Firewall ports opened for antivirus updates:

Firewall ports opened for SMTP:

Edge Filer user interface (in the CONFIGURATION view, select Alerts > Mail Server in the navigation pane).

Firewall ports opened for NTP updates:

Warning: HCP Anywhere Enterprise Edge Filers operate behind a firewall, and it is important to leave all other ports closed.

Browser Requirements
The latest two releases of Google Chrome, Apple Safari, Mozilla Firefox, and Microsoft Edge.

License Types

| License
---|---
EV16| EV32| EV64| EV128| EV256
Maximum RAM| 8GB| 16GB| 32GB| 64GB| 128GB
Maximum Storage| 16TB| 32TB| 64TB| 128TB| 256TB
Recommended vCPUs| 4| 8| 16| 32| 64
Maximum recommended users| 500| 1000| 3000| 5000| 5000

Note: The normal HCP Anywhere Enterprise Edge Filer usage is memory and network intensive and not CPU intensive. The number of vCPUs allocated for the HCP Anywhere Enterprise Edge Filer should take this in to account.

Software Features

NFS, FTP, WebDAV
Monitoring| SNMP

Cloud Service Features

deduplication, simultaneous synchronization.
Versioning| Retention of previous file versions.
Additional Services| Centralized management, centralized monitoring, Cloud Drive caching and synchronization, reporting, logging, remote access.

Chapter 2. HCP Anywhere Enterprise Edge Filer Planning

During the planning stage for the HCP Anywhere Enterprise Edge Filer, contact support regardless of whether the installation is a new installation or an upgrade from an existing installation.
End users who are familiar with a given folder structure and shares, as well as a given permission scheme, continue to see the same folder structure, shares, and permission scheme after migration to the HCP Anywhere Enterprise Edge Filer. This enables the migration from a current file system to a HCP Anywhere Enterprise Edge Filer, without the need to apply any structural changes such as flattening the folder structure or simplifying the permissions scheme.
File and folder access continue to be available following the migration in the same way they were in the original file system. Access, after the migration, is through SMB, provided by the HCP Anywhere Enterprise Edge Filer. Users continue to access the files and folders through standard client computers; for example, using Windows File Explorer or macOS Finder.
The following file server features are fully supported by HCP Anywhere Enterprise Edge Filer and are copied to HCP Anywhere Enterprise Edge Filer as part of the migration:

• ACL files/folder share permissions.
• Nested sharing.
• ACL emulation to allow files and folders management via standard SMB protocol.
• Shares can be mounted to users via standard administrator tools:
  • DFS Management
  • Group Policy (GPO)
  • Other tools based on Net use

You use HCP Anywhere Enterprise Migrate, that is accessed from the HCP Anywhere Enterprise Edge Filer user interface, to create the corresponding shares in the HCP Anywhere Enterprise Portal and sync them down to the HCP Anywhere Enterprise Edge Filer.

Chapter 3. Installing the HCP Anywhere Enterprise Edge Filer in an AWS

Environment

• Installing the HCP Anywhere Enterprise Edge Filer involves creating and configuring a virtual machine and then performing an initial configuration, described in Initial HCP Anywhere Enterprise Edge Filer Configuration.
• The HCP Anywhere Enterprise Edge Filer can be installed in an Amazon Web Services EC2 environment.
• Example AWS EC2 instance types that match the license:

Note: Amazon often adds instance types that are more powerful for the same or even less money.  Also, the instance type selected is dependent on the edge filer usage: memory intensive, network intensive, or CPU intensive. The above examples are for memory and network intensive workloads and not CPU intensive workloads. Hitachi Vantara recommends checking with Hitachi Vantara Support for the latest recommendations.
To set up the Amazon EC2 instance, go through the following sections in order. If you are using Amazon EC2 for the first time, sign up for an Amazon Web Services (AWS) account. Optionally, you can also sign up for an AWS Identity and Access Management (IAM) user account. Amazon recommends using IAM to control access to your EC2 instances, as well as other AWS resources.
Contact Hitachi Vantara, and request the latest Amazon Machine Image (AMI).

• Provide Hitachi Vantara with your Amazon account number.
• Provide Hitachi Vantara with the AWS region where you are planning to install the HCP Anywhere Enterprise Edge Filer instance.
• Hitachi Vantara will then share their latest AMI with your account.
• Warning: The HCP Anywhere Enterprise Edge Filer installation must be done using the
• AMI and not by cloning an existing HCP Anywhere Enterprise Edge Filer.

To install the HCP Anywhere Enterprise Edge Filer in an AWS EC2 environment:

1. From your Amazon Web Services account, sign in to the AWS Management Console.

2. In the AWS Management Console, select Services.

3. Under Compute, select EC2.
   The EC2 Dashboard is displayed.

4.  In the navigation pane, click IMAGES > AMIs.
   The IMAGES > AMIs screen is displayed.

5. Select the HCP Anywhere Enterprise Edge Filer image that Hitachi Vantara shared with you and click Launch.
   The Instances Wizard opens, displaying the Step 2: Choose an Instance Type screen.

6. Select the instance type for the license you purchased:

1. Click Next: Configure Instance Details.
   The Step 3: Configure Instance Details screen is displayed.

2. Configure the Network and Subnet settings.

3. Select the Protect against accidental termination check box.

4. Click Next: Add Storage.
   The Step 4 : Add Storage screen is displayed.

5.  Allocate an additional EBS volume.

6. Click Add New Volume. Another row is displayed in the table.

7. In the Volume Type field, select EBS.

8. In the Size field, type the size of the EBS volume. The minimum disk size is 1TB. Hitachi Vantara recommends storage of at least 20% of the HCP Anywhere Enterprise Portal Global Name Space. The maximum storage is dependent on the license.
   For an EV16 license the maximum is 16TB.
   For an EV32 license the maximum is 32TB.
   For an EV64 license the maximum is 64TB
   For an EV128 license the maximum is 128TB
   For an EV256 license the maximum is 256TB
   In the Volume Type field, select General Purpose SSD (gp3).
   Check Delete on Termination if you want the volume deleted when the instance is deleted.
   Check Encrypted if you want the volume encrypted.

9. Click Next: Tag Instance.
   The Step 5: Tag Instance screen is displayed.

10. Optionally, in the Key field, type Name and in the Value field, type a name for the HCP Anywhere Enterprise Edge Filer instance.

11. Click Next: Configure Security Group.
    The Step 6: Configure Security Group screen is displayed.

12. Enable the following TCP ports: 443, 8443, and 995.

13. Click Review and Launch.
    The Step 7: Review Instance Launch screen is displayed.

14. Review the configuration and click Launch.
    The Select an existing key pair or create a new key pair window is displayed.

15. Do one of the following.
    If you created a key pair, and have the private key file that corresponds to the pair in a safe Installing the HCP Anywhere Enterprise Edge Filer in an AWS Environment and accessible place, in the upper drop-down list, select

    • Choose an existing key pair; then select the name of the key pair that you created.
    • If you want to create a new key pair, do the following:
    • In the upper drop-down list, select Create a new key pair.
    • In the Key pair name field, enter a name for the key pair.
    • Click Download Key Pair.
    • A private key in *.poem format is downloaded.
    • Be sure to save the private key file in a safe place. You will need to provide the name of your key pair when you launch the instance and the corresponding private key each time you connect to the instance.
      Warning: Do not select Proceed without a key pair. If you launch your instance without  a key pair, you will not be able to connect to it.

16. Check the acknowledgment and click Launch Instances.
    The Launch Status screen is displayed.

17. Click View Instances.
    The Instances is displayed, showing the status of the instances.

18. Wait until the status checks for your instance have finished and then select the instance you created.
    Information about the instance is displayed on the screen, including the IP address to access the HCP Anywhere Enterprise Edge Filer.

Chapter 4. Initial HCP Anywhere Enterprise Edge Filer Configuration

After installing the HCP Anywhere Enterprise Edge Filer you perform an initial configuration.
In this chapter

• Configuring the HCP Anywhere Enterprise Portal as a Precondition to Setting Up the HCP Anywhere Enterprise Edge Filer
• Initial HCP Anywhere Enterprise Edge Filer Setup
• Loading a Trusted CA Certificate to a HCP Anywhere Enterprise Edge Filer

Configuring the HCP Anywhere Enterprise Portal as a Precondition to Setting Up the HCP Anywhere Enterprise Edge Filer

Before setting up the HCP Anywhere Enterprise Edge Filer, the HCP Anywhere Enterprise Portal administrator has to configure the HCP Anywhere Enterprise Portal to which the HCP Anywhere Enterprise Edge Filer will connect.

To configure the HCP Anywhere Enterprise Portal:

1. Sign in to the HCP Anywhere Enterprise Portal as a team administrator.

   • In a Web browser open
     http://./ServicesPortal.
     where, is the name of the portal, and is the DNS suffix for the HCP Anywhere Enterprise Portal installation.
     This opens the interface to the portal.

   • Note: If the HCP Anywhere Enterprise Portal is set to redirect HTTP requests to HTTPS, HCP Anywhere Enterprise Portal redirects the browser to the HTTPS page. It is also possible to set the HTTPS access port to be different from the standard 443. In this case, the address is: https://.:/Services Portal, where is a customized port.

   • For example, to connect to Acme’s administration HCP Anywhere Enterprise Portal using HTTPS port 2222, use the following address:

   • https://acme.example.com:2222/ServicesPortal.

   • The HCP Anywhere Enterprise Portal opens, displaying the sign in page.

   • Note: If SAML Single Sign On (SSO) is enabled, you are redirected to the SAML identity provider’s login page. If CAC, Common Access Card, is implemented at the site, the login page is skipped if the card access is authorized.

   • Enter your administrator user name and password and click SIGN IN. If you are redirected to an identity provider’s login page, enter your credentials there. The identity provider processes your authentication.
     The end user interface opens.

   • To access the full administrator interface, click the avatar at the top right, or your initials, if you have not configured an avatar, and select Administration. The administration interface opens in a new tab.

2. 2. Create a designated user as an owner of the cloud folders and data. Hitachi Vantara recommends creating the owner as a local service account with administrator read/write privileges and not a real user. This account must have read and write administrator permissions to enable syncing folders between the HCP Anywhere Enterprise Edge Filer and the HCP Anywhere Enterprise Portal global file system.
   Once the data is uploaded to the HCP Anywhere Enterprise Portal global file system there is an owner for the data who can get elevated rights.

   • Select Users > Users in the navigation pane.
     The USERS page is displayed.

   • Click New User.
     The New User window is displayed.

   • Complete the following fields in the Profile option.
     Username – A name for the user’s HCP Anywhere Enterprise Portal account.
     Email – An email address.
     First Name – A first name for the service account.
     Last Name – A last name for the service account.
     Role – Select Read/Write Administrator.
     Password/Retype Password – A password for the account.

   • Click SAVE.

3. Select Settings > User Roles in the navigation pane.
   The Roles window is displayed.

4. Click Read/Write Administrator and in the Edit Roles window make sure that Access End User Folders is granted.

Initial HCP Anywhere Enterprise Edge Filer Setup

• Before setting up the HCP Anywhere Enterprise Edge Filer, you have to configure the HCP Anywhere Enterprise Portal to which the HCP Anywhere Enterprise Edge Filer will connect, as described in Configuring the HCP
• Anywhere Enterprise Portal as a Precondition to Setting Up the HCP Anywhere Enterprise Edge Filer. After configuring the HCP Anywhere Enterprise Portal and installing the HCP Anywhere Enterprise Edge Filer, you need to perform an initial HCP Anywhere Enterprise Edge Filer setup. On first access to the HCP Anywhere Enterprise Edge Filer, you set up a HCP Anywhere Enterprise Edge Filer administrator and then a wizard guides you through connecting to a HCP Anywhere Enterprise Portal and storage and user setup. You can skip any of the wizard steps and perform them later, as described in the Hitachi Content Platform Anywhere Enterprise Edge Filer
• Administration Guide.
• After this initial HCP Anywhere Enterprise Edge Filer setup, the file server structure is synced from the HCP Anywhere Enterprise Portal to the HCP Anywhere Enterprise Edge Filer.

To access the HCP Anywhere Enterprise Edge Filer and initial setup:

1. Open any web browser.

2. Enter the HCP Anywhere Enterprise Edge Filer’s IP address to navigate to the device. When you connect to the web interface for the first time, your browser displays the Welcome to HCP Anywhere Enterprise page.

3.  Choose a user name and password for the administrator. The password must be at least eight  characters and must include at least a letter, digit and special character, such as ~, @, #, $ ,%, ^, & , (.
   Note: You can keep the default user name, admin. Other administrators are defined in the

4. Optionally, enter an email for receiving notifications regarding the HCP Anywhere Enterprise Edge Filer.

5. Click Save.
   If the HCP Anywhere Enterprise Edge Filer does not have a disk, the following message window is displayed.
   Add a disk to the HCP Anywhere Enterprise Edge Filer virtual machine. Otherwise, the Name this Edge Filer window is displayed.

6. Either keep the HCP Anywhere Enterprise Edge Filer default name or enter a new name to identify the HCP Anywhere Enterprise Edge Filer and click Next.
   The administration user interface is displayed to set up the HCP Anywhere Enterprise Edge Filer, starting with the Account Details window.
   Note: You can also change the HCP Anywhere Enterprise Edge Filer name after the initial setup, as described in the Hitachi Content Platform Anywhere Enterprise Edge Filer Administration Guide.

7. Enter the DNS name of the HCP Anywhere Enterprise Portal to which you have an account and want to connect the HCP Anywhere Enterprise Edge Filer to, in the Portal Address field and click Next.
   Note: If the HCP Anywhere Enterprise Portal does not have a valid certificate installed, a warning is displayed to the end user when logging a device into the portal, offering the option to proceed anyway.
   This warning is presented every time a user connects a device to the portal, until a valid certificate is installed.
   The Sign in window is displayed.
   Note: If single sign-on has been set up to the portal, click Sign In and then Allow in a new browser window that is displayed, when prompted. The Select License screen is displayed. Go to step 9.

8. Enter the HCP Anywhere Enterprise Portal designated user username and password, set in Configuring the HCP Anywhere Enterprise Portal as a Precondition to Setting Up the HCP Anywhere Enterprise Edge Filer to access the HCP Anywhere Enterprise Portal and click Next. The Select License window is displayed with the available licenses.
   The available storage and RAM are displayed.

9. Select the license for the HCP Anywhere Enterprise Edge Filer and click Next.
   The Select Gateway Mode window is displayed.
   CACHING – Provides users with LAN speed access to all the shared cloud folders on the HCP Anywhere Enterprise Portal. Shared storage is on the HCP Anywhere Enterprise Portal with stubs saved on the HCP Anywhere Enterprise Edge Filer. A stub is a file with a tiny footprint that contains the metadata about the file, such as the file name, size, and modification date. Only the folder and file metadata and not the actual file content is saved locally. Thus, the HCP Anywhere Enterprise Edge Filer can have much less physical storage than is made available to users, who have access to both the local HCP Anywhere Enterprise Edge Filer storage and the HCP Anywhere Enterprise Portal storage. Systems with many file changes, where only some of the files are required locally, don’t over use bandwidth between the cloud and HCP Anywhere Enterprise Edge Filer. Only the required files are passed across the wire. When a user accesses a file stub, the file is opened without delay, by streaming the file content from the cloud. After the download has completed, the file is unstubbed. Any changes to the file are synced back to the HCP Anywhere Enterprise Portal. Folders that are always required can be pinned, in which case the files in the folders, and not the stubs, are stored on the HCP Anywhere Enterprise Edge Filer.

10.  Click Next.
    The Easy Storage Setup window is displayed, showing the number of virtual disks.
    The maximum storage allowed for the selected HCP Anywhere Enterprise Edge Filer license is also displayed.

11.  Click Next.
    If there are options to configure the disks, for example, when more than one disk is defined, the Proposed Actions window is displayed with the recommended configuration. Hitachi Vantara recommends accepting the proposed actions and click Next and not clicking Skip.

12.  Click Next.
    The Join an Active Directory Domain window is displayed.

13. Specify the domain details so that the HCP Anywhere Enterprise Edge Filer is populated with the users from your Active Directory domain and click Next or, if you want to set up Active Directory later, click Skip.
    The Wizard Completed window is displayed.

14. Click Finish.
    The Configuration view Main > Welcome page is displayed.

15.  Select Main > Dashboard and verify that all the hard disk drives installed in the HCP Anywhere Enterprise Edge Filer are available.
    An LVM array, array1, which includes all the virtual disks, and a single volume, vol1, are created.

Note: You can rerun the wizard by selecting Main > Welcome and click Setup Wizard.
You can migrate a file server to HCP Anywhere Enterprise Edge Filer so that end users who are familiar with a given folder structure and share, while using the file server, continue to see the same folder structure and shares after migration to the HCP Anywhere Enterprise Edge Filer. If you are replacing an existing file server with the HCP Anywhere Enterprise Edge Filer, continue with Migrating a File Server.
When more than one DNS server is in use at the site, you can define the primary and secondary DNS servers, described in the Hitachi Content Platform Anywhere Enterprise Edge Filer Administration Guide, under Managing Network Settings.
For full details about managing the HCP Anywhere Enterprise Edge Filer, see the Hitachi Content Platform Anywhere Enterprise Edge Filer Administration Guide.

Loading a Trusted CA Certificate to a HCP Anywhere Enterprise Edge Filer

When the object storage used by theHCP Anywhere Enterprise Portal uses a X.509 Certificate signed by a private Certification Authority (a self-signed certificate) and not a public trusted certificate, this certificate must be uploaded to the HCP Anywhere Enterprise Edge Filer. You upload the certificate using the following procedure that requires a REST client tool such as Postman or HTTPie.
To upload a self-signed certificate to the HCP Anywhere Enterprise Edge Filer:

1. Get the certificate used by the object storage.
2. Launch the REST client.
3. Log in to the HCP Anywhere Enterprise Edge Filer with the following REST API, using HTTPS: https://edgefiler_IP/admingui/api/login with the following:

urlencoded](http://application/x-www-form-urlencoded)
Request Body| Key| Value
---|---|---
username password| u sername password
Expected Response Status|

• 200 OK and an HTTP session cookie which is then used for the duration of the session.
• The session times out after 30 minutes of inactivity.
• If a response such as 403 Forbidden is returned, check the user name and password provided.

Where:
edgefiler_IP – The IP address of the HCP Anywhere Enterprise Edge Filer.
username – Mandatory: The name of a user with administrative rights to the gateway. This is the username set in the procedure Initial HCP Anywhere Enterprise Edge Filer Setup. password – Mandatory: The password for the user. The login is over HTTPS to ensure that the password is encrypted. This is the password set in the procedure Initial HCP Anywhere Enterprise Edge Filer Setup.
Upon receiving a successful login reply, the server sets HTTP session cookies. The client must return these cookies to the server in the next request.
Note: To ensure that the session cookie returned by the API login is automatically returned in subsequent requests to the server, the same HTTP Client object must be used for all future requests.

1. Copy to your clipboard the contents of the certificate.
2. Upload the certificate using the following REST API:
   http://edgefiler_IP/admingui/api/config/extStorageTrustedCA?put with the following:

• —–BEGIN CERTIFICATE—–

• Certificate Content * —–END CERTIFICATE—–

Expected Response status| 200 OK

Where:
edgefiler_IP – The IP address of the HCP Anywhere Enterprise Edge Filer. Certificate Content – The content that was copied to the clipboard.

Chapter 5. Migrating a File Server

• You can migrate a file server to the HCP Anywhere Enterprise Edge Filer. After the migration has completed, end users who are familiar with a given folder structure and shares, as well as a given permission scheme continue to see the same folder structure, shares, and permission scheme. This enables the migration from a current file system to the HCP Anywhere Enterprise Edge Filer without the need to apply any structural changes such as flattening the folder structure or simplifying the permissions scheme.
• You can migrate file servers including a Windows Server, NetApp ONTAP, Isilon OneFS, Panzura Freedom Filer, NetAPP StorageGRID 9 (SMB), NetAPP StorageGRID 11 (SMB), Azure StorSimple, and Microsoft Azure Files.
• Access to files and folders after the migration is through SMB provided by the HCP Anywhere Enterprise Edge Filer so that users continue to access the files and folders in the same way as with the old system. You can migrate more storage than is physically available on the HCP Anywhere Enterprise Edge Filer and the user has access to the global namespace, even when this is much larger than the storage available on the HCP Anywhere Enterprise Edge Filer.
• Note: You can migrate a single file server to the HCP Anywhere Enterprise Edge Filer as a single  cloud folder. After the migration, the cloud folder will start with the C: path as it represents a single server with all the shares/nested shares.

Migrating a file server to a HCP Anywhere Enterprise Edge Filer can be performed while the current file server remains in production.
The flow when performing a migration is as follows:

Before migrating the file server to the HCP Anywhere Enterprise Edge Filer, the HCP Anywhere Enterprise Edge Filer must be connected to the HCP Anywhere Enterprise Portal. After finishing the initial setup, make sure that syncing between the HCP Anywhere Enterprise Edge Filer and HCP Anywhere Enterprise Portal is not suspended.
To migrate a single file server to the HCP Anywhere Enterprise Edge Filer as a single cloud folder involves the following procedures:

•  Discovering Shares – Optionally survey the current file server to discover which shares to migrate.
• Migrating Shares – Migration shares to the HCP Anywhere Enterprise Edge Filer.

After the migration, the cloud folder will start with the C: path as it represents a single server with all the shares/nested shares.
Note: Special characters in share names, % < > * ? | / \ + = ; : ” ,, are not supported by HCP Anywhere Enterprise Migrate. When such characters are used, the share contents are not migrated. This condition is reported, and the job is Completed with errors.
Share names that are over 80 characters in length and include the characters % [ ] will not be accessible from Windows clients and should also not be used in share names.

Discovering Shares

To discover the shares to migrate:

1. In the Configuration view, select Main > Welcome in the navigation pane. The Welcome page opens, displaying the HCP Anywhere Enterprise Edge Filer options.
   

2. Click File Server Migration.
   The File Server Migration page is displayed. 

3.  Click + to create a new job.
   The Create Discovery Job wizard is displayed showing the Task Type step.
   The default job is a Discovery job. This job analyses the file server that is being replaced to identify what data should be migrated.

4. Click Next.
   The Connect step is displayed.

5. Select the server type to connect to from the drop-down box. You can connect to a Windows Server, NetApp ONTAP, Isilon OneFS, Panzura Freedom Filer, NetAPP StorageGRID 9 (SMB), NetAPP StorageGRID1 (SMB), Azure StorSimple, Microsoft Azure Files, This Edge Filer, or another file server by selecting the Other option.
   You can run discovery on the edge filer itself, by selecting This Edge Filer for Server Type. When This Edge Filer is selected, no other Connect parameters are displayed.

6. For all server types except This Edge Filer, enter the IP address or DNS name for the source file server and an administrator user name and password to access this server.
   Note: The administrator used must have access to the files to migrate.

7. For Microsoft Azure Files, the shares cannot be presented and have to be added manually. Select Expert Mode to enable specifying the shares in the next step.

8. Click Next.
   The Select Shares step is displayed.
   The shares on the file server are displayed and you can select the shares that you want to migrate to the HCP Anywhere Enterprise Edge Filer.
   Note: When Expert Mode was selected, the following window is displayed where you enter the shares to migrate.

9. Select the shares to migrate and click Next.

10. Optionally, provide a different name for the job and any specific notes about the job.

11. Click Create.
    The discovery job runs and the results are displayed in the Dashboard.

The Dashboard After a Discovery Run
After analyzing the file server the job completes and you get a report as well as a full analysis of each share in the filer server that you selected.

Log files and discovery file lists generated by the migration are compressed if they are greater than 100MB.

Click the edit icon, to edit the discovery job name and notes.

• Click the report icon, to display the discovery report.
• Click the information icon,  to display the list of every time this job was run and rerun with the results of each run.
  The Task Details can also be accessed by clicking Details in the The Discovery Report.

• Click the run icon, to rerun the discovery.
  The discovery job reruns.

• Optionally, in the dashboard you can select a job and click the delete icon, to delete the job.

After deleting a job, you can display all the jobs including the deleted jobs by clicking the Deleted filter in the dashboard.

You can restore deleted jobs by selecting the deleted jobs to restore and clicking the undelete icon,

The Discovery Report

• Clicking the report icon, displays the discovery report.

• A report when Log Every File (Verbose Logging) was not checked.
  A report when Log Every File (Verbose Logging) was checked.

• At the top of the report the sum of the information for the migrated shares is displayed. Optionally, click the download CSV icon,  to download the discovery report as a .csv file.

• The first pane in the discovery report shows the list of shares with details of each share:

  • The number of folders in the selected shares.
  • The number of files in the selected shares.
  • The size of the selected shares.
  • The status of the migration for the selected shares.
  • If Log Every File (Verbose Logging) was checked, optionally for each share,    click download the discovery report for the share as a .csv file.

• Any errors in the discovery job are written to a separate log, under /error log. Each share with an error has a separate log file. Clicking the download icon,  downloads the log file as a .csv file.

The second pane in the discovery report has tabs showing the following:

• Files – A pie chart with the sizes of the files in the selected shares.

• Last Access – A bar chart showing when the files in the selected shares were last accessed.

• Last Modified – A bar chart showing when the files in the selected shares were last modified.

• File Types – The list of the file types in the selected shares.
  You can display this information either By Count, for example, the number of each file type, or By Size, for example, the size of each file type.

• Click Details to display the list of every time this job was run and rerun with the results of each run.

• Click Close to return to the Dashboard.

Migrating Shares

To migrate shares to the HCP Anywhere Enterprise Edge Filer:

1. In the Configuration view, select Main > Welcome in the navigation pane. The Welcome page opens, displaying the HCP Anywhere Enterprise Edge Filer options.

2.  Click File Server Migration.
   The File Server Migration page is displayed.

3.  Click + to create a new job.
   The Create Discovery Job wizard is displayed showing the Task Type step.
   The default job is a discovery job.

4. Click the Migration job to change the job to migrate a file server.

5. Click Next.
   The Connect step is displayed.

6. Select the server type to connect to from the drop-down box. You can connect to a windows Server, NetApp ONTAP, Isilon OneFS, Panzura Freedom Filer, NetAPP StorageGRID 9 (SMB), NetAPP StorageGRID1 (SMB), Azure StorSimple, Microsoft Azure Files, or another file server by selecting the Other option, or another file server by selecting the Other option.

7. Enter the IP address or DNS name for the source file server and an administrator user name and password to access the filer server.
   Note: The administrator used must have access to the files to migrate.

8. For Microsoft Azure Files, the shares cannot be presented and have to be added manually. Select Expert Mode to enable specifying the shares in the next step.

9. Click Next.
   The Select Shares step is displayed.
   Note: When Expert Mode was selected, a window is displayed where you enter the shares  to migrate.

10. Select the shares to migrate and click Next.
    The Select Options step is displayed.

11. 11. Optionally, provide a different name for the job and any specific notes about the job.

12. 12. You can specify patterns that you do not want to migrate, or that you do want to migrate, separating each pattern with a colon (:). You can include the asterisk (*) as a wildcard in the pattern. To specify the pattern, check the relevant box.

    • Exclude these path patterns from the migration (use the colon character (’:’) as a separator)
    • Include these path patterns in the migration (use the colon character (’:’) as a separator)
      To migrate specific folders in a share, instead of all the folders in the share:
      Include the folders by specifying each folder path.
      Note: Using the option to migrate specific folders can cause a migration to fail, depending on the size of the folders being migrated and the amount of RAM available to the HCP Anywhere Enterprise Edge Filer.

13. Check Validate and report checksums post-migration to include an MD5 hash checksum for every file being migrated to verify the migration was successful when the hash is compared with the checksum of the file in the source file server.

14. Check Migrate last access and creation time to include in the migration the last access time the creation time for each item being migrated.

15. You can select to migrate the data from the file server with the ACLs.

16.  You can specify when to start the migration:

    • Start now to start the migration immediately.
    • Don’t start to save the job configuration for later use.
    • Schedule to schedule the date and time to start the migration.

17.  You can throttle the bandwidth used for the migration with the time range to apply this throttling so as not to adversely impact ongoing work by bandwidth and time.

18.  Check Copy each share to a distinct Cloud Folder if you want to specify that each share is migrated to a distinct cloud folder.
    The cloud folder where the cloud folders are migrated is displayed under the Copy each share to a distinct Cloud Folder checkbox.
    When Copy each share to a distinct Cloud Folder is checked:

    • Jobs that were created in a previous version will continue to migrate into the cloud folder root directory.
    • New jobs will create a redundant directory with the name of the source share into the cloud folder root directory, and migrate into it instead.
      When Copy each share to a distinct Cloud Folder is not checked:
      Depending on the source exposing the data, either the full path in the original server is recreated and no files are migrated into the cloud folder root, or the share name is used under the cloud folder root as was the case in previous versions.

19.  Click Create.
    During the migration, the progress bar in the Dashboard shows the percentage completed and what is currently being processed.
    After migrating all the shares, the job completes and an email alert is sent with the job summary.

20.   Click the edit icon, to edit the migration job name, notes, include and exclude paths, migration checksum, whether to migrate access and creation times, schedule and throttling.
    

21.  Click the report icon,  to display the migration report.

22. Optionally, click the log download icon, to download the migration log file to a .log text file.

23.  Click the information icon, to display the list of every time this job was run with the results of each run, including the start and end times for the job, the number of files migrated and the total size of the migration, access to the report and the ability to download the log, which provides information about the migration and any errors that occurred during the migration.

24. Optionally, in the dashboard you can select a job and click the delete icon, to delete the job. After deleting a job, you can display all the jobs including the deleted jobs by clicking the Deleted filter in the dashboard.
    You can restore deleted jobs by selecting the deleted jobs to restore and clicking the undelete icon,
    The share structure from the source is recreated on the HCP Anywhere Enterprise Edge Filer, including nested shares and their permissions. If there are any recoverable errors during the copy process, retry the migration for the failed shares.
    Note: Only ACLs are migrated with the files. Extended attributes are not migrated. In the HCP Anywhere Enterprise Edge Filer the shares are defined with Windows ACL Emulation Mode.
    Direct all the users to the HCP Anywhere Enterprise Edge Filer.
    Users can now access and work on the HCP Anywhere Enterprise Edge Filer.

Completing a Migration and Performing a Delta Migration

After completing the migration there may well be a number of new or changed files on the original file server that require migrating. Complete the migration process using the following procedure.
To complete a migration:

1. During off-peak hours, disconnect the filer server.

2. In the HCP Anywhere Enterprise Edge Filer user interface, pin the folders that you want to remain local to the HCP Anywhere Enterprise Edge Filer.

   • In the Configuration view, select Cloud Drive > Pinned Folders in the navigation pane. The Pinned Folders page is displayed.
     The Pinned Folders area is separated into a users pane and folders pane, with paging in the users pane. This makes it easier to page through the users and select the folders to pin.

   • Select a user to display the folders owned by the user and then select the folders that you want pinned for this user, so that the folder content is always available on the HCP Anywhere Enterprise Edge Filer.
     In addition, you can use the search field to jump to a specific user.

   • Note: You can select a a user to select all the folders and subfolders owned by the user. You can also select a higher level folder to select all the subfolders under it and then uncheck specific folders to unpin them. If you check a cloud folder, all the subfolders under the cloud folder are pinned and any folders added later under the cloud folder will be pinned automatically.

   • Click Save.
     The checked folders are pinned.

3. In the Configuration view’s Main > Welcome page, click File Server Migration. The File Server Migration page is displayed showing the discover and migration jobs previously run.

4. Select the migration job to rerun and click the run icon

The migration job reruns, migrating the deltas from the last migration.

Migrating a File Server
Hitachi Content Platform Anywhere Enterprise

Hitachi Vantara

•  Corporate Headquarters 2535 Augustine Drive
• Santa Clara, CA 95054 USA www.HitachiVantara.com community.HitachiVantara.com
• Regional Contact Information
• Americas: +1 866 374 5822 or info@hitachivantara.com
• Europe, Middle East and Afr ica: +44 (0) 1753 618000 or info.emea@hitachivantara.com
• Asia Pacific: +852 3189 7900 or info.marketing.apac@hitachivantara.com

References

• Home - Hitachi Vantara
• Hitachi Vantara: Innovation Through Data Infrastructure | Hitachi Vantara
• Login Page
• Hitachi Vantara Support

Read User Manual Online (PDF format)

Read User Manual Online (PDF format)  >>

Download This Manual (PDF format)

Download this manual  >>