1.4.1 Continuity of Source Workloads Impacted by Transfer Method Selection
The operational continuity of your source workload depends on the selected transfer method.
The following table provides information about the different transfer methods along with their impact on the operational continuity of your source workloads.
Table 1-6 Continuity Impact by Transfer Method
|
Take Control |
The source is offline during the entire migration. |
|
Block-Based |
A single reboot is required at the beginning of the conversion job’s execution, when the Block-based Transfer Component is installed on the source.
On upgrading the component, existing protection contracts are suspended. |
|
VSS Block-Based |
No impact on migration jobs.
Impact on protection jobs: A single reboot is required at the beginning of the job’s execution, when the VSS Block-based Transfer Component is installed on the source. |
|
File-Based; VSS File-Based |
No impact on migration jobs. |
1.4.2 Default Post-Conversion End States of Source and Target Workloads
The following table lists the default post-conversion end states of source and target workloads by conversion task. You can also manually specify a post-conversion end state for your source and target. See Specifying End States for Source and Target Workloads.
Table 1-7 Default Post-Conversion End States
|
Move |
Take Control |
-
Shut down
-
Leave under control, then shut down after transfer, if transfer is OK
-
Leave under Control, then restart after transfer, if the transfer is not OK
|
|
|
Move |
Live Transfer |
|
|
|
Copy |
Take Control |
|
|
|
Copy |
Live Transfer |
|
|