Enhance Disaster Recovery Scenario thru re-copy template/snapshot between zone

##### ISSUE TYPE

* Enhancement Request

##### COMPONENT NAME

~~~
Snapshot
Tempalte
~~~

##### CLOUDSTACK VERSION

~~~
4.19
~~~

##### CONFIGURATION

##### OS / ENVIRONMENT

##### SUMMARY

While ACS 4.19 brought a new feature that enable copy disk snapshot to another zone, an idea came up to extend this feature to become a disaster recovery approach.

Assume administrator ensure all template and disk snapshots are already made the copy to the partner zone,
when the victim zone's primary/secondary storage is unusable or corrupted, we will have an opportunity to just copy the template/snapshot from partner zone back to victim zone after the storage were rebuilt. However since the current ACS did not design to handle such scenario, so the VM originally host on victim zone has to deploy as a new instance on partner zone and start a new lifecycle.

My preliminary idea is

Scenario 1 - When victim zone primary storage is dead and unrecoverable.
1. Rebuilt a new primary storage
2. ACS found the victim zone instance volume are unavailable
3. We revert the volume from the snapshot image reside on secondary storage (Full Clone).

Scenario 2 - When victim zone secondary storage is dead and unrecoverable.
1. Rebuild a new secondary storage
2. Implement replace copy mechanism for template/snapshot from partner zone to victim zone
3. When we try to revert a snapshot, ACS found the victim zone snapshot disk is lost in victim zone, ACS then copy the snapshot from partner zone to the fresh secondary storage and do the disk recovery (Full Clone).

Scenario 3 - When victim zone both primary secondary storage is dead and unrecoverable.
1. Rebuild both new primary and secondary storage
2. Implement replace copy mechanism for template/snapshot from partner zone to victim zone
3. ACS found the victim zone instance volume are unavailable
5. We revert the volume from the snapshot image
6. ACS found the victim zone snapshot disk is lost in victim zone, ACS then copy the snapshot from partner zone to the fresh secondary storage and do the disk recovery (Full Clone).

With such implementation, when ACS setup multiple zone with scheduled disk snapshot, it will facilitate recovery scenario itself without engaging third party backup solution.

##### STEPS TO REPRODUCE

~~~

~~~

##### EXPECTED RESULTS

~~~

~~~

##### ACTUAL RESULTS

~~~

~~~

Aucun fichier, test ou point d’entrée n’est identifié dans l’issue. Commencez par cartographier les workflows de snapshot, de template, de stockage et de copie interzone de CloudStack, puis définissez le comportement de récupération et les tests nécessaires pour les trois scénarios de disaster recovery.

Rédigé par le modèle d'indexation à partir du texte de l'issue.