IBM blue-and-white template with image

1
(No Transcript)
2
File Services from a Customer View

• Customer concerns
• High availability
• Lower management overhead
• Scalability without disruption
• Security
• ...
• A glance at typical customer installations gtgtgt

3
Typical Server Environment, w/wo. SAN

• Customer concern If server fails, data is
  inaccessible.
• If storage 'dies', changed data since last backup
  is lost.

'Office' clients
LAN
SAN
Local disks
Note Disk drives storeblocks of bytes servers
interpret those as files.
4
Providing High Availability

• Clustering Fileserver with local or SAN storage
• Active/Standby or Active/Active (mutual failover)

LAN
LAN
Active
Standby
Active'
Active"
SAN
local
Disk'
Disk"
Standby server takes over disk service IP
address during active server failure.
Same, but vice-versa
5
Customer Headache

• Needs a cluster for every new service ()
• Complex setup and maintenance
• No easy scalabililty

LAN
SAN
6
Scaling Servers, Migrating Data

• Customers needs a bigger file server...
• A Copying data, shutdown, startup new
• B Shutdown, re-assigning SAN disk, startup

LAN
A
B
SAN
Always disruptive!
7
Migrating Data between Locations

• Data needs to be copied over a thin WAN
  connection
• Original data is subject to change while being
  copied
• gt Servers have to be shut down for significant
  time

WAN
100km
Always disruptive!
8
Customer Whish List

• Make services less hardware-dependent
• Consolidate hardware
• Migrate scale without disruption

LAN
File service
Web service
Print service
Enough hardware to handle it
Just enough storage
9
Stonehenge Architecture

• Services (Samba, Apache, Print, ) are "virtual
  servers"
• Each virtual server has it's own IP address

LAN
IP1
IP2
IP3
File
web
print
Distributed file storage layer
10
Stonehenge Architecture (2)

• Virtual servers are implemented on physical
  machineswithout (!) locally stored data

LAN
IP1
IP3
IP2
IP2
File
print
web
web
Several virtual servers residing on one node
Distributed file storage layer
Virtual servers can 'hop' between nodes
11
Stonehenge Architecture (3)

• Data is stored on hidden backend servers
• (SAN recommended)

LAN
IP1
IP2
IP3
File
web
print
Private LAN
Each virtual server can access any AFS server
Cell Cell
AFS server
AFS server
AFS server
"Disk owner" layer
12
Stonehenge Ingredients
Linux
Admin server
Admin
MySQL
LDAP

• Where they go

OpenAFS client
Linux
Samba
IP2
IP3
IP1
File
web
print
Apache
Endpoint'
OpenAFS client
AIX / Linux
AFS server
AFS server
AFS server
Endpoint"
OpenAFS server
13
Admin Console View
14
Example Datacenter Branch Offices Setup
User LAN
User LAN
User LAN
Physical (xSeries)
Disk cache
Disk cache
WAN
WAN
Private LAN
AFS (x/p-Series)
Branch Type 1 Site with cached access to
headoffice data local speed after first
access. Mainly for reading
Branch Type 2 Site with local storage as well as
cached headoffice access. Reading, writing and
replicating to from
SAN
Tape backup of branch sites using replica
15
Stonehenge TCO Savings Where?

• Scaling
• Migrating
• Backing up/Restoring
• Securing/Mirroring
• Administrating

16
Scaling Stonehenge

• Adding services (e.g. new file servers) affects
  the front layer
• Add node hardware only if required

LAN
IP1
IP3
IP5
IP2
IP4
File
File
web
print
File
File
Add hardware, redistribute services No Downtime

Distributed file storage layer
17
Migrating Data within Stonehenge

• Moving data is done in the backend
• Services are not affected

LAN
IP1
IP2
IP3
File
web
print
Private LAN or WAN
Cell Cell
As soon as data is synchronized, mirror copy
becomes original
AFS server
AFS server
AFS server
18
Example1 Datacenter adds Webservers

• Traditional method
• Move servers in, attach storage
• install configure web services
• Transfer data (1 day)
• With Stonehenge
• Define new virtual web server on hardware with
  resources left
• Add access rights to web files, configure web
  (15 min)
• Later
• Add hardware when resources are low

19
Example2 Company opens a new Subsidiary

• Traditional method
• Move servers into subsidiary, install storage
• install services
• Replay data from tape, fetch latest changes
  through WAN (1 week)
• With Stonehenge
• Move server hardware in, connect to wide area
  network
• Create or Move virtual servers from remote
  (1 day)
• Cached access to company data ok
• Later
• Add backend server storage for enabling replica
  etc.

20
Backup Strategy in Stonehenge with AFS
AFS server
AFS server
AFS server

• Point-in-time copy of volumes (backup volume)
• Replicate snapshot/backup volume to other
  location
• Backup to tape if requried

"Snapshot" at T1
AFS server
AFS server
AFS server
Copy of "Snapshot"
21
Tapeless Backup in Stonehenge with AFS
AFS server
AFS server
AFS server

• Dump volume content onto disk archive file (full
  or incremental)
• Keep dump archive files on disks for quick
  restore
• Dumping eliminates TSM "small files" performance
  bottleneck

1
2
This can be cheaper"nearline" storage
22
Securing/Mirroring Data in Stonehenge with AFS
AFS server
AFS server
AFS server

• Asynchronous Mirror
• Scheduled Replica
• Synchronous local Mirror
• Sync. SAN Failover Mirror
• Logical Volume Manager feature

AFS server
AFS server
AFS server


23
Stonehenge User Management

• Integration
• Automation
• Accounting

24
User/Client Management Integration

• Single Sign-on in existing Windows environment
• W2K Active Directory is managed from Stonehenge
• User Access rights used for AFS / Samba
• Samba DFS is integrated in Stonehenge
• OpenLDAP may be used instead of external Active
  Directory
• Option Active Directory may be synchronized with
  external LDAP
• ACL management Yes for Samba/Web No for NFS
  access
• But Attaching NFS clients through OpenAFS client
  plugin offers enhanced ACLs, better network
  utilization, persistent caching etc.

http//www.openafs.org/release/latest.html
25
User Management Automation LDAP Sync

• Employee newly hired
• Employee re-assigned
• Employee retires
• Minimum Admin Involvement!

26
Economies in User Management

• Each user has a home volume (Z\ or
  //mainz/afs/home_065432)
• ...with optional subfolders with older versions
• Z\
• MyDocuments
• MyDailyWork.doc 5.4.2003
• .oldfiles
• MyDailyWork.doc 4.4.2003 lt previous document
  version
• Unchanged_file.doc 1.2.2003 lt unchanged
  only a pointer
• Minimizes restore requests for accidentially
  deleted files!

27
Easy Planning Accounting

• Charge service users according to their virtual
  service traffic

28
Information Sales Material

• Intranet Event calendarw3.ais.mainz.de.ibm.com/
  stonehenge/
• Internet
• www-5.ibm.com/services/de/its/filestore.html/
• Support for new opportunities, sizing, etc.
  stonehenge_at_de.ibm.com
• Sales Material
• 2-page Customer Flyer (english)
• Several presentations see website
• 1-page ITS Customer Flyer (german)
• Demo software for Thinkpads Offline GUI
  emulation

29
Questions ?
30
Additional Information
31
Sample accounting output
afsfs01.sc.ais.mainz.de.ibm.com /vicepaa
RWrite 536871744 ROnly 0 Backup
0 MaxQuota 10240000 K Creation
Tue Jul 23 132201 2002 Last Update Fri Mar
14 144121 2003 0 accesses in the past day
(i.e., vnode references)
Raw Read/Write Stats ------------------
------------------------- Same
Network Diff Network
----------------------------------------
Total Auth Total Auth
----------------------------------
------ Reads 1719 1719
913 913 Writes 190 190
0 0
-------------------------------------------
Writes Affecting Authorship
-------------------------------------------
File Authorship Directory
Authorship -------------------------
--------------- Same Diff
Same Diff
---------------------------------------- 0-60
sec 36 0 45 0
1-10 min 0 0 1
0 10min-1hr 0 0
0 0 1hr-1day 0 0
0 0 1day-1wk 0
0 3 0 gt 1wk 0
0 1 0
-------------------------------------------
RWrite 536871744 number of sites -gt 1
server afsfs01.sc.ais.mainz.de.ibm.com
partition /vicepaa RW Site

• Storage space used maximum quota
• Bandwidth usedlocal remote
• Recent accesses

32
When you should consider Stonehenge

• 1 Running a Windows or DCE-DFS office
  environment
• 2 Looking for file- print-server consolidation
• 3 Looking for scalable NAS with disaster
  recovery
• 4 Managing many users (min gt 500)
• 5 Running branch offices that need
  interconnection
• 6 Concerned with storage migration
• 7 NOT running databases on fileservers or NAS!

33
Product availability

• Public beta in Germany since 1/2003
• Preview at CeBIT 3/2003
• Product availability since 8/2003
• Western and Northern Europe regional support in
  Q1-2004
• IBM service organization ITS offers standardized
  bundles
• Hardware, software, implementation, service
• Storage environment managed from remote

34
Beta-installation outside IBM (Jan.2003)

• Large German public sector federal bureau
• Stonehenge for 5000 users
• Customer's reason for choosing Stonehenge
• Security, inherent hack-proof
• Savings potential on daily administrative tasks

35
Upcoming reference installations outside IBM

• Large German Bank
• Pilot with few 1000 users, later extending to
  subsidiaries
• German Energy Provider
• With IT partner, migrating all WinNT users to
  Stonehenge
• Multinational Electronics Power Manufacturer
• Managed Storage, hardware in-house / management
  remote
• University
• Pilot for joint German universities project
• Many users
• ...

36
Traditional IT services
Stonehenge Goal
Robust load balancing
37
Stonehenge Ingredients

• Linux (SuSE, RedHat)
• Samba "Windows server under Linux", SMB protocol
• Apache Webserver for Linux
• OpenAFS Andrew File System
• MySQL Database, Sequential Query Language
• OpenLDAP 'Index', Lightweight Directory Access
  Protocol
• Kerberos Security system developed by MIT
• ...
• Stonehenge Admin server
• Endpoints (per node type)
• GUI

Assisted Components
Helper Applications
Core Components
38
Stonehenge, VMware, SVC, Storage Tank

• Stonehenge
• is a fileserver virtualization architecture
  including ACL, User-, DNS and DFS management,
  storage migration and mirroring tools. Use for
  many small (Windows etc.) office clients.
• VMware
• is a partitioning software for several virtual OS
  spaces on one Intel machine. Use for any
  application, but within one machine.
• SAN Volume Controller (Lodestone)
• is a storage re-organizer on LUN level, totally
  transparent to any application or OS. Includes
  migration, resizing, copying and mirroring tools.
  Performance and I/O handling is ok for databases.
• SAN Filesystem (Storage Tank)
• is a network filesystem where clients access
  shared files not through LAN, but through SAN.
  Clients need fibrechannel and a driver that
  handles file placement using policies. Use for
  high duty fibre clients.

39
Disclaimer/Trademarks
The sizing data contained herein was obtained in
a controlled environment based on the use of
specific data. Actual results that may be
obtained in other operating environments may vary
significantly. These values do not constitute a
guarantee of performance. Product data is
accurate as of initial publication and is subject
to change without notice. No part of this
presentation may be reproduced or transmitted in
any form without written permission from IBM
Corporation. References in this document to IBM
products, programs, or services do not imply that
IBM intends to make these available in all
countries in which IBM operates. Any reference
to an IBM program product in this document is not
intended to state or imply that only IBM's
program product may be used. Any functionally
equivalent program may be used instead. The
information provided in this document has not
been submitted to any formal IBM test and is
distributed "As Is" basis without any warranty
either express or implied. The use of this
information or the implementation of any of these
techniques is a customer responsibility and
depends on the customer's ability to evaluate and
integrate them into their operating
environment. Java is a trademark of Sun
Microsystems, Inc. in the United States and other
countries. Windows is a registered trademark of
Microsoft Corporation in the United States and
other countries.