Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist

Welcome to Cohesity Documentation

Ask me anything — from configuration steps and architecture overviews to troubleshooting, feature details, and release notes.

AI may make mistakes. Always verify critical information.

Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. Product Documentation
  3. Section III. Setting up and managing the resiliency domain
  4. Integrating with InfoScale clusters
  5. Prerequisites for supporting InfoScale cluster node in Veritas Resiliency Platform

Prerequisites for supporting InfoScale cluster node in Veritas Resiliency Platform

The following prerequisites are required for managing InfoScale applications and clusters in Veritas Resiliency Platform:

  • Ensure that IMS can communicate with the cluster hosts.

  • Ensure that cluster hosts can resolve IMS name.

  • Ensure that the Veritas InfoScale Operations Manager Managed Host (MH) version should be 7.2 onwards in the cluster hosts.

  • For InfoScale service groups configured and associated with different replications, ensure that the service group dependency between these service groups should be online global firm.

    Note:

    If the service group dependency is other than online global firm, then the discovery may not happen in Resiliency Platform environment.

  • When VVR replication is configured for the InfoScale service groups and the same service group is added in Resiliency Platform, then the AutoResync attribute of the RVGPri resource should be set to "1" . Refer VVR configuration for more details on VVR replication configuration.

  • Ensure that the Service Group is at the top level in the hierarchy if you have application and replication in the Service Group.

  • For managing recovery of InfoScale applications, Global Cluster Option (GCO) should be enabled.

  • High Availability Daemon (HAD) should be running on the host.

  • Ensure that the time difference between the system clocks on the IMS and on the host is not more than 90 minutes. It is recommended to configure NTP on the hosts that needs to be secured. NTP should be configured in such a way that hosts on the source data center remain in sync with the IMS on source data center and hosts on target data center remain in sync with the IMS on the target data center.

  • For Unix systems, use a user account that is a part of the root group. For Windows systems, it is recommended to use a domain user account with local administrator privileges. If you cannot use a domain user account with local administrator privileges, you have an option to use an administrator user or a user in local administrator group with required prerequisites.

  • For configuring Unix InfoScale cluster, use a user account that is a part of the root group or a user account that has password-less sudo privileges.

The diagram below describe how the deployment architecture is required to manage InfoScale applications under Resiliency Platform:

Figure: Deployment architecture to manage InfoScale applications

Deployment architecture to manage InfoScale applications

See Configuring InfoScale clusters in Resiliency Platform.

Feedback

Was this page helpful?
Previous
Support matrix for InfoScale applications
Next
Configuring password-less sudo privileges for InfoScale cluster configuration

Feedback

Was this page helpful?