StorageX Release Notes - Data Dynamics File-Based Storage ... · It is a software platform for...

StorageX Release Notes

7.8

Data Dynamics StorageX 7.8 Release Notes

August 2016This 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 9

• “Additions to documentation” on page 26

• “Contacting Technical Support” on page 26

• “Legal notice” on page 28

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 NAS file data. This includes heterogeneous vendor support across different storage system platforms, as well as support for both CIFS and NFS protocols.

StorageX provides storage infrastructure management capabilities that allow storage professionals to logically view distributed file 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:

• “New StorageX API” on page 2

• “Updated Replication Module” on page 2

• “OneFS sources added for Migration Project designs” on page 2

• “Improved Resource Baseline Report” on page 2

• “New Simulate Replication option added for Phased Migration policy runs” on page 2

• “New Phased Migration policy templates added” on page 2

• “New StorageX reports” on page 3

• “Additional grooming options for managing StorageX server storage” on page 3

• “New Troubleshooting appendix in StorageX Administrator’s Guide” on page 3

1

Why install this version?

• “New Phased Migration policy options added” on page 3

• “StorageX allows users to export consolidated manifest errors” on page 4

• “Support added for Isilon OneFS 8.0” on page 4

• “Support added for Data ONTAP 8.3.2” on page 4

New StorageX APIStorageX now provides includes its own internal API, which allows advanced users to interact directly with the StorageX replication engine outside of the StorageX Console. This enables users to create their own custom integrations into the StorageX environment.

You can run API calls outside of the Console to create policies, delete policies, get details about policy runs, and perform other common StorageX functions.

Updated Replication ModuleStorageX now allows heterogeneous data replication across both SMB and NFS file storage resources.

OneFS sources added for Migration Project designsStorageX now allows you to create a Migration Project design with OneFS 7.0 and later devices as source resources.

Improved Resource Baseline ReportStorageX now has additional comparison functionality for Resource Baseline Reports. After you create a Resource Baseline Report and run the report at least two times, you can compare one version of the report, the baseline, to a different version of the report.

New Simulate Replication option added for Phased Migration policy runsStorageX now allows you to perform a dry run of a Phased Migration policy without actually replicating any data from the source to the destination, by selecting the Simulate Replication (No Data Copy) in the policy Properties dialog box.

New Phased Migration policy templates addedStorageX 7.8 adds several new Phased Migration policy templates to the product, allowing you to more quickly create policies that fit your environment. These new policy templates do not require daily or weekly default schedules and let you create policies based on how you want to copy files from the source to the destination.

The following Phased Migration policy templates are now included in the Data Movement view:

2 StorageX Release Notes


Phased Migration Template - Copy Older and Existing FilesCan be used to copy files from the source to the destination if the files on the destination exist and are older than the files on the source.

Phased Migration Template - Copy Older or Missing FilesCan be used to copy older or missing files from the source to the destination.

Phased Migration Template - Copy Only Missing FilesCan be used to copy only missing files from the source to the destination.

Phased Migration Template - Mirror CopyCan be used to copy different or missing files from the source to the destination.

Phased Migration Template - Sync Destination with SourceCan be used to synchronize the destination with the source.

New StorageX reportsStorageX 7.8 adds two new reports to provide information about what occurred during the previous Replication policy runs in your environment. The following reports are now included in the Reporting view, under the Disaster Recovery Reports folder:

New Replication Policy All Runs ReportProvides information about every run of every Replication policy specified when the report was created. For example, you can use this report to quickly see which policies have not yet run, which policies have completed, and which policies have errors.

New Replication Policy Last Run ReportProvides information about the status of the most recent run of every Replication policy in StorageX. The report lists only one run per Replication policy.

Additional grooming options for managing StorageX server storageStorageX now allows you to specify how long the product keeps records of policy runs and manifests, as well as configuring the schedule for the data grooming task.

New Troubleshooting appendix in StorageX Administrator’s GuideThe StorageX Administrator’s Guide now provides a troubleshooting appendix. This appendix provides detailed information about common problems you might encounter when using StorageX and explains how to resolve or work around those issues.

New Phased Migration policy options addedStorageX 7.8 adds two new options to the General Options tab of the Phased Migration policy Properties dialog box. You can now select the Copy directories only option if you want the policy to only replicate the directory structure from the source to the destination, or you can select the Copy files > If destination file is older and exists option if you want the policy to only replace existing files on the destination that have time stamps older than files on the source.

StorageX Release Notes 3


StorageX allows users to export consolidated manifest errorsStorageX now allows you to export the consolidated manifest errors for one or more of your policies in .tsv format, by selecting the policies in the My Policies window and selecting Consolidate Manifest Errors. This lets you quickly view and organize the errors StorageX encountered during those policy runs.

If you want to see a spreadsheet of all errors in the manifest for one or more policies, you can export the consolidated manifest errors for your policies in .tsv format from the My Policies window in the Console by right-clicking the policy and selecting Consolidate Manifest Errors. This allows you to quickly view and organize all the errors your policies encountered while running.

Support added for Isilon OneFS 8.0StorageX now supports migrating data to and from storage resources running Isilon OneFS 8.0.

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


How to install

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

NOTES:

• If upgrading to StorageX 7.8, you must upgrade both the StorageX server and StorageX Console to use the same version of the product.

• 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.

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. Download the installation package and double-click the Setup.exe file.

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

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

6. Click Install StorageX.

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

8. 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.

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

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

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

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

13. 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.

14. Click Install to begin the installation.

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

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


Resolved issues

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

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 Web site at www.datadynamicsinc.com/help.

Resolved issuesThis version of StorageX addresses the following issues:

• “StorageX does not display exports for Data ONTAP 8 resources with permanent NetApp licenses installed” on page 6

• “StorageX creates multiple TSV-format manifest files when “List all files” option selected” on page 7

• “StorageX grooming task does not automatically delete old StorageX database entries related to the replication agent” on page 7

• “Migration Project policies do not migrate tree quotas from EMC VNX to EMC Isilon storage resources” on page 7

• “Exported Phased Migration details file displays incorrect error paths” on page 7

• “StorageX policy manifest does not display any errors when some files are copied to the destination with 0 KB size” on page 8

• “StorageX fails to copy some files during an NFS migration with the error “Network Resource Not Found”” on page 8

• “StorageX cannot create new shares on certain Data ONTAP vServer destinations” on page 8

• “StorageX does not scan all DFS namespaces if one or more DFS namespace server names cannot be properly resolved” on page 8

• “Phased Migration policy completes with an error saying that the operation was canceled” on page 9

• “Phased Migration policy incremental runs with Data ONTAP 8.x as the destination copy unmodified files” on page 9

StorageX does not display exports for Data ONTAP 8 resources with permanent NetApp licenses installedIn StorageX 7.7, if you add a Data ONTAP 8 resource, and the resource has a permanent NetApp license installed, StorageX does not display the exports for that resource in the Storage Resources view. This occurs because a permanent NetApp V2 license does not have an expiration date.

This issue has been addressed and no longer occurs in StorageX 7.8. StorageX now correctly verifies permanent NetApp V2 licenses and displays all valid exports when the resource is properly added and configured in the My Resources folder.


http://www.datadynamicsinc.com/help/

http://www.datadynamicsinc.com/help/

Resolved issues

StorageX creates multiple TSV-format manifest files when “List all files” option selectedIn StorageX 7.7, when you select the Event details > List all files option on the General Options dialog box of the Phased Migration policy and then run the policy, the product creates multiple small .tsv files in the specified location instead of one overall file.

This issue has been resolved in StorageX 7.8. When you select the List all files option, StorageX now consolidates all manifest files received from the replication agent into two consolidated manifest files, ManifestDetailFile_X.tsv and ManifestSummaryFile_X.tsv. If either file reaches a default limit of 100 MB in sizes, StorageX rolls the manifest data into a subsequent file and increases the number in the file name by 1.

StorageX grooming task does not automatically delete old StorageX database entries related to the replication agentIn StorageX 7.7, when the regularly-scheduled grooming task ran, the product did not remove entries related to the replication agent from the StorageX database, even if those entries were older than the settings specified in the Options > Data Grooming Options dialog box.

This issue has been addressed and no longer occurs in StorageX 7.8. When the grooming task runs, StorageX automatically removes any replication agent-related entries from the StorageX database that meet the grooming criteria.

Migration Project policies do not migrate tree quotas from EMC VNX to EMC Isilon storage resourcesIn StorageX 7.7, if you run a Migration Project-generated policy with an EMC VNX storage resource as the source and an EMC Isilon storage resource as the destination, and the source includes a tree quota, the policy does not migrate the quota to the destination.

This issue has been addressed and no longer occurs in StorageX 7.8. When you run a policy that migrates a tree quota from an EMC VNX source to an EMC Isilon destination, the policy now correctly creates a directory quota on the EMC Isilon resource.

Exported Phased Migration details file displays incorrect error pathsIn StorageX 7.7, if you run a Phased Migration policy, StorageX cannot access a file on the destination resource, and you export the details of the policy run, the exported .tsv file displays the error path incorrectly.

This issue has been addressed and no longer occurs in StorageX 7.8. The manifest details in the exported .tsv file now match the information displayed in the Operation Details window in the StorageX Console.


Resolved issues

StorageX policy manifest does not display any errors when some files are copied to the destination with 0 KB sizeIn StorageX 7.7, the product did not properly report an error in the manifest if a file was incorrectly copied to the destination with a file size of 0 KB.

This issue has been addressed and no longer occurs in StorageX 7.8. StorageX now properly reports this type of error in the manifest.

NOTEThis hotfix only ensures that the error is reported properly in the manifest, and does not prevent the error from occurring altogether. There are still multiple scenarios, including but not limited to network interruption and conflicts with antivirus software, that can cause a file to be improperly copied with a file size of 0 KB during a Phased Migration policy.

StorageX fails to copy some files during an NFS migration with the error “Network Resource Not Found”In StorageX 7.7, when you create a new Phased Migration policy or run a Phased Migration policy that uses the NFS protocol, some files fail to copy with the error Network Resource Not Found, even if the resource is online and available.

This issue has been addressed and no longer occurs in StorageX 7.8. Phased Migration policies using the NFS protocol now copy files correctly when the resource is available.

StorageX cannot create new shares on certain Data ONTAP vServer destinationsIn StorageX 7.7, if you run the New Phased Migration Policy Wizard and try to create a new share on a Data ONTAP vServer, StorageX may return the following error and does not create the share:

The system cannot find the path specified.

This occurs when no specific share on the destination vServer is set as the Default Admin Share, StorageX has Write access to the root volume or the second-level volume, and the destination share the user wants to create is on a folder within a third-level volume mounted under the second-level volume. In this situation, StorageX cannot correctly detect where to create the share on the destination.

This issue has been addressed and no longer occurs in StorageX 7.8. StorageX now correctly creates the share on the specified destination, even when the Default Admin Share option is not set.

StorageX does not scan all DFS namespaces if one or more DFS namespace server names cannot be properly resolvedIn StorageX 7.7, if a user runs a Phased Migration or Disaster Recovery policy configured to update links on one or more DFS servers, and the server hosting DFS namespace targets or DFS link targets has a DNS configuration issue, the product returns the following error when attempting to scan the namespace prior to updating the links:


Known issues

The namespace could not be enumerated.

StorageX then stops the scan process, and the policy fails, even if there are other namespaces that can be successfully scanned.

This issue has been addressed in StorageX 7.8. StorageX now detects the DNS configuration issue on the hosting server and continues with any other namespaces included in the policy until all namespaces have been scanned.

Phased Migration policy completes with an error saying that the operation was canceledIn some StorageX 7.7 environments, when a user runs a Phased Migration policy, the policy may complete with errors, and then StorageX returns an error message saying that the operation was canceled. This occurs when the replication agent encounters a problem while executing the policy and is forced to stop the policy before completion.

This issue has been addressed and no longer occurs in StorageX 7.8. StorageX is now able to run Phased Migration policies successfully.

Phased Migration policy incremental runs with Data ONTAP 8.x as the destination copy unmodified filesIn StorageX 7.7, when a user performs an incremental Phased Migration policy run with Data ONTAP 8.x as the destination with the Copy files criteria set to different or missing, the manifest shows that the incremental run copied files even if they have not changed since the Baseline Copy.

This issue occurs because the destination overwrites some files’ last modified time stamp. This results in the last modified time being set to the time the file was copied instead of the original source file’s last modified time.

This issue has been addressed and no longer occurs in StorageX 7.8. Incremental policy runs to Data ONTAP 8.x no longer copy unchanged or unmodified files when a user sets the different or missing criteria.

Known issuesThe following issues are known issues in StorageX 7.8:

• “Installation and configuration issues” on page 12

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

• “Upgrade issues” on page 12

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

• “StorageX Console issues” on page 13

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

• “Agent management issues” on page 13

• “Throttling settings are ignored if the source or destination are on the same local server as the agent” on page 13


Known issues

• “Replication agent port cannot be changed” on page 13

• “Storage resource management issues” on page 13

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

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

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

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

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

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

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

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

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

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

• “Migration Project issues” on page 16

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

• “StorageX does not correctly display SmartLocked directories in Advanced Options” on page 16

• “Duplicate Migration Project policies displayed on the My Policies Summary pane” on page 16

• “Error when executing a Like-to-Like Migration Project design using thin provisioning” on page 16

• “StorageX does not display error when validating Migration Project design with SmartLocked OneFS source and non-SmartLocked Data ONTAP destination” on page 17

• “Migration Project policies using SnapMirror cannot be manually advanced to Final Phase” on page 17

• “Compression attributes are not copied from the source to the destination for Migration Projects” on page 17

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

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

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

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


Known issues

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

• “Cannot rename OneFS volumes in Migration Project designs directly from the validation error message” on page 19

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

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

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

• “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 20

• “Final Phase of Phased Migration policies fail in NFS migrations if replication agents do not have root permissions on source exports prior to executing the Migration Project design” 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 21

• “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 21

• “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 manifest incorrectly lists certain unsupported folders as excluded” on page 23

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

• “StorageX may take several minutes to display “Canceled” status for a canceled policy when throttling settings are enabled on the replication agent” 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


Known issues

• “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 25

• “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

• “Report not attached to email if saving the report to a folder fails” on page 26

• “REST API Issues” on page 26

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

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

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 7.8.

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 7.8.


Known issues

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.

Agent management issuesThis section lists known issues related to replication agent management.

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

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

Replication agent port cannot be changed

The port specified for a replication agent on the General tab for a replication agent cannot be changed.

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

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 are sufficiently different.

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.


Known issues

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.

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.


Known issues

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 replication agent 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.

• 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.


Known issues

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.

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 or automatically configure deduplication during Migration Project design execution.

StorageX does not correctly display SmartLocked directories in Advanced Options

If you create a Migration Project design that uses a SmartLocked directory on a OneFS resource as a source, StorageX does not display a selected check box in the Is SnapLock/WORM Source? column in the Advanced Options dialog box.

Duplicate Migration Project policies displayed on the My Policies Summary pane

If you run more than one Migration Project policy using SnapMirror at the same time, and both policies update namespaces, you will see duplicates of each of those policies in the Summary pane for the My Policies folder.

Error when executing a Like-to-Like Migration Project design using thin provisioning

If you create a Like to Like Migration Project design using thin provisioning, where the destination is a pool on a VNX resource, and you only specify one volume size, the design execution will fail with the following error:

Failed to execute Migration project design 'NAME': The operation on VNX machine 'NAME' failed: The auto-extension size provided for the file system is invalid. The auto-extension size (size of file system after auto extension) must be greater

To avoid this issue, you must specify two sizes for the thin provisioning: one for the maximum size and one for the initial file system size.


Known issues

StorageX does not display error when validating Migration Project design with SmartLocked OneFS source and non-SmartLocked Data ONTAP destination

If you create and validate a Migration Project design that uses a SmartLocked directory on a OneFS resource as a source and a non-SnapLocked aggregate on a Data ONTAP resource as the destination, StorageX does not display an error warning you that the migrated directory will not be SnapLocked on the destination.

In order to successfully migrate a SmartLocked directory on the source to a SnapLocked aggregate on the destination, SnapLock must be enabled on the destination aggregate.

Migration Project policies using SnapMirror cannot be manually advanced to Final Phase

If you create a Migration Project design that uses SnapMirror replication, when you run a Phased Migration policy generated from that design, you cannot manually advance the policy to the Final Phase. After the policy runs the initial baseline copy and one or more incremental copies, when you right-click the policy and select Advance policy to the next action the next time the policy runs, then right-click the policy and select Run, the policy does not advance as specified. Instead, the policy runs another incremental copy.

To resolve this issue, right-click the policy and select Properties, then click Migration Options > Incremental Phase. Select After policy’s current Incremental Phase run completes, advance the policy according to the Migration Schedule and click OK. Right-click the policy and select Run, and the policy will advance to the Final Phase.

Compression attributes are not copied from the source to the destination for Migration Projects

StorageX does not support the migration of compression attributes from source to destination for Migration Projects.

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:

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.


Known issues

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 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.

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.


Known issues

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.

Cannot rename OneFS volumes in Migration Project designs directly from the validation error message

If you create a Migration Project design that uses as the source a volume that already exists on the OneFS destination resource and validate the design, StorageX displays an error message indicating that the volume already exists on the destination resource and provides an Edit button to rename the volume on the destination. However, you cannot click the Edit button.

To work around this issue, click Advanced Options in the Summary pane, modify the Destination Path value, click OK, and then re-validate 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.


Known issues

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.

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.


Known issues

Final Phase of Phased Migration policies fail in NFS migrations if replication agents do not have root permissions on source exports prior to executing the Migration Project design

When migrating file data using the NFS protocol and Phased Migration policies generated from a Migration Project design, ensure that the replication agents you want to use to migrate the file data using the NFS protocol have root permissions on all NFS exports on the source file storage resources before you execute the Migration Project design and generate Phased Migration policies for the project.

If the replication agents you want to use to migrate the file data using the NFS protocol do not have root permissions on the source NFS exports before you execute the Migration Project design and generate Phased Migration policies for the project, the Phased Migration policies fail when they run in the Final Phase. In order to continue, you must manually grant the replication agents root access on all of the NFS exports on the destination and then manually run the policies again.

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.

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.


Known issues

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.

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.


Known issues

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.

Phased Migration policy manifest incorrectly lists certain unsupported folders as excluded

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.

This occurs for the following specific folder types, which StorageX does not support migrating:

• Snapshot folders

• System volume information

• Recycle Bin

For more information about the types of files and folders StorageX does not migrate, see the StorageX Administrator’s Guide.


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.

StorageX may take several minutes to display “Canceled” status for a canceled policy when throttling settings are enabled on the replication agent

If you create a Phased Migration policy, run that policy with an agent that has throttling settings enabled, and then you cancel the policy, StorageX may display the status of the policy as In Progress for up to 6 minutes before displaying the correct Canceled status for the policy in the Policy Status area.

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.


Known issues

Reporting issuesThis section lists known issues related to StorageX Reports.

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.


Additions to documentation

Report not attached to email if saving the report to a folder fails

If you set the Report Distribution Settings of a report to enable both Save report to folder and Send email when report is complete and StorageX is unable to successfully save the report to the specified folder, you will receive an error email notification without a report attached.

To work around this issue, ensure that the destination folder specified for the Save report to folder option is valid and that you have the correct privilege settings to write to that folder. If the issue persists, disable the Save report to folder option and run the report again with only the Send email when report is complete option enabled to receive a copy of the report attached to an email.

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

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

If you create or modify any of the StorageX REST API schema keys and include any misspellings or unnecessary spaces, the API requests will not correctly update the endpoint data.

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


http://www.datdynsupport.com/

mailto:[email protected]

Contacting Technical Support

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

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 notice

Legal noticeCopyright © 2016 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:	05-Sep-2018
Category:	Documents
Upload:	tranbao
View:	214 times
Download:	0 times

StorageX Release Notes - Data Dynamics File-Based Storage ... · It is a software platform for...

Documents