Posting this case on behalf of Masao.H,
Hello Zerto support
Tell me about the failover specifications
I think that the command (import-instance, import-volume) is issued from ZCA at the time of failover, but the VMDK file is specified when issuing the command, but if the migration destination is AWS, the VMDK in S3 Is it a specified recognition?
If possible, please tell us what option you want to issue failover (import-instance, import-volume).
I’m looking for the answer will response once I have the answer.
The Import-instance is for the boot volume, and Import-voume is for data volumes.
For more information, please review the relevant AWS document:
Zerto provides three different import method: AWS Import, zImport for Data Volumes and zImport for All Volumes.
AWS Import uses AWS API to completed the failover(Move) task. The failover(Move) task takes longer time to complete.
zImport for Data Volumes and zImport for All Volumes provides better RPO when you perform a failover task.
When the failover(Move) starts, Zerto creates an instance (called zImporter) for each disks (e.g. two disks = two instances)..
The difference between zImport for Data Volumes and zImport for All Volumes is that Zerto still use AWS import for OS disk if you choose zImport for Data Volumes.
For more information, please refer to the following document on page 26, 27 and 28.
AWS Import: https://gyazo.com/b56886f21ad4e3f37d41a08124e43343
zImport for Data Volumes: https://gyazo.com/66518e1a2732bb2b430816dbfc8e4f3c
zImport for All Volumes: https://gyazo.com/438d5b0a79aa6252aae1e57f730f1785
All mirror disks and journal disks are stored in S3 bucket (Scalable and Cheap Object Storage).
Only when a recovery operation is initialized, Zerto uses a combination of methods to convert the Amazon S3 objects into recovery disk in EC2 as EBS disks.