CLELUQMAN Lv4Posted 2024-Sep-19 08:39
  
Q1: When failover happens, another VPN connection must be created between the on-premises site and the VPC in MCS.
Q2: The VMs in the on-premises site can be divided into two categories: VMs protected by aDR and those VMs without aDR protection.
Q3: When the DR link has small bandwidth, but the backup data volume is great, online replication takes a longer time than offline backup. Therefore, using replica seeds is recommended.
Q4: Please pay attention, by default there not free disk slot in the HCI nodes of MCS, so it is not recommended to use HDD/SSD to store the seed files.
Newbie517762 Lv5Posted 2024-Sep-19 12:34
  
Q1: When a failover happens and the aDR customer accesses the service by IP address, they need to provide a channel to access the new IP address. This ensures that users can continue to access the service without interruption.

Q2: The VMs in the on-premises site can be divided into two categories:
1. VMs protected by aDR - These are the virtual machines that have disaster recovery protection enabled.
2. VMs without aDR protection - These are the virtual machines that do not have disaster recovery protection.

Q3: When the DR link has small bandwidth but the backup data volume is great, it is recommended to use replica seeds. This approach helps to manage the initial data replication more efficiently, especially when dealing with large data volumes.

Q4: It is not recommended to use HDD/SSD to store the seed files because, by default, there are no free disk slots in the HCI nodes of MCS. Instead, it is suggested to use a portable storage device with a USB interface to store and transport the seed files, as there is an available USB interface on the HCI nodes of MCS.
Chana T Lv1Posted 2024-Sep-19 16:31
  
Q1: Provide a channel to access the new IP address.
Q2: VMs protected by aDR and those VMs without aDR protection
Q3: using replica seeds
Q4: it is not recommended to use HDD/SSD to store the seed files.
Christ Lee Lv2Posted 2024-Sep-20 10:17
  
Q1: Provide a channel to access the new IP address
Q2: VMs protected by aDR & those VMs without aDR protection
Q3: recommend using replica seeds
Q4: Using HDD/SSD to store the seed files is not recommended.
You suggest using a portable storage device with a USB interface to store and transport the seed files,
as there is an available USB interface on the HCI nodes of MCS.
If you decide to use Seed files,  better inform and confirm with the HQ team in advance.
ilham Lv1Posted 2024-Sep-20 10:59
  
Q1 : Provide a channel to access the new IP address
Q2 : VMs protected by aDR and VMs without aDR protection
Q3 : Using Replica Seeds
Q4 : Yes, it is Possible
Ghostlying Lv2Posted 2024-Sep-20 11:00
  
Q1: Provide a channel to access the new IP address
Q2: VMs protected by aDR & those VMs without aDR protection
Q3: recommend using replica seeds
Q4: Using HDD/SSD to store the seed files is not recommended.
Newbie676033 Lv1Posted 2024-Sep-23 13:48
  
Q1) When a failover happens, what can the aDR customer do if they access the service by IP address?
A) When failover occurs, the aDR customer needs to provide a channel for accessing the new IP address. If the users access the service via IP address, an additional site-to-site VPN or SSL VPN must be configured to allow end users to reach the new IP address.

Q2) Which categories can be divided from the VMs in the on-premises site?
A) The VMs in the on-premises site can be divided into two categories:

a) VMs protected by aDR: These have specific dependencies like boot order and data access direction.
b) VMs without aDR protection: These might have dependencies on aDR-protected VMs for data access​.

Q3) What key action can be done when the DR link has small bandwidth, but the backup data volume is great?
A) When the DR link has small bandwidth and the backup data volume is large, it is recommended to use replica seeds. This involves exporting the VM data to a disk (such as an HDD or NAS), transporting the disk to the secondary site, and importing the data. Only the incremental data will need to be transmitted later​.

Q4) Is it possible to use HDD/SSD to store the seed files?
A) While it is possible to use HDD/SSD to store seed files, it is not recommended due to limited disk slot availability in HCI nodes. Instead, it is suggested to use portable storage devices with a USB interface to store and transport seed files​.
Zonger Lv5Posted 2024-Sep-23 19:37
  
Q1: The aDR feature automatically updates the DNS record to point to the secondary IP address allowing the customer to seamlessly transition to the backup network without interruption. As a result, the customer can continue to access the service without any disruption even if they are accessing it by IP address.

Q2: The VMs on-premises site can be divided into three categories:
Infrastructure VMs
Application VMs
Edge VMs.

Q3: Implementing data deduplication and compression can achieve through deduplication storage, compression algorithms or cloud-based backup solutions. Reducing data transfer volume ensures efficient DR link handling and reliable disaster recovery.

Q4: Yes. Seed files can be stored on external storage devices such as HDDs or SSDs which can be connected to the Sangfor device via USB or SATA interfaces.
Sheikh_Shani Lv2Posted 2024-Sep-24 02:39
  
Q # 1
ANS

1.1 Service Access Method
  
No matter where the end users come from, they access the service by IP address orDNS Domain name. When recovery atthe secondary site or migration to the primary site is implemented,the customer needs to act immediately to keep the accessibility of the service for the end users.
  
   
Method
   
Keyactionsfor aDR customer when failover happens
   
By IP address
   
Provide a channel to access the new IP address.
   
By Domain Name
   
Change DNS resolver record.
1.1 VM DependencyRelationship
  
The VMs in the on-premises site can be divided into two categories: VMs protected by aDR and those VMs without aDR protection. We need to know their dependencies, as listed in the table below.
  
   
VM Categories
   
VM Dependency
VMsprotected by aDR
1.The boot order and data access directionbetweenthem.
VMs without aDR protection
1.Is there any data access to VM protected by aDR or   vice versa
  
For example, Figure 8 shows 4 VMsonthe on-premises site. The web serverand the db server are protected by aDR,while the HRS server and PLM serverare notprotected by aDR.
  
The web server depends on the db server, and the db server must boot first and be ready before the web server can provide service.
In Figure 9,suppose the unprotected PLM server also accesses the db server.When the db server failovers to the MCS site, and the userwants to access the PLM server to get data from the db server, a second VPN connection is required.
1.1 Failover Policy
We need to design a failover policy for all the VMs with DR enabled. Usually, we would choose full failover or partial failover.
   
Failover policy
   
Details description
Full failover
If any aDR-protected VMserror, failover all of them   to the MCS site.
Partial failover
If any aDR-protected VMs error, failover only those   VMs in the error status to the MCS site.

For example,in Figure 10, when the web server error,a full failover will make both web server and db serverfailover to the MCS site. While in partial failover, only web server is failover to the MCS site, as shown in Figure 11.

                                                  
Sheikh_Shani Lv2Posted 2024-Sep-24 02:47
  
Q # 2

ANS

Now in allMCS sites,the SCC is 2.2.32EN , SCP is 6.9.32EN, and HCI is 670R3EN with patches. In the following table, we list matched the SCP version and HCI
   
MCS site
   
On-Premises site
SCC
2.2.32
HCI   version
SCP   version
SCP
6.9.32
HCI
670R3EN   with patches
HCI   version = 670R3EN
SCP6861   or SCP690EN or SCP691EN
HCI   version = 690 EN
SCP690EN   or SCP691EN
HCI   version = 691EN
SCP691EN




















version when planning for Hybrid Cloud for MCSand on-premises SCP/HCI.

The new version SCC 2.6 will bereleasedin Q4 2024. Each MCS site will be upgrade to SCC 2.6 later, its SCP and HCI will be upgrade too. Only after the upgrade, on-premises SCP 6.10 and HCI 6.10 will be supported accordingly.

   
HCI
   
670R3EN   with patches
HCI   version = 670R3EN
SCP6861   or SCP690EN or SCP691EN
HCI   version = 690 EN
SCP690EN   or SCP691EN
HCI   version = 691EN
SCP691EN
  
                                                         
  
   
  
The on-premises SCP and HCI version must be in the compatibility list, otherwise the aDR can’t be setup between MCS site and On-premises site, must ask HQ to confirm about the on-premises SCP and HCI version if not sure about this.