Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Current »

This article describes the process to install JetStream DR software in an AVS environment.

Issue

The AVS Cloud Admin account is granted limted administrative privileges that can impede manual installation of JetStream DR components (such as registering plugins, installing IOFilters, etc). To overcome this challenge, a set of AVS Run commands are provided to automate and facilitate installation and configuration of JetStream DR software.

Installation

Step 1: Log in to the Azure portal (portal.azure.com)

Step 2: Navigate to the AVS private cloud platform where JetStream DR software is intended to be deployed.

Step 3: Locate the Run command in the left panel then click it.

image-20240208-210914.png

Step 4: Under Packages select JSDR.Configuration.

image-20240208-210944.png

Step 5: From the dropdown of JSDR.Configuration select Install-JetDRWithStaticIP.

image-20240208-211026.png

Alternatively, JetStream DR can be configured using DHCP. To do this, use the Run command Install-JetDRWithDHCP instead.

Step 6: Complete the form by entering all necessary details then click the Run button.

image-20240208-211104.png

Required Fields and descriptions:

Protected Cluster → Name of the AVS cluster to be protected.
DataStore → Name of the datastore where the JetStream MSA will be deployed.
VMName → Name of the JetStream MSA VM (e.g., JetStreamServer).
Cluster → Name of the AVS cluster where the JetStream MSA will be deployed.
MSAIP → IP address of the JetStream MSA VM.
DNS → DNS IP address the JetStream MSA VM should use.
Gateway → IP address of the network gateway for the JetStream MSA VM.
MSA Credentials → Credentials of the JetStream MSA VM root user.
HostName → Hostname (FQDN) of the JetStream MSA VM.
Network → Name of the NSX-T Data Center network segment where the JetStream MSA will be deployed.
Retain Up to → Number of days to retain the Run command execution task.
Specify name for execution → An alphanumeric name for the execution. It is used to verify if the cmdlet runs successfully and should be unique for each run.
Timeout → A maximum timeout value for the executed Run command.

If DNS is not configured or resolving properly, enable the RegisterWithIp option (shown below).

image-20240208-211153.png

Step 7: The Run command status can be monitored under “Run execution status.”

image-20240208-211246.png

  • Additional details about a Run command execution can viewed by selecting its Execution name.

    image-20240208-211312.png

    image-20240208-211349.png

  • The current status of Run command execution can be viewed in realtime from the Information panel.

    image-20240208-211417.png

If JetStream DR will be deployed to multiple clusters within a single DC, use the Run command “Enable-JetDRForCluster.” This has to be executed per cluster - one at a time (shown below).

image-20240208-212438.png

  1. After completing the steps above, refresh the vCenter instance for changes to the JetStream DR plugin to take effect.

  2. Remaining configuration can be done directly from within the JetStream DR UI.
    (vCenter → Datacenter → Configure → JetStream DR)

  • No labels