StorageX Release Notes - datadynamicsinc.com › docs › releasenotes › ...Enables configuration...

StorageX Release Notes

8.1

Data Dynamics StorageX 8.1 Release Notes

May 2019This version of the Data Dynamics StorageX product (StorageX) provides several new features. This version also improves usability and extends several capabilities. Many of these improvements were made in direct response to suggestions from our customers.

These Release Notes outline why you should install this version, provide additions to the documentation, and identify the known or resolved issues.

This document includes the following sections:

• “Why install this version?” on page 1

• “How to install” on page 5

• “Resolved issues” on page 6

• “Known issues” on page 10

• “Additions to documentation” on page 29

• “Contacting Technical Support” on page 29

• “Legal notice” on page 30

Why install this version?The Data Dynamics StorageX (StorageX) product is more than simply a data mover or storage migration tool. It is a software platform for adding storage management structure around unstructured local and distributed data. This includes heterogeneous vendor support across different storage system platforms and support for both CIFS and NFS protocols, as well as support for object storage resources.

StorageX provides storage infrastructure management capabilities that allow storage professionals to logically view distributed file or object storage, and then use policies to automate data movement across heterogeneous storage infrastructures.

The following sections outline the important new features and functionality provided in this version of StorageX:

• “Optimizes scan and analysis functionality using clustered Elasticsearch” on page 2

• “Enhances scalability of StorageX Metadata Service components” on page 2

• “Support added for Microsoft Azure Blob resources” on page 2

• “Support added for ONTAP 9.2” on page 3

• “Integration added for third-party monitoring tools” on page 3

• “Enables configuration for Cassandra grooming” on page 3

• “Ability to cancel Archive policies now added to Management Portal” on page 3

• “Ability to delete Workload Tiering policies now added to Management Portal” on page 3

1

Why install this version?

• “Ability to edit or delete datasets and queries now added to Management Portal” on page 3

• “Enables user to use an analysis set as a dataset” on page 4

• “Support added for NFS destinations in object-to-file API calls” on page 4

• “Custom tagging enabled for file-to-object transformation API calls” on page 4

• “New StorageX API functions added” on page 4

• “Optimizes replication of security descriptors when migrating data to NetApp storage resources” on page 4

• “Resolves issue where StorageX server cannot access some OneFS storage resources” on page 4

Optimizes scan and analysis functionality using clustered ElasticsearchIn StorageX 8.1, scan and analysis functionality is improved and optimized by using an external Elasticsearch clustered installation.

Where StorageX 8.0 used an Apache Cassandra repository to store scan, analysis, and archival information for the StorageX Management Portal and StorageX Retrieval Portal, and Lucene to index and query that information, StorageX now uses Elasticsearch both for storing and querying data about scans and analysis sets.

The previous Cassandra repository is retained, but is now only used as a backup index during the archival process.

Enhances scalability of StorageX Metadata Service componentsIn StorageX 8.0, the StorageX Metadata Service could only be installed on a single StorageX server. This architecture limited StorageX functionality in environments where a large number of objects were processed by the Service.

In StorageX 8.1, the Metadata Service is broken apart into three sub-components:

• StorageX Metadata Service Web Service, which receives metadata from the data engine and responds to queries for metadata information.

• StorageX Metadata Service Processing Engine, which processes metadata information and inserts that metadata into the Elasticsearch repository.

• Clustered Redis installation, which acts as a message channel between the other Metadata Service and StorageX components.

Each of these three components can be installed on different servers other than the StorageX server. The Redis cluster, in fact, must be installed on a separate cluster of Linux servers.

This distributed architecture allows for greater scalability, enabling the overall Metadata Service to process, store, and query data about your environment more quickly and efficiently in environments with larger amounts of data.

Support added for Microsoft Azure Blob resourcesStorageX now supports managing Microsoft Azure Blob (Azure Blob) object storage resources in the StorageX Console, archiving data to Azure Blob resources, and restoring archived data from Azure Blob resources.

2 StorageX Release Notes


Support added for ONTAP 9.2StorageX now supports migrating data to and from storage resources running ONTAP 9.2.

Integration added for third-party monitoring toolsStorageX now includes integration with optional third-party monitoring tools that can be used to monitor your Elasticsearch and Cassandra installations.

Users can now configure the StorageX Management Portal to allow access directly from the Maintenance Portal tab to existing Grafana, Reaper, and/or Prometheus installations.

NOTEStorageX does not install nor support Grafana, Reaper, or Prometheus. For more information about these third-party applications, see their respective documentation.

Enables configuration for Cassandra groomingStorageX now allows users to configure the Cassandra grooming job that runs once per week and removes any data older than a year (365 days), by default. Users can change the default grooming settings in the new Maintenance Portal tab of the StorageX Management Portal.

Ability to cancel Archive policies now added to Management PortalStorageX now allows users to cancel running Archive policies in the StorageX Management Portal. To cancel a running Archive policy, click the Archive tab, select the policy you want to cancel, and click Cancel Job.

Ability to delete Workload Tiering policies now added to Management PortalStorageX now allows users to delete Workload Tiering policies in the StorageX Management Portal. To delete a Workload Tiering policy, click the Workload Tiering tab, select the policy you want to delete, and click Delete.

In previous versions of StorageX, you could only delete Workload Tiering policies in the StorageX Console.

Ability to edit or delete datasets and queries now added to Management PortalStorageX now allows users to modify or delete existing datasets and queries in the StorageX Management Portal.

To modify a dataset or query associated with an analysis set, click the Analyze tab, select the analysis set you want to change, and click Edit. In the Edit Analysis Set dialog box, click either the Dataset or Query tab, make changes as necessary, and click Save. If the Management Portal asks for confirmation, click Yes.

StorageX Release Notes 3


To delete a dataset or query associated with an analysis set, select the analysis set, click Delete, then click Yes to confirm the analysis set deletion and Yes again to confirm that you want to delete datasets or queries included in the analysis set.

In previous versions of StorageX, you could only delete or modify datasets or queries included in an analysis set using the API.

Enables user to use an analysis set as a datasetStorageX now allows users to include an existing analysis set as the dataset for a second analysis set. In previous versions of StorageX, you could only include datasets and queries in an analysis set.

Support added for NFS destinations in object-to-file API callsThe StorageX API now allows users to specify NFS-protocol destinations when creating and running object-to-file transformation API calls. In previous versions of StorageX, the API only supported CIFS destinations for object-to-file transformation.

Custom tagging enabled for file-to-object transformation API callsThe StorageX API now includes the ability to specify custom tags when creating and running file-to-object transformation API calls, tagging objects created on the destination object storage resource for later retrieval.

New StorageX API functions addedStorageX now includes REST API functions for working with Cassandra grooming settings outside of the StorageX Management Portal, including getting details about all grooming tasks and configuring Cassandra grooming.

In addition, you can now run StorageX API calls outside of the Management Portal to delete analysis sets and related queries or datasets, cancel Archive jobs, validate Workload Tiering policy names, and retrieve manifests both for scans and Archive jobs, in either CSV or JSON format.

Optimizes replication of security descriptors when migrating data to NetApp storage resourcesStorageX 8.1 optimizes the capability of the StorageX data engine to replicate security descriptors to resources running Data ONTAP or ONTAP using a Phased Migration or Replication policy.

Resolves issue where StorageX server cannot access some OneFS storage resourcesStorageX 8.1 resolves an issue where if you install a security patch on a OneFS storage resource, the StorageX server can no longer access the resource. This issue is caused by security updates to the OneFS platform. This version of StorageX has been updated to function properly with those updates.


How to install

How to installFollow the steps provided below to install StorageX 8.1 on each StorageX server or StorageX Console computer in your environment.

NOTES:

• If upgrading to StorageX 8.1, you must upgrade the StorageX server, StorageX Console, StorageX Management Portal, StorageX Retrieval Portal, and all StorageX Metadata Service components to use the same version of the product.

• If you have one or more Windows data engines deployed in StorageX 8.0 and want to upgrade to StorageX 8.1, you must first install Hotfix 01197 on all StorageX servers, upgrade all deployed data engine to the hotfixed version of StorageX, and then upgrade all components to StorageX 8.1.

• You must have a minimum of 4 processor cores, each 2 GHz or faster, installed on the StorageX server before you install this version of the product. Data Dynamics, Inc., recommends using 6 processor cores for optimum performance.

• For information about installing and configuring the StorageX Management Portal or StorageX Retrieval Portal, see the StorageX Analysis, Archival, & Retrieval Guide.

To install this version of the product:

1. Log on to the computer where you want to install the StorageX server or StorageX Console, using a user account that is a member of the local Administrators group on the computer and that has access to the StorageX database.

2. If upgrading to this version of the product, cancel any running policies in the StorageX Console.

3. If upgrading from StorageX 8.0 to StorageX 8.1 with one or more Windows data engines deployed, complete the following steps:

a. Open a browser and navigate to the Data Dynamics Technical Support Portal: www.datdynsupport.com.

b. Click the Downloads tab and download Hotfix 01197.

c. On your StorageX 8.0 server, close the StorageX Console.

d. Install Hotfix 01197. We recommend running the installation package using the Run as administrator option.

e. If prompted to restart after the hotfix installation, click Yes.

f. Start the StorageX Console.

g. Click Control Panel > Deployed Data Engines.

h. Right-click each remote data engine and select Upgrade.

NOTEThe data engine deployed by default on the StorageX server should already show the updated version number, 8.0.9144.0, in the Version column.

i. When all data engines have been upgraded to the hotfix version (8.0.9144.0), close the StorageX Console.

4. Download the installation package and double-click the Setup.exe file.


http://www.datdynsupport.com/


Resolved issues

5. If a User Account Control dialog box displays, click Yes to confirm that you want to run the installation package.

6. On the Setup tab, click System Requirements and review the system requirements.

7. Click Install StorageX.

8. On the StorageX Setup Wizard Welcome dialog box, review the welcome message and then click Next.

9. If upgrading, click Next to begin the upgrade process, then skip to step 18.

10. On the End-User License Agreement dialog box, review the terms of the license agreement, select the I accept the terms in the License Agreement check box, and then click Next.

11. Select the StorageX components you want to install and click Next.

12. Specify the login credentials you want to use for the StorageX server service account, and then click Next.

13. Select or specify the database instance you want to use for the StorageX database, and then click Next.

14. Specify credentials for the StorageX server to use when connecting to the StorageX database, test the database credentials, and then click Next.

15. Specify the certificate you want StorageX to use for making SSL connections, either the default self-signed certificate or a custom certificate, and then click Next.

16. If you are installing the StorageX Console without the StorageX server, specify the StorageX server that you want the StorageX Console to connect to, and then click Next.

17. Click Install to begin the installation.

18. When finished, click Finish to close the setup program.

19. If prompted to restart your StorageX server, click Yes to restart your StorageX server immediately or click No if you want to restart the server at a later time. You must restart the server to finish the upgrade process.

20. If you have any Windows or Linux universal data engines deployed using a previous version of StorageX, we recommend you upgrade all existing data engines. Follow the procedures provided in the StorageX Administrator’s Guide to upgrade your data engines.

ATTENTIONAfter you upgrade a universal data engine, whether deployed through the Console or manually, ensure you configure the firewall for the data engine host to allow StorageX to communicate with the data engine.

For more information about installing, configuring, and using the product, refer to the StorageX Administrator’s Guide and the StorageX online help, located on the Data Dynamics Technical Support Portal at www.datdynsupport.com.

Resolved issuesThis version of StorageX addresses the following issues:

• “StorageX incorrectly logs errors while migrating files with alternate data streams” on page 7




Resolved issues

• “StorageX universal data engine encounters error during migration and stops unexpectedly” on page 7

• “StorageX Management Portal does not immediately display analysis set changes in the Archive tab” on page 8

• “StorageX displays “Access is denied” errors when scanning resources with encrypted files” on page 8

• “Phased Migration policy manifest incorrectly lists certain unsupported folders as excluded” on page 8

• “StorageX Management Portal incorrectly displays simulated runs of Workload Tiering policies” on page 8

• “StorageX displays false errors when running scans or replication-based policies are canceled” on page 9

• “StorageX cannot correctly scan or archive data from NetApp or Isilon resources with cluster options enabled” on page 9

• “StorageX cannot archive files with double whitespaces to a StorageGRID destination” on page 9

• “StorageX does not check for duplicates when using API to transform application data” on page 9

• “StorageX server cannot connect to a locally-installed StorageX Metadata Service” on page 10

StorageX incorrectly logs errors while migrating files with alternate data streamsIn a previous version of StorageX, if you create and run a Phased Migration policy that includes one or more files that have alternate data streams, the data engine logs may display the following error:

Cannot flush file buffers. NFileWin pointer is NULL or invalid.

This error causes no actual problems during the migration process but is confusing and may alarm users. This issue has been addressed and no longer occurs in StorageX 8.1.

StorageX universal data engine encounters error during migration and stops unexpectedlyIn a previous version of StorageX, the application may rarely encounter an error while copying data from one resource to another as part of a Phased Migration policy, where the data engine is unable to rename a temporary file and then fails unexpectedly.

This issue has been addressed and no longer occurs in StorageX 8.1.


Resolved issues

StorageX Management Portal does not immediately display analysis set changes in the Archive tabIn a previous version of StorageX, if you create an Archive policy, click the analysis set link for the policy in the Analysis Set column on the Archive tab, make changes to the analysis set, and click Save, the StorageX Management Portal may not immediately display the analysis set changes, even when the Management Portal displays the confirmation message Analysis set updated successfully.


StorageX displays “Access is denied” errors when scanning resources with encrypted filesIn a previous version of StorageX, if you create and run a file scan that includes one or more storage resources with encrypted files, the StorageX Management Portal may display the following potentially-misleading error in the scan manifest:

Access is denied.

In some situations, this error may indicate that StorageX cannot access the storage resource, but it may also indicate that files on the resource are encrypted. StorageX does not support scanning, migrating, or archiving encrypted files.

In StorageX 8.1, the StorageX Management Portal now displays the correct error message:

The file or directory is encrypted. The request is not supported.

Phased Migration policy manifest incorrectly lists certain unsupported folders as excludedIn a previous version of StorageX, if you run a Phased Migration policy with a source that includes one or more folders that StorageX does not support migrating, when you view the details for the policy run, those unsupported folders are incorrectly included in the Folders Excluded column value rather than the correct Folders Ignored column value.

In StorageX 8.1, unsupported folders are correctly displayed in the Folders Ignored column, instead of in the Folders Excluded column.

StorageX Management Portal incorrectly displays simulated runs of Workload Tiering policiesIn a previous version of StorageX, if you create a Workload Tiering policy, set the Replication Type to Simulate Replication in the StorageX Console, and run the policy, when you open the StorageX Management Portal and go to the Workload Tiering tab, the list of Workload Tiering policies displays the simulated run of the policy with no indication that the policy run was a simulation.

In StorageX 8.1, the Workload Tiering tab of the Management Portal includes a new Simulation column that indicates if a completed policy run was a simulation.


Resolved issues

StorageX displays false errors when running scans or replication-based policies are canceledIn a previous version of StorageX, if you cancel a running file scan job, Phased Migration policy, Replication policy, Disaster Recovery policy, or Archive policy, when you view the manifest for the canceled action, StorageX incorrectly displays an error count that includes all files that were not scanned, replicated, or archived before the cancellation.


StorageX cannot correctly scan or archive data from NetApp or Isilon resources with cluster options enabledIn a previous version of StorageX, if you create and run either a scan or Archive policy that includes one or more NetApp or Isilon resources with cluster options enabled, StorageX cannot scan or archive data from those resources.

This occurs because when cluster options are enabled on these types of resources, the resource only returns an IP address, and the data engine is unable to collect platform metadata for the resource. Without this metadata, the data engine cannot scan files or archive data.


StorageX cannot archive files with double whitespaces to a StorageGRID destinationIn a previous version of StorageX, if you create and run an Archive policy with a StorageGRID object storage resource as the destination and one or more files that include two or more whitespaces in a row in the file name or any other tag, the destination StorageGRID resource returns an AWS error for those files that include multiple whitespaces.


StorageX does not check for duplicates when using API to transform application dataIn a previous version of StorageX, if you include duplicate entries in the JobItems parameter list for a transform job, StorageX transforms all specified source files into objects, even those that are duplicated. That version of StorageX only checks for duplicate entries when you use the Management Portal, not when you use the API.



Known issues

StorageX server cannot connect to a locally-installed StorageX Metadata ServiceIn a previous version of StorageX, if you have the StorageX Metadata Service installed on the StorageX server and the IPv6 protocol is disabled on the server, the StorageX Metadata Service uses the IP address of the StorageX server instead of the host name. The StorageX server is then unable to connect to the StorageX Metadata Service unless the server is configured to use that specific IP address.

Known issuesThe following issues are known issues in StorageX 8.1:

• “Installation and configuration issues” on page 13

• “StorageX Metadata Service/Management Portal installation program does not display SSL certificates” on page 13

• “StorageX database is not case sensitive” on page 14

• “Upgrade issues” on page 14

• “Users must re-configure customized .config files after upgrade” on page 14

• “StorageX Console issues” on page 14

• “StorageX Console does not automatically reconnect after restarting the StorageX server service” on page 14

• “Universal data engine management issues” on page 14

• “Throttling settings are ignored if the source or destination are on the same local server as the data engine” on page 14

• “Universal data engine port cannot be changed” on page 15


Known issues

• “Storage resource management issues” on page 15

• ““Set Hosting Properties” context menu item in My Resources does not save Virtual Data Mover setting changes” on page 15

• “StorageX may display an incorrect network connectivity error when adding Data ONTAP SVM resources” on page 15

• “StorageX does not automatically add hosting resources when users add Isilon or EMC VNX virtual resources” on page 15

• “StorageX only displays one Qtree in Storage Resources for NetApp 8 cluster mode” on page 15

• “StorageX displays error that export already exists when creating or cloning export on Data ONTAP Vserver” on page 16

• “Cannot create traditional volumes on Data ONTAP resources using the Mirror Volume and Automatic Disk Selection options” on page 16

• “Users may experience delays when managing namespaces with offline namespace servers” on page 16

• “StorageX does not properly display current restart mode setting for NetApp SnapMirrors” on page 16

• “Cannot add list of DFS namespaces that includes invalid or nonexistent namespaces” on page 16

• “Renaming DFS links in StorageX removes replication targets in the DFS Management console” on page 17

• “Local groups must be added using NetApp OnCommand on Data ONTAP 8.2.1 and earlier Vservers” on page 17

• “NFS export name and local path must match” on page 17

• “Cannot specify security style or oplocks settings when creating qtrees on Data ONTAP vFiler file storage resources” on page 17

• “Migration Project issues” on page 18

• “Migration Project design displays incorrect settings when resource configuration has changed” on page 18

• “StorageX does not support deduplication for OneFS Migration Project sources” on page 18

• “Migration Project policies cannot detect existing folder on destination Data ONTAP 8.3 Vserver” on page 18

• “StorageX cannot copy the NetApp “maxdirsize” volume option with Migration Projects” on page 19

• “StorageX displays incorrect error message when user deletes SnapMirror used by Migration Project” on page 19

• “Migration Project policies recreate deleted SnapMirrors in broken-off State” on page 19

• “StorageX incorrectly displays security style and oplocks settings after user sets the “Use Snapmirror” option” on page 20

• “Migration Project designs fail when migrating to multiple Vservers on the same cluster” on page 20

• “Migration Projects do not correctly migrate “Automatically grow this volume” setting” on page 20


Known issues

• “Information about provisioning actions not included in Phased Migration policy manifests” on page 20

• “Migration Project design execution completes successfully, but VNX mount options are not applied when the destination file system is a nested under a parent file system that is a regular, and not an NMFS, file system” on page 21

• “Volume quotas on Data ONTAP sources are not migrated to VNX OE for File destinations” on page 21

• “User and group quotas on Data ONTAP sources are not migrated to VNX OE for File destinations” on page 22

• “Migration Project design execution fails if the destination is a VNX OE for File Virtual Data Mover, an object on the source has the same name as an item on the destination, and the item on the destination with the same name is not visible to the destination VDM” on page 22

• “Migration Project Advanced design allows configuring the security style and oplocks settings when creating a volume on a Data ONTAP Vserver, but the settings are not used” on page 22

• “Export cloning fails when VNX is the destination, and the VNX server has a large number of NFS exports” on page 22

• “Phased Migration policy issues” on page 23

• “Canceled Phased Migration policy displays completed successfully in Completion State but shows errors in the manifest” on page 23

• “Phased Migration policy options reset to default when a user changes template inheritance” on page 23

• “Phased Migration policy schedule changes not being saved” on page 23

• “NFS permissions change on the destination resource if root squash is enabled” on page 23

• “Phased Migration policy wizard cloning does not create nested NFS exports on the destination” on page 24

• “Phased Migration replication option to clear the Archive attribute for files on the destination does not properly clear the attribute” on page 24

• “Phased Migration policies return error when migrating files or folders with local security descriptors between Data ONTAP 7-Mode and Data ONTAP 8.3” on page 24

• “Phased Migration policies fail when migrating data to destination resources with paths longer than the character limit allowed on the resource” on page 24

• “Reporting issues” on page 24

• “Error remains in Namespace Summary Report error panel even if the Namespace is removed from Storage Resources” on page 25

• “Replication Policy Report fails to export if the Replication Policy is still running” on page 25

• “Simulated migration run removes previous run information from the Migration Project Summary report” on page 25

• “Storage Resource Reports do not list the correct number of NFS exports for a VNX server when it has a large number of NFS exports” on page 25

• “File scanning issues” on page 25


Known issues

• “Management Portal displays incorrect status for scan failure with single NFS path” on page 26

• “Deleted scans may still be displayed in list of scans when using the StorageX API” on page 26

• “File-to-object Archive policy issues” on page 26

• “Archive policies cannot include files, shares, or exports hosted on a cluster” on page 26

• “Management Portal may display duplicate files with Errors or Warnings in manifest” on page 26

• “StorageX Console does not correctly display status of Archive policies in Events and Alerts tabs” on page 26

• “StorageX may time out when viewing an Archive policy job with a large number of files” on page 27

• “StorageX may be slow to cancel running Archive policies when throttling is enabled” on page 27

• “Linux universal data engines running multiple Archive policy jobs may cause Management Portal display issues” on page 27

• “Workload Tiering policy issues” on page 27

• “StorageX Console incorrectly displays Workload Tiering policies as Migration policies in Alerts tab” on page 28

• “Maintenance Portal issues” on page 28

• “Cassandra grooming job not running as scheduled” on page 28

• “REST API issues” on page 28

• “User can only use the “equals” operator for tags when creating or updating datasets” on page 28

• “User cannot specify a folder path when using the policy-creation POST method request” on page 28

• “REST API endpoint data does not update properly if there are errors in the schema keys” on page 29

Installation and configuration issuesThis section lists known issues related to StorageX installation and configuration.

StorageX Metadata Service/Management Portal installation program does not display SSL certificates

If you install the StorageX server or one of the StorageX Metadata Service (StorageX Management Portal) components and then install any Metadata Service component on the same server, the installation program displays the Specify SSL Certificate dialog box but does not list or allow you to select a custom certificate, even if a custom certificate is stored locally and properly configured.

When other StorageX components are installed on a server, those components must use the same SSL certificate. You cannot specify a different certificate, even if the Specify SSL Certificate dialog box being displayed. Click Next and then Yes to work around this issue.


Known issues

StorageX database is not case sensitive

The StorageX database is not case sensitive. If you have two items that have the same name but the name is specified using a difference case, StorageX does not recognize each item separately.

Consider the following examples:

• Assume you have two Data ONTAP qtrees. The first qtree is named finance. The second qtree is name FINANCE. The Data ONTAP operating system recognizes each of these qtrees as different objects based on case sensitivity. However, the StorageX database does not recognize case sensitivity. As a result, StorageX displays only one of the qtrees.

• Assume you are using a Phased Migration policy to migrate NFS file data. You have two files on your source with file names that differ only by case. The first file is named 2013-Financials, and the second file is named 2013-FINANCIALS. In this scenario, StorageX migrates both files but reports that only one of the files was migrated in the policy manifest.

Upgrade issuesThis section lists known issues related to upgrading previous versions of StorageX to StorageX 8.1.

Users must re-configure customized .config files after upgrade

If you want to upgrade an existing StorageX installation and have modified any settings in the storagexserver.exe.config, mc.exe.config, or storagexreplicationagent.exe.config files, you must re-configure those files after the upgrade process is completed. The installation package replaces those existing files with updated versions for StorageX 8.1.

StorageX Console issuesThis section lists known issues related to the StorageX Console.

StorageX Console does not automatically reconnect after restarting the StorageX server service

If you restart the StorageX server service while running the StorageX Console, the Console does not reconnect to the service. To work around this issue, close the current instance of the StorageX Console and open a new one.

Universal data engine management issuesThis section lists known issues related to universal data engine management.

Throttling settings are ignored if the source or destination are on the same local server as the data engine

If you configure throttling settings for a data engine and either the source or destination for a migration are on the same local server as that data engine, the throttling settings will be ignored.


Known issues

Universal data engine port cannot be changed

The port specified on the General tab for a universal data engine cannot be changed.

Storage resource management issuesThis section lists known issues related to file storage resource management.

“Set Hosting Properties” context menu item in My Resources does not save Virtual Data Mover setting changes

If you add a VNX CIFS or NFS server to your My Resources in the StorageX Console, right-click the resource, select Set Hosting Properties, and change the Hosting resource is a Virtual Data Mover setting, then click OK, the modified setting is not changed.

To work around this issue, right-click the resource, select Properties, click the Platform > Hosting Properties tab, and modify the Hosting resource is a Virtual Data Mover setting there, instead, then click OK.

StorageX may display an incorrect network connectivity error when adding Data ONTAP SVM resources

If you add or import a Data ONTAP Storage Virtual Machine (SVM) in StorageX and specify incorrect or invalid API credentials, the StorageX Console displays the following error:

Unable to contact the machine. This may be due to network connectivity or DNS issue, or the machine is offline.

This error may be misleading, indicating not that there are network issues but that there is an issue with the Data ONTAP SVM API credentials.

To work around this issue, when you encounter this error with a Data ONTAP SVM, ensure that the API credentials are correct, then right-click the SVM in the File Storage Resources tab on the Storage Resources view and select Refresh.

StorageX does not automatically add hosting resources when users add Isilon or EMC VNX virtual resources

If you add or import a Data ONTAP virtual resource in StorageX, StorageX automatically also adds the Data ONTAP cluster resource that hosts the virtual resource. However, if you add an Isilon or EMC VNX virtual resource, StorageX cannot automatically add the hosting resource for the virtual resource.

To work around this issue, when adding an Isilon or EMC VNX virtual resource, you must first add the resource that hosts the virtual resource, then add the virtual resource itself.

StorageX only displays one Qtree in Storage Resources for NetApp 8 cluster mode

If you create two Qtrees with differently-capitalized versions of the same name for a Data ONTAP 8 resource, you will only see one of those Qtrees in Storage Resources. This issue is the result of Qtrees being case sensitive as of Data ONTAP 8. To work around this issue, ensure that your Qtree names differ in ways other than just simple capitalization.


Known issues

StorageX displays error that export already exists when creating or cloning export on Data ONTAP Vserver

If you create a volume with the UNIX security style (NFS) on a Data ONTAP Vserver, mount that volume under a folder named vol, and then try to create or clone an export to the NFS volume, Storage displays an error that the export already exists on the destination volume or has already been exported to the destination volume.

To work around this issue, change the name of the destination mount folder to something other than vol and try to create or clone the export again.

Cannot create traditional volumes on Data ONTAP resources using the Mirror Volume and Automatic Disk Selection options

If you create a traditional volume on a Data ONTAP resource and select the Mirror Volume and Automatic Disk Selection options, the Volume Creation Wizard displays the following error message and does not create the specified volume:

Unable to create volume: X disks needed, but not enough matching HDD disks to create traditional volume are available

To avoid this issue, either use the Manual Disk Selection option and select the appropriate number of primary and mirror disks or create the volume without using the Mirror Volume option.

Users may experience delays when managing namespaces with offline namespace servers

If you add or create a domain namespace in StorageX, and that namespace has more than one namespace server, and one of the namespace servers shuts down, fails, or becomes otherwise unreachable, you may experience significant delays when StorageX attempts to validate the namespace, even if the other namespace server is online and functioning.

To resolve this issue, go to the Storage Resources view in the StorageX Console, click the namespace in the My Resources folder, right-click the offline namespace server in the Namespace Servers list, and select Remove.

StorageX does not properly display current restart mode setting for NetApp SnapMirrors

If you view the properties of a NetApp SnapMirror in the Storage Resources view and change the Restart mode setting on the Options and Schedule tab, then re-open the properties window, StorageX does not display the updated Restart mode setting. This error occurs because StorageX cannot correctly display the current restart mode of a SnapMirror. However, StorageX does correctly set the restart mode.

Cannot add list of DFS namespaces that includes invalid or nonexistent namespaces

If you try to add multiple new namespaces to StorageX at one time in the Add DFS Namespace dialog box, and one or more of the namespaces does not exist or cannot be accessed from the StorageX server, StorageX does not add the nonexistent namespace or any subsequent namespaces in the list but instead displays an error.


Known issues

To work around this issue, remove the invalid namespace from the list in the Add DFS Namespace dialog box and click OK again.

Renaming DFS links in StorageX removes replication targets in the DFS Management console

If you create a replication group in the DFS Management console, add a DFS link with more than one target, and then rename the DFS link using StorageX, the DFS Management console no longer displays the link targets in the Replication tab for the link. You should use caution when modifying DFS links and folders in multiple consoles.

Local groups must be added using NetApp OnCommand on Data ONTAP 8.2.1 and earlier Vservers

If you use a Data ONTAP 8.2.1 or earlier CIFS share as the destination for a migration, Disaster Recovery, or Replication policy, the policy may fail with the error message “The remote procedure call failed.” This error occurs when the Create local groups on the destination if not found option is enabled, because the StorageX data engine cannot create missing local groups on the Vserver. This is caused by a limitation in Data ONTAP.

To work around this issue, either disable the Create local groups on the destination if not found option or use the NetApp OnCommand console to create the local group on the Vserver and then re-run the policy.

NFS export name and local path must match

Data ONTAP and VNX OE for File file storage resources support exporting a folder when the export name is different from the local path on the resource. NFS exports created using StorageX do not support this capability. When you create an NFS export in the Storage Resources view, StorageX allows you to only specify a path. You cannot specify both an export name and a path. In the Migration Projects view, when StorageX executes a Migration Project design and create NFS exports on the destination, the NFS export name and local path are the same.

Cannot specify security style or oplocks settings when creating qtrees on Data ONTAP vFiler file storage resources

When you use StorageX to create qtrees on volumes Data ONTAP file storage resources, typically you can specify a security style for the qtree, as well as specify if you want to enable or disable oplocks settings. However, if you are creating a qtree on a volume that is owned by a Data ONTAP vFiler in the Storage Resources view, you cannot specify a security style or oplocks setting on the qtree. New qtrees created on volumes owned by vFilers inherit the security style and oplocks setting from the volume.

In addition, if you plan to use StorageX Migration Projects with Data ONTAP vFilers as destinations, consider the following scenarios:

• If you are moving a volume from a source Data ONTAP file storage resource to a volume on a destination Data ONTAP vFiler, when you execute the Migration Project design, StorageX creates the qtree on a volume on the destination vFiler, and the qtree on the destination inherits the security style and oplocks setting from the destination volume.


Known issues

• If you are moving a VNX OE for File File System from a source VNX OE for File file storage resource to a volume on a destination Data ONTAP vFiler, when you execute the Migration Project design, StorageX creates the qtree on a volume on the destination vFiler, and the qtree inherits the security style and oplocks setting from the destination volume.

• If you are moving a Data ONTAP qtree or VNX OE for File tree quota from a Data ONTAP or VNX OE for File file storage resources to a volume on a destination Data ONTAP vFiler file storage resource, StorageX creates the qtree on a volume on the destination vFiler, and the qtree inherits the security style and oplocks setting from the destination volume.

If you plan to use StorageX Migration Projects with Data ONTAP vFilers as destinations, after you execute the Migration Project design, ensure you verify the security style and oplocks settings on the destination qtrees before you migrate file data to the destinations using Migration Project Phased Migration policies.

If you want to change the qtree security style or oplocks settings on the destination, connect to the vFiler file storage resource directly and change the settings. For more information, see the Data ONTAP CLI command documentation.

Migration Project issuesThis section lists known issues related to StorageX Migration Projects.

Migration Project design displays incorrect settings when resource configuration has changed

If you create a Migration Project design, select a source and destination, and then modify the settings for either resource, the Migration Project Design Wizard and Advanced Options do not display the changes. StorageX cannot detect changes made to a resource after the resource has been included in the design.

To work around this issue, when you modify settings on resources included in a Migration Project, ensure that you refresh the Sources and Destinations lists in the Migration Projects tab before creating and executing any Migration Project designs using those resources.

StorageX does not support deduplication for OneFS Migration Project sources

If you create a Migration Project design that uses a OneFS resource as a source, StorageX does not correctly display whether the source has been deduplicated previously in the Src Is Deduped column or the percentage of the source that was previously deduplicated in the % Dedup Saved on Src column, both in the Advanced Options dialog box.

In addition, when the source is a OneFS resource, StorageX cannot determine if expanding the previously-deduplicated data would exceed the size of the destination and also cannot automatically configure deduplication during Migration Project design execution.

Migration Project policies cannot detect existing folder on destination Data ONTAP 8.3 Vserver

If you create a Migration Project design that uses a Data ONTAP 8.3 Vserver as the destination, and the Vserver contains a folder with the same name as the source, when you execute the design, the export creation process may fail with the following error in the Sharing data on destination node of the manifest:


Known issues

Failed to create or determine if a junction exists within volume "VOLUMENAME". Error occurred with the remaining junction path of "DESTPATH" for the given path of "SOURCEPATH" Reason: Junction create failed (21).

StorageX cannot determine if a folder already exists on the destination. To work around this issue, you must manually create the junction path, then re-run the Migration Project policy.

StorageX cannot copy the NetApp “maxdirsize” volume option with Migration Projects

If you create a Migration Project design that uses Data ONTAP resources as both source and destination, StorageX does not copy the NetApp volume option maxdirsize from the source to the destination.

This limitation occurs because NetApp optimizes this option for each specific version of Data ONTAP and does not allow you to copy the option value from one volume to another. For more information about configuring this volume option, contact NetApp technical support.

NOTES:

• If you use SnapMirror replication for a Migration Project policy, the SnapMirror functionality duplicates the source maxdirsize volume option on the destination.

• This limitation only applies to Migration Projects where the source is a volume. This limitation does not apply to Migration Projects where the source is a qtree.

StorageX displays incorrect error message when user deletes SnapMirror used by Migration Project

If you create a Migration Project design that uses SnapMirror replication, run the Phased Migration policy generated by the design to perform the baseline copy, and then delete the SnapMirror created during the policy run, when you right-click the policy and select Policy Actions > Continue the next action now, StorageX cannot create shares and displays the following incorrect error message:

SnapMirror Release: No release-able destination found that matched those parameters.

To avoid this issue, after you delete the SnapMirror created by the policy, right-click the policy and select Policy Actions > Retry the last action now. StorageX successfully creates shares and displays the correct status message for the policy.

Migration Project policies recreate deleted SnapMirrors in broken-off State

If you create a Migration Project design that uses SnapMirror replication, run the Phased Migration policy generated by the design to perform the baseline copy, and then delete the SnapMirror created during the policy run, when you re-run the baseline copy for the policy, StorageX recreates the SnapMirror but with a State of broken-off.

We recommend that you do not delete SnapMirrors that are being used in StorageX policies. If you delete a SnapMirror being used by a policy, and that SnapMirror is recreated in a broken-off state, you should remove the destination volume from the policy and add a new destination volume, then re-run the baseline copy.


Known issues

StorageX incorrectly displays security style and oplocks settings after user sets the “Use Snapmirror” option

If you create a Migration Project design with a Data ONTAP 7 or Data ONTAP 8 7-Mode resource as the source and a Data ONTAP 8 Cluster Mode resource as the destination and configure the destination security style and oplocks, then select Use Snapmirror, StorageX incorrectly displays the previous, non-SnapMirror values for the Volume Security Style and Volume Oplocks settings for the design in the Summary pane.

When using SnapMirror replication for a Migration Project design, StorageX should display no value for the Volume Security Style and Volume Oplocks settings for the design.

Migration Project designs fail when migrating to multiple Vservers on the same cluster

If you create a Migration Project design that uses as destination resources two Vservers or SVMs hosted on the same cluster and aggregate, and the aggregate does not have enough space to store the migrated data more than once, StorageX successfully validates the design and displays no errors. However, when you execute the design, the design fails to execute with an error that there is not enough space available to create the new volume on the destination.

When creating a Migration Project design with multiple Vservers or SVMs as destination resources, you must ensure that there is sufficient space on the destination host resource to migrate data for all specified destination Vservers or SVMs.

Migration Projects do not correctly migrate “Automatically grow this volume” setting

If you create a Migration Project to migrate data between Data ONTAP file storage resources and select the Automatically grow this volume setting on the source resource, when you execute the Migration Project design, StorageX does not migrate that volume setting to any destination resources.

StorageX does not currently support migrating this particular setting between Data ONTAP file storage resources. In this situation, you must manually set the Automatically grow this volume setting on all destination resources after the Migration Project is finished running.

Information about provisioning actions not included in Phased Migration policy manifests

If you are migrating file data using Migration Projects, information about provisioning actions performed when you execute the Migration Project design are not included in policy manifests.

For example, if you are migrating file data stored on a volume on a Data ONTAP 7 file storage resource using Migration Projects and the volume on the source has a quota, you can choose whether you want StorageX to create a new volume on the destination with the same quota, or whether you want StorageX to create a new volume on the destination with a different quota.

If you specify that you want to create a new volume on the destination with a different quota, when you execute your Migration Project design, StorageX creates the new volume on the destination and immediately applies the new quota to the destination. However, the information about the quota applied on the new quota is not written to the policy manifest.


Known issues

To verify that StorageX created the volume on the destination with the correct quota, use a native tool such as NetApp OnCommand System Manager to verify StorageX created the new volume using the correct quota on the destination Data ONTAP file storage resource.

However, if there are user or group quotas on sources, these user and group quotas are applied on the destinations when the Phased Migration policy runs and you can see this information in the policy manifest.

Migration Project design execution completes successfully, but VNX mount options are not applied when the destination file system is a nested under a parent file system that is a regular, and not an NMFS, file system

In VNX, when you mount a file system, you can mount the file system under the default VNX namespace, or you can mount the file system under another file system. For example, assume you have a regular file system, FS01, mounted as /FS01. Then assume that you have another regular file system, FS02, mounted as /FS01/FS02, which means the FS02 file system is nested under the FS01 file system. In addition, in VNX, there are regular file systems and Nested Mount File Systems (NMFS).

If you want to create a file system nested under another file system, ensure you create the parent file system as a Nested Mount File Systems (NMFS), and not as a regular file system. You cannot change the mount option for a regular file system if the regular file system is nested under another regular file system. You can only change the mount option for a file system mounted under another file system if the file system is a NMFS file system. This behavior is due to limitations with VNX technology.

For example, assume you are creating an Advanced Migration Project design, and you specify the mount path you want StorageX to create on the VNX OE for File destination and whether you want to use the Oplocks, NT Credentials, Read Only, or Disable Virus Checker mount path options.

If you enter a nested mount path, and if the parent file system is a regular file system and not an NMFS file system, and you specify a mount option other than the default mount option, the Migration Project design will complete successfully and StorageX will create the new file system on the destination. However, StorageX will use the default mount path option, and will not apply any other mount path options you specified in your Advanced Migration Project design.

If you then want to change the mount option, you will be unable to do so. This limitation is due to limitations with VNX technology.

If you want to be able to change the default mount option on a nested file system, ensure the parent file system is a NMFS file system.

Volume quotas on Data ONTAP sources are not migrated to VNX OE for File destinations

StorageX does not support the migration of volume quotas from source Data ONTAP file storage resources to destination VNX OE for File file storage resources.


Known issues

User and group quotas on Data ONTAP sources are not migrated to VNX OE for File destinations

StorageX does not support the migration of local user and group quotas or domain user and group quotas from source Data ONTAP file storage resources to destination VNX OE for File file storage resources.

Migration Project design execution fails if the destination is a VNX OE for File Virtual Data Mover, an object on the source has the same name as an item on the destination, and the item on the destination with the same name is not visible to the destination VDM

If your destination is a VNX OE for File Virtual Data Mover (VDM) and you have an object on your source, such as a Data ONTAP volume or VNX OE for File File System, with the same name as a VNX OE for File File System on your destination, and the VNX OE for File File System with the same name is not visible to the destination VDM, when you validate the Migration Project design, the design validates successfully. However, when you execute the Migration Project design, the design execution fails and a This name already exists error message displays.

To avoid this issue, ensure that source object names do not already exist on destination VNX OE for File VDM destinations when you create Migration Project designs.

Migration Project Advanced design allows configuring the security style and oplocks settings when creating a volume on a Data ONTAP Vserver, but the settings are not used

When you use a StorageX Advanced Migration Project design to create a volume on a Data ONTAP Vserver file storage resource, the options are available to specify the security style and oplocks settings for the volume. However, the security style and oplocks settings in the advanced design are not used and StorageX creates a volume that inherits these settings from the root volume of the Vserver.

If you plan to use StorageX Migration Projects with Data ONTAP Vservers as destinations, after you execute the Migration Project design, ensure you verify the security style and oplocks settings on the destination volumes before you migrate file data to the destinations using Migration Project Phased Migration policies.

If you want to change the volume security style or oplocks settings on the destination, connect to the Vserver file storage resource directly and change the settings. For more information, see the Data ONTAP CLI command documentation.

Export cloning fails when VNX is the destination, and the VNX server has a large number of NFS exports

When you execute a Migration Project design, and the destination of the migration project is a VNX server with a large number of NFS exports, the export creation phase may fail with the following error in the Sharing data on destination node of the manifest:

Failed sharing resources '<export name>': Failed to create NFS export on destination machine.


Known issues

A VNX server has an upper limit on the buffer size it will use when responding to a mount request to enumerate the NFS exports on the server. Because of this limit, the VNX server may not return information for all NFS exports. This happens when the amount of data required to list all exports is greater than the maximum buffer size configured for the VNX server. In testing StorageX with the default VNX configuration, the VNX returned information for approximately 3,000 exports even though it had 8,000 exports configured (the exact number returned will vary based on the lengths of the export paths).

Because the VNX server does not return all NFS exports, the StorageX server attempts to create an export that already exists, resulting in the error listed above.

The fix to this issue is to increase the upper limit of the buffer size used by the VNX server when it responds to a mount request to enumerate its NFS exports. In the EMC VNX Series Release 7.1 Parameters Guide for VNX for File document, the upper limit is documented as being controlled by the mount facility parameter tcpResponseLimit. The default value is 262144, but it can be increased up to 1048576. The needed size depends on the number of NFS exports (and their corresponding path lengths) defined on the VNX server. See the VNX documentation for more details.

Phased Migration policy issuesThis section lists known issues related to StorageX Phased Migration policies.

Canceled Phased Migration policy displays completed successfully in Completion State but shows errors in the manifest

If you cancel an NFS Phased Migration policy before it finishes running, you may see StorageX display “Completed Successfully” in the policy’s Completion State but you will see the error “The operation was canceled by the user” in the policy manifest.

Phased Migration policy options reset to default when a user changes template inheritance

If you create a Phased Migration policy from a template, make changes to the settings for that policy, and then go to the Template Options tab in the policy Properties and change the parent template to a different template, all modified options are reset to the default options for that new template.

To work around this issue, ensure you change the Manage template inheritance settings under the Template Options tab first, click Apply, and then modify any other options in the Properties dialog box, as necessary, and click Apply again.

Phased Migration policy schedule changes not being saved

If you create multiple schedules for a Phased Migration template, when you attempt to edit the schedule of any policy that uses that template after that policy is created, the changes will not be saved.

NFS permissions change on the destination resource if root squash is enabled

If you have root squash enabled on your CentOS destination, when you run a Phased Migration policy as root, the chosen files will copy with their NFS permissions set to nfsnobody.


Known issues

Phased Migration policy wizard cloning does not create nested NFS exports on the destination

If you use the Phased Migration policy wizard to discover NFS exports and attempt to clone them to the destination, StorageX will not create the exports.

Phased Migration replication option to clear the Archive attribute for files on the destination does not properly clear the attribute

If you create a Phased Migration policy and the destination storage resource contains files that have the Archive attribute set, when you select the Attribute setting on destination > Clear option for Archive attributes in the CIFS Attribute Replication tab, StorageX does not consistently clear the Archive attribute.

Phased Migration policies return error when migrating files or folders with local security descriptors between Data ONTAP 7-Mode and Data ONTAP 8.3

If you add a local group to the Security properties of a file or folder located on a NetApp Data ONTAP 7-Mode file storage resource and then run a Phased Migration policy to migrate from the 7-Mode file storage resource to a Data ONTAP 8.3 CIFS Vserver that does not have the same local group, StorageX returns the following error in the manifest:

A device attached to the system is not functioning.

This error occurs because of a NetApp Data ONTAP 8.3 issue, where NetApp Data ONTAP 8.3 Vservers cannot correctly process local security descriptors.

To work around this issue, right-click the Phased Migration policy and select Properties, click Replication Options > CIFS Security Replication, clear the Process local trustees in security descriptor option, click OK, and then re-run the policy.

Phased Migration policies fail when migrating data to destination resources with paths longer than the character limit allowed on the resource

If you run a Phased Migration policy where the destination file storage resource path is longer than the character limit allowed on the resource, the policy fails with a “The filename or extension is too long.” error message. This issue occurs both when the folders in the specified path already exist and when one or more folders are created during the migration process.

Before creating and running Phased Migration policies, ensure the destination path is shorter than the number of characters allowed on the resource. For information about storage resource character limits for a particular resource, see the documentation for the device.

Reporting issuesThis section lists known issues related to StorageX Reports.


Known issues

Error remains in Namespace Summary Report error panel even if the Namespace is removed from Storage Resources

If you have previously removed a DFS Namespace from Storage Resources, the Namespace Summary Report error panel for any of your other DFS Namespaces may display the error Namespace is excluded from the report because it is not managed by StorageX when you view the report.

Replication Policy Report fails to export if the Replication Policy is still running

The work around for the issue is to run the export when no policy is running, or schedule the report at a time where the replication policy is not running.

Simulated migration run removes previous run information from the Migration Project Summary report

If you perform a simulated migration run for a Migration Project policy, StorageX removes any information in the Migration Project Summary report for all previous non-simulated runs of that policy.

Storage Resource Reports do not list the correct number of NFS exports for a VNX server when it has a large number of NFS exports

When you view a report that lists NFS exports for a VNX server (e.g., the Exports report or the Storage Resource Summary report), the number of NFS exports listed in the report may be less than the number of exports configured on the VNX server if the VNX server has a large number of NFS exports.

A VNX server has an upper limit on the buffer size it will use when responding to a mount request to enumerate the NFS exports on the server. Because of this limit, the VNX server may not return information for all NFS exports. This happens when the amount of data required to list all exports is greater than the maximum buffer size configured for the VNX server. In testing StorageX with the default VNX configuration, the VNX returned information for approximately 3,000 exports even though it had 8,000 exports configured (the exact number returned will vary based on the lengths of the export paths).

Because the VNX server does not return all NFS exports, the StorageX reports that include information about NFS exports do not show the correct number of NFS exports for the VNX server.

The fix to this issue is to increase the upper limit of the buffer size used by the VNX server when it responds to a mount request to enumerate its NFS exports. In the EMC VNX Series Release 7.1 Parameters Guide for VNX for File document, the upper limit is documented as being controlled by the mount facility parameter tcpResponseLimit. The default value is 262144, but it can be increased up to 1048576. The needed size depends on the number of NFS exports (and their corresponding path lengths) defined on the VNX server. See the VNX documentation for more details.

File scanning issuesThis section lists known issues related to scanning files using the StorageX Management Portal.


Known issues

Management Portal displays incorrect status for scan failure with single NFS path

If you create and run an Archive policy that includes a single NFS path, and StorageX does not have access to that path, StorageX displays the Status "The operation completed successfully" in the Scan Path Manifest Details dialog box, even though the scan failed.

The Scan Path Manifest Details dialog box should instead display the Status "The operation completed with errors".

Deleted scans may still be displayed in list of scans when using the StorageX API

If you delete an existing scan in the StorageX Management Portal, you can no longer run or modify the scan or include the scan in an analysis set in the Management Portal. If you previously used the scan as dataset for an analysis set, the analysis set continues to display results that include the scan data.

However, when you use the StorageX API to view all scans in your environment by running the GET /api/v2/analyze/dataset API call, the API returns a list of scans that includes the deleted scan. Despite the deleted scan being listed, you cannot use the API to include the scan in a dataset.

File-to-object Archive policy issuesThis section lists known issues related to file-to-object Archive policies.

Archive policies cannot include files, shares, or exports hosted on a cluster

If you have one or more storage resources configured as a cluster, and you include files, shares, or exports hosted on the cluster in the analysis set used in an Archive policy, when you run the Archive policy, StorageX returns an error. StorageX does not currently support including data hosted on a cluster in Archive policies. You can only include data in an Archive policy that is hosted on non-clustered storage resources.

Management Portal may display duplicate files with Errors or Warnings in manifest

If you create and run an Archive policy in StorageX, and the policy job encounters an issue with one or more files included in the policy, when you click the entry in the Job Status column for the policy in the Archive tab, then click the Files tab, the Manifest Details dialog box may display duplicates of one or more files with a Status of Error or Warning.

These duplicate files are only caused by a display issue in the Management Portal and can be safely ignored.

StorageX Console does not correctly display status of Archive policies in Events and Alerts tabs

If you create and run an Archive policy in StorageX, when you start the StorageX Console interface and try to view the status of the policy, neither the Events or Alerts tabs in the center pane display any log entries for the policy.

To view the status of an Archive policy, open the StorageX Management Portal, click the Archive tab, and then click the link to view the manifest for the Archive policy or policy job you want to view.


Known issues

StorageX may time out when viewing an Archive policy job with a large number of files

If you create and run an Archive policy that includes a large number of files and then try to expand the policy in the Archives grid in the Management Portal to view the policy job status, StorageX may display the following error:

Failed to get the count of files for the archival policy, please try again. Error: Execution Timeout Expired. The timeout period elapsed prior to the completion of the operation or the server is not responding.

This may indicate that the request to retrieve the file count for the Archive policy job exceeded the default timeout limit on the StorageX database, which is set to 30 seconds.

To work around this issue, you can modify the following default setting in the StorageXServer.exe.config file on your StorageX server:

<add key="SqlOptions.SelectCommandInitTimeout" value="30" />

Change the default setting, then restart the StorageX Server service.

StorageX may be slow to cancel running Archive policies when throttling is enabled

If you create an Archive policy that uses a specific data engine, enable throttling on that data engine, run the Archive policy, and then cancel the policy in the StorageX Console, StorageX may require a significant amount of time to cancel the running policy, especially with a large number of files included in the policy.

This occurs because the data engine is already archiving files included in the policy, but the rate of archival is throttled at the rate specified when you enabled throttling. The data engine must finish archiving in-progress files before the policy can be stopped.

Linux universal data engines running multiple Archive policy jobs may cause Management Portal display issues

If you run multiple Archive policy jobs using a Linux universal data engine, and the Archive policy includes multiple paths, you may encounter issues with the StorageX Management Portal. In some situations, the Job Status column in the Archives grid may not update correctly, continuing to display a status of Running for jobs that have already been completed.

In addition, the Files Archived column in the Archives grid may not accurately reflect the number of files archived to the target object storage resource.

Workload Tiering policy issuesThis section lists known issues related to Workload Tiering policies.


Known issues

StorageX Console incorrectly displays Workload Tiering policies as Migration policies in Alerts tab

If you create and run a Workload Tiering policy in StorageX, when you start the StorageX Console interface and try to view the status of the policy in the Alerts tab on the center pane, the Workload Tiering policy is incorrectly listed in Alerts as a Migration policy.

However, the policy is correctly listed as a Workload Tiering policy in the Events tab. The incorrectly listed policies on the Alerts tab can be safely ignored.

Maintenance Portal issuesThis section lists known issues related to the Maintenance Portal tab in the StorageX Management Portal.

Cassandra grooming job not running as scheduled

If you have a StorageX installation that uses Cassandra, you may encounter an issue where the scheduled Cassandra grooming job does not run on its configured schedule. This may indicate that your Cassandra environment is running out of memory during the grooming process.

When Cassandra grooms data, it needs to first store the data in memory, and with a large number of tombstones (deletion markers), this can cause Cassandra to run out of memory and risks a failure of the cluster as a whole. To protect the cluster, Cassandra automatically cancels grooming when there are too many tombstones to safely store, so that an out-of-memory error will not occur.

REST API issuesThis section lists known issues related to the StorageX REST API.

User can only use the “equals” operator for tags when creating or updating datasets

If you use the StorageX API to create or update a dataset, the API allows you to use either the "equals" or "contains" value for the TagObject.isx-scan-name > operator parameter of the DatasetExpression property. StorageX successfully runs the API call, and the respective operator is stored in the database.

However, the API and StorageX Management Portal currently only support using the "equals" operator for the TagObject.isx-scan-name parameter. If you use the "contains" operator when you create or modify a dataset using the API, when you view the dataset in the Management Portal, the operator for the scan name is displayed as equals.

User cannot specify a folder path when using the policy-creation POST method request

If you use the policy-creation POST method request in the StorageX REST API, you cannot specify a folder location or path, despite the FolderPath option being displayed in the model schema for the API call.


Additions to documentation

If you specify a folder location or path when using this POST method request, the StorageX REST API will be unable to run the API call.

To work around this issue, use the POST method request to create the policy and then use the PUT method request for updating policy properties to add the new policy to a specific folder.

REST API endpoint data does not update properly if there are errors in the schema keys

If you use a PUT call in the StorageX REST API and specify an incorrect schema key name, StorageX does not update the endpoint specified for the call and does not return an error warning you that nothing was updated.

Additions to documentationThe product documentation is up-to-date and provides the latest information. For more information about system requirements, installing the product, and using the product, refer to the StorageX Administrator’s Guide and the StorageX online help.

Contacting Technical SupportThis section defines how to get additional support and information.

NOTETo obtain product version, build number, and license information, click About Data Dynamics StorageX on the Help menu.

Technical supportIf you encounter technical problems, go to the Data Dynamics, Inc. Technical Support site at www.datdynsupport.com or send an email to [email protected].

Include the following information in your email or support request:

• Product name, version, build number, and license serial numbers

NOTETo obtain your product name, version, build number, and license serial numbers, log on to a computer where you installed the StorageX Console. On the Help menu, click About Data Dynamics StorageX. StorageX displays the product name, version, and build number. Click Edit License Keys and Notifications to view license key information.

• Operating system on which the StorageX server and StorageX Console are installed

• Your company name

• Your name and a phone number where we can reach you

• Problem description



mailto:[email protected]

Legal notice

License supportTo purchase new licenses of StorageX or extend the StorageX evaluation period, send an email to [email protected].

If you want to purchase new licenses for StorageX, include the following information in your e-mail message:

• Company name

• Your name, job title, and a phone number where you can be contacted

• Product name and version you want to purchase

If you want to extend your StorageX evaluation period, include the following information in your e-mail message:

• Company name

• Your name, job title, and a phone number where you can be contacted

• Operating system on which the StorageX server and StorageX Console are installed

• Product information, including the following information:

• Product name

• Version number

• Build number

• License details for the StorageX evaluation you want to extend, including created date, customer contact name and ID, and the features you want enabled in the product.

Legal noticeCopyright © 2019 Data Dynamics, Inc. All Rights Reserved.

The trademark Data Dynamics is the property of Data Dynamics, Inc. StorageX is a registered trademark of Data Dynamics Inc. All other brands, products, or service names are or may be trademarks or service marks of, and are used to identify, products or services of their respective owners.

Notice: This document is for informational purposes only and does not set forth any warranty, expressed or implied, concerning any software, software feature, or service offered or to be offered by Data Dynamics, Inc. Data Dynamics, Inc. reserves the right to make changes to this document at any time, without notice, and assumes no responsibility for its use. This informational document describes features that may not be currently available. Contact a Data Dynamics sales office for information on feature and product availability. Export of technical data contained in this document may require an export license from the United States government.

The authors and Data Dynamics, Inc. shall have no liability or responsibility to any person or entity with respect to any loss, cost, liability, or damages arising from the information contained in this book or the computer programs that accompany it.

Data Dynamics, Inc.

Corporate HeadquartersData Dynamics, Inc.

101 Cedar Lane, Suite 102

Teaneck, NJ 07666

Tel: 1-713-491-4298

Fax: 713-491-4882

Email: [email protected]




Date post:	30-May-2020
Category:	Documents
Upload:	others
View:	9 times
Download:	0 times

StorageX Release Notes - datadynamicsinc.com › docs › releasenotes › ...Enables configuration...

Documents