Source:VMware Single File Restore and Instant Recovery Support Matrix: Difference between revisions
m (Prepared for translation) |
(Marked this version for translation) |
||
| Line 1: | Line 1: | ||
<div class="noprint"><languages/><translate> | <div class="noprint"><languages/><translate> | ||
<!--T:6--> | |||
{{Copyright SEP AG en}} | {{Copyright SEP AG en}} | ||
{{Navigation_latest|release=[[SEP_sesam_Release_Versions|5.0.0 ''Jaglion'']]|link=[[Special:MyLanguage/VMWare|VMware archive]]}}</translate></div><br /> | {{Navigation_latest|release=[[SEP_sesam_Release_Versions|5.0.0 ''Jaglion'']]|link=[[Special:MyLanguage/VMWare|VMware archive]]}}</translate></div><br /> | ||
<translate>==Overview==</translate> | <translate>==Overview== <!--T:7--></translate> | ||
<div class="boilerplate metadata" id="Additional resources" style="background-color: #f0f0f0; color:#636f73; border: 1px ridge #cdd3db; margin: 0.5em; padding: 0.5em; float: right; width: 35%; "><center><b><translate>Additional resources</translate></b></center> | <div class="boilerplate metadata" id="Additional resources" style="background-color: #f0f0f0; color:#636f73; border: 1px ridge #cdd3db; margin: 0.5em; padding: 0.5em; float: right; width: 35%; "><center><b><translate><!--T:8--> Additional resources</translate></b></center> | ||
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;" | {|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;" | ||
| rowspan="2" style="padding:0px 10px 0px;" |[[File:SEP_next.png|45px|link=Special:MyLanguage/Changed_Block_Tracking_(CBT)|Changed Block Tracking (CBT)]] | | rowspan="2" style="padding:0px 10px 0px;" |[[File:SEP_next.png|45px|link=Special:MyLanguage/Changed_Block_Tracking_(CBT)|Changed Block Tracking (CBT)]] | ||
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <translate>See also: [[Special:MyLanguage/5_0_0:VMware_Single_File_Restore|VMware Single File Restore]] – [[VMware_Instant_Recovery|VMware Instant Recovery]] – [[Special:MyLanguage/5_0_0:VMware_Restore|VMware Restore]] – [[Special:MyLanguage/Changed_Block_Tracking_(CBT)|Changed Block Tracking (CBT)]]</translate> | | style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <translate><!--T:9--> See also: [[Special:MyLanguage/5_0_0:VMware_Single_File_Restore|VMware Single File Restore]] – [[VMware_Instant_Recovery|VMware Instant Recovery]] – [[Special:MyLanguage/5_0_0:VMware_Restore|VMware Restore]] – [[Special:MyLanguage/Changed_Block_Tracking_(CBT)|Changed Block Tracking (CBT)]]</translate> | ||
|} | |} | ||
| Line 21: | Line 22: | ||
|} | |} | ||
</div> | </div> | ||
<translate>SEP sesam allows you to perform different types of restore and recovery from almost any type of VMware backup, including VM single file and instant recovery. Enabling or disabling the ''Backup as image'' option and in v. ≥ [[SEP_sesam_Release_Versions|5.0.0 ''Jaglion'']] also the option ''When run with backup level 'COPY', write all data into single saveset'', affects the size of your backed up data and determines whether or not [[Special:MyLanguage/Changed_Block_Tracking_(CBT)|changed block tracking (CBT)]] is used. | <translate><!--T:10--> | ||
SEP sesam allows you to perform different types of restore and recovery from almost any type of VMware backup, including VM single file and instant recovery. Enabling or disabling the ''Backup as image'' option and in v. ≥ [[SEP_sesam_Release_Versions|5.0.0 ''Jaglion'']] also the option ''When run with backup level 'COPY', write all data into single saveset'', affects the size of your backed up data and determines whether or not [[Special:MyLanguage/Changed_Block_Tracking_(CBT)|changed block tracking (CBT)]] is used. | |||
<!--T:11--> | |||
For example, if you perform a ''FULL'' backup using SEP sesam and the GUI option ''Backup as image'' is selected, CBT is not used. The same applies if you run a ''COPY'' backup with the GUI option ''When run with backup level 'COPY', write all data into single saveset''. Both will result in an increased size of the backed up data (see matrix below). | For example, if you perform a ''FULL'' backup using SEP sesam and the GUI option ''Backup as image'' is selected, CBT is not used. The same applies if you run a ''COPY'' backup with the GUI option ''When run with backup level 'COPY', write all data into single saveset''. Both will result in an increased size of the backed up data (see matrix below). | ||
<!--T:12--> | |||
Note that with ''Jaglion'', the behavior of VMware ''COPY'' backups has changed, so make sure to follow the relevant version-specific instructions. If you use previous SEP sesam versions, see [[Special:MyLanguage/4_4_3_Tigon:VMware_Single_File_Restore_and_Instant_Recovery_Support_Matrix|VMware SF and IR Support Matrix v. ≤ 4.4.3 ''Beefalo V2'']] and [[Special:MyLanguage/4_4_3:VMware_Single_File_Restore_and_Instant_Recovery_Support_Matrix|VMware SF and IR Support Matrix v. < 4.4.3 ''Tigon'']]. | Note that with ''Jaglion'', the behavior of VMware ''COPY'' backups has changed, so make sure to follow the relevant version-specific instructions. If you use previous SEP sesam versions, see [[Special:MyLanguage/4_4_3_Tigon:VMware_Single_File_Restore_and_Instant_Recovery_Support_Matrix|VMware SF and IR Support Matrix v. ≤ 4.4.3 ''Beefalo V2'']] and [[Special:MyLanguage/4_4_3:VMware_Single_File_Restore_and_Instant_Recovery_Support_Matrix|VMware SF and IR Support Matrix v. < 4.4.3 ''Tigon'']]. | ||
== VMware SFR and IR matrix == | == VMware SFR and IR matrix == <!--T:13--> | ||
<!--T:14--> | |||
The following chart shows different combinations of used options and how they affect the CBT usage, the disk size usage and the support for ''single file (SF) restore and VMware instant recovery (IR)''. | The following chart shows different combinations of used options and how they affect the CBT usage, the disk size usage and the support for ''single file (SF) restore and VMware instant recovery (IR)''. | ||
</translate> | </translate> | ||
{| border="2" cellpadding="4" cellspacing="0" style="width:90%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;" | {| border="2" cellpadding="4" cellspacing="0" style="width:90%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;" | ||
|- style="background:grey; color:#FFFFFF" | |- style="background:grey; color:#FFFFFF" | ||
! scope="col" | <translate>Backup level</translate> | ! scope="col" | <translate><!--T:15--> Backup level</translate> | ||
! scope="col" | <translate>GUI option ''Backup as image''/''When run with backup level 'COPY'...''<br />{{Tick}} (enabled) or <br />{{Cross}} (disabled)</translate> | ! scope="col" | <translate><!--T:16--> GUI option ''Backup as image''/''When run with backup level 'COPY'...''<br />{{Tick}} (enabled) or <br />{{Cross}} (disabled)</translate> | ||
! scope="col" | <translate>CBT usage</translate> | ! scope="col" | <translate><!--T:17--> CBT usage</translate> | ||
! scope="col" | <translate>Total disk size of VM (GB)</translate> | ! scope="col" | <translate><!--T:18--> Total disk size of VM (GB)</translate> | ||
! scope="col" | <translate>Occupied disk size (GB)</translate> | ! scope="col" | <translate><!--T:19--> Occupied disk size (GB)</translate> | ||
! scope="col" | <translate>Backed up disk size (GB)</translate> | ! scope="col" | <translate><!--T:20--> Backed up disk size (GB)</translate> | ||
! scope="col" | <translate>Support for SF & IR</translate> | ! scope="col" | <translate><!--T:21--> Support for SF & IR</translate> | ||
|- | |- | ||
|FULL || <translate> [[image:Backup as image option-checked.jpg|link=]] || {{Cross}} CBT is not used for FULL backup. <br />A raw backup of VMDK is performed. However, CBT is used for subsequent INCR & DIFF in the same backup chain. </translate> || 100 || 60 || 100 || {{Tick}} <translate>(also with INCR/DIFF)</translate> | |FULL || <translate> <!--T:22--> [[image:Backup as image option-checked.jpg|link=]] || {{Cross}} CBT is not used for FULL backup. <br />A raw backup of VMDK is performed. However, CBT is used for subsequent INCR & DIFF in the same backup chain. </translate> || 100 || 60 || 100 || {{Tick}} <translate><!--T:23--> (also with INCR/DIFF)</translate> | ||
|- | |- | ||
|FULL || <translate>[[image:Backup as image option-unchecked.jpg|link=]] || {{Tick}} CBT is fully utilized.</translate> || 100|| 60 ||bgcolor="#A3D306"| 60|| {{Tick}} <translate>(also with INCR/DIFF) </translate> | |FULL || <translate><!--T:24--> [[image:Backup as image option-unchecked.jpg|link=]] || {{Tick}} CBT is fully utilized.</translate> || 100|| 60 ||bgcolor="#A3D306"| 60|| {{Tick}} <translate><!--T:25--> (also with INCR/DIFF) </translate> | ||
|- | |- | ||
|COPY || <translate>[[image:Backup as image option-checked.jpg|link=]]<br />[[image:VMware_copy_option_checked.jpg|link=]]|| {{Cross}} CBT is not used. </translate>|| 100 || 60 || 100 || {{Tick}} | |COPY || <translate><!--T:26--> [[image:Backup as image option-checked.jpg|link=]]<br />[[image:VMware_copy_option_checked.jpg|link=]]|| {{Cross}} CBT is not used. </translate>|| 100 || 60 || 100 || {{Tick}} | ||
|- | |- | ||
|COPY || <translate>[[image:Backup as image option-unchecked.jpg|link=]]<br />[[image:VMware_copy_option.jpg|link=]] || {{Tick}} CBT is fully utilized.</translate> || 100 || 60 || bgcolor="#A3D306"| 60 ||{{Tick}} | |COPY || <translate><!--T:27--> [[image:Backup as image option-unchecked.jpg|link=]]<br />[[image:VMware_copy_option.jpg|link=]] || {{Tick}} CBT is fully utilized.</translate> || 100 || 60 || bgcolor="#A3D306"| 60 ||{{Tick}} | ||
|- | |- | ||
|} | |} | ||
<translate> | <translate> | ||
==See also== | ==See also== <!--T:28--> | ||
[[Special:MyLanguage/5_0_0:VMware_Single_File_Restore|VMware Single File Restore]] – [[VMware_Instant_Recovery|VMware Instant Recovery]] – [[Special:MyLanguage/5_0_0:VMware_Restore|VMware Restore]] – [[Special:MyLanguage/Changed_Block_Tracking_(CBT)|Changed Block Tracking (CBT)]] – [[SEP_sesam_Release_Versions|SEP sesam Release Versions]] – [[Special:MyLanguage/5_0_0:VMware_Backup|VMware Backup]]</translate> | [[Special:MyLanguage/5_0_0:VMware_Single_File_Restore|VMware Single File Restore]] – [[VMware_Instant_Recovery|VMware Instant Recovery]] – [[Special:MyLanguage/5_0_0:VMware_Restore|VMware Restore]] – [[Special:MyLanguage/Changed_Block_Tracking_(CBT)|Changed Block Tracking (CBT)]] – [[SEP_sesam_Release_Versions|SEP sesam Release Versions]] – [[Special:MyLanguage/5_0_0:VMware_Backup|VMware Backup]]</translate> | ||
[[Category:Support Matrices]] | [[Category:Support Matrices]] | ||
Revision as of 11:59, 14 January 2022
Overview
|
See also: VMware Single File Restore – VMware Instant Recovery – VMware Restore – Changed Block Tracking (CBT) |
|
Check also: SEP sesam Release Versions – VMware Backup |
|
Problems with VMware? Check VMware troubleshooting. |
SEP sesam allows you to perform different types of restore and recovery from almost any type of VMware backup, including VM single file and instant recovery. Enabling or disabling the Backup as image option and in v. ≥ 5.0.0 Jaglion also the option When run with backup level 'COPY', write all data into single saveset, affects the size of your backed up data and determines whether or not changed block tracking (CBT) is used.
For example, if you perform a FULL backup using SEP sesam and the GUI option Backup as image is selected, CBT is not used. The same applies if you run a COPY backup with the GUI option When run with backup level 'COPY', write all data into single saveset. Both will result in an increased size of the backed up data (see matrix below).
Note that with Jaglion, the behavior of VMware COPY backups has changed, so make sure to follow the relevant version-specific instructions. If you use previous SEP sesam versions, see VMware SF and IR Support Matrix v. ≤ 4.4.3 Beefalo V2 and VMware SF and IR Support Matrix v. < 4.4.3 Tigon.
VMware SFR and IR matrix
The following chart shows different combinations of used options and how they affect the CBT usage, the disk size usage and the support for single file (SF) restore and VMware instant recovery (IR).
| Backup level | GUI option Backup as image/When run with backup level 'COPY'... (enabled) or  (disabled)
|
CBT usage | Total disk size of VM (GB) | Occupied disk size (GB) | Backed up disk size (GB) | Support for SF & IR |
|---|---|---|---|---|---|---|
| FULL |  |
CBT is not used for FULL backup. A raw backup of VMDK is performed. However, CBT is used for subsequent INCR & DIFF in the same backup chain. |
100 | 60 | 100 | (also with INCR/DIFF)
|
| FULL |  |
CBT is fully utilized. |
100 | 60 | 60 | (also with INCR/DIFF)
|
| COPY |  |
CBT is not used. |
100 | 60 | 100 |
|
| COPY |  |
CBT is fully utilized. |
100 | 60 | 60 |
|
See also
VMware Single File Restore – VMware Instant Recovery – VMware Restore – Changed Block Tracking (CBT) – SEP sesam Release Versions – VMware Backup