eNAS Support Matrix for VMAX3 - hk.emc.com · EMC does not announce qualification prior to vendors’ General Availability (GA). In some cases, EMC may choose to perform regression

December-2016 Rev 18.1 Page 1 of 24 EMC Confidential

eNAS Support Matrix for VMAX3

December, 2016 V18.1

Copyright © 2016 EMC Corporation. All rights reserved. EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com. All other trademarks used herein are the property of their respective owners.


EMC Policies and Requirements for Open Systems Support Matrix This section describes EMC policies and requirements for any document characterized as an EMC Open Systems Support Matrix1. Purpose and Limitations of this Document This document is for informational purposes only and may change at any time. This version supersedes and replaces all previous versions. The information is to serve only as a guide for those configurations/products that EMC has qualified. This document identifies and lists various vendor host systems and integral components that have been tested and qualified by EMC for use with EMC products. Vendor components include, but are not limited to, host operating systems, host bus adapters (HBAs), associated drivers, firmware, and BIOS; Fibre Channel switches, hubs, and bridges. This document also lists various vendors’ software, cluster software, tape hardware, heterogeneous information storage, and configurations that EMC has tested and/or qualified for use with EMC products. The information included in this document is intended as a guide in the configuration of systems for EMC’s products. It is not intended to be the sole resource for system configuration. For more information or topics not found in this document, refer to relevant vendor documentation, or contact your EMC Sales or EMC Customer Support representative. Policies for Qualifying Systems Policies and procedures for support of EMC products are set forth in the customer’s applicable agreements. EMC’s publication of information relating to system configurations covers only those outlined in this document or by approval from EMC Engineering. Other system configurations not found in this document are not qualified without EMC engineering approval. EMC has qualified hardware and software provided only by the vendors listed in this document; host systems, hardware, and software from other vendors are not qualified, and may never be. Please contact your EMC Sales or EMC Customer Support representative for updates or information not included in this document. EMC maintains a large collection of products as well as third-party application software for qualification with EMC storage hardware and software to simulate customer environments, but you must consult the vendors for information about their system internals, such as hardware and associated drivers. Policy for Future Qualification of Operating System Software Releases The information in this document is maintained by EMC, and EMC strives to update this document with new releases of hardware, operating systems, firmware, BIOS, switch software, etc., as they become available from the vendors. EMC works with the vendors during their development and release processes in order to be fully informed at the time the vendors release new versions. EMC does not announce qualification prior to vendors’ General Availability (GA). In some cases, EMC may choose to perform regression testing following the vendors’ GA; in these cases and in cases where advance preparation is not possible, EMC may test and qualify vendors’ products as appropriate after they have been released. For early support of such products, including vendor beta participation, contact your EMC Sales or EMC Customer Support representative. Policy for End-of-Life Support EMC strives to continue support for any installed platforms, but may remove support from this host matrix for new installations within 3 months after the vendor has announced that this platform has reached the end of life. EMC will continue support for existing installations of hardware, operating systems, and components that the vendor has officially declared to have reached end of life as long as support is available from the vendor.

1 Documents characterized as an EMC Open Systems Support Matrix include any of the following: EMC Symmetrix Open Systems Support Matrix; EMC CLARiiON Open Systems Support Matrix; EMC CLARiiON Open Systems Configuration Guide; ESN Topology Design Guide; EMC Data Manager Interoperability Support Matrix; E-Lab Interoperability Navigator; and the EMC Software Support Matrix.


Table of Contents

Table 1: eNAS for File 8.1 limits .................................................................................................................... 4

Table 2 : eNAS IO (SLIC) Information ........................................................................................................... 4

Table 3: I18N Support Chart .......................................................................................................................... 5

Table 4: eNAS for File 8.1 Configuration Guidelines ..................................................................................... 6

Table 5: System Requirements for SnapSure and Replicator .................................................................... 12

System Requirements for SnapSure ................................................................................................................................................ 12 System Requirements for Replicator v2 .......................................................................................................................................... 12

Table 6: NDMP Backup Qualified Vendor Matrix (eNAS for File 8.1.4/.7/.10 only)..................................... 14

Table 7: Qualified Vendors for Heterogeneous 3-Way NDMP .................................................................... 18

Table 8: Qualified Tape Drives .................................................................................................................... 20

Table 9: NAS Connectivity ........................................................................................................................... 23

Table 10 : Anti-Virus .................................................................................................................................... 23


Table 1: eNAS for File 8.1 limits Following is a list of the version 8.1 eNAS for File capacity limits. Refer to the E-Lab™ Interoperability Navigator for the most up-to-date capacity limits.

eNAS for File version 8.1.10 capacity limit NAS for VMAX

VG10 VG50 eNAS VMAX 100K

eNAS VMAX 200K

VMAX 450F/FX

eNAS VMAX 400K

VMAX 850F/FX Usable IP Storage capacity per Data Mover (all disk types/uses)

256 TB 256 TB 256 TB 512 TB 512 TB

Max FS Size 16 TB 16 TB 16 TB 16 TB 16 TB Max # of FS per Data Mover2 2048 2048 2048 2048 2048 Max # of FS per system 4096 4096 4096 4096 4096 Max configured replications sessions per Data Mover for Replication for File3

1024 1024 1024 1024 1024

Max # of checkpoints per Production File System

96 96 96 96 96

Max # of NDMP sessions per Data Mover 4 8 4 8 8 Memory per Data Mover 6 GB 24 GB 6 GB 24 GB 24 GB Table 2 : eNAS IO (SLIC) Information

Model # Description FW Version E-FE00400C VMAX VG 4PT GBE BASE T 3.28 E-FE00200TC VMAX VG 2PT 10 GBE BASE T 6.2.17 E-FE00200TO VMAX VG 2PT 10 GBE OPTICAL 6.2.11 E-BK40000E VMAX VG FC BACKUP I/O FOR NAS

2 This count includes production file systems, user-defined file system checkpoints, and two checkpoints for each replication session 3 A maximum of 256 concurrently transferring sessions are supported per Data Mover


Table 3: I18N Support Chart

Encoding or Character

Set

Celerra Supplied

File

Conversion to UTF-8

Supported Not Supported Languages Covered RPQ Comments

NFS/ FTP Clients

Latin-1 8859-1.txt Yes File and directory names

• Mount point • Celerra File

Server Manager and Monitor

Most West European languages, such as French, Spanish, Catalan, Basque, Portuguese, Italian, Albanian, Rhaeto-Romanic, Dutch, German, Danish, Swedish, Norwegian, Finnish, Faroese, Icelandic, Irish, Scottish, and English, incidentally also Afrikaans and Swahili, thus in effect also the entire American continent, Australia and much of Africa.

No 8859-1.txt is standard and the same as the one on Unicode website.

Latin-9 8859-15.txt Yes Same as above

Same as above Same as above No Customers who require Euro sign support should get 8859-15.txt instead of 8859-1.txt

Latin-2 None Yes Same as above

Same as above Central and Eastern Europe: Czech, Hungarian, Polish, Romanian, Croatian, Slovak, Slovenian, Sorbian.

Yes The German umlauts äöüß are found at exactly the same positions in Latin1, Latin2, Latin3, Latin4, Latin5, Latin6. Thus you can write German+Polish with Latin2 or German+Turkish with Latin5.

Shift-JIS or EUC-JP

sjis.txt, eucjp1.txt, jp-euc.txt, jp-pck.txt

Yes Same as above

Same as above Japanese No • Customers should fill out detailed descriptions regarding their encodings in Celerra Qualifier.

• Engineering double check with local technical experts. Different variations of Shift-JIS and EUC-JP encodings exist.

Korean/KSC kr-uhc.txt No Same as above

Same as above Korean No Follow same procedure as Japanese.

GB or GBK GB2312.txt No Same as above

Same as above Simplified Chinese (Mainland China, Singapore)

No Follow same procedure as Japanese.

Big 5 Big5.txt Yes Same as above

Same as above Traditional Chinese (Taiwan, Hong Kong)

No Follow same procedure as Japanese

Other non UTF-8

encodings

None Yes Same as above

Same as above Depends on the specific encoding

Yes Needs RPQ

Unicode UTF-8 None No Same as above

Same as above All languages No Talk to us first to make sure

CIFS Clients

Unicode (UCS-2)

unidata2.txt and cp437.txt

Yes •File and directory names. •User, group and local group names.

•Share name. •Celerra File Server Manager and Monitor. •Share level security when I18N feature is on.

All languages No. • Win 95, 98, 2000, NT are supported.

• Windows release prior to Win 95 are not supported.

• 16-bit Unicode format is sent over the wire by Windows clients (negotiated). This is not to be confused with encodings used by Windows clients for display purpose which can be different.


Table 4: eNAS for File 8.1 Configuration Guidelines The values listed in this section represent the highest or lowest values tested by EMC. In some cases, actual capacities might exceed the capacities tested by EMC. Theoretical means in theory, not always practical. Refer to the E-Lab Interoperability Navigator for the most up-to-date information regarding these guidelines.

CIFS guidelines Guideline/ Specification

Maximum tested value

Comment

CIFS TCP connection

64K (default and theoretical max.), 40K (max. tested)

Param tcp.maxStreams sets the maximum number of TCP connections a Data Mover can have. Maximum value is 64K, or 65535. TCP connections (streams) are shared by other components and should be changed in monitored small increments. With SMB1/SMB2 a TCP connection means single client (machine) connection. With SMB3 and multi channel, a single client could use several network connections for the same session. It will depend on the number of available interfaces on the client machine, or for high speed interface like 10Gb link, it can go up to 4 TCP connections per link.

Share name length

80 characters (Unicode).

Unicode: The maximum length for a share name with Unicode enabled is 80 characters.

Number of CIFS shares

40,000 per Data Mover(Max. tested limit)

Larger number of shares can be created. Maximum tested value is 40K per Data Mover.

Number of NetBIOS names/compnames per Virtual Data Mover

509 (max) Limited by the number of network interfaces available on the Virtual Data Mover. From a local group perspective, the number is limited to 509. NetBIOS and compnames must be associated with at least one unique network interface.

NetBIOS name length

15 NetBIOS names are limited to 15 characters (Microsoft limit) and cannot begin with an@ (at sign) or a - (dash) character. The name also cannot include white space, tab characters, or the following symbols: / \ : ; , = * + | [ ] ? < > “. If using compnames, the NetBIOS form of the name is assigned automatically and is derived from the first 15 characters of the <comp_name>.

Comment (ASCII chars) for NetBIOS name for server

256 Limited to 256 ASCII characters. • Restricted Characters: You cannot use double quotation ("), semicolon (;), accent (`), and comma (,) characters within the body of a comment. Attempting to use these special characters results in an error message. You can only use an exclamation point (!) if it is preceded by a single quotation mark (’). • Default Comments: If you do not explicitly add a comment, the system adds a default comment of the form EMC-SNAS:T<x.x.x.x> where <x.x.x.x> is the version of the NAS software.

Compname length 63 bytes For integration with Windows environment releases later than Windows 2000, the CIFS server computer name length can be up to 21 characters when UTF-8 (3 bytes char) is used.

Number of domains

10 tested 509 (theoretical max.) The maximum number of Windows domains a Data Mover can be a member of. To increase the max default value from 32, change parameter cifs.lsarpc.maxDomain. The Parameters Guide for VNX for File contains more detailed information about this parameter.

Block size 64 KB Maximum buffer size that can be negotiated with Microsoft Windows


Guideline/ Specification


Comment

negotiated 128KB with SMB2

clients. To increase the default value, change param cifs.W95BufSz, cifs.NTBufSz or cifs.W2KBufSz. The Parameters Guide for VNX for File contains more detailed information about these parameters. Note: With SMB2.1, read and write operation supports 1MB buffer (this feature is named “large MTU”).

Number of simultaneous requests per CIFS session (maxMpxCount)

127(SMB1) 512(SMB2)

For SMB1, value is fixed and defines the number of requests a client is able to send to the Data Mover at the same time (for example, a change notification request). To increase this value, change wsathe maxMpxCount parameter. For SMB2 and newer protocol dialect, this notion has been replaced by ‘credit number’, which has a max of 512 credit per client but could be adjusted dynamically by the server depending on the load. The Parameters Guide for VNX for File contains more detailed information about this parameter.

Total number files/directories opened per Data Mover

500,000 A large number of open files could require high memory usage on the Data Mover and potentially lead to out-of-memory issues.

Number of Home Directories supported

20,000(Max possbile limit, not recommended)

As Configuration file containing Home Directories info is read completely at each user connection, recommendation would be to not exceed few thousands for easy management.

Number of Windows/UNIX users connected at the same time

40,000(limited by the number of TCP connections)

Earlier versions of the EMC NAS server relied on a basic database, nameDB, to maintain Usermapper and secmap mapping information. DBMS now replaces the basic database. This solves the inode consumption issue and provides better consistency and recoverability with the support of database transactions. It also provides better atomicity, isolation, and durability in database management.

Number of users per TCP connection

64K To decrease the default value, change param cifs.listBlocks (default 255, max 255). The value of this parameter times 256 = max number of users. Note: TID/FID/UID shares this parameter and cannot be changed individually for each ID. Use caution when increasing this value as it could lead to an out-of-memory condition. Refer to the Parameters Guide for VNX for File for parameter information.

Number of files/directories opened per CIFS connection in SMB1

64K To decrease the default value, change param cifs.listBlocks (default 255, max 255). The value of this parameter times 256 = max number of files/directories opened per CIFS connection. Note: TID/FID/UID shares this parameter and cannot be changed individually for each ID. Use caution when increasing this value as it could lead to an out-of-memory condition. Be sure to follow the recommendation for total number of files/directories opened per Data Mover. Refer to the System Parameters Guide for VNX for File for parameter information.

Number of files/directories opened per CIFS connection in SMB2

127K To decrease the default value, change parameter cifs.smb2.listBlocks (default 511, max 511). The value of this parameter times 256 = max number of files/directories opened per CIFS connection.

Active Directory Domain Controller

Authentication The SSPI establishes a SMB client connection to contact a Windows Active Directory Domain Controller. This connection is required for exchanging security information and for validating a user credential accessing a SMB server share with the NTLM authentication. Microsoft shipped the SMB2 protocol since Windows 2008 server OS in 2007. The SMB2 protocol is now widely used with Windows 2008R2, 2012, and 2012R2 server OS. Microsoft no longer supports XP and Windows 2003 servers supporting SMB1 protocol.




Comment

Number of VDMs per Data Mover

128 The total number of VDMs, file systems, and checkpoints across a whole cabinet cannot exceed 2048. The maximum number has not been tested.

Number of ntxmap User Mapping entries

1000

FileMover



comment

Max connections to secondary storage per primary (eNAS for File) file system

1024

Number of HTTP threads for servicing FileMover API requests per Data Mover

64 Number of threads available for recalling data from secondary storage is half the number of whichever is the lower of CIFS or NFS threads. 16 (default), can be increased using server_http command, max (tested) is 64.

File systems guidelines



comment

Mount point name length

255 bytes (ASCII) The "/" is used when creating the mount point and is equal to one character. If exceeded, Error 4105: Server_x:path_name: invalid path specified is returned.

File system name length

240 bytes (ASCII) 19 chars display for list option

For nas_fs list, the name of a file system will be truncated if it is more than 19 characters. To display the full file system name, use the –info option with a file system ID (nas_fs -i id=<fsid>).

Filename length 255 bytes (NFS), 255 characters (CIFS)

With Unicode enabled in an NFS environment, the number of characters that can be stored depends on the client encoding type such as latin-1. For example: With Unicode enabled, a Japanese UTF-8 character may require three bytes. With Unicode enabled in a CIFS environment, the maximum number of characters is 255. For filenames shared between NFS and CIFS, CIFS allows 255 characters. NFS truncates these names when they are more than 255 bytes in UTF-8, and manages the file successfully.

Pathname length

1,024 bytes Note: Make sure the final path length of restored files is less than 1024 bytes. For example, if a file is backed up which originally had path name of 900 bytes, and it is restoring to a path with 400 bytes, the final path length would be 1300 bytes and would not be restored. 1

Directory name length

255 bytes This is a hard limit and is rejected on creation if over the 255 limit.The limit is bytes for UNIX names, Unicode characters for CIFS.

Subdirectories (per parent directory)

64,000 This is a hard limit, code will prevent you from creating more than 64,000 directories.

Number of file systems per

4096 This max number includes VDM and checkpoint file systems.




comment

eNAS Number of file systems per Data Mover

2048 The mount operation will fail when the number of file systems reaches 2048 with an error indicating maximum number of file systems reached. This maximum number includes VDM and checkpoint file systems.

Maximum disk volume size

Dependent on RAID group (see comments)

eNAS systems —For eNAS systems, users might configure LUNs greater than 2 TB up to 16 TB or max size of the RAID group, whichever is less. This is supported for eNAS systems when attached to VMAX3 arrays.

Total storage for a Data Mover

512TB (raw) (256TB for the VMAX 100K)

On a per-Data-Mover basis, the total size of all file systems, and the size of all SavVols used by SnapSure must be less than the total supported capacity. Exceeding these limit can cause out of memory panic. Refer to the eNAS file capacity limits table for more information

File size 16 TB This hard limit is enforced and cannot be exceeded. Number of directories supported per file system

Same as number of inodes in file system. Each 8 KB of space = 1 inode.

Number of files per directory

500,000 Exceeding this number will cause performance problems.

Maximum number of files and directories per eNAS file system

256 million (default) This is the total number of files and directories that can be in a single eNAS file system. This number can be increased to 4 billion at file system creation time but should only be done after considering recovery and restore time and the total storage utilized per file. The actual maximum number in a given file system is dependent on a number of factors including the size of the file system.

Maximum amount of deduplicated data supported

256 TB When quotas are enabled with file size policy, the maximum amount of deduplicated data supported is 256 TB. This amount includes other files owned by UID 0 or GID.

All other industry-standard caveats, restrictions, policies, and best practices prevail. This includes, but is not limited to, fsck times (now made faster through multi-threading), backup and restore times, number of objects per file system, snapshots, file system replication, VDM replication, performance, availability, extend times, and layout policies. Proper planning and preparation should occur prior to implementing these guidelines.

Naming services guidelines Guideline/Specification Maximum tested

value comment

Number of DNS domains 3 - WebUI unlimited – CLI

Three DNS servers per Data Mover is the limit if using WebUI. There is no limit when using the command line interface (CLI).

Number of NIS Servers per Data Mover

10 You can configure up to 10 NIS servers in a single NIS domain on a Data Mover.

NIS record capacity 1004 bytes A Data Mover can read 1004 bytes of data from a NIS record.

Number of DNS servers per DNS domain

3


NFS guidelines Guideline/ Specification Maximum tested

value comment

Number of NFS exports 2,048 per Data Mover tested Unlimited theoretical max.

You might notice a performance impact when managing a large number of exports using Unisphere.

Number of concurrent NFS clients

64K with TCP (theoretical) Unlimited with UDP (theoretical)

Limited by TCP connections.

Netgroup line size 16383 The maximum line length that the Data Mover will accept in the local netgroup file on the Data Mover or the netgroup map in the NIS domain that the Data Mover is bound to.

Number of UNIX groups supported

64K 2 billion max value of any GID. The maximum number of GIDs is 64K, but an individual GID can have an ID in the range of 0- 2147483648.

Networking guidelines



comment

Link aggregation/ether channel

8 ports (ether channel) 12 ports (link aggregation (LACP)

Ether channel: the number of ports used must be a power of 2 (2, 4, or 8). Link aggregation: any number of ports can be used. All ports must be the same speed. Mixing different NIC types (that is copper and fibre) is not recommended.

Number of VLANs supported

4094 IEEE standard.

Number of interfaces per Data Mover

45 tested Theoretically 509.

Number of FTP connections

Theoretical value 64K By default the value is (in theory) 0xFFFF, but it is also limited by the number of TCP streams that can be opened. To increase the default value, change param tcp.maxStreams (set to 0x00000800 by default). If you increase it to 64K before you start TCP, you will not be able to increase the number of FTP connections. Refer to the Parameters Guide for VNX for File for parameter information.

Quotas guidelines

Guideline/Specification Maximum tested value Comment

Number of tree quotas 8191 Per file system Max size of tree quotas 256 TB Includes file size and quota tree size. Max number of unique groups 64K Per file system Quota path length 1024

Replicator V2 guidelines


Number of replication sessions per eNAS

1365 (NSX) 682 (other platforms)

Max number of replication sessions 1024 This enforced limit includes all


Guideline/Specification Maximum tested value Comment per Data Mover configured file system, VDM, and

copy sessions. Max number of local and remote file system and VDM replication sessions per Data Mover

682

Max number of loopback file system and VDM replication sessions per Data Mover

341

Snapsure guidelines


Number of checkpoints per file system

96 read-only 16 writeable

Up to 96 read-only checkpoints per file system are supported as well as 16 writeable checkpoints.

On systems with Unicode enabled, a character might require between 1 and 3 bytes, depending on encoding type or character used. For example, a Japanese character typically uses 3 bytes in UTF-8. ASCII characters require 1 byte.

Storage Group and Storage Pool Configurations In VMAX3, storage resource pool consists of number of disk groups and device (LUN) gets storage from these storage resource pools (SRP). Desired performance can be achieved from a device belonging to storage group by setting the service level objective (SLO). There is one to one mapping between backend device and eNAS disk. Device belongs to a specific storage profile/ storage pool (on eNAS) depending on the storage group and the advance data services set on that storage group. If device belongs to storage group on which either SRP or SLO is set then the device is identified on eNAS as part of mapped pool else it is identified as part of system defined pool called symm_dsl. Default storage group shipped with eNAS is “EMBEDDED_NAS_DM_SG”. Disk volumes of like storage profiles are used to configure volumes to be added to the AVM storage pools of the same name. File systems, savVols and other objects requiring disk space can use AVM to allocate space from the system defined pools with these names via the Unisphere or CLI. Table given below shows the relation between storage groups, storage pools/storage profile and eNAS disk type.

Is SLO set on SG ?

Is SRP set on SG ?

Storage Pool/ Storage Profile Disk Type/ Disk Group per SRP

eNAS Disk Type

YES YES mapped_pool (same name as SG) Single actual disk technology type per SRP (eg ATA) Multiple mixed

YES NO mapped_pool (same name as SG) Single actual disk technology type per SRP (eg ATA) Multiple mixed

NO YES mapped_pool (same name as SG) Single actual disk technology type per SRP (eg ATA) Multiple mixed

NO NO symm_dsl Single DSL Multiple DSL

Note: If SRP is not set on SG then it gets storage from default SRP.


Table 5: System Requirements for SnapSure and Replicator System Requirements for SnapSure

Following are the SnapSure system requirements:

• Total storage capacity per DM (including Replicator SavVol and SnapSure SavVol) should not exceed the

limits listed in the NAS Interoperability Matrix. • We recommend that a checkpoint file system in a production environment not be refreshed more frequently

than every 15 minutes. This recommendation is based on the Control Station load. System Requirements for Replicator v2

Following are the Replicatorv2 system requirements:

• NAS 5.6 or greater is required for Replicator v2. • Replicator works with any backend systems supported for Celerra and VNX File.. • Replication between DART 5.6.x and DART 6.x and VNX File 7.x and VNX 8.1 is supported with DART 5.6.47

and higher. • Total storage capacity per DM (including Replicator SavVol and SnapSure SavVol) not exceed the limits

listed in the NAS Interoperability Matrix. eNAS for File 8.1.4 • How to determine the number of available File system and VDMs per DM when using Replicator V2 2048 is the maximum number of file systems allowed per Blade/DM, See Table 1 for more details regarding file system limits. File system and VDM replication, each utilizes two additional file systems on the source (i.e. the two internal checkpoints) and three file systems on the destination, the target file system (or VDM if VDM replication) and its two internal checkpoints. Thus, an itemized list of what counts towards number of File system allowed on a DM:

File System count contributors (Max allowed 2048) Primary file system = 1 Destination file system = 1 Replication session = 2 per file system (i.e. 2 on source and 2 on destination) Local User Ckpt = 1 NDMP SnapSure Ckpt = 1

Note: NDMP SnapSure Ckpt consumption is transitory. The file system is consumed for the duration of the backup job.. Note: A VDM is a special Celerra /VNX/eNAS File software feature that creates a CIFS container. They enable users to administratively separate CIFS servers, replicate CIFS environments, and move CIFS servers from one Data Mover to another. Note: A single file system that is replicated to two target locations consumes two replication sessions. Example: A system replicating three file systems with no NDMP SnapSure Ckpt being used and no user ckpts configured will use nine FS IDs on the source and nine FS IDs on the target.


• Maximum number of remote data copies It is possible to create 16 remote copies by using 1-to-many to four locations and then cascading from each to three additional sites. See below. Source --> 1 --> 5, 6, 7 Source --> 2 --> 8, 9, 10 Source --> 3 --> 11, 12, 13 Source --> 4 --> 14, 15, 16 • Maximum number of remote data copies with copy session reserved at source site It is possible to create 12 remote copies by using 1-to-many to three locations and then cascading from each to three additional sites. See below. Source --> 1 --> 5, 6, 7 Source --> 2 --> 8, 9, 10 Source --> 3 --> 11, 12, 13 Source --> 4 (reserved for copy) The following notes also pertain to Replicator v2: eNAS for File 8.1.4, 8.1.7, 8.1.10 • Please remember that replication operations use checkpoint for internal use. Please account for potential

internal checkpoints in architecting your designs. • Asynchronous data recovery solution. In the event of a disaster, some of the updates made to the source file

system site may not be replicated the destination file system site. • A file system cannot be used as a TimeFinder destination filesystem and as a destination file system for

replication at the same time. Do not use the TimeFinder/FS -restore option for a file system involved in replication.

• TimeFinder/FS Restore is not supported. (fs_timefinder -Restore cannot be used for replicated file system.) However, you can restore per a single file basis using a NFS/CIFS client which has access to the source file system and the snap file system of the source file system.

• Destination file system cannot be mounted from multiple Data Movers. • Freeze/thaw activity that occurs on the destination file system during Replication may cause some

applications to time out. • Some applications may have limitations due to read-only access to destination file system(s) and caching,

locking, etc. on the source file system(s). • The replicated file system cannot be moved from Data Mover to Data Mover unless replication session is

stopped/deleted. • Replication supports stop and start, allowing network interfaces including IP address to be changed. • Replication relies on checkpoints for initial copy, maintaining SLA and maintaining common base on both

source and destination. Losing a common base will lead to full copy when the session is re-started. You should have sufficient SavVol available to checkpoint for these features to work.


Table 6: NDMP Backup Qualified Vendor Matrix (eNAS for File 8.1.4/.7/.10 only) NOTE: We support “backward” compatibility from one version of Celerra/VNX/eNAS File to another, e.g. from a VNX File 7.1 system, one can restore a backup done on a VNX File 7.0 system or a backup done on a Celerra DART 5.x or 6.x system. We do not support “forward” compatibility, e.g. a restore on a VNX File 7.0 system of a backup from a VNX File 7.1 system is not supported. In addition to what’s listed in this NDMP Backup Matrix, EMC will provide corporate support for applications where the following criteria have been met:

Note: The naming convention used in the descriptions below follows that of VNX File releases (M.m.J.P), where ‘M’ is Major, ‘m’ is minor, ‘J’ is Jumbo-patch and ‘P’ is Patch.

Generally, Major/Minor versions of NAS code or vendor applications that are newer/later than what is listed in the table below, are NOT supported by default. Re-qualification is usually required to re-affirm the supportability of our respective products given a Major/Minor version change. Generally, Jumbo-patch or Patch versions of NAS code or vendor applications that are newer/later than what is listed in the table below are supported by default. NDMP Vendor/Version Patches NDMP Capabilities (am) eNAS File Version

Ver. dump/ tar 3-way

(d) DAR DDS or SSO(e) eNAS File 8.1.4, 8.1.7, 8.1.10

CORE NDMP2D DDAR FIlters Int. Ckpts. NVB (VBB)

Tape Silvering

8 Streams (bk)

ASG Time Navigator v4.2 SPO P3267 4 dump/tar YES YES YES NO NO NO NO NO NO NO NO v4.2 SP6 P4461 (bm, bn) 4 dump/tar YES YES YES NO NO NO NO NO NO NO NO v4.3 4 dump/tar YES YES YES NO NO NO NO NO NO NO NO BridgeHead HT Backup v3.1.3 NDMP Agent (v, ay) 3 dump/tar YES YES YES NO NO NO NO NO NO NO NO v3.1.5 NDMP Agent (v, ay) 3 dump/tar YES YES YES NO NO NO NO NO NO NO NO v4.2 NDMP Agent (v, ay) 3 dump/tar YES YES YES NO NO NO NO NO NO NO NO v4.3 NDMP Agent (v, ay) 3 dump/tar YES YES YES NO NO NO NO NO NO NO NO v4.4 NDMP Agent (v, ay) 3 dump/tar YES YES YES NO NO NO NO NO NO NO NO

CA BrightStor ARCserve Backup (ay) v15.0 (bl) 4 Dump YES YES YES NO NO NO NO NO NO NO NO v16.0 SP1 (bl) 4 Dump YES YES YES NO NO NO NO NO NO NO NO v16.5 (bl) 4 Dump YES YES YES NO NO NO NO NO NO NO NO CommVault Simpana with NDMP v8.0 SP1 and updates 11638, 11823 4 Dump YES YES YES (x) NO NO NO NO NO NO NO NO v8.0 SP4 4 Dump YES YES YES (x) NO NO NO NO NO NO NO NO v9.0 4 Dump YES YES YES (x) NO NO NO NO NO NO NO NO v10.0 4 Dump YES YES YES (x) YES YES YES YES YES YES YES YES Dell NetVault v8.5, NDMP APM 7.1.11 4 Dump YES YES YES NO NO NO NO NO NO NO NO v8.5.2, NDMP APM 7.1.15 4 Dump YES YES YES NO NO NO NO NO NO NO NO v8.5.3, NDMP APM 7.1.16 4 Dump YES YES YES NO NO NO NO NO NO NO NO v8.6, NDMP APM 7.1.19 4 Dump YES YES YES NO NO NO NO NO NO NO NO v8.6.1, NDMP APM 7.6.3 4 Dump YES YES YES NO NO NO NO NO NO NO NO v8.6.3, NDMP APM 7.6.7 4 Dump YES YES YES NO NO NO NO NO NO NO NO v9.x, NDMP APM 7.6.11 4 Dump YES YES YES NO NO NO NO NO NO NO NO EDM with NDMP v5.1 2 Dump YES NO NO NO NO NO NO NO NO NO NO V5.1 with patch 9 (PE510_09) (ah, aq) 2 Dump YES NO NO NO NO NO NO NO NO NO NO EMC Avamar v5.0 (au,av) NOT QUALIFIED 4 N/A N/A (ax) N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A v5.0SP2 (au,av) NOT QUALIFIED 4 N/A N/A (ax) N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A v6.0 (au,av) NOT QUALIFIED 4 N/A N/A (ax) N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A v6.1 (au,av) NOT QUALIFIED 4 N/A N/A (ax) N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A v7.0 (au,av) QUALIFIED 4 N/A N/A (ax) N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A v7.1 (au,av) QUALIFIED 4 N/A N/A (ax) N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A EMC Networker with NDMP v7.5 4 dump/tar YES YES YES NO NO NO NO NO NO NO NO v7.6 (bd) 4 dump/tar YES YES YES NO NO NO NO NO NO NO NO v8.0 (bd) 4 dump/tar YES YES YES YES YES YES YES YES (ai) YES YES YES v8.1 (bd) 4 dump/tar YES YES YES YES YES YES YES YES (ai) YES YES YES


NDMP Vendor/ Version/ Patches NDMP Capabilities (am) eNAS File Version

Ver. dump/ tar 3-way (d) DAR DDS or

SSO(e) eNAS File 8.1.4, 8.1.7, 8.1.10

CORE NDMP2D DDAR FIlters Int. Ckpts. NVB (VBB)

Tape Silvering

8 Streams (bk)

EMC Networker Fast Start with NDMP v7.4 SP3 4 dump/tar YES YES YES NO NO NO NO NO NO NO NO HP OpenView Storage Data Protector

v6.1 4 Dump NO YES NO NO NO NO NO NO NO NO NO v6.11 4 Dump NO YES NO NO NO NO NO NO NO NO NO v6.2 4 Dump NO YES NO NO NO NO NO NO NO NO NO v7.0 4 Dump NO YES NO NO NO NO NO NO NO NO NO IBM Tivoli Storage Manager v5.5 4 Dump NO YES YES YES YES NO NO YES (ai) NO NO YES v6.1 4 Dump NO YES YES YES YES NO NO YES (ai) NO NO YES v6.2 4 Dump NO YES YES YES YES NO NO YES (ai) NO NO YES v6.3 4 Dump NO YES YES YES YES NO NO YES (ai) NO NO YES NEC WebSAM NetWorker v7.5 4 dump/tar YES YES YES NO NO NO NO NO NO NO NO v7.6 (bd) 4 dump/tar YES YES YES NO NO NO NO NO NO NO NO v8.0 (bd) 4 dump/tar YES YES YES NO NO NO NO NO NO NO NO Oracle Secure Backup v10.1.0.2 (aa) 4 Dump YES YES YES NO NO NO NO NO NO NO NO

v10.1.0.3 (aa, ak) 4 Dump YES YES (aj) YES NO NO NO NO NO NO NO NO

v10.2 (aa, ak) 4 Dump YES YES (aj) YES NO NO NO NO NO NO NO NO

v10.3 (aa, ak) 4 Dump YES YES (aj) YES NO NO NO NO NO NO NO NO

V10.4 (aa, ak) 4 Dump YES YES (aj) YES NO NO NO NO NO NO NO NO

Symantec Backup Exec v11d (11.0.7170) (an, ap) 4 Dump YES YES NO NO NO (ba) NO NO NO NO NO NO v12.0 (an) 4 Dump YES YES NO NO NO (ba) NO NO NO NO NO NO v12.5 (an) 4 Dump YES YES YES NO NO (ba) NO NO NO NO NO NO V12.5 SP3 (an,be,bf) 4 Dump YES YES YES NO NO (ba) NO NO NO NO NO NO V2010 (an,be,bf) 4 Dump YES YES YES NO NO (ba) NO NO NO NO NO NO V2010 R2 (an,be,bf) 4 Dump YES YES YES NO NO (ba) NO NO NO NO NO NO V2012 (an,be,bf, bp) 4 Dump YES YES YES YES YES (ba) YES YES YES YES NO YES V2014 (an,be,bf) 4 Dump YES YES YES YES YES (ba) YES YES YES YES NO YES Symantec NetBackup with NDMP ( c, bo ) V7.0 (bh, bi, bj) 4 dump/tar YES YES YES YES YES YES YES YES YES YES YES V7.1 4 dump/tar YES YES YES YES YES YES YES YES YES YES YES V7.5 4 dump/tar YES YES YES YES YES YES YES YES YES YES YES V7.6 4 dump/tar YES YES YES YES YES YES YES YES YES YES YES

v) HT Backup - Robot Manager version 3.4 or later is required if one plans to control the robot in a TLU via NDMP and the Celerra/VNX/eNAS/eNAS File Data Mover. x) If you have a license for SCSI-3 reserve with CommVault Simpana (5.9 and after) and you are planning to use it, then set param 'NDMP.scsiReserve' to zero on the Data Mover (NAS version 5.1 and after) where devices are connected.' aa) For optimum 3-Way backup performance, set PAX.readWriteBlockSizeInKB=128 on the NAS Server where tape devices are connected (mover server), and set blockingfactor and maxblockingfactor=256 in Oracle Secure Backup server. ah) Data Movers used with EDM need the following param settings: param NDMP bufsz=128 param readWriteBlocSizeInKB=128 ai) "There are two methods that can be used to enable "Integrated Checkpoints": - Enable this via the DMA (backup Vendor's software) using NDMP environment variable SNAPSURE=y - Enable this via the Celerra/VNX/eNAS/eNAS File Control Station and new NDMP parameter, snapsure. If the DMA SNAPSURE environment variable is not configured or supported, you can set the Celerra/VNX/eNAS/eNAS File NDMP snapsure parameter to use SnapSure. The DMA NDMP environment variable SNAPSURE, always overrides the Celerra/VNX/eNAS/eNAS File NDMP snapsure parameter. Please consult DART 5.5.25.2 release notes for additional information." aj) DAR restores of "files-only" are supported. For restores of directories or a mix of directories and files, only non-DAR operations are supported; The environment variable DIRECT=n must be configured from the OSB interface, to force non-DAR restores; Reference Oracle case 5837693.


ak) OSB 10.1.0.3 is unable to browse the catalog in the GUI for file or directory names containing the character "Line Feed (octal 12)", but these files and directories can be seen via command line; Reference OSB case 5837707. am) DART does not support backups and/or restores of files with absolute path length greater than 1023 characters. an) A restore of an empty backup, e.g. an incremental backup with no changes to the filesystem, fails. ao) Support for this capability is the default; DAR/DDAR can only be enabled/disabled together in Backup Exec ap) Cancelled or Failed NDMP backups will not be recoverable and will not be correctly marked as corrupt in the Backup Exec catalogs. Fixed, consult Backup Exec defect 999715. aq) EDM reached End of Service Life (EOSL) on June 30, 2007. After this date, EDM will only be supported for customers that have purchased an “extended support contract”. au) Avamar will fail if an attempt is made to restore only an empty directory. av) Foreign (i18n) characters in file and directory names may not render correctly in the Avamar Administrator UI, though they will be restored properly. ax) Entries in this column are relevant to homogeneous 3-Way operations only, i.e. transfers between an NDMP backup application and Celerra/VNX/eNAS/eNAS File Data Mover as a data server, to another Celerra/VNX/eNAS/eNAS File Data Mover as a tape server; note the data server and tape server must both be Celerra/VNX/eNAS/eNAS File Data Movers for homogeneous 3-Way. Avamar performs heterogeneous 3-Way only, i.e. transfers between Avamar NDMP backup application and Celerra/VNX/eNAS/eNAS File Data Mover as a data server, to Avamar tape server; note the data server is a Celerra/VNX/eNAS/eNAS File Data Mover but the tape server is not a Celerra/VNX/eNAS/eNAS File Data Mover. Avamar heterogeneous 3-Way qualifications are noted in the table "Qualified Vendors for Heterogeneous 3-Way NDMP". ay) Param NDMP.v4OldTapeCompatible must be set to 0 ba) The default signatures for NDMP2D robot and drives, i.e., vendor, product and revision values, must not be modified. These are "EMC, svtlRobot, 1.01", and "EMC, svtlDrive, 1.01" for NDMP2D robot and drives respectively. bd) The default value for NetWorker parameter "Volume block size" was changed in NetWorker 7.6.0 from 64KB to "Handler Default" value. Handler Default will be whatever device size is being used by other non-NDMP configured devices. This parameter value must be less than or equal to the Celerra/VNX/eNAS File parameter value for "readWriteBlockSize", which is 64KB by default, or users will be unable to perform basic tape functions like labeling. To resolve this problem, one must change parameter values in either NetWorker 7.6.0 or Celerra/VNX/eNAS File. Note that default Volume block size for NetWorker 7.6.1 will be set to 60KB and thus this value will work with Celerra/VNX/eNAS File readWriteBlockSize default. ERROR REPORTS: The following errors will be reported when running NDMP backup using NetWorker 7.6.0 with NetWorker parameter Volume block size greater than Celerra/VNX/eNAS File parameter readWriteBlockSize: Message in Celerra/VNX/eNAS File server_log: NDMP: 3: Specified record size (131072) is bigger than readWriteBlockSize(65536) NDMP: 3: Failed to start pax threads Message in NetWorker log: “nsrndmp_save: NDMP Service Error: Specified record size (131072) is bigger than readWriteBlockSize (65536), please refer to Celerra document on how to increase param PAX.readWriteBlockSize.” SOLUTIONS: To change the Volume block size value in NetWorker, within the NetWorker GUI in the NMC, go to the "devices" tab on the top bar, choose "devices" from left hand side menu, just below libraries. From there, on each tape drive, right click to choose properties. From Properties window, choose volume tab. In the volume tab window, on right hand side, change the value in "Volume block size". Note: No Celerra/VNX/eNAS File Data Mover reboot is required. To change readWriteBlockSize parameter in Celerra/VNX/eNAS File, use server_param server_# -f PAX -m readWriteBlockSizeInKB -v ### Note: This will require a reboot of the affected Celerra/VNX/eNAS File Data Mover for the parameter to take affect. be) Review Backup Exec TechNote 351783 to resolve a backup hang issue during tape spanning. bf) Backup Exec set copy jobs currently do not support VBB type backups. bg) Requires DART 5.6.50 or later to resolve a device discovery issue. bh) NetBackup may indicate that a restore has failed (Red-X indication in the GUI) while the restore is still progressing. bi) Filenames containing certain special characters may not be browse-able – reference Etrack 2072821. bj) Within a policy under the Schedule tab, one selects whether the backup will be of type Full, Differential Incremental, or Cumulative Incremental. The pull-down menu lists all three options but only the Full option is listed before Policy is closed. When the policy is run, it appears the backup will be whatever was selected, e.g. Differential or Cumulative Incremental. bk) DART 6.0, VNX 7.0, eNAS 8.1.4 and later now supports 8 streams per Data Mover but this requires a Celerra/VNX/eNAS File hardware platform that officially supports 8GBs or more of main memory on the Data Mover.


bl) When restoring a span session while there is no media information in the DB, ARCserve will set the window offset to a default value of 0x10000000 00000000. This may cause the restore to seek for a tape sequence that does not exist after hitting the span condition. Only data from the first sequence will be restored and the user will need to cancel the restore job. In order to successfully restore all data in the spanned session, the user will have to submit a merge job for that media and session number so ARCserve can repopulate the database with media information. This footnote is also posted to CA's support website as solution RI26869. bm) EMC DART versions do not manage Finite Size Window, so the Time Navigator variable NDMP_FINITE_SIZE_WINDOW_ON_TAPE_SPANNING should be set to default value 'No'. bn) At media dismount time, the EMC VTLU requires drive UNLOAD before library MOVE. Only library models handling this capability can be declared in ASG Time Navigator configuration; A few examples of these models are EMC Celerra VTL, Overland LXB. bo) eNAS 8.1.4 and later software requires hotfix 8.1.2.510 to work with Symantec NetBackup 7.x. bp) eNAS 8.1.4 and later software requires Symantec Backup Exec 2012 Service Pack 4 or higher. Required driver support can be found in "DDI 2012 20140320 MP3 212772”.


Table 7: Qualified Vendors for Heterogeneous 3-Way NDMP In addition to what’s listed in this matrix, EMC will provide corporate support for applications where the following criteria have been met:

Note: The naming convention used in the descriptions below follows that of Celerra/VNX/eNAS File releases (M.m.J.P), where ‘M’ is Major, ‘m’ is minor, ‘J’ is Jumbo-patch and ‘P’ is Patch.

Generally, Major/Minor versions of NAS code or vendor applications that are newer/later than what is listed in the table below, are NOT supported by default. Re-qualification is usually required to re-affirm the supportability of our respective products given a Major/Minor version change. Generally, Jumbo-patch or Patch versions of NAS code or vendor applications that are newer/later than what is listed in the table below are supported by default. “Heterogeneous 3-Way NDMP" capability has been qualified with the following vendors

Vendor/Versions/Patches NDMP Capability

eNAS File Versions

DAR eNAS File 8.1.4 8.1.7, 8.1.10

ASG Time Navigator

v4.2 SPO P3267 YES NO

v4.2 SP6 P4461 (t,u) YES NO

V4.3 YES NO

CA CAB v16.0 SP1 YES NO V16.5 YES NO CommVault Simpana 8.0 SP1 and updates 11638, 11823 YES NO 8.0 SP4 YES NO 9.0 YES NO 10.0 YES YES

Dell NetVault

v8.5, NDMP APM 7.1.11 YES NO

v8.5.2, NDMP APM 7.1.15 YES NO


v8.6, NDMP APM 7.1.19 YES NO



v9.x, NDMP APM 7.6.11 YES NO

Global Automation DinoStor v3.6.5 (j) YES NO EMC Avamar V5.0 N/A NO V5.0SP2 N/A NO V6.0 N/A NO V6.1 N/A NO V7.0 N/A YES V7.1 N/A YES EMC datadomain V5.0, V5.1, V5.2, V5.3, V5.4, V5.5 YES YES EMC NetWorker

v7.5 with Storage Node (DSA) YES NO


v8.0 with Storage Node (DSA) YES YES (m,n)

v8.1 with Storage Node (DSA) YES YES (m,n)

Vendor Versions/Patches NDMP


Capability

DAR eNAS File 8.1.4 8.1.7, 8.1.10

EMC NetWorker Fast Start

v7.4 SP3 with Storage Node (DSA) YES NO

IBM TSM

v5.5 YES YES v6.1 YES YES v6.2 YES YES v6.3 YES YES NEC WebSAM NetWorker




Quantum

GbE Pseries with MC350 and NDMP version 2.17 YES NO

Symantec Backup Exec v12.5 (o) YES NO v12.5 SP3 YES NO v2010 YES NO v2010 R2 YES NO v2012 YES YES (v) v2014 YES YES Symantec NetBackup v7.0 (q,r,s) YES YES (m,n) v7.1 YES YES (m,n) v7.5 YES YES (m,n) v7.6 YES YES (m,n)

Notes: j) The DinoStor Tape Server must be configured with only one data transfer interface enabled when used with EMC NetWorker. This is set via the DinoStor GUI under the page: configure/ndmp. Select the check box corresponding to the one single network intended to be used for backup data transfers. This is a best practice for all backup applications. Models supported are as follows: TS222L - 2 Gige port, 2 SCSI port, 2 drive license TS242L - 2 Gige port, 2 SCSI port, unlimited drive license TS241F - 2 Gige port, 1 2G FC port, unlimited drive license TS444L - 4 Gige port, 4 SCSI port, unlimited drive license TS442F - 4 Gige port, 2 2G FC port, unlimited drive license

m) Not qualified with NVB (VBB) n) Not qualified with Tape Silvering (TS)

o) A restore of an empty backup, e.g. an incremental backup with no changes to the filesystem, fails. q) NetBackup may indicate that a restore has failed (Red-X indication in the GUI) while the restore is still progressing. r) Filenames containing certain special characters may not be browse-able – reference Etrack 2072821. s) Within a policy under the Schedule tab, one selects whether the backup will be of type Full, Differential Incremental, or Cumulative Incremental. The pull-down menu lists all three options but only the Full option is listed before Policy is closed. When the policy is run, it appears the backup will be whatever was selected, e.g. Differential or Cumulative Incremental. t) EMC DART versions do not manage Finite Size Window, so the Time Navigator variable NDMP_FINITE_SIZE_WINDOW_ON_TAPE_SPANNING should be set to default value 'No'. u) At media dismount time, the EMC VTLU requires drive UNLOAD before library MOVE. Only library models handling this capability can be declared in ASG Time Navigator configuration; A few examples of these models are EMC Celerra VTL, Overland LXB. v) eNAS 8.1.4 software requires Symantec Backup Exec 2012 Service Pack 4 or higher. Required driver support can be found in "DDI 2012 20140320 MP3 212772”.


Table 8: Qualified Tape Drives NAS Engineering qualifies tape drives only and not TLUs. The following test should be used to determine if a particular TLU is supported with a particular backup application and Celerra/VNX/eNAS File:

IF the backup software vendor’s NDMP or LAN application is listed in the NSM as supported, AND the tape drive and any associated bridges are listed in the NSM as supported, AND the TLU, tape drive and any associated bridges are supported by the backup software vendor, THEN the TLU, tape drive and any associated bridges are supported.

ELSE the TLU is not supported.

Vendor/tape Drive SCSI (a) Fibre (a,i) SCSI/FC Connectivity (see

Legend below)

eNAS File Versions

eNAS File Versions

eNAS File 8.1.4, 8.1.7, 8.1.10 eNAS File 8.1.4, 8.1.7, 8.1.10

SE LVD (f) HVD Native

FC EMC datadomain (x) v4.8,

v4.9(j), v5.0, v5.1, v5.2, v5.4, v5.5

YES N/A N/A N/A TESTED

EMC EDL 210 Rev. 2.1.5/3.01/3.1 (j) YES NA NA NA TESTED

EMC EDL 300/700 Rev. 2.2

(j) (x) YES NA NA NA TESTED

EMC EDL 310/710 Rev. 2.0/ 2.1/2.2/3.0 (j) (q) (x) YES NA NA NA TESTED

EMC EDL 720/740 Rev. 2.0/2.1/2.2/3.0/3.1 (j) (x) YES NA NA NA TESTED

EMC EDL3D 1500 Rev. 1.01, 1.1 (j) (x) (aa) YES NA NA NA TESTED

EMC EDL3D 3000 Rev. 1.01, 1.1 (j) (x) (aa) YES NA NA NA TESTED

EMC EDL 4000 series Rev. 3.0/3.1/3.2 SP1/3.3 (j) (t) (x) YES NA NA NA TESTED

EMC EDL3D 4000 Rev. 1.1 (j) (x) YES NA NA NA TESTED

EMC EDL 5000 series Rev. 4.0 (j) (x) YES NA NA NA TESTED

Exabyte 85xx series &

Mammoth-2 YES NA A TESTED TESTED

HP LTO-1 Full-Height(h) NO NA TESTED A NA HP LTO-2 Full-Height (e) YES NA TESTED NA TESTED HP LTO-3 Full-Height (p) YES NA TESTED NA TESTED HP LTO-4 Full-Height (z) YES NA TESTED NA TESTED

HP LTO-4 Half-Height (ac) YES NA TESTED NA TESTED HP LTO-5 Full-Height (ae) YES NA TESTED NA TESTED HP LTO-5 Half-Height (ah) YES NA TESTED NA TESTED HP LTO-6 Full-Height(an) YES NA TESTED NA TESTED

HP SDLT 320 (r) N/A NA TESTED A NA HP SDLT 600 YES NA TESTED N/A TESTED

IBM Magstar 3590 YES NA NA TESTED TESTED

IBM 3592-E05 (TS1120) (s) YES NA NA NA TESTED IBM 3592-J1A (k) YES NA NA NA TESTED

IBM LTO-1 Full-Height (b) YES NA A TESTED TESTED IBM LTO-2 Full-Height (c) YES NA TESTED NA TESTED

IBM 3588 LTO-3 Ultrium Full Height (o) YES NA TESTED NA TESTED

IBM LTO-4 Full-Height (w) YES NA TESTED NA TESTED IBM LTO-4 Half-Height (ak) YES NA TESTED NA TESTED IBM LTO-5 Full-Height (ad) YES NA TESTED NA TESTED IBM LTO-5 Half-Height (aj) YES NA TESTED NA TESTED IBM LTO-6 Full-Height (al) YES NA TESTED NA TESTED

IBM LTO-6 Half-Height (am) YES NA TESTED NA TESTED


Vendor/tape Drive SCSI (a) Fibre (a,i) SCSI/FC Connectivity (see

Legend below)

eNAS File Versions

eNAS File Versions

eNAS File 8.1.4 8.1.7, 8.1.10

eNAS File 8.1.4 8.1.7, 8.1.10 SE LVD (f) HVD

Native FC

Quantum DLT 4000, 7000 YES N/A A NA TESTED NA Quantum DLT 8000 YES N/A NA A TESTED NA

Quantum DLT S4 (y) YES YES NA TESTED N/A TESTED Quantum SDLT 220 YES N/A NA A TESTED NA Quantum SDLT 320 (g) YES N/A NA TESTED A NA Quantum SDLT 600 (m) YES YES NA TESTED N/A TESTED

Quantum LTO-3 (ab) YES YES NA TESTED NA TESTED

Sony AIT-2 YES N/A NA TESTED NA NA Sony AIT-3 YES N/A NA TESTED NA NA Sony AIT-4 YES N/A NA TESTED NA NA

Sony S-AIT (l) NO YES NA NA NA TESTED

STK 9840A, 9940A YES YES NA NA TESTED TESTED STK 9840B, 9940B (d) NO YES NA NA NA TESTED

STK 9840C (n) NO YES NA NA NA TESTED STK 10000A (u,af) NO YES

(v) NA NA NA TESTED

STK 10000B (ag) NO YES (v)

NA NA NA TESTED

STK 10000C (ai) NO YES (v)

NA NA NA TESTED

STK 10000D (ao) NO YES (v)

NA NA NA TESTED

Notes: a) For specific connectivity information, refer to the backup connectivity drawings. An N/A indicates "Not Applicable" b) Min. firmware tested for IBM LTO-1 is 25D4 c) Min. firmware tested for IBM LTO-2 is 31MJ d) Min. firmware tested for StorageTek 9940B is .32.427 e) Min. firmware tested for HP LTO-2 is K342 f) A qualified SCSI to Fibre Channel bridge was used during the testing of LVD SCSI tape drives as Celerra uses SCSI HVD connectivity only g) Min. firmware tested for Quantum SDLT320 is 70 h) Min. firmware tested for HP LTO-1 is E370/007.040 i) This does not include connectivity with a bridge. Refer to “Qualified FC to SCSI Bridges” table for connectivity with a bridge. j) Support for this VTL with our backup vendors and Celerra/VNX/eNAS File is determined by the following test: IF the backup software vendor’s NDMP or LAN implementation is listed in the NSM as supported AND this VTL is listed in NSM as supported for the version of NAS required by the customer, AND the tape drive being emulated by this VTL is listed in NSM as supported, AND this VTL is supported by the backup software vendor, AND the tape drive and TLU being emulated by this VTL is supported by the backup software vendor, THEN this VTL is supported as a valid NDMP backup target device with Celerra /VNX File and the chosen backup software product, ELSE it is not supported. k) Min. firmware tested for IBM 3592-J1A is 03592J1A 04E6 l) Min. firmware tested for Sony S-AIT is 0200 FW:02.00.09 m) Min. firmware tested for Quantum SDLT 600 is 1E1E n) Min. firmware tested for StorageTek 9840C is 1.34.558 o) Min. firmware tested for IBM 3588 LTO-3 Ultrium –TD3 is 5481 p) Min. firmware tested for HP LTO-3 is L25S q) Any fibre switch used between these models of CDL v2.1 and Celerra/VNX/eNAS File must be either - non-Brocade or - Brocade switch with 4.x.x firmware or - Brocade switch with either 5.1.0a or 5.0.4a or later firmware r) Min. firmware tested for HP SDLT 320 is V82 s) Min. firmware tested for IBM 3592-E05 (aka TS1120) is D3I1_6E1 t) Dual server loop attach models present a Target and a Iniator port to the switch. Insure the Target port is zoned to the Celerra/VNX/eNAS File. The Target port can be identified via the CDL GUI. Go to the physical resources, highlight port attached and in the general tab,


the WWN port numbers and their function will be displayed (Target or Iniator ). u) Min. firmware tested for StorageTek 10000A is 1.32 v) This drive must be connected in a switched fabric configuration. Direct connect is not supported. w) Min. firmware tested for IBM LTO-4 is 74H4 x) Only switched fabric FC-SW is supported and not direct connect FC-AL y) Min. firmware tested for Quantum DLT S4 is 2222N z) Min. firmware tested for HP LTO-4 is H22S aa) - If EDL3D 1500/3000 are already discovered, and these devices are moved to a different switch on the same fabric they will not be rediscovered. A reinsertion or port enable/disable is needed to have the host rediscover these devices.

- On some Windows configurations the EDL3D 1500/3000 does not get discovered by the host if the switch is in auto detect mode. To resolve this, hard set the ports to fabric.

ab) Min firmware tested for Quantum LTO-3 was v20776316 -782 ac) Min firmware tested for HP LTO-4 Half Height was V51Z ad) Min firmware tested for IBM LTO-5 Full Height was A420 ae) Min firmware tested for HP LTO-5 Full Height was 124Z af) Min firmware version for StorageTek 10000A to support both L and N ports is 1.46.109. ag) Min firmware version tested for StorageTek 10000B was 1.46.209. This tape drive must be connected to an L-port capable switch to support arbitrated loop. Also, the L180 Tape Library Unit should have version 3.18.02 or better to identify this drive as T10000B instead of “unknown”. ah) Min firmware tested for HP LTO-5 Half Height was Y23Z ai) Min firmware tested for STK 10000C was R1.53.310f aj) Min firmware tested for IBM LTO-5 Half Height was A422 ak) Min firmware tested for IBM LTO-4 Half Height was B171 al) Min firmware tested for IBM LTO-6 Full Height was CB20 (For Spectralogic T380, firmware version 12.4.1-20130116F or later is required) am) Min firmware tested for IBM LTO-6 Half Height was CB21(For Spectralogic T50e, firmware version 12.4.3-20130125F or later is required) an) Min firmware tested for HP LTO-6 Full Height was J2AZ ao) Min firmware tested for STK 10000D was 4.07.104 SCSI/FC Connectivity Legend A = Available, i.e. connectivity offered by vendor but not tested NA = Not Available, i.e. connectivity NOT offered by vendor TESTED = Connectivity offered by vendor and we have tested


Table 9: NAS Connectivity

# NAS Platform

Operating Environment SW

Storage Array HYPERMAX OS Storage Operating Environment

Foot-notes

Notes (not published). Serves as a memory aid and instructions to the data entry person.

1 eNAS 8.1.4.15 VMAX 100K VMAX 200K VMAX 400K

5977.498.472

1 Uses a derivative of VNX File 8.1


5977.498.472 5977.596.583

1,2


5977.691.684

1 Indus Release

4 eNAS 8.1.7.702 VMAX 450F/FX VMAX 850F/FX VMAX 100K VMAX 200K VMAX 400K

5977.691.684.5560

1 Indus ePack for All-Flash support, but also applies to hybrid arrays as well

5 eNAS 8.1.10.21 VMAX 100K VMAX 200K VMAX 400K VMAX 450F/FX VMAX 850F/FX

5977.811.784

1 Hudson release

6 eNAS 8.1.10.26 VMAX 100K VMAX 200K VMAX 400K VMAX 450F/FX VMAX 850F/FX

5977.813.785 1 Hudson SR release to pick up Indus ePack changes

Footnotes

1. eNAS is the only NAS solution for VMAX3 and VMAX All-Flash arrays, there is no VNX Gateway (VG2/VG8,

VG10/VG50) support 2. eNAS 8.1.4.53 supports the baseline release 5977.498.472 up thrurelease 5977.596.583

Table 10 : Anti-Virus Vendor Latest Version Supported McAfee VirusScan

8.8i Patches 1-4

Symantec Protection Engine

7.5

Symantec Endpoint Protection

12.1 RU6

Microsoft SCEP

4.3, 4.5


F-Secure ESS

11.00.739

Kaspersky 8.0.0.559 Sophos AV 10.6