Merge pull request #48 from NetAppDocs/um-914-ga

Unified Manager 9.14 GA release

data-protection/concept_types_of_snapmirror_protection.adoc

@@ -1,7 +1,7 @@
 ---
 permalink: data-protection/concept_types_of_snapmirror_protection.html
 sidebar: sidebar
-keywords: types, snapmirror, protection, consistency group, snapmirror business continuity, smbc, sm-bc
+keywords: types, snapmirror, protection, consistency group, SnapMirror active sync
 summary: "Depending on the deployment of your data storage topology, Unified Manager enables you to configure multiple types of SnapMirror protection relationships. All variations of SnapMirror protection offer failover disaster recovery protection, but offer differing capabilities in performance, version flexibility, and multiple backup copy protection."
 ---
 = Types of SnapMirror protection
@@ -55,14 +55,14 @@ SnapMirror Synchronous protection with "`regular`" synchronization does not requ
 The Restore button and the Relationship operation buttons are not available when monitoring synchronous protection relationships from the Health: All Volumes view or the Volume / Health details page.
 ====
 
-== SnapMirror Synchronous Business Continuity
+== SnapMirror active sync
 
-The SnapMirror Business Continuity (SM-BC) feature is available with ONTAP 9.8 and later, and you can use it to protect applications with LUNs, enabling applications to fail over transparently, ensuring business continuity in case of a disaster.
+The SnapMirror active sync feature is available with ONTAP 9.8 and later, and you can use it to protect applications with LUNs, enabling applications to fail over transparently, ensuring business continuity in case of a disaster.
 
-It allows you to discover and monitor the synchronous SnapMirror relationships for Consistency Groups (CGs) available on clusters and storage virtual machines from Unified Manager. SM-BC is supported on AFF clusters or All SAN Array (ASA) clusters, where the primary and secondary clusters can be either AFF or ASA. SM-BC protects applications with iSCSI or FCP LUNs.
+It allows you to discover and monitor the synchronous SnapMirror relationships for Consistency Groups (CGs) available on clusters and storage virtual machines from Unified Manager. SnapMirror active sync is supported on AFF clusters or All SAN Array (ASA) clusters, where the primary and secondary clusters can be either AFF or ASA. SnapMirror active sync protects applications with iSCSI or FCP LUNs.
 
-When you view the volumes and LUNs protected by the SM-BC relationship, you can get a unified view for protection relationships, Consistency Groups in volume inventory, view protection topology for Consistency Group relationships, view historical data for Consistency Group relationships up to a year. You can also download the report. You can also view the summary of Consistency Group relationships, search support for Consistency Group relationships, and gain information about volumes that are protected by the Consistency Group.
+When you view the volumes and LUNs protected by the SnapMirror active sync relationship, you can get a unified view for protection relationships, Consistency Groups in volume inventory, view protection topology for Consistency Group relationships, view historical data for Consistency Group relationships up to a year. You can also download the report. You can also view the summary of Consistency Group relationships, search support for Consistency Group relationships, and gain information about volumes that are protected by the Consistency Group.
 
 On the Relationships page, you can also sort, filter, and extend protection on the source and destination storage objects and their relationship that are protected by the Consistency Group.
 
-To know more about SnapMirror Synchronous Business Continuity, refer to link:https://docs.netapp.com/us-en/ontap/smbc/index.html[ONTAP 9 Documentation for SM-BC].
+To know more about SnapMirror active sync, refer to link:https://docs.netapp.com/us-en/ontap/smbc/index.html[ONTAP 9 Documentation for Snapmirror active sync (formerly SM-BC)].

data-protection/reference_relationship_all_relationships_view.adoc

@@ -209,7 +209,7 @@ Displays the mediator status.
 
 ** Not Applicable
 +
-If the cluster does not support SnapMirror Business Continuity.
+If the cluster does not support SnapMirror active sync.
 
 ** Not Configured
 +
@@ -259,7 +259,7 @@ Displays the name of the source cluster for the SnapMirror relationship.
 +
 Displays the name of the source node name link for the SnapMirror relationship of a volume and displays the SnapMirror relationship node count link when the object is a Storage VM or Consistency Group.
 
-In the custom view, when you click the node name link, you can view and extend protection for storage objects on which the volumes of those Consistency Groups that belong to SM-BC relationship.
+In the custom view, when you click the node name link, you can view and extend protection for storage objects on which the volumes of those Consistency Groups belong to a SnapMirror active sync relationship.
 
 When you click the node count link, it takes you to the node page with respective nodes associated with that relationship. When the node count is 0, there is no value displayed as there are no nodes associated with the relationship.
 

data-protection/task_abort_an_active_data_protection_transfer.adoc

@@ -1,7 +1,7 @@
 ---
 permalink: data-protection/task_abort_an_active_data_protection_transfer.html
 sidebar: sidebar
-keywords: abort, active data protection, transfer, volume relationships page, smbc, sm-bc
+keywords: abort, active data protection, transfer, volume relationships page, SnapMirror active sync
 summary: "You can abort an active data protection transfer when you want to stop a SnapMirror replication that is in progress. You can also clear the restart checkpoint for transfers subsequent to the baseline transfer. You might abort a transfer when it conflicts with another operation, such as a volume move."
 ---
 = Aborting an active data protection transfer from the Volume Relationships page

data-protection/task_create_cascade_or_fanout_relationships_to_extend_protection.adoc

@@ -11,7 +11,7 @@ summary: "You can extend protection from an existing relationship by creating ei
 [.lead]
 You can extend protection from an existing relationship by creating either a fanout from the source volume or a cascade from the destination volume of an existing relationship. You might do this when you need to copy data from one site to many sites or to provide additional protection by creating more backups.
 
-You can extend protection to volumes using consistency group, which is a container that holds several volumes so that you can manage all of the volumes as one entity. You can view the SnapMirror Business Continuity (SM-BC) Consistency Group and the synchronous consistency group relationship in the Relationships page of Unified Manager.
+You can extend protection to volumes using consistency group, which is a container that holds several volumes so that you can manage all of the volumes as one entity. You can view the SnapMirror active sync Consistency Group and the synchronous consistency group relationship in the Relationships page of Unified Manager.
 
 
 *What you'll need*

data-protection/view-lun-relationships.adoc

@@ -1,24 +1,24 @@
 ---
 permalink: data-protection/view-lun-relationships.html
 sidebar: sidebar
-keywords: LUN, SM-BC, SnapMirror Business Continuity, Consistency Group, CG
-summary: "Unified view of LUNs protected by SM-BC."
+keywords: LUN, SnapMirror active sync, Consistency Group, CG
+summary: "Unified view of LUNs protected by SnapMirror active sync."
 ---
 = Monitoring LUNs in a Consistency Group relationship
 :icons: font
 :imagesdir: ../media/
 
 [.lead]
-If your ONTAP environment supports SnapMirror Business Continuity (SM-BC) to
+If your ONTAP environment supports SnapMirror active sync to
 protect applications with LUNs, you can view and monitor those LUNs on Active IQ Unified Manager.
 
-SM-BC ensures zero recovery time objective (RTO) during failover in SAN environments. In a typical deployment supporting SM-BC, the LUNs on volumes are protected by Consistency Group relationships.
+SnapMirror active sync ensures zero recovery time objective (RTO) during failover in SAN environments. In a typical deployment supporting SnapMirror active sync, the LUNs on volumes are protected by Consistency Group relationships.
 
 These primary and secondary LUNs are composite LUNs, or a replica LUN pair with the same UUID and serial number. The I/O operations (both read and write) are multiplexed across the source and destination sites on these composite LUNs, ensuring transparency.
 
 For viewing composite LUNs, both the primary and secondary clusters with the LUNs that are a part of the Consistency Group relationship should be added and discovered on Unified Manager. Only iSCSI and FCP LUNs are supported.
 
-For information about SM-BC, see link:https://docs.netapp.com/us-en/ontap/smbc/index.html[ONTAP 9 Documentation for SM-BC].
+For information about SnapMirror active sync, see link:https://docs.netapp.com/us-en/ontap/smbc/index.html[ONTAP 9 Documentation for SnapMirror active sync (formerly SM-BC)].
 
 To view composite LUNs in your environment follow these steps:
 

data-protection/view-protection-status.adoc

@@ -56,7 +56,7 @@ Clicking the events on this page takes you to the Event details page. You can cl
 
 *	Individual events raised for SnapMirror relationships, including the events raised in the last 24 hours
 *	The number of volumes protected by each type of SnapMirror policy.
-*	The number of relationships protected by the SnapMirror relationship types, such as Asynchronous Mirror, Asynchronous Vault, Asynchronous MirrorVault, StricxtSync, SnapMirror Business Continuity (SMBC) consistency group, and Sync.
+*	The number of relationships protected by the SnapMirror relationship types, such as Asynchronous Mirror, Asynchronous Vault, Asynchronous MirrorVault, StricxtSync, SnapMirror active sync consistency group, and Sync.
 *	The number of healthy and unhealthy relationships.
 *	Break-up of the volume relationship count. You can toggle the charts by RPO lag time and status.
 *   Lag thresholds for unmanaged relationship. You can click the settings icon (image:../media/Settings.PNG[Icon for lag threshold settings]) to configure the lag threshold settings. For more information, see link:../health-checker/task_configure_lag_threshold_settings_for_unmanaged_protection.html[Configuring lag threshold settings for unmanaged protection relationships].

events/reference_snapmirror_relationship_events.adoc

@@ -149,7 +149,7 @@ Mediator
 a|
 Error
 a|
-Ontap Mediator Connectivity has been reestablished, and is resynced and ready for SMBC (snapmirrorMediatorInQuorum)
+Ontap Mediator Connectivity has been reestablished, and is resynced and ready for SnapMirror active sync (snapmirrorMediatorInQuorum)
 
 a|
 Event

health-checker/reference_health_volume_details_page.adoc

@@ -498,7 +498,7 @@ Displays the type of protection used for the selected volume. For example, if a
 
  ** Consistency Group
 +
-For volumes protected by SnapMirror Business Continuity (SM-BC) relationships, this column displays the Consistency Group of the volume.
+For volumes protected by SnapMirror active sync relationships, this column displays the Consistency Group of the volume.
 
 
 * *Views*

install-linux/reference_red_hat_and_centos_software_and_installation_requirements.adoc

@@ -24,6 +24,9 @@ http://mysupport.netapp.com/matrix[mysupport.netapp.com/matrix^]
 
 The server should be dedicated to running Unified Manager. No other applications should be installed on the server. It is possible that vulnerability scanner like Qualys is installed on your Linux system because of company regulations. You should disable the vulnerability scanner before installing Unified Manager to prevent the installation from failing. 
 
+[NOTE]
+Vulnerability scanners (such as Qualys) might lead to high CPU usage when scanning the virtual machine (VM) either internally (where Unified Manager and the vulnerability scanner are installed on the same VM) or externally (where Unified Manager and the vulnerability scanner are installed on two different servers and the vulnerability scanner scans the VM where Unified Manager is installed). This issue often results in the VM being unresponsive and affects the Unified Manager services. Therefore, NetApp recommends disabling the vulnerability scanner in the VM where Unified Manager is installed. If disabling the scanner is not an option, then scan the VM during non-business hours and restart the services after the scan is complete.
+
 == Third-party software
 
 Unified Manager is deployed on a WildFly web server. WildFly 26.1.3 is bundled and configured with Unified Manager.

install-windows/reference_protocol_and_port_requirements.adoc

@@ -76,6 +76,39 @@ a|
 3306
 a|
 Used to enable OnCommand Workflow Automation and OnCommand API Services access to Unified Manager.
+a|
+AMQP QPID broker
+a|
+TCP/IP
+a|
+56072
+a|
+Used for internal message communication.
+a|
+AMQP QPID broker
+a|
+WebSocket over TCP
+a|
+56080
+a|
+Used to listen on this port for messages received from ONTAP (cloud agent).
+a|
+AMQP QPID broker
+a|
+WebSocket over TCP
+a|
+56443
+a|
+Used to listen on this port for messages received from ONTAP (cloud agent).The communication over this port supports encryption provided by TLS or SSL.
+a|
+AMQP QPID broker
+a|
+HTTP
+a|
+9000
+a|
+Used to launch the AMQP management UI interface on this page.
+
 |===
 
 [NOTE]
@@ -167,4 +200,28 @@ a|
 123/UDP
 a|
 Used to synchronize the time on the Unified Manager server with an external NTP time server. (VMware systems only)
+a|
+AMQP QPID broker
+a|
+TCP/IP
+a|
+56072
+a|
+Used for internal message communication.
+a|
+AMQP QPID broker
+a|
+WebSocket over TCP
+a|
+56080
+a|
+Used to listen on this port for messages received from ONTAP (cloud agent).
+a|
+AMQP QPID broker
+a|
+WebSocket over TCP
+a|
+56443
+a|
+Used to listen on this port for messages received from ONTAP (cloud agent). The communication through this port supports encryption provided by TLS or SSL.
 |===