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

Reminder

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

upgrade

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

FAQs

How Long Does It Take for Data to Be Replicated to the Remote Storage System After a Pair Synchronization Is Started?

Question

How long does it take for data to be replicated to the remote storage system after a pair synchronization is started?

Answer

Note that a remote storage system is not equal to the secondary storage system. Data can only be replicated from the primary storage system to the remote storage system. Therefore, when the local storage system is the primary storage system, data of the local storage system can be replicated to the remote storage system after the replication pair is synchronized. However, when the local storage system is the secondary storage system, data cannot be replicated to the remote storage system after the pair synchronization.

The data replication time is determined by the following factors:
  • The amount of data to be replicated (initial synchronization)
  • The amount of data changed after the last synchronization (non-initial synchronization)
  • Network bandwidth
  • Performance of storage nodes and disks
  • Number of storage nodes that participate in remote replication
  • Workload of concurrent system tasks
  • Replication transmission rate of a pair

For more details, see Principle Description.

How Can I Ensure That Critical Data Is Preferentially Replicated?

Question

How can I ensure that critical data is preferentially replicated?

Answer

InfoReplicator supports directory-based asynchronous remote replication and allows you to use traffic control and bandwidth limit to improve the overall replication performance. However, this feature cannot identify the importance of data.

When the critical data and common data reside in the same primary directory, the system automatically detects and replicates the changed data but cannot preferentially replicate data.

Therefore, you are advised to sort out critical data before replicating it and store the data under specific directories for separate management. Then, you can add these directories to replication pairs and set a high transmission rate for the pairs to raise the pair priority. In this way, critical data can be preferentially replicated.

Can I Use CLI Commands to Perform Remote Replication Operations?

Question

Can I use CLI commands to perform remote replication operations?

Answer

You can use InfoReplicator to configure remote replication tasks in both the graphical user interface (GUI) and command-line interface (CLI). Configuring remote replication using the GUI has been described in Configuration and Management. Table 6-27 lists the CLI commands used to configure replication tasks. For details about the usage of each command, see OceanStor 9000 Command Reference.

Table 6-27  CLI commands supported by InfoReplicator

Command

Function

create remote_replication general

Creates a replication pair.

change remote_replication general Modifies a replication pair.
show remote_replication general Queries a replication pair.
show remote_replication latest_snap_path Obtains the path to the latest replication snapshots.
delete remote_replication general Deletes a replication pair.
change remote_replication split Splits a replication pair.
change remote_replication switch Switches the roles of the source and destination.
change remote_replication synchronize Starts data synchronization.
show remote_replication zone Queries a replication zone.
change remote_replication zone Changes a replication zone.
clear remote_replication zone_ip_range Clears the IP address segments in a replication zone.
clear remote_replication zone_exclude_ip Clears the excluded IP address segments in a replication zone.
show remote_replication zone_working_ip Queries available IP addresses in a replication zone.
create remote_replication channel Creates a replication channel.
change remote_replication channel Modifies a replication channel.
delete remote_replication channel Deletes a replication channel.
show remote_replication channel Queries a replication channel.
show remote_replication link_info Queries the link information of a replication channel.

How Is a Replication Cycle Measured?

Question

A replication pair can be automatically or manually synchronized. How is a replication cycle measured for automatic synchronization?

Answer

When the synchronization method is set to Manual, the remote replication session is manually started by the replication administrator. When the replication method is set to Timed wait when synchronization begins or Timed wait when synchronization ends, the timer starts to measure time when synchronization starts or completes. The timer measures time differently for different phases and operations. The following explains how the timer works.

Normal Conditions
  • Pair creation

    When you are creating a pair, no timer is created.

  • Data synchronization
    When a synchronization task starts, the system creates a timer according to the synchronization method. Only when the synchronization method is Timed wait when synchronization begins or Timed wait when synchronization ends, the system creates a timer. When other synchronization methods are used, no timer is created.
    • Timed wait when synchronization begins: The system creates a timer to measure time when a synchronization task starts and creates another timer after the specified period when the next synchronization starts. If a synchronization task is not completed within the period measured by the timer, the synchronization method is changed to Timed wait when synchronization ends and the next synchronization starts immediately after the current one is complete.
    • Timed wait when synchronization ends: The system creates a timer to measure time when a synchronization task is complete and creates another timer after the specified period when the next synchronization ends.
  • The system deletes the timer when the pair state is Split, Interrupted, or Invalid.

Synchronization Method Change

Changing the synchronization method will change the timer and therefore affects the synchronization progress. For details about how the timer changes with the synchronization method, see Table 6-28 and Table 6-29.
Table 6-28  Changing the synchronization method when the pair state is Normal

Original Synchronization Method

Changed to Manual

Changed to Timed wait when synchronization begins

Changed to Timed wait when synchronization ends

Manual

-

The timer is created and synchronization starts after the specified period measured by the timer.

The timer is created and synchronization starts after the specified period measured by the timer.

Timed wait when synchronization begins

The timer is deleted.

The timer is reset and measures the time based on the newly specified period.

The timer is reset and measures the time based on the newly specified period.

Timed wait when synchronization ends

The timer is deleted.

The timer is reset and measures the time based on the newly specified period.

The timer is reset and measures the time based on the newly specified period.

Table 6-29  Changing the synchronization method when the pair state is Synchronizing

Original Synchronization Method

Changed to Manual

Changed to Timed wait when synchronization begins

Changed to Timed wait when synchronization ends

Manual

-

The timer is created and synchronization starts again after the specified period measured by the timer.

-

Timed wait when synchronization begins

The timer is deleted.

The timer is reset and measures the time based on the newly specified period.

The timer is deleted.

Timed wait when synchronization ends

-

The timer is created and synchronization starts again after the specified period measured by the timer.

-

NOTE:
- indicates that the timer does not exist and will not be created.

How Can I Know a Data Synchronization Is Complete?

Question

How can I know a data synchronization is complete?

Answer

InfoReplicator provides a GUI-based management and monitoring page. You can log in to DeviceManager to view the replication pair status in real time.

When the data synchronization is complete, a Succeeded in Synchronizing a Remote Replication Pair event is reported. You can go to the Alarm > All Events page to confirm it.

As shown in Figure 6-27, when the initial synchronization of a pair is complete, Data Status is Consistent, a snapshot has been created for the secondary end, which indicate that the data synchronization is complete. You can also view the synchronization start time and end time of a pair in the following figure.
Figure 6-27  DeviceManager management page
Translation
Download
Updated: 2019-06-27

Document ID: EDOC1000122519

Views: 78891

Downloads: 147

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next