StorageX Release Notes - Data Dynamics, Inc · · 2017-09-30StorageX Release Notes 1 7.7 Data...

StorageX Release Notes

7.7

Data Dynamics StorageX 7.7 Release Notes

November 2015This 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 11

• “Additions to documentation” on page 24

• “Contacting Technical Support” on page 24

• “Legal notice” on page 25

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 Calendar view and Cutover Estimation tab” on page 2

• “Report scheduling and distribution functionality” on page 2

• “New StorageX reports” on page 2

• “StorageX server/replication agent policy and replication task capacity expanded” on page 3

• “New SID mapping rule functionality” on page 3

• “Phased Migration policy import functionality” on page 3

• “Multi-node cluster functionality added for Data Movement policies and Migration Projects” on page 3

• “Support added for Microsoft SQL Server 2014” on page 3

1

Why install this version?

• “Policy Action functionality improved” on page 4

• “StorageX assigns policies to replication agents in agent groups based on agent availability” on page 4

• “StorageX allows users to specify a root path for Migration Project designs with EMC Isilon OneFS destinations” on page 4

• “StorageX Console displays number of policies created from template” on page 4

• “Existing email notifications automatically updated to global notification profiles when you upgrade StorageX” on page 4

New Calendar view and Cutover Estimation tabStorageX now provides a graphical representation of upcoming scheduled items with the Calendar view. The StorageX Calendar provides daily, weekly, and monthly views of your scheduled actions that you can filter and group to identify any conflicts in your schedule.

StorageX also now provides a new Cutover Estimation tab. The Cutover Estimation tab allows you to plan cutover windows for one or more of your resources. The Cutover Estimation tab analyzes policies based on past incremental runs to determine if they will finish within your specified cutover window.

NOTEThe Cutover Estimation tab provides only an estimate, based upon previous policy runs and available replication agents. The cutover window suggested by a specific cutover plan should be viewed as a recommendation, not as a requirement.

Report scheduling and distribution functionalityStorageX now allows you to configure reports to run on a specified schedule. You can schedule a report to run at a specific time, on a per-minute, hourly, daily, or weekly basis, or regularly over a date range, as necessary for your environment.

You can also configure StorageX to automatically distribute a scheduled report each time it runs. You can have StorageX save a completed report to a specified location, email a completed report to one or more recipients configured in an SMTP email notification profile, or both. StorageX can distribute most reports in either Microsoft Excel (XLSX) or comma-separated value (CSV) format, although certain reports can only be saved in CSV format.

New StorageX reportsStorageX 7.7 adds two new reports to help you understand how you are using resources in your StorageX environment. The following reports are now included in the Reporting view:

New Resource Baseline ReportProvides detailed baseline information about selected file storage resources managed by StorageX, including DNS configuration information, management accounts, volume and filesystem statistics, quotas, and more.

New CIFS and NFS Resource Connections ReportProvides information about the servers or client nodes that are accessing your CIFS and NFS storage resources when the report is run.

2 StorageX Release Notes


StorageX server/replication agent policy and replication task capacity expandedStorageX applications, including the StorageX server, Console, Windows replication agent, FileInsight, LogViewerX, and the Support Site Kit, now run as 64-bit processes. The expanded virtual memory space allows the server to run more policies simultaneously and the Windows replication agent to run larger and more frequent replication jobs simultaneously. The default for concurrent jobs on the Windows replication agent is now 16.

NOTES:

• The Linux replication agent does not operate as a 64-bit process.

• You cannot upgrade your previously installed version of StorageX in-place, as the default installation location has changed. See “How to install” on page 5 for more information.

New SID mapping rule functionalityStorageX now allows you to configure your Phased Migration policies to automatically map SIDs from the source to the destination using one or more SID mapping rules. You can replace any SID in a CIFS security descriptor with any other SID and even translate SIDs across domains. SID mapping rules are configured in a SID map file for each replication agent.

Phased Migration policy import functionalityStorageX 7.7 lets you import one or more sets of sources and destinations to use for a Phased Migration from a comma-separated value (CSV)-format policy import file. The New Phased Migration Policy Wizard takes those sources and destinations and creates a separate Phased Migration policy for each of up to 50 pairs of resources. This allows you to quickly create large numbers of policies when you know the sources and destinations you want to use.

Multi-node cluster functionality added for Data Movement policies and Migration ProjectsFor Data Movement policies and Migration Projects, StorageX now allows you to choose which nodes to utilize for reading and writing to and from NetApp and EMC Isilon clusters.

NOTENode selection is not on a per-policy level, but per NetApp vFiler or EMC Isilon cluster.

Support added for Microsoft SQL Server 2014StorageX now supports installing the StorageX database in a Microsoft SQL Server 2014 environment. StorageX now requires one of the following versions of Microsoft SQL Server:

• Microsoft SQL Server 2012 Express, Standard, or Enterprise Edition

• Microsoft SQL Server 2014 Express, Standard, or Enterprise Edition

For more information about StorageX database requirements, see the StorageX Administrator’s Guide.

StorageX Release Notes 3


Policy Action functionality improvedStorageX 7.7 improves the existing Policy Action functionality to streamline the process for moving from one policy phase to another. This reduces confusion and makes the migration policy workflow easier to use within the product.

StorageX assigns policies to replication agents in agent groups based on agent availabilityIn StorageX 7.7, when you run a policy using an agent group, StorageX checks the availability of each agent in the group when assigning the policy to a specific agent. If an agent is already busy, StorageX does not automatically assign the policy to that agent but instead checks the availability of the other agents in the group to see which agent is not already overburdened.

StorageX allows users to specify a root path for Migration Project designs with EMC Isilon OneFS destinationsIn StorageX 7.7, when you create a Migration Project with an EMC Isilon OneFS storage resource as the destination, StorageX lets you use the default /ifs root path for the destination or specify a custom root path to use for one or more of your migrations. For example, instead of /ifs, you could change the root destination to /ifs/data. To configure a root path other than the default, in the Specify Destinations window of the New Migration Project Design Wizard, click Destination Path and specify the root you want to use.

StorageX Console displays number of policies created from templateIn StorageX 7.7, when you create one or more Data Movement policies using a template, the Summary window for the template now displays the number of policies created from that specific template. This information is displayed on the right-hand side of the Policies area within the Summary window.

Existing email notifications automatically updated to global notification profiles when you upgrade StorageXStorageX will now automatically update your previously configured email notifications when you upgrade StorageX to the latest version.

StorageX will continue to send email notifications as configured, and you can now use the updated notification profiles in any area of the product where email notifications are available.


How to install

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

NOTES:

• Because StorageX 7.7 utilizes a 64-bit architecture, you cannot directly upgrade from StorageX 7.6 to StorageX 7.7. Instead, you must first uninstall all StorageX 7.6 servers and Console computers, leaving the StorageX database in place, and then run the installation package for the new version of the product.

• Ensure that you know the database path to use when installing StorageX 7.7 before uninstalling version 7.6 and running the new installation package.

• Ensure the account you use to run the version 7.7 installation package has dbowner rights on the version 7.6 iStorageX database.

• If you want to upgrade from StorageX 7.5 to StorageX 7.7, you must first upgrade from version 7.5 to version 7.6, and then uninstall the StorageX 7.6 server and Console, leaving the upgraded StorageX database in place, and then run the StorageX 7.7 installation package.

• When you uninstall StorageX 7.6 and run the new installation package, the product retains all licenses, configurations, customizations, policies, resources, and reports.

• You can only upgrade to StorageX 7.7 from StorageX 7.6, StorageX 7.6 Service Pack 1, or StorageX 7.6 Service Pack 2.

• 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 StorageX server or StorageX Console computer where you want to install the product, 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. In the StorageX Console, cancel any running policies.

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.


Resolved issues

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.

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. If you configured the firewall to allow the replication agent access as a program or service, you must modify those existing firewall rules for the agent to reflect the correct installation folder for StorageX 7.7.

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 returns misleading “Source does not exist” error when creating a Phased Migration policy for NFS exports” on page 7

• “User cannot manually advance Phased Migration policies to Final Phase” on page 7

• “StorageX returns “String or binary data would be truncated” error when adding replication filters to a policy” on page 7

• “StorageX returns “Unable to mount an export for NFS operations” errors when running NFS migration policies” on page 8

• “StorageX may display incorrect values in the Files Copied column” on page 8

• “StorageX does not allow user to browse Data ONTAP 8.3 clusters to add SVMs when FCP is configured” on page 8

• “StorageX returns “Unsupported ACE type” error when cloning shared folder with Auditing permissions configured” on page 8

• “StorageX cannot copy security for NFS files with backslashes in the file name when “Enable copy-in-place” is not set” on page 9

• “Phased Migration reports display incorrect data when exported to Excel format” on page 9

• “All service recovery options for remotely deployed replication agents are set to “Take No Action”” on page 9

• “StorageX displays “Unknown” status for running policies and jobs after StorageX server restarts” on page 9


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

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

Resolved issues

• “StorageX allows users to assign empty agent groups to policies” on page 9

• “StorageX does not properly copy top-level folder permissions from Data ONTAP to EMC Isilon resources” on page 10

• “StorageX Console is slow when renaming DFS folders” on page 10

• “Archival Migration policy schedules not correctly stored” on page 10

• “StorageX policies do not migrate NFS SUID and GUID permissions correctly” on page 10

• “StorageX policies duplicate data on NFS resources in certain situations” on page 10

• “StorageX unable to create file system structure on EMC VNX destinations when executing Migration Project designs” on page 11

StorageX returns misleading “Source does not exist” error when creating a Phased Migration policy for NFS exportsIn StorageX 7.6, if you create a Phased Migration policy and include an NFS export that uses the NTFS security style, StorageX returns the following error message:

Source does not exist

This message does not correctly describe the issue with the specified export. This issue has been addressed in StorageX 7.7. StorageX now displays a more useful error message when an NFS export cannot be accessed by the StorageX server.

User cannot manually advance Phased Migration policies to Final PhaseIn StorageX 7.6, if you create a Phased Migration policy, set the Never advance automatically setting in the Migration Options > Incremental Phase tab of the policy Properties window, and run the policy through at least one incremental replication, when you right-click the policy you cannot tell StorageX to manually advance from the Incremental Phase to the Final Phase. All options in the right-click Policy Action menu are unavailable.

This issue has been addressed and no longer occurs in StorageX 7.7. StorageX now allows you to manually advance a Phased Migration policy to the Final Phase, even when the Never advance automatically option is set.

StorageX returns “String or binary data would be truncated” error when adding replication filters to a policyIn StorageX 7.6, when you create a Phased Migration, Disaster Recovery, or Replication policy and add multiple exclusion or inclusion replication filters to that policy, the StorageX Console may return the following error message:

String or binary data would be truncated. The statement has been terminated.

This error message indicates that the combined paths for the specified replication filters exceeds the 256-character limit allowed by StorageX.

This issue has been addressed in StorageX 7.7. The StorageX Console now has an expanded total character limit of 4000 characters for replication filter paths in a policy and displays a more informative error message when a user exceeds that limit.


Resolved issues

StorageX returns “Unable to mount an export for NFS operations” errors when running NFS migration policiesIn StorageX 7.6, migration policies using the NFS protocol may fail intermittently due to insufficient permissions, with StorageX returning the following error message in the Details dialog box:

Unable to mount an export for NFS operations

StorageX returns this error when the NFS export policy on the resource does not include the replication agent, but this error may also be encountered even when you specifically provide access to the NFS source and destination resources. The issue occurs because cached NFS settings are not properly cleaned up on the StorageX server when a policy runs.

This issue has been addressed and no longer occurs in StorageX 7.7. StorageX now automatically refreshes cached NFS settings at the start of an NFS migration policy run and recognizes the most recent permissions granted to the StorageX server.

StorageX may display incorrect values in the Files Copied columnIn StorageX 7.6, when StorageX runs a migration policy, the Files Copied column in the Policy Status area may display double the number of files actually copied from the source to the destination. This issue occurs because StorageX erroneously counts migrated security attributes as copied files.

This issue has been addressed and no longer occurs in StorageX 7.7. The Files Copied column now only displays the number of actual files copied from the source to the destination, while the new Files Security Copied column displays the number of files for which security attributes were copied.

StorageX does not allow user to browse Data ONTAP 8.3 clusters to add SVMs when FCP is configuredIn StorageX 7.6, if you try to add an SVM and browse an existing Data ONTAP 8.3 cluster which has one or more Fibre Channel Protocol (FCP) interfaces configured, StorageX returns the following error:

Object reference not set to an instance of an object

This issue has been addressed and no longer occurs in StorageX 7.7. You can now browse a Data ONTAP 8.3 cluster with FCP and select an SVM to manage in StorageX without encountering the error above.

StorageX returns “Unsupported ACE type” error when cloning shared folder with Auditing permissions configuredIn StorageX 7.6, when you try to clone a CIFS shared folder on which Auditing permissions were configured, StorageX returns the following error:

Unsupported ACE type: SYSTEM_AUDIT_ACE_TYPE

This issue has been addressed and no longer occurs in StorageX 7.7. StorageX now allows you to successfully clone a CIFS shared folder with Auditing permissions to a specified destination.


Resolved issues

StorageX cannot copy security for NFS files with backslashes in the file name when “Enable copy-in-place” is not setIn StorageX 7.6, if the Enable copy-in-place option is not set for a policy, and you run that policy on a NFS resource where the names of the files on the resource include one or more backslashes (\), StorageX returns an error and cannot copy security attributes for those files.

This issue has been addressed and no longer occurs in StorageX 7.7. StorageX now correctly copies security attributes for files where the filename includes backslashes.

Phased Migration reports display incorrect data when exported to Excel formatIn StorageX 7.6, when you run a Phased Migration report in the StorageX Console and then export that report in Excel (.xlsx) format, the exported Excel report may display data that does not match the data displayed in the Console.

This issue has been addressed and no longer occurs in StorageX 7.7. Exported Phased Migration reports in Excel format now display data that matches data displayed in the Console.

All service recovery options for remotely deployed replication agents are set to “Take No Action”In StorageX 7.6, when you remotely deploy a replication agent to a server other than the StorageX server, log on to that server, open the Services Administrative Tool, and view the Recovery tab of the Properties dialog box for the StorageX Replication Agent service, all available service recovery options are set to Take No Action.

This issue has been addressed and no longer occurs in StorageX 7.7. The First failure and Second failure service recovery options for all replication agents are now set to Restart the Service, whether the agent is deployed locally or remotely.

StorageX displays “Unknown” status for running policies and jobs after StorageX server restartsIn StorageX 7.6, when the StorageX server is restarted while one or more policies or jobs are in progress, the product does not retain knowledge of the status of running policies or jobs after the restart process is completed. The server displays the status of those policies as “Unknown”.

This issue has been addressed in StorageX 7.7. The StorageX server now properly tracks and cleans up any running jobs or policies after restarting.

StorageX allows users to assign empty agent groups to policiesIn StorageX 7.6, you could create a Phased Migration, Disaster Recovery, or Replication policy and assign any agent group to run that policy, even if the agent group had no replication agents. StorageX then returned an error that no valid agents were found for the agent group.

This issue has been addressed in StorageX 7.7. Users can no longer assign agent groups with no replication agents to policies.


Resolved issues

StorageX does not properly copy top-level folder permissions from Data ONTAP to EMC Isilon resourcesIn StorageX 7.6, when you use a Migration Project to migrate a shared volume on a Data ONTAP resource to an EMC Isilon resource and the share has non-default permissions configured, the Migration Project does not accurately replicate the share permissions of the top-level folder on the Data ONTAP resource to the Isilon destination.

This issue has been addressed and no longer occurs in StorageX 7.7. Migration Projects now correctly replicate top-level permissions from Data ONTAP shared volumes to EMC Isilon destinations.

StorageX Console is slow when renaming DFS foldersIn previous versions of StorageX, when you create a folder in a DFS namespace, add links to the folder, and then rename the folder, the StorageX Console requires several seconds to change the folder name.

This issue has been addressed in StorageX 7.7. The StorageX Console has been modified to make the folder renaming process significantly faster.

Archival Migration policy schedules not correctly storedIn StorageX 7.6 Service Pack 2, when you create an Archival Migration policy with a schedule, that schedule is not properly stored in the database unless you make a change to the schedule in the policy’s Properties tab.

This issue has been addressed in StorageX 7.7. Now when you create an Archival Migration policy with a schedule, the schedule is stored in the database correctly, and you can view the policy’s schedule in the new Calendar tab.

StorageX policies do not migrate NFS SUID and GUID permissions correctlyIn StorageX 7.6, when a user creates and runs a Phased Migration policy that migrates data from an NFS source resource to an NFS destination, StorageX does not copy setuid or setgid permission bits from the source to the destination.

This issue has been addressed and no longer occurs in StorageX 7.7. Phased Migration policies now correctly migrate setuid and setgid permission bits.

StorageX policies duplicate data on NFS resources in certain situationsIn StorageX 7.6, in certain cases when a user runs an incremental Phased Migration, Disaster Recovery, or Replication policy to and from NFS resources, the policy appends data to one or more files, doubling the contents of the affected file and increasing file size.

This issue occurs only in the following scenario:

• The policy copies files using the NFS protocol, from a source NFS export to a destination NFS export.


Known issues

• The destination file already exists.

• The source file is smaller than the existing destination file at the time of the incremental copy.

• The Enable Copy-in-place option is set on the policy.

This issue has been addressed and no longer occurs in StorageX 7.7. StorageX now does not duplicate file data on the destination resource when the Enable copy-in-place option is set.

StorageX unable to create file system structure on EMC VNX destinations when executing Migration Project designsIn StorageX 7.6, when a user attempts to execute a Migration Project design with an EMC VNX storage resource as the destination, StorageX may be unable to create the file system structure on the destination resource. This issue occurs when previous versions of StorageX time out when communicating with the EMC VNX resource and cannot complete the design execution.

This issue has been addressed and no longer occurs in StorageX 7.7. StorageX now does not time out while creating the file system structure on the EMC VNX resource and allows the user to successfully execute the design.

Known issuesThe following issues are known issues in StorageX 7.7:

• “Installation and configuration issues” on page 13

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

• “Upgrade issues” on page 13

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

• “StorageX Console issues” on page 13

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

• “Agent management issues” on page 14

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

• “Storage resource management issues” on page 14

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

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

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

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


Known issues

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

• “Migration Project issues” on page 16

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

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

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

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

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

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

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

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

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

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

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

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

• “Phased Migration policy issues” on page 22


Known issues

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

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

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

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

• “Reporting issues” on page 23

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

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

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

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

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


Known issues

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.

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.

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.


Known issues

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.

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.


Known issues

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.

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


Known issues

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.

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.


Known issues

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.

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.


Known issues

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.

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.


Known issues

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.

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.


Known issues

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.

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


Known issues

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.

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.


Known issues

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.

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.

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.


Additions to documentation

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

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


http://www.datdynsupport.com/

mailto:[email protected]


Legal notice

• 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 © 2015 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]



Legal notice


StorageX Release Notes - Data Dynamics, Inc · · 2017-09-30StorageX Release Notes 1 7.7 Data...

Documents

Transcript of StorageX Release Notes - Data Dynamics, Inc · · 2017-09-30StorageX Release Notes 1 7.7 Data...