{"id":2439,"date":"2023-03-02T13:11:20","date_gmt":"2023-03-02T21:11:20","guid":{"rendered":"https:\/\/jetstreamsoft.com\/portal\/?post_type=ht_kb&#038;p=2439"},"modified":"2025-03-05T12:51:09","modified_gmt":"2025-03-05T20:51:09","slug":"jetstream-dr-preparation-checklist-on-prem-vsphere","status":"publish","type":"ht_kb","link":"https:\/\/jetstreamsoft.com\/portal\/jetstream-knowledge-base\/jetstream-dr-preparation-checklist-on-prem-vsphere\/","title":{"rendered":"Preparation Checklist: On-Premises vSphere"},"content":{"rendered":"\n<p class=\"\">Use this document to record the required inputs and verify prerequisite conditions for successfully installing JetStream DR in an <em>on-premises vSphere to on-premises vSphere<\/em> configuration. Refer to JetStream DR product documentation for additional information and explanation of the installation steps and operation of JetStream DR.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">Prerequisites: On-Premises<\/h1>\n\n\n\n<h2 class=\"wp-block-heading\">Azure Marketplace<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\">Identify the Azure subscription, Regions, resource groups and credentials for installation and configuration of Azure resources including Azure Storage Account, AVS Private Clouds, Azure VNETs, etc.<\/li>\n\n\n\n<li class=\"\">JetStream DR for AVS Subscription ID: _______________________________________________<br>(<em>Required for Azure Storage Account access<\/em>)<\/li>\n\n\n\n<li class=\"\">The JetStream MMS server (<a href=\"https:\/\/jsdr-mms.azurewebsites.net\" target=\"_blank\" rel=\"noreferrer noopener\">https:\/\/jsdr-mms.azurewebsites.net<\/a>) must be accessible from the JetStream DR MSA at both the protected and recovery sites to validate the JetStream DR for AVS Subscription ID before connecting to an Azure storage account.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">Object Storage<\/h1>\n\n\n\n<p class=\"\">The object storage maintains the continuously updated objects for each Protected Domain including domain info, the VMs and their data. The Storage Site may be located with the Recovery Site, or it may be in a different location.\u000b<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Amazon S3<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\">Amazon S3 endpoint must be accessible from JetStream DR MSA, DRVA\u2019s and RocVA\u2019s at both the protected and recovery sites.\n<ul class=\"wp-block-list\">\n<li class=\"\">Storage site name (friendly name): _______________________________________________<\/li>\n\n\n\n<li class=\"\">Amazon access key ID: _______________________________________________<\/li>\n\n\n\n<li class=\"\">Amazon secret access key: _______________________________________________<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">MinIO S3<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\">MinIO S3 endpoint must be accessible from JetStream DR MSA, DRVA\u2019s and RocVA\u2019s at both the protected and recovery sites.<\/li>\n\n\n\n<li class=\"\">MinIO S3 endpoint FQDN must be resolvable by the JetStream MSA, DRVA\u2019s and RocVA\u2019s at both the protected and recovery sites.\n<ul class=\"wp-block-list\">\n<li class=\"\">Storage site name (friendly name): _______________________________________________<\/li>\n\n\n\n<li class=\"\">MinIO S3 server: _______________________________________________<\/li>\n\n\n\n<li class=\"\">MinIO port: _______________________________________________<\/li>\n\n\n\n<li class=\"\">Access key: _______________________________________________<\/li>\n\n\n\n<li class=\"\">Secret key: _______________________________________________<\/li>\n\n\n\n<li class=\"\">Use SSL<\/li>\n\n\n\n<li class=\"\">Verify SSL<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Cloudian S3<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\">Cloudian S3 endpoint must be accessible from JetStream DR MSA, DRVA\u2019s and RocVA\u2019s at both the protected and recovery sites.<\/li>\n\n\n\n<li class=\"\">Cloudian S3 endpoint FQDN must be resolvable by the JetStream MSA, DRVA\u2019s and RocVA\u2019s at both the protected and recovery sites.<\/li>\n\n\n\n<li class=\"\">Storage site name (friendly name): _______________________________________________<\/li>\n\n\n\n<li class=\"\">Cloudian S3 endpoint (FQDN):  _______________________________________________<\/li>\n\n\n\n<li class=\"\">Cloudian S3 endpoint IP address: _____._____._____._____<\/li>\n\n\n\n<li class=\"\">Cloudian port: _______________________________________________<\/li>\n\n\n\n<li class=\"\">Access key: _______________________________________________<\/li>\n\n\n\n<li class=\"\">Secret key: _______________________________________________<\/li>\n\n\n\n<li class=\"\">Use SSL<\/li>\n\n\n\n<li class=\"\">Verify SSL<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Azure Blob Storage<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\">Storage account must be accessible from JetStream DR MSA and DRVA\u2019s at both the protected and recovery sites.<\/li>\n\n\n\n<li class=\"\">The Jetstream MMS server (<a href=\"https:\/\/jsdr-mms.azurewebsites.net\" target=\"_blank\" rel=\"noreferrer noopener\">https:\/\/jsdr-mms.azurewebsites.net<\/a>) must be accessible from the JetStream DR MSA at both the protected and recovery sites to validate the JetStream DR subscription ID before connecting to an Azure storage account.<\/li>\n\n\n\n<li class=\"\">Storage account FQDN must be resolvable by the JetStream MSA and DRVA\u2019s at both the protected and recovery sites.<\/li>\n\n\n\n<li class=\"\">Storage account must not have \u201chierarchical namespace\u201d enabled.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\">Azure storage account name (FQDN): <strong><em><strong><em>___________________________________<\/em><\/strong><\/em><\/strong><\/li>\n\n\n\n<li class=\"\">IP address: _____._____._____._____<\/li>\n\n\n\n<li class=\"\">Access type: [ ] Key Access [ ] Microsoft Entra ID based access (<em>Tech Preview feature<\/em>)<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\">Access key: <strong><em><strong><em>___________________________________<\/em><\/strong><\/em><\/strong><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Microsoft Entra ID (<em>Tech Preview Feature<\/em>)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\">Microsoft Entra ID based access requires additional configuration and the following credentials:<br>(<em>The application ID and application secret key value should be unique for each site accessing the Azure storage account.<\/em>)\n<ul class=\"wp-block-list\">\n<li class=\"\">Microsoft Entra ID tenant ID: _______________________________________________<\/li>\n\n\n\n<li class=\"\">Protected site application ID: _______________________________________________<\/li>\n\n\n\n<li class=\"\">Protected site application secret key: _______________________________________________<\/li>\n\n\n\n<li class=\"\">Recovery site application ID: _______________________________________________<\/li>\n\n\n\n<li class=\"\">Recovery site application secret key: _______________________________________________<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">Protected Site<\/h1>\n\n\n\n<p class=\"\">The installer requires the target environment to be available before proceeding: vCenter, ESXi host cluster(s), datastores, network segments, IP address ranges, DHCP services, DNS services, etc.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">vCenter Server<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\">Using a supported version?  [  ] Yes  \/  [  ] No\n<ul class=\"wp-block-list\">\n<li class=\"\">7.0 (U3c or later required, U3f or later preferred) Installed version: _____________________________<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li class=\"\">vCenter server FQDN: _______________________________________________<\/li>\n\n\n\n<li class=\"\">IP address: _____._____._____._____<\/li>\n\n\n\n<li class=\"\">\u201cAdmin\u201d user credentials: ___________________________, password known? ______________________________<\/li>\n\n\n\n<li class=\"\">Datacenter name: _______________________________________________<\/li>\n\n\n\n<li class=\"\">Cluster name: _______________________________________________<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">ESXi Hosts<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\">Using a supported version?  [  ] Yes  \/  [  ] No\n<ul class=\"wp-block-list\">\n<li class=\"\">7.0 Update 3c or later (build number# 19193900 or later) Installed version: _____________________<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li class=\"\">CIM service started and running on ESXi hosts.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Network Security<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\">Firewall(s) configured to allow communication between the JetStream DR virtual appliances, protected site vCenter, ESXi hosts, object storage, JetStream Metering server, and Azure Marketplace.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">JetStream Virtual Appliances<\/h2>\n\n\n\n<p class=\"is-style-alert wp-block-ht-blocks-messages wp-block-hb-message wp-block-hb-message--withicon\">MSA and DRVA FQDNs should be registered in DNS and resolvable.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\">Identify the \u201cmanagement\u201d network for virtual appliances \u2013 needs to communicate with on-premises vCenter, ESXi hosts, and object storage.<\/li>\n\n\n\n<li class=\"\">Identify Datastores for virtual appliances and replication logs (VMFS).<\/li>\n\n\n\n<li class=\"\">iSCSI LUN(s) for replication logs (iSCSI) (optional).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Management Server Appliance (MSA)<\/h3>\n\n\n\n<p class=\"is-style-info wp-block-ht-blocks-messages wp-block-hb-message wp-block-hb-message--withicon\"><em>1 per vCenter server\/site<\/em><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\">VM name (FQDN): _______________________________________________<\/li>\n\n\n\n<li class=\"\">MSA root username:<strong> _______________________________________________<\/strong><\/li>\n\n\n\n<li class=\"\">Password: _______________________________________________<\/li>\n\n\n\n<li class=\"\">Datastore for virtual appliance disk: _______________________________________________<br>(<em>60 GB operating system virtual disk<\/em>)<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">Management Network<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\">Network name: _______________________________________________<\/li>\n\n\n\n<li class=\"\">IP address: _____._____._____._____  or  [  ] DHCP<\/li>\n\n\n\n<li class=\"\">Net mask: _____._____._____._____<\/li>\n\n\n\n<li class=\"\">Gateway IP: _____._____._____._____<\/li>\n\n\n\n<li class=\"\">DNS server(s): _______________________________________________<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">DR Virtual Appliance (DRVA)<\/h3>\n\n\n\n<p class=\"is-style-info wp-block-ht-blocks-messages wp-block-hb-message wp-block-hb-message--withicon\"><em>Minimum: 1 &#8211; Repeat this section for each additional DRVA as needed.<\/em><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\">VM name: <strong><em>jss-drva-<\/em><\/strong>_______________________________________________<\/li>\n\n\n\n<li class=\"\">Datacenter: _______________________________________________<\/li>\n\n\n\n<li class=\"\">Cluster: _______________________________________________<\/li>\n\n\n\n<li class=\"\">Datastore for virtual appliance disk:<strong><em> _______________________________________________<\/em><\/strong><br>(<em>32 GB operating system virtual disk<\/em>)<\/li>\n\n\n\n<li class=\"\">Number of CPUs: _______________________________________________<br>(<em>Minimum: 4 \u2013 Size according to CPT recommendation<\/em>)<\/li>\n\n\n\n<li class=\"\">Memory (GB): _______________________________________________<br>(<em>Minimum: 8 \u2013 Size according to CPT recommendation<\/em>)<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">Networks<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\">Management Network\n<ul class=\"wp-block-list\">\n<li class=\"\">Network name: _______________________________________________<\/li>\n\n\n\n<li class=\"\">IP address: _____._____._____._____  or  [  ] DHCP<\/li>\n\n\n\n<li class=\"\">Net mask: _____._____._____._____<\/li>\n\n\n\n<li class=\"\">Gateway IP: _____._____._____._____<\/li>\n\n\n\n<li class=\"\">DNS server(s): _______________________________________________<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li class=\"\">DRVA Data Network (DRVA to ESXi hosts)<br>(<em>Optional \u2013 if different from Management Network<\/em>)\n<ul class=\"wp-block-list\">\n<li class=\"\">Network name: _______________________________________________<\/li>\n\n\n\n<li class=\"\">IP address: _____._____._____._____   or  [  ] DHCP<\/li>\n\n\n\n<li class=\"\">Net mask: _____._____._____._____<\/li>\n\n\n\n<li class=\"\">Gateway IP: _____._____._____._____<\/li>\n\n\n\n<li class=\"\">DNS server(s): _______________________________________________<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li class=\"\">Replication Network to Object Store (DRVA to object storage)<br>(<em>Optional \u2013 if different from Management Network<\/em>)\n<ul class=\"wp-block-list\">\n<li class=\"\">Network name: _______________________________________________<\/li>\n\n\n\n<li class=\"\">IP address: _____._____._____._____   or  [  ] DHCP<\/li>\n\n\n\n<li class=\"\">Net mask: _____._____._____._____<\/li>\n\n\n\n<li class=\"\">Gateway IP: _____._____._____._____<\/li>\n\n\n\n<li class=\"\">DNS server(s): _______________________________________________<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li class=\"\">Replication Log Network #1 (DRVA to iSCSI DR Store)<strong><br><\/strong>(<em>Optional \u2013 only required for iSCSI backed Replication Log Volumes<\/em>)\n<ul class=\"wp-block-list\">\n<li class=\"\">Network name: _______________________________________________<\/li>\n\n\n\n<li class=\"\">IP address: _____._____._____._____   or  [  ] DHCP<\/li>\n\n\n\n<li class=\"\">Net mask: _____._____._____._____<\/li>\n\n\n\n<li class=\"\">Gateway IP: _____._____._____._____<\/li>\n\n\n\n<li class=\"\">DNS server(s): _______________________________________________<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li class=\"\">Replication Log Network #2 (DRVA to iSCSI DR Store)<br>(<em>Optional \u2013 only required for multi-path iSCSI backed Replication Log Volumes<\/em>)\n<ul class=\"wp-block-list\">\n<li class=\"\">Network name: _______________________________________________<\/li>\n\n\n\n<li class=\"\">IP address: _____._____._____._____   or  [  ] DHCP<\/li>\n\n\n\n<li class=\"\">Net mask: _____._____._____._____<\/li>\n\n\n\n<li class=\"\">Gateway IP: _____._____._____._____<\/li>\n\n\n\n<li class=\"\">DNS server(s): _______________________________________________<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">VMDK Replication Log Volume<\/h3>\n\n\n\n<p class=\"is-style-info wp-block-ht-blocks-messages wp-block-hb-message wp-block-hb-message--withicon\"><em>Minimum: 1 &#8211; R<em>epeat for additional replication log volumes as needed.<\/em><\/em><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\">Datacenter: _______________________________________________<\/li>\n\n\n\n<li class=\"\">Datastore:  _______________________________________________<\/li>\n\n\n\n<li class=\"\">Log disk size (GB): _______________________________________________\n<ul class=\"wp-block-list\">\n<li class=\"\">128 GB recommended as a starting point for a single protected domain.<\/li>\n\n\n\n<li class=\"\">64 GB additional for each additional protected domain.<\/li>\n\n\n\n<li class=\"\"><em>Use the CPT resource recommendations for sizing specific to your protected workloads.<\/em><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">iSCSI Replication Log Volume<\/h3>\n\n\n\n<p class=\"\">All hosts in the cluster and the DRVA VMs must have access to the configured iSCSI target LUN. Also, the iSCSI storage adapter must be defined on all hosts of the cluster and rescanned so that the iSCSI LUN appears in the list under the Devices tab.<\/p>\n\n\n\n<p class=\"is-style-info wp-block-ht-blocks-messages wp-block-hb-message wp-block-hb-message--withicon\"><em>Minimum: 1 &#8211; R<em>epeat for additional replication log volumes as needed.<\/em><\/em><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\">iSCSI target address 1: _______________________________________________<\/li>\n\n\n\n<li class=\"\">iSCSI target port 1: _______________________________________________<\/li>\n\n\n\n<li class=\"\">iSCSI target address 2 (for Multipathing Only): _______________________________________________<\/li>\n\n\n\n<li class=\"\">iSCSI target port 2 (for Multipathing Only): _______________________________________________<\/li>\n\n\n\n<li class=\"\">LUN IQN: _______________________________________________<\/li>\n\n\n\n<li class=\"\">Force format already configured LUN<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Recover from Object Cloud Virtual Appliance (RocVA)<\/h3>\n\n\n\n<p class=\"\">RocVA is automatically deployed on the protected side during restore, recover or failback operations.<br>If using static IP addresses repeat this section for each additional protected domain (RocVA) as needed.<\/p>\n\n\n\n<p class=\"is-style-info wp-block-ht-blocks-messages wp-block-hb-message wp-block-hb-message--withicon\"><em>1 per protected domain.<\/em><\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Networks<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\">Management Network\n<ul class=\"wp-block-list\">\n<li class=\"\">Network name: _______________________________________________<\/li>\n\n\n\n<li class=\"\">IP address: _____._____._____._____   or  [  ] DHCP<\/li>\n\n\n\n<li class=\"\">Net mask: _____._____._____._____<\/li>\n\n\n\n<li class=\"\">Gateway IP: _____._____._____._____<\/li>\n\n\n\n<li class=\"\">DNS server(s): _______________________________________________<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li class=\"\">Host (IO Filter) to DRVA Data Network<br>(<em><em>Optional \u2013 If different from Management Network<\/em><\/em>)\n<ul class=\"wp-block-list\">\n<li class=\"\">Network name: _______________________________________________<\/li>\n\n\n\n<li class=\"\">IP address: _____._____._____._____   or  [  ] DHCP<\/li>\n\n\n\n<li class=\"\">Net mask: _____._____._____._____<\/li>\n\n\n\n<li class=\"\">Gateway IP: _____._____._____._____<\/li>\n\n\n\n<li class=\"\">DNS server(s): _______________________________________________<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li class=\"\">Replication Network to Object Store<br>(<em><em>Optional \u2013 If different from Management Network<\/em><\/em>)\n<ul class=\"wp-block-list\">\n<li class=\"\">Network name: _______________________________________________<\/li>\n\n\n\n<li class=\"\">IP address: _____._____._____._____   or  [  ] DHCP<\/li>\n\n\n\n<li class=\"\">Net mask: _____._____._____._____<\/li>\n\n\n\n<li class=\"\">Gateway IP: _____._____._____._____<\/li>\n\n\n\n<li class=\"\">DNS server(s): _______________________________________________<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Representation VM (RVM)<\/h3>\n\n\n\n<p class=\"is-style-info wp-block-ht-blocks-messages wp-block-hb-message wp-block-hb-message--withicon\"><em>1 per protected domain.<\/em><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\">One RVM is automatically deployed for each VM in a protected domain on the protected side during failback or recovery\/restore operations.<\/li>\n\n\n\n<li class=\"\">\u000bRVMs require DHCP assigned IP addresses on the protected side\u2019s internal \u201cHost to DRVA Data Network\u201d for the duration of failback or recovery\/restore operations.<\/li>\n\n\n\n<li class=\"\">Plan to provide enough IP addresses via DHCP to support the total number of VMs in all protected domains, or for the maximum number that will be restored to the protected side at one time.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">JetStream Virtual Appliances \u2013 Summary<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Management Server Appliance (MSA)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\">1 per vCenter server\/site.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">DR Virtual Appliance (DRVA)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\">Minimum 1 per protected cluster, consider 1 per protected domain. \n<ul class=\"wp-block-list\">\n<li class=\"\">Current recommendation is a ratio of 100 protected VMs per DRVA.<\/li>\n\n\n\n<li class=\"\">Use the CPT resource recommendations for sizing specific to your protected workloads.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Recover from Object Cloud Virtual Appliance (RocVA)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\">1 per protected domain. <\/li>\n\n\n\n<li class=\"\">Deployed automatically during restore, recovery or failback operations.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Representation VM (RVM)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\">1 per protected VM. \n<ul class=\"wp-block-list\">\n<li class=\"\">Deployed automatically during restore, recovery or failback operations.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-ht-blocks-messages wp-block-hb-message wp-block-hb-message--withicon\">Plan to provide enough IP addresses via DHCP to support the total number of VMs in all protected domains, or for the maximum number that will be restored to the protected side at one time.<br><br>Typically in AVS, the RocVA is deployed with all interfaces on the same network segment, but up to three separate segments can be specified: <em>Management Network<\/em>, <em>Replication Network to Object Store<\/em>, and <em>Host (IO Filter) to DRVA Data Network<\/em>.<br><br>The RocVA requires an address on each unique network segment specified.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<figure class=\"wp-block-image size-large\"><img fetchpriority=\"high\" decoding=\"async\" width=\"1024\" height=\"626\" src=\"https:\/\/jetstreamsoft.com\/portal\/wp-content\/uploads\/2023\/03\/onpre_network-flow-1024x626.png\" alt=\"\" class=\"wp-image-2429\" srcset=\"https:\/\/jetstreamsoft.com\/portal\/wp-content\/uploads\/2023\/03\/onpre_network-flow-1024x626.png 1024w, https:\/\/jetstreamsoft.com\/portal\/wp-content\/uploads\/2023\/03\/onpre_network-flow-300x183.png 300w, https:\/\/jetstreamsoft.com\/portal\/wp-content\/uploads\/2023\/03\/onpre_network-flow-768x469.png 768w, https:\/\/jetstreamsoft.com\/portal\/wp-content\/uploads\/2023\/03\/onpre_network-flow-50x31.png 50w, https:\/\/jetstreamsoft.com\/portal\/wp-content\/uploads\/2023\/03\/onpre_network-flow-1536x939.png 1536w, https:\/\/jetstreamsoft.com\/portal\/wp-content\/uploads\/2023\/03\/onpre_network-flow-2048x1252.png 2048w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">Recovery Site<\/h1>\n\n\n\n<p class=\"\">The installer requires the target environment to be available before proceeding: vCenter, ESXi host cluster(s), datastores, network segments, IP address ranges, DHCP services, DNS services, etc.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">vCenter Server<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\">Using a supported version?  [  ] Yes  \/  [  ] No\n<ul class=\"wp-block-list\">\n<li class=\"\">7.0 (U3c or later required, U3f or later preferred) Installed version: _____________________________<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li class=\"\">vCenter server FQDN: _______________________________________________<\/li>\n\n\n\n<li class=\"\">IP address: _____._____._____._____<\/li>\n\n\n\n<li class=\"\">\u201cAdmin\u201d user credentials: ___________________________, password known? ______________________________<\/li>\n\n\n\n<li class=\"\">Datacenter name: _______________________________________________<\/li>\n\n\n\n<li class=\"\">Cluster name: _______________________________________________<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">ESXi Hosts<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\">Using a supported version?  [  ] Yes  \/  [  ] No\n<ul class=\"wp-block-list\">\n<li class=\"\">7.0 Update 3c or later (build number# 19193900 or later) Installed version: _____________________<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li class=\"\">CIM service started and running on ESXi hosts.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Network Security<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\">Firewall(s) configured to allow communication between the JetStream DR virtual appliances, protected site vCenter, ESXi hosts, object storage, JetStream Metering server, and Azure Marketplace.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">JetStream Virtual Appliances<\/h2>\n\n\n\n<p class=\"is-style-alert wp-block-ht-blocks-messages wp-block-hb-message wp-block-hb-message--withicon\">MSA and DRVA FQDNs should be registered in DNS and resolvable.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\">Identify the \u201cmanagement\u201d network for virtual appliances \u2013 needs to communicate with on-premises vCenter, ESXi hosts, and object storage.<\/li>\n\n\n\n<li class=\"\">Identify Datastores for virtual appliances and replication logs (VMFS).<\/li>\n\n\n\n<li class=\"\">iSCSI LUN(s) for replication logs (iSCSI) (optional).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Management Server Appliance (MSA)<\/h3>\n\n\n\n<p class=\"is-style-info wp-block-ht-blocks-messages wp-block-hb-message wp-block-hb-message--withicon\"><em>1 per vCenter server\/site<\/em><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\">VM name (FQDN): _______________________________________________<\/li>\n\n\n\n<li class=\"\">MSA root username:<strong> _______________________________________________<\/strong><\/li>\n\n\n\n<li class=\"\">Password: _______________________________________________<\/li>\n\n\n\n<li class=\"\">Datastore for virtual appliance disk: _______________________________________________<br>(<em>60 GB operating system virtual disk<\/em>)<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">Management Network<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\">Network name: _______________________________________________<\/li>\n\n\n\n<li class=\"\">IP address: _____._____._____._____  or  [  ] DHCP<\/li>\n\n\n\n<li class=\"\">Net mask: _____._____._____._____<\/li>\n\n\n\n<li class=\"\">Gateway IP: _____._____._____._____<\/li>\n\n\n\n<li class=\"\">DNS server(s): _______________________________________________<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">DR Virtual Appliance (DRVA)<\/h3>\n\n\n\n<p class=\"is-style-info wp-block-ht-blocks-messages wp-block-hb-message wp-block-hb-message--withicon\"><em>Minimum: 1 &#8211; Repeat this section for each additional DRVA as needed.<\/em><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\">VM name: <strong><em>jss-drva-<\/em><\/strong>_______________________________________________<\/li>\n\n\n\n<li class=\"\">Datacenter: _______________________________________________<\/li>\n\n\n\n<li class=\"\">Cluster: _______________________________________________<\/li>\n\n\n\n<li class=\"\">Datastore for virtual appliance disk:<strong><em> _______________________________________________<\/em><\/strong><br>(<em>32 GB operating system virtual disk<\/em>)<\/li>\n\n\n\n<li class=\"\">Number of CPUs: _______________________________________________<br>(<em>Minimum: 4 \u2013 Size according to CPT recommendation<\/em>)<\/li>\n\n\n\n<li class=\"\">Memory (GB): _______________________________________________<br>(<em>Minimum: 8 \u2013 Size according to CPT recommendation<\/em>)<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">Networks<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\">Management Network\n<ul class=\"wp-block-list\">\n<li class=\"\">Network name: _______________________________________________<\/li>\n\n\n\n<li class=\"\">IP address: _____._____._____._____  or  [  ] DHCP<\/li>\n\n\n\n<li class=\"\">Net mask: _____._____._____._____<\/li>\n\n\n\n<li class=\"\">Gateway IP: _____._____._____._____<\/li>\n\n\n\n<li class=\"\">DNS server(s): _______________________________________________<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li class=\"\">DRVA Data Network (DRVA to ESXi hosts)<br>(<em>Optional \u2013 if different from Management Network<\/em>)\n<ul class=\"wp-block-list\">\n<li class=\"\">Network name: _______________________________________________<\/li>\n\n\n\n<li class=\"\">IP address: _____._____._____._____   or  [  ] DHCP<\/li>\n\n\n\n<li class=\"\">Net mask: _____._____._____._____<\/li>\n\n\n\n<li class=\"\">Gateway IP: _____._____._____._____<\/li>\n\n\n\n<li class=\"\">DNS server(s): _______________________________________________<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li class=\"\">Replication Network to Object Store (DRVA to object storage)<br>(<em>Optional \u2013 if different from Management Network<\/em>)\n<ul class=\"wp-block-list\">\n<li class=\"\">Network name: _______________________________________________<\/li>\n\n\n\n<li class=\"\">IP address: _____._____._____._____   or  [  ] DHCP<\/li>\n\n\n\n<li class=\"\">Net mask: _____._____._____._____<\/li>\n\n\n\n<li class=\"\">Gateway IP: _____._____._____._____<\/li>\n\n\n\n<li class=\"\">DNS server(s): _______________________________________________<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li class=\"\">Replication Log Network #1 (DRVA to iSCSI DR Store)<strong><br><\/strong>(<em>Optional \u2013 only required for iSCSI backed Replication Log Volumes<\/em>)\n<ul class=\"wp-block-list\">\n<li class=\"\">Network name: _______________________________________________<\/li>\n\n\n\n<li class=\"\">IP address: _____._____._____._____   or  [  ] DHCP<\/li>\n\n\n\n<li class=\"\">Net mask: _____._____._____._____<\/li>\n\n\n\n<li class=\"\">Gateway IP: _____._____._____._____<\/li>\n\n\n\n<li class=\"\">DNS server(s): _______________________________________________<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li class=\"\">Replication Log Network #2 (DRVA to iSCSI DR Store)<br>(<em>Optional \u2013 only required for multi-path iSCSI backed Replication Log Volumes<\/em>)\n<ul class=\"wp-block-list\">\n<li class=\"\">Network name: _______________________________________________<\/li>\n\n\n\n<li class=\"\">IP address: _____._____._____._____   or  [  ] DHCP<\/li>\n\n\n\n<li class=\"\">Net mask: _____._____._____._____<\/li>\n\n\n\n<li class=\"\">Gateway IP: _____._____._____._____<\/li>\n\n\n\n<li class=\"\">DNS server(s): _______________________________________________<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">VMDK Replication Log Volume<\/h3>\n\n\n\n<p class=\"is-style-info wp-block-ht-blocks-messages wp-block-hb-message wp-block-hb-message--withicon\"><em>Minimum: 1 &#8211; R<em>epeat for additional replication log volumes as needed.<\/em><\/em><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\">Datacenter: <strong><em>SDDC-Datacenter<\/em><\/strong><\/li>\n\n\n\n<li class=\"\">Datastore:  <strong><em>vsanDatastore<\/em><\/strong><\/li>\n\n\n\n<li class=\"\">Log disk size (GB): _______________________________________________\n<ul class=\"wp-block-list\">\n<li class=\"\">128 GB recommended as a starting point for a single protected domain.<\/li>\n\n\n\n<li class=\"\">64 GB additional for each additional protected domain.<\/li>\n\n\n\n<li class=\"\"><em>Use the CPT resource recommendations for sizing specific to your protected workloads.<\/em><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">iSCSI Replication Log Volume<\/h3>\n\n\n\n<p class=\"\">All hosts in the cluster and the DRVA VMs must have access to the configured iSCSI target LUN. Also, the iSCSI storage adapter must be defined on all hosts of the cluster and rescanned so that the iSCSI LUN appears in the list under the Devices tab.<\/p>\n\n\n\n<p class=\"is-style-info wp-block-ht-blocks-messages wp-block-hb-message wp-block-hb-message--withicon\"><em>Minimum: 1 &#8211; R<em>epeat for additional replication log volumes as needed.<\/em><\/em><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\">iSCSI target address 1: _______________________________________________<\/li>\n\n\n\n<li class=\"\">iSCSI target port 1: _______________________________________________<\/li>\n\n\n\n<li class=\"\">iSCSI target address 2 (for Multipathing Only): _______________________________________________<\/li>\n\n\n\n<li class=\"\">iSCSI target port 2 (for Multipathing Only): _______________________________________________<\/li>\n\n\n\n<li class=\"\">LUN IQN: _______________________________________________<\/li>\n\n\n\n<li class=\"\">Force format already configured LUN<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Recover from Object Cloud Virtual Appliance (RocVA)<\/h3>\n\n\n\n<p class=\"\">RocVA is automatically deployed on the recovery side during restore, recover, failover or continuous failover operations. \u000bIf using static IP addresses repeat this section for each additional protected domain (RocVA) as needed.<\/p>\n\n\n\n<p class=\"is-style-info wp-block-ht-blocks-messages wp-block-hb-message wp-block-hb-message--withicon\"><em>1 per protected domain.<\/em><\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Networks<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\">Management Network\n<ul class=\"wp-block-list\">\n<li class=\"\">Network name: _______________________________________________<\/li>\n\n\n\n<li class=\"\">IP address: _____._____._____._____   or  [  ] DHCP<\/li>\n\n\n\n<li class=\"\">Net mask: _____._____._____._____<\/li>\n\n\n\n<li class=\"\">Gateway IP: _____._____._____._____<\/li>\n\n\n\n<li class=\"\">DNS server(s): _______________________________________________<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li class=\"\">Host (IO Filter) to DRVA Data Network<br>(<em><em>Optional \u2013 If different from Management Network<\/em><\/em>)\n<ul class=\"wp-block-list\">\n<li class=\"\">Network name: _______________________________________________<\/li>\n\n\n\n<li class=\"\">IP address: _____._____._____._____   or  [  ] DHCP<\/li>\n\n\n\n<li class=\"\">Net mask: _____._____._____._____<\/li>\n\n\n\n<li class=\"\">Gateway IP: _____._____._____._____<\/li>\n\n\n\n<li class=\"\">DNS server(s): _______________________________________________<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li class=\"\">Replication Network to Object Store<br>(<em><em>Optional \u2013 If different from Management Network<\/em><\/em>)\n<ul class=\"wp-block-list\">\n<li class=\"\">Network name: _______________________________________________<\/li>\n\n\n\n<li class=\"\">IP address: _____._____._____._____   or  [  ] DHCP<\/li>\n\n\n\n<li class=\"\">Net mask: _____._____._____._____<\/li>\n\n\n\n<li class=\"\">Gateway IP: _____._____._____._____<\/li>\n\n\n\n<li class=\"\">DNS server(s): _______________________________________________<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Representation VM (RVM)<\/h3>\n\n\n\n<p class=\"is-style-info wp-block-ht-blocks-messages wp-block-hb-message wp-block-hb-message--withicon\"><em>1 per protected domain.<\/em><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\">One RVM is automatically deployed for each VM in a protected domain on the recovery side during failover, continuous failover or recovery\/restore operations.<\/li>\n\n\n\n<li class=\"\">\u000bRVMs require DHCP assigned IP addresses on the protected side\u2019s internal \u201cHost to DRVA Data Network\u201d for the duration of failback continuous failover, or recovery\/restore operations.<\/li>\n\n\n\n<li class=\"\">Plan to provide enough IP addresses via DHCP to support the total number of VMs in all protected domains, or for the maximum number that will be restored to the recovery side at one time.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">JetStream Virtual Appliances \u2013 Summary<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Management Server Appliance (MSA)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\">1 per vCenter server\/site.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">DR Virtual Appliance (DRVA)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\">Minimum 1 per protected cluster, consider 1 per protected domain. \n<ul class=\"wp-block-list\">\n<li class=\"\">Current recommendation is a ratio of 100 protected VMs per DRVA.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Recover from Object Cloud Virtual Appliance (RocVA)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\">1 per protected domain. <\/li>\n\n\n\n<li class=\"\">Deployed automatically during restore, recovery or failover operations.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Representation VM (RVM)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\">1 per protected VM. \n<ul class=\"wp-block-list\">\n<li class=\"\">Deployed automatically during restore, recovery or failover operations.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<p class=\"is-style-success wp-block-ht-blocks-messages wp-block-hb-message wp-block-hb-message--withicon\">Plan to provide enough IP addresses via DHCP to support the total number of VMs in all protected domains, or for the maximum number that will be restored to the protected side at one time.<br><br>Typically in AVS, the RocVA is deployed with all interfaces on the same network segment, but up to three separate segments can be specified: <em>Management Network<\/em>, <em>Replication Network to Object Store<\/em>, and <em>Host (IO Filter) to DRVA Data Network<\/em>.<br><br>The RocVA requires an address on each unique network segment specified.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">Network Communication Ports<\/h1>\n\n\n\n<p class=\"is-style-info wp-block-ht-blocks-messages wp-block-hb-message wp-block-hb-message--withicon\">The source ports for the traffic flows from our appliances are ephemeral. All listed ports are destination ports.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">AVS Local Traffic (within the same site)<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\">JetStream MSA to vCenter: TCP 443<\/li>\n\n\n\n<li class=\"\">JetStream MSA to vCenter: TCP 80<\/li>\n\n\n\n<li class=\"\">vCenter to JetStream MSA: TCP 443<\/li>\n\n\n\n<li class=\"\">JetStream MSA to ESXi hosts (CIM Server): TCP 5989<\/li>\n\n\n\n<li class=\"\">JetStream IO Filter (ESXi hosts) to DRVA (DATA): TCP 32877<\/li>\n\n\n\n<li class=\"\">JetStream MSA to JetStream DRVA (REST): TCP 32878<\/li>\n\n\n\n<li class=\"\">JetStream MSA to JetStream RocVA (REST): TCP 32878<\/li>\n\n\n\n<li class=\"\">JetStream RocVA to JetStream DRVA (DATA): TCP 32877<\/li>\n\n\n\n<li class=\"\">JetStream RocVA to JetStream ReVM (iSCSI): TCP 3260<\/li>\n\n\n\n<li class=\"\">JetStream DRVA to iSCSI Replication Log Volume (iSCSI): TCP 3260<\/li>\n\n\n\n<li class=\"\">ESXi Hosts to iSCSI Replication Log Volume (iSCSI): TCP 3260<\/li>\n\n\n\n<li class=\"\">JetStream MSA, DRVA and DNS: TCP\/UDP 53<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Other Traffic (may not be local to a site)<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\">JetStream MSA to Azure Storage Account: TCP 443<\/li>\n\n\n\n<li class=\"\">JetStream DRVA to Azure Storage Account: TCP 443<\/li>\n\n\n\n<li class=\"\">JetStream RocVA to Azure Storage Account: TCP 443<\/li>\n\n\n\n<li class=\"\">JetStream MSA to JetStream Azure metering website\u000b (jsdr-mms.azurewebsites.net): TCP 443<\/li>\n\n\n\n<li class=\"\">JetStream MSA to Amazon S3: TCP 443<\/li>\n\n\n\n<li class=\"\">JetStream DRVA to Amazon S3: TCP 443<\/li>\n\n\n\n<li class=\"\">JetStream RocVA to Amazon S3: TCP 443<\/li>\n\n\n\n<li class=\"\">JetStream MSA to MinIO S3: TCP 9000<\/li>\n\n\n\n<li class=\"\">JetStream DRVA to MinIO S3: TCP 9000<\/li>\n\n\n\n<li class=\"\">JetStream RocVA to MinIO S3: TCP 9000<\/li>\n\n\n\n<li class=\"\">JetStream MSA to Cloudian S3: TCP 443<\/li>\n\n\n\n<li class=\"\">JetStream DRVA to Cloudian S3: TCP 443<\/li>\n\n\n\n<li class=\"\">JetStream RocVA to Cloudian S3: TCP 443<\/li>\n\n\n\n<li class=\"\">JetStream MSA to Microsoft Entra ID (login.microsoftonline.com) (OAuth 2.0): TCP 443 (for Storage Account Microsoft Entra ID Authentication)<\/li>\n\n\n\n<li class=\"\">JetStream DRVA to Microsoft Entra ID (login.microsoftonline.com) (OAuth 2.0): TCP 443 (for Storage Account Microsoft Entra ID Authentication)<\/li>\n\n\n\n<li class=\"\">JetStream RocVA to Microsoft Entra ID (login.microsoftonline.com) (OAuth 2.0): TCP 443 (for Storage Account Microsoft Entra ID Authentication)<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Troubleshooting (Only needed upon request for support)<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\">JetStream MSA, DRVA and RocVA (SSH): TCP 22<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Use this document to record the required inputs and verify prerequisite conditions for successfully installing JetStream DR in an on-premises vSphere to on-premises vSphere configuration. Refer to JetStream DR product documentation for additional information and explanation of the installation steps and operation of JetStream DR. Prerequisites: On-Premises Azure Marketplace Object Storage The object storage maintains [&hellip;]<\/p>\n","protected":false},"author":1,"comment_status":"open","ping_status":"closed","template":"","format":"standard","meta":{"nf_dc_page":"","footnotes":""},"ht-kb-category":[245],"ht-kb-tag":[246],"class_list":["post-2439","ht_kb","type-ht_kb","status-publish","format-standard","hentry","ht_kb_category-how-to","ht_kb_tag-getting-started"],"_links":{"self":[{"href":"https:\/\/jetstreamsoft.com\/portal\/wp-json\/wp\/v2\/ht-kb\/2439","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/jetstreamsoft.com\/portal\/wp-json\/wp\/v2\/ht-kb"}],"about":[{"href":"https:\/\/jetstreamsoft.com\/portal\/wp-json\/wp\/v2\/types\/ht_kb"}],"author":[{"embeddable":true,"href":"https:\/\/jetstreamsoft.com\/portal\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/jetstreamsoft.com\/portal\/wp-json\/wp\/v2\/comments?post=2439"}],"version-history":[{"count":3,"href":"https:\/\/jetstreamsoft.com\/portal\/wp-json\/wp\/v2\/ht-kb\/2439\/revisions"}],"predecessor-version":[{"id":6745,"href":"https:\/\/jetstreamsoft.com\/portal\/wp-json\/wp\/v2\/ht-kb\/2439\/revisions\/6745"}],"wp:attachment":[{"href":"https:\/\/jetstreamsoft.com\/portal\/wp-json\/wp\/v2\/media?parent=2439"}],"wp:term":[{"taxonomy":"ht_kb_category","embeddable":true,"href":"https:\/\/jetstreamsoft.com\/portal\/wp-json\/wp\/v2\/ht-kb-category?post=2439"},{"taxonomy":"ht_kb_tag","embeddable":true,"href":"https:\/\/jetstreamsoft.com\/portal\/wp-json\/wp\/v2\/ht-kb-tag?post=2439"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}