Skip to main content

Proof of Concept

Mr.OneProCloudOctober 20, 2025About 2 min

Proof of Concept

This document is primarily intended to describe how to provide Proof of Concept (PoC) for HyperMotion & HyperBDR before the project.

PoC Scope Overview

Solution ComponentIn Scope
Investigation- Gathering and Assessment about detail technical specification requirements
- Information gathering & analysis
Schedule- Provide PoC schedule
Deployment- Provisioning Cloud (VM)
- Setup HyperMotion & HyperBDR Server (for x VM/Server)
- Setup HyperMotion & HyperBDR Agent/Agentless (for x VM/Server)
- Setup and Configuration Migration/DR Backup (Source VM/Server to Cloud)
Functional Testing- Data Sync
- Data Sync Policy
- Drill Testing
- (Optional) Failback Testing (for x VM/Server)

HyperBDR UAT

DR Scope

Solution ComponentIn Scope
Configuration- Configuration HyperMotion & HyperBDR
- Configuration OBS or Block storage backup mode on Cloud
- Configure Cloud as the Migration/DR Recovery Site
Post DeploymentDrill & Takeover:
- Testing Data Sync Process (Policy, Incremental)
- Testing Drill & Takeover (to VM in Cloud)
Finalization- Hand over after deployment is ready in the production

(Optional)Failback Scope

Solution ComponentIn Scope
Configuration- Configuration HyperBDR System
- Configuration OBS or Block storage failback mode on Cloud
- Configure Production Site
Post DeploymentFailback:
- Testing Failback Process (Full Data Transmission)
- Testing Failback Recovery (to VM in source production Site)
Finalization- Hand over after deployment is ready in the production

Out of Scope

Solution ComponentOut of Scope
Network ConfigurationConfiguration existing Backup Network and Firewall such as:
• Configuration and construction of the cloud special line and the Access test (VPN and source production firewall)
• Configuration DR Network and Drill & Takeover Network on Cloud
Business ValidationVerify Drill & Takeover business service availability
Verify Failback business service availability

Warning

Due to the critical importance of networking for cloud disaster recovery, we also aim to assist users as much as possible in completing network configurations.

Responsibility Matrix

Network

Warning

This section is only applicable when users need to use an intranet for output transmission. If users are using a public network solution, they can skip this part.

NoItemOneProCustomer
1Cloud VPN settings(VPN Service or Open Source Solution)Assist
2Private credentails for VPNAssist
3Firewall Settings
4Connectivity Testing

Drill & Takeover

NoItemOneProCustomer
1On-Premises backup server / VM
2Accessing Remote
3Cloud Provisioning
4Setup HyperMotion & HyperBDR
5Hosts Register in Console
6Data Sync & Policy Settings
7Drill & Takeover
8Make sure host boot to login status
9Business System Validation

Failback

NoItemOneProCustomer
1Accessing Remote
2Install Agent on failback VMs on Cloud
3Setup HyperBDR Console
4Failback Host Register in HyperBDR Console
5On-Premises failback server / VM Preparations
6Failback Full Data Sync
7Restore failback server / VM
8Business System Validation

PoC Success Criteria

Click here to access the complete spreadsheet. Please download and print the spreadsheet for easy confirmation of the PoC results after completion.

PoC Success Criteria Checklist

NoCriteriaPassFailRemarks
Success Parameter – DR Backup (for x VM/Server)
1Backup process On-prems to Cloud
2Configuration DR & Backup Policy
3Full and Incremental Backup
4Drill Backup (to VM in Cloud)
5Validity Drill business service availability in Cloud
(Optional) Success Parameter – Failback (for x VM/Server)
1Failback process Cloud to On-prems
2Full data transmission
3Restore failback server / VM in On-prems
4Validity after failback business service availability
Prepared by,Accepted by,





e.g. MSP Companye.g. Cusotmer Company