Hello, everyone!
Today we can discuss the Cloud Server.
1 Relationship Between CSDR and Other Services
ECS
This service allows CSDR to apply for and create production and placeholder ECSs.
Elastic Volume Service (EVS)
This service indirectly provides EVS disks for CSDR by directly providing them to ECSs.
Virtual Private Cloud (VPC)
This service indirectly provides DR networks for CSDR by directly providing networks for DR placeholder ECSs.
2 Common Concepts
2.1 Service Instance
A service instance is the combination of the DR recovery policy and time settings of specific production and DR ECSs. You can perform DR operations, such as testing, data clearance, planned migration, and fault recovery, on service instances.
2.2 Replication Policy
A replication policy defines the replication mode of DR protection and scheduling policy that the DR management system uses to protect replication objects. It is configured during CSDR creation.
2.3 Recovery Policy
A recovery policy defines the start priorities of ECSs in a service instance when data or applications in the production center are being recovered to the DR center.
3 Accessing and Using CSDR
3.1 How to Access CSDR
CloudOpera ServiceCenter can be accessed through a management console.
If you are a resource administrator of CloudOpera ServiceCenter or have the operation permission for OBS, you can directly log in to the management console and select Cloud Server DR Service from the Productor Consolepage.
3.2 Restrictions
Restrictions on CSDR are as follows:
· CSDR can only be deployed in cross-region mode, instead of within a region.
· Resources in resource pools in each availability zone of an OpenStack must adopt the same virtualization type.
· Only one-to-one replication relationship is supported. One-to-N or N-to-one replication relationship is not supported.
· EVS disks configured with CSDR only support advanced SAN storage (an EVS disk of an ECS corresponds to a LUN on the storage device).
· Cloud Host HA Service and Active/Standby DR Service cannot be deployed for the same cloud host at the same time.
· An ECS can only be added to one CSDR instance.
· EVS disks of ECSs that are configured with CSDR must be on the same production storage. ECSs that mount the same shared disk must be in the same CSDR instance.
· The NIC used for a CSDR test cannot be a PCI passthrough NIC or an SRIOV NIC.
· You cannot apply for DR protection for partial EVS disks of an ECS. After a new EVS disk is bound to a DR ECS, the tenant needs to manually configure DR protection for this disk.
· CSDR is only applicable to replicate VMs from the production region to the DR region.
· Operations such as planned migration and fault failover are performed by the DR administrator using BCManager eReplication.
· CSDR is not applicable to an ECS whose storage does not support remote replication.
· If a protected cloud server is a KVM VM, the user needs to check whether Cloudinit or Cloudbaseinit of the VM meets the DR configuration requirements before applying for Active/Standby DR Service. If Cloudinit or Cloudbaseinit of the VM does not meet the DR configuration requirements, disable or uninstall it; otherwise, the password or key used to log in to the VM may change after a DR test or switchover is performed, which may cause the user unable to log in to the VM.
· When applying for a DR test, configure a gateway IP address for a test NIC on the VM if the test NIC is used to connect to the test network. In this way, the VM can be accessed from other network segments.
· Data disks of DR mirroring and production mirroring must be of the same type. Using the same mirroring template is recommended.
· VMs that require DR are shut down
That's all, thanks!
