By default, a local account for the source cluster is already configured. Run the isi dm accounts list command, and the output displays the ‘DM Local Account.’

SmartSync account

The steps provided in this section assume a traditional push policy, defined and initiated from the source cluster. After reviewing this section, see the Pull policy section to define an account for a pull policy on the target cluster.

Note: Although the steps in this section reference specific sections for push and pull policies, you may use a single account for a push and pull policy depending on the data-replication topology. The steps in this section reference the push and pull to provide an example.

After encryption is configured, the next step is to add a replication account to the source cluster, pointing replication to a target cluster.

On the source cluster, add a replication account, with the following command:

source-cluster# isi dm accounts create DM dm://[Target Cluster IP]:7722 [Account name: For example ‘target-acc’]

Note: The target cluster IP address may be a hostname, IPv4, or IPv6 address. As a best practice, use a SmartConnect round-robin DNS name for the target cluster IP address.

Optionally, now you can specify the local and remote SmartConnect pools for the source and target clusters, respectively, with the --local-network-pool and --remote-network-pool fields.

Pull policy

To perform a pull policy from the target cluster, add the replication account on the target cluster and enter the source cluster’s IP.

The command is now issued on the target cluster and is updated to the following:

target-cluster# isi dm accounts create DM dm://[Source Cluster IP]:7722 [Account name: For example ‘source-acc’]

Cloud copy Account

To replicate object data to AWS, Azure, or ECS, use the isi dm accounts create command and specify the following:

• Object store type: AWS_S3, AZURE, or ECS_S3
• URI: {http,https}://hostname:port/bucketname
• Access ID, Secret Key
• Optional proxy information

Confirm account creation

Run the isi dm accounts list command again to confirm the account is now created. The new account and the local account are now listed, as displayed in Figure 5.

Figure 5.   isi dm accounts list

The output in the example above lists the ‘DM Local Account’, which is the source cluster’s account. The ‘demo-acc’ is the target cluster’s account and IP address. However, this command is run on the target cluster for a pull policy account. The ‘DM Local Account’ would be the target cluster, while the ‘demo-acc’ would be the source cluster.