This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
public:microsoft_hyper-v [2019/08/16 17:53] ronnie.chan |
public:microsoft_hyper-v [2019/08/26 11:13] ronnie.chan |
||
---|---|---|---|
Line 8: | Line 8: | ||
The following high level system architecture diagram illustrates the major elements involved in the backup process of a Hyper-V host with AhsayOBM and AhsayCBS. | The following high level system architecture diagram illustrates the major elements involved in the backup process of a Hyper-V host with AhsayOBM and AhsayCBS. | ||
- | {{public:ahsay_wiki_module_hyper-v_architecture_1.png?800}} | + | {{public:content_components_hyperv.png?800}} |
---- | ---- | ||
Line 169: | Line 169: | ||
</code> | </code> | ||
- | </WRAP> | ||
=== Integration Service === | === Integration Service === | ||
Line 230: | Line 229: | ||
For Run Direct Hyper-V Cluster backup sets the storage destination must be accessible by all Hyper-V nodes. | For Run Direct Hyper-V Cluster backup sets the storage destination must be accessible by all Hyper-V nodes. | ||
- | ==- Hyper-V Cluster === | + | === Hyper-V Cluster === |
For Hyper-V Cluster backup sets the guest virtual machines must be created and managed by the Failover Cluster Manager. | For Hyper-V Cluster backup sets the guest virtual machines must be created and managed by the Failover Cluster Manager. | ||
- | |||
- | |||
</WRAP> | </WRAP> |