Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The cloud admin account of AVS holds minimal administrative privileges, which might impede the manual installation of JetDr 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 IOF IOFilters, etc). To overcome this challenge, we have implemented specific a set of AVS Run commands are provided to automate and facilitate a seamless JetDr installation and configuration process.

This article elucidates the process of installing JetDr within an AVS environment.

...

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 the deployment of JetDR is neededJetStream DR software is intended to be deployed.

Step 3: Look for Locate the Run command in the left panel and then click on it.

...

Step 4: Under the packages Packages select JSDR.Configuration.

...

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

...

Info

...

Alternatively, JetStream DR can

...

be configured using DHCP

...

. To do this, use the Run command

...

Install-

...

JetDRWithDHCP instead.

Step 6: From the Run Command form fill the details accordingly.

...

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

...

Info

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.

Note

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

...

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

...

    ...

    • Additional details

    ...

    • about a Run command execution can viewed by

    ...

    • selecting its Execution name.

      image-20240208-211312.pngImage Added

      image-20240208-211349.pngImage Added

    • The current status of Run command execution

    ...

    • can

    ...

    • be viewed in realtime from the Information panel.

      image-20240208-211417.pngImage Added

    Note

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

    ...

    Step 8: After successful completion of above steps

    1. After completing the steps above, refresh the vCenter instance for changes to the

    ...

    1. JetStream DR plugin to

    ...

    1. take effect.

    ...

    1. Remaining configuration can be done directly from within the

    ...

    1. JetStream DR UI.
      (vCenter → Datacenter → Configure → JetStream DR)

    ...

    If any issues observed please reach out JetStream support
    /wiki/spaces/KBDR/pages/2784657420

    ...