3.2.2. Usage patterns

When capacity required for backup and time requirements are organized, it is necessary to consider patterns for using Acronis in the ECL1.0 environment. As for ECL1.0 environment, backup destinations can be applied in some environments.
This section describes the following patterns.
../../../_images/image235.png

3.2.2.1. Usage pattern 1

It is possible to prepare a server that is different from the backup target server and specify vHDD as the backup destination.
../../../_images/image311.png

[Points]
It is possible to configure the environment for backup and restoration in compute resources at a low cost.
The backup destination also exists in compute resource so that pattern 2 and pattern 3 need to be examined to improve safety further.

[Scope of recovery]
Recovery to the timing just before occurrence of failure of individual unit of server is performed. It is impossible to respond to DC failure and large scale disaster (regional disaster).

3.2.2.2. Usage pattern 2

If already using the collocation service apart from ECL1.0, it is possible to use your server or storage as a backup destination of the server to be backed up.
../../../_images/image411.png

[Points]
Safety is enhanced compared to the pattern 1 by backing up data outside the compute resource.
If ECL1.0 establishes the collocation service with ECL1.0, it is necessary to subscribe the collocation connection service separately so that the cost becomes higher than that of the pattern 1. In addition, it is necessary to take care of the network bandwidth.
The pattern 3 needs to be examined to improve safety further.
[Scope of recovery]
Restoration at the timing before occurrence of failure of the service unit and occurrence of failure of cloud platform. It is impossible to respond to DC failure and large scale disaster (regional disaster).

3.2.2.3. Usage pattern 3

If placing emphasis on safety over cost and it is necessary to recover from DC or large-scale disaster, it is possible to use GFS as a backup destination for the server to be backed up.
../../../_images/image511.png

[Points]
Safety improves compared to the pattern 2 by using the remote location replication function of GFS.
It is necessary to subscribe GFS separately so that the cost becomes higher than that of the pattern 1. In addition, it is necessary to take care of the network bandwidth.
[Scope of recovery]
Backup is retained with GFS functions even if DC failure and large-scale disaster (regional disaster) occurs.