Installing the JetPatch OVA

If you haven't already, download the JetPatch OVA file and Virtual Appliance Console Credentials.

• The download file contains the JetPatch Agent Manager for Azure Site Recovery, pre-installed on a CentOS 7.7 server. The OVA is about 2.4GB.
• If you are using the vSphere desktop client, use File->Deploy OVF Template (as detailed below). Or, if you are using VMware vSphere web client, follow these instructions.

1. Import the virtual appliance:
   • In your vSphere client, from the File menu, select Deploy OVF Template:

     

   • Type or browse to the location of the provided OVA, and click Next:

     

   • Continue through the wizard with the appropriate settings for your environment.  The virtual appliance automatically allocates a 16GB disk for itself, but if you select Thin Provisioned further on in the wizard, the virtual appliance initially only takes up less than 4B.
   • By default, the created VM will get a dynamic IP address via DHCP, that can be modified if required.
2. For virtual machine specs, see article.
3. It’s recommended to log into the VM with SSH and change the default root password, which is jetpatch123456. Log in as root, and you will be asked to re-enter and then change the password immediately.
4. Note: if you are using a local RHEL repo, please bypass the subscription check.

Hostname Configuration

1. Configure a server hostname

• set HOSTNAME to the new hostname using the following command

  • hostnamectl set-hostname intigua.example.com

Make sure the hostname is accessible by local applications:

• Run:

  hostname -f

  If the correct hostname is returned, it is available to applications and you're done with this. Otherwise:

• Check if nss-myhostname is installed. If not, run:

  yum install nss-myhostname

  and wait for the installation to complete.

• Open the following file for editing:

  /etc/nsswitch.conf

• Find the line beginning with hosts, and add the new hostname to the end of the line. For example, change
  

  hosts: files mdns4_minimal dns

• to
  

  hosts: files mdns4_minimal dns intigua.example.com

• Again run hostname -f to confirm that the hostname is successfully resolved.

Login to the JetPatch Console via chrome or firefox browser using https://< IP>/

Note: if there is an issue, please review proxy settings.

Next step: Environment Discovery and Connector Deployment