You can perform a failover test on a replication object by selecting an existing restore point or generating a restore point immediately. The two modes follow nearly the same internal flow.
In cross-site disaster recovery scenarios, you can initiate failover test jobs only from the target site.

The following is the failover test process for virtual machines:
After you create a failover test job on the AOC UI, the frontend sends a request to AOC Server to create a FailoverExecution resource object.
AOC Server sends a request to the target-side replication service to create FailoverExecution with the Failover test identifier.
After the FailoverExecution controller in controller-manager observes that FailoverExecution is created, it creates one or more FailoverJob resource objects. After the FailoverJob controller observes that FailoverJob is created, if failover test is performed in Generate now mode, the controller first creates ReplicationJob for asynchronous replication and waits until replication is complete.
If failover test is performed in Select existing restore point mode, or after replication is complete, the FailoverJob controller uses the snapshot reconstruction feature by calling AOC APIs to generate a test virtual machine.
FailoverJob performs network mapping and IP mapping on VPC NICs for the test virtual machine based on the test network/IP mapping rules in the current replication plan, and configures VPC floating IPs based on user options.
After the FailoverExecution controller observes that FailoverJob is complete, it creates one or more BootJob resource objects. After the BootJob controller observes that BootJob is created, it waits for the specified boot delay and then starts the test virtual machine by calling AOC APIs.
If VMTools is running in the specified restore point when you create a failover test job, and the IP mapping scenario is met, ReIPJob is created for the corresponding test virtual machine. After the ReIPJob controller observes that ReIPJob is created, it monitors the startup of the test virtual machine. After the virtual machine starts, the controller changes the IP address of the test virtual machine NIC to the mapped IP based on test IP mapping rules by calling AOC APIs.