You are on page 1of 6

stornextnotes: 01-Stornext Concepts & Architechture

Page 1 of 6

Compartilhar

Denunciar abuso

Prximo blog

Criar um blog

Login

stornextnotes
Monday, June 23, 2008

01-Stornext Concepts & Architechture

Menu

Personal Class Notes


Topics Tiered Storage Information Lifecycle Management StorNext Architechture Storage management Concepts Data Integrity
00-index-Stornext File Manager 01-Stornext Concepts & Architecture 02-Software Installation 03-System-Overview 04-using-theconfiguration-wizard 05 Client Installation and Configuration 06 Administering managed File Systems 07 Policy Management 08 Managing Files 09 Library Operations 10 Data Protection and Recovery 11 Advanced Administration and Configuration 12 Maintenance and Diagnostics StorNext Documentation CLI Commands of Interest Recap and General Info

See Quantum's website for their pdf documents for release notes, install guides, user guides, file system tuing guide, upgrade guide, CLI reference guide, AMASS conversion guide, File System Quick Reference Guide, Storage Manager Quick Reference guide. It is important to note the supported/compatible Operating Systems, and also to determine how many (total) file systems are supported on one Metadata Server (MS) (they recommend no more than eight file systems on a single metadata server, yet some customers *do* exceed this and do not have significant problems). Stornext major products (abbreviated list) Stornext File System (aka "DSM", "D" stands for disk) Stornext Storage Manager File Manager (aka "TSM", "T" stands for tertiary) * (fileserv) Library manager (aka "MSM", "M" stands for media) (volserv) Stored in /usr/adic/dsm (goes to /usr/cvfs) * /usr/adic/tsm /usr/adic/msm * "cvfs" stands for "CentraVision file system", based on a legacy product that Quantum purchased.

Blog Archive 2010 (1) 2008 (18) August (1) June (17) Reverse-order-startat-00-indexStornext-FileMana... CLI-commands-ofinterest recap-and-generalinfo

http://stornextnotes.blogspot.com/2008/06/01-stornext-concepts-architechture.html

9/28/2011

stornextnotes: 01-Stornext Concepts & Architechture

Page 2 of 6

Commands applicable to above: cv commands, i.e. "cvfs" fs commands, i.e. "fsfmover" to copy data to tape vs commands, i.e. "vs[cmd] use above with "| grep [modifier]" to get specific results fsfileinfo is a useful command Note: fs[cmd] is for fs commands, fs_* is for processes. When installing stornext with the install script, there's are ".cshrc" and ".profile" file [in /usr/adic/.profile and /usr/adic/.cshrc] with useful aliases with a source command. Sourcing those two files is useful, or edit your default path as needed. The man pages on a StorNext clients are not immediately available. The man pages are available are on the server. (NOTE: Verify if the ".profile" has the man pages path to export the man path, it is there for SuSE, but verify for RHEL and others). source /path/to/.cshrc dsmup msmup tsmup - won't start until all else is started (the last thing that starts up, if this is running, all others ought to be running)

12-maintenance-and -diagnostics 11-advancedadministration-and -configuration 10-data-protectionand-recovery 09-library-operations 08-managing-files 07-policymanagement 06-administering managed-filesystems 05-client-installation -and-configuration 04-using-theconfigurationwizard

Log files /usr/cvfs/data//log/cvlog Tiered Storage and ILM Was once called "TDLM" - total data life mgt - not remarkably important, just info - however keep in mind that when installing SN mgr, a user called "tdlm" is a cron job to run log files" * Important Ensure rock-solid backups of metadata occur. SAN high speed shared file access (san clients) | p3 FC Disk (SNFS, StoreNext File System) SAN 'cloud' (fabric) connected to FC disk via fibre channel cable Hosts connected to SAN cloud, these are SAN Clients These are SNFS clients, SAN Clients SNFS server is a traffic cop that controls access) (aka FSS ->fsm, MDC, MDS) All this is intended to be a metadata network. It can be shared with other clients, however it's recommended to be at minimum GigE. Caution, can flood metadata server, could be a Bad ThingTM.

03-System-Overview 02-Software Installation pdfs 01-Stornext Concepts & Architechture 00-index-Stornext File Manager

About Me
D EV NU L L

I am a systems administrator servicing servers for customers who use Red Hat Enterprise Linux, SuSE

http://stornextnotes.blogspot.com/2008/06/01-stornext-concepts-architechture.html

9/28/2011

stornextnotes: 01-Stornext Concepts & Architechture

Page 3 of 6

Maximum performance would recommend not sharing metadata network with file access. Each file system must have a separate unique name, the FSS will have a single process for each file system. So 3 file systems = 3 processes (FSS). Was originally designed for large video, was changed for audio (great for movie industry). Information Lifecycle Mgt, Consolidated Tiered Storage Architecture. RAID < - > ATA Disk < - > Library (Tertiary) < - > Vault (tape) The "Library" level doesn't just have to be a tape library, it can also be a tiered disk (such as Hitatchi carved-up LUN) HSM high and low water marks work with this, the concepts for "high/low water marks" are the same for the StorNext Storage Mgr /usr/cvfs/config - in here is the configuration file, such as "snfs1.cfg datamigration value is set to "yes" If it's a managaged file system "datamigration" must be set to "yes" StoreNext Architecture | p4 Ethernet LAN, for Client/Server communications. Clients can be AIX, Cray, HP-UX, IRIX, Linux, OSX, Solaris, Windows Metadata servers Library San-connected storage devices p5 Provides HSM ability "demapi" interface, transparent mgt of SNFS, transparent to user. a user's file could be on disk or tape. Theoretical maximum file system size for 64-bit, is 2 to the 64th (18 exabytes). Your milage may vary due to OS limitations for file systems (some OS's limit to 2TB, such as Solaris). SN will support 512 Luns per stripe group 32 Stripe groups 512 x 32 = 16384 Luns ("Recommended max" 100TB, 100 million files) A 'cvfsck' will obviously take longer as one's file system increases. (one specific example, a 170 TB file system takes 10 hours to cvfsck). Some history - Physical limitations of database (metadata) (linter database) Version 2.7 - 100,000,000 (2 copies)

Linux, Solaris and Windows (all). I have worked with StorNext, but lately am working on other technologies primarily. View my complete profile Location of Visitors

http://stornextnotes.blogspot.com/2008/06/01-stornext-concepts-architechture.html

9/28/2011

stornextnotes: 01-Stornext Concepts & Architechture

Page 4 of 6

Version 2.8 - 400,000,000 (2 copies - they doubled it) Version 3.1.2 - 4 Billion

SNSM - 3 key points of Storage Manager. 1. Policy Class (part of the TSNM) Define where the file is written in Tertiary storage - Schedule policies to perform whatever tasks (such as backups to tape) 2. Policy Class Relationship (part of the TSM) (Tertiary) 3. Robotically controlled Library Management (MSM) Tape (Tape is cheapest) Files are written to Storage Disk, the same way they are written to tape. Access through Storage Manager Server only (not via clients) 4. (also Vault, tape library, where) Long-Term Data Mgt based on Levels of Service: - how a file is managed over time: [File] -> [Storage Management Policies] -> [RAID] - [ata disk] - [copy (Tape Library/Sdisk] - [Vault] 1. File comes in - goes to raid. Based on a policy, stays on raid for X days or months. 2. From RAID to Tape Library or Sdisk (perhaps after 6 months, or some other policy) 3. From Tape Library or Sdisk to "Vault" (tapes removed from tape library, placed perhaps in a box or vault someplace physically different). These files are still part of the StoreNext file system. Features: Versioning File Replication Steering Recovery Metadata copy automated full and partial database backup Fast file system recovery Integrity checks Checksum generation and validation [newly added, still being refined]

Raid & ATA is 'online' Disk to disk - is called relocation (not migration), it relocates the inode. Truncation keeps/retains the inode in the namespace, yet points to tape.

http://stornextnotes.blogspot.com/2008/06/01-stornext-concepts-architechture.html

9/28/2011

stornextnotes: 01-Stornext Concepts & Architechture

Page 5 of 6

HSM - StorNext Storage Manager is Quantum's instantiation for HSM. The database is an SQL database, a "Linter" database. Side Note: root@yoursystem # ls -ls 0 -rwxrwxr-x 1 someuser them 562 Jun 23 08:57 video_file01.mov (The "0" above left (red) shows this file was truncated (sent to tape by HSM) HSM Truncation is where the data blocks are "deleted" (but the file handle remains). Store Policy and Truncation Policy, these are different StorNext can deal with de-duplication. Scheduling tasks Full Partial Rebuild - run a utility to rebuild candidates list. Can schedule periodically, 1/week 1/month etc. make sure all files are part of the candidates list. Clean info - cleans files marked for removal, removes from file system, updates metadata. Caution, could take A LOT OF TIME if a lot of changes have occured. Clean versons - cleans versions at 10 versions Cron is used for rolling log files. RAS - Reliability, availability, servicability State capture - resembles cvgather command. gathers info needed for Quantum support folks Health Check - somewhat self-explainitory RAS ticketing - goes to an email of your choice. Lab -identify related components (StorNext Storage Management Configuration), Server host name, client quantities/host names/OS, Library tipe, drive, SAN components, raid Lun count, Lun sizes.
Posted by devnull at 9:27 AM

0 comments: Post a Comment Newer Post Home Older Post

http://stornextnotes.blogspot.com/2008/06/01-stornext-concepts-architechture.html

9/28/2011

stornextnotes: 01-Stornext Concepts & Architechture

Page 6 of 6

Subscribe to: Post Comments (Atom)

http://stornextnotes.blogspot.com/2008/06/01-stornext-concepts-architechture.html

9/28/2011