with ibm corp.€¦ · 1. a list operation generates a list of the first 1,500 slice names that ar...

IBM Cloud Object Storage Slicestor®

Version 3.14.3

Device Data Evacuation

IBM

This edition applies to IBM Cloud Object Storage System™ and is valid until replaced by new editions.

© Copyright IBM Corporation 2016, 2019.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Document Information . . . . . . . . v

Chapter 1. New Capabilities . . . . . . 1

Chapter 2. Benefits . . . . . . . . . . 3

Chapter 3. Terminology and components 5

Chapter 4. Workflows . . . . . . . . . 7Data evacuation state workflow . . . . . . . . 7Data evacuation workflow . . . . . . . . . . 8

Generate a tracking file . . . . . . . . . . 8Listing and copying data . . . . . . . . . 9Errors during list or copy operations . . . . . 12Pause and resume evacuations . . . . . . . 13Read and write operations during evacuation . . 13

Chapter 5. Use cases . . . . . . . . 15

Chapter 6. Feature impact . . . . . . 17Throttling data throughput . . . . . . . . . 17

System upgrades . . . . . . . . . . . . 17

Chapter 7. Deployment using theManager Web Interface. . . . . . . . 19Replace and evacuate data from devices . . . . . 19Replacing a device . . . . . . . . . . . . 19Pause/resume data evacuation . . . . . . . . 20Terminate data evacuation . . . . . . . . . 20Rolling back a data evacuation . . . . . . . . 20Changing the destination device . . . . . . . 21Change the rate of evacuation during evacuation . . 21

Chapter 8. Deployment using the API 23

Chapter 9. Operations . . . . . . . . 25

Notices . . . . . . . . . . . . . . 29Trademarks . . . . . . . . . . . . . . 31Homologation statement . . . . . . . . . . 31

© Copyright IBM Corp. 2016, 2019 iii

iv Device Data Evacuation

Document Information

Intended Purpose and Audience

IBM Cloud Object Storage Slicestor® device data evacuation transfers data from an older Slicestor deviceto a new Slicestor device to maintain data availability as these devices age.

© Copyright IBM Corp. 2016, 2019 v

vi Device Data Evacuation

Chapter 1. New Capabilities

As Slicestor® devices age, they might need to be replaced.

The need to retain data still exists and needs to be transferred to replacement Slicestor® devices.

Note: Data evacuation from one Slicestor® device to another involves copying all data from the originalSlicestor® device. Refer to the "Initial Setup" and "Approve Registered Devices" sections in the ManagerAdministration Guide (or "Identity Checking Rules" and "Use Cases" of the Device Registration Guide) forinitial setup and approval of a new Slicestor® device.

© Copyright IBM Corp. 2016, 2019 1

2 Device Data Evacuation

Chapter 2. Benefits

Device Data Evacuation can:v Maintain data availability through renewal of hardware.v Maintain data availability despite failing hardware.v Facilitate the migration of data to new physical locations.


Chapter 3. Terminology and componentsSource Slicestor® device

Device transferring data.

Destination Slicestor® deviceDevice receiving transferred data.

Data EvacuationCopying all user data from Source Slicestor® device to Destination Slicestor® device.

NamespaceThe IBM Cloud Object Storage System™’s address structure to uniquely identify and locate objects,slices, vaults, and servers in a system.

A namespace is an address range in which slices can be stored. Namespaces are not filled and can besubdivided to simplify I/O operations.


Chapter 4. Workflows

Data evacuation state workflow

CAUTION:All IBM Cloud Object Storage Slicestor® devices that are included in the Storage Pool first must beupgraded to ClevOS 3.4 or higher.

Slicestor® Data Evacuation follows this simple workflow:

1. Follow the steps that are outlined in Replace a Device in the Manager Administration Guide.2. When a Slicestor® device is replaced, data evacuation starts and enters the Evacuating state. It can be

paused and resumed after it begins evacuation.3. When all data is copied to the Destination Slicestor® device, the evacuation enters the final Completed

state.

Attention: Do not remove Slicestor® devices during an evacuation.

If the Source Slicestor® device is reimaged or removed from the System Manager before data evacuationis completed, all data slices that are not already evacuated are lost. The data slices must be rebuilt.

If the Destination Slicestor® device is reimaged for any reason during data evacuation, data slices that arealready evacuated are not present and are lost. These data slices must be rebuilt.

Do not remove or reimage any Slicestor® device that is involved in data evacuation while it is in progressin a production environment.

For more information about the Rebuilder process, see the Rebuilder Agent guidelines.

Note: Lists and reads are disabled on the Destination Slicestor® device during evacuation. It prevents theRebuilder process on other Slicestor® devices or clients from gathering incomplete data.

Figure 1. Slicestor Data Evacuation State Diagram


Data evacuation workflow

Generate a tracking fileWhen data evacuation starts, a tracking file is created.

This tracking file contains the namespaces to be copied.1. All namespaces currently stored on the Source Slicestor device are cataloged in a Local Storage Map

file (storage.json).

2. To aid in better distribution of data across disks, all of these namespaces are then split into 512smaller namespaces.

3. These smaller namespaces are shuffled and stored in the tracking file.


Note: The smaller namespaces are shuffled to randomize the order in which data is copied to achievemaximum uniformity across all disks.

Listing and copying dataListing and copying data uses a producer/consumer model: list operations produce content that the copyoperations use to initiate copies.

It prevents delays in copying files that could occur while waiting for either a list or a copy to completefirst before starting a new copy or list.1. A List operation generates a list of the first 1,500 slice names that are found in the smaller namespaces

that are stored in the tracking file.

2. This slice list is put into a queue in memory.

Chapter 4. Workflows 9

3. Each copy operation pulls a single slice from the first slice list in the queue.


4. If slices are left in the list, the slice list is reinserted at the end of the queue.

5. The slice read and remote-write operations happen asynchronously.6. After an entire slice list is completed copying successfully, the range in the namespace housing the

slice list is truncated and the tracking file is updated.


7. After an entire small namespace is completed, it is removed from the tracking file.

The number of bytes transferred is also maintained in the tracking file for reporting purposes. A progressbar is visible on the Source Slicestor device and the Destination Slicestor device pages on the ManagerWeb Interface.

The combination of randomized namespace ranges and jumping between list requests results in highlyparallel and uniform reading from all data disks.

Errors during list or copy operationsIf errors occur during list, read, or write operations, the entire namespace that is being worked on isreinserted into the namespace tracker. It does not affect any other namespace and data evacuationproceeds onto other namespaces. The erroneous namespace is tried again at a later point in time.


Pause and resume evacuationsUser can use the Manager Web Interface to pause and resume evacuation.v The Pause button disables evacuation operations.v The Resume button resumes the evacuation operations.

Note: Due to the highly parallel and asynchronous nature of data evacuation, any interruption (includinga power outage, a process restart, or a pause/resume action) results in resending a large amount of data.Depending on the system configuration, 20 - 200 GB might be needed to be resent after an interruption. Itis visible as a drop in progress on the Data Evacuation Progress Bar on both the Source Slicestor® deviceand the Destination Slicestor® device pages on the Manager Web Interface. It happens automatically anddata evacuation proceeds thereafter.

Read and write operations during evacuationWhile data is being evacuated, data can still be read from and written to the destination Slicestor® device.

During reads, the destination Slicestor® device takes the read request and passes it to the source Slicestor®

device to return the file.

During writes, the destination Slicestor® device accepts the request and the data is written to it.


Chapter 5. Use cases1. Use Device data evacuation when an IBM Cloud Object Storage System™ is aged or when Slicestor®

Devices are failing and data needs to be moved to a new Slicestor® Device.2. Implement Device data evacuation to move data from one data center to another.


Chapter 6. Feature impact

Throttling data throughputThe relocation of all of the data on an IBM Cloud Object Storage Slicestor® device could impact I/Ooperations with this storage pool, within this system, or into the site where the Slicestor® devices reside.

To mitigate that impact, the data evacuation throughput rate can be limited via the System Manager. Thethroughput rate can be set during the initial replacement options or can be configured later from theConfigure page.

Note: See "Change the Storage Pool Reallocation Rate" in the Manager Administration Guide or "Edit DataEvacuation Rate Limit" in the Manager API Guide.

System upgradesDestination Slicestor® devices are considered down for purposes of upgrading a System Manager.

If an upgrade of another Slicestor device would impact the health of Vaults negatively by dropping thetotal number of available Slicestor® devices below the threshold, the upgrade pauses until the evacuationscomplete.


Chapter 7. Deployment using the Manager Web Interface

Replace and evacuate data from devicesWhen an IBM Cloud Object Storage Slicestor® device is replaced, its data can be evacuated to anotherdevice.

The device that is moved out of the storage pool is called the source device and the device that is movedinto the storage pool is called the destination device. Before a source device is replaced, the followinginternal checks must pass:v A storage pool that contains the source and destination devices must be updated to ClevOS 3.4.0.0 or

later.v The destination device must have a capacity equal to or greater than the source device.v The destination device must be reimaged if it previously contained data.v Both the source and destination device must not already be a part of an ongoing device replacement.v The replacement process must not impact vault health.v When a Slicestor® using the Concentrated Dispersal feature is being replaced in a Device Set, the

Manager requires that the Slicestor must have twice as many disks than the (Widest Vault's IDA Width/ Number of Slicestors in the Device Set).

Attention: Data cannot be evacuated during data reallocation. Before you perform an expansion, ensurethat the system is in a healthy a state by doing maintenance tasks such as executing any planned dataevacuations and replacing bad drives.

After data reallocation starts, drives can be replaced; however, devices that are replaced during datareallocation will not evacuate data. Do not replace devices during data reallocation because all data sliceson the old device are lost.

Replacing a deviceBefore you begin

CAUTION:This procedure assumes that a new Slicestor® device is properly installed and configured to serve asthe destination Slicestor device.

Procedure1. Navigate to the Configure Storage Pool page.2. On the Devices section, click the Replace Device link.3. From the list that is provided, select a source device.4. Click Next.5. If wanted, the network throughput that is allocated for data evacuation can be set.

a. Check the Data Evacuation Rate Limit check box.b. Enter a throughput limit in MBps.c. The limit can be changed later from the top-level Configure page.

6. Select the destination device on the right side.7. Click Confirm Replacement.8. A confirmation pop-up box displays.


9. Click OK.10. The data replacement and evacuation starts.11. Evacuation progress can be tracked on the Monitor page of the destination device.

What to do next

Note: All data evacuation events are visible only on the Source Slicestor® device.

The graphs that are found on the Monitor page for the Source Slicestor® device include the following:

Scanning RateShows Graph Data Not Available instead of any rate data.

Outgoing RebuildShows no Rebuild Bytes Sent.

Incoming RebuildShows Rebuild Slices Received.

Pause/resume data evacuationv To pause a data evacuation, click Pause Evacuation from the source devices Device Monitor page.v To resume a data evacuation, click Resume Evacuation from the source devices Device Monitor page.

Terminate data evacuationData evacuation can be terminated, if necessary, before it is completed.

Termination might be necessary due to hardware failure on the source or destination devices or if theoperator chooses to terminate the data evacuation.1. Click Pause Evacuation from the source devices Device Monitor page.2. Remove the source device from the Device Configure page.

The Enter Password page appears. Enter your password to confirm the device removal.

Alternately, just reimaging the source device is another way to terminate data migration.

Attention: Terminating data evacuation before completion results in loss of the remaining data slicesthat are not yet copied to the destination. These data slices must be rebuilt later.

Rolling back a data evacuationDuring evacuation, to return the evacuated data to the original source device (rollback), do the followingsteps.

Procedure1. Pause the evacuation on the source device.2. Click the Configure tab.3. Expand the list under Storage Pools on the left navigation tree.4. Click the Storage Pool to replace a device.5. The Storage Pool: <Pool Name> page displays.6. Swap the source and destination devices:

a. Click Replace Device to the right of the Slicestor Devices heading.b. Click the radio button to the left of the current destination device.c. Click Next.


d. Under the Replacement Slicestor Devices list, click the radio button to the left of the currentsource device.

e. Click Confirm Replacement to confirm the swap of source and destination devices.7. The data evacuates from the original destination device to the original source device.

Changing the destination deviceWhile data evacuation is taking place, it might be necessary to change the destination device (if hardwareproblems exist on the current one or if it was incorrectly chosen). No straightforward way to change thedestination device exists besides rolling back and starting a new evacuation.

Procedure1. Roll back evacuation according to “Rolling back a data evacuation” on page 20.2. Wait for the evacuation to roll back. If it is necessary to stop the evacuation, reimage the original

destination device (new source device). It stops the rollback.3. Start a new evacuation with the correct destination device.

Change the rate of evacuation during evacuationA user can enable/disable the data evacuation rate limit on all source devices on the top level configurepage.

Click Configure on the Data Evacuation Rate Limit Configuration action bar and complete the form thatis provided.

Note: On the configure page of a source device, the Remove button is disabled while data evacuation isin progress.

Attention: A user is allowed to pause evacuation and remove the source device. A device removal is adestructive action and can result in losing all data that is not copied.

Chapter 7. Deployment using the Manager Web Interface 21

Chapter 8. Deployment using the API

Replace Storage Pool Device

Replaces a device in a storage pool.

Note: Data evacuation will start shortly after a successful request, if there are vaults on the storage pool.

Request

Security

Table 1. Roles capable of executing the Replace Storage Pool Device (replaceStoragePoolDevice) API method

Any Super User System Admin Security Admin Operator

superUser systemAdmin

HTTP MethodPOST /manager/api/{apiResponseType}/1.0/replaceStoragePoolDevice.adm HTTP/1.1Host:{manager.dsnet}sourceId={deviceId}&destinationId={destinationId}

Curl Methodcurl -u {admin}:{password} -k"https://{manager.dsnet}/manager/api/json/1.0/replaceStoragePoolDevice.adm" -d"sourceId={deviceId}&destinationId={destinationId}"

Table 2. Request Parameters for Replace Storage Pool Device (replaceStoragePoolDevice) API method

Parameter Type Usage Default Description

sourceId Long Required Slicestor device ID to be replaced in StoragePool.

destinationId Long Required v Slicestor device ID of the device beingreplaced.

v This device cannot already be in a storagepool.

v If this device has recently been replaced andis currently in the evacuation stage, it cannotbe used for replacement.

evacuationEnabled Boolean Optional Start (true) data evacuation immediately afterthe device is replaced or enable data evacuationlater (false).

rateLimitEnabled Boolean Optional false Enable (true) or disable (false) a transferbandwidth rate limit for the evacuation.

v If provided and true, rateLimit is required.

v If provided and false, a rateLimit isprovided, but the rate limit is not enabledwhen device evacuation begins.


Table 2. Request Parameters for Replace Storage Pool Device (replaceStoragePoolDevice) API method (continued)

Parameter Type Usage Default Description

rateLimit Optional Optional v Value to set for the bandwidth limit for theevacuation from sourceId to destinationId

v A rate limit can be set to prevent device dataevacuation from having an impact on the restof the system Manager.

v If not provided, there will not be a rate limit

Response

Returns success or failure status.

JSON Response Example

The default JSON success or failure response is shown in Default JSON Success Response and DefaultJSON Failure Response.

Parameters

None other than the default response parameters are shown in the Common Response Parameters.


Chapter 9. Operations

Events, incidents, and logs

New Audit Messages

When device replacement with data evacuation starts, the following audit message displays:

Device: slicestor-mvm14.cleversafelab.comThe ’slicestor’ ’slicestor-mvm14.cleversafelab.com’ was modified. The dataevacuation was " and is now ’evacuating’. The data evacuation rate limit was" and is now ’enabled’.The data evacuation rate limit was " and is now set to ’777 MB/s’.

Account: AdminRequest IP: 10.10.13.10Source: UIAction code: Edit Storage Entry

When a data evacuation rate limit is set, the following audit message displays:

Storage Pool: vmpoolThe storage pool ’vmpool’ was modified. The following Slicestor device(s)were added to the storage pool: slicestor-mvm19.cleversafelab.com. Thefollowing Slicestor device(s) were removed from the storage poollicestor-mvm14.cleversafelab.com.

Account: AdminRequest IP: 10.10.13.10Source: UIAction code: Edit Storage Entry

When data evacuation is paused, the following audit message displays:

Device: slicestor-mvm10.cleversafelab.comThe slicestor ’slicestor-mvm10.cleversafelab.com’ was modified.The data evacuation was ’evacuating’ and is now ’paused’.

Account: AdminRequest IP: 10.10.13.10Source: Rest APIAction code: Device Data Evacuation

When data evacuation is resumed, the following audit message displays:

Device: slicestor-mvm10.cleversafelab.comThe slicestor ’slicestor-mvm10.cleversafelab.com’ was modified.The data evacuation was ’paused’ and is now ’evacuating’.

Account: AdminRequest IP: 10.10.13.10Source: Rest APIAction code: Device Data Evacuation


New Events

When data evacuation completes, the following event message displays with an Info icon:

Device: slicestor-mvm1.cleversafelab.comData evacuation has completed. 15.29 GB out of 15.29 GB evacuated.

When an error occurs during data evacuation, the following event message displays with an Error iconand an open incident is created:

Device: slicestor-mvm10.cleversafelab.comData evacuation is not making any progress due to I/O errors. Please make sure boththe source and destination devices are healthy and accessible.

When an error during data evacuation is resolved, the following event message displays with a checkmark icon and the open incident is cleared:

Device: slicestor-mvm10.cleversafelab.comData evacuation is now proceeding as expected.

Troubleshooting

Troubleshoot Data Evacuation Incidents

Troubleshoot Data Evacuation Incidents

Table 3. Request Parameters for Replace Storage Pool Device (replaceStoragePoolDevice) API method

Incident Action

Error occurred during dataevacuation

This error is caused when the data evacuation progress tracker does not persist to thesource device OS disk. If the problem persists or causes evacuation to halt, the usercan replace the OS drive on the Source device to continue data evacuation. Please seeinstructions for replacing the OS drive on the IBM Cloud Object Storage Slicestor®

2210, 2212, 1440, 2440, and 4100 devices.

v HP ProLiant SL4500 Series Quick Setup Instructions

v HP ProLiant SL4500 Series Setup and Installation Guide

v HP ProLiant SL4540 Gen8 Server Node User Guide

Data evacuation is reportingtoo many I/O errors. Pleasemake sure both the sourceand destination devices arehealthy and accessible.

This incident may be seen due to I/O errors on data disks on either the Source or theDestination device.

v Check to see if the source and destination devices are accessible over the network.

v Check to see if there are disks in a Quarantined state on either of these devices.

– The disks may be resumed first and if they get quarantined again, they mayneed to be failed. See the Quarantined section of the Manager Admin Manual onhow to resume or fail a Quarantined drive.

– If a quarantined disk is failed on the source device, the data slices on this diskmay never be evacuated. These data slices will have to be rebuilt later.

– If a quarantined disk is failed on the destination device, the data slices that havealready been evacuated to it may be lost. These data slices will have to be rebuiltlater. If no action is taken, data evacuation will continue to make progress untilno further progress can be made due to errors. In this case, the next incident willappear. If the problem persists, please contact an IBM Customer SuccessEngineer.


https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-c03667364

http://h20565.www2.hpe.com/hpsc/doc/public/display?sp4ts.oid=5287871&docId=emr_na-c03483688&docLocale=en_US

http://h20565.www2.hpe.com/hpsc/doc/public/display?ac.admitted=1413579448208.876444892.492883150&docId=emr_na-c03488786-6&lang=en-us&cc=us&docLocale=en_US

Table 3. Request Parameters for Replace Storage Pool Device (replaceStoragePoolDevice) API method (continued)

Incident Action

Data evacuation is notmaking any progress due toI/O errors. Please make sureboth the source anddestination devices arehealthy and accessible.

Please follow all the steps from the previous incident. If this incident appears withoutany quarantined disks on either the Source or the Destination device, it may be dueto low error ratio that doesn’t cause disks to become quarantined. In this case dataevacuation will continue to make progress until no further progress can be made.This may result in evacuation to be halted. At this point, the operator may terminatethe data evacuation and let Rebuilder rebuild the remaining data slices.

Attention: Terminating the data evacuation results in a loss of any data slices thathave not been evacuated. If an evacuation is terminated, please wait for the lost dataslices to be rebuilt before attempting another data evacuation.

Chapter 9. Operations 27

Notices

This information was developed for products and services offered in the US. This material might beavailable from IBM® in other languages. However, you may be required to own a copy of the product orproduct version in that language in order to access it.

IBM may not offer the products, services, or features discussed in this document in other countries.Consult your local IBM representative for information on the products and services currently available inyour area. Any reference to an IBM product, program, or service is not intended to state or imply thatonly that IBM product, program, or service may be used. Any functionally equivalent product, program,or service that does not infringe any IBM intellectual property right may be used instead. However, it isthe user's responsibility to evaluate and verify the operation of any non-IBM product, program, orservice.

IBM may have patents or pending patent applications covering subject matter described in thisdocument. The furnishing of this document does not grant you any license to these patents. You can sendlicense inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.

For license inquiries regarding double-byte character set (DBCS) information, contact the IBM IntellectualProperty Department in your country or send inquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan, Ltd.19-21, Nihonbashi-Hakozakicho, Chuo-kuTokyo 103-8510, Japan

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS"WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOTLIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY ORFITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of express orimplied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodicallymade to the information herein; these changes will be incorporated in new editions of the publication.IBM may make improvements and/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM websites are provided for convenience only and do not inany manner serve as an endorsement of those websites. The materials at those websites are not part ofthe materials for this IBM product and use of those websites is at your own risk.

IBM may use or distribute any of the information you provide in any way it believes appropriate withoutincurring any obligation to you.


Licensees of this program who wish to have information about it for the purpose of enabling: (i) theexchange of information between independently created programs and other programs (including thisone) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Director of LicensingIBM CorporationNorth Castle Drive, MD-NC119Armonk, NY 10504-1785US

Such information may be available, subject to appropriate terms and conditions, including in some cases,payment of a fee.

The licensed program described in this document and all licensed material available for it are providedby IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement orany equivalent agreement between us.

The performance data discussed herein is presented as derived under specific operating conditions.Actual results may vary.

Information concerning non-IBM products was obtained from the suppliers of those products, theirpublished announcements or other publicly available sources. IBM has not tested those products andcannot confirm the accuracy of performance, compatibility or any other claims related to non-IBMproducts. Questions on the capabilities of non-IBM products should be addressed to the suppliers ofthose products.

Statements regarding IBM's future direction or intent are subject to change or withdrawal without notice,and represent goals and objectives only.

All IBM prices shown are IBM's suggested retail prices, are current and are subject to change withoutnotice. Dealer prices may vary.

This information is for planning purposes only. The information herein is subject to change before theproducts described become available.

This information contains examples of data and reports used in daily business operations. To illustratethem as completely as possible, the examples include the names of individuals, companies, brands, andproducts. All of these names are fictitious and any similarity to the names and addresses used by anactual business enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programmingtechniques on various operating platforms. You may copy, modify, and distribute these sample programsin any form without payment to IBM, for the purposes of developing, using, marketing or distributingapplication programs conforming to the application programming interface for the operating platform forwhich the sample programs are written. These examples have not been thoroughly tested under allconditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of theseprograms. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not beliable for any damages arising out of your use of the sample programs.

If you are viewing this information softcopy, the photographs and color illustrations may not appear.


TrademarksIBM, the IBM logo, and ibm.com® are trademarks or registered trademarks of International BusinessMachines Corp., registered in many jurisdictions worldwide. Other product and service names might betrademarks of IBM or other companies. A current list of IBM trademarks is available on the web atCopyright and trademark information at www.ibm.com/legal/copytrade.shtml.

Accesser®, Cleversafe®, ClevOS™, Dispersed Storage®, dsNet®, IBM Cloud Object Storage Accesser®, IBMCloud Object Storage Dedicated™, IBM Cloud Object Storage Insight™, IBM Cloud Object StorageManager™, IBM Cloud Object Storage Slicestor®, IBM Cloud Object Storage Standard™, IBM Cloud ObjectStorage System™, IBM Cloud Object Storage Vault™, SecureSlice™, and Slicestor® are trademarks orregistered trademarks of Cleversafe, an IBM Company and/or International Business Machines Corp.

Other product and service names might be trademarks of IBM or other companies.

Homologation statementThis product may not be certified in your country for connection by any means whatsoever to interfacesof public telecommunications networks. Further certification may be required by law prior to making anysuch connection. Contact an IBM representative or reseller for any questions.

Notices 31

http://www.ibm.com/legal/copytrade.shtml

IBM®

Printed in USA

with ibm corp.€¦ · 1. a list operation generates a list of the first 1,500 slice names that ar...

Documents