Unit/Project Name: Enterprise Technology Document Name: Tier 2 NetApp Baseline Design Standard Date: August 13 th 2009 Tier 2 NetApp Baseline Design Standard Directly Impacted Teams: X86 Servers Unix Servers Data Storage Data Networking Voice Services Monitoring Data Center Other____________ Scope: Enterprise Wide Alaska California Oregon Washington/Montana Other____________ Baseline Design Standard Summary The NetApp Filers provide tier 2 storage and are used primarily for file sharing. They utilize Active Directory for controlling access to the file shares. Each volume on the Filers corresponds to a share. Twice daily a NetApp snapshot is made of the volumes, and these snapshots are kept for 30 days. These snapshots are available for end user restore via the “Previous Versions” method available in the right-click menu on Windows clients. The Filers are also backed up to TSM six nights a week and these backups are kept for 90 days. Selective restore of files in the 30-90 day timeframe is available and requires an administrator to initiate the restore. Snapmirror is used to replicate filers between data centers. Replication can be used in lieu of TSM backups.
8
Embed
Tier 2 net app baseline design standard revised nov 2011
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Directly Impacted Teams: X86 Servers Unix Servers Data Storage Data Networking Voice Services Monitoring Data Center Other____________
Scope: Enterprise Wide Alaska California Oregon Washington/Montana Other____________
Baseline Design Standard Summary
The NetApp Filers provide tier 2 storage and are used primarily for file sharing. They utilize Active Directory for controlling access to the file shares.
Each volume on the Filers corresponds to a share. Twice daily a NetApp snapshot is made of the volumes, and these snapshots are kept for 30 days. These snapshots are available for end user restore via the “Previous Versions” method available in the right-click menu on Windows clients.
The Filers are also backed up to TSM six nights a week and these backups are kept for 90 days. Selective restore of files in the 30-90 day timeframe is available and requires an administrator to initiate the restore.
Snapmirror is used to replicate filers between data centers. Replication can be used in lieu of TSM backups.
In Alaska, we do have some Fibre Channel LUNS allocated on WAFL. The NetApp Snapdrive utility is the multipathing driver. (This use is not currently in favor, and presenting additional storage in this fashion in the future is not anticipated.)
The Base configuration: The filers are accessed by customers using the CIFS and NFS protocols. (AK,
TBC,RDC, and CA use is 95%+ CIFS.) Filers have two heads and are clustered for fault tolerance. Filers have redundant power supplies. Filers are managed with Data Fabric Manager ( OnCommand Core Package).
Considerations: The filers currently use TSM to coordinate the backups, store and retrieve the TOC
(table of contents), and as an interface for selective restore of files. The filers use SAN attached tape drives in the same tape pools as TSM. Volumes that do not need snapshots typically do not have them configured. This saves
space on the Filer.
Use CasesCase UsageTier 2 Storage Not recommended for FC connectivityTier 3 Storage Used for archive storage and disaster recoveryNAS CIFS Best File sharing platform for Windows because of
the snapshotting/replication and other integrated tools make them easy to upgrade expand/grow reduce/shrink shift data around easily
NFS Used as an Oracle platform that does not require High IO’s , gives you replication functionality and sharpshooting natively.
Used on UNIX platforms to give CIFS (windows) access to UNIX files.
Used on VMWare for its back end shared storage Excellent for this because of reduced space required because of De-duplication technology 50-70% Space Reduction without impact to performance.
Integrated dedupe and replication for DR.FTP server FTP functionality.Fibre Channel and Snapdrive Allows LUNS to be allocated on the filers and offered
over the SAN to hosts. The multipath driver is not as desirable as on other storage platforms. This tends to limit Fibre Channel use.
Multistore Allows Windows fileservers contents to be more easily moved onto filers. (No need to consolidate shares and folders to just the one filer.)
Baseline Design StandardsComponent Status Configurationa_sis Required Zero cost key for Dedupe.CIFS Required Windows file share protocol.Cluster Required Cluster for fault tolerance.iSCSI Required Zero cost key for iSCSI.Multistore Required Allows for multiple filers.Nearstore Required Required for a_sis.NFS Required NFS Protocol.Snapmirror Required Allows for replication.Snapmover Optional Allows moving volumes between
filer heads in the same cluster.Snaprestore Required Allows for fast restore of snaps.DFM (OnCommand)
Required Data Fabric Manager (OnCommand) handles alerting, performance management, and trending of Filers and storage.
Page 3 of 6
Baseline Design Standard Diagram
Page 4 of 6
Implementation Example
Page 5 of 6
Document DetailsDocument Name: Tier 2 NetApp Baseline Design Standard
Version Number: 1.2
Documentation Status: Working Draft Approved Change Requested