No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


OceanStor 9000 V300R006C00 File System Feature Guide 12

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).


This section describes the impact on system performance, compatibility issues, and application restrictions of InfoReplicator.

Impact on System Performance

Remote replication occupies resources on the local and remote storage systems and therefore compromises storage system performance. The impact on system performance is directly proportional to the data synchronization rate. The impact on replication bandwidth and latency is limited to less than 20% of the total.

Compatibility Issues

InfoReplicator is a directory-based replication feature and has compatibility issues with other system features. Table 6-5 describes the compatibility issues of InfoReplicator with other system features.
Table 6-5  Compatibility issues of InfoReplicator with other system features


Compatibility Issues


  • Snapshot directories cannot be replicated. This means that you cannot configure remote replication for the snapshot directory.
  • Snapshots created by a remote replication session cannot be manually deleted.
  • Snapshots cannot be created for all the parent and child directories of a directory already involved in remote replication.
  • A snapshot directory or directory with snapshots cannot be specified as the source or destination of a replication pair.


  • To create the remote replication pair when InfoLocker is enabled, the source and destination directories must have the same InfoLocker attributes, and the write once read many (WORM) clock must be consistent between the source and destination. The time difference, if any, must be within 60 minutes, and the WORM protection periods for both directories must be the same.
  • The destination directory of a replication pair that has InfoLocker enabled must be empty.
  • InfoLocker attributes cannot be configured for the child directories of the source and destination directories any more when the replication pair has been created.
  • InfoLocker configuration cannot be modified for the destination directory. If you disable InfoLocker write protection for the destination directory of the pair with InfoLocker configured, the replication relationship is suspended between these directories and cannot be restored.


  • The quota and statistics information about the source directory cannot be replicated to the destination directory. To reduce the failover time, you are advised to configure InfoAllocator for the destination directory before starting replication. This configuration ensures that the source and destination directories have the same InfoAllocator settings.
  • You cannot modify the quota for a write protected destination directory. The quota can be modified after you disable write protection for the directory.
  • The quota of the source directory can be modified anytime because this directory is never write protected.
Network data management protocol (NDMP) backup
  • The NDMP backup window and window of InfoReplicator should not conflict when making the policy. Because if InfoReplicator and NDMP backup service performed at the same time, they will influence the performance by each other.
  • OceanStor 9000 does not support snapshot nesting. If the snapshot used by InfoReplicator does not deleted immediately after service finished, please ensure that the snapshot created by InfoReplicator and the snapshot created by NDMP backup do not have nesting relations.

Application Restrictions

  • The remote replication feature only supports replication of regular files, directories, and symbolic link files.
  • When a directory is added to a replication pair as the source or destination directory, the full path to the directory and its parent directories cannot be deleted, moved, or renamed; otherwise, the remote replication may not work correctly, or even the user data may be lost.
  • When a directory is added to a replication pair as the source or destination directory, its parent or child directories cannot be added to another pair.
  • When a directory is added to a replication pair as a destination directory, it cannot be added to another pair as either the source or destination directory.
  • When the source directory has several destination directories (in one-to-many replication), the roles of the source and destination directories cannot be switched.
  • The roles of the source and destination directories cannot be switched before initial synchronization is complete.
  • The quota information, share permission, strip size, and redundancy ratio of the source and destination directories are not switched together with the directory roles. You need to manually configure them for the directories before a failover. You are advised to configure the same attributes for the destination directory as the source directory before you create a replication pair.
  • When a storage system has multiple subnets, you can only add nodes of one subnet to the replication zone.
  • Data transmitted across clusters is not encrypted and has security risks. You are advised to deploy virtual private network (VPN) devices when enabling InfoReplicator to ensure data transmission security. Also, you are advised to deploy physical firewalls to defend against distributed denial of service (DDoS) attacks that interrupt communication by occupying system resources in a short time.
  • The password of the channel authentication account (_machine_user) must be consistent between the local and remote clusters. After changing the account password of one end, modify the account password of the other end.
Updated: 2019-06-27

Document ID: EDOC1000122519

Views: 109406

Downloads: 166

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next