1.2.2. Pattern of backup destination

This part had better use when you consider use of Acronis in ECL.
We give you some typical patterns as example.
../../_images/image2.png

1.2.2.1. Pattern1

You cannot backup to vHDD of server for backup. However you can select different server as backup destination.
../../_images/image3.png
[Point]
You can backup and restore at a low cost.
If you improve your security, you had better consider regarding pattern2 or pattern3.
[Recovery area]
Pattern1 intends for problem of a single server. It cannot handle malfunction of data center and natural disaster.

1.2.2.2. Pattern2

If you have already used colocation service, you can select your server or storage as backup destination.
../../_images/image4.png
[Point]
Pattern2 is more secure than Pattern1 because you can store data out of compute resources.
If you do not contract colocation service, you need to contract.
You have to pay attention to network bandwidth.
If you improve your security, you had better consider regarding pattern3.
[Recovery area]
Pattern2 intends for problem of a single server or cloud infrastructure.
It cannot handle malfunction of data center and natural disaster.

1.2.2.3. Pattern3

You focus on security and you need to recover even if malfunction of data center or natural disaster occur.
In this case, you should select GFS as backup destination.
../../_images/image5.png
[Point]
Pattern3 is more secure than Pattern2 because you can save remote area using replication function of GFS. If you restore at replication destination, it is limited to the case that replication source cannot recover. (Copyright OS License)
If you do not contract GFS service, you need to contract.
You have to pay attention to network bandwidth.
[Recovery area]
You can retain backup data using GFS if malfunction of data center or natural disaster occur.