Source:Cross-Platform Recovery File System Layer: Difference between revisions

From SEPsesam
(Added /4.4.3 Grolar in the nav box.)
(Update related to 24391 and 18582.)
Line 30: Line 30:
|}</div>
|}</div>
<translate><!--T:11-->
<translate><!--T:11-->
Cross-platform recovery file system layer (XPRFS) is a special implementation of a ''virtual file system layer''. It is an '''advanced restore feature''' that allows for '''mount and restore onto different operating systems and hardware platforms''' (Windows – ''MTF'' <–> Linux/Unix – ''cpio''). XPRFS employs direct access to backed up data and allows you to access individual backed up files through a file browser, thus enabling '''single file restore'''.  
Cross-platform recovery file system layer (XPRFS) is a special implementation of a ''virtual file system layer''. It is an '''advanced restore feature''' that allows for '''mount and restore onto different operating systems and hardware platforms''' (Windows – ''MTF'' <–> Linux/Unix – ''cpio'').  


<!--T:12-->
<!--T:12-->
For example, data backed up from a Linux system (''cpio'' save set) can be mounted on Windows [[Special:MyLanguage/SEP_sesam_Glossary#RDS|RDS]], and data backed up from a Windows system (''MTF'' save set) can be mounted on Linux/Unix [[Special:MyLanguage/SEP_sesam_Glossary#RDS|RDS]].
For example, data backed up from a Linux system (''cpio'' save set) can be mounted on Windows [[Special:MyLanguage/SEP_sesam_Glossary#RDS|RDS]], and data backed up from a Windows system (''MTF'' save set) can be mounted on Linux/Unix [[Special:MyLanguage/SEP_sesam_Glossary#RDS|RDS]]; note that the operating system of the restore target must be the same as the operating system of the used Remote Device Server (RDS) (for details, see [[Special:MyLanguage/Cross-Platform_Recovery_File_System_Layer#restrictions|Restrictions]] below).  


===XPRFS advantages=== <!--T:13-->
XPRFS employs direct access to backed up data and allows you to access individual backed up files through a file browser, thus enabling '''single file restore'''. However, the original ownership and access settings for restored objects are not preserved when the backup is mounted; the user under which the SEP sesam service is running is effectively the owner of the restored files. For details, see [[Special:MyLanguage/Cross-Platform_Recovery_File_System_Layer#restrictions|Restrictions]] below.
 
==={{anchor|advantages}}XPRFS advantages=== <!--T:13-->


<!--T:14-->
<!--T:14-->
One of the XPRFS main advantages is that it is no longer required to perform a complete restore of backed up data. By selecting the '''Mount save set''' option in the restore wizard, the target save set 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>. The mounted save set is instantly accessible for browsing and searching.  
One of the XPRFS main advantages is that it is no longer required to perform a complete restore of backed up data. By selecting the '''Mount save set''' option in the restore wizard, the target save set 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>. The mounted save set is instantly accessible for browsing and searching (some limitations apply, see [[Special:MyLanguage/Cross-Platform_Recovery_File_System_Layer#restrictions|Restrictions]] below).  


<!--T:15-->
<!--T:15-->
It is recommended to use the XPRFS for restoring specific data, such as Exchange, Hyper-V and V-Sphere backups with the following major advantages:</translate>
It is recommended to use the XPRFS for restoring specific data, such as Exchange, Hyper-V and V-Sphere backups with the following major advantages:</translate>
*<translate><!--T:16-->
*<translate><!--T:16-->
Instant access to your data, such as single mailboxes.</translate>
Instant access to your data, such as single mailboxes.</translate>
Line 47: Line 50:
*<translate><!--T:17-->
*<translate><!--T:17-->
Faster restore time and performance.</translate>  
Faster restore time and performance.</translate>  
*<translate><!--T:18-->
*<translate><!--T:18-->
Reduced free space requirement on restore target.</translate>
Reduced free space requirement on restore target.</translate>


*<translate><!--T:19-->
*<translate><!--T:19-->
Protection of mounted data – all data is mounted read-only, allowing you to query the save set and preventing you from altering or damaging the data content.
Protection of mounted data – all data is mounted read-only, allowing you to query the save set and preventing you from altering or damaging the data content.</translate>


===Prerequisites=== <!--T:20-->
<translate>
==={{anchor|restrictions}}XPRFS restrictions===
The following restrictions apply for mounting and cross-platform recovery:</translate>
 
*<translate>Note that mounting does not preserve the original ownership and permissions for restored objects. The owner of the mounted backup/restored data is determined by the user under which the SEP sesam service runs. Typically, on Unix/Linux this is ''root'', while on Windows the sesam service is typically running under the ''LocalService'' account (NT AUTHORITY\LocalService; ''system user''). Note, however, that some SEP sesam extensions (such as [[Special:MyLanguage/Exchange_configuration_guide_for_SEP_sesam_Version_4.4.3.x|Exchange Recovery Pro]]'' or ''[[Special:MyLanguage/SharePoint_Backup|SharePoint Recovery Pro]]'') require that the SEP sesam service is configured with a user account with domain administrator privileges.</translate>
 
*<translate>You can mount a Windows backup to a Linux system or a Linux backup to a Windows system, but the operating system of both, the Remote Device Server (RDS) you used for mounting and of the destination restore target must be the same. For example, you can mount a Windows backup on the Linux device server, but this backup can be restored on Linux host only and vice versa: you can mount a Linux backup on the Windows device server, but this backup can then be restored on Windows host only.</translate>
 
*<translate><!--T:25-->
When performing cross-platform restore, you should be aware of the data characteristics related to different platforms. For example, if you are restoring Windows data with [[Special:MyLanguage/SEP_sesam_Glossary#ACL|access control list (ACL)]] (or [[Special:MyLanguage/Support_for_NTFS_alternate_data_streams_(ADS)_for_Windows|alternate data streams (ADS)]]) to Linux, you have to be aware that ACL (and ADS) will not be preserved. Be aware that certain limitations apply whenever data is restored to another environment.</translate>
 
*<translate><!--T:26-->
Restore with ''Exchange Recovery Pro'' and ''SharePoint Recovery Pro'' is using the XPRFS feature too, therefore the same requirements apply. For details, see ''[[Special:MyLanguage/Exchange_configuration_guide_for_SEP_sesam_Version_4.4.3.x|Exchange Recovery Pro]]'' or ''[[Special:MyLanguage/SharePoint_Backup|SharePoint Recovery Pro]]''.</translate>
 
<translate>===Prerequisites=== <!--T:20-->


<!--T:21-->
<!--T:21-->
Line 62: Line 80:
*<translate><!--T:23-->
*<translate><!--T:23-->
A SEP sesam [[Special:MyLanguage/SEP_sesam_Glossary#data_store|data store]] ''Path'' or SEP sesam ''Si3'' data store is required for instant single item recovery.</translate>
A SEP sesam [[Special:MyLanguage/SEP_sesam_Glossary#data_store|data store]] ''Path'' or SEP sesam ''Si3'' data store is required for instant single item recovery.</translate>
{{<translate><!--T:24-->
note</translate>|
*<translate><!--T:25-->
When performing cross-platform restore, you should be aware of the data characteristics related to different platforms. For example, if you are restoring Windows data with [[Special:MyLanguage/SEP_sesam_Glossary#ACL|access control list (ACL)]] (or [[Special:MyLanguage/Support_for_NTFS_alternate_data_streams_(ADS)_for_Windows|alternate data streams (ADS)]]) to Linux, you have to be aware that ACL (and ADS) will not be preserved. Be aware that certain limitations apply whenever data is restored to another environment.</translate>
*<translate><!--T:26-->
Restore with ''Exchange Recovery Pro'' and ''SharePoint Recovery Pro'' is using the XPRFS feature too, therefore the same requirements apply. For details, see ''[[Special:MyLanguage/Exchange_configuration_guide_for_SEP_sesam_Version_4.4.3.x|Exchange Recovery Pro]]'' or ''[[Special:MyLanguage/SharePoint_Backup|SharePoint Recovery Pro]]''.</translate>}}


<translate>==Enabling XPRFS== <!--T:27-->
<translate>==Enabling XPRFS== <!--T:27-->

Revision as of 16:14, 25 September 2018

Other languages:
Template:Copyright SEP AG en
Docs latest icon.png Welcome to the latest SEP sesam documentation version 4.4.2/4.4.3 Grolar. For previous documentation version(s), check documentation archive.


Overview

Cross-platform recovery file system layer (XPRFS) is a special implementation of a virtual file system layer. It is an advanced restore feature that allows for mount and restore onto different operating systems and hardware platforms (Windows – MTF <–> Linux/Unix – cpio).

For example, data backed up from a Linux system (cpio save set) can be mounted on Windows RDS, and data backed up from a Windows system (MTF save set) can be mounted on Linux/Unix RDS; note that the operating system of the restore target must be the same as the operating system of the used Remote Device Server (RDS) (for details, see Restrictions below).

XPRFS employs direct access to backed up data and allows you to access individual backed up files through a file browser, thus enabling single file restore. However, the original ownership and access settings for restored objects are not preserved when the backup is mounted; the user under which the SEP sesam service is running is effectively the owner of the restored files. For details, see Restrictions below.

XPRFS advantages

One of the XPRFS main advantages is that it is no longer required to perform a complete restore of backed up data. By selecting the Mount save set option in the restore wizard, the target save set is mounted to the SEP sesam home directory var\tmp\mnt, e.g., C:\Program Files\SEPsesam\var\tmp\mnt\save_set_ID. The mounted save set is instantly accessible for browsing and searching (some limitations apply, see Restrictions below).

It is recommended to use the XPRFS for restoring specific data, such as Exchange, Hyper-V and V-Sphere backups with the following major advantages:

  • Instant access to your data, such as single mailboxes.
  • Faster restore time and performance.
  • Reduced free space requirement on restore target.
  • Protection of mounted data – all data is mounted read-only, allowing you to query the save set and preventing you from altering or damaging the data content.

XPRFS restrictions

The following restrictions apply for mounting and cross-platform recovery:

  • Note that mounting does not preserve the original ownership and permissions for restored objects. The owner of the mounted backup/restored data is determined by the user under which the SEP sesam service runs. Typically, on Unix/Linux this is root, while on Windows the sesam service is typically running under the LocalService account (NT AUTHORITY\LocalService; system user). Note, however, that some SEP sesam extensions (such as Exchange Recovery Pro or SharePoint Recovery Pro) require that the SEP sesam service is configured with a user account with domain administrator privileges.
  • You can mount a Windows backup to a Linux system or a Linux backup to a Windows system, but the operating system of both, the Remote Device Server (RDS) you used for mounting and of the destination restore target must be the same. For example, you can mount a Windows backup on the Linux device server, but this backup can be restored on Linux host only and vice versa: you can mount a Linux backup on the Windows device server, but this backup can then be restored on Windows host only.
  • When performing cross-platform restore, you should be aware of the data characteristics related to different platforms. For example, if you are restoring Windows data with access control list (ACL) (or alternate data streams (ADS)) to Linux, you have to be aware that ACL (and ADS) will not be preserved. Be aware that certain limitations apply whenever data is restored to another environment.

Prerequisites

XPRFS requires the following:

  • A SEP sesam data store Path or SEP sesam Si3 data store is required for instant single item recovery.

Enabling XPRFS

To enable XPRFS, from the SEP sesam GUI menu bar select Activities -> Restore -> select save set -> select task -> under Single file restore select Mount save set. For details, see Standard Restore Procedure.