4 4 3:VMware Single File Restore: Difference between revisions

From SEPsesam
(Minor correction and prepared for translation.)
Line 1: Line 1:
<translate>
<div class="noprint"><languages />
{{Copyright SEP AG|en}}
{{Copyright SEP AG|en}}


{{Navigation_latest|release=4.4.3/4.4.3 ''Tigon''|link=[[Special:MyLanguage/VMware|VMware archive]]}}<br />
{{Navigation_latest|release=[[Special:MyLanguage/SEP_sesam_Release_Versions|4.4.3/4.4.3 ''Grolar'']]|link=[[Special:MyLanguage/VMware|VMware archive]]}}</div></translate><br />
==Overview==
<translate>==Overview==</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>Additional resources</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>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/VMware Restore]]
| rowspan="2" style="padding:0px 10px 0px;" | <translate>[[File:SEP_next.png|45px|link=Special:MyLanguage/VMware_Restore]]</translate>
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | See also: [[Special:MyLanguage/4_4_3_Tigon:VMware_Single_File_Restore_and_Instant_Recovery_Support_Matrix|SF & IR support matrix 4.4.3 ''Tigon'']] – [[Special:MyLanguage/4_4_3:VMware_Single_File_Restore_and_Instant_Recovery_Support_Matrix|SF & IR support matrix 4.4.3]] – [[Special:MyLanguage/4_4_3:VMware_Requirements_%26_Restrictions|VMware Requirements & Restrictions]] – [[Special:MyLanguage/4_4_3_Tigon:VMware Backup|VMware Backup 4.4.3 ''Tigon'']] – [[Special:MyLanguage/4_4_3_Tigon:VMware Backup|VMware Backup 4.4.3]] – [[Special:MyLanguage/4_4_3:VMware Restore|VMware Restore]] – [[Special:MyLanguage/4_4_3:VMware Instant Recovery|VMware Instant Recovery]]
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <translate>See also: [[Special:MyLanguage/4_4_3_Tigon:VMware_Single_File_Restore_and_Instant_Recovery_Support_Matrix|SF & IR support matrix 4.4.3 ''Tigon'']] – [[Special:MyLanguage/4_4_3:VMware_Single_File_Restore_and_Instant_Recovery_Support_Matrix|SF & IR support matrix 4.4.3]] – [[Special:MyLanguage/4_4_3:VMware_Requirements_%26_Restrictions|VMware Requirements & Restrictions]] – [[Special:MyLanguage/4_4_3_Tigon:VMware_Backup|VMware Backup 4.4.3 ''Tigon'']] – [[Special:MyLanguage/4_4_3_Tigon:VMware Backup|VMware Backup 4.4.3]] – [[Special:MyLanguage/4_4_3:VMware Restore|VMware Restore]] – [[Special:MyLanguage/4_4_3:VMware Instant Recovery|VMware Instant Recovery]]</translate>
|}
|}


{|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 Troubleshooting.png|45px|link=Special:MyLanguage/Troubleshooting_Guide#VMware_vStorage_API]]
| rowspan="2" style="padding:0px 10px 0px;" | <translate>[[File:SEP Troubleshooting.png|45px|link=Special:MyLanguage/Troubleshooting_Guide#VMware_vStorage_API]]</translate>
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | If you have a problem with your ''VMware'' ''restore'', check the [[Special:MyLanguage/Troubleshooting_Guide#VMware_vStorage_API|VMware troubleshooting]].
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <translate>If you have a problem with your ''VMware'', check the [[Special:MyLanguage/Troubleshooting_Guide#VMware_vStorage_API|VMware troubleshooting]].</translate>
|}
|}


{|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:icon_archived_docs.png|45px|link=Special:MyLanguage/VMware]]
| rowspan="2" style="padding:0px 10px 0px;" | <translate>[[File:icon_archived_docs.png|45px|link=Special:MyLanguage/VMware]]</translate>
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | If you are using an older SEP sesam version, refer to [[Special:MyLanguage/VMware|VMware archive]].
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <translate>If you are using an older SEP sesam version, refer to [[Special:MyLanguage/VMware|VMware archive]].</translate>
|}</div>
|}</div>
{{cheatsheet|
{{cheatsheet|
<ol><li>[[#attach|Attach VMDK to a virtual machine.]] </li>
<ol><li><translate>[[#attach|Attach VMDK to a virtual machine.]]</translate> </li>
<li>[[#client|Configure a virtual host as a SEP sesam client.]]</li>
<li><translate>[[#client|Configure a virtual host as a SEP sesam client.]]</translate></li>
<li>[[#NFS|Prepare the NFS share on Linux.]]</li>  
<li><translate>[[#NFS|Prepare the NFS share on Linux.]]</translate></li>  
<li>[[#restore_VM|Restore a VM using the attached VMDK.]]</li>  
<li><translate>[[#restore_VM|Restore a VM using the attached VMDK.]]</translate></li>  
OR
<translate>OR</translate>
<li>[[#mount|Mount VMDK ]] to a SEP sesam RDS.</li>
<li><translate>[[#mount|Mount VMDK ]] to a SEP sesam RDS.</translate></li>
<li>[[#restore|Restore a single file]] using the mounted VMDK.</li></ol>
<li><translate>[[#restore|Restore a single file]] using the mounted VMDK.</translate></li></ol>
}}<br />
}}<br />
It is estimated that about three quarters of the typical VMware virtual machine restore cases only require a single file restore rather than a restore of an entire virtual machine. As of version 4.4.3, SEP sesam introduces '''simple and flexible single file restore''' that enables you to '''restore an individual item without any special backup preparation''' from '''full/differential/incremental backups'''. To learn what applies to single file restore and instant recovery, which [[Special:MyLanguage/SEP_sesam_Glossary#backup_level|backup level]] supports it and how it relates to the disk size usage, see [[Special:MyLanguage/4_4_3_Tigon:VMware_Single_File_Restore_and_Instant_Recovery_Support_Matrix|SF & IR support matrix 4.4.3 ''Tigon'']].
<translate>It is estimated that about three quarters of the typical VMware virtual machine restore cases only require a single file restore rather than a restore of an entire virtual machine. As of version 4.4.3, SEP sesam introduces '''simple and flexible single file restore''' that enables you to '''restore an individual item without any special backup preparation''' from '''full/differential/incremental backups'''. To learn what applies to single file restore and instant recovery, which [[Special:MyLanguage/SEP_sesam_Glossary#backup_level|backup level]] supports it and how it relates to the disk size usage, see [[Special:MyLanguage/4_4_3_Tigon:VMware_Single_File_Restore_and_Instant_Recovery_Support_Matrix|SF & IR support matrix 4.4.3 ''Tigon'']].


This article provides information for restoring an '''individual item from a vSphere backup'''. For details on how to a restore a single VMware virtual machine, see [[Special:MyLanguage/4_4_3:VMware Restore|VMware Restore]]. For details on how to perform a VMware virtual machine instant recovery, see [[Special:MyLanguage/4_4_3:VMware Instant Recovery|VMware Instant Recovery]].
This article provides information for restoring an '''individual item from a vSphere backup'''. For details on how to a restore a single VMware virtual machine, see [[Special:MyLanguage/4_4_3:VMware Restore|VMware Restore]]. For details on how to perform a VMware virtual machine instant recovery, see [[Special:MyLanguage/4_4_3:VMware Instant Recovery|VMware Instant Recovery]].


You can restore individual items from any successful VMware backup by using any of the following procedures:
You can restore individual items from any successful VMware backup by using any of the following procedures:</translate>
*[[Special:MyLanguage/4_4_3:VMware_Single_File_Restore#attach|Attaching VMDK to a virtual machine]]
*<translate>[[Special:MyLanguage/4_4_3:VMware_Single_File_Restore#attach|Attaching VMDK to a virtual machine]]</translate>
*[[Special:MyLanguage/4_4_3:VMware_Single_File_Restore#mount|Mounting VMDK on a device server]]
*<translate>[[Special:MyLanguage/4_4_3:VMware_Single_File_Restore#mount|Mounting VMDK on a device server]]


Before starting a restore, check the supported file systems and restrictions.
Before starting a restore, check the supported file systems and restrictions.


===Supported file systems===
===Supported file systems===
SEP sesam can in general recover '''all file systems''' as long as the '''respective operating system''' offers <u>read/write support</u> for it.


* Example 1: A restore of files from ReFS on Windows is only possible if the data mover is able to read the ReFS file system which is supported since Windows Server 2012.
SEP sesam can in general recover '''all file systems''' as long as the '''respective operating system''' offers <u>read/write support</u> for it.</translate>
* Example 2: A restore of files from a Btrfs is only possible if the data mover is a Linux with Kernel support for it, for example SLES 12.
* Example 3: If the file system on OES Linux is NSS, the data mover must be able to read the NSS file system data.


When '''restoring files from the NSS file system''' some '''limitations''' apply:
* <translate>Example 1: A restore of files from ReFS on Windows is only possible if the data mover is able to read the ReFS file system which is supported since Windows Server 2012.</translate>
* The restore process itself does not differ from the restore of native Linux or Windows files, but the proxy VM must be an OES11 Server. For prerequisites, check [[Special:MyLanguage/4_4_3:VMware_Single_File_Restore#Recommendations for Linux proxy|Recommendations for Linux proxy]].
* <translate>Example 2: A restore of files from a Btrfs is only possible if the data mover is a Linux with Kernel support for it, for example SLES 12.</translate>
* Files from a native NetWare VM can be restored only to an OES Linux or native Linux target.
* <translate>Example 3: If the file system on OES Linux is NSS, the data mover must be able to read the NSS file system data.
*To restore trustees, the extended attributes on NSS must be enabled before backup. For details, refer to ''Novell OES documentation for NSS''.
*If you restore NSS files to a server in the original tree and on an NSS file system, the restored files will keep the original trustees (regardless of the tree of the proxy OES VM you used for restore).
* Trustees from native NetWare VMs cannot be restored because native NetWare has no extended attributes to store the trustees into the file system.


===Restrictions===
When '''restoring files from the NSS file system''' some '''limitations''' apply:</translate>
*SEP sesam does not support a restore of files from the DOS boot partition of a native NetWare server.
* <translate>The restore process itself does not differ from the restore of native Linux or Windows files, but the proxy VM must be an OES11 Server. For prerequisites, check [[Special:MyLanguage/4_4_3:VMware_Single_File_Restore#Recommendations for Linux proxy|Recommendations for Linux proxy]].</translate>
*SEP sesam provides limited support for single file restore on Windows virtual machines with spanned volumes due to Microsoft's restrictions. The following limitations exist:
* <translate>Files from a native NetWare VM can be restored only to an OES Linux or native Linux target.</translate>
**[[Special:MyLanguage/4_4_3:VMware_Single_File_Restore#mount|Mounting VMDK]] to a SEP sesam Server/RDS is not supported.
*<translate>To restore trustees, the extended attributes on NSS must be enabled before backup. For details, refer to ''Novell OES documentation for NSS''.</translate>
**[[Special:MyLanguage/4_4_3:VMware_Single_File_Restore#attach|Attaching VMDK]] to original virtual machine is not supported if the original disks are still attached (as is typically the case in most scenarios).
*<translate>If you restore NSS files to a server in the original tree and on an NSS file system, the restored files will keep the original trustees (regardless of the tree of the proxy OES VM you used for restore).</translate>
*The attach method does not work with a virtual SEP sesam Server or a virtual RDS to itself. For example, a virtual SEP sesam Server stores the virtual disk(s) on the SEP sesam data store. It is not possible to attach VMDK to the respective virtual SEP sesam Server; another VM must be used for this.
* <translate>Trustees from native NetWare VMs cannot be restored because native NetWare has no extended attributes to store the trustees into the file system.
 
===Restrictions===</translate>
*<translate>SEP sesam does not support a restore of files from the DOS boot partition of a native NetWare server.</translate>
*<translate>SEP sesam provides limited support for single file restore on Windows virtual machines with spanned volumes due to Microsoft's restrictions. The following limitations exist:</translate>
**<translate>[[Special:MyLanguage/4_4_3:VMware_Single_File_Restore#mount|Mounting VMDK]] to a SEP sesam Server/RDS is not supported.</translate>
**<translate>[[Special:MyLanguage/4_4_3:VMware_Single_File_Restore#attach|Attaching VMDK]] to original virtual machine is not supported if the original disks are still attached (as is typically the case in most scenarios).</translate>
*<translate>The attach method does not work with a virtual SEP sesam Server or a virtual RDS to itself. For example, a virtual SEP sesam Server stores the virtual disk(s) on the SEP sesam data store. It is not possible to attach VMDK to the respective virtual SEP sesam Server; another VM must be used for this.


==={{anchor|best_practice}}Best practice for individual file restore for Windows and Linux VMs===
==={{anchor|best_practice}}Best practice for individual file restore for Windows and Linux VMs===
SEP sesam provides simple restore of individual files without any special backup preparation from VMware CBT snapshot. The following steps represent best practices and latest recommendations from SEP sesam support. Detailed instructions on VMware requirements and backup configuration can be found in related articles [[Special:MyLanguage/4_4_3:VMware_Requirements_%26_Restrictions|VMware Requirements & Restrictions]] and [[Special:MyLanguage/4_4_3:VMware_Backup|VMware Backup]]. 
<ul><li>For version 4.4.3, the following limitation applies: Windows SEP sesam Server or Windows RDS is not supported in v. 4.4.3, therefore use Linux SEP sesam Server or RDS. In case of v. 4.4.3 ''Tigon'', Windows can be used as a SEP sesam Server or RDS.</li>
<li>Enable the NFS server on the SEP sesam Server or RDS as described in section [[Special:MyLanguage/4_4_3:VMware_Single_File_Restore#NFS|Preparing the NFS share]].</li>
<li>Install SEP sesam Client to a Linux VM (sandbox for Linux single file restore). VDDK is only required if this VM is also the data mover. In this case, check [[Special:MyLanguage/4_4_3:VMware_Requirements_%26_Restrictions|VMware Requirements & Restrictions]].</li>
<li>Add the Linux VM as a client as described in [[Special:MyLanguage/4_4_3:VMware_Single_File_Restore#client|Step 1: Configuring a virtual host as a SEP sesam client]]. Make sure that you select the check box '''Client is a virtual machine'''.</li>
{{note|
*Any operating system can be used except in case that you need a sandbox for Netware single file restore. Search the wiki for Netware reference.
*Do not use a productive system as a sandbox!}}
<li>Install SEP sesam Client to a Windows VM (sandbox for Windows single file restore). No specific Windows version is required. VDDK is only required if this VM is also the data mover. In this case, check [[Special:MyLanguage/4_4_3:VMware_Requirements_%26_Restrictions|VMware Requirements & Restrictions]].</li>
<li>Add the Windows VM as a client as described in [[Special:MyLanguage/4_4_3:VMware_Single_File_Restore#client|Step 1: Configuring a virtual host as a SEP sesam client]]. Make sure that you select the check box '''Client is a virtual machine'''.</li>
<li>Follow [[Special:MyLanguage/4_4_3:VMware_Single_File_Restore#restore|Step 3: Restore a VM using the attached VMDK
]]: Select the VMware snapshot and select the check box '''Attach virtual disk(s) (VMDK) to a Proxy-VM via NFS server'''. Then click Next and under ''Select VM'' use the drop-down list to select Linux or Windows sandbox VM.</li></ul>


=={{anchor|attach}}Attaching VMDK to a virtual machine==
SEP sesam provides simple restore of individual files without any special backup preparation from VMware CBT snapshot. The following steps represent best practices and latest recommendations from SEP sesam support. Detailed instructions on VMware requirements and backup configuration can be found in related articles [[Special:MyLanguage/4_4_3:VMware_Requirements_%26_Restrictions|VMware Requirements & Restrictions]] and [[Special:MyLanguage/4_4_3:VMware_Backup|VMware Backup]].</translate> 
Attaching VMDK to a virtual machine is the '''recommended option for single file restore''' for Windows and Linux that requires only one SEP sesam Server or Remote Device Server (RDS).
<ul><li><translate>For version 4.4.3, the following limitation applies: Windows SEP sesam Server or Windows RDS is not supported in v. 4.4.3, therefore use Linux SEP sesam Server or RDS. In case of v. 4.4.3 ''Tigon'', Windows can be used as a SEP sesam Server or RDS.</translate></li>
{{note|SEP sesam provides limited support for single file restore on Windows virtual machines with spanned volumes due to Microsoft's restrictions. Attaching VMDK to the original virtual machine is not supported if the original disks are still attached. You can only attach VMDK to another Windows host, because Microsoft does not allow to use the same volumes twice when having spanned volumes. Then the disks will be marked as ''Foreign'' in Disk Management. Only possible workaround is to bring these disks online manually using Disk Management. For details, see section [[Special:MyLanguage/4_4_3:VMware_Single_File_Restore#manage_VMs|Managing virtual machines with spanned volumes]].}}
<li><translate>Enable the NFS server on the SEP sesam Server or RDS as described in section [[Special:MyLanguage/4_4_3:VMware_Single_File_Restore#NFS|Preparing the NFS share]].</translate></li>
<li><translate>Install SEP sesam Client to a Linux VM (sandbox for Linux single file restore). VDDK is only required if this VM is also the data mover. In this case, check [[Special:MyLanguage/4_4_3:VMware_Requirements_%26_Restrictions|VMware Requirements & Restrictions]].</translate></li>
<li><translate>Add the Linux VM as a client as described in [[Special:MyLanguage/4_4_3:VMware_Single_File_Restore#client|Step 1: Configuring a virtual host as a SEP sesam client]]. Make sure that you select the check box '''Client is a virtual machine'''.</translate></li>
{{<translate>note</translate>|
*<translate>Any operating system can be used except in case that you need a sandbox for Netware single file restore. Search the wiki for Netware reference.</translate>
*<translate>Do not use a productive system as a sandbox!</translate>}}
<li><translate>Install SEP sesam Client to a Windows VM (sandbox for Windows single file restore). No specific Windows version is required. VDDK is only required if this VM is also the data mover. In this case, check [[Special:MyLanguage/4_4_3:VMware_Requirements_%26_Restrictions|VMware Requirements & Restrictions]].</translate></li>
<li><translate>Add the Windows VM as a client as described in [[Special:MyLanguage/4_4_3:VMware_Single_File_Restore#client|Step 1: Configuring a virtual host as a SEP sesam client]]. Make sure that you select the check box '''Client is a virtual machine'''.</translate></li>
<li><translate>Follow [[Special:MyLanguage/4_4_3:VMware_Single_File_Restore#restore|Step 3: Restore a VM using the attached VMDK
]]: Select the VMware snapshot and select the check box '''Attach virtual disk(s) (VMDK) to a Proxy-VM via NFS server'''. Then click Next and under ''Select VM'' use the drop-down list to select Linux or Windows sandbox VM.</translate></li></ul>
 
<translate>=={{anchor|attach}}Attaching VMDK to a virtual machine==
 
Attaching VMDK to a virtual machine is the '''recommended option for single file restore''' for Windows and Linux that requires only one SEP sesam Server or Remote Device Server (RDS).</translate>
{{<translate>note</translate>|<translate>SEP sesam provides limited support for single file restore on Windows virtual machines with spanned volumes due to Microsoft's restrictions. Attaching VMDK to the original virtual machine is not supported if the original disks are still attached. You can only attach VMDK to another Windows host, because Microsoft does not allow to use the same volumes twice when having spanned volumes. Then the disks will be marked as ''Foreign'' in Disk Management. Only possible workaround is to bring these disks online manually using Disk Management. For details, see section [[Special:MyLanguage/4_4_3:VMware_Single_File_Restore#manage_VMs|Managing virtual machines with spanned volumes]].</translate>}}


''Conceptual view of a single item restore with the attached VMDK''
<translate>''Conceptual view of a single item restore with the attached VMDK''</translate><br />
[[File:SEP sesam instant-recovery and single-file-restore 04 attach 03.png|link=]]
<translate>[[File:SEP sesam instant-recovery and single-file-restore 04 attach 03.png|link=]]</translate>
<br clear=all>
<br clear=all>
===Prerequisites===
<translate>===Prerequisites===
 
Before attempting to attach VMDK and performing a single file restore, all preparation steps have to be performed properly, including configuration and VM backup. Depending on your SEP sesam version, see the relevant [[Special:MyLanguage/VMware|VMware guide]] for details.  
Before attempting to attach VMDK and performing a single file restore, all preparation steps have to be performed properly, including configuration and VM backup. Depending on your SEP sesam version, see the relevant [[Special:MyLanguage/VMware|VMware guide]] for details.  


The VMware single file restore prerequisites differ slightly depending on your SEP sesam version. For example, 4.4.3 ''Tigon'' already supports all backup levels and provides selective restore.
The VMware single file restore prerequisites differ slightly depending on your SEP sesam version. For example, 4.4.3 ''Tigon'' already supports all backup levels and provides selective restore.
Make sure that the following conditions are met:
Make sure that the following conditions are met:</translate>
* SEP sesam Server version ≥ 4.4.3. For the list of supported systems, see [[SEP sesam OS and Database Support Matrix]].
* <translate>SEP sesam Server version ≥ 4.4.3. For the list of supported systems, see [[SEP sesam OS and Database Support Matrix]].</translate>
* A SEP sesam [[Special:MyLanguage/SEP_sesam_Glossary#data_store|data store]] ''Path'' or SEP sesam ''Si3'' data store:  
* <translate>A SEP sesam [[Special:MyLanguage/SEP_sesam_Glossary#data_store|data store]] ''Path'' or SEP sesam ''Si3'' data store:</translate>
** SEP sesam v. 4.4.3 ''Tigon'' supports the UNC path (e.g., <tt>\\server\folder</tt>) for data store.
** <translate>SEP sesam v. 4.4.3 ''Tigon'' supports the UNC path (e.g., <tt>\\server\folder</tt>) for data store.</translate>
** In SEP sesam v. 4.4.3, data store via UNC path is not supported. A volume must be visible as a locally attached storage (not as a network drive letter). Only iSCSI, SAN and locally connected drives can be used as a locally attached storage.
** <translate>In SEP sesam v. 4.4.3, data store via UNC path is not supported. A volume must be visible as a locally attached storage (not as a network drive letter). Only iSCSI, SAN and locally connected drives can be used as a locally attached storage.</translate>
* Backups must not be [[Special:MyLanguage/SEP_sesam_Glossary#encryption|encrypted]] or [[Special:MyLanguage/SEP_sesam_Glossary#compression|compressed]], and they must not be migrated to another media – only the original backup on SEP sesam data store can be used for restore.
* <translate>Backups must not be [[Special:MyLanguage/SEP_sesam_Glossary#encryption|encrypted]] or [[Special:MyLanguage/SEP_sesam_Glossary#compression|compressed]], and they must not be migrated to another media – only the original backup on SEP sesam data store can be used for restore.</translate>
* At least one virtual host of VMware vCenter needs to be added as a SEP sesam Client ≥ 4.4.3 to attach VMDKs.
* <translate>At least one virtual host of VMware vCenter needs to be added as a SEP sesam Client ≥ 4.4.3 to attach VMDKs.</translate>
* Encrypted file systems within the virtual machine can only be read if the system (proxy VM) with the attached virtual disk is able to decrypt the data.
* <translate>Encrypted file systems within the virtual machine can only be read if the system (proxy VM) with the attached virtual disk is able to decrypt the data.</translate>
* The system that stores the VMDK files to SEP sesam data store (either SEP sesam Server or SEP sesam RDS) must provide NFS (network file system) services:  
* <translate>The system that stores the VMDK files to SEP sesam data store (either SEP sesam Server or SEP sesam RDS) must provide NFS (network file system) services:</translate>
**V. 4.4.3 ''Tigon'' already includes the NFS server and does not require a regular NFS server provided by Windows.
**<translate>V. 4.4.3 ''Tigon'' already includes the NFS server and does not require a regular NFS server provided by Windows.</translate>
** For SEP sesam v. 4.4.3 with the NFS service on Windows, it is recommended to use Windows 2012 (R2) for providing a higher level of NFS support.
** <translate>For SEP sesam v. 4.4.3 with the NFS service on Windows, it is recommended to use Windows 2012 (R2) for providing a higher level of NFS support.</translate>
*A proxy server (either Windows or Linux VM) should be a non-production environment. For more details, see [[Special:MyLanguage/4_4_3:VMware_Single_File_Restore#Recommendations for Linux proxy|Recommendations for Linux proxy]] below.
*<translate>A proxy server (either Windows or Linux VM) should be a non-production environment. For more details, see [[Special:MyLanguage/4_4_3:VMware_Single_File_Restore#Recommendations for Linux proxy|Recommendations for Linux proxy]] below.</translate>
*When using both, virtual Linux and Windows hosts, it is recommended to add one virtual Linux and one virtual Windows host to ensure file system compatibility.
*<translate>When using both, virtual Linux and Windows hosts, it is recommended to add one virtual Linux and one virtual Windows host to ensure file system compatibility.</translate>
*Some versions, for example, VDDK 6.5.x on Windows, might require rebooting the host after the update, followed by running the <tt>vstor2install.bat script</tt>. For details, see [[Special:MyLanguage/4_4_3:VMware_Single_File_Restore#VMDK|troubleshooting section below]].  
*<translate>Some versions, for example, VDDK 6.5.x on Windows, might require rebooting the host after the update, followed by running the <tt>vstor2install.bat script</tt>. For details, see [[Special:MyLanguage/4_4_3:VMware_Single_File_Restore#VMDK|troubleshooting section below]].</translate>
{{note|
{{<translate>note</translate>|
SEP sesam can restore all file systems for which the respective operating system provides a read/write support. For example, a restore of files on Windows ReFS is only possible if the system with the attached disk is able to read ReFS data. Or, if the file system on OES Linux is NSS, the system with the attached disk must be able to read the NSS file system data.}}
<translate>SEP sesam can restore all file systems for which the respective operating system provides a read/write support. For example, a restore of files on Windows ReFS is only possible if the system with the attached disk is able to read ReFS data. Or, if the file system on OES Linux is NSS, the system with the attached disk must be able to read the NSS file system data.}}


==={{anchor|client}}Step 1: Configuring a virtual host as a SEP sesam client===
==={{anchor|client}}Step 1: Configuring a virtual host as a SEP sesam client===


To be able to attach a VMDK file to a virtual host, SEP sesam needs to know where to attach the VMDK file(s). You have to add at least one virtual host as a SEP sesam client and this system must be assigned to the virtual host.
To be able to attach a VMDK file to a virtual host, SEP sesam needs to know where to attach the VMDK file(s). You have to add at least one virtual host as a SEP sesam client and this system must be assigned to the virtual host.</translate>
<ol><li>From '''Main Selection -> Components -> Topology''', select your location and click the '''New client''' button. The ''New client'' window opens.</li>
<ol><li><translate>From '''Main Selection -> Components -> Topology''', select your location and click the '''New client''' button. The ''New client'' window opens.</translate></li>
<li>In the ''New client'' window, configure the following options:
<li><translate>In the ''New client'' window, configure the following options:</translate>
<ul><li>Enter the name of the virtual host in the '''Client name''' field.</li>
<ul><li><translate>Enter the name of the virtual host in the '''Client name''' field.</translate></li>
<li>Select the relevant platform from the '''Platform''' drop-down list and the relevant OS under '''Operating system'''.</li>
<li><translate>Select the relevant platform from the '''Platform''' drop-down list and the relevant OS under '''Operating system'''.</translate></li>
<li>Choose the '''Access mode''' (SMSSH) for the SEP sesam server-client communication (the default setting is ''CTRL'').</li>
<li><translate>Choose the '''Access mode''' (SMSSH) for the SEP sesam server-client communication (the default setting is ''CTRL'').</translate></li>
<li>On the left, under the ''SBC Version info'', select the check box '''Client is a virtual machine'''.</li>
<li><translate>On the left, under the ''SBC Version info'', select the check box '''Client is a virtual machine'''.</translate></li>
<li>From the drop-down list on the right,select the name of your vCenter under '''VM host'''.</li>
<li><translate>From the drop-down list on the right,select the name of your vCenter under '''VM host'''.</translate></li>
<li>Then select the virtual machine from the '''VM name''' list and click '''Create'''.</li></ul></li>
<li><translate>Then select the virtual machine from the '''VM name''' list and click '''Create'''.</translate></li></ul></li>
[[image:add_client_VH.png|600px|link=]]
<translate>[[image:add_client_VH.png|600px|link=]]</translate>
<br clear=all></ol>
<br clear=all></ol>
Your new client is displayed in the ''Topology'' content pane.
<translate>Your new client is displayed in the ''Topology'' content pane.


==={{anchor|NFS}}Step 2: Preparing the NFS share on Linux===
==={{anchor|NFS}}Step 2: Preparing the NFS share on Linux===
NFS (Network File System) is a client/server application that allows to share files across a network. You have to set up the NFS service on the Linux SEP sesam Server or RDS system, which stores the VMDK files.  
NFS (Network File System) is a client/server application that allows to share files across a network. You have to set up the NFS service on the Linux SEP sesam Server or RDS system, which stores the VMDK files.</translate>
<!--
<!--
The procedure for creating a NFS share depends on your SEP sesam Server/RDS operating sytem:
The procedure for creating a NFS share depends on your SEP sesam Server/RDS operating sytem:
*[[Special:MyLanguage/4_4_3:VMware_Single_File_Restore#NFS on Windows|NFS on Windows]]
*[[Special:MyLanguage/4_4_3:VMware_Single_File_Restore#NFS on Windows|NFS on Windows]]
*[[Special:MyLanguage/4_4_3:VMware_Single_File_Restore#NFS on Linux|NFS on Linux]]
*[[Special:MyLanguage/4_4_3:VMware_Single_File_Restore#NFS on Linux|NFS on Linux]]
====NFS on Windows====
<translate>====NFS on Windows====
SEP '''recommends using Windows 2012 (R2)''' for providing a higher level of NFS support. SEP sesam creates the required NFS share on Windows 2012 automatically (if the NFS share is not added, follow the procedure below to add it manually). '''On Windows 2008(R2), you have to set up the NFS share manually''':
 
<ol><li>Login to your SEP sesam Server or RDS which stores the VMDK files and for which you want to configure the NFS share.</li>
SEP '''recommends using Windows 2012 (R2)''' for providing a higher level of NFS support. SEP sesam creates the required NFS share on Windows 2012 automatically (if the NFS share is not added, follow the procedure below to add it manually). '''On Windows 2008(R2), you have to set up the NFS share manually''':</translate>
<li>To install server for NFS services, execute the following command as administrator via ''Powershell version 2'' at {{Sesamroot|\bin\sesam}}: <tt>sm_installnfs.ps1</tt>. The installation starts automatically.</li>
<ol><li><translate>Login to your SEP sesam Server or RDS which stores the VMDK files and for which you want to configure the NFS share.</translate></li>
<li>Create the NFS share by using ''Server Manager'': Log on your SEP sesam Server or RDS as a member of the local Administrators group. Use Start menu to start ''servermanager.exe'' if it does not start automatically. Then click '''File Services''' ->  '''Share and Storage Management''' -> '''Provision Share''', and specify the following:
<li><translate>To install server for NFS services, execute the following command as administrator via ''Powershell version 2'' at {{Sesamroot|\bin\sesam}}: <tt>sm_installnfs.ps1</tt>. The installation starts automatically.</translate></li>
[[File:NFS_Server_share.jpg|700px|left|link=]]
<li><translate>Create the NFS share by using ''Server Manager'': Log on your SEP sesam Server or RDS as a member of the local Administrators group. Use Start menu to start ''servermanager.exe'' if it does not start automatically. Then click '''File Services''' ->  '''Share and Storage Management''' -> '''Provision Share''', and specify the following:</translate><br />
<translate>[[File:NFS_Server_share.jpg|700px|left|link=]]</translate>
<br clear=all>
<br clear=all>
<ul><li>'''Shared Folder Location''': Browse for the path where the SEP sesam data store is located.
<ul><li><translate>'''Shared Folder Location''': Browse for the path where the SEP sesam data store is located.</translate>
{{note|The path of the NFS share must be the same as the path of the SEP sesam data store and the name of the NFS share must be the same as the name of the SEP sesam data store where the VMDK files are stored.}}
{{<translate>note</translate>|<translate>The path of the NFS share must be the same as the path of the SEP sesam data store and the name of the NFS share must be the same as the name of the SEP sesam data store where the VMDK files are stored.}}
In our example, the name of the NFS share must be ''NFS-Store1'' and the path must be set to ''E:\nfs'' (see above data store screenshot). Click Next.</li>
In our example, the name of the NFS share must be ''NFS-Store1'' and the path must be set to ''E:\nfs'' (see above data store screenshot). Click '''Next'''.</translate></li>
<li>'''NTFS Permissions''': Leave default NTFS permissions. Click Next.</li>
<li><translate>'''NTFS Permissions''': Leave default NTFS permissions. Click '''Next'''.</translate></li>
<li>'''Share Protocols''': Select '''NFS''' and specify a name for the new share – the name of the SEP sesam data store, e.g. ''NFS-Store1''. Click Next.</li>
<li><translate>'''Share Protocols''': Select '''NFS''' and specify a name for the new share – the name of the SEP sesam data store, e.g. ''NFS-Store1''. Click '''Next'''.</translate></li>
<li>NFS Authentication: Leave default settings.</li>
<li><translate>NFS Authentication: Leave default settings.</translate></li>
<li>NFS Permissions: Change the ''Type of access'' to '''Read-Write''', and select the check box '''Allow root access'''. Click Next.</li>
<li><translate>NFS Permissions: Change the ''Type of access'' to '''Read-Write''', and select the check box '''Allow root access'''. Click '''Next'''.</translate></li>
<li>Confirmation: Review your configuration, and click '''Create''' to create the NFS file share.</li></ul></li>
<li><translate>Confirmation: Review your configuration, and click '''Create''' to create the NFS file share.</translate></li></ul></li>
<li>Once you created the share, right-click it and select '''Properties''', select the tab '''NFS Sharing''', and click on '''Manage NFS Sharing'''. In the '''NFS Advanced Sharing''' window, set the authentication for the NFS share: select option '''No server authentication''' with sub-option '''Enable unmapped user access''' and radio button '''Allow unmapped user access by UID/GID'''.</li>
<li><translate>Once you created the share, right-click it and select '''Properties''', select the tab '''NFS Sharing''', and click on '''Manage NFS Sharing'''. In the '''NFS Advanced Sharing''' window, set the authentication for the NFS share: select option '''No server authentication''' with sub-option '''Enable unmapped user access''' and radio button '''Allow unmapped user access by UID/GID'''.</translate></li>
[[Image:NFS_settings.jpg|left|link=]]
<translate>[[Image:NFS_settings.jpg|link=]]</translate>
<br clear=all>
<br clear=all>
<li>Then click the '''Permissions''' button to open the ''NFS Share Permission'' dialog. Check that the ''Type of access'' is set to '''Read-Write''', and that the check box '''Allow root access''' is enabled to give the root user Administrative privileges. You can set the share permissions for all machines or just for the vCenter server.</li></ol>
<li><translate>Then click the '''Permissions''' button to open the ''NFS Share Permission'' dialog. Check that the ''Type of access'' is set to '''Read-Write''', and that the check box '''Allow root access''' is enabled to give the root user Administrative privileges. You can set the share permissions for all machines or just for the vCenter server.</li></ol>
For more details on NFS configuration, see Microsoft article [https://technet.microsoft.com/en-us/library/dd758767(v=ws.10).aspx Services for NFS – Step-by-Step Guide for Windows Server 2008 R2].
For more details on NFS configuration, see Microsoft article [https://technet.microsoft.com/en-us/library/dd758767(v=ws.10).aspx Services for NFS – Step-by-Step Guide for Windows Server 2008 R2].


====NFS on Linux====-->
====NFS on Linux====-->
SEP sesam automatically creates a VMware data store to attach the VMDK file(s) to a virtual host.
 
[[Image:VSphere SF Datastore en.jpg|600px|link=]]
SEP sesam automatically creates a VMware data store to attach the VMDK file(s) to a virtual host.</translate><br />
<translate>[[Image:VSphere SF Datastore en.jpg|600px|link=]]</translate>
<br clear=all>
<br clear=all>


The following overview provides only basic information for configuring NFS on Linux. For details, see relevant Linux documentation, for example, the article [https://linuxconfig.org/how-to-configure-nfs-on-linux How to configure NFS on Linux].
<translate>The following overview provides only basic information for configuring NFS on Linux. For details, see relevant Linux documentation, for example, the article [https://linuxconfig.org/how-to-configure-nfs-on-linux How to configure NFS on Linux].</translate>
* NFS server must be installed and NFS service must run.  
* <translate>NFS server must be installed and NFS service must run.</translate>
* Exports will be created dynamically during restore by SEP sesam. Note that exports can also be created manually by editing the <tt>/etc/exports</tt> file. The exported path has to match the location of the SEP sesam data store or any of its parent directories on the same file system.
* <translate>Exports will be created dynamically during restore by SEP sesam. Note that exports can also be created manually by editing the <tt>/etc/exports</tt> file. The exported path has to match the location of the SEP sesam data store or any of its parent directories on the same file system.</translate>
* All ESX servers must be allowed to mount the directory.
* <translate>All ESX servers must be allowed to mount the directory.</translate>
* ''Read/write'' permission should be set.
* <translate>''Read/write'' permission should be set.


===Recommendations for Linux proxy===
===Recommendations for Linux proxy===


'''OES Linux proxy VM (for restore from NSS file systems)'''
'''OES Linux proxy VM (for restore from NSS file systems)'''</translate>
* <translate>VM with OES11 SP2 or higher</translate>
* <translate>OES pattern to install: NSS (all other dependencies will be selected automatically)</translate>
* <translate>Recommended to install the NetIQ eDirectory as a separate tree.</translate>
* <translate>Static IP address (required by NetIQ eDirectory).</translate>
* <translate>Only minimal system is required, X server is not required.</translate>
* <translate>Size of file system only for SLES11 SP3 + OES11 SP2 (or higher versions).</translate>
* <translate>Current SEP sesam client for SLES11.


* VM with OES11 SP2 or higher
'''OES Linux'''</translate>
* OES pattern to install: NSS (all other dependencies will be selected automatically)
* Recommended to install the NetIQ eDirectory as a separate tree.
* Static IP address (required by NetIQ eDirectory).
* Only minimal system is required, X server is not required.
* Size of file system only for SLES11 SP3 + OES11 SP2 (or higher versions).
* Current SEP sesam client for SLES11.


'''OES Linux'''
* <translate>Use a separate, non-production OES VM</translate>
* <translate>Install the NetIQ eDirectory as a separate tree.</translate>
* <translate>Do not add NSS pools and volumes to the OES server – all non-active pools are automatically avtivated and deactivated after restore</translate>
* <translate>Do not change the mounted NSS file systems – they are your backup!


*Use a separate, non-production OES VM
==={{anchor|restore_VM}}Step 3: Restore a VM using the attached VMDK===
* Install the NetIQ eDirectory as a separate tree.
* Do not add NSS pools and volumes to the OES server – all non-active pools are automatically avtivated and deactivated after restore
* Do not change the mounted NSS file systems – they are your backup!


==={{anchor|restore_VM}}Step 3: Restore a VM using the attached VMDK===
Create a new restore task for individual file(s) you want to restore.</translate>
Create a new restore task for individual file(s) you want to restore.
<ol><li><translate>From the SEP sesam GUI menu bar, select '''Activities''' -> '''Restore'''. The ''New restore task'' window opens.</translate></li>
<ol><li>From the SEP sesam GUI menu bar, select '''Activities -> Restore'''. The ''New restore task'' window opens.</li>
<li><translate>Select what you want to restore. You can search save sets by ''task name'' or by ''filename or path''.</translate>
<li>Select what you want to restore. You can search save sets by ''task name'' or by ''filename or path''.
* <translate>When searching by ''task name'', use the drop-down list of available tasks and select the one you want to restore from. This option is selected by default.</translate>
* When searching by ''task name'', use the drop-down list of available tasks and select the one you want to restore from. This option is selected by default.
* <translate>If you are searching by filename/path, select the option '''Filename or path in save set''' and enter your search expression in the search pattern field.</translate></li>
* If you are searching by filename/path, select the option '''Filename or path in save set''' and enter your search expression in the search pattern field.</li>
<li><translate>Under the '''Saved in period''' drop-down list, specify the time frame for which you want to conduct the search. Click '''Next'''.</translate></li>
<li>Under the '''Saved in period''' drop-down lists, specify the time frame for which you want to conduct the search. Click '''Next'''.</li>
<li><translate>The search results are displayed. From the list of save sets matching your query, select the version from which you want to restore an individual file. Then select the check box '''Attach virtual disk(s) (VMDK) to a Proxy-VM via NFS server'''. Click '''Next'''.</translate></li>
<li>The search results are displayed. From the list of save sets matching your query, select the version from which you want to restore an individual file. Then select the check box '''Attach virtual disk(s) (VMDK) to a Proxy-VM via NFS server'''. Click '''Next'''.</li>
<translate>[[Image:VSphere SF attach mount 4.4 en.jpg|600px|link=]]</translate>
[[Image:VSphere SF attach mount 4.4 en.jpg|600px|link=]]
<br clear=all>
<br clear=all>
<li>Under the ''Select VM'', use the drop-down list to select the relevant '''vSphere server''', '''Sesam client name of the proxy VM''' and '''vSphere internal name of proxy VM'''. The vSphere server is the vCenter where the virtual host  – vSphere internal name of proxy VM – is running, which is assigned as a SEP sesam Client – Sesam client name of the proxy VM. If the host that attaches the disk(s) uses multiple network cards, you must also specify '''NFS interface'''; otherwise this option does not need to be specified. Click '''Next'''.</li>
<li><translate>Under the ''Select VM'', use the drop-down list to select the relevant '''vSphere server''', '''Sesam client name of the proxy VM''' and '''vSphere internal name of proxy VM'''. The vSphere server is the vCenter where the virtual host  – vSphere internal name of proxy VM – is running, which is assigned as a SEP sesam Client – Sesam client name of the proxy VM. If the host that attaches the disk(s) uses multiple network cards, you must also specify '''NFS interface'''; otherwise this option does not need to be specified. Click '''Next'''.</translate></li>
[[Image:VSphere SF select vm 4.4 en.jpg|600px|link=]]
<translate>[[Image:VSphere SF select vm 4.4 en.jpg|600px|link=]]</translate>
<br clear=all>
<br clear=all>
<li>On the page '''Select Files'''  only the drives of the chosen VMDK(s) are shown. Note that it might take form 5 to 20 seconds to load the drive list. SEP sesam automatically enables the automount function of Windows on host, which attaches the VMDK(s). The automount function of Windows assigns a drive letter to a new disk drive without interaction of a user. SEP sesam automatically sets all connected drives on this particular host to '''Online'''. <br />
<li<translate>>On the page '''Select Files'''  only the drives of the chosen VMDK(s) are shown. Note that it might take form 5 to 20 seconds to load the drive list. SEP sesam automatically enables the automount function of Windows on host, which attaches the VMDK(s). The automount function of Windows assigns a drive letter to a new disk drive without interaction of a user. SEP sesam automatically sets all connected drives on this particular host to '''Online'''.</translate> <br />
If no drives are shown, either an invalid partition was chosen (for example, if a Windows host tries to attach Linux partitions) or the drives did not start in expected time. You can use the refresh button (on the right side of the table) to display the list of all drives, local and the attached ones. Click '''Next'''.</li>
<translate>If no drives are shown, either an invalid partition was chosen (for example, if a Windows host tries to attach Linux partitions) or the drives did not start in expected time. You can use the refresh button (on the right side of the table) to display the list of all drives, local and the attached ones. Click '''Next'''.</translate></li>
[[Image:VSphere SF list drives en.jpg|600px|link=]]
<translate>[[Image:VSphere SF list drives en.jpg|600px|link=]]</translate>
<br clear=all>
<br clear=all>
<li>On the last '''Save and Start''' page of the restore wizard, you only need to select the client and the destination.</li>
<li><translate>On the last '''Save and Start''' page of the restore wizard, you only need to select the client and the destination.</translate></li>
[[Image:VSphere SF restore options en.jpg|600px|link=]]
<translate>[[Image:VSphere SF restore options en.jpg|600px|link=]]</translate>
<br clear=all>
<br clear=all>
<li>You can start your VM restore immediately by clicking '''Start'''. If you want to save the restore task, click '''Save'''. </li></ol>
<li><translate>You can start your VM restore immediately by clicking '''Start'''. If you want to save the restore task, click '''Save'''.</translate> </li></ol>


You can view the status of your restore jobs by selecting '''Job state''' -> '''Restore''' from the ''Main selection''. Restore overview provides detailed information on the last run of restore jobs, including the task name, status (successful, error, in queue ...), start and stop time of the last backup, data size, throughput, client and message.
<translate>You can view the status of your restore jobs by selecting '''Job state''' -> '''Restore''' from the ''Main selection''. Restore overview provides detailed information on the last run of restore jobs, including the task name, status (successful, error, in queue ...), start and stop time of the last backup, data size, throughput, client and message.


==={{anchor|manage_VMs}}Managing virtual machines with spanned volumes===
==={{anchor|manage_VMs}}Managing virtual machines with spanned volumes===
Line 203: Line 211:
You can only attach VMDK to another Windows host, because Microsoft does not allow to use the same volumes twice when having spanned volumes. Then the disks will be marked as ''Foreign'' in Disk Management. Only possible workaround is to bring these disks online manually using Disk Management.
You can only attach VMDK to another Windows host, because Microsoft does not allow to use the same volumes twice when having spanned volumes. Then the disks will be marked as ''Foreign'' in Disk Management. Only possible workaround is to bring these disks online manually using Disk Management.


====Steps====
====Steps====</translate>
<ol><li>Open '''Computer Management''' -> '''Disk Management''', and click '''Import Foreign Disks''' option. This lists one or more disk groups, identified by the name of the computer where they were created. If you expand the details on a disk group, it lists the locally-connected disks.</li>
<ol><li><translate>Open '''Computer Management''' -> '''Disk Management''', and click '''Import Foreign Disks''' option. This lists one or more disk groups, identified by the name of the computer where they were created. If you expand the details on a disk group, it lists the locally-connected disks.</translate></li>
<li>Select the relevant ''Disk Group''. The dialog box with a list of volumes in the Disk Group opens.</li>
<li><translate>Select the relevant ''Disk Group''. The dialog box with a list of volumes in the Disk Group opens.</translate></li>
<li>Select the relevant volumes and click '''OK''' to add the foreign disks to your system configuration.
<li><translate>Select the relevant volumes and click '''OK''' to add the foreign disks to your system configuration.</translate>
</ol>
</ol>
The operation is slightly different, depending on whether there are pre-existing online foreign (dynamic) disks on the target computer. For details, see [https://support.microsoft.com/en-us/help/222189/description-of-disk-groups-in-windows-disk-management Microsoft support article Description of Disk Groups in Windows Disk Management].
<translate>The operation is slightly different, depending on whether there are pre-existing online foreign (dynamic) disks on the target computer. For details, see [https://support.microsoft.com/en-us/help/222189/description-of-disk-groups-in-windows-disk-management Microsoft support article Description of Disk Groups in Windows Disk Management].


=={{anchor|mount}}Mounting VMDK to a SEP sesam RDS==
=={{anchor|mount}}Mounting VMDK to a SEP sesam RDS==
You can mount any non-compressed VMDK save set stored to ''default data store Path'' or to ''Si3 data store'' to the local system, which is used as a [[Special:MyLanguage/4_4_3:VMware_Requirements_%26_Restrictions#data_mover|VMware data mover]] and SEP sesam [[Special:MyLanguage/SEP_sesam_Glossary#RDS|RDS]] with a [[Special:MyLanguage/SEP_sesam_Glossary#data_store|data store]]. The target VMDK is mounted to the SEP sesam home directory <code>var\tmp\mnt</code>, e.g., <code>C:\Program Files\SEPsesam\var\tmp\mnt\''save_set_ID''</code>. This way the VMDK is instantly accessible for browsing and searching before the actual restore is even triggered, providing you with quick access to your data. The mounted VMDK is basically a '''virtual read-only file system''', therefore it cannot be altered or otherwise damaged. Comparing to the ''attach'' method, mounting has the advantage of much easier setup and requires less configuration steps.


{{note|
You can mount any non-compressed VMDK save set stored to ''default data store Path'' or to ''Si3 data store'' to the local system, which is used as a [[Special:MyLanguage/4_4_3:VMware_Requirements_%26_Restrictions#data_mover|VMware data mover]] and SEP sesam [[Special:MyLanguage/SEP_sesam_Glossary#RDS|RDS]] with a [[Special:MyLanguage/SEP_sesam_Glossary#data_store|data store]].
*Mounting is not possible if the save sets are stored to tapes or if the save sets are compressed.  
 
*Mounting is not supported on Windows virtual machines with spanned volumes due to Microsoft's restriction.}}
The target VMDK is mounted to the SEP sesam home directory <code>var\tmp\mnt</code>, e.g., <code>C:\Program Files\SEPsesam\var\tmp\mnt\''save_set_ID''</code>. This way the VMDK is instantly accessible for browsing and searching before the actual restore is even triggered, providing you with quick access to your data. The mounted VMDK is basically a '''virtual read-only file system''', therefore it cannot be altered or otherwise damaged. Comparing to the ''attach'' method, mounting has the advantage of much easier setup and requires less configuration steps.</translate>
 
{{<translate>note</translate>|
*<translate>Mounting is not possible if the save sets are stored to tapes or if the save sets are compressed.</translate>
*<translate>Mounting is not supported on Windows virtual machines with spanned volumes due to Microsoft's restriction.</translate>}}


''Conceptual view of a single item restore with mounted VMDK''
<translate>''Conceptual view of a single item restore with mounted VMDK''</translate><br />
[[File:SEP sesam instant-recovery and single-file-restore 03 mount 03.png|link=]]
<translate>[[File:SEP sesam instant-recovery and single-file-restore 03 mount 03.png|link=]]</translate>
<br clear=all>
<br clear=all>
===Prerequisites===
<translate>===Prerequisites===
Before attempting to mount VMDK and performing a single file restore, all preparation steps have to be performed properly, including configuration and VM backup. Depending on your SEP sesam version, see the relevant [[Special:MyLanguage/VMware|VMware guide]] for details. Make sure that the following conditions are met:
* SEP sesam Server version ≥ 4.4.3. For the list of supported systems, see [[SEP sesam OS and Database Support Matrix]].
* A SEP sesam [[Special:MyLanguage/SEP_sesam_Glossary#data_store|data store]] ''Path'' or SEP sesam ''Si3'' data store:
** SEP sesam v. 4.4.3 ''Tigon'' supports the UNC path (e.g., <tt>\\server\folder</tt>) for data store.
** In SEP sesam v. 4.4.3, data store via UNC path is not supported. A volume must be visible as a locally attached storage (not as a network drive letter). Only iSCSI, SAN and locally connected drives can be used as a locally attached storage.
* Backups must not be [[Special:MyLanguage/SEP_sesam_Glossary#encryption|'''encrypted''']] or [[Special:MyLanguage/SEP_sesam_Glossary#compression|'''compressed''']], and they must not be migrated to another media – only the original backup on SEP sesam data store can be used for restore.
* VDDK 5.5.x must be installed on the system, which is used as a VMware data mover and SEP sesam RDS with a data store. On Windows, VDDK is a part of the SEP sesam installation. SEP sesam version 4.4.3 is using VDDK version 6. If you are using a Linux system or any of the previous SEP sesam versions, you have to install the VDDK manually. For details, see [[Special:MyLanguage/Installing_VDDK#Linux|Installing VDDK on Linux]].
* When using a Linux data mover to mount the VMDK, it must be able to read Linux and Windows systems. Note that mounting Windows VMDKs with Linux data mover might result in ACL-related problems and is therefore not recommended.
*When using a Windows data mover to mount the VMDK, it is required to have a second data mover on Linux with installed VDDK 5.5.x which is also a SEP sesam RDS. Virtual Windows hosts must be stored on Windows RDS and Linux virtual hosts must be stored on Linux RDS.
{{note|
SEP sesam can restore all file systems for which the respective operating system provides a read/write support. For example, a restore of files on Windows ReFS is only possible if the data mover is able to read ReFS data. Or, if the file system on OES Linux is NSS, the data mover must be able to read the NSS file system data.}}


==={{anchor|restore}}Restore a single file using the mounted VMDK===
Before attempting to mount VMDK and performing a single file restore, all preparation steps have to be performed properly, including configuration and VM backup. Depending on your SEP sesam version, see the relevant [[Special:MyLanguage/VMware|VMware guide]] for details. Make sure that the following conditions are met:</translate>
Create a new restore task for individual file(s) you want to restore.
* <translate>SEP sesam Server version ≥ 4.4.3. For the list of supported systems, see [[SEP sesam OS and Database Support Matrix]].</translate>
<ol><li>From the SEP sesam GUI menu bar, select '''Activities -> Restore'''. The ''New restore task'' window opens.</li>
* <translate>A SEP sesam [[Special:MyLanguage/SEP_sesam_Glossary#data_store|data store]] ''Path'' or SEP sesam ''Si3'' data store:</translate>
<li>Select what you want to restore. You can search save sets by ''task name'' or by ''filename or path''.
** <translate>SEP sesam v. 4.4.3 ''Tigon'' supports the UNC path (e.g., <tt>\\server\folder</tt>) for data store.</translate>
* When searching by ''task name'', use the drop-down list of available tasks and select the one you want to restore from. This option is selected by default.
** <translate>In SEP sesam v. 4.4.3, data store via UNC path is not supported. A volume must be visible as a locally attached storage (not as a network drive letter). Only iSCSI, SAN and locally connected drives can be used as a locally attached storage.</translate>
* If you are searching by filename/path, select the option '''Filename or path in save set''' and enter your search expression in the search pattern field.</li>
* <translate>Backups must not be [[Special:MyLanguage/SEP_sesam_Glossary#encryption|'''encrypted''']] or [[Special:MyLanguage/SEP_sesam_Glossary#compression|'''compressed''']], and they must not be migrated to another media – only the original backup on SEP sesam data store can be used for restore.</translate>
<li>Under the '''Saved in period''' drop-down lists, specify the time frame for which you want to conduct the search. Click '''Next'''.</li>
* <translate>VDDK 5.5.x must be installed on the system, which is used as a VMware data mover and SEP sesam RDS with a data store. On Windows, VDDK is a part of the SEP sesam installation. SEP sesam version 4.4.3 is using VDDK version 6. If you are using a Linux system or any of the previous SEP sesam versions, you have to install the VDDK manually. For details, see [[Special:MyLanguage/Installing_VDDK#Linux|Installing VDDK on Linux]].</translate>
<li>The search results are displayed. From the list of save sets matching your query, select the version from which you want to restore an individual file. Then select the check box '''Mount virtual disk(s) via VMware API'''. A mount action is triggered and your VMDK is mounted to the SEP sesam home directory <tt>var\tmp\mnt</tt>, e.g., <tt>C:\Program Files\SEPsesam\var\tmp\mnt\''save_set_ID''</tt>. Click '''Next'''.</li>
* <translate>When using a Linux data mover to mount the VMDK, it must be able to read Linux and Windows systems. Note that mounting Windows VMDKs with Linux data mover might result in ACL-related problems and is therefore not recommended.</translate>
[[Image:VSphere SF attach mount 4.4 en.jpg|600px|link=]]
*<translate>When using a Windows data mover to mount the VMDK, it is required to have a second data mover on Linux with installed VDDK 5.5.x which is also a SEP sesam RDS. Virtual Windows hosts must be stored on Windows RDS and Linux virtual hosts must be stored on Linux RDS.</translate>
{{<translate>note</translate>|
<translate>SEP sesam can restore all file systems for which the respective operating system provides a read/write support. For example, a restore of files on Windows ReFS is only possible if the data mover is able to read ReFS data. Or, if the file system on OES Linux is NSS, the data mover must be able to read the NSS file system data.</translate>}}
 
<translate>==={{anchor|restore}}Restore a single file using the mounted VMDK===
 
Create a new restore task for individual file(s) you want to restore.</translate>
<ol><li><translate>From the SEP sesam GUI menu bar, select '''Activities''' -> '''Restore'''. The ''New restore task'' window opens.</translate></li>
<li><translate>Select what you want to restore. You can search save sets by ''task name'' or by ''filename or path''.</translate>
* <translate>When searching by ''task name'', use the drop-down list of available tasks and select the one you want to restore from. This option is selected by default.</translate>
* <translate>If you are searching by filename/path, select the option '''Filename or path in save set''' and enter your search expression in the search pattern field.</translate></li>
<li><translate>Under the '''Saved in period''' drop-down list, specify the time frame for which you want to conduct the search. Click '''Next'''.</translate></li>
<li><translate>The search results are displayed. From the list of save sets matching your query, select the version from which you want to restore an individual file. Then select the check box '''Mount virtual disk(s) via VMware API'''. A mount action is triggered and your VMDK is mounted to the SEP sesam home directory <tt>var\tmp\mnt</tt>, e.g., <tt>C:\Program Files\SEPsesam\var\tmp\mnt\''save_set_ID''</tt>. Click '''Next'''.</translate></li>
<translate>[[Image:VSphere SF attach mount 4.4 en.jpg|600px|link=]]</translate>
<br clear=all>
<br clear=all>
<li>On the page '''Select Files'''  only the mounted VDMK drives are shown (the local drives are not displayed). Select the files you want to restore and click '''Next'''.</li>
<li><translate>On the page '''Select Files'''  only the mounted VDMK drives are shown (the local drives are not displayed). Select the files you want to restore and click '''Next'''.</translate></li>
<li>On the last '''Save and Start''' page of the restore wizard, select where you want to restore your files.</li>
<li><translate>On the last '''Save and Start''' page of the restore wizard, select where you want to restore your files.</translate></li>
<li>You can start your single file restore immediately by clicking '''Start'''. If you want to save the restore task, click '''Save'''. </li></ol>
<li><translate>You can start your single file restore immediately by clicking '''Start'''. If you want to save the restore task, click '''Save'''.</translate> </li></ol>


You can view the status of your restore jobs by selecting '''Job state''' -> '''Restore''' from the ''Main selection''. Restore overview provides detailed information on the last run of restore jobs, including the task name, status (successful, error, in queue ...), start and stop time of the last backup, data size, throughput, client and message.
<translate>You can view the status of your restore jobs by selecting '''Job state''' -> '''Restore''' from the ''Main selection''. Restore overview provides detailed information on the last run of restore jobs, including the task name, status (successful, error, in queue ...), start and stop time of the last backup, data size, throughput, client and message.


=={{anchor|troubleshooting}}Troubleshooting==
=={{anchor|troubleshooting}}Troubleshooting==


===When restoring a single file, SEP sesam cannot access storage on a VM that is configured with the SCSI LSI Logic SAS adapter ===
===When restoring a single file, SEP sesam cannot access storage on a VM that is configured with the SCSI LSI Logic SAS adapter ===
'''Problem'''
*In SEP sesam version ≥ 4.4.3.48 in combination with a Linux proxy VM, when trying to select the restore source in the restore wizard (step 4: ''Select Files''), no items are displayed in the browser.


'''Cause'''  
'''Problem'''</translate>
*This issue seems to be related to the SCSI controller of the proxy VM. When trying to restore a single file from a virtual machine, SEP sesam cannot access storage on a virtual machine that is configured with the SCSI LSI Logic SAS adapter.
*<translate>In SEP sesam version ≥ 4.4.3.48 in combination with a Linux proxy VM, when trying to select the restore source in the restore wizard (step 4: ''Select Files''), no items are displayed in the browser.
&rArr; '''Solution'''
 
*Open the properties of the proxy VM in your vCenter and change the controller on the VM from the LSI Logic SAS controller (on some VMs, this is selected by default) to an LSI Logic Parallel controller. For more information, see VMware Docs article [https://docs.vmware.com/en/VMware-vSphere/6.0/com.vmware.vsphere.hostclient.doc/GUID-B70BF1B1-5DEB-4C85-A3D0-931DA37E995B.html Change the SCSI Controller Type in the vSphere Client].     
'''Cause'''</translate>
*Restart the restore wizard. If there are still no items displayed in the restore browser, reboot the proxy VM and then click the '''Update''' button.
*<translate>This issue seems to be related to the SCSI controller of the proxy VM. When trying to restore a single file from a virtual machine, SEP sesam cannot access storage on a virtual machine that is configured with the SCSI LSI Logic SAS adapter.</translate>
&rArr; <translate>'''Solution'''</translate>
*<translate>Open the properties of the proxy VM in your vCenter and change the controller on the VM from the LSI Logic SAS controller (on some VMs, this is selected by default) to an LSI Logic Parallel controller. For more information, see VMware Docs article [https://docs.vmware.com/en/VMware-vSphere/6.0/com.vmware.vsphere.hostclient.doc/GUID-B70BF1B1-5DEB-4C85-A3D0-931DA37E995B.html Change the SCSI Controller Type in the vSphere Client].</translate>    
*<translate>Restart the restore wizard. If there are still no items displayed in the restore browser, reboot the proxy VM and then click the '''Update''' button.


==={{anchor|VMDK}}After updating an existing SEP sesam structure with a new VDDK version, it is no longer possible to mount a VMDK===
==={{anchor|VMDK}}After updating an existing SEP sesam structure with a new VDDK version, it is no longer possible to mount a VMDK===
'''Problem'''
* After VDDK ≥ 6.5.x has been manually installed on Windows, it is no longer possible to mount a VMDK save set on this host.


'''Cause'''
'''Problem'''</translate>
*If another VDDK version, for example VDDK ≥ 6.5.x, is manually installed on Windows, the host requires a reboot after the update if you want to mount a VMDK on this host.  
* <translate>After VDDK ≥ 6.5.x has been manually installed on Windows, it is no longer possible to mount a VMDK save set on this host.
 
'''Cause'''</translate>
*<translate>If another VDDK version, for example VDDK ≥ 6.5.x, is manually installed on Windows, the host requires a reboot after the update if you want to mount a VMDK on this host.</translate>


&rArr; '''Solution'''
&rArr; <translate>'''Solution'''</translate>
<ul><li>Reboot the host after the VDDK update, then run the following script from the command line:</li>
<ul><li><translate>Reboot the host after the VDDK update, then run the following script from the command line:</translate></li>
<tt>vstor2install.bat</tt> in directory <tt>C:\Program Files\VMware\VMware Virtual Disk Development Kit\bin</tt>
<tt>vstor2install.bat</tt> <translate>in directory</translate> <tt>C:\Program Files\VMware\VMware Virtual Disk Development Kit\bin</tt>
</ul>
</ul>


<translate>
<div class="noprint">
==See also==
==See also==
[[Special:MyLanguage/4_4_3_Tigon:VMware_Single_File_Restore_and_Instant_Recovery_Support_Matrix|SF & IR support matrix 4.4.3 ''Tigon'']] – [[Special:MyLanguage/4_4_3:VMware_Single_File_Restore_and_Instant_Recovery_Support_Matrix|SF & IR support matrix 4.4.3]] – [[Special:MyLanguage/4_4_3:VMware_Requirements_%26_Restrictions|VMware Requirements & Restrictions]] – [[Special:MyLanguage/4_4_3_Tigon:VMware Backup|VMware Backup 4.4.3 ''Tigon'']] – [[Special:MyLanguage/4_4_3_Tigon:VMware Backup|VMware Backup 4.4.3]] – [[Special:MyLanguage/4_4_3:VMware Restore|VMware Restore]] – [[Special:MyLanguage/4_4_3:VMware Instant Recovery|VMware Instant Recovery]] – [[Special:MyLanguage/Scheduling Restore|Scheduling Restore]] – [[Special:MyLanguage/Troubleshooting_Guide#VMware_vStorage_API|Troubleshooting]]
[[Special:MyLanguage/4_4_3_Tigon:VMware_Single_File_Restore_and_Instant_Recovery_Support_Matrix|SF & IR support matrix 4.4.3 ''Tigon'']] – [[Special:MyLanguage/4_4_3:VMware_Single_File_Restore_and_Instant_Recovery_Support_Matrix|SF & IR support matrix 4.4.3]] – [[Special:MyLanguage/4_4_3:VMware_Requirements_%26_Restrictions|VMware Requirements & Restrictions]] – [[Special:MyLanguage/4_4_3_Tigon:VMware Backup|VMware Backup 4.4.3 ''Tigon'']] – [[Special:MyLanguage/4_4_3_Tigon:VMware Backup|VMware Backup 4.4.3]] – [[Special:MyLanguage/4_4_3:VMware Restore|VMware Restore]] – [[Special:MyLanguage/4_4_3:VMware Instant Recovery|VMware Instant Recovery]] – [[Special:MyLanguage/Scheduling Restore|Scheduling Restore]] – [[Special:MyLanguage/Troubleshooting_Guide#VMware_vStorage_API|Troubleshooting]]</div></translate>

Revision as of 08:25, 7 August 2018

Other languages:

Copyright © SEP AG 1999-2024. All rights reserved.

Any form of reproduction of the contents or parts of this manual is allowed only with the express written permission from SEP AG. When compiling and designing user documentation SEP AG uses great diligence and attempts to deliver accurate and correct information. However, SEP AG cannot issue a guarantee for the contents of this manual.

Docs latest icon.png Welcome to the latest SEP sesam documentation version 4.4.3/4.4.3 Grolar. For previous documentation version(s), check VMware archive.


Overview

Quick Start 3.png
Quick setup
  1. Attach VMDK to a virtual machine.
  2. Configure a virtual host as a SEP sesam client.
  3. Prepare the NFS share on Linux.
  4. Restore a VM using the attached VMDK.
  5. OR
  6. Mount VMDK to a SEP sesam RDS.
  7. Restore a single file using the mounted VMDK.


It is estimated that about three quarters of the typical VMware virtual machine restore cases only require a single file restore rather than a restore of an entire virtual machine. As of version 4.4.3, SEP sesam introduces simple and flexible single file restore that enables you to restore an individual item without any special backup preparation from full/differential/incremental backups. To learn what applies to single file restore and instant recovery, which backup level supports it and how it relates to the disk size usage, see SF & IR support matrix 4.4.3 Tigon.

This article provides information for restoring an individual item from a vSphere backup. For details on how to a restore a single VMware virtual machine, see VMware Restore. For details on how to perform a VMware virtual machine instant recovery, see VMware Instant Recovery.

You can restore individual items from any successful VMware backup by using any of the following procedures:

Before starting a restore, check the supported file systems and restrictions.

Supported file systems

SEP sesam can in general recover all file systems as long as the respective operating system offers read/write support for it.

  • Example 1: A restore of files from ReFS on Windows is only possible if the data mover is able to read the ReFS file system which is supported since Windows Server 2012.
  • Example 2: A restore of files from a Btrfs is only possible if the data mover is a Linux with Kernel support for it, for example SLES 12.
  • Example 3: If the file system on OES Linux is NSS, the data mover must be able to read the NSS file system data.

When restoring files from the NSS file system some limitations apply:

  • The restore process itself does not differ from the restore of native Linux or Windows files, but the proxy VM must be an OES11 Server. For prerequisites, check Recommendations for Linux proxy.
  • Files from a native NetWare VM can be restored only to an OES Linux or native Linux target.
  • To restore trustees, the extended attributes on NSS must be enabled before backup. For details, refer to Novell OES documentation for NSS.
  • If you restore NSS files to a server in the original tree and on an NSS file system, the restored files will keep the original trustees (regardless of the tree of the proxy OES VM you used for restore).
  • Trustees from native NetWare VMs cannot be restored because native NetWare has no extended attributes to store the trustees into the file system.

Restrictions

  • SEP sesam does not support a restore of files from the DOS boot partition of a native NetWare server.
  • SEP sesam provides limited support for single file restore on Windows virtual machines with spanned volumes due to Microsoft's restrictions. The following limitations exist:
    • Mounting VMDK to a SEP sesam Server/RDS is not supported.
    • Attaching VMDK to original virtual machine is not supported if the original disks are still attached (as is typically the case in most scenarios).
  • The attach method does not work with a virtual SEP sesam Server or a virtual RDS to itself. For example, a virtual SEP sesam Server stores the virtual disk(s) on the SEP sesam data store. It is not possible to attach VMDK to the respective virtual SEP sesam Server; another VM must be used for this.

Best practice for individual file restore for Windows and Linux VMs

SEP sesam provides simple restore of individual files without any special backup preparation from VMware CBT snapshot. The following steps represent best practices and latest recommendations from SEP sesam support. Detailed instructions on VMware requirements and backup configuration can be found in related articles VMware Requirements & Restrictions and VMware Backup.

  • For version 4.4.3, the following limitation applies: Windows SEP sesam Server or Windows RDS is not supported in v. 4.4.3, therefore use Linux SEP sesam Server or RDS. In case of v. 4.4.3 Tigon, Windows can be used as a SEP sesam Server or RDS.
  • Enable the NFS server on the SEP sesam Server or RDS as described in section Preparing the NFS share.
  • Install SEP sesam Client to a Linux VM (sandbox for Linux single file restore). VDDK is only required if this VM is also the data mover. In this case, check VMware Requirements & Restrictions.
  • Add the Linux VM as a client as described in Step 1: Configuring a virtual host as a SEP sesam client. Make sure that you select the check box Client is a virtual machine.
  • Information sign.png Note
    • Any operating system can be used except in case that you need a sandbox for Netware single file restore. Search the wiki for Netware reference.
    • Do not use a productive system as a sandbox!
  • Install SEP sesam Client to a Windows VM (sandbox for Windows single file restore). No specific Windows version is required. VDDK is only required if this VM is also the data mover. In this case, check VMware Requirements & Restrictions.
  • Add the Windows VM as a client as described in Step 1: Configuring a virtual host as a SEP sesam client. Make sure that you select the check box Client is a virtual machine.
  • Follow Step 3: Restore a VM using the attached VMDK : Select the VMware snapshot and select the check box Attach virtual disk(s) (VMDK) to a Proxy-VM via NFS server. Then click Next and under Select VM use the drop-down list to select Linux or Windows sandbox VM.

Attaching VMDK to a virtual machine

Attaching VMDK to a virtual machine is the recommended option for single file restore for Windows and Linux that requires only one SEP sesam Server or Remote Device Server (RDS).

Information sign.png Note
SEP sesam provides limited support for single file restore on Windows virtual machines with spanned volumes due to Microsoft's restrictions. Attaching VMDK to the original virtual machine is not supported if the original disks are still attached. You can only attach VMDK to another Windows host, because Microsoft does not allow to use the same volumes twice when having spanned volumes. Then the disks will be marked as Foreign in Disk Management. Only possible workaround is to bring these disks online manually using Disk Management. For details, see section Managing virtual machines with spanned volumes.

Conceptual view of a single item restore with the attached VMDK
SEP sesam instant-recovery and single-file-restore 04 attach 03.png

Prerequisites

Before attempting to attach VMDK and performing a single file restore, all preparation steps have to be performed properly, including configuration and VM backup. Depending on your SEP sesam version, see the relevant VMware guide for details.

The VMware single file restore prerequisites differ slightly depending on your SEP sesam version. For example, 4.4.3 Tigon already supports all backup levels and provides selective restore. Make sure that the following conditions are met:

  • SEP sesam Server version ≥ 4.4.3. For the list of supported systems, see SEP sesam OS and Database Support Matrix.
  • A SEP sesam data store Path or SEP sesam Si3 data store:
    • SEP sesam v. 4.4.3 Tigon supports the UNC path (e.g., \\server\folder) for data store.
    • In SEP sesam v. 4.4.3, data store via UNC path is not supported. A volume must be visible as a locally attached storage (not as a network drive letter). Only iSCSI, SAN and locally connected drives can be used as a locally attached storage.
  • Backups must not be encrypted or compressed, and they must not be migrated to another media – only the original backup on SEP sesam data store can be used for restore.
  • At least one virtual host of VMware vCenter needs to be added as a SEP sesam Client ≥ 4.4.3 to attach VMDKs.
  • Encrypted file systems within the virtual machine can only be read if the system (proxy VM) with the attached virtual disk is able to decrypt the data.
  • The system that stores the VMDK files to SEP sesam data store (either SEP sesam Server or SEP sesam RDS) must provide NFS (network file system) services:
    • V. 4.4.3 Tigon already includes the NFS server and does not require a regular NFS server provided by Windows.
    • For SEP sesam v. 4.4.3 with the NFS service on Windows, it is recommended to use Windows 2012 (R2) for providing a higher level of NFS support.
  • A proxy server (either Windows or Linux VM) should be a non-production environment. For more details, see Recommendations for Linux proxy below.
  • When using both, virtual Linux and Windows hosts, it is recommended to add one virtual Linux and one virtual Windows host to ensure file system compatibility.
  • Some versions, for example, VDDK 6.5.x on Windows, might require rebooting the host after the update, followed by running the vstor2install.bat script. For details, see troubleshooting section below.
Information sign.png Note

SEP sesam can restore all file systems for which the respective operating system provides a read/write support. For example, a restore of files on Windows ReFS is only possible if the system with the attached disk is able to read ReFS data. Or, if the file system on OES Linux is NSS, the system with the attached disk must be able to read the NSS file system data.

Step 1: Configuring a virtual host as a SEP sesam client

To be able to attach a VMDK file to a virtual host, SEP sesam needs to know where to attach the VMDK file(s). You have to add at least one virtual host as a SEP sesam client and this system must be assigned to the virtual host.

  1. From Main Selection -> Components -> Topology, select your location and click the New client button. The New client window opens.
  2. In the New client window, configure the following options:
    • Enter the name of the virtual host in the Client name field.
    • Select the relevant platform from the Platform drop-down list and the relevant OS under Operating system.
    • Choose the Access mode (SMSSH) for the SEP sesam server-client communication (the default setting is CTRL).
    • On the left, under the SBC Version info, select the check box Client is a virtual machine.
    • From the drop-down list on the right,select the name of your vCenter under VM host.
    • Then select the virtual machine from the VM name list and click Create.
  3. Add client VH.png


Your new client is displayed in the Topology content pane.

Step 2: Preparing the NFS share on Linux

NFS (Network File System) is a client/server application that allows to share files across a network. You have to set up the NFS service on the Linux SEP sesam Server or RDS system, which stores the VMDK files.

SEP sesam automatically creates a VMware data store to attach the VMDK file(s) to a virtual host.
VSphere SF Datastore en.jpg

The following overview provides only basic information for configuring NFS on Linux. For details, see relevant Linux documentation, for example, the article How to configure NFS on Linux.

  • NFS server must be installed and NFS service must run.
  • Exports will be created dynamically during restore by SEP sesam. Note that exports can also be created manually by editing the /etc/exports file. The exported path has to match the location of the SEP sesam data store or any of its parent directories on the same file system.
  • All ESX servers must be allowed to mount the directory.
  • Read/write permission should be set.

Recommendations for Linux proxy

OES Linux proxy VM (for restore from NSS file systems)

  • VM with OES11 SP2 or higher
  • OES pattern to install: NSS (all other dependencies will be selected automatically)
  • Recommended to install the NetIQ eDirectory as a separate tree.
  • Static IP address (required by NetIQ eDirectory).
  • Only minimal system is required, X server is not required.
  • Size of file system only for SLES11 SP3 + OES11 SP2 (or higher versions).
  • Current SEP sesam client for SLES11.

OES Linux

  • Use a separate, non-production OES VM
  • Install the NetIQ eDirectory as a separate tree.
  • Do not add NSS pools and volumes to the OES server – all non-active pools are automatically avtivated and deactivated after restore
  • Do not change the mounted NSS file systems – they are your backup!

Step 3: Restore a VM using the attached VMDK

Create a new restore task for individual file(s) you want to restore.

  1. From the SEP sesam GUI menu bar, select Activities -> Restore. The New restore task window opens.
  2. Select what you want to restore. You can search save sets by task name or by filename or path.
    • When searching by task name, use the drop-down list of available tasks and select the one you want to restore from. This option is selected by default.
    • If you are searching by filename/path, select the option Filename or path in save set and enter your search expression in the search pattern field.
  3. Under the Saved in period drop-down list, specify the time frame for which you want to conduct the search. Click Next.
  4. The search results are displayed. From the list of save sets matching your query, select the version from which you want to restore an individual file. Then select the check box Attach virtual disk(s) (VMDK) to a Proxy-VM via NFS server. Click Next.
  5. VSphere SF attach mount 4.4 en.jpg
  6. Under the Select VM, use the drop-down list to select the relevant vSphere server, Sesam client name of the proxy VM and vSphere internal name of proxy VM. The vSphere server is the vCenter where the virtual host – vSphere internal name of proxy VM – is running, which is assigned as a SEP sesam Client – Sesam client name of the proxy VM. If the host that attaches the disk(s) uses multiple network cards, you must also specify NFS interface; otherwise this option does not need to be specified. Click Next.
  7. VSphere SF select vm 4.4 en.jpg
  8. On the page Select Files only the drives of the chosen VMDK(s) are shown. Note that it might take form 5 to 20 seconds to load the drive list. SEP sesam automatically enables the automount function of Windows on host, which attaches the VMDK(s). The automount function of Windows assigns a drive letter to a new disk drive without interaction of a user. SEP sesam automatically sets all connected drives on this particular host to Online.
    If no drives are shown, either an invalid partition was chosen (for example, if a Windows host tries to attach Linux partitions) or the drives did not start in expected time. You can use the refresh button (on the right side of the table) to display the list of all drives, local and the attached ones. Click Next.
  9. VSphere SF list drives en.jpg
  10. On the last Save and Start page of the restore wizard, you only need to select the client and the destination.
  11. VSphere SF restore options en.jpg
  12. You can start your VM restore immediately by clicking Start. If you want to save the restore task, click Save.

You can view the status of your restore jobs by selecting Job state -> Restore from the Main selection. Restore overview provides detailed information on the last run of restore jobs, including the task name, status (successful, error, in queue ...), start and stop time of the last backup, data size, throughput, client and message.

Managing virtual machines with spanned volumes

SEP sesam provides limited support for single file restore on Windows virtual machines with spanned volumes due to Microsoft's restrictions. Attaching VMDK to the original virtual machine is not supported if the original disks are still attached.

You can only attach VMDK to another Windows host, because Microsoft does not allow to use the same volumes twice when having spanned volumes. Then the disks will be marked as Foreign in Disk Management. Only possible workaround is to bring these disks online manually using Disk Management.

Steps

  1. Open Computer Management -> Disk Management, and click Import Foreign Disks option. This lists one or more disk groups, identified by the name of the computer where they were created. If you expand the details on a disk group, it lists the locally-connected disks.
  2. Select the relevant Disk Group. The dialog box with a list of volumes in the Disk Group opens.
  3. Select the relevant volumes and click OK to add the foreign disks to your system configuration.

The operation is slightly different, depending on whether there are pre-existing online foreign (dynamic) disks on the target computer. For details, see Microsoft support article Description of Disk Groups in Windows Disk Management.

Mounting VMDK to a SEP sesam RDS

You can mount any non-compressed VMDK save set stored to default data store Path or to Si3 data store to the local system, which is used as a VMware data mover and SEP sesam RDS with a data store.

The target VMDK is mounted to the SEP sesam home directory var\tmp\mnt, e.g., C:\Program Files\SEPsesam\var\tmp\mnt\save_set_ID. This way the VMDK is instantly accessible for browsing and searching before the actual restore is even triggered, providing you with quick access to your data. The mounted VMDK is basically a virtual read-only file system, therefore it cannot be altered or otherwise damaged. Comparing to the attach method, mounting has the advantage of much easier setup and requires less configuration steps.

Information sign.png Note
  • Mounting is not possible if the save sets are stored to tapes or if the save sets are compressed.
  • Mounting is not supported on Windows virtual machines with spanned volumes due to Microsoft's restriction.

Conceptual view of a single item restore with mounted VMDK
SEP sesam instant-recovery and single-file-restore 03 mount 03.png

Prerequisites

Before attempting to mount VMDK and performing a single file restore, all preparation steps have to be performed properly, including configuration and VM backup. Depending on your SEP sesam version, see the relevant VMware guide for details. Make sure that the following conditions are met:

  • SEP sesam Server version ≥ 4.4.3. For the list of supported systems, see SEP sesam OS and Database Support Matrix.
  • A SEP sesam data store Path or SEP sesam Si3 data store:
    • SEP sesam v. 4.4.3 Tigon supports the UNC path (e.g., \\server\folder) for data store.
    • In SEP sesam v. 4.4.3, data store via UNC path is not supported. A volume must be visible as a locally attached storage (not as a network drive letter). Only iSCSI, SAN and locally connected drives can be used as a locally attached storage.
  • Backups must not be encrypted or compressed, and they must not be migrated to another media – only the original backup on SEP sesam data store can be used for restore.
  • VDDK 5.5.x must be installed on the system, which is used as a VMware data mover and SEP sesam RDS with a data store. On Windows, VDDK is a part of the SEP sesam installation. SEP sesam version 4.4.3 is using VDDK version 6. If you are using a Linux system or any of the previous SEP sesam versions, you have to install the VDDK manually. For details, see Installing VDDK on Linux.
  • When using a Linux data mover to mount the VMDK, it must be able to read Linux and Windows systems. Note that mounting Windows VMDKs with Linux data mover might result in ACL-related problems and is therefore not recommended.
  • When using a Windows data mover to mount the VMDK, it is required to have a second data mover on Linux with installed VDDK 5.5.x which is also a SEP sesam RDS. Virtual Windows hosts must be stored on Windows RDS and Linux virtual hosts must be stored on Linux RDS.
Information sign.png Note

SEP sesam can restore all file systems for which the respective operating system provides a read/write support. For example, a restore of files on Windows ReFS is only possible if the data mover is able to read ReFS data. Or, if the file system on OES Linux is NSS, the data mover must be able to read the NSS file system data.

Restore a single file using the mounted VMDK

Create a new restore task for individual file(s) you want to restore.

  1. From the SEP sesam GUI menu bar, select Activities -> Restore. The New restore task window opens.
  2. Select what you want to restore. You can search save sets by task name or by filename or path.
    • When searching by task name, use the drop-down list of available tasks and select the one you want to restore from. This option is selected by default.
    • If you are searching by filename/path, select the option Filename or path in save set and enter your search expression in the search pattern field.
  3. Under the Saved in period drop-down list, specify the time frame for which you want to conduct the search. Click Next.
  4. The search results are displayed. From the list of save sets matching your query, select the version from which you want to restore an individual file. Then select the check box Mount virtual disk(s) via VMware API. A mount action is triggered and your VMDK is mounted to the SEP sesam home directory var\tmp\mnt, e.g., C:\Program Files\SEPsesam\var\tmp\mnt\save_set_ID. Click Next.
  5. VSphere SF attach mount 4.4 en.jpg
  6. On the page Select Files only the mounted VDMK drives are shown (the local drives are not displayed). Select the files you want to restore and click Next.
  7. On the last Save and Start page of the restore wizard, select where you want to restore your files.
  8. You can start your single file restore immediately by clicking Start. If you want to save the restore task, click Save.

You can view the status of your restore jobs by selecting Job state -> Restore from the Main selection. Restore overview provides detailed information on the last run of restore jobs, including the task name, status (successful, error, in queue ...), start and stop time of the last backup, data size, throughput, client and message.

Troubleshooting

When restoring a single file, SEP sesam cannot access storage on a VM that is configured with the SCSI LSI Logic SAS adapter

Problem

  • In SEP sesam version ≥ 4.4.3.48 in combination with a Linux proxy VM, when trying to select the restore source in the restore wizard (step 4: Select Files), no items are displayed in the browser.

Cause

  • This issue seems to be related to the SCSI controller of the proxy VM. When trying to restore a single file from a virtual machine, SEP sesam cannot access storage on a virtual machine that is configured with the SCSI LSI Logic SAS adapter.

Solution

  • Open the properties of the proxy VM in your vCenter and change the controller on the VM from the LSI Logic SAS controller (on some VMs, this is selected by default) to an LSI Logic Parallel controller. For more information, see VMware Docs article Change the SCSI Controller Type in the vSphere Client.
  • Restart the restore wizard. If there are still no items displayed in the restore browser, reboot the proxy VM and then click the Update button.

After updating an existing SEP sesam structure with a new VDDK version, it is no longer possible to mount a VMDK

Problem

  • After VDDK ≥ 6.5.x has been manually installed on Windows, it is no longer possible to mount a VMDK save set on this host.

Cause

  • If another VDDK version, for example VDDK ≥ 6.5.x, is manually installed on Windows, the host requires a reboot after the update if you want to mount a VMDK on this host.

Solution

  • Reboot the host after the VDDK update, then run the following script from the command line:
  • vstor2install.bat in directory C:\Program Files\VMware\VMware Virtual Disk Development Kit\bin