DR CloudCasa Servers

Note

This section only applies to CloudCasa Selfhosted version.

The DR CC servers page provides information about CloudCasa servers installed at the primary and DR sites. In a typical DR configuration, workloads would be running in a cluster at primary site while the cluster at the DR site is in a standby state, ready to start running workloads in case primary site fails. In this scenario, one may want to install two different CloudCasa servers - one at primary site and the other at DR site. The primary cluster will be registered in the CC server running in the primary site while the DR cluster will be registered in the CC server running at DR site. Just to be clear, installing two CloudCasa servers as described above is not mandatory. CloudCasa fully supports using the same CloudCasa instance for both primary and DR clusters.

In rest of the section, the CC server running in DR site would be referred to as “remote CC server”.

A CC server can be added to CloudCasa by going to DR => CC servers page and clicking on Add CC server. When adding a DR CC server, you will be prompted to supply the following information:

Name

A descriptive name you want to use for this CC server

URL

End point where CloudCasa server can be reached. This is typically the URL you use in your browser to reach CloudCasa.

Disable TLS certificate validation

Select the option if CloudCasa server uses a self-signed certificate

API key

An API key with ADMIN role, created on the CC server.

When a CC server resource is added to point to the CC server at DR site, CloudCasa automatically adds a CC server resource pointing to the CloudCasa server at the primary site (including the creation of the required API key). This is needed so that some DR tasks can be run at the primary site as part of failover and failback. Such automatically added CC server resources are named using the pattern

Reverse CloudCasa server  (<NAME-OF-THE-CREATED-CC-SERVER>)

While creating a DR Plan, users can configure a CC server, if one is present.

In this case, several DR related resources such as DR plan, storage systems, cluster storage systems, and storage volumes are synced from the primary CC server to the remote CC server. The synced resources on the remote CC server are read-only.

Note that when a remote CC server is configured for a DR plan, DR recovery job can only be created and run from the remote CC server. These operations cannot be run from the primary CC server.