SEP sesam Storage Hardware Support Matrix: Difference between revisions
(Hardware Snapshots for VMware Backup) |
|||
(40 intermediate revisions by 7 users not shown) | |||
Line 1: | Line 1: | ||
{{Copyright | {{Copyright}}<br /> | ||
== Overview == | == Overview == | ||
Line 15: | Line 15: | ||
{|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;" | | | rowspan="2" style="padding:0px 10px 0px;" | | ||
[[File:SEP Tip.png|45px|link=Special:MyLanguage/FAQ|FAQ]] | [[File:SEP Tip.png|45px|link=Special:MyLanguage/4_4_3_Beefalo:FAQ|FAQ]] | ||
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | | | style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | | ||
Check [[Special:MyLanguage/FAQ|FAQ]] to find the answers to most common questions. | Check [[Special:MyLanguage/FAQ|FAQ]] to find the answers to most common questions. | ||
Line 27: | Line 27: | ||
|} | |} | ||
</div> | </div> | ||
SEP sesam generally supports all devices | SEP sesam generally supports all devices connected via standard interfaces, such as FC, iSCSI, SAS, SATA, SCSI and S3. | ||
The device connection must be supported by the hardware vendor and recognized | The device connection must be supported by the hardware vendor and correctly recognized by the operating system. | ||
For example: | |||
* Single tape drives | * Single tape drives | ||
* Tape | * Tape libraries | ||
* VTL | * VTL | ||
* Storage | * Storage systems | ||
* NAS | * NAS | ||
* Cloud | * Cloud storage | ||
<div id="note">''''' | <div id="note">'''''Note '''''</div> | ||
''SEP sesam can use a wide range of devices. We receive | ''SEP sesam can use a wide range of devices. We regularly receive reports from our customers that other tape or storage devices not explicitly listed in our harware matrix also work smoothly. Customers should be up to date with the latest OS update level, device driver and firmware levels. For hardware problems with listed and non-listed devices, please contact the hardware vendor first.'' | ||
'''The list of supported hardware vendors and devices on this page is | '''The list of supported hardware vendors and devices on this page is only a selection of our most valuable partners and does not claim to be complete. If you have special requests or questions about supported devices, please contact us by email at [mailto:support@sep.de support@sep.de].''' | ||
For more compatibility | For more information on compatibility, refer to [[Special:MyLanguage/SEP_sesam_OS_and_Database_Support_Matrix|SEP sesam OS and Database Support Matrix]]. | ||
==Technology Partners== | ==Technology Partners== | ||
Line 59: | Line 59: | ||
|- | |- | ||
| DELL/EMC || DataDomain V6.0 and higher with DDBoostFS | | DELL/EMC || DataDomain V6.0 and higher with DDBoostFS | ||
|- | |- | ||
Line 104: | Line 102: | ||
| HPE || HPE StoreOnce VSA | | HPE || HPE StoreOnce VSA | ||
|- | |- | ||
| HPE || HPE StoreOnce Catalyst | | HPE || HPE StoreOnce Catalyst | ||
|- | |||
|} | |||
===Huawei=== | |||
{| class="wikitable sortable" | |||
|+ | |||
|- | |||
| Huawei|| Huawei OceanStor Dorado | |||
|- | |- | ||
Line 174: | Line 182: | ||
| LTO || LTO7 | | LTO || LTO7 | ||
|- | |- | ||
| LTO || LTO8 <sup>[[# | | LTO || LTO8 <sup>[[#note1|'''Note 1''']]</sup> | ||
|- | |||
| LTO || LTO9 <sup>[[#note2|'''Note 2''']]</sup> | |||
|} | |} | ||
<div id=" | <div id="note1">'''''Note 1'''''</div> | ||
''Hardware encryption for LTO 8 is | ''Hardware encryption for LTO 8 is supported since SEP sesam version 4.4.3.64 with service pack 2019-1 installed.'' | ||
<div id="note2">'''''Note 2'''''</div> | |||
''Hardware encryption for LTO 9 is supported since SEP sesam version 5.0. - Jaglion V2.'' | |||
''LTO-9 tapes should be initialized using the software provided by the LTO-9 drive/loader manufacturer before using them in SEP sesam to avoid backup failures or limited or no access to the LTO-9 tapes. For details see [[Special:MyLanguage/Troubleshooting_Guide#Problems_with_LTO-9_tapes|Problems with LTO-9 tapes]]''. | |||
'' | |||
===Cloud Storage=== | ===Cloud Storage=== | ||
Line 185: | Line 199: | ||
|- | |- | ||
| | | S3|| Any kind of cloud provider is supported as long as it provides a standard '''S3''' (Simple Storage Service) interface (e.g. AWS). An S3 target can be used with SEP sesam as a backup target and requires the usage of SEP Si3 deduplication technology. The configuration and management of [[Special:MyLanguage/SEP_sesam_Glossary#Si3_store|Si3 NG]] in an S3-compatible cloud implementation is similar to the example shown in [[Special:MyLanguage/5_0_0:Backup_to_S3_Cloud_Storage|Backup to S3 Cloud Storage]].<BR>'''Note'''<BR>As SEP sesam uses a generic S3 interface this could also be used for an SDS appliance (e.g. SES). | ||
|- | |- | ||
Line 205: | Line 219: | ||
|- | |- | ||
| RDX|| Will be configured in SEP sesam as a diskbased VTL. Find more details here [[Special:MyLanguage/ | | RDX|| Will be configured in SEP sesam as a diskbased VTL. Find more details here [[Special:MyLanguage/4_4_3:Configuring_Removable_Media#add_drives|RDX Configuration]]. | ||
|- | |- | ||
Line 216: | Line 230: | ||
| DLT || Can be configured in SEP sesam via drive type. Find more details here [[Special:MyLanguage/Drives|Drive Configuration]]. | | DLT || Can be configured in SEP sesam via drive type. Find more details here [[Special:MyLanguage/Drives|Drive Configuration]]. | ||
|- | |||
|} | |||
==Vendor Depending Software Functions== | |||
==={{anchor|NDMP}}NDMP=== | |||
{| border="2" cellpadding="4" cellspacing="0" style="width:70%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;" | |||
|- style="background:#000000; color:#FFFFFF" | |||
! scope="col" style="width: 170px; text-align:left;" |Version | |||
! scope="col" style="width: 40px; text-align:left;" | Client | |||
! scope="col" style="width: 40px; text-align:left;"| Server | |||
! scope="col" style="width: 40px; text-align:left;" | RDS | |||
! scope="col" style="width: 40px; text-align:left;"| GUI | |||
|- | |||
|Dell EMC Unity ||4.4.3.84 ''Beefalo V2'' || || || | |||
|- | |||
|NetApp ||4.4 || || || | |||
|- | |||
|Oracle ZFS ||4.4 || || || | |||
|} | |||
<div id="note1"><span style="font-size:92%; line-height: 1.3em; color:black;">'''Note<sup>1</sup>'''</span></div> | |||
<span style="font-size:92%; line-height: 1.3em; color:black;">NDMP is supported for 3-way NDMP only.</span> | |||
==={{anchor|HW_snapshots}}Hardware Snapshots for VMware Backup=== | |||
{| border="2" cellpadding="4" cellspacing="0" style="width:70%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;" | |||
|- style="background:#000000; color:#FFFFFF" | |||
! scope="col" style="width: 170px; text-align:left;" |Version | |||
! scope="col" style="width: 40px; text-align:left;" | Client | |||
! scope="col" style="width: 40px; text-align:left;"| Server | |||
! scope="col" style="width: 40px; text-align:left;" | RDS | |||
! scope="col" style="width: 40px; text-align:left;"| GUI | |||
|- | |||
|HPE Nimble Storage ||5.1.0 ''Apollon'' || || || | |||
|- | |||
|HPE Alletra 5000/6000 <sup>[[#noteHPE|'''Note''']]</sup> ||5.1.0 ''Apollon'' || || || | |||
|- | |||
|Pure Storage ||5.1.0 ''Apollon'' || || || | |||
|- | |||
|Huawei OceanStor ||5.1.0 ''Apollon'' || || || | |||
|} | |||
<div id="noteHPE"><span style="font-size:92%; line-height: 1.3em; color:black;">'''Note'''</span></div> | |||
<span style="font-size:92%; line-height: 1.3em; color:black;">HPE Alletra 5000/6000 is fully compatible with Nimble Storage. When configuring this storage system as a SEP sesam Client, select ''HPE Nimble Storage'' as the OS.</span> | |||
==={{anchor|Storage_Snapshots}}Storage Snapshots=== | |||
{| border="2" cellpadding="4" cellspacing="0" style="width:70%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;" | |||
|- style="background:#000000; color:#FFFFFF" | |||
! scope="col" style="width: 170px; text-align:left;" |Version | |||
! scope="col" style="width: 40px; text-align:left;" | Client | |||
! scope="col" style="width: 40px; text-align:left;"| Server | |||
! scope="col" style="width: 40px; text-align:left;" | RDS | |||
! scope="col" style="width: 40px; text-align:left;"| GUI | |||
|- | |||
|NetApp <sup>[[#note2|'''Note<sup>2</sup>''']]</sup> ||4.4 || || || | |||
|} | |||
<div id="note2"><span style="font-size:92%; line-height: 1.3em; color:black;">'''Note<sup>2</sup>'''</span></div> | |||
<span style="font-size:92%; line-height: 1.3em; color:black;">Consistency is given for file data.</span> | |||
==={{anchor|ACSLS}}ACSLS=== | |||
{| border="2" cellpadding="4" cellspacing="0" style="width:70%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;" | |||
|- style="background:#000000; color:#FFFFFF" | |||
! scope="col" style="width: 170px; text-align:left;" |Version | |||
! scope="col" style="width: 40px; text-align:left;" | Client | |||
! scope="col" style="width: 40px; text-align:left;"| Server | |||
! scope="col" style="width: 40px; text-align:left;" | RDS | |||
! scope="col" style="width: 40px; text-align:left;"| GUI | |||
|- | |||
|Oracle (StorageTek) <sup>[[#note3|'''Note<sup>3</sup>''']]</sup> ||4.4.3.84 ''Beefalo V2'' || || || | |||
|} | |||
<div id="note3"><span style="font-size:92%; line-height: 1.3em; color:black;">'''Note<sup>3</sup>'''</span></div> | |||
<span style="font-size:92%; line-height: 1.3em; color:black;">StorageTek Automated Cartridge System Library Software as of Release 8.3. For earlier versions please contact us.<BR>SEP DataMover must be Oracle Linux/Red Hat Enterprise Linux 6.3 or 6.4.</span> | |||
==Hyper-converged Infrastructure== | |||
===Nutanix=== | |||
{| class="wikitable sortable" | |||
|+ | |||
|- | |||
| Nutanix with VMware || SEP VMware agent can be used | |||
|- | |||
| Nutanix with Hyper-V || SEP Hyper-V agent can be used | |||
|- | |||
| Nutanix with Citrix Hypervisor || SEP Citrix agent can be used | |||
|- | |||
| Nutanix AHV (Acropolis) || New SEP agent under development | |||
|- | |||
|} | |||
===HPE=== | |||
{| class="wikitable sortable" | |||
|+ | |||
|- | |||
| SimpliVity with VMware || SEP VMware agent can be used | |||
|- | |- | ||
Line 251: | Line 366: | ||
|} | |} | ||
==Object Storage== | |||
As of version [[Release_Notes_5.0.0_Jaglion|5.0.0.x Jaglion]], SEP sesam supports S3 as a generic interface based on the new deduplication store [[Special:MyLanguage/5_0_0:Configuring_Si3_NG_Deduplication_Store|Si3 NG]].<br /> | |||
Some S3 targets are already supported, others have been looked at in more detail (see list below) and are currently being tested. | |||
{{:OS Support Matrix for Object_Storage}} | |||
==Archive of Supported Devices== | ==Archive of Supported Devices== |
Latest revision as of 14:06, 27 March 2024
Overview
SEP sesam generally supports all devices connected via standard interfaces, such as FC, iSCSI, SAS, SATA, SCSI and S3. The device connection must be supported by the hardware vendor and correctly recognized by the operating system.
For example:
- Single tape drives
- Tape libraries
- VTL
- Storage systems
- NAS
- Cloud storage
SEP sesam can use a wide range of devices. We regularly receive reports from our customers that other tape or storage devices not explicitly listed in our harware matrix also work smoothly. Customers should be up to date with the latest OS update level, device driver and firmware levels. For hardware problems with listed and non-listed devices, please contact the hardware vendor first.
The list of supported hardware vendors and devices on this page is only a selection of our most valuable partners and does not claim to be complete. If you have special requests or questions about supported devices, please contact us by email at support@sep.de.
For more information on compatibility, refer to SEP sesam OS and Database Support Matrix.
Technology Partners
DELL/EMC
DELL/EMC | PowerVault Series |
DELL/EMC | ML Series |
DELL/EMC | DataDomain |
DELL/EMC | DataDomain V6.0 and higher with DDBoostFS |
FUJITSU
FUJITSU | Fujitsu Scalar |
FUJITSU | ETERNUS LT Series |
FUJITSU | ETERNUS CS800 |
FUJITSU | ETERNUS CS8000 (vjuke only) |
FUJITSU | ETERNUS DX Series |
FUJITSU | ETERNUS AF Series |
FUJITSU | ETERNUS CD10000 |
FUJITSU | ETERNUS JX |
HPE
HPE | HPE 3PAR StoreServ |
HPE | HPE MSA |
HPE | HPE StoreEver |
HPE | HPE StoreOnce |
HPE | HPE StoreOnce VSA |
HPE | HPE StoreOnce Catalyst |
Huawei
Huawei | Huawei OceanStor Dorado |
IBM
IBM | IBM TS Series |
NetApp
NetApp | FAS Series |
NetApp | AFF Series |
QUANTUM
QUANTUM | Scalar |
QUANTUM | DXi |
SAYTEC
SAYTEC | sayFUSE |
Media Technology
LTO
LTO | LTO1 |
LTO | LTO2 |
LTO | LTO3 |
LTO | LTO4 |
LTO | LTO5 |
LTO | LTO6 |
LTO | LTO7 |
LTO | LTO8 Note 1 |
LTO | LTO9 Note 2 |
Hardware encryption for LTO 8 is supported since SEP sesam version 4.4.3.64 with service pack 2019-1 installed.
Hardware encryption for LTO 9 is supported since SEP sesam version 5.0. - Jaglion V2.
LTO-9 tapes should be initialized using the software provided by the LTO-9 drive/loader manufacturer before using them in SEP sesam to avoid backup failures or limited or no access to the LTO-9 tapes. For details see Problems with LTO-9 tapes.
Cloud Storage
S3 | Any kind of cloud provider is supported as long as it provides a standard S3 (Simple Storage Service) interface (e.g. AWS). An S3 target can be used with SEP sesam as a backup target and requires the usage of SEP Si3 deduplication technology. The configuration and management of Si3 NG in an S3-compatible cloud implementation is similar to the example shown in Backup to S3 Cloud Storage. Note As SEP sesam uses a generic S3 interface this could also be used for an SDS appliance (e.g. SES). |
VTL
VTL | Will be configured in SEP sesam as a real library. Find more details here Loader Configuration. |
RDX
RDX | Will be configured in SEP sesam as a diskbased VTL. Find more details here RDX Configuration. |
DLT
DLT | Can be configured in SEP sesam via drive type. Find more details here Drive Configuration. |
Vendor Depending Software Functions
NDMP
Version | Client | Server | RDS | GUI |
---|---|---|---|---|
Dell EMC Unity | 4.4.3.84 Beefalo V2 | |||
NetApp | 4.4 | |||
Oracle ZFS | 4.4 |
NDMP is supported for 3-way NDMP only.
Hardware Snapshots for VMware Backup
Version | Client | Server | RDS | GUI |
---|---|---|---|---|
HPE Nimble Storage | 5.1.0 Apollon | |||
HPE Alletra 5000/6000 Note | 5.1.0 Apollon | |||
Pure Storage | 5.1.0 Apollon | |||
Huawei OceanStor | 5.1.0 Apollon |
HPE Alletra 5000/6000 is fully compatible with Nimble Storage. When configuring this storage system as a SEP sesam Client, select HPE Nimble Storage as the OS.
Storage Snapshots
Version | Client | Server | RDS | GUI |
---|---|---|---|---|
NetApp Note2 | 4.4 |
Consistency is given for file data.
ACSLS
Version | Client | Server | RDS | GUI |
---|---|---|---|---|
Oracle (StorageTek) Note3 | 4.4.3.84 Beefalo V2 |
StorageTek Automated Cartridge System Library Software as of Release 8.3. For earlier versions please contact us.
SEP DataMover must be Oracle Linux/Red Hat Enterprise Linux 6.3 or 6.4.
Hyper-converged Infrastructure
Nutanix
Nutanix with VMware | SEP VMware agent can be used |
Nutanix with Hyper-V | SEP Hyper-V agent can be used |
Nutanix with Citrix Hypervisor | SEP Citrix agent can be used |
Nutanix AHV (Acropolis) | New SEP agent under development |
HPE
SimpliVity with VMware | SEP VMware agent can be used |
Software Defined Storage
SUSE
SUSE | SUSE Enterprise Storage (SES) |
Thomas Krenn
Thomas Krenn | Thomas-Krenn SES Appliance |
Red Hat
Red Hat | Red Hat Ceph Storage |
Object Storage
As of version 5.0.0.x Jaglion, SEP sesam supports S3 as a generic interface based on the new deduplication store Si3 NG.
Some S3 targets are already supported, others have been looked at in more detail (see list below) and are currently being tested.
Vendor | Type | Status Notea |
---|---|---|
AWS | S3 Public Cloud | Supported |
Clyso | S3 Public Cloud | Supported Notec |
Ebertlang | S3 Public Cloud | Certified |
IBM Cloud | S3 Public Cloud | Supported |
Wasabi | S3 Public Cloud | Certified |
DataCore Swarm | S3 Local Object Storage | Supported Noteb |
Huawei OceanStor Pacific | S3 Local Object Storage | Supported Notec |
MinIO | S3 Local Object Storage | Supported |
Nutanix Objects | S3 Local Object Storage | Supported Noteb |
PureStorage FlashBlade | S3 Local Object Storage | Supported |
Vendor | Type | Status |
---|---|---|
Microsoft Azure | Blob Storage | Supported Noteb |
SEP sesam Si3 NG can be used with various S3-compatible cloud implementations. The configuration and management of Si3 NG in an S3-compatible cloud implementation is similar to the example shown in Backup to S3 Cloud Storage. Note, however, that only some S3-compatible cloud environments have already been validated by SEP, while others may not work in some cases. You are solely responsible for using SEP sesam in a non-S3 compatible cloud environment and agree that SEP shall not be responsible for it.
Supported as of ≥ 5.0.0.9 Jaglion V2.
Supported as of ≥ 5.1.0.7 Apollon.