ETERNUS vCenter Plug-in 3.0.0 User's Guide - … · This chapter provides an overview of ETERNUS vCenter Plug-in and also explains functions and operations ... ETERNUS vCenter Plug-in

ETERNUS vCenter Plug-in 3.0.0

User's Guide

P3AM-7442-04ENZ0

This page is intentionally left blank.

Preface

This manual explains an overview and usage of ETERNUS vCenter Plug-in.

Fourth EditionDecember 2015

Organization

The contents of this manual are as follows:

● Chapter 1 About ETERNUS vCenter Plug-in (Common for SAN and NAS)

This chapter provides an overview of ETERNUS vCenter Plug-in and also explains functions and operationsfor ETERNUS vCenter Plug-in.

● Chapter 2 Installation and Initial Setup (Common for SAN and NAS)

This chapter describes installation and initial setup for ETERNUS vCenter Plug-in.

● Chapter 3 SAN Functions

This chapter describes the SAN functions of ETERNUS vCenter Plug-in.

● Chapter 4 NAS Functions

This chapter describes the NAS functions of ETERNUS vCenter Plug-in.

● Chapter 5 Backup/Restore of ETERNUS vCenter Plug-in (Common for SAN and NAS)

This chapter explains how to migrate vCenter Server to a different machine.

● Chapter 6 Changing Settings

This chapter explains how to change various settings.

● Chapter 7 Required Information for Failure Investigation

This chapter describes the required information for failure investigation.

ETERNUS vCenter Plug-in 3.0.0 User’s Guide

Copyright 2015 FUJITSU LIMITED P3AM-7442-04ENZ0

3

Preface

The following contents are described as appendices:

• Appendix A Frequent Inquiry Solutions (Common for SAN and NAS)• Appendix B Role Control• Appendix C List of Displayed Items• Appendix D Messages• Appendix E JRE Use Conditions (Common for SAN and NAS)• Appendix F About Open Source Software License (Common for SAN and NAS)

Naming Conventions

Abbreviations Used in This Manual

In this manual, "ETERNUS DX" refers to a storage system that is supported by ETERNUS vCenter Plug-in. For thesupported storage systems, refer to the following website:

http://www.fujitsu.com/global/support/products/computing/storage/download/evcp.html

In this manual, the configuration/management software that is included in the ETERNUS DX controller isreferred to as "ETERNUS Web GUI" for the web-based interface and "ETERNUS CLI" for the command lineinterface.

Symbols and Expressions

The following symbols and expressions are used in this manual:

Points to note when using the product.

Functions and know-how which can be useful when setting up or operating ETERNUSvCenter Plug-in.



4


Preface

Product Names

The following products are referred to as "Windows Server":• Microsoft® Windows Server® 2008 R2 Standard• Microsoft® Windows Server® 2008 R2 Enterprise• Microsoft® Windows Server® 2008 R2 Datacenter• Microsoft® Windows Server® 2012 Datacenter• Microsoft® Windows Server® 2012 Standard• Microsoft® Windows Server® 2012 Essentials• Microsoft® Windows Server® 2012 Foundation• Microsoft® Windows Server® 2012 R2 Datacenter• Microsoft® Windows Server® 2012 R2 Standard• Microsoft® Windows Server® 2012 R2 Essentials• Microsoft® Windows Server® 2012 R2 Foundation

Acknowledgments

• Microsoft, Windows, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

• VMware is either a registered trademark or trademark of VMware, Inc. in the U.S. and/or other countries.• Oracle and Java are registered trademarks of Oracle and/or its affiliates.• Itanium is a trademark or registered trademark of Intel Corporation or its subsidiaries in the United States

and other countries.• The company names, product names and service names mentioned in this document are trademarks or

registered trademarks of their respective companies. In this document, system names and product names are not necessarily indicated with a trademark of ® or ™.

Microsoft product screen shot(s) reprinted with permission from Microsoft Corporation.



5

Release Information

ETERNUS vCenter Plug-in Modification History

This section provides a history of modifications for ETERNUS vCenter Plug-in.

Version Modification effect

1.0.1 None

1.1.0 Changed the tab name to [FUJITSU ETERNUS DX]

1.1.1 None

1.1.2 Changed the recommended value for the ETERNUS DX60 S2/DX80 S2/DX90 S2 to Round Robin as the Path Policy (Recommend) in the Best Practice Settings window

2.0.0 • vSphere Client is not supported

• Deleted the -i option and the -p option from the "evcpConfig" command

2.1.0 Changed the product name of the ETERNUS DX that is displayed for each function to the characters that are assigned to each device

2.2.0 • Changed the product names for ETERNUS DX storage systems that are displayed in each wiz-ard screen to the storage system names of ETERNUS DX storage systems. Also changed the display item name to "Storage System Name".

• Changed the message that is displayed when selecting an unregistered ETERNUS DX in the storage information display screen or the adapter information display screen from STXE1001 to STXE1019

• Changed the message that is displayed when selecting an unsupported ETERNUS DX in the storage information display screen from STXE1002 to STXE1019

• Changed the adapter information display screen to display the unsupported ETERNUS DX information only with the serial number in the "Storage Targets" window

• Changed the system to display the STXE2012 message when a user attempts to specify a RAID group in which volumes other than Standard, WSV, SDV, or SDPV are registered to pre-vent the registration of the new resource

• Changed the system to display the STXE2015 message when rescanning of an HBA fails while datastores/volumes are being added

2.2.1 Changed the product names for ETERNUS DX storage systems that are displayed in each function to "ETERNUS DX" in version 2.2.1 and later

3.0.0 • Changed the default installation folder from "<system_drive>:\Program Files\ETERNUS vCen-ter Plug-in" to "<system_drive>:\ETERNUS vCenter Plug-in"

• Changed some of the wizard names, menu names, item names, and icons

• Changed the system to display Japanese when the browser whose language setting is Japa-nese is used

• Deleted the [Continue] button from the execution result screen of the Register Resource Wiz-ard

• Deleted the [Continue] button from the execution result screen of the Delete Datastore/LUN Wizard

• Changed the system to not display the datastore name in the [Type] properties of the [Vir-tual Disks] window



6

Release Information

ETERNUS vCenter Plug-in Updates

The following table shows the updates for each ETERNUS vCenter Plug-in version:

Version Modification details

1.0.0(February 2012)

First version

1.0.1(April 2012)

Corrected version

• Corrected the display error when a license for the Advanced Copy or Thin Provisioning functions is not registered

• Corrected the display error when an unsupported disk is used as Raw Device Mapping

1.1.0(June 2012)

• Added support for the function to display adapter information

• Added support for the function to display performance information

• Added support for the function to display best practice information

• Added support for the ETERNUS DX60 S2

1.1.1(August 2012)

Corrected version

• Corrected the display error when the NFS datastore is used

• Corrected the display error when a Wide Striping Volume is used

2.0.0(December 2012)

• Added support for VMware Web Client

• Added support for the new datastore/volume function

• Added the -l option to the "evcpConfig" command

2.1.0(July 2013)

• Added support for the new datastore/volume function for clusters

• Added support for the new function to delete datastores/volumes

• Added support for the function to display WSV/FTV information

2.2.0(December 2013)

• Added support for the ETERNUS DX100 S3/DX200 S3, DX500 S3/DX600 S3, and ETERNUS DX200F

2.2.1(January 2015)

• Added support for the ETERNUS DX60 S3

3.0.0(November 2015)

• Added support for vSphere 6

• Added support for the ETERNUS DX8700 S3/DX8900 S3

• Added support for NAS functions

• Added support for role control

• Added support for displaying Japanese

• Added functions for displaying the maximum number of LUNs and the number of created LUNs



7

Table of Contents

Chapter 1 About ETERNUS vCenter Plug-in (Common for SAN and NAS) 13

1.1 Overview ........................................................................................................................... 13

1.2 Functions .......................................................................................................................... 14

1.3 Operation .......................................................................................................................... 18

1.4 Supported Environment .................................................................................................... 18

1.5 Required Resources ........................................................................................................... 191.5.1 Disk Space Required for Installation .............................................................................................................. 191.5.2 Disk Space Required for Operation ................................................................................................................. 19

1.6 Exclusive Software ............................................................................................................ 19

1.7 Notes ................................................................................................................................ 201.7.1 Firewall Settings ............................................................................................................................................ 201.7.2 SSH Settings for the ETERNUS DX ................................................................................................................... 201.7.3 Supported Processors ..................................................................................................................................... 201.7.4 Displaying Performance Monitoring and Performance Information ............................................................... 201.7.5 IP Addresses .................................................................................................................................................. 211.7.6 Creating and Deleting Datastores/Volumes ................................................................................................... 211.7.7 Virtual Volumes (VVOL) ................................................................................................................................. 211.7.8 NAS Functions ................................................................................................................................................ 21

Chapter 2 Installation and Initial Setup (Common for SAN and NAS) 22

2.1 New Installation ............................................................................................................... 22

2.2 Operations Required After New Installation ...................................................................... 252.2.1 Registering ETERNUS DX Storage Systems for Management .......................................................................... 25

2.3 Upgrading ETERNUS vCenter Plug-in ................................................................................. 25

2.4 Setting the User Privileges ................................................................................................ 27

2.5 Uninstallation ................................................................................................................... 30

Chapter 3 SAN Functions 32

3.1 Displaying Storage Information ........................................................................................ 323.1.1 Displaying Datastore Information .................................................................................................................. 323.1.2 Displaying Virtual Machine Information ........................................................................................................ 343.1.3 Displaying Host Information .......................................................................................................................... 36



8

Table of Contents

3.1.4 Notes ............................................................................................................................................................. 38

3.2 Displaying Adapter Information ........................................................................................ 39

3.3 Displaying Performance Monitoring and Performance Information .................................. 413.3.1 Starting Performance Monitoring .................................................................................................................. 413.3.2 Displaying Performance Information ............................................................................................................. 433.3.3 Stopping Performance Monitoring ................................................................................................................. 45

3.4 Refreshing Displayed Information ..................................................................................... 48

3.5 Registering ETERNUS DX Storage Systems ......................................................................... 493.5.1 Starting the Register Storage Wizard ............................................................................................................. 493.5.2 Registering ETERNUS DX Storage Systems ..................................................................................................... 503.5.3 Unregistering ETERNUS DX Storage Systems .................................................................................................. 52

3.6 Adding or Deleting Datastores/Volumes ........................................................................... 543.6.1 Registering Resources .................................................................................................................................... 543.6.2 Creating Volumes/Datastores ......................................................................................................................... 573.6.3 Deleting Volumes/Datastores ........................................................................................................................ 623.6.4 Unregistering Resources ................................................................................................................................ 653.6.5 Points to Note ................................................................................................................................................ 68

Chapter 4 NAS Functions 69

4.1 Preliminary Preparation for Using the NAS Functions ....................................................... 694.1.1 Preliminary Settings by ETERNUS DX Storage Systems ................................................................................... 694.1.2 Preliminary Settings for ETERNUS SF .............................................................................................................. 704.1.3 Preliminary Settings by vCenter Server .......................................................................................................... 73

4.2 Initial Setup in ETERNUS vCenter Plug-in .......................................................................... 744.2.1 Registering, Deleting, or Updating Storage Systems ...................................................................................... 744.2.2 Registering, Deleting, or Updating Resources ................................................................................................ 794.2.3 Registering, Changing, or Deleting ETERNUS SF Connection Information ...................................................... 84

4.3 Creating Datastores and Virtual Machines ........................................................................ 924.3.1 Creating Datastores or LUNs .......................................................................................................................... 924.3.2 Changing NFS Allowed Hosts for a Datastore ............................................................................................... 1034.3.3 Creating Virtual Machines ............................................................................................................................ 105

4.4 Backing Up Datastores and Virtual Machines .................................................................. 1064.4.1 Creating a Schedule ..................................................................................................................................... 1064.4.2 Changing a Schedule ................................................................................................................................... 1104.4.3 Disabling or Enabling a Schedule ................................................................................................................ 1134.4.4 Executing a Schedule Immediately .............................................................................................................. 1174.4.5 Canceling a Schedule That Is Being Executed .............................................................................................. 1204.4.6 Deleting a Schedule ..................................................................................................................................... 121



9

Table of Contents

4.5 Restoring a Virtual Machine ............................................................................................ 1234.5.1 Restoring a Virtual Machine ......................................................................................................................... 1234.5.2 Canceling Virtual Machine Restore and Recovering It from Cancellation ..................................................... 1284.5.3 Single Item Restore ..................................................................................................................................... 1334.5.4 Stopping Single Item Restore Immediately .................................................................................................. 1374.5.5 Canceling Single Item Restore and Recovering It from Cancellation ............................................................ 1394.5.6 Restoring from NAS Backups or Backups between ETERNUS DX Storage Systems ........................................ 142

4.6 Changing Settings ........................................................................................................... 1444.6.1 Changing Storage Information .................................................................................................................... 1444.6.2 Changing Resource Information .................................................................................................................. 1444.6.3 Changing ETERNUS SF Information .............................................................................................................. 1444.6.4 Expanding the Capacity of a Datastore ........................................................................................................ 1444.6.5 Changing NFS Allowed Hosts for a Datastore ............................................................................................... 146

4.7 Deleting Datastores or LUNs ........................................................................................... 147

4.8 Displaying Information ................................................................................................... 1504.8.1 FUJITSU Storage ETERNUS DX Screen ............................................................................................................ 1504.8.2 Displaying Datastore Information ................................................................................................................ 1524.8.3 Displaying Virtual Machine Information ...................................................................................................... 1564.8.4 Displaying Host System Information ............................................................................................................ 1584.8.5 Performance Information ............................................................................................................................ 160

Chapter 5 Backup/Restore of ETERNUS vCenter Plug-in

(Common for SAN and NAS) 161

5.1 Backing Up the Setting Information for ETERNUS vCenter Plug-in ................................... 161

5.2 Restoring the Setting Information for ETERNUS vCenter Plug-in ..................................... 162

5.3 Migrating the Environment to Other vSphere Web Client Servers ................................... 162

Chapter 6 Changing Settings 163

6.1 Changing Settings for ETERNUS DX Storage Systems ....................................................... 163

6.2 Changing Settings for Windows Server Where vCenter Server Is Installed ....................... 164

6.3 evcpConfig Command ..................................................................................................... 165

Chapter 7 Required Information for Failure Investigation 167



10

Table of Contents

Appendix A Frequent Inquiry Solutions (Common for SAN and NAS) 168

A.1 The Initial Setup During Installation Failed or Was Skipped............................................. 168

A.2 The Environment Settings Are Not Retained Normally After Upgrading ETERNUS vCenter Plug-in ................................................................................................. 169

Appendix B Role Control 171

B.1 ETERNUS vCp Administrator ............................................................................................. 171

B.2 ETERNUS vCp Provision .................................................................................................... 173

B.3 ETERNUS vCp Backup ....................................................................................................... 174

B.4 ETERNUS vCp Restore ....................................................................................................... 175

B.5 ETERNUS vCp Single Item Restore .................................................................................... 176

B.6 ETERNUS vCp Read-only ................................................................................................... 177

Appendix C List of Displayed Items 178

C.1 Datastore Detail (SAN) .................................................................................................... 178

C.2 Datastore Detail (NAS) .................................................................................................... 178

C.3 Schedule Status (NAS) ..................................................................................................... 178

C.4 Schedule Information (NAS) ............................................................................................ 179

C.5 NAS Volume (NAS)........................................................................................................... 180

C.6 NFS Datastores located on the NAS Volume (NAS)........................................................... 180

C.7 Virtual Disks (Common for SAN and NAS) ........................................................................ 181

C.8 Snapshots (NAS) .............................................................................................................. 181

C.9 Single Item Restore Information (NAS)............................................................................ 181

C.10 Assigned Disks (Datastore) (Common for SAN and NAS) ................................................. 182

C.11 Assigned Disks (Raw Device Mapping) (SAN) .................................................................. 182

C.12 Assigned Disks (Others) (SAN)......................................................................................... 183

C.13 ETERNUS Details (Common for SAN and NAS).................................................................. 183

C.14 Adapter (Server Adapters) (SAN) ..................................................................................... 193

C.15 Adapter (Storage Targets) (SAN) ..................................................................................... 194

C.16 Adapter (Storage LUNs) (SAN)......................................................................................... 194

C.17 Performance (Common for SAN and NAS)........................................................................ 195



11

Table of Contents

C.18 Storage Information (Common for SAN and NAS) ............................................................ 196

C.19 Resource Pool Information (Common for SAN and NAS) .................................................. 196

C.20 ETERNUS SF Connection information (NAS) ..................................................................... 197

Appendix D Messages 198

D.1 Common for SAN and NAS................................................................................................ 198D.1.1 Performance Information ............................................................................................................................ 198D.1.2 Registering Storage Systems ....................................................................................................................... 203D.1.3 evcpConfig Command.................................................................................................................................. 206D.1.4 Adding and Deleting Datastores/Volumes ................................................................................................... 208

D.2 NAS.................................................................................................................................. 213D.2.1 Provisioning ................................................................................................................................................ 213D.2.2 Backup ........................................................................................................................................................ 215D.2.3 Restore ........................................................................................................................................................ 222D.2.4 Other Messages ........................................................................................................................................... 232

Appendix E JRE Use Conditions (Common for SAN and NAS) 256

Appendix F About Open Source Software License

(Common for SAN and NAS) 257



12

Chapter 1

About ETERNUS vCenter Plug-in (Common for SAN and NAS)

1.1 Overview

ETERNUS vCenter Plug-in expands the user interface of VMware vSphere Web Client (hereinafter referred to as"vSphere Web Client") to provide various functions for Fujitsu ETERNUS DX storage systems that can be used incombination with vCenter Server. Application of this product facilitates visualization of information on thestorage systems and allows the VMware administrators to grasp physical and virtual mapping related tovirtual machines, datastores and host systems, which enables integrated management of the infrastructure ofvirtual environment.The VMware administrator can also perform operations related to datastores/volumes from vSphere WebClient without being aware of the ETERNUS DX. In addition, NFS datastores and virtual machines can bebacked up or restored if the Unified storage function of the ETERNUS DX is enabled.



13

Chapter 1 About ETERNUS vCenter Plug-in (Common for SAN and NAS) 1.2 Functions

1.2 Functions

■ Information display function

By selecting a VMware object from the inventory tree of vSphere Web Client, the [FUJITSU ETERNUS DX] tab isadded under the [Manage] tab. Selecting this tab enables the information of the ETERNUS DX to be displayedon vSphere Web Client.



14


■ Operating datastores/volumes

This function is used to operate datastores/volumes.By selecting a VMware host or a VMware cluster from the inventory tree of vSphere Web Client and by right-clicking on it, [ALL FUJITSU ETERNUS DX Actions] is added to the menu list. The "Create Datastore/LUN" and"Delete Datastore/LUN" functions can be performed with the wizard process that is started from this menu."Modify NFS Allowed Host" and "Expand Capacity of Datastore (NAS Volume)" can also be performed for NFSdatastores.



15


■ Backing up datastores and virtual machines

This function is used to acquire NAS snapshots of virtual machines that are stored in datastores and to performNAS backups for NAS volumes by creating backup schedules for NFS datastores (or NAS volumes).By selecting a datastore from the inventory tree of vSphere Web Client, and by right-clicking on it or clicking[Actions] at the top of the screen, [ALL FUJITSU ETERNUS DX Actions] is added to the menu list. The followingoperations can be performed with the wizard process that is started from this menu.

• Create Schedule• Modify Schedule• Enable Schedule• Disable Schedule• Delete Schedule• Backup Now



16


■ Restoring virtual machines

This function is used to restore virtual machines from NAS snapshots.By selecting a virtual machine from the inventory tree of vSphere Web Client, and by right-clicking on it orclicking [Actions] at the top of the screen, [ALL FUJITSU ETERNUS DX Actions] is added to the menu list. Thefollowing operations can be performed with the wizard process that is started from this menu.

• Restore Virtual Machine• Single Item Restore• Stop Single Item Restore



17

Chapter 1 About ETERNUS vCenter Plug-in (Common for SAN and NAS) 1.3 Operation

1.3 Operation

Install ETERNUS vCenter Plug-in in a Windows server in which vSphere Web Client is installed. The followingfigure shows a system configuration example.

1.4 Supported Environment

For the storage systems, and for the versions of VMware vSphere and vSphere Web Client that are supportedby ETERNUS vCenter Plug-in, refer to the following website:


When vCSA (vCenter Server Appliance) is used as the vCenter Server, ETERNUS vCenter Plug-in cannot be installed in a vSphere Web Client that is bundled with vCSA. Install ETERNUS vCenter Plug-in in a Windows server in which vSphere Web Client is already installed.



18


Chapter 1 About ETERNUS vCenter Plug-in (Common for SAN and NAS) 1.5 Required Resources

1.5 Required Resources

1.5.1 Disk Space Required for Installation

*1: The default installation folder is as follows:<system drive>:\ETERNUS vCenter Plug-in

1.5.2 Disk Space Required for Operation

*1: The default installation folder is as follows:<system drive>:\ETERNUS vCenter Plug-in

1.6 Exclusive Software

Do not start the following software at the same time as ETERNUS vCenter Plug-in. If the following software isrunning, information about the ETERNUS DX may not be displayed in the [FUJITSU ETERNUS DX] tab.

• ETERNUS Web GUI• ETERNUS CLI (Command Line Interface)

The following software can be used at the same time as ETERNUS vCenter Plug-in:• ETERNUS SF Storage Cruiser• ServerView Resource Coordinator VE

Note that a message about exclusive software that has a message number such as STXE1006 may be displayed while operating ETERNUS vCenter Plug-in. If this type of message is displayed, close the window of ETERNUS SF Storage Cruiser or ServerView Resource Coordinator VE and reperform the operation with ETERNUS vCenter Plug-in. The above software can be used again after the target operations with ETERNUS vCenter Plug-in are complete.

No. Details Space Folder

1 Program storage 200MB Installation folder (*1)

No. Details Space Folder

1 Trace log 250MB Installation folder (*1)



19

Chapter 1 About ETERNUS vCenter Plug-in (Common for SAN and NAS) 1.7 Notes

1.7 Notes

1.7.1 Firewall Settings

Set the following port numbers to bypass the firewall when setting up a firewall between the server in whichETERNUS vCenter Plug-in is installed and the ETERNUS DX or ETERNUS SF.

*1: Used for communication only when ssh is used to link ETERNUS vCenter Plug-in with ETERNUS SF.*2: These set ports that are used for communication can be changed arbitrarily.*3: Used for communication only when PowerShell (http) is used to link ETERNUS vCenter Plug-in with ETERNUS SF.*4: Used for communication only when PowerShell (https) is used to link ETERNUS vCenter Plug-in with ETERNUS SF.

1.7.2 SSH Settings for the ETERNUS DX

Enable the SSH connection for the monitoring target ETERNUS DX. For details, refer to "ETERNUS Web GUIUser's Guide".

1.7.3 Supported Processors

Itanium is not supported.

1.7.4 Displaying Performance Monitoring and Performance Information

• This function is not supported for the ETERNUS DX60 S2 Disk storage system.• Firmware version V10L30-0000 or later for the ETERNUS DX is required to use this function with the

ETERNUS DX S2 series.

No. Destination Port number/protocol Communication direction

1ETERNUS DX 1999/tcp From the server in which ETERNUS vCenter Plug-in

is installed to the ETERNUS DX





4(*1)ETERNUS SF 22/tcp(*2) From the server in which ETERNUS vCenter Plug-in

is installed to ETERNUS SF







20

Chapter 1 About ETERNUS vCenter Plug-in (Common for SAN and NAS) 1.7 Notes

1.7.5 IP Addresses

IPv4 and IPv6 can be used for vCenter Server and ETERNUS DX storage systems that are managed by ETERNUSvCenter Plug-in.However, when both IPv4 and IPv6 are set for NAS interfaces in the ETERNUS DX, the IP addresses are used inthe order of IPv4, IPv6 link local addresses, and IPv6 connect IP addresses. Note that if a connection erroroccurs in a high priority IP address, a different IP address cannot be used.

1.7.6 Creating and Deleting Datastores/Volumes


ETERNUS DX S2 series.• Fibre Channel, iSCSI, and NFS are supported for interfaces between servers and ETERNUS DX storage sys-

tems.• This function is not supported for Flexible Tier Volumes (FTV) and Wide Striping Volumes (WSV).• A datastore/volume that is used in Virtual Machine cannot be deleted with this function.• To use an iSCSI interface, "Network Port Binding" must be performed with vSphere Web Client. Refer to the

vSphere Web Client help for a detailed procedure on performing this action.

1.7.7 Virtual Volumes (VVOL)

VVOL is not supported.

1.7.8 NAS Functions

• Except for an ETERNUS DX S3 with the unified storage function, these functions are not supported in any other models.

• For the ETERNUS DX S3 series, firmware version V10L51-0000 or later is required in order to use these func-tions.

• Refer to "Confirmed OS" in "ETERNUS DX Disk storage system Configuration Guide (NAS)" before using these functions.

• If an error occurs in the ETERNUS DX when ETERNUS vCenter Plug-in is operating, the following events may occur:

- The execution of the schedule fails.- A virtual machine restore or single item restore fails.

• To use NAS interfaces on the ETERNUS DX that is registered in ETERNUS vCenter Plug-in, ports must be specified in advance.

• Virtual machines cannot be started in the following situations:- NAS volumes do not have free space.- The limited capacity is exceeded when a quota is set to the NFS datastore.

• When installing Windows PowerShell 3.0 or when updating Windows PowerShell to version 3.0, restart the VMware vSphere Web Client service if the service is running.



21

Chapter 2

Installation and Initial Setup (Common for SAN and NAS)

The installation methods for ETERNUS vCenter Plug-in are described as below:• New installation

Perform the procedures from "2.1 New Installation" (page 22) to "2.2 Operations Required After NewInstallation" (page 25).

• Upgrade ETERNUS vCenter Plug-inPerform the procedure in "2.3 Upgrading ETERNUS vCenter Plug-in" (page 25).

2.1 New Installation

Install ETERNUS vCenter Plug-in using the following procedure:

Procedure

1 Extract the downloaded file.

2 Double-click the extracted ETERNUS vCenter Plug-in installer to start the wizard. Proceed with the installation according to the wizard.

When the installation is complete, the vSphere Web Client service automatically restarts.



22

Chapter 2 Installation and Initial Setup (Common for SAN and NAS) 2.1 New Installation

3 Enter all of the following items, and then click the [Register] button.

• IP AddressEnter the IP address of the vCenter Server that is to be registered to ETERNUS vCenter Plug-in.Do not enter a local loopback address.

• User NameEnter a valid account of the vCenter Server specified above.

• PasswordEnter the password for the account specified above.

In the [Initialization] screen, perform the initial setup (registering the vCenter Server to ETERNUSvCenter Plug-in).Register the vCenter Server to ETERNUS vCenter Plug-in and log in to the vSphere Web Client that man-ages the vCenter Server. Then, the information of the ETERNUS DX can be displayed on vSphere WebClient.

• If the [Skip] button is clicked, the installation process completes without performing the initial setup. In this case, the initial setup must be performed manually after installation. For details, refer to "Appendix A Frequent Inquiry Solutions (Common for SAN and NAS)" (page 168).

• Multiple vCenter Servers can be registered to ETERNUS vCenter Plug-in. For the second and subse-quent vCenter Servers, register each one separately using the "evcpConfig -a" command after the installation is completed.



23

Chapter 2 Installation and Initial Setup (Common for SAN and NAS) 2.1 New Installation

4 When the installation process is complete, the [InstallShield Wizard Completed] screen appears. Click the [Finish] button to finish the installation.

End of procedure

• If all the following conditions apply to the environment in which ETERNUS vCenter Plug-in is installed, an internal error (such as STXE5900) may occur and ETERNUS vCenter Plug-in may not operate normally.

- VMware vSphere 6 is being used.- VMware vSphere 6 was installed by a user that is managed with the Active Directory domain

controller.• If ETERNUS vCenter Plug-in is not operating normally, perform the following procedure.

(1) Right-click the installation folder of ETERNUS vCenter Plug-in and open [Folder Properties].

(2) Select the security tab, click the [Edit] button, and then open [Folder Access Permissions].

(3) Click the [Add] button, and then open [Select Users, Computers, Service Accounts or Groups].

(4) Click [Locations], and then select a computer name.

If the initial setup fails, a Warning screen appears. In this case, the initial setup must be performed manually after installation. For details, refer to "Appendix A Frequent Inquiry Solutions (Common for SAN and NAS)" (page 168).



24

Chapter 2 Installation and Initial Setup (Common for SAN and NAS) 2.2 Operations Required After New Installation

2.2 Operations Required After New Installation

Perform the following operations after installing ETERNUS vCenter Plug-in.

2.2.1 Registering ETERNUS DX Storage Systems for Management

Before registering the information of the ETERNUS DX that is to be managed, the SSH connection of the targetETERNUS DX must be enabled. For the detailed procedure, refer to "ETERNUS Web GUI User’s Guide".To display the information of the ETERNUS DX onto vSphere Web Client, the information of the target ETERNUSDX must be registered in ETERNUS vCenter Plug-in. For the registration procedure, refer to "3.5 RegisteringETERNUS DX Storage Systems" (page 49).

2.3 Upgrading ETERNUS vCenter Plug-in

This procedure explains how to upgrade ETERNUS vCenter Plug-in in an environment in which an old versionof ETERNUS vCenter Plug-in is already installed and used. There is no need to change the environmentsettings again after upgrading ETERNUS vCenter Plug-in because the settings prior to upgrading are retainedeven after upgrading is complete. When upgrading to version 3.x or later, setting the installation folder to an area outside the Windows systemis required.However, upgrading from version 1.x of ETERNUS vCenter Plug-in cannot be performed. If version 1.x ofETERNUS vCenter Plug-in is installed, uninstall the old version before installing the new version.

(5) Click the [OK] button.

(6) Enter the following user name in the [Enter the object name to select] field, and then click [OK].NT SERVICE\vspherewebclientsvc

(7) Click the [OK] button.

(8) Give full control permission to the vspherewebclientsvc user, and then click [OK].

(9) Click the [OK] button to close [Folder Properties].

(10)Restart the vSphere Web Client service.

When the installation is complete, the vSphere Web Client service automatically restarts.After the service is restarted, the [FUJITSU ETERNUS DX] tab of ETERNUS vCenter Plug-in might not appear.If this tab is not displayed, wait a couple of minutes, and then log in again.



25

Chapter 2 Installation and Initial Setup (Common for SAN and NAS) 2.3 Upgrading ETERNUS vCenter Plug-in

When the installation is complete, the vSphere Web Client service automatically restarts.

Procedure

1 Extract the downloaded file.

2 Double-click the extracted ETERNUS vCenter Plug-in installer to start the wizard. Proceed with the installation according to the wizard.

3 When the installation process is complete, the [InstallShield Wizard Completed] screen appears. Click the [Finish] button to finish the installation.

End of procedure

If the environment settings prior to upgrading of ETERNUS vCenter Plug-in are not retained normally after upgrading is complete, a Warning screen appears.

In this case, changing the environment settings manually is required after upgrading of ETERNUS vCenter Plug-in is complete. For details, refer to "Appendix A Frequent Inquiry Solutions (Common for SAN and NAS)" (page 168).



26

Chapter 2 Installation and Initial Setup (Common for SAN and NAS) 2.4 Setting the User Privileges

2.4 Setting the User Privileges

Set the privileges to the vCenter Server user account in order to use the functions of ETERNUS vCenter Plug-in.For details about the roles that are created when installing ETERNUS vCenter Plug-in, refer to "Appendix BRole Control" (page 171). Perform the following procedure.

Procedure

1 Prepare a vCenter Server user account for using the functions of ETERNUS vCenter Plug-in.

2 After logging in to vSphere Web Client, select a vCenter Server object from the inventory tree on the left pane, and then select the [Permissions] tab under the [Manage] tab.



27


3 Click the "Add Permission" icon, and then click the [Add] button on the dialog that is dis-played.



28


4 Select the user account that was prepared in Step 1. Click [Add], and then click [OK].

5 Select a role from the "Assigned Role" list, and then click [OK].



29

Chapter 2 Installation and Initial Setup (Common for SAN and NAS) 2.5 Uninstallation

6 Log out from vSphere Web Client.When logging in, use the prepared user account.

End of procedure

2.5 Uninstallation

This section explains how to uninstall ETERNUS vCenter Plug-in.If the [User Account Control] screen appears during the uninstallation process, select [Allow] to continue theprocess.

Perform the following procedure.

Procedure

1 From [Programs and Features] in the Control Panel, select [ETERNUS vCenter Plug-in], and then click the [Uninstall] button.

2 Log in to vSphere Web Client.

3 Click the "Roles" icon in the vSphere Web Client home screen.

When uninstallation is complete, the vSphere Web Client service automatically restarts.

• For vCenter 5.x, the user login account must have the system administrator privileges.• For vCenter 6.x, the user login account must have the SSO administrator privileges.



30

Chapter 2 Installation and Initial Setup (Common for SAN and NAS) 2.5 Uninstallation

4 Select the following roles, and then click the "Role delete action" icon.

• ETERNUS vCp Administrator

• ETERNUS vCp Provision

• ETERNUS vCp Backup

• ETERNUS vCp Restore

• ETERNUS vCp Single Item Restore

• ETERNUS vCp Read-only

5 Click the [Yes] button.

6 Delete the unnecessary files in the installation folder.Manually delete the files if necessary.

End of procedure

If the deletion target roles are being used by a user account, change to a role other than the deletion target and then execute this step.



31

Chapter 3

SAN Functions

This chapter describes the configurations that are required prior to using the SAN functions and describes theoperating procedures of the SAN functions for ETERNUS vCenter Plug-in.For details about the items displayed in this chapter, refer to "Appendix C List of Displayed Items" (page 178).

3.1 Displaying Storage Information

This function is used to display various types of information for the ETERNUS DX storage systems in thevSphere Web Client screen. By selecting a VMware object from the inventory tree of vSphere Web Client, the[FUJITSU ETERNUS DX] tab is added under the [Manage] tab. To display the information of the ETERNUS DX,click the [FUJITSU ETERNUS DX] tab. The following three VMware objects are supported:

• Datastore• Virtual Machine• Host

3.1.1 Displaying Datastore Information

To display the information corresponding to datastores of the ETERNUS DX storage systems, perform thefollowing procedure:

Procedure

1 From the vCenter home screen of vSphere Web Client, select [vCenter Inventory Lists] [Datastores].

2 From the datastore list in the left pane, select the datastore that is assigned to the ETERNUS DX, and then click the [FUJITSU ETERNUS DX] tab under the [Manage] tab.



32

Chapter 3 SAN Functions 3.1 Displaying Storage Information

A list of the disks that configure the selected datastore is displayed in the [Datastore Detail] window.

3 From the [Datastore Detail] window, select a disk to display the detailed information of the disk in the [ETERNUS Details] window.

Eight portlets are displayed in the [ETERNUS Details] window.

• Volume Displays LUN specific information such as the name and the size of the selected disk.

• System InformationDisplays all of the ETERNUS DX information in which the selected disk belongs.

• RAID Group / Thin Provisioning PoolDisplays the information for the RAID group and the Thin Provisioning Pool in which the selected disk belongs.

• Storage ConditionDisplays the usages of the RAID group, the Thin Provisioning Pool, and the Snap Data Pool of the ETERNUS DX in which the selected disk belongs.

• PerformanceDisplays the performance information for the selected disk. To display the information, performance monitoring must be started with the [Start/Stop Perfmon] function.

• AdapterDisplays the information of the host bus adapter that recognizes the selected disk and the information of the ETERNUS DX port that is connected to the host bus adapter.



33


• WSV RAID GroupsDisplays the information of the RAID group that configures the Wide Striping Volume (WSV) when a WSV is selected.

• Flexible Tier PoolDisplays the Flexible Tier Pool information and also the Flexible Tier Sub Pool information when a Flexible Tier Volume (FTV) is selected.

End of procedure

3.1.2 Displaying Virtual Machine Information

To display the information corresponding to virtual machines of the ETERNUS DX storage systems, perform thefollowing procedure:

Procedure

1 From the vCenter home screen of vSphere Web Client, select [Inventory Tree] [Virtual Machines].

2 From the virtual machine list in the left pane, select the virtual machine that is assigned to the ETERNUS DX, and then click the [FUJITSU ETERNUS DX] tab under the [Manage] tab.

Click [Storage View] to display the list of disks that are used as hard disks for the selected virtualmachine in the [Virtual Disks] window.



34


3 From the [Virtual Disks] window, select a hard disk that is to be checked.The information of the disks that configure the hard disk is displayed in the [Datastore Detail] window.

4 From the [Datastore Detail] window, select a disk that is to be checked.The detailed information of the disk is displayed in the [ETERNUS Details] window.

End of procedure



35


3.1.3 Displaying Host Information

To display the information corresponding to the host of the ETERNUS DX storage systems, perform thefollowing procedure:

Procedure

1 From the vCenter home screen of vSphere Web Client, select [vCenter Inventory Lists] [Hosts].

2 From the host list in the left pane, select the host that uses the ETERNUS DX.

3 Click the [FUJITSU ETERNUS DX] tab under the [Manage] tab. The following three links are displayed under the [Storage View] menu: [Datastore], [Raw Device Mapping], and [Others]. Clicking each link changes the information that is displayed.

The displayed contents vary depending on the selected link.

■ Datastore

Item Details

Datastore Displays a list of the disks used as Datastore in the host selected in the inventory tree.

Raw Device Mapping Displays information of the disks used as Raw Device Mapping in the host selected in the inventory tree.

Others Displays information of the disks not used as either Datastore or Raw Device Mapping in the host selected in the inventory tree.



36


(1) A list of datastores used by the selected host is displayed in the [Assigned Disks] window.

(2) From the [Assigned Disks] window, select a datastore to display a list of disks that configure the selected datastore in the [Datastore Detail] window.

(3) From the [Datastore Detail] window, select a disk to display the detailed information of the disk in the [ETERNUS Details] window.

■ Raw Device Mapping

(1) A list of devices used as Raw Device Mapping in the selected host is displayed in the [Assigned Disks] window.

(2) From the [Assigned Disks] window, select a disk to display the detailed information of the disk in the [ETERNUS Details] window.



37


■ Others

(1) A list of devices not used as either Datastore or Raw Device Mapping in the selected host is displayed in the [Assigned Disks] window.

(2) From the [Assigned Disks] window, select a disk to display the detailed information of the disk in the [ETERNUS Details] window.

End of procedure

3.1.4 Notes

• In each list displayed by clicking the [FUJITSU ETERNUS DX] tab, only the information of disks on the ETERNUS DX is displayed. Other disk information is not displayed.

• No information is displayed in the [ETERNUS Details] window when using an ETERNUS DX that is not supported by ETERNUS vCenter Plug-in or a supported ETERNUS DX that is not registered as a management storage system.

• For datastore information display, the following message appears when a datastore that is used by multi-ple hosts is selected and the [FUJITSU ETERNUS DX] tab is clicked. Use [Datastore] of the host to display the information for the datastore that is used by multiple hosts.

STXE1017 NOTICE The datastore that is accessible from multiple hosts is not supported in this function.The information on this datastore can be confirmed with Host System.



38

Chapter 3 SAN Functions 3.2 Displaying Adapter Information

3.2 Displaying Adapter Information

This function is used to display adapter information for the host that is selected from the inventory tree, portinformation for the ETERNUS DX that is connected to the adapter, and information for recognized LUNs.Only the host is supported for the VMware object.

For details about the items displayed with this function, refer to "Appendix C List of Displayed Items" (page178).

To display adapter information, perform the following procedure:

Procedure


2 From the host list in the left pane, select the host that uses the ETERNUS DX, and then click the [FUJITSU ETERNUS DX] tab under the [Manage] tab.

3 Click the [Adapter] link to display the list of host bus adapters that are used for the selected host in the [Server Adapters] window.

4 Select an adapter in the [Server Adapters] window. The port information for the ETERNUS DX that is recognized by the adapter is displayed in the [StorageTargets] window.



39

Chapter 3 SAN Functions 3.2 Displaying Adapter Information

5 Select a port in the [Storage Targets] window. The list of LUNs that are assigned to the port is displayed in the [Storage LUNs] window.

End of procedure



40

Chapter 3 SAN Functions 3.3 Displaying Performance Monitoring and Performance Information

3.3 Displaying Performance Monitoring and Performance Information

This function is used to monitor ETERNUS DX performance and display its information.After performance monitoring is started, refer to the performance information and stop the performancemonitoring when monitoring is complete.

For details about the items displayed with this function, refer to "Appendix C List of Displayed Items" (page178).

3.3.1 Starting Performance Monitoring

This section explains how to start the performance monitoring. The following example is for the case whenthe datastore is selected from the inventory tree.

Procedure

1 From the vCenter Home screen of vSphere Web Client, select [vCenter Inventory Lists] [Datastores].

2 From the datastore list in the left pane, select the arbitrary datastore, and then click the [FUJITSU ETERNUS DX] tab under the [Manage] tab. Click the "Start/Stop Perfmon" icon.

The wizard is started and a list of the ETERNUS DX storage systems that are registered by theETERNUS DX registration function is displayed.


ETERNUS DX S2 series.



41


3 Select the radio button of the ETERNUS DX for which performance monitoring is started, select the performance monitoring interval from the pull-down menu, and then click the [Next] button.The ETERNUS DX collects and measures the performance information at the interval that is selected.

4 The following screen appears. Click the [Start] button to start performance monitoring.



42


5 The following screen appears after performance monitoring is started. Click the [Finish] button.

End of procedure

3.3.2 Displaying Performance Information

After performance monitoring is started, performance information can be displayed as a list or displayedindividually.

3.3.2.1 Displaying the Performance Information of All the LUNs in a List

Performance information for all of the LUNs that are recognized by the selected host can be displayed. Onlythe host is supported for the VMware object. This section explains how to check the performance information.

Procedure


2 From the host list in the left pane, select the host that uses the ETERNUS DX, and then click the [FUJITSU ETERNUS DX] tab under the [Manage] tab.



43


3 From the [Performance], click the [Host I/O] link or the [Advanced Copy I/O] link.A list of the LUNs that are used in the ETERNUS DX by the selected host and the LUN performanceinformation are displayed. To refresh the performance information, click the [Host I/O] link or the[Advanced Copy I/O] link again.

End of procedure

3.3.2.2 Displaying the Performance Information of Each LUN

Click the [Performance] portlet in the [ETERNUS Details] window to display I/O performance information foreach LUN. To refresh the performance information, click the "Refresh" icon (blue arrow) on the header of the[Performance] portlet.



44


The disk busy ratio is displayed on the [RAID Group] portlet or the [Thin Provisioning Pool] portlet in the[ETERNUS Details] window. To refresh the information, select any entries other than the target entry in awindow above the [ETERNUS Details] window, and then select the target entry again.

3.3.3 Stopping Performance Monitoring

This section explains how to stop performance monitoring.The following example is for cases when the host is selected from the inventory tree.

Procedure

1 From the vCenter Home screen of vSphere Web Client, select [vCenter Inventory Lists] [Hosts].

2 From the host list in the left pane, select the arbitrary host, and then click the [FUJITSU ETERNUS DX] tab under the [Manage] tab. Select [Storage View] [Datastore], and then click the "Start/Stop Perfmon" icon. The wizard is started and a list of the ETERNUS DX storage systems that are registered by the ETERNUSDX registration function is displayed.



45


3 Select the radio button of the ETERNUS DX for which performance monitoring is to be stopped, and then click the [Next] button.

4 The following screen appears. Click the [Stop] button to stop performance monitoring.



46


5 The following screen appears after performance monitoring is stopped. Click the [Finish] button.

End of procedure

For ETERNUS DX storage systems for which performance monitoring is started via ETERNUS SF Storage Cruiser, performance monitoring cannot be stopped via ETERNUS vCenter Plug-in.



47

Chapter 3 SAN Functions 3.4 Refreshing Displayed Information

3.4 Refreshing Displayed Information

ETERNUS vCenter Plug-in retains the information of vSphere and the ETERNUS DX storage systems to bemanaged as database. Selecting the [FUJITSU ETERNUS DX] tab displays information based on the database.Therefore, the contents displayed by selecting the [FUJITSU ETERNUS DX] tab may not be the latestinformation at the point.ETERNUS vCenter Plug-in communicates with vCenter Servers and the ETERNUS DX storage systems atintervals of 30 minutes and keeps the database up-to-date. Note that displayed information can be refreshedwhen a volume/datastore is created or deleted.

"Refresh" is the function to update the database manually. Using this function enables the latest informationto be displayed when the [FUJITSU ETERNUS DX] tab is selected. Use the following procedure:

Procedure

1 From the inventory tree in the left pane of vSphere Web Client, select any object from Datastores, Virtual Machines, or Hosts, and then select the [FUJITSU ETERNUS DX] tab under the [Manage] tab.

2 Click the "Refresh" icon.

The message "Now loading..." appears and the database is updated. This process may require a longperiod of time.

When the update process is complete, the latest information is displayed for the object selected fromthe inventory tree.

End of procedure



48

Chapter 3 SAN Functions 3.5 Registering ETERNUS DX Storage Systems

3.5 Registering ETERNUS DX Storage Systems

This function is used to register the information of the ETERNUS DX storage systems to ETERNUS vCenter Plug-in as the management target. Registration allows the information of the ETERNUS DX storage systems to bedisplayed in the [ETERNUS Details] window under the [FUJITSU ETERNUS DX] tab. Use the Register StorageWizard as an interface to register the information of the ETERNUS DX storage systems.

3.5.1 Starting the Register Storage Wizard

Procedure

1 From the inventory tree in the left pane of vSphere Web Client, select any object from Datastores, Virtual Machines, or Hosts, and then click the [FUJITSU ETERNUS DX] tab under the [Manage] tab.

2 Click the "Register Storage" icon to start the Register Storage Wizard.

End of procedure



49


3.5.2 Registering ETERNUS DX Storage Systems

Procedure

1 Start the Register Storage Wizard, select the [Add the ETERNUS disk storage system to the control of the ETERNUS vCenter Plug-in.] radio button, and then click the [Next] button.



50


2 Enter the "IP Address", "User ID", and "Password" of the ETERNUS DX to be newly registered, and click the [Add] button.

When registration is complete successfully, the ETERNUS DX is added to the list.

3 Click the [Finish] button to finish the wizard.

Use a user account with the Software role for registration.



51


4 Click the "Refresh" icon to update the displayed contents to the latest status.For details about Refresh, refer to "3.4 Refreshing Displayed Information" (page 48).

End of procedure

3.5.3 Unregistering ETERNUS DX Storage Systems

Procedure

1 Start the Register Storage Wizard, select the [Delete the ETERNUS disk storage system from the control of the ETERNUS vCenter Plug-in.] radio button, and then click the [Next] button.



52


2 Select the checkbox for the ETERNUS DX to be deleted and click the [Delete] button.Selection of multiple ETERNUS DX storage systems is available.

When unregistration is complete successfully, the target ETERNUS DX storage systems are deleted fromthe list.


End of procedure



53

Chapter 3 SAN Functions 3.6 Adding or Deleting Datastores/Volumes

3.6 Adding or Deleting Datastores/Volumes

This function is used to add volumes to a host or a cluster. Created volumes can automatically be convertedinto datastores. This function is also used to delete created datastores/volumes. To create or delete a volume, a RAID group or a Thin Provisioning Pool to which the volume is to be created orfrom which the volume is to be deleted must be registered in advance. Note that the supported VMware objects are host and cluster.

3.6.1 Registering Resources

Procedure

1 From the vCenter Home screen of vSphere Web Client, select [vCenter Inventory Lists] [Hosts] or [Clusters], and then right-click on the host or the cluster to display the menu bar.

• This function is not supported for the ETERNUS DX60 S2 Disk storage system.• Firmware version V10L40-0000 or later for the ETERNUS DX is required to use this function with the ETER-

NUS DX S2 series.• Only Fibre Channel and iSCSI are supported for interfaces between servers and ETERNUS DX storage sys-

tems.• This function is not supported for Flexible Tier Volumes (FTV) and Wide Striping Volumes (WSV). • A datastore/volume that is used in a virtual machine cannot be deleted with this function.• To use an iSCSI interface, "Network Port Binding" must be performed with vSphere Web Client. Refer to the

vSphere Web Client help for a detailed procedure on performing this action.



54


2 From the menu bar, select [All FUJITSU ETERNUS DX Actions] Register Resource], and then start the wizard.

3 Select the [Add the ETERNUS disk storage system resource.] radio button, and then click the [Next] button.



55


4 Enter all of the following items, and then click the [Add] button.

• IP AddressEnter the IP address of the ETERNUS DX in which the resource is registered.

• TypeSelect the resource type that is to be registered from "RAID Group" or "Thin Provisioning Pool".

• NameEnter the name of the resource that is to be registered.

When registration is successfully completed, the resource is added to the list.

Only resources with "evcp" as the first four letters of the name can be registered. Note that these letters are not case-sensitive.



56



End of procedure

3.6.2 Creating Volumes/Datastores

Procedure


After resources are registered by using this procedure, if a RAID group or Thin Provisioning Pool is deleted in ETERNUS Web GUI, delete the corresponding resource by using the wizard for registering resources.



57


2 From the menu bar, select [All FUJITSU ETERNUS DX Actions] [Create Datastore/LUN], and then start the wizard.

3 Select the radio button for one of the following modes, and then click the [Next] button.

• Create DatastoreLUNs are automatically changed to datastores after LUNs are created in the ETERNUS DX and theseLUNs are recognized as volumes by the selected host. Select the [VMFS] radio button.

• Create LUN LUNs are recognized as volumes by the selected host after LUNs are created in the ETERNUS DX.



58


4 Select the radio button of the ETERNUS DX in which the volume is to be created, and then click the [Next] button.

5 The path information between the selected host and the ETERNUS DX is displayed. If [Clusters] is selected to start the wizard, the path information between all of the hosts that belong to the cluster and the ETERNUS DX is displayed. Select the path that is to be used to create a volume, and then click the [Next] button.



59


6 Enter all of the following items, and then click the [Next] button.

• NameEnter the name of the volume that is to be created.

• CapacityEnter the size of the volume that is to be created.

• Start Host LUNsEnter the number for the first volume. Unused numbers after the first volume number that is specified are allocated in order for created volumes.

• TypeSelect the type of the volume that is to be created.

• Encryption by CMSelect "On" or "Off" for [Encryption by CM] only if input is available.

• Number of VolumesEnter the number of volumes in the [Number of Volumes] field for the RAID group or the Thin Provisioning Pool where the volumes are to be created.



60


7 The entered information is displayed. After making sure that the entered information is correct, select the [Please refresh the view of ETERNUS vCenter Plug-in right now.] checkbox in the [Refresh option] field if necessary, and then click the [Add] button.

If the registration is complete normally, the information of the created volume is displayed.

• An entered volume name is also used for both the volume name and the datastore name that are managed by the ETERNUS DX.

• If multiple volumes are created by a single operation, the entered name and the suffix "x" (the serial number starting from x: 0) are automatically assigned to each volume.

- Example The entered volume name: StandardVolume (14 letters) The created volume names: StandardVolume0, StandardVolume1, etc.

• If the total number of characters including the suffix "x" for the volume name exceeds 16, the excess letters are omitted and "~x" is assigned at the end of the name.

- ExampleThe entered volume name: Standard_Volume0 (16 letters) The created volume names: Standard_Volum~0, Standard_Volum~1, etc.

• From 1 to 16 alphanumeric characters, symbols, and spaces can be entered in the [Name] field. Note that the following symbols cannot be used:

- Comma (,)- Question mark (?)

If "Create Datastore" is selected in Step 3, the following symbols cannot be used:- Slash (/)- Backslash (\)- Percent (%)- A space that is used as the first or the last character

• If a decimal number is entered in the [Capacity] field, this number is automatically rounded to the nearest whole number.

• For details on other field requirements, refer to the ETERNUS Web GUI manual or help.



61



End of procedure

3.6.3 Deleting Volumes/Datastores

Procedure


If the [Cancel] button or the [X] button is clicked during the process of creating volumes/datastores after clicking the [Add] button, the wizard finishes but the volumes/datastores continue to be created.



62


2 From the menu bar, select [All FUJITSU ETERNUS DX Actions] [Delete Datastore/LUN], and then start the wizard.

A list of the datastores/volumes that are recognized by the selected host is displayed. If [Clusters] isselected to start the wizard, a list of the datastores/volumes that are recognized by all of the hosts thatbelong to the cluster is displayed.Letters in red indicate the datastores/volumes that are recognized by multiple hosts. Letters in grayindicate any datastores/volumes that cannot be deleted.

3 Select the datastore/volume that is to be deleted from the deletable datastores/volumes, and then click the [Next] button.



63


4 The selected information is displayed. After making sure that the selected information is correct, select the [Please refresh the view of ETERNUS vCenter Plug-in right now.] checkbox in the [Refresh option] field if necessary, and then click the [Delete] button.

When the deletion is complete normally, the information of the deleted datastores/volumes isdisplayed.

If the [Cancel] button or the [X] button is clicked during the process of deleting volumes/datastores after clicking the [Delete] button, the wizard finishes but the volumes/datastores continue to be deleted.



64



End of procedure

3.6.4 Unregistering Resources

Procedure




65


2 From the menu bar, select [All FUJITSU ETERNUS DX Actions] [Register Resource], and then start the wizard.

3 Select the [Delete the ETERNUS disk storage system resource.] radio button, and then click the [Next] button.



66


4 Select the checkbox of the resource that is to be deleted, and then click the [Delete] button.Multiple resources can be selected.

When the cancellation of the registration is complete, the resource is deleted from the list.


End of procedure

• A resource that is unregistered from ETERNUS vCenter Plug-in is not deleted from the ETERNUS DX.• Use ETERNUS Web GUI to delete resources from the ETERNUS DX. For more details, refer to "ETERNUS Web

GUI User’s Guide".



67


3.6.5 Points to Note

This section describes points to note when adding datastores/volumes in an environment in which volumesare shared in a cluster configuration. For more details about the host groups, the port groups, and the LUN groups that are used in this section,refer to "ETERNUS Web GUI User’s Guide".

3.6.5.1 When LUN Groups Are Shared

For configurations in which multiple hosts share the same LUN group as shown in the example below, refer to"3.6.2 Creating Volumes/Datastores" (page 57) and select LUN group in which a volume or a datastore is cre-ated.If only one of the hosts is selected, the volumes are automatically recognized by the other host.

• Host 1Host group: HG 1Port group: PG 1LUN group: LG 1

• Host 2 Host Group: HG 2Port group: PG 2 LUN group: LG 1

3.6.5.2 When Different LUN Groups Are Used

This section provides information about a configuration in which multiple hosts each use different LUN groupsand when some volumes are shared between these LUN groups as shown below.

• Host 1Host group: HG 1Port group: PG 1LUN group: LG 1 (LUN 1, 2, 3, 6)

• Host 2Host group: HG 2Port group: PG 2LUN group: LG 2 (LUN 1, 2, 3, 4, 5)

■ When adding a new local volume

Refer to "3.6.2 Creating Volumes/Datastores" (page 57) and select LUN group in which a volume or a datastoreis created.

■ When adding a new volume that is to be shared

Refer to "3.6.2 Creating Volumes/Datastores" (page 57), and then select [Clusters] to start the wizard. Selectall the LUN groups in which a volume or a datastore is created.



68

Chapter 4

NAS Functions

This chapter describes the configurations that are required prior to using the NAS functions and describes theoperating procedures of the NAS functions for ETERNUS vCenter Plug-in.For details about the items displayed in this chapter, refer to "Appendix C List of Displayed Items" (page 178).

4.1 Preliminary Preparation for Using the NAS Functions

This section describes the preliminary preparation that is required for using the NAS functions of ETERNUSvCenter Plug-in.

4.1.1 Preliminary Settings by ETERNUS DX Storage Systems

This section describes the settings in ETERNUS DX storage systems that are required for using the NASfunctions of ETERNUS vCenter Plug-in.

■ Enabling the unified storage function

To use all NAS-related functions of ETERNUS vCenter Plug-in, enable the unified storage function of theETERNUS DX storage systems that are to be managed. If the unified storage function is disabled, perform theunified upgrade. The unified upgrade is a maintenance operation that can be performed by maintenanceengineers with the "Maintenance Operation" role. If the unified storage function is already enabled, skip thisoperation.

■ Creating a Thin Provisioning Pool (TPP)

Create a TPP that is used to create NAS volumes that are created by ETERNUS vCenter Plug-in. The first fourcharacters of the TPP name must be "evcp". The characters are not case-sensitive. For details about theoperating procedure, refer to "General Settings" in "ETERNUS DX Disk storage system Configuration Guide(NAS)".

■ Changing the NAS interface settings

Set NAS interfaces of the ETERNUS DX that is specified by ETERNUS vCenter Plug-in as the destination to createNFS datastores. For the operation procedure, refer to "NAS Interface Settings" in "ETERNUS DX Disk storage sys-tem Configuration Guide (NAS)". In addition, ports must be specified to use NAS interfaces.



69

Chapter 4　NAS Functions 4.1　Preliminary Preparation for Using the NAS Functions

■ Creating a RAID group

When the datastore backup, virtual machine backup, or virtual machine restore of ETERNUS vCenter Plug-in isused, a RAID group for saving NAS snapshots must be created. The first four characters of the RAID groupname must be "evcp". The characters are not case-sensitive. For details about the operating procedure, referto "RAID Group Creation" in "ETERNUS DX Disk storage system Configuration Guide (Basic)". If the backup/restore function is not used, skip this operation.

■ Creating a copy data destination volume (SDPV)

In the RAID group for saving NAS snapshots, create an SDPV that is an expansion area of the generationmanagement volume (SDV). For details about the operating procedure, refer to "Copy Data DestinationVolume (SDPV) Creation" in "ETERNUS DX Disk storage system Configuration Guide (Basic)". If the backup/restore function is not used, skip this operation.

■ Specifying the copy table size

Specify the copy table size of the ETERNUS DX. For details about the operating procedure, refer to "Copy TableSize Settings" in "ETERNUS DX Disk storage system Configuration Guide (Basic)". If the copy table size isalready specified or the backup/restore function is not used, skip this operation.

4.1.2 Preliminary Settings for ETERNUS SF

In ETERNUS vCenter Plug-in, ETERNUS SF can be registered as a linked product. The link with the registeredETERNUS SF allows for a NAS volume backup within a single ETERNUS DX or between ETERNUS DX storagesystems.Perform the following preliminary settings to use ETERNUS SF as a linked product:

• Preliminary settings by ETERNUS SF- Preliminary settings for ETERNUS DX storage systems- Registering ETERNUS DX storage systems- Registering Advanced Copy licenses- Creating a Thin Provisioning Pool- Specifying the connection type of the Advanced Copy

• Preliminary settings by the vSphere Web Client server in which ETERNUS vCenter Plug-in is installed- Configuring network environment settings to connect to ETERNUS SF

If the NAS volume backup/restore function based on the link with ETERNUS SF is not used within a singleETERNUS DX or between ETERNUS DX storage systems, skip this operation.



70


4.1.2.1 Preliminary Settings by ETERNUS SF

■ Preliminary settings for ETERNUS DX storage systems

Perform the preliminary settings for ETERNUS DX storage systems to register ETERNUS DX storage systems inETERNUS SF. For details about the setting contents, refer to "ETERNUS Disk Storage System Configuration" of"NAS Management" in "ETERNUS SF Operation Guide". If the ETERNUS DX storage systems are alreadyregistered to ETERNUS SF, skip this operation.

■ Registering ETERNUS DX storage systems

Register the ETERNUS DX storage systems that are used in ETERNUS vCenter Plug-in as devices that are man-aged by ETERNUS SF. For details about the setting contents, refer to "Registering ETERNUS DX StorageSystems" of "Preliminary Settings for the Operation Management Server" in "Preliminary Settings" of "NASManagement" in "ETERNUS SF Operation Guide". If the ETERNUS DX storage systems are already registered toETERNUS SF, skip this operation.

■ Registering Advanced Copy licenses

Register licenses for allowing the NAS operation of the ETERNUS DX storage systems. For details about thelicense registration procedure, refer to "License Registration" of "Prior Configuration of OperationManagement Server" in "Required Setup Configuration" of "NAS Management" in "ETERNUS SF OperationGuide". If the licenses are already registered, skip this operation.

■ Creating a Thin Provisioning Pool

Create a Thin Provisioning Pool that is to be the creation destination of NAS backup volumes for backupswithin a single ETERNUS DX storage system or between ETERNUS DX storage systems. For details about theprocedure for creating a Thin Provisioning Pool, refer to "Create Thin Provisioning Pool" in "ETERNUS SF WebConsole Guide". If the Thin Provisioning Pool for NAS backup volumes is already created, skip this operation.

■ Specifying the connection type of the Advanced Copy

Specify the connection type of the Advanced Copy to define backup settings for NAS volumes. For detailsabout the procedure for specifying the connection type, refer to "Configure Connection Type for ETERNUS DiskStorage System" in "ETERNUS SF Web Console Guide". If the connection type is already specified, skip thisoperation.

The preliminary settings for ETERNUS DX storage systems must be performed from ETERNUS SF Web Console for all the ETERNUS DX storage systems that are used in ETERNUS vCenter Plug-in.

• Configuring a NAS file system requires an ETERNUS SF Storage Cruiser Standard Edition license.• Backing up a NAS volume requires an ETERNUS SF AdvancedCopy Manager Standard Edition license.

For the copy control type, select [Access through volumes] or [Access through network].



71


4.1.2.2 Preliminary Settings by the vSphere Web Client Server

■ Configuring network environment settings to connect to ETERNUS SF

From the vSphere Web Client server in which ETERNUS vCenter Plug-in is installed, configure the networkenvironment for running the AdvancedCopy Manager CCM command of the ETERNUS SF Manager throughPowerShell or SSH.

● When using PowerShell (Windows)

Procedure

1 Specify the execution policy of Windows PowerShell scripts.On the vSphere Web Client server, start PowerShell using "Run as administrator", and then run thefollowing command.

2 Enable the remoting feature.In the ETERNUS SF Manager, start PowerShell using "Run as administrator", and then run thefollowing command.

3 Use the PowerShell remoting feature to perform one of the following procedures depending on whether the HTTP transport is used or the HTTPS transport is used.

- When using the HTTP transportOn the vSphere Web Client server, add the ETERNUS SF Manager to the trusted hosts(TrustedHosts). On the vSphere Web Client server, start PowerShell using "Run as administrator",and then run the following command.

- When using the HTTPS transportConfigure the ETERNUS SF Manager for the HTTPS transport.

End of procedure

● When using SSH (Windows, Linux, or Solaris)

Configure the network environment so that the ETERNUS SF Manager can accept SSH connections.

Set-ExecutionPolicy RemoteSigned

Enable-PSRemoting

Set-Item wsman:localhost\client\trustedhosts <IP_address or host_name_of_the_ ETERNUS_SF_Manager>

When setting up a firewall between the vSphere Web Client server in which ETERNUS vCenter Plug-in is installed and the ETERNUS SF Manager, configure the settings to bypass the firewall.



72


4.1.3 Preliminary Settings by vCenter Server

Register the information on the vCenter Server that is managed by ETERNUS vCenter Plug-in. Configure thefollowing preliminary settings.

■ Registering the credential information for vCenter Server

To acquire the vCenter Server information that is displayed by ETERNUS vCenter Plug-in, register the credentialinformation (IP address, account, and password) for vCenter Server. The credential information is registeredduring the installation procedure of ETERNUS vCenter Plug-in. In addition, use the "evcpConfig" command toregister multiple sets of vCenter Server information. For details, refer to "6.3 evcpConfig Command" (page165).



73

Chapter 4　NAS Functions 4.2　Initial Setup in ETERNUS vCenter Plug-in

4.2 Initial Setup in ETERNUS vCenter Plug-in

This section describes the initial setup that is required for using the NAS functions of ETERNUS vCenter Plug-in.

4.2.1 Registering, Deleting, or Updating Storage Systems

This section describes the procedure for registering, deleting, or updating the ETERNUS DX that is managed byETERNUS vCenter Plug-in.

■ Registering storage systems

Procedure

1 In the [Home] screen of vSphere Web Client, click the "FUJITSU ETERNUS DX" icon.

2 Click the "Register Storage" icon to start the wizard for registering ETERNUS DX storage systems.



74


3 Select [Add the ETERNUS disk storage system to the control of the ETERNUS vCenter Plug-in.] and click the [Next] button.

4 Enter the management IP address (IPv4/IPv6), user account, and password of the ETERNUS DX to be registered, and then click the [Add] button.

Use a user account with the Software role for registration.



75


5 Check that the ETERNUS DX is registered.

■ When registering another ETERNUS DX

Click the [Continue] button. The screen display returns to the screen in Step 3.

■ When finishing the registration

Click the [Finish] button.

6 Click the "Refresh" icon to update the displayed contents to the latest status.For details, refer to "3.4 Refreshing Displayed Information" (page 48).

End of procedure

One ETERNUS DX cannot be managed by multiple vSphere Web Clients.



76


■ Deleting storage systems

Procedure


2 Click the "Register Storage" icon to start the wizard for registering ETERNUS DX storage systems.

3 Select [Delete the ETERNUS disk storage system from the control of the ETERNUS vCenter Plug-in.] and click the [Next] button.



77


4 Select the ETERNUS DX to be deleted from among the ETERNUS DX storage systems to be managed, and then click the [Delete] button.

5 Check that the ETERNUS DX is deleted.

■ When deleting another ETERNUS DX

Click the [Continue] button. The screen display returns to the screen in Step 3.

■ When finishing the deletion

Click the [Finish] button.

End of procedure

■ Updating storage systems

To update the information on the ETERNUS DX, register new storage information after deleting the existingstorage system.



78


4.2.2 Registering, Deleting, or Updating Resources

This section describes the procedure for registering, deleting, or updating a resource (RAID group or ThinProvisioning Pool) that is managed by ETERNUS vCenter Plug-in.

■ Registering resources

Procedure


2 In the [FUJITSU ETERNUS DX] screen, select the [Resources] tab to display [Resource Pool Information]. Click the "Register Resource" icon to start the wizard for registering resources.



79


3 Select [Add the ETERNUS disk storage system resource.] and click the [Next] button.

4 Enter the management IP address (IPv4/IPv6) of the ETERNUS DX to which the resource is registered, resource type (RAID group or Thin Provisioning Pool), and resource name,and then click the [Add] button.

The first four characters of the resource name must be "evcp". The characters are not case-sensitive.



80


5 Check that the resource is registered, and then click the [Finish] button.

End of procedure

After resources are registered, if a RAID group or Thin Provisioning Pool is deleted in ETERNUS Web GUI, delete the corresponding resource by using the wizard for registering resources.



81


■ Deleting resources

Procedure


2 In the [FUJITSU ETERNUS DX] screen, select the [Resources] tab to display [Resource Pool Information]. Click the "Register Resource" icon to start the wizard for registering resources.



82


3 Select [Delete the ETERNUS disk storage system resource.] and click the [Next] button.

4 Select the resource to be deleted from among the resources to be managed, and then click the [Delete] button.



83


5 Check that the resource is deleted, and then click the [Finish] button.

End of procedure

■ Updating resources

To update the information on the resource, register new resource information after deleting the existingresource.

4.2.3 Registering, Changing, or Deleting ETERNUS SF Connection Information

This section describes the procedure for registering, changing, or deleting the ETERNUS SF connectioninformation for using the NAS volume backup function within a single ETERNUS DX or between ETERNUS DXstorage systems.If the NAS volume backup function is not used within a single ETERNUS DX or between ETERNUS DX storagesystems, skip this operation.

The resource that is deleted by ETERNUS vCenter Plug-in is not deleted from the ETERNUS DX.To delete a resource from the ETERNUS DX, use ETERNUS Web GUI. For details about the procedure, refer to "ETERNUS Web GUI User's Guide".

To register or change the ETERNUS SF connection information, configure the settings for using the ETERNUS SF in advance. For details about the settings, refer to "4.1.2 Preliminary Settings for ETERNUS SF" (page 70).



84


■ Registering ETERNUS SF connection information

Procedure


2 In the [FUJITSU ETERNUS DX] screen, select the [ETERNUS SF] tab to display [ETERNUS SF Connection Information]. Click the "ETERNUS SF Connection Information Addition" icon to start the wizard for registering the ETERNUS SF Connection Information.

3 Enter all of the following items, and then click the [Add] button.

• IP AddressEnter the IP address (IPv4/IPv6) of the link destination ETERNUS SF.

• User IDEnter the user ID.

• PasswordEnter the password for the user.

• ETERNUS SF ManagerSelect [Windows], [Linux], or [Solaris] for the OS for the ETERNUS SF Manager.

• MethodSelect [PowerShell] or [SSH] for the execution method. When the OS for the ETERNUS SF Manager isLinux or Solaris, only [SSH] can be selected.

• ProtocolSelect [http] or [https] for the communication protocol. The communication protocol can bespecified only when the execution method is PowerShell.



85


• Port No.Enter the port number that is used for the connection to ETERNUS SF.

• AdvancedCopy Manager CCM Command Path (bin Directory)Enter the absolute path of the bin directory that stores the AdvancedCopy Manager CCM commandthat is installed in the ETERNUS SF Manager.

• Operation MethodSelect the operation method. When no backup between ETERNUS DX storage systems is created,select [Not Set]. When backups between ETERNUS DX storage systems are created, select [DataProtection] or [Stand-by].

• Inter-box Backup Script PathWhen backups between ETERNUS DX storage systems are created for data protection operation,enter the absolute path to the sample scripts for data protection operation. When backups betweenETERNUS DX storage systems are created for standby operation, enter the absolute path to the sam-ple scripts for standby operation. For details about the sample scripts for data protection operationand for standby operation, refer to "Automation of Operation" in "ETERNUS SF AdvancedCopyManager Operation Guide for Copy Control Module".

• Check if the preliminary settings for ETERNUS SF are already configured. For details about the preliminary settings, refer to "4.1.2 Preliminary Settings for ETERNUS SF" (page 70).

• An account with the execution privileges for the AdvancedCopy Manager CCM command of ETERNUS SF must be specified. For ETERNUS SF in Linux or Solaris, specify the root (superuser).

• For the script that is to be specified in the backup script path between ETERNUS DX storage systems, specify the one that was placed when ETERNUS SF was installed.



86


4 Click the [Finish] button.

End of procedure

■ Changing ETERNUS SF connection information

Procedure




87


2 In the [FUJITSU ETERNUS DX] screen, select the [ETERNUS SF] tab to display [ETERNUS SF Connection Information]. Click the "ETERNUS SF Connection Information Modification" icon to start the wizard for changing the ETERNUS SF Connection Information.

3 Enter the information to be changed, and then click the [Modify] button.

Check that the preliminary settings for ETERNUS SF are already configured. For details about the settings, refer to "4.1.2 Preliminary Settings for ETERNUS SF" (page 70).

For details about the information to be entered, refer to "Registering ETERNUS SF connection information" (page 85).



88



End of procedure

■ Deleting ETERNUS SF connection information

Procedure




89


2 In the [FUJITSU ETERNUS DX] screen, select the [ETERNUS SF] tab to display [ETERNUS SF Connection Information]. Click the "ETERNUS SF Connection Information Deletion" icon to start the wizard for deleting the ETERNUS SF Connection Information.

3 Check the ETERNUS SF information to be deleted. If the contents are correct, click the [Delete] button.

• If a schedule for creating a NAS backup within a single ETERNUS DX or between ETERNUS DX storage systems exists, [Modify Schedule] to change the schedule setting to [Do Not Create NAS Backup], and then perform the procedure of "Deleting ETERNUS SF connection information".

• If the registered ETERNUS SF is deleted, a NAS backup based on the link with ETERNUS SF is not performed. If a schedule for creating a NAS backup exists, the execution of the schedule or the immediate execution of the schedule fails.

• Even if the registration of ETERNUS SF is deleted from ETERNUS vCenter Plug-in, the NAS backup settings are not deleted from ETERNUS SF. For details about the procedure for deleting the NAS backup settings from ETERNUS SF, refer to "Delete NAS Backup Settings" in "ETERNUS SF Web Console Guide".



90



End of procedure



91

Chapter 4　NAS Functions 4.3　Creating Datastores and Virtual Machines

4.3 Creating Datastores and Virtual Machines

This function is used to create an NFS datastore, create a NAS volume, and configure the allowed host settingsfor an NFS datastore. In addition, when an NFS datastore is created, the backup of the datastore and virtualmachines can be set up. This function requires the following preliminary settings.

• Creation of a NAS volumeCreate a Thin Provisioning Pool in the ETERNUS DX in which the NAS volume is to be created.

• When setting up backupCreate a RAID group in which a NAS snapshot is to be created.

• When performing a NAS backup based on the link with ETERNUS SFPerform the preliminary settings for the ETERNUS SF that is linked.

4.3.1 Creating Datastores or LUNs

This section describes the procedure for creating an NFS datastore or new NAS volume.

Procedure

1 From the vCenter Home screen of vSphere Web Client, select [vCenter Inventory Lists] — [Hosts] or [Clusters].

This function is not supported for Flexible Tier Volumes (FTV) and Wide Striping Volumes (WSV).

This function cannot be used to create only a NAS volume.



92


2 Right-click on the host or cluster in which the NFS datastore is created to display the menu bar. Select [All FUJITSU ETERNUS DX Actions] — [Create Datastore/LUN] to start the wizard for creating a datastore/LUN.

3 Select [Create Datastore] — [NFS], and then click the [Next] button.



93


4 Select the ETERNUS DX for which a NAS volume and an NFS datastore are to be created, and then click the [Next] button.

5 Select the NAS interface of the ETERNUS DX that is used to mount the NFS datastore, and then click the [Next] button.



94


6 Select [New] or [Existing] for the NAS volume in which the NFS datastore is to be created.

■ When creating a new NAS volumeEnter all of the following items, and then click the [Next] button.

• NameEnter the NAS volume name.

• CapacityEnter the capacity of the NAS volume.

• Block SizeSelect [8KB], [32KB], or [256KB] for the file system block size.

• Selection of the Thin Provisioning Pool in which the NAS volume is createdSelect the Thin Provisioning Pool in which the NAS volume is to be created.



95


■ When using an existing NAS volumeSelect the NAS volume in which the NFS datastore is to be created, and then click the [Next] button.

• From 1 to 42 alphanumeric characters and symbols can be entered in the [Name] field. Note that the following characters and symbols cannot be used:

- Space- Following symbols:

"\", "/", ":", "*", "?", """, "<", ">", "|", "=", ",", ";"- $bak that is used as the last character

• A value from 400GB to 128TB can be entered in the [Capacity] field. If a decimal number is entered, this number is automatically rounded to the nearest whole number.

• The capacity of the created NAS volume cannot be reduced.• The maximum NAS volume capacity and the maximum file size vary depending on the value that

is specified for the block size. For details, refer to "Block Size" in "ETERNUS DX Disk storage system Configuration Guide (NAS)".

• If [8KB] is selected for the block size, in order to perform a backup with ETERNUS vCenter Plug-in or acquire snapshots of virtual machines manually, the hard disk capacity of the virtual machine must be set to 1016GB or less.



96


7 Create the NFS datastore. Specify [Datastore Name] and [NFS Allowed Host], and then click the [Next] button.

• From 1 to 42 alphanumeric characters, symbols, and multi-byte characters can be entered in the [Datastore Name] field. Note that the following characters and symbols cannot be used regardless of case:

- Space- Following symbols:

"\", "/", ":", "*", "?", """, "<", ">", "|", "=", ",", ";", "[", "]", "%", "+"- @GMT at the beginning- $bak that is used as the last character- .snap- global- homes- printers- ipc$- . (one period)- .. (two periods)

• An IP address (IPv4/IPv6) or FQDN format string can be entered in the [NFS Allowed Host] field.• Multiple NFS allowed hosts that are separated by a comma (,) can be specified. Up to 1023

characters can be entered.• Subnet specification can be used to specify an IP address in the [NFS Allowed Host] field.• If the [NFS Allowed Host] field is blank, all hosts are allowed.



97


8 Set the schedule for backing up the NFS datastore.

Enter all of the following items, and then click the [Next] button.

• Execution PeriodSelect one of the following execution periods:

- Hourly- Daily- Weekly- Monthly- Once

• Schedule NameEnter the schedule name.

• Number of Snapshot GenerationsEnter the number of snapshot generations.

• Schedule Effective DateSet the date when the schedule is enabled.

- If [Hourly] is specified for [Execution Period], set the following items:• Start Time• Interval

- If [Daily] is specified for [Execution Period], set the following item:• Start Time

- If [Weekly] is specified for [Execution Period], set the following items:• Day of the Week (One or More)• Start Time

- If [Monthly] is specified for [Execution Period], set the following items:• Start Date• Start Time

- If [Once] is specified for [Execution Period], set the following item:• Start Time

• Virtual Machine Snapshot OptionSelect one of the following options to acquire snapshots of virtual machines.

- Snapshot the virtual machine's memorySelect this option to acquire snapshots of the virtual machine memory.

- Quiesce guest file system (Needs VMware Tools installed)Select this option to acquire snapshots of the virtual machine's file system that is not in use.

• Snapshot Destination PoolSelect the RAID group in which NAS snapshots are to be created.

To set a schedule, register a RAID group in which a NAS snapshot is to be created.

If a schedule is set after the NFS datastore is created, select [Skip] and click the [Next] button.



98


• From 1 to 64 alphanumeric characters and symbols can be entered in the [Schedule Name] field. Note that the following characters and symbols cannot be used:

- Space- Symbols except for the following ones:

"-", "_", ".", ":"• The maximum number of snapshot generations varies depending on the models of ETERNUS DX

storage systems. For details, refer to "Snapshot" in "ETERNUS DX Disk storage system Configuration Guide (NAS)".

• If the number of snapshot generations is set to "0", no NAS snapshot is acquired.• Schedule settings cannot be changed on this screen. If a schedule is already set for the selected

NAS volume, the setting contents are displayed.• If the number of NAS snapshots that are acquired reaches the specified number of generations,

the oldest NAS snapshot is automatically deleted and a new NAS snapshot is acquired.• When snapshots of virtual machines are acquired, snapshots are acquired for all virtual machines

that are stored in the NAS volume in which the NFS datastore is created. If there are a large number of virtual machines, the execution of the schedule may take some time.

• When snapshots of the virtual machine’s memory are acquired, the execution of the schedule may take some time.

• To use the Quiesce guest file system, install VMware Tools in the virtual machines.



99


9 Set up the NAS backup. Select [Create NAS Backup] or [Do Not Create NAS Backup] for the NAS backup method.

■ When creating NAS backups within a single ETERNUS DXSelect [Create NAS Backup] — [Intra-box], and then click the [Next] button.

■ When creating NAS backups between ETERNUS DX storage systemsSelect [Create NAS Backup] — [Inter-box], and then click the [Next] button.

■ When not creating NAS backupsSelect [Do Not Create NAS Backup], and then click the [Next] button.

• To create a NAS backup, register the information on the ETERNUS SF that is linked.• If [Create NAS Backup] — [Intra-box] or [Inter-box] cannot be selected, perform [Modify Schedule]

after ETERNUS SF is registered.• NAS backup settings cannot be changed in this screen. If NAS backup is already set up for the

selected NAS volume, the backup settings are displayed.• If [Skip] is selected in Step 8, NAS backup cannot be set up. To set up NAS backup, click the [Back]

button. To skip the setup, click the [Next] button.



100


10 The entered information is displayed. After making sure that the entered information is correct, select the [Please refresh the view of ETERNUS vCenter Plug-in right now.] checkbox in the [Refresh option] field if necessary, and then click the [Add] button.




101


12 If [Create NAS Backup] was selected in Step 9, set up the NAS backup in ETERNUS SF Web Console.

■ When creating NAS backups within a single ETERNUS DXFrom ETERNUS SF Web Console, set up the NAS backup for the NAS volume in which the NFS datastore is stored. For details about the setup procedure, refer to "Set NAS Backup" in "ETERNUS SF Web Console Guide".

■ When creating NAS backups between ETERNUS DX storage systems

(1)From ETERNUS SF Web Console, set up the NAS backup for the NAS volume in which the NFS datastore is stored. For details about the setup procedure, refer to "Set NAS Backup" in "ETERNUS SF Web Console Guide".

(2)Create the environment for backup between ETERNUS DX storage systems according to the operation.For NAS volume backup/restore between ETERNUS DX storage systems, there are two types of operations: "data protection operation" and "standby operation". The environment for backup/restore between ETERNUS DX storage systems must be created according to the operation in advance. For the procedure for creating the environment, refer to the following references:

• For the data protection"Creation of Environment" of "Details of Data Protection Operation" in "ETERNUS SFAdvancedCopy Manager Operation Guide for Copy Control Module"

• For the standby operation"Creation of Environment" of "Details of Data Protection Operation" in "ETERNUS SFAdvancedCopy Manager Operation Guide for Copy Control Module"

If the NAS backup of the NAS volume is already set up, skip this operation.

• ETERNUS SF must be registered in advance. For the registration procedure, refer to "4.2.3 Registering, Changing, or Deleting ETERNUS SF Connection Information" (page 84).

• After a schedule is created, a NAS backup (within a single ETERNUS DX) is not acquired immediately. A NAS backup (within a single ETERNUS DX) is acquired at the start time that is specified when the schedule was created. To acquire a NAS backup (within a single ETERNUS DX) immediately, perform the procedure for executing the schedule immediately.

• The result of acquiring a NAS backup can be checked from the Task Console of vSphere Web Client. If acquiring a NAS backup fails, check the status from ETERNUS SF Web Console and remove the cause of the error. A backup is acquired when the schedule is executed next time.

• Even if the schedule is completed in ETERNUS vCenter Plug-in, the acquisition of a NAS backup may not be completed. Check the process status of the NAS backup acquisition from ETERNUS SF Web Console.

If the NAS backup of the NAS volume is already set up, skip this operation.



102


End of procedure

4.3.2 Changing NFS Allowed Hosts for a Datastore

This section describes the procedure for changing the hosts that are allowed to access an NFS datastore.

Procedure

1 From the vCenter Home screen of vSphere Web Client, select [vCenter Inventory Lists] — [Datastores], and then right-click on the NFS datastore for which NFS allowed hosts are to be changed to display the menu bar.

If the environment for NAS volume backup between ETERNUS DX storage systems is already configured, skip this operation.

• ETERNUS SF must be registered in advance. For the registration procedure, refer to "4.2.3 Registering, Changing, or Deleting ETERNUS SF Connection Information" (page 84).

• After a schedule is created, a backup between ETERNUS DX storage systems is not acquired immediately. A backup between ETERNUS DX storage systems is acquired at the start time that is specified when the schedule is created. To immediately acquire a backup between ETERNUS DX storage systems, perform the procedure in "4.4.4 Executing a Schedule Immediately" (page 117).

• When a backup between ETERNUS DX storage systems is acquired, a NAS backup within a single ETERNUS DX is created at the same time.

• The result of acquiring a backup between ETERNUS DX storage systems can be checked from the Task Console of vSphere Web Client. If acquiring a backup between ETERNUS DX storage systems fails, check the status from ETERNUS SF Web Console and address the cause of the error. A backup is acquired when the schedule is executed next time.

Check that no powered-on virtual machine exists on the datastore for which the NFS allowed hosts are to be changed. If a host on which a powered-on virtual machine is operating is removed from the allowed hosts, the virtual machine is forcibly powered off.



103


2 From the menu bar, select [All FUJITSU ETERNUS DX Actions] — [Modify NFS Allowed Host] to start the wizard for changing NFS allowed hosts for a datastore.

3 In the [NFS Allowed Host] field, enter all the hosts that are to be allowed to access the datastore, and then click the [Next] button.

• An IP address (IPv4/IPv6) or FQDN format string can be entered in the [NFS Allowed Host] field.• Multiple NFS allowed hosts that are separated by a comma (,) can be specified. Up to 1023

characters can be entered.• Subnet specification can be used to specify an IP address in the [NFS Allowed Host] field.• If the [NFS Allowed Host] field is blank, all hosts are allowed.• Specify all hosts that include the allowed hosts that are already specified.



104


4 The entered information is displayed. After making sure that the entered information is correct, select the [Please refresh the view of ETERNUS vCenter Plug-in right now.] checkbox in the [Refresh option] field if necessary, and then click the [Modify] button.


End of procedure

4.3.3 Creating Virtual Machines

For details about the procedure for creating a virtual machine, refer to the vSphere Web Client help.

For a virtual machine that consists of multiple datastores, there are some restrictions on virtual machine restore and single item restore. For details, refer to "4.5 Restoring a Virtual Machine" (page 123).



105

Chapter 4　NAS Functions 4.4　Backing Up Datastores and Virtual Machines

4.4 Backing Up Datastores and Virtual Machines

This function is used to back up NFS datastores and virtual machines.To perform backup, set a schedule.

4.4.1 Creating a Schedule

This section describes the procedure for creating a schedule. The following example is for the case when thedatastore is selected from the inventory tree.

Procedure

1 From the vCenter Home screen of vSphere Web Client, select [vCenter Inventory Lists] — [Datastores], and then right-click on the datastore to display the menu bar.

• For a NAS volume, one schedule can be set.• When multiple NFS datastores exist in a NAS volume, the schedule is applied to all the NFS datastores.• Backup is performed on a NAS volume basis. When a virtual machine restore or single item restore is

performed, the configuration file of the virtual machine to be restored must exist on the same NAS volume. For details, refer to "4.5 Restoring a Virtual Machine" (page 123).

• If the NAS volume capacity is expanded by [Expand Volume] of the ETERNUS DX, the execution of the schedule that is already set in ETERNUS vCenter Plug-in fails. In that case, create the schedule again.

• When a schedule is executed during a firmware update of the ETERNUS DX, the execution of the schedule may fail. Temporarily disable the schedule before updating the firmware.

• If the ETERNUS DX is in a state of error, restore the ETERNUS DX.• If the vSphere Web Client screen is not displayed properly, click the [Refresh] button to reacquire the

information.

• If the schedule is executed for the NFS datastore under the NAS volume that stores a virtual machine for which [Restore Virtual Machine] or [Single Item Restore] is being performed, the execution of the schedule fails.

• If the schedule is being executed for another NFS datastore under the same NAS volume, the execution of the schedule fails.

• If NAS backup within a single ETERNUS DX or NAS backup between ETERNUS DX storage systems is set, the execution of the schedule may take some time.



106


2 From the menu bar, select [All FUJITSU ETERNUS DX Actions] — [Create Schedule] to start the wizard for creating a schedule.

3 Enter the setting contents of the schedule, and then click the [Next] button.

For details about the setting contents, refer to Step 8 (page 98) in "4.3.1 Creating Datastores or LUNs".

If [Number of Snapshot Generations] is set to "0", no NAS snapshot is acquired.



107


4 Select [Create NAS Backup] or [Do Not Create NAS Backup] for the NAS backup method, and then click the [Next] button.

5 The entered information is displayed. After making sure that the entered information is correct, select the [Please refresh the view of ETERNUS vCenter Plug-in right now.] checkbox in the [Refresh option] field if necessary, and then click the [Create] button.


If ETERNUS SF is not registered, the backup option cannot be set. For details, refer to "4.1.2 Preliminary Settings for ETERNUS SF" (page 70).



108



End of procedure



109


4.4.2 Changing a Schedule

This section describes the procedure for changing a schedule. The following example is for the case when thedatastore is selected from the inventory tree.

Procedure


2 From the menu bar, select [All FUJITSU ETERNUS DX Actions] — [Modify Schedule] to start the wizard for changing a schedule.

• If the schedule is for the NFS datastore under the NAS volume that stores a virtual machine for which [Restore Virtual Machine] or [Single Item Restore] is being performed, [Modify Schedule] cannot be performed.

• After a disabled schedule is changed, the schedule is not enabled automatically. Enable the schedule manually after changing it. For details, refer to "Enabling a schedule" (page 115).



110


3 Change the setting contents of the schedule, and then click the [Next] button.


• If [Number of Snapshot Generations] is set to "0", NAS snapshots that are already acquired are deleted.

• The snapshot creation destination pool cannot be changed.



111


4 Select [Create NAS Backup] or [Do Not Create NAS Backup] for the backup option, and then click the [Next] button.

5 The entered information is displayed. After making sure that the entered information is correct, select the [Please refresh the view of ETERNUS vCenter Plug-in right now.] checkbox in the [Refresh option] field if necessary, and then click the [Modify] button.




112



End of procedure

4.4.3 Disabling or Enabling a Schedule

This section describes the procedure for temporarily disabling or enabling a schedule that is set. The followingexample is for the case when the datastore is selected from the inventory tree.

■ Disabling a schedule

Procedure


If the function for disabling or enabling a schedule is executed for a schedule that is being executed, the schedule is disabled or enabled after the execution of the schedule is completed.



113


2 From the menu bar, select [All FUJITSU ETERNUS DX Actions] — [Disable Schedule] to start the wizard for disabling a schedule.

3 The information on the schedule to be disabled is displayed. After making sure that the displayed information is correct, select the [Please refresh the view of ETERNUS vCenter Plug-in right now.] checkbox in the [Refresh option] field if necessary, and then click the [Disable] button.



114



End of procedure

■ Enabling a schedule

Procedure




115


2 From the menu bar, select [All FUJITSU ETERNUS DX Actions] — [Enable Schedule] to start the wizard for enabling a schedule.

3 The information on the schedule to be enabled is displayed. After making sure that the displayed information is correct, select the [Please refresh the view of ETERNUS vCenter Plug-in right now.] checkbox in the [Refresh option] field if necessary, and then click the [Enable] button.



116



End of procedure

4.4.4 Executing a Schedule Immediately

This section describes the procedure for executing a schedule immediately. The following example is for thecase when the datastore is selected from the inventory tree.

Procedure


Even if the process of the wizard is completed, the process for executing the schedule immediately is not completed. The progress rate can be checked in the Task Console of vSphere Web Client.

• If the schedule is for the NFS datastore under the NAS volume that stores a virtual machine for which [Restore Virtual Machine] or [Single Item Restore] is being performed, [Backup Now] cannot be executed.

• If the schedule is being executed for another NFS datastore under the same NAS volume, [Backup Now] cannot be executed.

• If NAS backup within a single ETERNUS DX or NAS backup between ETERNUS DX storage systems is set, the execution of the schedule may take some time.



117


2 From the menu bar, select [All FUJITSU ETERNUS DX Actions] — [Backup Now] to start the wizard for executing a schedule immediately.

3 The information on the schedule to be executed immediately is displayed. After making sure that the displayed information is correct, select the [Please refresh the view of ETERNUS vCenter Plug-in right now.] checkbox in the [Refresh option] field if necessary, and then click the [Execute] button.



118



5 The progress of the immediate execution of the schedule can be checked in the Task Console of vSphere Web Client.

End of procedure



119


4.4.5 Canceling a Schedule That Is Being Executed

This section describes the procedure for canceling a schedule that is being executed. The following example isfor the case when the target task is selected from the Task Console.

Procedure

1 In the Task Console of vSphere Web Client, select the [FUJITSU Storage ETERNUS DX Execute Schedule] task or the [FUJITSU Storage ETERNUS DX Backup now] task, and then click the [X] button in the [Status] column to display a confirmation dialog box.


3 Check that the task is canceled.

End of procedure

• If a NAS backup between ETERNUS DX storage systems is being performed, the acquisition of the NAS backup between ETERNUS DX storage systems cannot be canceled.

• To cancel a NAS backup between ETERNUS DX storage systems, use ETERNUS SF to forcibly stop the oper-ating copy sessions for the three copy groups that were created in Step 12 (page 102) of "4.3.1 Creating Datastores or LUNs" (page 92). For details, refer to "Display/Forcible Suspend/Forcible Cancel Copy Session" in "ETERNUS SF Web Console Guide".



120


4.4.6 Deleting a Schedule

This section describes the procedure for deleting a schedule. The following example is for the case when thedatastore is selected from the inventory tree.

Procedure


2 From the menu bar, select [All FUJITSU ETERNUS DX Actions] — [Delete Schedule] to start the wizard for deleting a schedule.

3 Select [Delete Storage System Snapshot Setting], and then click the [Next] button.



121


4 The information of the schedule that is to be deleted is displayed. After making sure that the displayed information is correct, select the [Please refresh the view of ETERNUS vCenter Plug-in right now.] checkbox in the [Refresh option] field if necessary, and then click the [Delete] button.


End of procedure



122

Chapter 4　NAS Functions 4.5　Restoring a Virtual Machine

4.5 Restoring a Virtual Machine

This function is used to restore a virtual machine to the state in which the virtual machine was when ETERNUSvCenter Plug-in acquired a NAS snapshot.In a virtual machine restore, a specified virtual machine can be restored. In addition, a new virtual machine iscreated in the state in which a specified virtual machine was when a NAS snapshot was acquired, while thespecified machine is left unchanged.In a single item restore, one or more virtual disk files (VMDK files) that were created when a NAS snapshotwas acquired are assigned to a virtual machine and the files are restored.

4.5.1 Restoring a Virtual Machine

This section describes the procedure for restoring a virtual machine. The following example is for the casewhen the virtual machine is selected from the inventory tree.

• For a virtual machine restore or a single item restore, the restore can be performed simultaneously for up to two virtual machines.

• When a virtual machine restore or a single item restore is performed during a firmware update of the ETERNUS DX, the execution of the restore may fail.

Even if the process of the wizard is completed, the process for restoring the virtual machine is not completed. The progress rate can be checked in the Task Console of vSphere Web Client.



123


Procedure

1 From the vCenter Home screen of vSphere Web Client, select [vCenter Inventory Lists] — [Virtual Machines], and then right-click on the virtual machine to be restored to display the menu bar.

• If much of physical capacity of the virtual machine is in use when the NAS snapshot is acquired, the restore may take some time.

• If the I/O process of business-related data is being executed, the restore may take some time.• When [Restore Virtual Machine] is performed, the configuration file (VMX file) of the virtual machine

must exist on the NFS datastore that is stored in the ETERNUS DX that is registered in ETERNUS vCenter Plug-in.

• If [Restore Virtual Machine] or [Single Item Restore] is being performed for a virtual machine, an additional virtual machine restore cannot be performed for the virtual machine.

• If [Restore Virtual Machine] is being performed for a virtual machine that is stored in an NFS datastore under a NAS volume, the procedure for executing, immediately executing, changing, or deleting a schedule cannot be performed for the NFS datastore.

• If a restore is performed when [Restore to other VM] is selected, a conflict of IP addresses occurs between the specified virtual machine and the new virtual machine. Before powering on the new virtual machine, resolve conflicting IP addresses or check that the specified virtual machine is not powered on.

• If the resource pool or vApp in which a virtual machine was registered when a NAS snapshot was acquired does not exist, an error occurs during the restore process. In this case, take actions according to the instructions in the error message, and then the restored virtual machine can be used.

• If VMDK files that configure a virtual machine are placed in multiple NAS volumes when a NAS snapshot is acquired or when a restore is performed, only the resources within the NAS volume in which the VMX file exists are restored. To restore the resources within the NAS volumes in which the VMX file does not exist, use [Single Item Restore].

• If a virtual machine uses a VMFS datastore or an NFS datastore that is not managed by ETERNUS vCenter Plug-in, the virtual machine restore function is not supported.

• If a VMX file is in a directory that is different from the directory in which a VMDK file is placed when a NAS snapshot is acquired or when restore is performed, [Restore Virtual Machine] cannot be performed when [Restore to other VM] is selected.

• If VMDK files of a virtual machine that are placed in multiple directories are moved in a single directory, for example, by an operation of VMware vSphere vMotion after a NAS snapshot is acquired, [Restore Virtual Machine] cannot be performed.

• When a virtual machine restore is being performed, the schedule is automatically disabled to prevent the oldest generation of the NAS snapshot from being deleted after the number of generations reaches the maximum. The disabled schedule is automatically enabled again after the completion of the virtual machine restore.



124


2 From the menu bar, select [All FUJITSU ETERNUS DX Actions] — [Restore Virtual Machine] to start the wizard for restoring a virtual machine.


• SnapshotsSelect the restore source snapshot.

• Restore toSelect [Restore to Selected VM] or [Restore to other VM] for the restore destination.

• Virtual Machine NameEnter the virtual machine name when [Restore to other VM] is selected for the restore destination.

• Boot after restoreSelect whether to start the virtual machine after the restore.

From 1 to 80 any characters and symbols can be entered in the [Virtual Machine Name] field.



125


4 Select the host in which the restored virtual machine is registered, and then click the [Next] button.

5 Select the datastore in which the files of the restored virtual machine are stored, and then click the [Next] button.

If [Restore to Selected VM] is selected for the restore destination in Step 3, skip this step.

If [Restore to Selected VM] is selected for the restore destination in Step 3, skip this step.



126


6 The entered information is displayed. After making sure that the entered information is correct, select the [Please refresh the view of ETERNUS vCenter Plug-in right now.] checkbox in the [Refresh option] field if necessary, and then click the [Restore] button.




127


8 The progress of the virtual machine restore can be checked in the Task Console of vSphere Web Client.

End of procedure

4.5.2 Canceling Virtual Machine Restore and Recovering It from Cancellation

This section describes the procedure for canceling a virtual machine restore and recovering it fromcancellation. The following example is for the case when the target task is selected from the Task Console ofvSphere Web Client.

■ Canceling virtual machine restore

Procedure

1 In the Task Console of vSphere Web Client, select the [FUJITSU Storage ETERNUS DX Restore Virtual Machine] task, and then click the [X] button in the [Status] column to display a confirmation dialog box.




128



End of procedure

■ Recovering canceled virtual machine restore

Procedure

1 In the Task Console of vSphere Web Client, select the canceled [FUJITSU Storage ETERNUS DX Restore Virtual Machine] task.

2 Check the related events.



129


3 Refer to the following progress status of the virtual machine restore and perform the recovery procedure in the suitable arrow direction.

■ When [Restore to Selected VM] is selected

When a temporary folder (*1) is left in the folder that stores the files of the virtual machine

Select the VMX file, and then execute [Register VM] in vSphere Web Client.

When a temporary folder is not left in the folder that stores the files of the virtual machine, no operation is required.

"Start Restoring VirtualMachine <virtual_machine_name>" is displayed in the [Related events] field.

"Completion Restore VirtualMachine <virtual_machine_name>" is displayed in the [Related events] field.

Select the registered virtual machine, and then execute [Power On] in vSphere Web Client.

The [Remove Snapshot] task has been executed.

Execute [Enable Schedule] to enable the schedule.

The [Power On virtual Machine] task has been executed.

[Restore Virtual Machine] has been successfully completed. Recovery is not required.

"Enable Schedule <schedule_name>" is displayed in the [Related events] field.

1. Select the registered virtual machine, and then execute [Edit Settings] in vSphere Web Client. Delete all hard disks whose capacity is 0 and for which an error is displayed. Before deleting them, enter "1" or a larger value in the capacity field.

2. Select the registered virtual machine, and then open [Manage Snapshots] in vSphere Web Client. If the name of the latest snapshot is "EVCP_SCHEDULE_VMSNAP", execute [Revert to]. If “EVCP_SCHEDULE_VMSNAP” does not exist or is not the latest, do not execute any operation.

The [Register virtual machine] task has been executed.

Select the registered virtual machine, and then open [Manage Snapshots] in vSphere Web Client. If the name of the latest snapshot is "EVCP_SCHEDULE_VMSNAP", delete it.

The [Revert snapshot] task has been executed.

The [Unregister virtual Machine] task has been executed.

The [Power Off virtual machine] task has been executed.

Select the VMX file, and then execute [Register VM] in vSphere Web Client.

Select the virtual machine, and then execute [Power On] in vSphere Web Client.

"Disable Schedule <schedule_name>" is displayed in the [Related events] field.


"Preparation Completion" is displayed in the [Related events] field.

Recovery is not required.

*1: Example of a temporary file name: 423c02a9-7e93-4fb9-85e0-7494da447048_EVCP_RESTORE_TMP

If the time stamps on all the files in the folder that stores the files of the virtual machine are older than the files in the temporary folder, delete the temporary folder.

If the time stamps on the files in the folder that stores the files of the virtual machine are the same as at least one file in the temporary folder, overwrite the folder that stores the files of the virtual machine with all the files in the temporary folder.



130


• Example 1: In the progress of the canceled restore, the [Unregister virtual machine] task is executed.

(1) Select the VMX file of the virtual machine for which the restore was canceled, and then execute [Register VM] in vSphere Web Client.

(2) Select the registered virtual machine, and then execute [Power On] in vSphere Web Client.

(3) Perform [Enable Schedule] to enable the schedule.

• Example 2: In the progress of the canceled restore, the [Remove snapshot] task is executed.

(1) Select the registered virtual machine, and then execute [Power On] in vSphere Web Client.




131


■ When [Restore to other VM] is selected

Example: In the progress of the canceled restore, the [Register virtual machine] task is executed.

(1) Select the registered virtual machine, and then execute [Remove from Inventory] in vSphere Web Client.

(2) If the directory with the virtual machine name that is entered in Step 5 (page 126) of "4.5 Restoring a Virtual Machine" exists in the datastore that is selected in Step 1 (page 124) of "4.5 Restoring a Virtual Machine", delete the directory.


End of procedure

- The [Register virtual machine] task has been executed.- The [Revert snapshot] task has been executed.- The [Remove Snapshot] task has been executed.- The [Power On virtual Machine] task has been executed.

- "Start Restoring VirtualMachine <virtual_machine_name>" is displayed in the [Related events] field.- "Completion Restore VirtualMachine <virtual_machine_name>" is displayed in the [Related events] field.

“Enable Schedule <schedule_name>” is displayed in the [Related events] field.

[Restore Virtual Machine] has been successfully completed. Recovery is not required.



If the datastore selected in Step 3 of the wizard for restoring the virtual machine contains a folder with the name of the virtual machine that was specified in Step 1, delete the folder.

If the datastore selected in Step 3 of the wizard for restoring the virtual machine does not contain a folder with the name of the virtual machine that was specified in Step 1, no action is required.



Select the registered virtual machine, and then execute [Remove from Inventory] in vSphere Web Client.



132


4.5.3 Single Item Restore

This section describes the procedure for performing a single item restore. The following example is for thecase when the virtual machine is selected from the inventory tree.

Procedure

1 From the vCenter Home screen of vSphere Web Client, select [vCenter Inventory Lists] — [Virtual Machines], and then right-click on the virtual machine to display the menu bar.

Even if the process of the wizard is completed, the process of the single item restore is not completed. The progress rate can be checked in the Task Console of vSphere Web Client.

• Multiple generations of VMDK files cannot be assigned at the same time.• The same generation of multiple VMDK files can be connected.• If much of physical capacity of the virtual machine is in use when the NAS snapshot is acquired, the

restore may take some time.• If the I/O process of business-related data is being executed, the restore may take some time.• If [Single Item Restore] or [Restore Virtual Machine] is being performed for a virtual machine, an

additional virtual machine restore cannot be performed for the virtual machine.• If [Single Item Restore] is being performed for a virtual machine that is stored in an NFS datastore under

a NAS volume, the procedure for executing, immediately executing, changing, or deleting a schedule cannot be performed for the NFS datastore.

• When [Single Item Restore] is performed, the configuration file (VMX file) of the virtual machine must exist on the NFS datastore that is stored in the ETERNUS DX that is registered in ETERNUS vCenter Plug-in.

• VMDK files that meet all of the following conditions are displayed as VMDK files that can be used for the restore:

- VMDK files that exist on the NAS volume that stores the VMX file of the virtual machine that is to be restored

- VMDK files that exist on the NFS datastore that is managed by ETERNUS vCenter Plug-in• When a single item restore is being performed, the schedule is automatically disabled to prevent the

oldest generation of the NAS snapshot from being deleted after the number of generations reaches the maximum. The disabled schedule is automatically enabled again after the completion of the single item restore.

• VMDK files that are stored in different NFS datastores but have the same name (including VMDK files of VM snapshots that are created from a VMDK with the same name) cannot be connected at the same time.If multiple VMDK files that are stored in different NFS datastores but have the same name are specified at the same time, single item restore fails.



133


2 From the menu bar, select [All FUJITSU ETERNUS DX Actions] — [Single Item Restore] to start the wizard for the single item restore.

3 Select the snapshot to be used for the restore, and then click the [Next] button.



134



• Expiration dateSpecify the single item restore period. When the specified period passes, the connected VMDK file isautomatically removed from the virtual machine. The valid setting value is an integer from 1 to 72.

• VMDK filesSelect the VMDK file that is to be restored.

5 The entered information is displayed. After making sure that the entered information is correct, select the [Please refresh the view of ETERNUS vCenter Plug-in right now.] checkbox in the [Refresh option] field if necessary, and then click the [Restore] button.



135



7 The progress of the single item restore can be checked in the Task Console of vSphere Web Client.

End of procedure



136


4.5.4 Stopping Single Item Restore Immediately

This function is used to immediately stop a single item restore that is being executed when the single itemrestore must be stopped before the specified automatic stop time.This section describes the procedure for stopping single item restore immediately. The following example isfor the case when the virtual machine is selected from the inventory tree.

Procedure

1 From the vCenter Home screen of vSphere Web Client, select [vCenter Inventory Lists] — [Virtual Machines], and then right-click on the virtual machine to display the menu bar.

2 From the menu bar, select [All FUJITSU ETERNUS DX Actions] — [Stop Single Item Restore] to start the wizard for stopping a single item restore immediately.

The information for the VMDK files that were connected when a single item restore was performed isdisplayed.

This function can configure settings to allow the VMDK files that were connected when [Single Item Restore] was performed to continue to be used.

If the expiration date setting for [Single Item Restore] is disabled, the VMDK files that are connected when [Single Item Restore] is performed can be deleted in [Edit Settings] by selecting the virtual machine from vSphere Web Client.



137


3 To continue using the connected VMDK files, select the [Disable expiration date of single item restore.] checkbox.After making sure that the displayed information is correct, select the [Please refresh the view of ETERNUS vCenter Plug-in right now.] checkbox in the [Refresh option] field if necessary, and then click the [Stop] button.


End of procedure



138


4.5.5 Canceling Single Item Restore and Recovering It from Cancellation

This section describes the procedure for canceling a single item restore and recovering it from cancellation.The following example is for the case when the target task is selected from the Task Console.

■ Canceling single item restore

Procedure

1 In the Task Console of vSphere Web Client, select the [FUJITSU Storage ETERNUS DX Execute Single Item Restore] task, and then click the [X] button in the [Status] column to display a confirmation dialog box.



End of procedure



139


■ Recovering canceled single item restore

Procedure

1 In the Task Console of vSphere Web Client, select the [FUJITSU Storage ETERNUS DX Execute Single Item Restore] task.

2 Check the related events.



140


3 Refer to the following progress status of single item restore and perform the recovery procedure in the arrow direction.

Example: In the progress of the restore when the restore is canceled, the [Reconfigure virtual machine]task is executed.

(1) From the [Completion Restore VMDK File <VMDK_file_path>] event, check the path to the target VMDK file.

(2) Select the target virtual machine, and then execute [Edit Settings] in vSphere Web Client to delete the target VMDK file.

(3) If the following directory exists on the datastore in which the target virtual machine exists, delete the directory.Virtual machine directory name:-SIR-yyyyMMddHHmmss-yyyyMMddHHmmss

(4) If [Disable Schedule] is displayed in the [Related events] field, perform [Enable Schedule] to enable the schedule.

End of procedure

"Create SingleItemRestore Auto Stop Job" is displayed in the [Related events] field.

"Enable Schedule <schedule_name>" is displayed in the [Related events] field.

The [Reconfigure virtual machine] task has been executed.

[Single Item Restore] has been successfully completed. Recovery is not required.

No action is required.

"Completion Restore VMDK File <VMDK_file_path>" is displayed in the [Related events] field.

If the "virtual_machine_directory_name:-SIR-yyyyMMddHHmmss(*1)-yyyyMMddHHmmss(*2)" folder exists under the datastore that stores the restore target virtual machine directory, delete the folder.

Select the virtual machine, and then execute [Edit Settings] in vSphere Web Client to delete the added VMDK file (*3).

If the "virtual_machine_directory_name:-SIR-yyyyMMddHHmmss(*1)-yyyyMMddHHmmss(*2)" folder does not exist under the datastore that stores the restore target virtual machine directory, no action is required.





*1: The first "yyyyMMddHHmmss" part is the date and time of snapshot acquisition that was selected in Step 1 of the wizard for single item restore.

*2: The second "yyyyMMddHHmmss" part is the date and time when single item restore was performed.

*3: For the VMDK file that is to be deleted, refer to the VMDK file path for "Completion Restore VMDK File <VMDK_file_path>" in the related events.



141


4.5.6 Restoring from NAS Backups or Backups between ETERNUS DX Storage Systems

This section describes the procedure for restoring data from a NAS backup or a backup between ETERNUS DXstorage systems.Perform the following operations on ETERNUS SF and vSphere Web Client server in which ETERNUS vCenterPlug-in is installed:

• Operations on ETERNUS SF- Restore from a NAS backup- Restore from a backup between ETERNUS DX storage systems

• Operations on the vSphere Web Client server in which ETERNUS vCenter Plug-in is installed- Disable schedule- Power-off of the virtual machine- Reconfiguration of the inventory- Creation of schedules

Procedure

1 If a schedule for creating a NAS backup (within a single ETERNUS DX or between ETERNUS DX storage systems) is set in the NAS volume to be restored, perform [Disable Schedule].For details, refer to "Disabling a schedule" (page 113).

2 In vSphere Web Client, select the virtual machine that is stored in the NAS volume to be restored, and then execute [Power Off] in the right-click menu.

If the schedule is not set, skip this operation.

If the virtual machine is powered off or cannot be accessed, skip this operation.



142


3 On ETERNUS SF Web Console, restore data from a NAS backup or from a backup between ETERNUS DX storage systems.

■ When restoring from a NAS backup

For the procedure for restoring data from a NAS backup, refer to "Backup / Restoration with WebConsole" in "Backup of NAS Environment" of "Operation" in "ETERNUS SF AdvancedCopy ManagerOperation Guide for Copy Control Module".

■ When restoring from a backup between ETERNUS DX storage systems

The procedure for restoring data from a backup between ETERNUS DX storage systems varies dependingon the operating policy as follows:

• For the data protectionFor the restore procedure, refer to "Restoration Procedures" in "Details of the Data ProtectionOperation" of "Inter-box Backup/Restore of NAS Volumes" in "ETERNUS SF AdvancedCopy ManagerOperation Guide for Copy Control Module".

• For the standby operationA restore is not required for the standby operation because if a failure or an error occurs on theactive device, the NAS volume of the standby device is used to continue the NAS operation.

4 Use vSphere Web Client to restore the inventory.

■ For an NFS datastore that was deleted from the storage by the restore

(1) Delete the virtual machine that is stored in the NFS datastore from vSphere Web Client.

(2) Delete the NFS datastore by using the procedure for deleting a datastore. For details about the procedure, refer to "4.7 Deleting Datastores or LUNs" (page 147).

■ For an NFS datastore that was deleted from vSphere Web Client and restored to the storage side by the restore

(1) In vSphere Web Client, select the host and execute [New Datastore] in the right-click menu to create an NFS datastore.

(2) In vSphere Web Client, select the NFS datastore and execute [Register VM] in the right-click menu to register the virtual machine that was restored on the storage side.

5 In vSphere Web Client, select the virtual machine that was powered off in Step 2, and then execute [Power On] in the right-click menu.

6 Perform [Enable Schedule] and [Backup Now] if necessary.

End of procedure

For details, refer to "Enabling a schedule" (page 115) and "4.4.4 Executing a Schedule Immediately" (page 117).



143

Chapter 4　NAS Functions 4.6　Changing Settings

4.6 Changing Settings

This section describes the procedures for changing the registered information of ETERNUS vCenter Plug-in,expanding the capacity of an NFS datastore, and changing the settings of a datastore.

4.6.1 Changing Storage Information

For details about the procedure for changing storage information, refer to "4.2.1 Registering, Deleting, orUpdating Storage Systems" (page 74).

4.6.2 Changing Resource Information

For details about the procedure for changing resource information, refer to "4.2.2 Registering, Deleting, orUpdating Resources" (page 79).

4.6.3 Changing ETERNUS SF Information

For details about the procedure for changing ETERNUS SF information, refer to "4.2.3 Registering, Changing,or Deleting ETERNUS SF Connection Information" (page 84).

4.6.4 Expanding the Capacity of a Datastore

This section describes the procedure for expanding the capacity of a datastore. The capacity expansion isexecuted for the NAS volume that stores the selected NFS datastore.

Procedure

1 From the vCenter Home screen of vSphere Web Client, select [vCenter Inventory Lists] — [Datastores].

• When this function is used to expand the capacity of an NFS datastore, the schedule that is set for the NFS datastore must be deleted. If the capacity of an NFS datastore is expanded and the schedule is not deleted, the expansion fails.

• Recreate the schedule as required after the capacity is expanded.• The capacity of the expanded NAS volume cannot be reduced.



144


2 From the menu bar, select [All FUJITSU ETERNUS DX Actions] — [Expand Capacity of Datastore (NAS Volume)] to start the wizard for expanding the capacity of a datastore.

3 Enter desired values in [Expansion Capacity] or [Expansion Result Capacity], and then click the [Next] button.



145


4 The entered information is displayed. After making sure that the entered information is correct, select the [Please refresh the view of ETERNUS vCenter Plug-in right now.] checkbox in the [Refresh option] field if necessary, and then click the [Expand] button.


End of procedure

4.6.5 Changing NFS Allowed Hosts for a Datastore

For details about the procedure for changing NFS allowed hosts for a datastore, refer to "4.3.2 Changing NFSAllowed Hosts for a Datastore" (page 103).



146

Chapter 4　NAS Functions 4.7　Deleting Datastores or LUNs

4.7 Deleting Datastores or LUNs

This section describes the procedure for deleting NFS datastores.

Procedure

1 From the vCenter Home screen of vSphere Web Client, select [vCenter Inventory Lists] — [Hosts] or [Clusters].

2 Right-click on the host or cluster to which the NFS datastores to be deleted are mounted to display the menu bar. Select [All FUJITSU ETERNUS DX Actions] — [Delete Datastore/LUN] to start the wizard for deleting datastores/LUNs.

The datastores/volumes that are recognized by the selected host (or all hosts that belong to the clusterwhen the action is started from that cluster) are displayed in a list.Rows with red letters show the datastores/volumes that are recognized by multiple hosts. Rows withgray letters show the datastores/volumes that cannot be deleted.

• This function deletes only NFS datastores and does not delete the NAS volume that stores the NFS datastores. To delete the NAS volume, use ETERNUS Web GUI, ETERNUS CLI, or ETERNUS SF Web Console.

• To delete NFS datastores, delete all files and directories that are stored in the NFS datastores to be deleted.

• To delete schedules that are created on NFS datastores, perform [Delete Schedule]. For details, refer to "4.4.6 Deleting a Schedule" (page 121).

• If the schedule is not displayed after the deletion of the NFS datastore but before the schedule is deleted, create an NFS datastore in the NAS volume in which the schedule is set to display the schedule again. After the schedule is displayed, delete it.

• If an error occurs during the deletion of an NFS datastore, the shared folder that is used as the NFS data-store may remain in the ETERNUS DX. Use ETERNUS Web GUI or ETERNUS CLI to delete any unnecessary shared folders.



147


3 Select the NFS datastores to be deleted, and then click the [Next] button.

4 The selected NFS datastores are displayed in a list. After making sure that the displayed information is correct, select the [Please refresh the view of ETERNUS vCenter Plug-in right now.] checkbox in the [Refresh option] field if necessary, and then click the [Delete] button.



148



End of procedure



149

Chapter 4　NAS Functions 4.8　Displaying Information

4.8 Displaying Information

This function is used to display the information on ETERNUS DX storage systems and the schedule informationthat is set for a NAS volume in the vSphere Web Client screen.For details about the items displayed with this function, refer to "Appendix C List of Displayed Items" (page178).

4.8.1 FUJITSU Storage ETERNUS DX Screen

When ETERNUS vCenter Plug-in is installed, the [FUJITSU ETERNUS DX] menu and the "FUJITSU ETERNUS DX"icon are added in the [Home] screen of vSphere Web Client. Click either of them to display the [FUJITSUStorage ETERNUS DX] screen.



150


The [FUJITSU Storage ETERNUS DX] screen consists of the following four tabs:

■ Storage System

This screen displays the information on ETERNUS DX storage systems that are registered in ETERNUS vCenterPlug-in. In this screen, the status of each ETERNUS DX can be checked and also the login screen of ETERNUSWeb GUI can be opened.Clicking the "Register Storage" icon starts the wizard for registering or deleting ETERNUS DX storage systems.

■ Resources

This screen displays the information on resources (RAID groups or Thin Provisioning Pools) for ETERNUS DXstorage systems that are registered in ETERNUS vCenter Plug-in.Clicking the "Register Resource" icon starts the wizard for registering or deleting resources.



151


■ ETERNUS SF

This screen displays the connection information on the ETERNUS SF that is registered in ETERNUS vCenterPlug-in. In this screen, the connection status of ETERNUS SF and the setting contents of a NAS backup can bechecked.Clicking the icons at the upper left of the screen starts the wizard for registering, changing, or deleting theETERNUS SF connection information.

■ Version

This screen displays the version information of ETERNUS vCenter Plug-in.

4.8.2 Displaying Datastore Information

This section describes the procedure for displaying the information on a datastore.The following information can be displayed when an NFS datastore is selected:

• Information on the ETERNUS DX in which the datastore is stored• Schedule information• NAS snapshot information



152


Procedure

1 From the vCenter Home screen of vSphere Web Client, select [vCenter Inventory Lists] — [Datastores].

2 Select the NFS datastore that is created in the ETERNUS DX from the datastore list that is displayed in the left pane.

3 Click the [FUJITSU ETERNUS DX] tab under the [Manage] tab.Two submenus, [Storage View] and [Backup], are displayed.

■ Storage View

The information on the NFS datastore that is stored in the ETERNUS DX that is registered in ETERNUS vCenter Plug-in is displayed.



153


Selecting the [Storage View] submenu displays the [Datastore Detail] and [ETERNUS Details] windows.

• Datastore DetailThis window displays the information on the NFS server and folder of the selected NFS datastore.

• ETERNUS DetailsThis window displays the ETERNUS-related information of the selected NFS datastore on thefollowing seven types of portlets:

- VolumeThis portlet displays the information such as the name and size of the NAS volume that storesthe selected NFS datastore.

- NFS Datastores located on the NAS VolumeThis portlet displays a list of NFS datastores that are created in the NAS volume.

- Schedule InformationThis portlet displays the schedule information that is created in the NAS volume.

- Thin Provisioning PoolThis portlet displays the information on the Thin Provisioning Pool that stores the selected NFSdatastore.

- PerformanceThis portlet displays the performance information of the selected NFS datastore. Beforedisplaying the information, it is necessary to use the procedure for setting the performanceinformation to start the measurement of the performance information.

- System InformationThis portlet displays the basic information on the ETERNUS DX that stores the selected NFSdatastore.

- Storage ConditionThis portlet displays the usage statuses of the RAID group, Thin Provisioning Pool, and Snap DataPool of the ETERNUS DX that stores the selected NFS datastore.



154


■ Backup

Selecting the [Backup] menu displays two submenus, [Schedule] and [Snapshot], under the menu.

• Schedule

Selecting the [Schedule] submenu displays the [Schedule Status], [Schedule Information], [NASVolume], and [NFS Datastores located on the NAS Volume] windows.

- Schedule StatusThis window displays the previous results of the schedules for the selected NFS datastore.

- Schedule InformationThis window displays the detailed information of the schedules for the selected NFS datastore.

- NAS VolumeThis window displays the information on the NAS volume that stores the selected NFS datastore.

- NFS Datastores located on the NAS VolumeThis window displays a list of NFS datastores that are created in the NAS volume.

• Snapshots

Selecting the [Snapshot] submenu displays a list of the acquired snapshots for the selecteddatastore. The [Snapshot] submenu consists of the [NAS Volume] and [Snapshots] windows.

- NAS VolumeThis window displays the information on the NAS volume that stores the selected NFS datastore.

- SnapshotsThis window displays a list of the NAS snapshots that contain the selected NFS datastore.

End of procedure



155


4.8.3 Displaying Virtual Machine Information

This section describes the procedure for displaying the information on a virtual machine.The following information can be displayed when a virtual machine is selected:

• Information on the ETERNUS DX in which the virtual machine is stored• NAS snapshot information

Procedure

1 From the vCenter Home screen of vSphere Web Client, select [vCenter Inventory Lists] — [Virtual Machines].

2 Select the virtual machine that is created in the ETERNUS DX from the virtual machine list that is displayed in the left pane.

3 Click the [FUJITSU ETERNUS DX] tab under the [Manage] tab.Two submenus, [Storage View] and [Backup], are displayed.

■ Storage View

The information on the virtual disks of the virtual machine that is stored in the ETERNUS DX that is registered in ETERNUS vCenter Plug-in is displayed.



156


Selecting the [Storage View] submenu displays the [Virtual Disks], [Datastore Detail], and [ETERNUSDetails] windows.

• Virtual DisksThis window displays the information on all the virtual disks that are used by the selected virtualmachine.

• Datastore DetailThis window displays the information on the NFS server and folder of the NFS datastore that storesthe selected virtual disk.

• ETERNUS DetailsThis window displays the ETERNUS-related information of the selected NFS datastore on thefollowing seven types of portlets:

- VolumeThis portlet displays the information such as the name and size of the NAS volume that storesthe selected NFS datastore.

- NFS Datastores located on the NAS VolumeThis portlet displays a list of NFS datastores that are created in the NAS volume.

- Schedule InformationThis portlet displays the schedule information that is created in the NAS volume.

- Thin Provisioning PoolThis portlet displays the information on the Thin Provisioning Pool that stores the selected NFSdatastore.

- PerformanceThis portlet displays the performance information of the selected NFS datastore. Beforedisplaying the information, it is necessary to use the procedure for setting the performanceinformation to start the measurement of the performance information.

- System InformationThis portlet displays the basic information on the ETERNUS DX that stores the selected NFSdatastore.

- Storage ConditionThis portlet displays the usage statuses of the RAID group, Thin Provisioning Pool, and Snap DataPool of the ETERNUS DX that stores the selected NFS datastore.



157


■ Backup

Selecting the [Backup] submenu displays the [NAS Volume], [Snapshots], and [Single Item RestoreInformation] windows.

• NAS VolumeThis window displays the NAS volume that stores the selected virtual machine.

• Snapshot ListThis window displays a list of the NAS snapshots that contain the selected NFS datastore.

• Single Item Restore InformationThe information on the VMDK files that were assigned to the selected virtual machine when [SingleItem Restore] was performed is displayed.

End of procedure

4.8.4 Displaying Host System Information

This section describes the procedure for displaying the information on a host system.The following information can be displayed when a host system is selected:

• Information on the datastore that is assigned to the host system• Datastore information• Performance information

Procedure

1 From the vCenter Home screen of vSphere Web Client, select [vCenter Inventory Lists] — [Hosts].

2 From the host system list that is displayed in the left pane, select the host system that uses the NFS datastore for the ETERNUS DX.

The information on the NFS datastore that is stored in the ETERNUS DX that is registered in ETERNUS vCenter Plug-in is displayed.



158


3 Click the [FUJITSU ETERNUS DX] tab under the [Manage] tab.Three submenus, [Storage View], [Adapter], and [Performance], are displayed. [Adapter] is not usedfor the NAS functions.

■ Storage View

Selecting the [Storage View] submenu displays three submenus, [Datastore], [Raw Device Mapping],and [Others], under the submenu. [Raw Device Mapping] and [Others] are not used for the NASfunctions.

• Datastore

Selecting the [Datastore] submenu displays the [Assigned Disks], [Datastore Detail], and [ETERNUSDetails] windows.

- Assigned DisksThis window displays a list of the NFS datastores that are mounted to the selected host.

- Datastore DetailThis window displays the information on the NFS server and folder of the NFS datastore thatstores the selected virtual disk.

- ETERNUS DetailsThis window displays the ETERNUS-related information of the selected NFS datastore on thefollowing seven types of portlets:

• VolumeThis portlet displays the information such as the name and size of the NAS volume thatstores the selected NFS datastore.

• NFS Datastores located on the NAS VolumeThis portlet displays a list of NFS datastores that are created in the NAS volume.

• Schedule InformationThis portlet displays the schedule information that is created in the NAS volume.

• Thin Provisioning PoolThis portlet displays the information on the Thin Provisioning Pool that stores the selectedNFS datastore.



159


• PerformanceThis portlet displays the performance information of the selected NFS datastore. Beforedisplaying the information, it is necessary to use the procedure for setting the performanceinformation to start the measurement of the performance information.

• System InformationThis portlet displays the basic information on the ETERNUS DX that stores the selected NFSdatastore.

• Storage ConditionThis portlet displays the usage statuses of the RAID group, Thin Provisioning Pool, and SnapData Pool of the ETERNUS DX that stores the selected NFS datastore.

■ PerformanceFor details about the [Performance] submenu, refer to "4.8.5 Performance Information" (page 160).

End of procedure

4.8.5 Performance Information

This function is a common function between the SAN and NAS functions. For details about the procedure, referto "3.3 Displaying Performance Monitoring and Performance Information" (page 41).



160

Chapter 5

Backup/Restore of ETERNUS vCenter Plug-in(Common for SAN and NAS)

This chapter explains the backup/restore procedure for the setting information of ETERNUS vCenter Plug-inand the procedure for migrating the environment directly to other vSphere Web Client servers.

5.1 Backing Up the Setting Information for ETERNUS vCenter Plug-in

This section explains how to back up the setting information of ETERNUS vCenter Plug-in.

Procedure

1 Back up the following folders under the installation folder.<Installation_folder>\conf<Installation_folder>\backupconf

End of procedure

The default installation folder is as follows:<system drive>:\ETERNUS vCenter Plug-in

When performing a backup, make sure that the ETERNUS vCenter Plug-in functions and the schedule are not operating, and then execute a backup.



161

Chapter 5 Backup/Restore of ETERNUS vCenter Plug-in (Common for SAN and NAS) 5.2 Restoring the Setting Information for ETERNUS vCenter Plug-in

5.2 Restoring the Setting Information for ETERNUS vCenter Plug-in

This section explains how to restore the setting information of ETERNUS vCenter Plug-in.

Procedure

1 Overwrite the backup files that are under the installation folder.

2 Restart the vSphere Web Client service.

End of procedure

5.3 Migrating the Environment to Other vSphere Web Client Servers

This section explains how to migrate the environment directly to other vSphere Web Client servers.

Procedure

1 Install ETERNUS vCenter Plug-in in the migration destination vSphere Web Client server.

2 Restore ETERNUS vCenter Plug-in's backup data of the migration source vSphere Web Client server to the migration destination vSphere Web Client server.

3 Restart the vSphere Web Client service of the migration destination vSphere Web Client server.

End of procedure

When vCenter Server 6.0 or later is used, add full control permissions for the "NT SERVICE\vspherewebclientsvc" user for the following items.

• The "backupconf" folder itself• The "evcp_esf.xml", "evcp_resource.xml", and "evcp_storage.xml" files in the "conf" folder



162

Chapter 6

Changing Settings

This chapter describes the operations required for changing various settings after installing ETERNUS vCenterPlug-in. The procedures are explained for the following two cases:

• Changing settings for the ETERNUS DX storage systems• Changing settings for Windows Server where vCenter Server is installed

6.1 Changing Settings for ETERNUS DX Storage Systems

To change the IP address, account, or password for an ETERNUS DX that is registered with the Register StorageWizard, the ETERNUS DX must be registered again. Perform the following procedure:

Procedure

1 Start the Register Storage Wizard, and unregister the ETERNUS DX.

2 Register the ETERNUS DX with the changed information.

3 Click the "Refresh" icon to update the display information.

End of procedure



163

Chapter 6 Changing Settings 6.2 Changing Settings for Windows Server Where vCenter Server Is Installed

6.2 Changing Settings for Windows Server Where vCenter Server Is Installed

To change the IP address, account, or password for the vCenter Server that is registered in ETERNUS vCenterPlug-in, the "evcpConfig" command must be executed to update the configuration information of ETERNUSvCenter Plug-in.

Procedure

1 Execute the "evcpConfig -x" command. For the argument, specify the current IP address of the vCenter Server. Enter the information of a new vCenter Server in interactive mode.

2 Click the "Refresh" icon to update the display information.

End of procedure

C:\ETERNUS vCenter Plug-in\bin>evcpConfig -x 192.168.10.1Welcome to the setup wizard for vCenter registration.Please enter a NEW IP address of vCenter Server : 192.168.10.11Please enter a NEW valid account of vCenter Server : administratorPlease enter a NEW password for the account : ***********

Updated successfully.

C:\ETERNUS vCenter Plug-in\bin>



164

Chapter 6 Changing Settings 6.3 evcpConfig Command

6.3 evcpConfig Command

The "evcpConfig" command is used for environment setting for ETERNUS vCenter Plug-in. This command isused only when the server and/or storage settings are changed after ETERNUS vCenter Plug-in is installed.The command is mainly used in the conditions as mentioned below.

• The initial setup during installation was skipped or failed.• The account and/or network settings for each server were changed during operation.

Execute the command with the built-in administrator privileges. A user belonging to the Administrator group must execute the command with the administrator privileges.

■ Command format

evcpConfig -aevcpConfig -d vCenter-IP-addressevcpConfig -x vCenter-IP-addressevcpConfig -l

■ Option details

■ Example

● -a option

Option Description

-a Registers the vCenter Server to ETERNUS vCenter Plug-in. With this option, the command runs in interactive mode. Enter the IP address, account, and password of the vCenter Server to be registered.

-d Deletes the vCenter Server from ETERNUS vCenter Plug-in. Specify the IP address of the vCenter Server to be deleted.

-x Updates the information of the registered vCenter Server. If this option is executed by specifying the IP address of the vCenter Server to be updated, the command runs in interactive mode. Enter the IP address, account, and password of the vCenter Server after updated.

-l Displays the information about the registered vCenter Server.

C:\ETERNUS vCenter Plug-in\bin>evcpConfig -aWelcome to the setup wizard for vCenter registration.Please enter a IP address of vCenter Server : 192.168.0.10Please enter a valid account of vCenter Server : administratorPlease enter a password for the account : ***********

Registration completed successfully.




165

Chapter 6 Changing Settings 6.3 evcpConfig Command

● -d option

● -x option

● -l option

C:\ETERNUS vCenter Plug-in\bin>evcpConfig -d 192.168.0.10

Unregistration completed successfully.


C:\ETERNUS vCenter Plug-in\bin>evcpConfig -x 192.168.0.10Welcome to the setup wizard for vCenter registration.Please enter a NEW IP address of vCenter Server : 192.168.0.20Please enter a NEW valid account of vCenter Server : administratorPlease enter a NEW password for the account : ***********

Updated successfully.


C:\ETERNUS vCenter Plug-in\bin>evcpConfig -l

IP address=(192.168.10.10) Account=(administrator)




166

Chapter 7

Required Information for Failure Investigation

Prepare the following files when an error occurs, and contact a Fujitsu engineer.

• Files are stored in the following folders.

<Installation_folder>\log<Installation_folder>\conf<Installation_folder>\backupconf<Installation_folder>\ETERNUS-MICC\var\log

The default installation folder is as follows:<system_drive>:\ETERNUS vCenter Plug-in



167

Appendix A

Frequent Inquiry Solutions (Common for SAN and NAS)

Solutions for frequent inquiries are provided in this appendix.Follow the solutions provided for each case.

A.1 The Initial Setup During Installation Failed or Was Skipped

Perform the following procedure to configure the initial setup:

Procedure

1 Execute the "evcpConfig -a" command. Enter the information of the vCenter Server in interactive mode. This operation must be performed for all the vCenter Servers to be managed.

2 Perform the operations required after installation by referring to "2.2 Operations Required After New Installation" (page 25).

End of procedure

C:\ETERNUS vCenter Plug-in\bin>evcpConfig -aWelcome to the setup wizard for vCenter registration.Please enter a IP address of vCenter Server : 192.168.0.10Please enter a valid account of vCenter Server : administratorPlease enter a password for the account : ***********

Registration completed successfully.




168

Appendix A Frequent Inquiry Solutions (Common for SAN and NAS) A.2 The Environment Settings Are Not Retained Normally After Upgrading ETERNUS vCenter Plug-in

A.2 The Environment Settings Are Not Retained Normally After Upgrading ETERNUS vCenter Plug-in

Perform the following procedure to check an ETERNUS DX or a resource in which the environment settingsprior to upgrading of ETERNUS vCenter Plug-in are not retained normally after upgrading is complete, andthen register it again.

Procedure

1 Start the Register Storage Wizard or the Register Resource Wizard to check the ETERNUS DX or the resource in which the environment settings prior to upgrading of ETERNUS vCenter Plug-in are not retained normally after upgrading is complete.

• "-" is displayed as the "Storage System Name" of an ETERNUS DX in which the environment settings prior to upgrading of ETERNUS vCenter Plug-in are not retained normally after upgrading is complete when the Register Storage Wizard is started.



169

Appendix A Frequent Inquiry Solutions (Common for SAN and NAS) A.2 The Environment Settings Are Not Retained Normally After Upgrading ETERNUS vCenter Plug-in

• "-" is displayed as the "Storage System Name" of a resource in which the environment settings prior to upgrading of ETERNUS vCenter Plug-in are not retained normally after upgrading is complete when the Register Resource Wizard is started.

2 Delete the ETERNUS DX or the resource in which the environment settings prior to upgrading of ETERNUS vCenter Plug-in are not retained normally after upgrading is complete, and then register it again. For details, refer to the following sections.

• "3.5.2 Registering ETERNUS DX Storage Systems" (page 50)• "3.5.3 Unregistering ETERNUS DX Storage Systems" (page 52)• "3.6.1 Registering Resources" (page 54)• "3.6.4 Unregistering Resources" (page 65)

End of procedure



170

Appendix B

Role Control

This appendix describes the roles that are installed with ETERNUS vCenter Plug-in.With the use of a roll that is given control of each function, creating specialized user accounts for certain func-tions is possible.

After ETERNUS vCenter Plug-in is installed, the following roles are created.• ETERNUS vCp Administrator• ETERNUS vCp Provision• ETERNUS vCp Backup• ETERNUS vCp Restore• ETERNUS vCp Single Item Restore• ETERNUS vCp Read-only

B.1 ETERNUS vCp Administrator

ETERNUS vCp Administrator is the role that has the privilege to use all the functions of ETERNUS vCenter Plug-in.This role is given the minimum privilege to use all the functions of ETERNUS vCenter Plug-in.

Location Privilege

Distributed switch • Modify

• Port configuration operation

• Port setting operation

ETERNUS vCenter Plug-in> Storage and Resource Management

• ETERNUS SF Registration• Storage System Registration• Resource Registration• View

ETERNUS vCenter Plug-in> Backup and Restore> Backup

• Create, Modify, Delete Schedule

• Enable/Disable Backup Schedule

• Backup Now

ETERNUS vCenter Plug-in> Backup and Restore> Restore

• Execute Single Item Restore/Stop Single Item Restore

• Restore Virtual Machine

ETERNUS vCenter Plug-in> Backup and Restore

View



171

Appendix B Role Control B.1 ETERNUS vCp Administrator

ETERNUS vCenter Plug-in> Provisioning

• Modify NFS Allowed Host

• Extend Datastore (NAS Volume)

• Create Datastore/LUN

• Delete Datastore/LUN

• View

ETERNUS vCenter Plug-in> Performance

• Start/Stop Performance

• View

dvPort group Modify

Extension • Update extension

• Register extension

Global • Log event

• Cancel task

• Licenses

• Settings

Storage views • Configure service

• View

Tasks • Create task

• Update task

Datastore • Remove datastore

• Browse datastore

• Move datastore

• Rename datastore

• Remove file

• Low level file operations

• Allocate space

Datastore cluster Configure a datastore cluster

Network Assign network

Profile-driven storage • Profile-driven storage view

• Profile-driven storage update

Host> Local operations

• Relayout snapshots

• Create virtual machine

• Reconfigure virtual machine

• Delete virtual machine

Host> Configuration

Storage partition configuration

Virtual machine> Inventory

• Create from existing

• Register

• Unregister

Virtual machine> Snapshot management

• Revert to snapshot

• Create snapshot

• Remove Snapshot

Location Privilege



172

Appendix B Role Control B.2 ETERNUS vCp Provision

B.2 ETERNUS vCp Provision

ETERNUS vCp Provision is the role that has the privilege to use the following functions of ETERNUS vCenterPlug-in.

• Creation of the datastore or LUN• Deletion of the datastore or LUN• Capacity expansion of the datastore (NAS volume)• Modification of the NFS allowed host in the datastore

This role provides the necessary privileges for the datastore operation.

Virtual machine> Configuration

• Remove disk

• Add or remove device

• Change resource

Virtual machine> Interaction

• Console interaction

• Power Off

• Power On

• Answer question

Location Privilege

Location Privilege


View


View


• Modify NFS Allowed Host

• Extend Datastore (NAS Volume)

• Create Datastore/LUN

• Delete Datastore/LUN

• View


• Licenses

• Settings

Storage views • Configure service

• View


• Update task



173

Appendix B Role Control B.3 ETERNUS vCp Backup

B.3 ETERNUS vCp Backup

ETERNUS vCp Backup is the role that has the privilege to use the following functions of ETERNUS vCenter Plug-in.

• Creation of the schedule• Modification of the schedule• Deletion of the schedule• Immediate execution of the schedule

This role provides the necessary privileges for the schedule operation.

Datastore • Remove datastore

• Browse datastore

• Move datastore


• Remove file


• Allocate space

Profile-driven storage • Profile-driven storage view

• Profile-driven storage update

Host> Configuration


Location Privilege

Location Privilege


View

ETERNUS vCenter Plug-in> Backup and Restore> Backup

• Create, Modify, Delete Schedule

• Backup Now


View


View


• Cancel task

• Licenses

• Settings


• Update task

Datastore Allocate space



174

Appendix B Role Control B.4 ETERNUS vCp Restore

B.4 ETERNUS vCp Restore

ETERNUS vCp Restore is the role that has the privilege to use the following functions of ETERNUS vCenter Plug-in.

• Restoring the virtual machine• Powering on the virtual machine• Powering off the virtual machine

This role provides the necessary privileges for restoring the virtual machine.

Host> Configuration



• Create snapshot

• Remove Snapshot

Location Privilege

Location Privilege


View


Restore Virtual Machine


View


View


• Cancel task

• Settings


• Update task

Datastore • Browse datastore


• Remove file


• Allocate space

Network Assign network


• Relayout snapshots

• Create virtual machine

• Reconfigure virtual machine

• Delete virtual machine

Host> Configuration




175

Appendix B Role Control B.5 ETERNUS vCp Single Item Restore

B.5 ETERNUS vCp Single Item Restore

ETERNUS vCp Single Item Restore is the role that has the privilege to use the following functions of ETERNUSvCenter Plug-in.

• Executing the single item restore• Immediate stop of a single item restore

This role provides the necessary privileges for a Single Item Restore.

Virtual machine> Inventory

• Create from existing

• Register

• Unregister


• Revert to snapshot

• Remove Snapshot


• Remove disk


• Change resource

Virtual machine> Interaction

• Console interaction

• Power Off

• Power On

• Answer question

Location Privilege

Location Privilege


View


Execute Single Item Restore/Stop Single Item Restore


View


View


• Cancel task


• Update task

Datastore • Browse datastore

• Remove file



Reconfigure virtual machine



176

Appendix B Role Control B.6 ETERNUS vCp Read-only

B.6 ETERNUS vCp Read-only

ETERNUS vCp Read-only is the role that only has the privilege to reference the following information ofETERNUS vCenter Plug-in.

Host> Configuration



• Remove disk


Location Privilege

Location Privilege


View


View


View

ETERNUS vCenter Plug-in> Performance

View

Global Log event

Storage views View


• Update task

Datastore Browse datastore

Profile-driven storage Profile-driven storage view

Host> Configuration




177

Appendix C

List of Displayed Items

C.1 Datastore Detail (SAN)

C.2 Datastore Detail (NAS)

C.3 Schedule Status (NAS)

Display Item Description

Name Disk name

Identifier Identifier

Model Product ID of the ETERNUS DX

Runtime Name Runtime name

LUN LUN (LUN on the host)

Paths The number of paths between the server and the ETERNUS DX

Status Path status. If there are multiple paths, the status of each path is separated by a comma and displayed.

Policy Multipath I/O policy


Type Datastore type

NFS Server IP address of the NFS server

Folder Datastore mount point


Last Result Result of the last execution

• Normal

• Error

Last Start Time Date and time when the last execution started (yyyy/mm/dd hh:mm:ss)

Last End Time Date and time when the last execution ended (yyyy/mm/dd hh:mm:ss)



178

Appendix C List of Displayed Items C.4 Schedule Information (NAS)

C.4 Schedule Information (NAS)


Name Schedule name

Status Schedule state

• Enable

• Disable

• Executing

Next Start Time Date and time when the next execution starts (yyyy/mm/dd hh:mm:ss)

Number of Snapshot Generations Number of Snapshot generations

Execution Period Execution period

Interval Execution interval

Start Time Time when the execution starts

Start Date Execution date

Start Time Date and time when the execution starts

Snapshot Destination Pool Destination pool for saving snapshots

Virtual Machine Snapshot Option Snapshot options for virtual machines

• Do not take virtual machine snapshot

• Snapshot the virtual machine's memory

• Quiesce guest file system (Needs VMware Tools installed)

• - (hyphen)

NAS Backup Option NAS backup options

• NAS Backup(Intra-box)

• NAS Backup(Inter-box)

• - (hyphen)



179

Appendix C List of Displayed Items C.5 NAS Volume (NAS)

C.5 NAS Volume (NAS)

C.6 NFS Datastores located on the NAS Volume (NAS)


No. Identification number (decimal) of the NAS volume

Name NAS volume name

Status Volume state

• Available

• Broken

• Data Lost

• Exposed

• Partially Exposed

• Copyback

• Redundant Copy

• Not Available

• Not Supported

• Readying

• Rebuild

• Recalculate

• Spare in Use

• Portable

• Not Ready

• Partially Exposed Rebuild

• Exposed Rebuild

• Unknown

Type Volume type

• TPV

Pool Name Thin Provisioning Pool name

Capacity NAS volume capacity (TB/GB/MB)

Used Capacity Used NAS volume capacity (TB/GB/MB)


Name NFS datastore name

Host Host where the NFS datastore is mounted



180

Appendix C List of Displayed Items C.7 Virtual Disks (Common for SAN and NAS)

C.7 Virtual Disks (Common for SAN and NAS)

C.8 Snapshots (NAS)

C.9 Single Item Restore Information (NAS)


Name Name of virtual disk

Capacity Size of virtual disk (TB/GB/MB)

Type Type of virtual disk

File Path Path to the vmdk file. If Raw Device Mapping is used for connection, the path to the datastore mapping file is displayed.


Snapshot Created Time Date and time when the snapshot is created (yyyy/mm/dd hh:mm:ss)

No. Identification number (decimal) of the destination volume (SDV) where snapshots are saved

Snapshot Name Snapshot name

Pool Name Name of the destination Thin Provisioning Pool where snapshots are cre-ated

Quiesce guest file system (Needs VMware Tools installed)

Whether a quiescent guest file system is enabled or disabled. If this item is "Yes", snapshots of virtual machines are acquired in conjunction with Windows VSS.

Snapshot the virtual machine’s memory Whether the snapshot setting of the virtual machine memory is enabled or disabled. If this item is "Yes", snapshots including memory dumps of virtual machines are acquired.


Snapshot Created Time Date and time when the snapshot is created (yyyy/mm/dd hh:mm:ss)

Auto Stop Task Status The state of the automatic stop schedule for a single item restore

• Waiting

• Executing

• Failed

Auto Stop Task Start Time Date and time when a single item restore is automatically stopped

VMDK file name VMDK file name for a single item restore



181

Appendix C List of Displayed Items C.10 Assigned Disks (Datastore) (Common for SAN and NAS)

C.10 Assigned Disks (Datastore) (Common for SAN and NAS)

C.11 Assigned Disks (Raw Device Mapping) (SAN)


Name Datastore name

Status Datastore status

Capacity Datastore size (TB/GB/MB)

Free Space Free space size in datastore (TB/GB/MB)

Type Type of file system


Name Disk name








Assigned Guest Assigned guest OS name and device name

File Path Path to the datastore mapping file

Mode Raw Device Mapping mode



182

Appendix C List of Displayed Items C.12 Assigned Disks (Others) (SAN)

C.12 Assigned Disks (Others) (SAN)

C.13 ETERNUS Details (Common for SAN and NAS)

■ Volume


Name Disk name









Name Volume name

Status Volume health status

• Available

• Broken

• Data Lost

• Exposed


• Copyback

• Redundant Copy

• Not Available

• Not Supported

• Readying

• Rebuild

• Recalculate

• Spare in Use

• Portable

• Not Ready


• Exposed Rebuild

• Unknown

LUN No. Volume No. (decimal)



183

Appendix C List of Displayed Items C.13 ETERNUS Details (Common for SAN and NAS)

Type Volume type

• For Open volumes- Standard- TPV- FTV- SDV- SDPV- WSV

• For Mainframe volumes- F6427

• For MVV volumes- MVV

• For any other volume types not listed above- Unknown

Capacity Volume size (TB/GB/MB)

Path Policy (Actually) Current path policyIf "RoundRobin" (recommended setting) is not specified, "!" is displayed.

Path Policy(Recommend)

Recommended path policy

VAAI Features (Actually)

Current VAAI feature status. "Supported" is displayed when any of the VAAI features are operational. This value is the same as the value for [Hardware Acceleration] that is displayed for vSphere Client.

VAAI Features (Recommend)

Recommended VAAI features status




184


■ RAID Group


No. RAID group No.

Name RAID group name

Status RAID group health status

• Available

• Exposed

• Broken

• Not Available

• Not Supported


• Present

• Copyback

• Redundant Copy

• Rebuild

• Recalculate

• Protected Disabled

• Verify in Progress

• Dynamic Reconfiguration

• Portable

• Spare in Use

• Failed Usable

• Formatting


• Exposed Rebuild

• No Disk Path

• SED Locked

• Unknown

Usage RAID group usage. If the RAID group is used in multiple ways, each different usage is separated by a comma and displayed.

• RDB

• Standard

• SDV

• SDPV

• TPV

• FTV

• Mainframe

• MVV

• Temporary

• TPP

• FTRP

• Unknown

• WSV

• Extreme Cache Pool



185


● Disks

■ Thin Provisioning Pool

RAID Type RAID type

• Striping (RAID0)

• Mirroring (RAID1)

• High Performance (RAID1+0)

• High Capacity (RAID5)

• Reliability (RAID5+0)

• High Reliability (RAID6)

• High Reliability (RAID6-FR)

• Unknown

Bar chart Used Capacity: Total used capacity (TB/GB/MB)Free Space: Total free capacity (TB/GB/MB)Total: Total capacity (TB/GB/MB)


Enclosure Enclosure No.

Slot No. Slot No.

Disk Type Disk type

• Online

• Nearline

• SED

• SSD

• SSD-SED

• Unknown

Capacity Capacity (TB/GB)

Speed Disk speed (rpm)

Busy Ratio Disk usage rate (%)



No. Thin Provisioning Pool (TPP) No.

Name TPP name

Disk Type Type of disks that configure the TPP

• Online

• Nearline

• SSD

• SED

• SSD-SED

• Unknown



186


RAID Type Type of RAID groups that configure the TPP







• Unknown

Status TPP health status

• Available

• Exposed

• Partially Readying

• Readying

• Maintenance

• Broken

• Data Lost

• Blockade

• Unknown

Used Status Used status of TPP

• NormalThe used capacity of the TPP is less than the attention alarm notification threshold

• AttentionThe used capacity of the TPP is less than the warning alarm notification threshold and is equal to or greater than the attention alarm notification threshold

• WarningThe used capacity of the TPP is equal to or greater than the warning alarm notification threshold

• UnknownThe used capacity of the TPP cannot be obtained

Encryption Encryption status of TPP

• CMThe TPP is encrypted by CM

• SEDThe TPP is encrypted by SED

• – (hyphen)The TPP is not encrypted

• UnknownThe encryption status of the TPP cannot be obtained

Warning Warning threshold to monitor used capacity of TPP (%)

Attention Attention threshold to monitor used capacity of TPP (%)

Bar chart • Used CapacityTotal used capacity of TPP (TB/GB/MB)

• Free SpaceTotal free capacity of TPP (TB/GB/MB)

• TotalTotal capacity of TPP (TB/GB/MB)




187


■ WSV RAID Groups

● RAID Group

All of the RAID groups that configure the WSV are displayed. The displayed information for each RAID groupis same as "RAID Group" (page 185).

■ Flexible Tier Pool


No. Flexible Tier Pool (FTRP) No.

Name FTRP name

Status FTRP health status

• Available

• Exposed


• Readying

• Maintenance

• Broken

• Data Lost

• Blockade

• Unknown

Used Status Used status of FTRP

• NormalThe used capacity of the FTRP is less than the attention alarm notification threshold

• AttentionThe used capacity of the FTRP is less than the warning alarm notification threshold and is equal to or greater than the attention alarm notification threshold

• WarningThe used capacity of the FTRP is equal to or greater than the warning alarm notification threshold

• UnknownThe used capacity of the FTRP cannot be obtained

Encryption Encryption status of FTRP

• CMThe FTRP is encrypted by CM

• SEDThe FTRP is encrypted by SED

• – (hyphen)The FTRP is not encrypted

• UnknownThe encryption status of the FTRP cannot be obtained

Warning Warning threshold to monitor used capacity of FTRP (%)



188


● Flexible Tier Sub Pool

Attention Attention threshold to monitor used capacity of FTRP (%)

Bar chart • Used CapacityTotal used capacity of FTRP (TB/GB/MB)

• Free SpaceTotal free capacity of FTRP (TB/GB/MB)

• TotalTotal capacity of FTRP (TB/GB/MB)


No. Flexible Tier Sub Pool (FTSP) No.

Name FTSP name

Status FTSP health status

• Available

• Exposed


• Readying

• Maintenance

• Broken

• Data Lost

• Blockade

• Unknown

Disk Type Type of disks that configure the FTSP

• Online

• Nearline

• SSD

• SED

• SSD-SED

• Unknown

RAID Type Type of RAID groups that configure the FTSP







• Unknown




189


■ System Information

RAID Group No. No. of RAID groups that configure the FTSPRAID group numbers are displayed with a comma at the end of each number if multiple RAID groups exist.

Bar chart • Used CapacityTotal used capacity of FTSP (TB/GB/MB)

• Free SpaceTotal free capacity of FTSP (TB/GB/MB)

• TotalTotal capacity of FTSP (TB/GB/MB)



Storage System Name Name of the ETERNUS DX

Model Name Model name of the ETERNUS DX

Product Product name of the ETERNUS DX

Serial No. Serial No. of the ETERNUS DX

Firmware Version Firmware version of running controller

Type Type of the ETERNUS DX

• SAN

• Unified

Status Health status of the total storage system

• Offline

• Normal

• Warning

• Maintenance

• Not Ready

• Error

Management URL Link to ETERNUS Web GUI



190


■ Storage Condition


System • Maximum number of VolumesMaximum number of LUNs that can be created in the storage system

• Volume CountThe number of volumes that have been created

RAID Group • Used CapacityTotal used capacity of the RAID group (TB/GB/MB).The total used capacity is the total capacity of the area that is used for the volumes of all the RAID groups. Note that RAID groups that configure TPPs and RAID groups that are registered as REC Disk Buffers are not included.

• Free SpaceTotal free capacity of the RAID group (TB/GB/MB).The total free capacity is the total unused capacity of all the RAID groups. Note that RAID groups that configure TPPs and RAID groups that are registered as REC Disk Buffers are not included.

• TotalTotal capacity of the RAID group (TB/GB/MB).The total capacity is the total of all the RAID groups registered in the storage system. Note that RAID groups that configure TPPs or RAID groups that are registered as REC Disk Buffers are not included.

RAID Group Count The number of RAID groups registered in the storage systemThis includes the number of RAID groups that configure the TPP and the number of RAID groups that are registered as REC Disk Buffers.

Volume Count The number of volumes registered in the storage systemVolumes of "Standard" or "WSV" volume type are applicable.

Thin Provisioning Pool • Used CapacityTotal used physical capacity of the TPP (TB/GB/MB).The total used physical capacity is the total of the physical capacity that is allocated to the volumes for all the TPPs.

• Free SpaceTotal free physical capacity of the TPP (TB/GB/MB).The total free physical capacity is the total of the physical capacity for areas that are not allocated to volumes for all the TPPs.

• TotalTotal physical capacity of the TPP (TB/GB/MB).The total physical capacity is the total physical capacity of all the TPPs registered in the storage system.

Thin Provisioning Pool Count

The number of TPPs registered in the storage system

Volume Count The number of volumes registered in the storage systemVolumes of "TPV" volume type are applicable.



191


■ Adapter

■ Performance

The performance information of the ETERNUS DX is displayed. When unsupported firmware is used for theETERNUS DX, or when information cannot be retrieved successfully from the ETERNUS DX, "-" is displayed.

● Host I/O

Snap Data Pool • Used CapacityTotal used capacity of the SDP (TB/GB/MB).The total used capacity is the total of the capacity that is allocated to all the SDP volumes.

• Free SpaceTotal free capacity of the SDP (TB/GB/MB).The total free capacity is the total unallocated capacity of the volumes for all of the SDPs.

• TotalTotal capacity of the SDP (TB/GB/MB).The total capacity is the total of all the SDPs registered in the storage system.

Snap Data Pool Count The number of SDPs registered in the storage system



HBA Host bus adapter name. The host name is displayed in the first brackets [ ].

Device Logical device name for host bus adapter


Port

Port location information for the ETERNUS DX (displayed only for Fibre Channel and iSCSI interfaces) Format: CM#xCA#yPort#z

x: CM numbery: CA numberz: Port number

For high-end models, the CE number is displayed before the CM number.

WWN/IP AddressWWN or iSCSI IP address for the ETERNUS DX port (displayed only for Fibre Channel and iSCSI interfaces)


Read IOPS The number of Read per second

Write IOPS The number of Write per second

Read Throughput Transmission amount of Read data per second (MB/s)

Write Throughput Transmission amount of Write data per second (MB/s)

Read Response Time Average response time (Read) per millisecond (ms)

Write Response Time Average response time (Write) per millisecond (ms)

Read Cache Hit Rate Cache hit rate (Read) (%)

Write Cache Hit Rate Cache hit rate (Write) (%)

Prefetch Cache Hit Rate Cache hit rate (Prefetch) (%)



192

Appendix C List of Displayed Items C.14 Adapter (Server Adapters) (SAN)

● Advanced Copy I/O

■ NFS Datastores located on the NAS Volume (NAS)

■ Schedule Information (NAS)

C.14 Adapter (Server Adapters) (SAN)










Name NFS datastore name

Hosts Host where the NFS datastore is mounted


Status Snapshot state

• Enable

• Disable

Number of Snapshot Generations

Number of Snapshot generations

NAS Backup Option NAS backup options

• NAS Backup(Intra-box)

• NAS Backup(Inter-box)

• - (hyphen)


Device Host bus adapter name and logical device name

Type Host bus adapter type

WWNWWN or iSCSI name for the ETERNUS DX port (displayed only for Fibre Channel and iSCSI interfaces)



193

Appendix C List of Displayed Items C.15 Adapter (Storage Targets) (SAN)

C.15 Adapter (Storage Targets) (SAN)

C.16 Adapter (Storage LUNs) (SAN)

*1: A volume for WSV, which is created by concatenating multiple RAID groups with striping, that belongs to the RAIDgroup that is first in the concatenation order.


Series Product name of the ETERNUS DX




Port

Port location information for the ETERNUS DX (displayed only for Fibre Channel and iSCSI interfaces) Format: CM#xCA#yPort#z

x: CM numbery: CA numberz: Port number

For high-end models, the CE number is displayed before the CM number.


No. Volume number

Name Volume name

Status Volume status

Type Volume type

Capacity Volume capacity (MB/GB/TB)

RAID Group/TPP/FTRP No.

The RAID group number, the TPP number, or the FTRP number to which a volume belongs.RAID group numbers are displayed with a comma at the end of each number if multiple RAID groups exist. If the type is "WSV", the RAID group number to which the representative volume (*1) belongs is displayed.

Encryption Volume encryption status

Forbid Advanced Copy Protection setting status for a volume



194

Appendix C List of Displayed Items C.17 Performance (Common for SAN and NAS)

C.17 Performance (Common for SAN and NAS)

■ Performance (Host I/O)

■ Performance (Advanced Copy I/O)



No. Volume number

Name Volume name

Type Volume type





Read Response Time Average response time (Read) per millisecond (ms)

Write Response Time Average response time (Write) per millisecond (ms)






No. Volume number

Name Volume name

Type Volume type










195

Appendix C List of Displayed Items C.18 Storage Information (Common for SAN and NAS)

C.18 Storage Information (Common for SAN and NAS)

C.19 Resource Pool Information (Common for SAN and NAS)



Status

Health status of the total storage system

• Offline

• Normal

• Warning

• Maintenance

• Not Ready

• Error

Product Product ID of the ETERNUS DX

Type

Type of the ETERNUS DX

• SAN

• Unified


Firmware Version Firmware version of running controller


Management URL Link to ETERNUS Web GUI


Resource Name Resource name

Resource Type

Resource type

• RAID Group

• Thin Provisioning Pool



IP Address Management IP address of the ETERNUS DX



196

Appendix C List of Displayed Items C.20 ETERNUS SF Connection information (NAS)

C.20 ETERNUS SF Connection information (NAS)


IP Address IP address of ETERNUS SF

User ID ETERNUS SF user name

Connection

Connection state with ETERNUS SF

• Connected

• Not connected

ETERNUS SF Manager

OS of the ETERNUS SF management server

• Windows

• Linux

• Solaris

Method

Execution method for the AdvancedCopy Manager CCM commands

• PowerShell

• SSH

Protocol

Protocol that is used to communicate with ETERNUS SF

• http

• https

Port No. Port number that is used to communicate with ETERNUS SF

AdvancedCopy Manager CCM Command Path (bin Directory)

File path of the AdvancedCopy Manager CCM commands on ETERNUS SF

Operation Method

Operation method for backups between storage systems

• Data Protection

• Stand-by

• Not Set

Inter-box Backup Script Path

File path of the backup script between storage systems on ETERNUS SF



197

Appendix D

Messages

D.1 Common for SAN and NAS

D.1.1 Performance Information

■ STXE1000

[Message]STXE1000 NOTICE Please click "Refresh" button to display information of the object specified at inventorytree if the specified object consists of the volume that is supported by the ETERNUS vCenter Plug-in.

[Cause]The object selected in the inventory tree is not registered in the database of ETERNUS vCenter Plug-in.

[Solution]Execute Refresh. For details, refer to "3.4 Refreshing Displayed Information" (page 48).

■ STXE1001

[Message]STXE1001 NOTICE This ETERNUS Disk Storage System is not registered. Register by Registration.

[Cause]The selected ETERNUS DX is not registered in ETERNUS vCenter Plug-in.

[Solution]Start GUI for storage system registration and register the storage system. For details, refer to "3.5.2Registering ETERNUS DX Storage Systems" (page 50).

■ STXE1002

[Message]STXE1002 NOTICE ETERNUS vCenter Plug-in does not support this kind of ETERNUS disk storage system.

[Cause]The selected ETERNUS DX storage systems is not supported by ETERNUS vCenter Plug-in.

[Solution]Unnecessary.

■ STXE1003

[Message]STXE1003 NOTICE ETERNUS vCenter Plug-in does not support this type of volume.



198

Appendix D Messages D.1 Common for SAN and NAS

[Cause]The selected volume is not supported by ETERNUS vCenter Plug-in.


■ STXE1005

[Message]STXE1005 ERROR Detail information was not able to be acquired from ETERNUS disk storage systemnormally because of invalid credentials.

[Cause]Information was not able to be acquired from the ETERNUS DX that was registered to ETERNUS vCenterPlug-in by using the storage system registration function normally because the account or password of theETERNUS DX is invalid. The account information might have been changed after registered to ETERNUSvCenter Plug-in with the storage system registration function.

[Solution]Unregister the ETERNUS DX from GUI for storage system registration and then re-register it. For details,refer to "6.1 Changing Settings for ETERNUS DX Storage Systems" (page 163).

■ STXE1006

[Message]STXE1006 ERROR Detail information was not able to be acquired from ETERNUS disk storage systemnormally because another user is using exclusive software of the ETERNUS vCenter Plug-in. Please click"Refresh" button after checking no one is using exclusive software.

[Cause]Information was not able to be acquired from the ETERNUS DX normally because another user was usingexclusive software of ETERNUS vCenter Plug-in. For details, refer to "1.6 Exclusive Software" (page 19).

[Solution]Stop exclusive software of ETERNUS vCenter Plug-in, and then execute Refresh.

■ STXE1007

[Message]STXE1007 ERROR Detail information was not able to be acquired from ETERNUS disk storage systemnormally because a login account specified by the registration tool does not have a software role. Please loginthe ETERNUS Web GUI and give a software role to a user account using by the ETERNUS vCenter Plug-in,and click "Refresh" button.

[Cause]Information was not able to be acquired from the ETERNUS DX that was registered to ETERNUS vCenterPlug-in by using the storage system registration function normally because the account of the ETERNUS DXdoes not have the Software role. The account information might have been changed after registered toETERNUS vCenter Plug-in with the storage system registration function.

[Solution]Grant the Software role to a configured account using ETERNUS Web GUI. Then execute Refresh.



199


■ STXE1008

[Message]STXE1008 ERROR Detail information was not able to be acquired from ETERNUS disk storage systemnormally because of a transport error." Please click "Refresh" button after fixing network issues.

[Cause]Information was not able to be acquired from the ETERNUS DX normally because of a network errorbetween the server where ETERNUS vCenter Plug-in is installed and the ETERNUS DX.

[Solution]Check for any problems in network connection. Solve the problem and then execute Refresh.

■ STXE1009

[Message]STXE1009 ERROR Detail information was not able to be acquired from ETERNUS disk storage systemnormally because of an internal error.

[Cause]Information was not able to be acquired from the ETERNUS DX normally because of a detected internalerror.

[Solution]Refer to "Chapter 7 Required Information for Failure Investigation" (page 167) to prepare the requiredinformation, and contact a Fujitsu engineer.

■ STXE1010

[Message]STXE1010 ERROR Detail information was not able to be acquired from a vSphere server normally becauseof invalid credentials.

[Cause]Information was not able to be acquired from the vSphere Server normally because of invalid account orpassword of the vCenter Server where ETERNUS vCenter Plug-in is installed. The account or password of thevCenter Server might have been changed after installation of ETERNUS vCenter Plug-in.

[Solution]Refer to "6.2 Changing Settings for Windows Server Where vCenter Server Is Installed" (page 164).

■ STXE1011

[Message]STXE1011 ERROR Detail information was not able to be acquired from a vSphere server normally becauseof a transport error or invalid credentials.

[Cause]Information was not able to be acquired from the vSphere Server normally because of a network errorbetween the server where ETERNUS vCenter Plug-in is installed and the vCenter Server, or because of aninvalid account information of the vCenter Server.

[Solution]Check for any problems in network connection. If no problem is found, check for any errors in the accountinformation. For details, refer to "6.2 Changing Settings for Windows Server Where vCenter Server IsInstalled" (page 164). Solve the problem and then execute Refresh.



200


■ STXE1012

[Message]STXE1012 ERROR Detail information was not able to be acquired from a vSphere server normally becauseof an internal error.

[Cause]Information was not able to be acquired from the vSphere Server normally because of a detected internalerror.


■ STXE1013

[Message]STXE1013 ERROR Detail information was not able to be acquired from a vSphere server normally becauseof wrong configuration files.

[Cause]The configuration file of ETERNUS vCenter Plug-in is invalid.


■ STXE1014

[Message]STXE1014 NOTICE There is no supported ETERNUS Disk Storage system device on the selected vmwareobject.

[Cause]No disks for the ETERNUS DX exist for the selected resource.


■ STXE1015

[Message]STXE1015 NOTICE The license is currently not registered.

[Cause]A license for the Advanced Copy functions or the Thin Provisioning function is not registered.

[Solution]Use ETERNUS Web GUI to register a license.

■ STXE1016

[Message]STXE1016 NOTICE This ETERNUS Disk Storage System does not support this resource.



201


[Cause]The resource is not supported.


■ STXE1017

[Message]STXE1017 NOTICE The datastore that is accessible from multiple hosts is not supported in this function.The information on this datastore can be confirmed with Host System.

[Cause]The information about the datastore that is used by multiple hosts cannot be displayed.

[Solution]Select the host that uses the target datastore from the inventory tree, click the [FUJITSU ETERNUS DX] tab,and use [Datastore] to display the information.

■ STXE1018

[Message]STXE1018 ERROR ETERNUS vCenter Plug-in does not support this type of volume. Or, detail information was not able to be acquired from ETERNUS disk storage system.

[Cause]The selected volume is not supported by ETERNUS vCenter Plug-in or information was not able to beacquired from the ETERNUS DX.

[Solution]Check if the selected volume is supported by ETERNUS vCenter Plug-in.When the selected volume is not supported, no action is necessary.When the selected volume is supported, execute Refresh.

■ STXE1019

[Message]STXE1019 NOTICE This ETERNUS Disk Storage System is not registered, or is not supported by ETERNUSvCenter Plug-in. Register by Registration.

[Cause]The selected ETERNUS DX is not registered in ETERNUS vCenter Plug-in or the selected ETERNUS DX is notsupported by ETERNUS vCenter Plug-in.

[Solution]Start GUI for storage system registration and register the storage system. For details, refer to "3.5.2Registering ETERNUS DX Storage Systems" (page 50).



202


D.1.2 Registering Storage Systems

■ STXE2001

[Message]STXE2001 ERROR Input information has already been registered.

[Cause]The specified ETERNUS DX is already registered in ETERNUS vCenter Plug-in.


■ STXE2002

[Message]STXE2002 ERROR Registration failed because of invalid credentials.

[Cause]The specified ETERNUS DX has an invalid account or password.

[Solution]Specify a valid account and password.

■ STXE2003

[Message]STXE2003 ERROR Registration failed because specified user account does not have a software role.Please retry after giving a software role to a user account by using ETERNUS Web GUI.

[Cause]The specified ETERNUS DX account does not have the Software role.

[Solution]Specify a user account with the Software role.

■ STXE2004

[Message]STXE2004 ERROR Registration failed because of a transport error. Please retry after fixing network issues.

[Cause]The specified ETERNUS DX was not able to be connected. The network or the SSH connection setting of theETERNUS DX has an error.

[Solution]Check the network connection or check the SSH connection setting of the ETERNUS DX for any problems.Solve the problem, and then perform registration again.

■ STXE2005

[Message]STXE2005 ERROR Registration failed because of an internal error.



203


[Cause]An internal error was detected.


■ STXE2006

[Message]STXE2006 ERROR The error occurred because of wrong configuration files.

[Cause]The configuration file of ETERNUS vCenter Plug-in is invalid.


■ STXE2007

[Message]STXE2007 ERROR The operation failed because of invalid credential of ETERNUS disk storage system.

[Cause]The operation failed for the ETERNUS DX that was registered to ETERNUS vCenter Plug-in by using thestorage system registration function because the account or password of the ETERNUS DX is invalid. Theaccount information might have been changed after registered to ETERNUS vCenter Plug-in with thestorage system registration function.

[Solution]Unregister the ETERNUS DX from GUI for storage system registration and then re-register it. For details,refer to "6.1 Changing Settings for ETERNUS DX Storage Systems" (page 163).

■ STXE2008

[Message]STXE2008 ERROR The operation failed because a login account specified by the registration tool does nothave a software role. Please login the ETERNUS Web GUI and give a software role to a user account using bythe ETERNUS vCenter Plug-in.

[Cause]The operation failed for the ETERNUS DX that was registered to ETERNUS vCenter Plug-in by using thestorage system registration function because the account of the ETERNUS DX does not have the Softwarerole.The account information might have been changed after registered to ETERNUS vCenter Plug-in with thestorage system registration function.

[Solution]Grant the Software role to a configured account using ETERNUS Web GUI.

■ STXE2009

[Message]STXE2009 ERROR The operation failed because of a transport error. Please retry after fixing network issues.



204


[Cause]The specified ETERNUS DX was not able to be connected. The network or the SSH connection setting of theETERNUS DX has an error.

[Solution]Check the network connection or check the SSH connection setting of the ETERNUS DX for any problems.Solve the problem, and then perform the operation again.

■ STXE2010

[Message]STXE2010 ERROR The operation failed because of an internal error.



■ STXE2011

[Message]STXE2011 ERROR The operation failed because another user was using exclusive software of the ETERNUSvCenter Plug-in.

[Cause]The operation failed because another user was using exclusive software of ETERNUS vCenter Plug-in. Fordetails on exclusive software, refer to "1.6 Exclusive Software" (page 19).

[Solution]Stop the exclusive software of ETERNUS vCenter Plug-in, and perform the operation again.

■ STXE2012

[Message]STXE2012 ERROR The resource does not exist in this ETERNUS Disk Storage System.

[Cause]One of the following resources is specified when adding a resource with the Register Resource Wizard.

- A resource that does not exist in the ETERNUS DX- A RAID group without registered Standard volumes, WSVs, SDVs, or SDPVs

[Solution]Check the following conditions and then try again.

- The resource that is to be registered exists in the ETERNUS DX- Only a RAID group with registered Standard volumes, WSVs, SDPs, or SDPVs is selected

■ STXE2013

[Message]STXE2013 ERROR ETERNUS vCenter Plug-in does not support this resource.



205


[Cause]A resource that ETERNUS vCenter Plug-in does not support was specified when adding a resource in theRegister Resource Wizard or the resource that was selected in the LUN Provisioning Wizard does not exist.

[Solution]Make sure a resource that ETERNUS vCenter Plug-in supports or a resource that exists is specified.

D.1.3 evcpConfig Command

■ Message

[Cause]The command is executed by an account without the execution privileges.

[Solution]Execute the command with the built-in administrator privileges. A user belonging to the Administratorgroup must execute the command with the administrator privileges.

■ Message

[Cause]ETERNUS vCenter Plug-in is not properly installed.

[Solution]Uninstall ETERNUS vCenter Plug-in and then install it again.

■ Message

[Cause]The command argument is invalid.

[Solution]Specify a correct argument.

■ Message

[Cause]This command is running in another process. Multiple instances of this command cannot be started.

[Solution]After the command in another process is complete, execute it again.

[ERROR] This command requires administrative rights.

[ERROR] ETERNUS vCenter Plug-in has not installed correctly.

[ERROR] Invalid Argument.

[NOTICE] evcpConfig command is already running.



206


■ Message



■ Message

[Cause]The entered vCenter Server account or password is incorrect.

[Solution]Enter a valid account and password.

■ Message

[Cause]A connection to the vCenter Server of the specified IP address could not be established.

[Solution]Specify a valid IP address for the vCenter Server. If the specified IP address is valid, check for any problemsthat may exist in the network connection. Fix any problems, and then try again.

■ Message

[Cause]Registration of the vCenter Server in ETERNUS vCenter Plug-in or deletion of the vCenter Server fromETERNUS vCenter Plug-in failed.

[Solution]Refer to "Chapter 7 Required Information for Failure Investigation" (page 167) to prepare any requiredinformation for troubleshooting, and then contact a Fujitsu engineer.

[ERROR] Failed to create JAVA VM.[ERROR] Failed to Find Class.[ERROR] Failed Get Method.[ERROR] Failed to get computer name.

[ERROR] Invalid login account or password.

[ERROR] Invalid IP address(transport error).

[ERROR] Plug-in Registration failed.[ERROR] Plug-in Unregistration failed.



207


D.1.4 Adding and Deleting Datastores/Volumes

If datastores/volumes are added or deleted, messages that are described in "D.1.1 Performance Information"(page 198) and "D.1.2 Registering Storage Systems" (page 203) may be displayed as well as the messagesthat are described in this section.

■ 1027

[Cause]Invalid characters were specified for the volume name.

[Solution]Make sure the volume name is specified correctly, and then try again.

■ 2012

[Cause]Information was not able to be acquired from the ETERNUS DX that was registered to ETERNUS vCenterPlug-in by using the storage system registration function normally because the account or password of theETERNUS DX is invalid. The account information might have been changed after registered to ETERNUSvCenter Plug-in with the storage system registration function.

[Solution]Unregister the ETERNUS DX from GUI for storage system registration and then re-register it.

■ 2013

[Cause]Information was not able to be acquired from the ETERNUS DX that was registered to ETERNUS vCenterPlug-in by using the storage system registration function normally because the account of the ETERNUS DXdoes not have the Software privilege. The account information might have been changed after registeredto ETERNUS vCenter Plug-in with the storage system registration function.

[Solution]Unregister the ETERNUS DX from GUI for storage system registration and then re-register it.

■ 4015

[Cause]The exclusive software of ETERNUS vCenter Plug-in is being used by another user.

[Solution]Stop the exclusive software of ETERNUS vCenter Plug-in that is running, and then try again.

■ 4018

[Cause]The specified RAID group is not registered in the ETERNUS DX.

[Solution]Specify a RAID group that is registered in the ETERNUS DX, and then try again.



208


■ 4028

[Cause]The operation cannot be performed because the specified RAID group is for work.

[Solution]Specify a RAID group in the ETERNUS DX that is not being used for work, and then try again.

■ 4042

[Cause]The specified volume is not registered in the ETERNUS DX.

[Solution]Specify a volume that is already registered in the ETERNUS DX, and then try again.

■ 4045

[Cause]The specified volume name is already registered in the ETERNUS DX.

[Solution]Enter a volume name that is not registered in the ETERNUS DX, and then try again.

■ 4065

[Cause]The maximum number of host affinities that can be created for one port has been exceeded.

[Solution]Delete the host affinities that exceed the maximum, make sure the maximum number of host affinitiesthat can be created for one port is not exceeded, and then try again.

■ 4067

[Cause]The maximum number of volumes that can be created for the RAID group has been exceeded.

[Solution]Delete the volumes that exceed the maximum, make sure the maximum number of volumes that can becreated for one RAID group is not exceeded, and then try again.

■ 4068

[Cause]The specified RAID group is in error status.

[Solution]When the status for the specified RAID group changes to normal, and then try again.

■ 4070

[Cause]The maximum number of volumes that can be created in a single ETERNUS DX has been exceeded.



209


[Solution]Delete the volumes that exceed the maximum, make sure the maximum number of volumes that can becreated for one ETERNUS DX is not exceeded, and then try again.

■ 4071

[Cause]The specified RAID group is undergoing LDE.

[Solution]Wait for LDE of the RAID group to complete, and then try again.

■ 4074

[Cause]The specified volume is undergoing an Advanced Copy.

[Solution]Wait for the Advanced Copy process to compete, and then try again.

■ 4089

[Cause]The specified volume is undergoing RAID migration.

[Solution]Stop RAID migration that is running, and then try again.

■ 4099

[Cause]The specified RAID group is blocked.

[Solution]When the RAID group status changes to normal, and then try again.

■ 4119

[Cause]The maximum volume capacity that can be created for an ETERNUS DX has been exceeded.

[Solution]Delete the capacity that exceeds the maximum, make sure the maximum volume capacity that can becreated for one ETERNUS DX is not exceeded, and then try again.



210


■ 4121

[Cause]The functions for the ETERNUS DX are disabled.

[Solution]If an Advanced Copy license is not registered, register it. If an Advanced Copy license is already registered, refer to "Chapter 7 Required Information for FailureInvestigation" (page 167) to prepare any required information for troubleshooting, and then contact aFujitsu engineer.

■ 5002


[Solution]Possible causes are as follows:

- The ETERNUS DX is in error status- One or more parts in the ETERNUS DX failed- The network environment is not correctly set - The LAN connection is not correctly set- The maximum number of installable disks has been exceeded

Check and correct any of the possible causes that are listed above, wait for a while, and then try again.If the problem persists, refer to "Chapter 7 Required Information for Failure Investigation" (page 167) toprepare any required information for troubleshooting, and then contact a Fujitsu engineer.

■ 7004

[Cause]Communication between the server in which ETERNUS vCenter Plug-in is installed and the ETERNUS DXfailed.

[Solution]Check for any problems in the network connection. Fix any problems, and then try again.

■ 8002

[Cause]The size of the specified volume is not valid.

[Solution]Specify a volume size that is in the valid size range, and then try again. For more details about the valid size range of a volume, refer to "ETERNUS Web GUI User's Guide".

■ 8071

[Cause]Deletion of the LUN group mapping information failed.

[Solution]If exclusive software of ETERNUS vCenter Plug-in is running, stop the exclusive software and then try again.If exclusive software of ETERNUS vCenter Plug-in is not running, refer to "Chapter 7 Required Information



211


for Failure Investigation" (page 167) to prepare any required information for troubleshooting, and thencontact a Fujitsu engineer.

■ 8080

[Cause]The available resources are insufficient.

[Solution]Check the capacity of the RAID group or the Thin Provisioning Pool. If the capacity is sufficient, fix any otherpossible problems such as the maximum number of affinity groups that can be registered being exceeded.

■ 8101

[Cause]The memory is insufficient.

[Solution]Obtain a sufficient amount of memory, and then try again.

■ 8110

[Cause]The specified Thin Provisioning Pool or LUN group is not registered in the ETERNUS DX.

[Solution]Specify a Thin Provisioning Pool or LUN group that is registered in the ETERNUS DX, and then try again.

■ 8151

[Cause]Startup or shutdown of the ETERNUS DX is currently being performed.

[Solution]Wait for the startup or shutdown process of the ETERNUS DX to complete, and then try again.

■ 8156

[Cause]The RAID group to which the specified volume belongs is undergoing LDE.

[Solution]Wait for LDE of the RAID group to complete, and then try again.

■ D010

[Cause]Encryption was specified for a RAID group that is configured with SEDs.

[Solution]Specify encryption for a RAID group that is not configured with SEDs.



212

Appendix D Messages D.2 NAS

■ E007

[Cause]The specified volume is undergoing an Advanced Copy (Offloaded Data Transfer Copy).

[Solution]Wait for the Advanced Copy process to complete, and then try again.

■ STXE2014

[Cause]The created volume was not recognized by a host even after an extended period of time. The processfinished without creating a datastore.

[Solution]Check if the created volume is recognized by vSphere Web Client. If the created volume is recognized,convert it to a datastore manually. If the created volume is not recognized, scan the host HBA again, andcheck if the created volume is recognized.

■ STXE2015

[Cause]Rescanning of HBAs for the host failed.

[Solution]Rescan the HBAs of the target host from vSphere Web Client. After scanning is complete, make sure thatthe added datastore/volume exists in vSphere Web Client and that the deleted datastore/volume does notexist.

■ For error numbers other than the above

[Cause]An error was detected.


D.2 NAS

D.2.1 Provisioning

■ STXE5000

[Message]STXE5000 ERROR The specified datastore already exists. Please specify another datastore name.

[Cause]The datastore cannot be created because the specified datastore already exists.



213


[Solution]Specify another datastore name.

■ STXE5001

[Message]STXE5001 ERROR The datastore cannot be mounted to host. After you check the status of the host, mountthe created datastore again from [New Datastore] by using the vSphere Web Client.

[Cause]The created datastore cannot be mounted to the host.

[Solution]Check the status of the host, and then mount the datastore that was created using [New Datastore] under[All vCenter Actions] from the vSphere Web Client actions.

■ STXE5020

[Message]STXE5020 ERROR Please specify NFS allow host in 1023 characters.

[Cause]The number of characters that are specified for the NFS allowed host exceeds 1023.

[Solution]Specify the NFS allowed host within 1023 characters.

■ STXE5030

[Message]STXE5030 ERROR Please specify volume capacity with a maximum volume size of 128TB.

[Cause]The volume capacity is invalid.

[Solution]Specify the volume capacity within 128TB.

■ STXE5031

[Message]STXE5031 ERROR Failed to expand the selected volume because backup schedule exists or snapshot set-ting exists in the storage. Delete the existing schedule or snapshot setting and try again.

[Cause]The selected volume cannot be expanded because a backup schedule exists or a snapshot setting exists inthe storage system.

[Solution]Take the following actions, and then expand the volume:

- If a schedule is set for the selected volume, delete the schedule.- If a snapshot setting exists in the storage system, delete the snapshot setting.



214


■ STXE5103

[Message]STXE5103 ERROR No registered host exists in the specified cluster.

[Cause]The datastore cannot be created because no registered host exists in the specified cluster.

[Solution]Register the host to the cluster, and then try again.

D.2.2 Backup

■ STXE5100

[Message]STXE5100 ERROR The schedule is already registered. Either modify the schedule or delete the schedule,then try again.

[Cause]The schedule cannot be created because the schedule is already registered or data inconsistency hasoccurred.

[Solution]Perform either of following actions.

- Perform a schedule modification.- Delete the schedule, and then re-create the schedule.

■ STXE5101

[Message]STXE5101 ERROR The start time of the schedule cannot be past time. Specify the start time of the scheduleand try again.

[Cause]The schedule cannot be created because a past time is specified for the start time.

[Solution]Specify a time that is later than the current time for the start time of the schedule, and then try again.

■ STXE5102

[Message]STXE5102 ERROR The maximum generation is set to 0. If you want to create a schedule that creates NASbackup but does not create snapshot, please specify "Create NAS Backup" as NAS backup option.

[Cause]If the number of generations is set to 0, the backup option (or the setting for acquiring a NAS backup)must be enabled.

[Solution]To create a schedule that creates only a NAS backup without creating a snapshot, select the [Create NASBackup].To create a snapshot, set the number of snapshot generations to one or more.



215


■ STXE5104

[Message]STXE5104 ERROR The specified schedule already exits. Please specify another schedule name.

[Cause]Cannot create the specified schedule because the schedule name already exists.

[Solution]Specify another schedule name.

■ STXE5105

[Message]STXE5105 ERROR The operation cannot be executed because an automatically snapshot schedule alreadyexists in the storage side, you can not create a schedule.

[Cause]The schedule cannot be created because snapshots are created with the automatic acquisition mode in thestorage system.

[Solution]In the storage system, delete the snapshot schedule in which the acquisition mode is set to automatic andthen re-create the schedule.

■ STXE5110

[Message]STXE5110 ERROR The specified schedule does not exist. Please click [Refresh] button, check the detail ofthe schedule and try again.

[Cause]The specified schedule cannot be changed because the schedule does not exist.

[Solution]Click the [Refresh] button to refresh the screen display. Check that the schedule exists, and then try again.

■ STXE5111

[Message]STXE5111 ERROR The operation cannot be executed because an automatically snapshot schedule alreadyexists in the storage side, you can not modify a schedule.

[Cause]The schedule cannot be modified because an automatic schedule that regularly creates a snapshot alreadyexists in the storage system.

[Solution]Perform the following actions.

(1) Delete the schedule of the modification target with ETERNUS vCenter Plug-in.

(2) In the storage system, delete the snapshot schedule in which the acquisition mode is set to automatic and then re-create the schedule.

(3) Create the schedule again with ETERNUS vCenter Plug-in.



216


■ STXE5130

[Message]STXE5130 ERROR The operation cannot be executed because an already executed [run only once] schedulecannot be enabled.

[Cause]The specified "Once" schedule cannot be enabled because the schedule is already executed.

[Solution]None.

■ STXE5131

[Message]STXE5131 ERROR The schedule is already enabled.

[Cause]The specified schedule cannot be enabled because the schedule is already enabled.

[Solution]None.

■ STXE5132

[Message]STXE5132 ERROR The schedule is already disabled.

[Cause]The specified schedule cannot be disabled because the schedule is already disabled.

[Solution]None.

■ STXE5140

[Message]STXE5140 ERROR Failed to create snapshot of the virtual machine. For detail information, please refer tothe task console.

[Cause]The execution of the schedule failed because the creation of a snapshot of the virtual machine failed.

[Solution]Check the details of the error in the Task Console. Resolve the error, and then try again.

■ STXE5141

[Message]STXE5141 ERROR Failed to execute the schedule. detail: {}

[Cause]The execution of the schedule failed.

[Solution]Perform the following operations, and then try again:



217


- Check the state of the vCenter Server. If an error has occurred, resolve the error.- Check the connection status between the vCenter Server and the host. If an error has occurred, resolve

the error.- If a detailed message is output, refer to "Error Messages/Error Codes" in "ETERNUS CLI User's Guide" to

check the error number that was output in the message and resolve the error.

■ STXE5142

[Message]STXE5142 ERROR The selected schedule has been disabled. Enable the schedule and try again.

[Cause]The execution of the specified schedule failed because the schedule is disabled.

[Solution]Enable the schedule, and then try again.

■ STXE5143

[Message]STXE5143 ERROR The Schedule Execution task has been canceled.

[Cause]The task for executing the schedule has been canceled.

[Solution]None.

■ STXE5144

[Message]STXE5144 ERROR The NAS volume that is set in the schedule does not exist. The NAS volume may havebeen deleted on the storage side. If this is an unnecessary schedule, please delete it.

[Cause]The NAS volume may have been deleted on the storage system. The schedule cannot be executed becausethe NAS volume does not exist.

[Solution]Delete the schedule.

■ STXE5145

[Message]STXE5145 ERROR The execution of the schedule has completed, but virtual machine that failed to get ordelete the VM snapshot exist. Refer to task console to get detail error information, then fix the issues.

[Cause]The execution of the schedule has completed, but a virtual machine that failed to acquire or delete the VMsnapshot exists.

[Solution]Resolve the cause of the failure for the VM snapshot acquisition and deletion. Perform [Backup Now] asnecessary.



218


■ STXE5150

[Message]STXE5150 ERROR Intra-box backup setting of the NAS volume does not exist, or is incorrect. Please login to[ETERNUS SF Web Console], confirm NAS backup setting and try again.

[Cause]The settings of NAS volume backup within a single ETERNUS DX do not exist, or the settings are incorrect.

[Solution]Log in to the ETERNUS SF Web Console and check the settings of the NAS backup. After checking that thesettings of the NAS backup are correct, perform [Backup Now] as necessary.

■ STXE5151

[Message]STXE5151 ERROR Inter-box backup setting of the NAS volume does not exist or is incorrect. Please login to[ETERNUS SF Web Console], confirm inter-box backup setting and try again.

[Cause]The settings of the NAS volume backup between ETERNUS DX storage systems do not exist, or the settingsare incorrect.

[Solution]Log in to the ETERNUS SF Web Console and check the settings of the NAS volume backup betweenETERNUS DX storage systems. After checking that the NAS backup settings between ETERNUS DX storagesystems are correct, perform [Backup Now] as necessary.

■ STXE5152

[Message]STXE5152 ERROR Please check the network status, ETERNUS SF registration information and try again afterfixing the issues.

[Cause]The NAS backup cannot be executed because a connection to the ETERNUS SF cannot be established.


- Check the network status and the connection status between the vCenter Server and the ETERNUS SF.- Check the status of the ETERNUS SF Manager.- Check if the AdvancedCopy Manager CCM command of the ETERNUS SF Manager can be run remotely

from PowerShell or SSH.- If a detailed message is output, resolve the error by referring to the "ETERNUS SF Messages" to check

the error number that is output in the message.

■ STXE5153

[Message]STXE5153 ERROR Failed to create inter-box backup of the NAS volume. detail: {}

[Cause]The creation of the NAS backup failed.



219



- Check the network status and the connection status between the vCenter Server and the ETERNUS SF.- Check the status of the ETERNUS SF Manager.- If a detailed message is output, resolve the error by referring to the "ETERNUS SF Messages" to check


■ STXE5154

[Message]STXE5154 ERROR Failed to get copy group list. detail: {}

[Cause]The acquisition of the copy group list failed.


- Check the connection status between the vCenter Server and the ETERNUS SF.- Check the status of the ETERNUS SF Manager.- If a detailed message is output, resolve the error by referring to the "ETERNUS SF Messages" to check


■ STXE5155

[Message]STXE5155 ERROR Failed to get copy group information. detail: {}

[Cause]The acquisition of the copy group information failed.


- Check the connection status between the vCenter Server and the ETERNUS SF.- Check the status of the ETERNUS SF Manager.- If a detailed message is output, resolve the error by referring to the "ETERNUS SF Messages" to check


■ STXE5156

[Message]STXE5156 ERROR Failed to create inter-box backup of the NAS volume. For details, please refer to ETERNUSSF Web Console.

[Cause]A NAS volume backup between ETERNUS DX storage systems cannot be created.


- Check the network status and the connection status between the vCenter Server and the ETERNUS SF.- Check the status of the ETERNUS SF Manager.- If an end status is output in a message, resolve the error by referring to the "ETERNUS SF Messages" to

check the end status that is output in the message.



220


■ STXE5157

[Message]STXE5157 ERROR Failed to check the copy progress of the inter-box backup of the NAS volume. For details,please refer to ETERNUS SF Web Console.

[Cause]The progress of the NAS volume backup between ETERNUS DX storage systems could not be checked.


- Check the network status and the connection status between the vCenter Server and the ETERNUS SF.- Check the status of the ETERNUS SF Manager.- If an end status is output in a message, resolve the error by referring to the "ETERNUS SF Messages" to

check the end status that is output in the message.

■ STXE5160

[Message]STXE5160 ERROR Virtual machine restore or single item restore is already executed. After the restore com-pleted or after cancel the restore task in the task console, try again.

[Cause]Virtual machine restore or single item restore failed because the virtual machine restore or the single itemrestore is being executed.

[Solution]After the virtual machine restore or single item restore is completed or after canceling the restore in theTask Console, try it again.

■ STXE5161

[Message]STXE5161 ERROR Virtual machine restore or single item restore is already executed. After the restore com-pleted or after cancel the restore task in the task console, try again. If he execution of the schedule wasinterrupted, please executed [Backup Now] as necessary.

[Cause]Virtual machine restore or single item restore failed because the virtual machine restore or the single itemrestore is being executed.

[Solution]After the virtual machine restore or single item restore is completed or after canceling the restore in theTask Console, try it again.If the execution of the schedule is interrupted, perform [Backup Now] to acquire a backup as necessary.



221


D.2.3 Restore

■ STXE5200

[Message]STXE5200 ERROR The operation failed because there is an error occurred when powering off the virtualmachine. Either check the status of the virtual machine or power off the virtual machine first, and then tryagain.

[Cause]The restore cannot be executed because powering off the virtual machine failed.

[Solution]Resolve the cause of the failure in powering off the virtual machine, and then perform the following proce-dure:

(1) Perform the restore again, or use [Shut Down Guest OS] in vSphere Web Client to power off the vir-tual machine, and then try the restore again.

(2) Perform [Enable Schedule] to enable the schedule as necessary.

■ STXE5201

[Message]STXE5201 ERROR The operation failed because there is an error occurred when powering on the virtualmachine. Check the status of the virtual machine and power on it.

[Cause]The virtual machine restore is completed, but powering on the virtual machine failed.

[Solution]Resolve the cause of the failure in powering on the virtual machine, and then perform the following proce-dure:

(1) Select the registered virtual machine, and then execute [Power On] in vSphere Web Client.If the message "This virtual machine might have been moved or copied. In order to configure certainmanagement and networking features, VMware ESX needs to know if this virtual machine wasmoved or copied. If you don't know, answer "I copied it"." is displayed, select "I copied it".


■ STXE5202

[Message]STXE5202 ERROR The virtual machine cannot be removed from the inventory. Either confirm the status ofthe virtual machine or power off the virtual machine first, and then try again.

[Cause]The restore failed because the virtual machine cannot be removed from the inventory.

[Solution]Resolve the cause of the failure in canceling the registration of the virtual machine, and then perform thefollowing procedure:



222


(1) Perform the restore again.


■ STXE5203

[Message]STXE5203 ERROR There is an error occurred when registering the virtual machine to the inventory. Pleaseregister the virtual machines that exists in the datastore that has been restored from "New VirtualMachine" by using the vSphere Web Client.

[Cause]The inventory registration of the restored virtual machine failed.

[Solution]Resolve the cause of the failure in the registration of the virtual machine, and then perform the followingprocedure:

■ If an error occurred in a virtual machine restore (to the selected VM)

(1) Execute [Register VM] in vSphere Web Client to register the virtual machine of the restore target to the inventory.

(2) Select the registered virtual machine, and then execute [Edit Settings] in vSphere Web Client.

(3) Delete all hard disks whose capacity is 0 and for which an error is displayed. Before deleting them, enter "1" or a larger value in the capacity field.

(4) Select the registered virtual machine, and then open [Manage Snapshots] in vSphere Web Client. If the name of the latest snapshot is "EVCP_SCHEDULE_VMSNAP", execute [Revert to].Note that if "EVCP_SCHEDULE_VMSNAP" does not exist or the snapshot is not the latest one, do not execute it.

(5) If [Revert to] was executed in Step (4), delete "EVCP_SCHEDULE_VMSNAP".



■ If an error occurred in a virtual machine restore (to the other VM)

(1) If a folder with the same name as the specified virtual machine name in Step 3 exists in the data-store that was selected in Step 5 of "4.5.1 Restoring a Virtual Machine" (page 123), delete the folder.

(2) Perform the restore of the virtual machine again.


■ STXE5204

[Message]STXE5204 ERROR There is an error occurred when restoring the virtual machine from VM snapshot. Checkthe status of the virtual machine, if VM snapshot exists, restore the virtual machine from "Snapshots" byusing the vSphere Web Client.



223


[Cause]The restore of the virtual machine from the VM snapshot failed.

[Solution]Resolve the cause of the failure in restoring from the VM snapshot, and then perform the following proce-dure:

■ If an error occurred for a virtual machine restore (to the selected VM)







(2) Delete the folder with the same name as the specified virtual machine name in Step 3 that exists in the datastore that was selected in Step 5 of "4.5.1 Restoring a Virtual Machine" (page 123).



■ STXE5205

[Message]STXE5205 ERROR There is an error occurred when deleting VM snapshot. Check the status of the virtualmachine, if VM snapshot exists, delete VM snapshot from "Snapshots" by using the vSphere Web Client.

[Cause]The deletion of the virtual machine snapshot failed.

[Solution]Resolve the cause of the failure in deleting the VM snapshot, and then perform the following procedure:


(1) Select the registered virtual machine, and then open [Manage Snapshots] in vSphere Web Client. If the name of the latest snapshot is "EVCP_SCHEDULE_VMSNAP", delete the snapshot.

(2) Select the registered virtual machine, and then execute [Power On] in vSphere Web Client. If the message "This virtual machine might have been moved or copied. In order to configure certain management and networking features, VMware ESX needs to know if this virtual machine was moved or copied. If you don't know, answer "I copied it"." is displayed, select "I copied it".




224







■ STXE5206

[Message]STXE5206 ERROR There is an error occurred when enabling the schedule. Check vCenter Server status, net-work status and try enable the schedule again.

[Cause]The schedule that is temporarily disabled could not be enabled when the restore is being executed.

[Solution]Resolve the cause of the failure in enabling the schedule, and then perform [Enable Schedule] to enablethe schedule.

■ STXE5207

[Message]STXE5207 ERROR Schedule does not exist. Please create a schedule and try again.

[Cause]The restore cannot be executed because the schedule does not exist.

[Solution]Create the schedule, and then try the restore again.

■ STXE5208

[Message]STXE5208 ERROR Failed to get VM snapshot information. Check the status of the virtual machine andrestore VM snapshot from [Snapshots] by using the vSphere Web Client.

[Cause]The snapshot of the virtual machine cannot be restored because the snapshot information of the virtualmachine cannot be acquired.

[Solution]Resolve the cause of the failure in acquiring the information of the virtual machine, and then perform thefollowing procedure:






225











■ STXE5209

[Message]STXE5209 ERROR The datastore cannot be mounted to host. After you check the status of the host, mountthe created datastore again from [New Datastore] by using the vSphere Web Client.

[Cause]The restore failed because the datastore cannot be mounted to the host.

[Solution]Check the status of the host, and then use [New Datastore] in vSphere Web Client to mount the datastoreto the host.

■ STXE5210

[Message]STXE5210 ERROR Failed to get virtual machine information. Check virtual machines status and try again.

[Cause]The operation failed because the information of the virtual machine cannot be acquired.

[Solution]Check the status of the virtual machine, resolve the error, and then try again.

■ STXE5211

[Message]STXE5211 ERROR The schedule is running. Check the status of the schedule and try again.



226


[Cause]The restore cannot be executed because the schedule is being executed.

[Solution]Wait until the scheduled backup that is currently being executed is completed, or cancel [Backup Now] andtry the restore again. To check the execution status of the schedule, use the Task Console screen.

■ STXE5212

[Message]STXE5212 ERROR The operation could not be executed because other operation is restoring the selectedvirtual machine. Try again after the restore completed.

[Cause]The restore cannot be executed because the specified virtual machine is being restored.

[Solution]Wait until the restore that is being executed is completed, and then try the restore again.

■ STXE5213

[Message]STXE5213 ERROR Restore has been canceled. To use the virtual machine as it is, add the virtual machinefrom "New Virtual Machine" by using the vSphere Web Client. To delete files that has been copied, pleasedelete files manually.

[Cause]The restore has been canceled.

[Solution]Refer to "4.5.2 Canceling Virtual Machine Restore and Recovering It from Cancellation" (page 128) to per-form a recovery.

■ STXE5214

[Message]STXE5214 ERROR There is an error occurred when disabling the schedule. Check vCenter Server status, net-work status and try enable the schedule again.

[Cause]Disabling the schedule failed.

[Solution]Resolve the cause of the failure in disabling the schedule, and then perform the following procedure:

(1) Perform the restore again, or perform [Disable Schedule] and then try the restore again with the schedule being disabled.


■ STXE5215

[Message]STXE5215 ERROR Since the virtual machine configuration at the time of the snapshot taken is differentfrom the current virtual machine, restore cannot be executed.



227


[Cause]The restore cannot be executed because the configuration of the virtual machine when the snapshot wasacquired is different from the current configuration of the virtual machine.

[Solution]None.

■ STXE5216

[Message]STXE5216 ERROR Failed to change virtual machine configuration. Refer to manual, please change the vir-tual machine configuration, apply and delete the VM snapshots.

[Cause]The restore cannot be executed because the deletion of the virtual disk file that does not exist failed.

[Solution]Resolve the cause of the failure in deleting the virtual disk file that does not exist, and then perform thefollowing procedure:







■ STXE5217

[Message]STXE5217 ERROR Failed to get storage information. Check the status of registered storage and try again.

[Cause]The restore cannot be executed because the storage information cannot be acquired.

[Solution]Check the status of the registered storage system, resolve the error, and then try the restore again.

■ STXE5218

[Message]STXE5218 ERROR The single item restore has already been executed. Please stop single item restore andtry again.



228


[Cause]The restore cannot be executed because the single item restore is being executed.

[Solution]Wait until the single item restore stops automatically, or perform [Stop Single Item Restore] and then trythe restore again.

■ STXE5219

[Message]STXE5219 ERROR The specified snapshot does not exist. Please specify another snapshot and try again.

[Cause]The specified snapshot has been deleted or the specified snapshot is being used as the new snapshot dueto a backup execution.

[Solution]Select the other snapshot and then try the restore again.

■ STXE5220

[Message]STXE5220 ERROR SCSI controller does not exist. Please add a SCSI controller and try again.

[Cause]The single item restore cannot be started because the SCSI controller does not exist.


- Check the events related to the single item restore in the Task Console of vSphere Web Client and refer to "4.5.5 Canceling Single Item Restore and Recovering It from Cancellation" (page 139) to perform a recovery.

- Add a SCSI controller, and then try again.

■ STXE5221

[Message]STXE5221 ERROR The specified VMDK file cannot be connected. The available unit number of the SCSI con-troller is insufficient. Add SCSI controller, disconnected virtual disk, or decrease the number of the VMDKfiles, and try again.

[Cause]The specified VMDK file cannot be connected because there are insufficient available unit numbers of SCSIcontrollers.



- Perform any of the following actions, and try again:• Add a SCSI controller.• Disconnect unnecessary virtual disks.• Reduce the number of VMDK files to be connected.



229


■ STXE5222

[Message]STXE5222 ERROR The target VMDK file cannot be connected from the virtual machine. For details, refer tothe Task Console. Try again after fixing the issues.

[Cause]The single item restore failed because the target VMDK file cannot be connected to the virtual machine.



- Check the details of the error in the Task Console, resolve the error, and then try again.

■ STXE5223

[Message]STXE5223 ERROR There is an error occurred when deleting the directory. Confirm the target directory fromTask Console and delete it manually.

[Cause]The deletion of the temporary directory that was created during single item restore failed.



- From the Task Console, check the directory to be deleted and delete it manually, and then try again.

■ STXE5224

[Message]STXE5224 ERROR Single Item restore is already executed. Already executed single item restore cannot beexecuted.

[Cause]A Single item restore is already executing for the specified virtual machine.

[Solution]Perform one of the following operations:

- Wait until the single item restore that is being executed stops, and then try again.- Perform [Stop Single Item Restore], and then try again.

■ STXE5225

[Message]STXE5225 ERROR Single Item restore task has been canceled. To delete files that is being copied, pleasedelete files manually.

[Cause]The single item restore has been canceled.



230


[Solution]Refer to "4.5.5 Canceling Single Item Restore and Recovering It from Cancellation" (page 139) to perform arecovery.

■ STXE5226

[Message]STXE5226 ERROR The operation could not be executed because template is selected. Please try again afterconvert it to a virtual machine.

[Cause]The single item restore cannot be executed because the specified virtual machine is converted to a tem-plate.

[Solution]Use [Convert to Virtual Machine] in vSphere Web Client to convert the template to the virtual machine, andthen try the single item restore again.

■ STXE5227

[Message]STXE5227 ERROR The target VMDK file cannot be disconnected from the virtual machine. For details, referto the Task Console. Try again after fixing the issues.

[Cause]The single item restore cannot be stopped because the target VMDK file cannot be disconnected from thevirtual machine.



- Check the details of the error in the Task Console. Resolve the error, and then perform [Stop Single Item Restore]. Alternatively, manually disconnect the target VMDK file from the virtual machine, and then perform [Stop Single Item Restore].

■ STXE5228

[Message]STXE5228 ERROR Single Item restore information on the specified virtual machine cannot be found. CheckSingle Item restore information on the specified virtual machine and try again.

[Cause]The single item restore cannot be stopped immediately because the single item restore is not started.

[Solution]None.



231


D.2.4 Other Messages

■ STXE5300

[Message]STXE5300 ERROR Make sure ETERNUS vCenter Plug-in is registered to all vCenter Servers that are managedby vSphere Web Client and then try again.

[Cause]ETERNUS vCenter Plug-in may have not been registered to vCenter Servers that are managed by vCenterWeb Client.

[Solution]Check that ETERNUS vCenter Plug-in is registered to all vCenter Servers that are managed by vSphere WebClient, and then try again.

■ STXE5310

[Message]STXE5310 ERROR The specified storage already exists.

[Cause]The specified storage system is already registered.

[Solution]Specify another storage system.

■ STXE5321

[Message]STXE5321 ERROR There is an error occurred to access the configuration file. Wait a few minutes then tryagain. If you still have a problem, collect the information required for troubleshooting and contact FujitsuTechnical Support.

[Cause]The internal information management file cannot be accessed.

[Solution]Wait for a while, and then try again. If the problem persists, refer to "Chapter 7 Required Information forFailure Investigation" (page 167) to prepare any required information for troubleshooting, and then con-tact a Fujitsu engineer.

■ STXE5336

[Message]STXE5336 ERROR There is an error occurred when updating the information. For detail information, pleaserefer to Related Events in Task Console.

[Cause]An error has occurred while information was being updated.

[Solution]Check the details of the error in the Task Console, and then resolve the error.



232


■ STXE5340

[Message]STXE5340 ERROR Please specify correct IP address.

[Cause]The specified IP address is invalid.

[Solution]Specify a correct IP address.

■ STXE5341

[Message]STXE5341 ERROR ETERNUS SF cooperative information is not registered or is insufficient. Confirm ETERNUSSF cooperative information then try again.

[Cause]The ETERNUS SF connection information is not registered.

[Solution]Register the ETERNUS SF connection information, and then try again.

■ STXE5342

[Message]STXE5342 ERROR ETERNUS SF cooperative information setting file is incorrect. Collect the informationrequired for troubleshooting and contact Fujitsu Technical Support.

[Cause]The setting file of the ETERNUS SF is incorrect.


■ STXE5343

[Message]STXE5343 ERROR There is an error occurred to access the ETERNUS SF cooperative information file. Wait afew minutes then try again. If you still have a problem, collect the information required for troubleshootingand contact Fujitsu Technical Support.

[Cause]The setting file of the ETERNUS SF cannot be accessed.


■ STXE5344

[Message]STXE5344 ERROR ETERNUS SF cooperative information is already registered.



233


[Cause]The ETERNUS SF connection information cannot be registered because the information is already regis-tered.

[Solution]Modify the registered ETERNUS SF connection information, or delete the registered ETERNUS SF connectioninformation and then register the new information.

■ STXE5350

[Message]STXE5350 ERROR The schedule is running. Check the status of the schedule and try again.

[Cause]A schedule is being executed.

[Solution]Wait until the schedule that is being executed is completed, and then try again.

■ STXE5351

[Message]STXE5351 ERROR Restore task is running. Confirm the restore task has completed, then try again.

[Cause]Restore is being executed.

[Solution]Wait until the restore that is being executed is completed, and then try again.

■ STXE5400

[Message]STXE5400 ERROR Detail information was not able to be acquired from the vCenter server. Confirm the sta-tus of the vCenter Server and try again.

[Cause]Information cannot be acquired from the vCenter Server.

[Solution]Check the state of the vCenter Server. Resolve the error, and then try again.

■ STXE5401

[Message]STXE5401 ERROR A communication error might be occurred when access to the host. Check the networkstatus and try again. If you still have a problem, collect the information required for troubleshooting andcontact Fujitsu Technical Support.

[Cause]An error may have occurred in the communication to the host.

[Solution]Check the information of the network. If the problem persists after retrying, refer to "Chapter 7 RequiredInformation for Failure Investigation" (page 167) to prepare any required information for troubleshooting,and then contact a Fujitsu engineer.



234


■ STXE5402

[Message]STXE5402 ERROR Failed to login to the vCenter Server. Please check the vCenter server status and confirmthe credential information.

[Cause]The login to the vCenter Server failed.

[Solution]Check the server configuration and the credential information. If the problem persists after retrying, referto "Chapter 7 Required Information for Failure Investigation" (page 167) to prepare any required informa-tion for troubleshooting, and then contact a Fujitsu engineer.

■ STXE5403

[Message]STXE5403 ERROR The specified datastore does not exist. Please click [Refresh], confirm that the specifieddatastore exists and try again.

[Cause]The specified datastore cannot be found.

[Solution]Click the [Refresh] button to refresh the screen. Check that the specified datastore exists, and then tryagain.

■ STXE5404

[Message]STXE5404 ERROR The selected datastore is not a NFS datastore. Please specify a NFS datastore.

[Cause]The specified datastore is not an NFS datastore.

[Solution]Specify an NFS datastore, and then try again.

■ STXE5405

[Message]STXE5405 ERROR The selected datastore is not managed by ETERNUS vCenter Plug-in.

[Cause]The datastore is not an NFS datastore that is managed by ETERNUS vCenter Plug-in.

[Solution]Specify an NFS datastore that is managed by ETERNUS vCenter Plug-in.

■ STXE5406

[Message]STXE5406 ERROR The specified host or cluster cannot be found. Check the specified host or cluster and tryagain.



235


[Cause]The specified host or cluster cannot be found.

[Solution]Click the [Refresh] button to refresh the screen. Check that the specified host or cluster exists, and then tryagain.

■ STXE5407

[Message]STXE5407 ERROR The specified virtual machine cannot be found. Check the specified virtual machine andtry again.

[Cause]The specified virtual machine cannot be found.

[Solution]Click the [Refresh] button to refresh the screen. Check that the specified virtual machine exists, and thentry again.

■ STXE5408

[Message]STXE5408 ERROR Failed to mount the datastore. Please mount the created datastore to the host.

[Cause]The datastore could not be mounted to the host.

[Solution]Mount the created datastore to the host.

■ STXE5409

[Message]STXE5409 ERROR Failed to unmount the datastore. Please confirm the datastore is not being used and thestatus of the host, then try again.

[Cause]The datastore cannot be unmounted.

[Solution]Check that the datastore is not being used and also check the status of the host, and then try again.

■ STXE5500

[Message]STXE5500 ERROR Failed to get NAS volume list. detail: {}

[Cause]The acquisition of the NAS volume list failed.


- Check the state of the vCenter Server. If an error has occurred, resolve the error.



236


- Check the connection status between the vCenter Server and the host. If an error has occurred, resolve the error.

- Check the network status and the connection status between the vCenter Server and the ETERNUS DX. If an error has occurred, resolve the error.

- Check the status of the ETERNUS DX. If an error has occurred, resolve the error.- If a detailed message is output, resolve the error by referring to "Error Messages/Error Codes" in "ETER-

NUS CLI User's Guide" to check the error number that is output in the message.

■ STXE5501

[Message]STXE5501 ERROR Failed to get shared folder. detail: {}

[Cause]The acquisition of the shared folder failed.



the error.- Check the network status and the connection status between the vCenter Server and the ETERNUS DX. If

an error has occurred, resolve the error.- Check the status of the ETERNUS DX. If an error has occurred, resolve the error.- If a detailed message is output, resolve the error by referring to "Error Messages/Error Codes" in "ETER-


■ STXE5502

[Message]STXE5502 ERROR Failed to get NAS snapshot volume information. detail: {}

[Cause]The acquisition of the NAS snapshot volume information failed.






■ STXE5503

[Message]STXE5503 ERROR Failed to get NAS interface information. detail: {}



237


[Cause]The acquisition of the NAS interface failed.






■ STXE5504

[Message]STXE5504 ERROR Failed to create NAS volume. detail: {}

[Cause]The creation of the NAS volume failed.






■ STXE5506

[Message]STXE5506 ERROR Failed to get NFS allowed hosts. detail: {}

[Cause]The acquisition of the NFS allowed hosts for the shared folder failed.








238


■ STXE5507

[Message]STXE5507 ERROR Failed to change NFS allowed hosts. detail: {}

[Cause]Changing the NFS allowed hosts for the shared folder failed.






■ STXE5508

[Message]STXE5508 ERROR Failed to get NAS volume information. detail: {}

[Cause]The acquisition of the NAS volume failed.






■ STXE5509

[Message]STXE5509 ERROR Failed to expand the capacity of NAS volume. detail: {}

[Cause]The expansion of the NAS volume failed.




an error has occurred, resolve the error.



239




■ STXE5511

[Message]STXE5511 ERROR Failed to get RAID group list. detail: {}

[Cause]The acquisition of the RAID group list failed.






■ STXE5513

[Message]STXE5513 ERROR Failed to get shared folder list. detail: {}

[Cause]The acquisition of the shared folder list failed.






■ STXE5514

[Message]STXE5514 ERROR Failed to execute NAS snapshot setting. detail: {}

[Cause]The configuration of the snapshot settings failed.





240






■ STXE5515

[Message]STXE5515 ERROR Failed to delete shared folder. detail: {}

[Cause]The deletion of the shared folder failed.






■ STXE5516

[Message]STXE5516 ERROR Failed to delete NAS snapshot volume. detail: {}

[Cause]The deletion of the NAS snapshot volume failed.






■ STXE5517

[Message]STXE5517 ERROR Failed to start the scheduled operation for snapshot. detail: {}



241


[Cause]Starting the scheduled operation of the snapshot failed.






■ STXE5518

[Message]STXE5518 ERROR Failed to get the number of available generations of snapshot backup. detail: {}

[Cause]Acquiring the number of snapshot generations that can be created failed.






■ STXE5519

[Message]STXE5519 ERROR There is an error occurred when executing the script to create snapshot. detail: {}

[Cause]The execution of the script for obtaining a NAS snapshot failed.








242


■ STXE5520

[Message]STXE5520 ERROR Failed to create shared folder. detail: {}

[Cause]The creation of the shared folder failed.






■ STXE5521

[Message]STXE5521 ERROR Failed to get NAS snapshot setting information. detail: {}

[Cause]The acquisition of the snapshot setting information failed.






■ STXE5522

[Message]STXE5522 ERROR Failed to get NAS snapshot volume information. detail: {}

[Cause]The acquisition of the snapshot volume information failed.




an error has occurred, resolve the error.



243




■ STXE5523

[Message]STXE5523 ERROR Failed to stop the scheduled operation for snapshot. detail: {}

[Cause]Stopping the scheduled operation of the snapshot failed.






■ STXE5524

[Message]STXE5524 ERROR NAS snapshot setting does not exist. detail: {}

[Cause]The settings of the snapshot do not exist.






■ STXE5525

[Message]STXE5525 ERROR Failed to get NAS snapshot setting information. detail: {}

[Cause]The acquisition of the snapshot settings failed.





244





NUS CLI User’s Guide" to check the error number that is output in the message.

■ STXE5526

[Message]STXE5526 ERROR Failed to check datastore name. detail: {}

[Cause]Checking the datastore name failed.





NUS CLI User’s Guide" to check the error number that is output in the message.

■ STXE5527

[Message]STXE5527 ERROR The operation failed because no snapshot volume exists.

[Cause]SDV does not exist.

[Solution]Delete the schedule and then create the schedule again.

■ STXE5528

[Message]STXE5528 ERROR Couldn't get detail information from ETERNUS disk storage system.

[Cause]Because the ETERNUS DX was not able to be connected, the information cannot be acquired.

[Solution]Check the state of the ETERNUS DX and the network, and then try again.

■ STXE5529

[Message]STXE5529 ERROR Couldn't get information. Please click [Refresh].

[Cause]Because the ETERNUS DX was not able to be connected, the information cannot be acquired.



245


[Solution]Check the state of the ETERNUS DX and the network, and then click [Refresh] button again.

■ STXE5550

[Message]STXE5550 ERROR The operation of restore failed. Check the network status and try again after fixing theissues.

[Cause]The restore failed because the storage system cannot be connected.

[Solution]Check the state of the vCenter Server, the storage system, and the network, and then perform the followingprocedure:


(1) Select the datastore that contains the virtual machine to be restored.

(2) If a temporary directory is created in the datastore, delete the temporary directory.Example of the temporary directory:

423c02a9-7e93-4fb9-85e0-7494da447048_EVCP_RESTORE_TMP


(4) Select the registered virtual machine, and then try the restore again.

(5) If the STXE5552 error occurs, the last restore is being executed internally. In this case, wait for a while and try again from Step (1). Do not power on the virtual machine.






■ If an error occurred in a single item restore

(1) If the following directory exists in the datastore in which the target virtual machine exists, delete the directory.Example of a directory name:

Virtual_machine_name:-SIR-yyyyMMddHHmmss-yyyyMMddHHmmss

(2) Perform the single item restore again.




246


■ STXE5551

[Message]STXE5551 ERROR The operation of restore failed. Confirm that the restore target volume, datastore, virtualmachine exists and try again after fixing the issues.

[Cause]The restore failed because the volume, datastore, or virtual machine that is to be restored cannot be found.

[Solution]Check the state of the vCenter Server, the storage system, and the network, and then perform the followingprocedure:

















■ STXE5552

[Message]STXE5552 ERROR The operation of restore failed. Confirm that the selected virtual machine is not used bysingle item restore and try again after fixing the issues.



247


[Cause]The restore failed because the virtual machine restore or single item restore is being executed for theselected virtual machine.

[Solution]Wait until the restore that is being executed is completed, and then perform the following procedure:














■ STXE5553

[Message]STXE5553 ERROR You have reached the limit of multiple execution. Cancel the current restore or try againafter the restore completed.

[Cause]The number of restore operations that are executed at the same time has reached its upper limit.

[Solution]Wait until the restore that is being executed is completed, and then perform the following procedure:








248










■ STXE5554

[Message]STXE5554 ERROR The operation of restore failed because the source file of restore does not exist. Tryrestore again.

[Cause]The source file for the restore does not exist.

[Solution]Check the state of the storage system, and then perform the following procedure:
















249


■ STXE5555

[Message]STXE5555 ERROR The operation of restore failed. Try again after update the firmware of storage to newestversion.

[Cause]The firmware of the storage system may be outdated.

[Solution]Update the firmware of the storage system to the latest version, and then perform the following procedure:

















■ STXE5556

[Message]STXE5556 ERROR The operation of restore failed because an insufficient capacity error occurred. Pleaseconfirm the free capacity of the datastore and try again.

[Cause]The free space of the datastore (NAS volume) is insufficient.



250


[Solution]Allocate sufficient space for datastore (NAS volume), and then perform the following procedure:



(2) Delete the temporary directory that is created in the datastore.Example of the temporary directory:














■ STXE5557

[Message]STXE5557 ERROR The operation of restore failed because an I/O error occurred. Please check the status ofthe storage and try again.

[Cause]An I/O error has occurred.








251














■ STXE5558

[Message]STXE5558 ERROR Failed to detect if the restore is running or not. Try restore again.

[Cause]It is not possible to detect if the restore is being executed.

[Solution]Check the state of the storage system and the network, and then perform the following procedure:










252











■ STXE5559

[Message]STXE5559 ERROR The operation of restore failed. Refer to the troubleshooting in manual and fix the issues.

[Cause]The process could not be continued because a directory name in the restore destination directory conflictswith the name of the file that is to be restored.




(2) Delete all the files in the datastore except for the files in the temporary directory, and then copy the files in the temporary directory to the datastore.Example of the temporary directory:


(3) Delete the temporary directory.








253



(10)Perform [Enable Schedule] to enable the schedule as necessary.










■ STXE5598

[Message]STXE5598 ERROR Failed to execute the operation in ETERNUS DX. Refer to ETERNUS CLI Users Guide to getcorrective action information for error code {}.

[Cause]The operation in ETERNUS DX failed.

[Solution]Refer to the message number {} in ETERNUS CLI User’s Guide and resolve the problem.

■ STXE5599

[Message]STXE5599 ERROR Failed to execute the operation in ETERNUS DX. You can find the message code in the[Related events]. Refer to ETERNUS CLI Users Guide for details.

[Cause]The operation in ETERNUS DX failed.

[Solution]Check the ETERNUS CLI message number in the related event, and then refer to "ETERNUS CLI User's Guide"to resolve the problem.



254


■ STXE5900

[Message]STXE5900 ERROR Internal error occurred. Please collect the information required for troubleshooting andcontact Fujitsu Technical Support.

[Cause]An internal error has occurred.

[Solution]If this message is displayed immediately after ETERNUS vCenter Plug-in is installed, check whether theconditions of the caution in "2.1 New Installation" (page 22) apply and follow the procedure to resolve theissue.If the conditions do not apply, refer to "Chapter 7 Required Information for Failure Investigation" (page167) to prepare any required information for troubleshooting, and then contact a Fujitsu engineer.

■ STXE5901

[Message]STXE5901 ERROR Internal error occurred. Try again after waiting a few minutes. If you still have a problem,collect the information required for troubleshooting and contact Fujitsu Technical Support.

[Cause]An internal error has occurred.


■ STXE5902

[Message]STXE5902 ERROR Currently, the specified operation cannot be executed. After waiting for a few minutes,execute the command again. If you still have a problem, collect the information required for troubleshoot-ing and contact a Fujitsu customer engineer.

[Cause]Currently, the specified operation cannot be executed.


■ STXE5903

[Message]STXE5903 ERROR ETERNUS vCenter Plug-in has been restarted by vSphere Web Client.

[Cause]ETERNUS vCenter Plug-in has been restarted by vSphere Web Client, and the task that is being executed isplaced in an error state.

[Solution]None.



255

Appendix E

JRE Use Conditions (Common for SAN and NAS)

Before using ETERNUS vCenter Plug-in, you must agree to the following articles regarding the handling of theJava Runtime Environment (JRE) that is packaged together with this software.If you do not agree to these articles, you cannot use ETERNUS vCenter Plug-in.

(1) Observe the JRE use conditions that are described in the license text file.The license text is stored under the following directory or file:<Installation_folder>\ETERNUS-MICC\jre\<version_of_JRE>\LICENSE<Installation_folder>\ETERNUS-MICC\jre\<version_of_JRE>\THIRDPARTYLICENSEREADME.txt

(2) The JRE that is packaged together with ETERNUS vCenter Plug-in cannot be used for any purposes other than the operation of this software.

(3) Fujitsu shall not be liable for loss or damage caused by using JRE under conditions other than (1) and (2) above.




256

Appendix F

About Open Source Software License (Common for SAN and NAS)

This product uses the following open source software:

• Ganymed SSH-2 for JavaThe license that is applied to this software is stored in the following file:<Installation_folder>\ETERNUS-MICC\jars\LICENSE.txt<Installation_folder>\evcpService\LICENSE_ganymed.txt

• QuartzThe license that is applied to this software is stored in the following file:<Installation_folder>\evcpService\LICENSE_quartz.txt

• Slf4j-apiThe license that is applied to this software is stored in the following file:<Installation_folder>\evcpService\LICENSE_slf4j.txt

• VMware vSphere Web Service SDKThe license that is applied to this software is stored in the following file:<Installation_folder>\evcpService\open_source_licenses.txt




257

ETERNUS vCenter Plug-in 3.0.0 User's Guide

P3AM-7442-04ENZ0

Date of issuance: December 2015Issuance responsibility: FUJITSU LIMITED

• The content of this manual is subject to change without notice.

• This manual was prepared with the utmost attention to detail. However, Fujitsu shall assume no responsibility for any operational problems as the result of errors, omissions, or the use of information in this manual.

• Fujitsu assumes no liability for damages to third party copyrights or other rights arising from the use of any information in this manual.

• The content of this manual may not be reproduced or distributed in part or in its entirety without prior permission from Fujitsu.

Documents

ETERNUS vCenter Plug-in 3.0.0 User's Guide - … · This chapter provides an overview of ETERNUS vCenter Plug-in and also explains functions and operations ... ETERNUS vCenter Plug-in