Scribd
Upload
123 views4 pages

HCP Replication

The document provides steps to configure replication between two HCP systems. It involves enabling the replication feature, installing SSL certificates, configuring replication links, enabling replication for tenants and namespaces, and confirming replication by uploading a file. Major steps are to enable replication, configure SSL certificates between the systems, create an active-active replication link, set up a test tenant and namespace for replication, and verify replication by uploading a file and seeing it replicated between the systems.

Uploaded by

Luis Moralez Jimenez
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
123 views4 pages

HCP Replication

The document provides steps to configure replication between two HCP systems. It involves enabling the replication feature, installing SSL certificates, configuring replication links, enabling replication for tenants and namespaces, and confirming replication by uploading a file. Major steps are to enable replication, configure SSL certificates between the systems, create an active-active replication link, set up a test tenant and namespace for replication, and verify replication by uploading a file and seeing it replicated between the systems.

Uploaded by

Luis Moralez Jimenez
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

HCP Replication Introduction

In this lab, we will configure replication between 2 of the HCP systems in this lab.
 This lab has many systems and other products that we will not be using. The full lab diagram is
at this link.
 The product documentation that we will be referencing is called Replicating Tenants and
Namespaces and is located at this link.

The major steps we will perform to configure HCP replication are:


1. Confirm Replication feature is enabled
2. Installing Secure Socket Layer (SSL) certificates from each system on the other system.
3. Configuring the replication links between the systems.
4. Enabling the replication option for specific Tenants and configure the link it will use.
5. Enabling the replication option for specific Namespaces.
6. Confirm replication by uploading a sample file.
We will end up with 6 browser tabs open to various screens, so keep the tabs straight.

1: Confirm Replication is enabled


KNOW: During the installation process, there is an option to enable the feature.
DO: We will log in and check the menus to confirm the feature

1. Open Firefox and select the link for HCP1.


 Login as admin/f2.

2. Check the Menus


 Select Services > Replication
 If you have menu options, then the feature is enabled. When it not enabled, you receive a
screen stating that it’s disabled.

2: Configure SSL Certificates


KNOW: In order for the HCPs to communicate in a secure, encrypted fashion they have to have
each other’s encryption keys.
DO: We will be executing the steps starting on page 59 of the documentation referenced above.

1. Download the certificate from HCP1 to our PC.


 Select Services > Replication
 Select Certificates > Replication Server
 On the far left of the line is a downward-facing arrow. Right-click it and select Save Link
As. Name the file something like HCP1_Certificate, so we’ll know how to find it later.

2. Download the certificate from HCP2 to our PC.


 Open another browser tab and login to HCP2 as admin/f2.
 Follow all of the same steps as we did on HCP1 to download the HCP2_Certificate.
3. Upload the HCP1 certificate to HCP2.
 Select the Trusted Replication tab
 Use the Browse button to find the HCP1 certificate we downloaded, probably in the Downloads
folder.
 Use the Upload Certificate button, and you should receive a large green notification that the
upload is successful. If you like, you should be able to view the certificate under the Trusted
Replication tab.

4. Upload the HCP2 certificate to HCP1.


 Return to the browser tab for HCP1.
 Follow the same steps to upload the certificate we downloaded from HCP2.
 Now, both HCPs have they keys to establish secure, encrypted communication with each other.

3: Create the replication links

KNOW: HCP offers Active-Active and Active-Passive configurations. The documentation (starting
at page 13) has a detailed explanation of these and the many ways to combine them.
KNOW: Active-Active replication is metadata-first, and the objects themselves are replicated in a
leisurely fashion at a future time, so objects will appear replicated before they truly are. This is best
used to provide a cloud-like experience where requests to any HCP with a replica can serve any
replicated namespace and load can be balanced with a load balancer or round-robin DNS
configuration.
KNOW: With Active-Passive, the metadata is copied with the object, allowing clarity on exactly what
has been replicated. This is best suited for backup or disaster-recovery configurations.

KNOW: Configuring the replication links presumes that the HCP systems already have IP routing
between their respective VLANs and DNS resolution of each other.
DO: We will be executing the steps starting at page 65 in the documentation.

1. Create an Active/Active link between the HCPs.


 From HCP1, browse to Services > Replication > Overview.
 Click on the Create Link button.
 Name the link something useful and descriptive, such as HCP1 <-> HCP2, click next.
 We will create an Active/Active link.
KNOW: The Encryption and Compression features add processing overhead to your system’s
nodes. Use them if the size of your telecom link or regulatory regime require them.

 Click Next
 Use this name for the other HCP: replication.hcp2.hcpdemo.com.
 Click Next, review the config and Finish.
 Browse to HCP2 Services > Replication > Overview and verify that the link is created and its
status is Synchronizing Data.

4: Create Tenants configured for replication


KNOW: When a Tenant is configured for replication and added to a link, all of the Tenant-level
users and their attributes are replicated and visible on the other system. The Namespaces within
the Tenant are enabled for replication as a separate step.
KNOW: Active/Active allows all of these steps can be done from either system.
DO: We will create a tenant and configure it and the links to replicate it.

1. Create a tenant with replication configured


 On HCP1, browse to Tenants > Create Tenant and use the following values:
Name: Rep-Test
Hard Quota: 10G
Namespace Quota: 10
Authentication Type: Local (not AD)
Security Account: Local
Username: replicator
Password: Password123
Enable Features: Replication
 Click Create Tenant. You will receive a green confirmation, and the tenant will be listed.
KNOW: You can enable the replication feature for existing Tenants.

2. Add the Tenant to the replication link


 Browse to Services > Replication and click the gear icon next to the link we created earlier.
 Select the Content tab to select the Rep-Test tenant and user the Add Selected Tenants.
 Confirm the Tenant configuration by browsing to HCP2 and Services > Replication.
 User the gear icon to open the settings for our link and select the Tenants tab. The configured
Tenant should be listed. If you are very fast, you may see the elusive status of “Replicating
Tenant” which indicates that the Tenant is still on its way.

5: Create Namespaces for replication


KNOW: Configuring a Namespace for replication synchronizes the both the objects in the
namespace as well as settings specific to that namespace.
KNOW: Active/Active allows all of these steps can be done from either system.

1. Login to our new Tenant


 On HCP1, under Tenants, expand the Tenant we created.
 Right-click to open the Tenant link in a new tab. The link will look like this:
https://rep-test.hcp1.hcpdemo.com:8000
 Log in with the user created above: replicator/Password123 and change the password as
prompted. Pass123 works.
 Browse to Security > Users and give the replicator user Administrator access to enable the
“Allow namespace management” box and select Update Settings.
For more information on user management, please work through the appropriate companion lab.

2. Create a Namespace
 Under Namespaces, select Create Namespace. Use these parameters:
Name: NS-Rep
Hard Quota: 1G
Configure Features: Replication: On
KNOW: Namespaces can be modified in future to have replication enabled or disabled. The
setting is found by expanding the namespace then Services > Replication.

6: Confirm replication

1. Configure our user to access our Namespace


 Browse through Security > Users and expand our user: replicator
 Expand Assign Namespace Permissions and select the + next to our namespace.
 Click Select All and Assign Namespaces to grant all of the permissions in this namespace to our
lab user.

2. Login to our new Namespace


 Using the tab you still have open for HCP2, browse through Tenants and expand the Rep-test
Tenant.
 Right click the link provided to open the Tenant in a new tab.
 Login with the user we created: replicator/Pass123.
KNOW: the user, its new password, and the configured permissions as created on the other system
were replicated between the HCPs so we can login here.
 Browse through Namespaces to expand our namespace. Right-click the link to open the
namespace browser in a new tab.

3. Upload a document
 On the top right, click the Upload Object button.
 Browse to select a file. The bookmarks file on the desktop is a good choice, but any file will do.
 Select Upload to input the document to HCP2.

4. Confirm it is replicated between the systems


 In the tab on HCP21where we created the namespace, expand it and right-click to open the
namespace in a new tab.
 You should immediately see the replicated file.
KNOW: Even if you uploaded an extremely large file, its metadata will replicate immediately and
appear in the namespace browser while the file’s data is replicating.

END LAB

You might also like