Configuring Data Migrator to Cloud
To use Data Migrator to Cloud, you must define the following:
- An established network route. See the Network Administration Guide for details.
- Cloud account.
- Cloud destination.
- Cloud path, which defines the relationship between primary storage and to the cloud destination to which data will be migrated.
- Data migration rules, which define the properties of files that will be migrated.
- Data migration policies, which define rules to apply to specific data migration paths based on the available free space on the source file system. Free space is the amount of unused space allocated to the file system (before it automatically expands, if automatic expansion is enabled for the file system).
- Data migration schedules, which define when data migration policies are run.
- A cloud target is resolvable in a DNS server configured in Global Context.
- A route from the aggregate ports to the Cloud provider (Amazon S3, Microsoft Azure, S3 Cloud Object Storage or HCP) server exists on all nodes.
Checking and setting the status of aggregate ports for Data Migrator to Cloud
In most cases, the default configuration of the ports should be sufficient and you will not need to take any action. To check the current data transfer mode that Cloud Gateway is running, issue the following CLI command:
migration-cloud-service-mode-show
- If this is the first time you are using Data Migrator to Cloud, the system will send data through the aggregate ports with zero copy for the local HCP cloud target.
- If you currently have
Data Migrator to Cloud configured and running, the default will continue to be management ports. You have the option to switch and send data through the aggregate ports. If you decide to use aggregate ports, you must first ensure that the route exists. Once you confirm that the route exists, issue one of the following CLI commands:
- migration-cloud-service-mode-set -a to transfer data through the aggregate ports.
- migration-cloud-service-mode-set -z to transfer data at a higher outgoing performance rate through the aggregate ports for local HCP target servers.
For more information on the CLI commands, see the Command Line Reference
Tagged VLANs are supported with Data Migrator to Cloud. For information on VLANs, link aggregations, and adding aggregations, see the Network Administration Guide.
Ensuring that the route exists when using aggregate ports
To check the existence of a viable route from the EVS hosting the file system to the cloud server you want to migrate files to.
Procedure
Open a BALI command prompt window.
Enter ping -I <source address> <target name>
where <source address> is one of the IP addresses on the EVS associated with the file system and <target name> is the fully qualified domain name of the HCP namespace or cloud provider address.The verification process is complete when the system successfully receives responses to the ping messages from the target. The following is an example of a successful ping to check cloud server reachability from an EVS, with the response of "0% packet loss."
mercury15:$ ping -I 192.168.43.22 ns01.tenant01.hcp01.us.dev.bluearc.com ns01.tenant01.hcp01.us.dev.bluearc.com (10.23.34.58) ... 64 bytes from 10.23.34.58: icmp_seq=0 time=1 ms 64 bytes from 10.23.34.58: icmp_seq=1 time <1 ms 64 bytes from 10.23.34.58: icmp_seq=2 time <1 ms 64 bytes from 10.23.34.58: icmp_seq=3 time <1 ms -- 4 packets transmitted, 4 packets received, 0% packet loss round-trip min/avg/max = 0/0/1 ms mercury15:$
If the route does not exist, refer to the Network Administration Guide.
Ensuring the route exists when using management ports
To check the existence of a viable route from the EVS hosting the file system to the cloud server you want to migrate files to.
Procedure
Open a Linux command prompt
Enter ping <target name>
where <target name> is the fully qualified domain name of the HCP namespace or cloud provider address.If the route does not exist, refer to the Network Administration Guide.
Data Migrator to Cloud Configurations
Two example aggregate port configurations are presented in this section:
- Target on the Internet when using aggregate ports
- Data Migrator to Cloud with aggregate support with the target on the LAN
For all targets, the server must be able to resolve the hostname. Because the target is on the Internet, at least one of the configured DNS servers must be connected to the Internet.
For information on VLAN support, see the Network Administration Guide.Target on the Internet when using aggregate ports
The server must be able to resolve the hostname using one of the aggregate ports. Because the target is on the Internet, at least one of the configured DNS servers must be connected to the Internet.
| Item | Description |
| 1 | node 1 |
| 2 | node 2 |
| 3 | agg_1 |
| 4 | agg_2 |
| 5 | agg_3 |
| 6 | agg_4 |
Data Migrator to Cloud with aggregate support and target on LAN
For this configuration, HNAS must be able to reach a DNS server using aggregate ports, which resolves the names of the target.
| Item | Description |
| 1 | node 1 |
| 2 | node 2 |
| 3 | agg_1 |
| 4 | agg_2 |