24
1 Technical Report IBM Storwize V7000 and DCS3700 Value Solution Guide In collaboration with NetApp Mohinder Toor – [email protected] Rick Newland – [email protected] June 2012
1
Technical Report
IBM Storwize V7000 and DCS3700 Value Solution Guide In collaboration with NetApp Mohinder Toor – [email protected]
Rick Newland – [email protected]
June 2012
2
EXECUTIVE SUMMARY
This guide provides direction for IBM, NetApp and partner field teams as well as authorized IBM. This document is
intended to help those looking to provide their customers with leading edge solutions for their specific needs. The
solutions benefit from the rich functionality, great performance, scalability and reliability of the Storwize V7000,
coupled with the extreme expandable performance, scalability and high density of the DCS3700 storage system at
entry level prices.
The performance data covered in this guide does not in any way stress the storage systems to their full capabilities.
However, given the compute power available for the activity, the tests inevitably assist in broadly identifying the
best practice recommendations for both the Storwize V7000 and DCS3700 storage systems in various
configurations.
This report also provides value of the Storwize V7000 and DCS3700 with reference to solutions. Some of the
solutions outlined in this report have already been successfully integrated by IBM partners in EMEA and are in
constant use in the field. The aim of this report is to help provide guidance in best practices as well as equip our
IBM partners and their resellers to extend the benefits to our customer base.
This report also covers some of the other solutions that may benefit from the integration of IBMs DCS3700 outside
of the traditional HPC (High Performance Computing) environments. The DCS3700 is recommended and integrated
both as a ―Performance‖ and ―Performance & Capacity‖ solution within HPC, but this will NOT be covered as part
of the solution in this document.
3
CONTENTS
1. INTRODUCTION ………………………………………………………………………………… 4
2. Storwize V7000 plus DCS3700 – Best of Breed, Best of both worlds …………………………… 5
2.1. Storwize V7000 Features & Benefits ……………………………………………………….. 6
2.2. DCS3700 Features & Benefits ………………………………………………………………. 6
3. SOLUTION TYPES ………………………………………………………………………………. 8
3.1. Customers experiencing Data Explosion: Constrained by Budget, Rack Space ……………. 8
and Power & Cooling
3.2. Classic TSM Archive: Solution Opportunities ……………………………………………… 9
3.3. System Storage Easy-Tier Solution Opportunities …………………………………………. 10
3.4. LARGE CCTV & DVS: Solutions Opportunities ………………………………………….. 10
4. SOLUTION GUIDELINES ……………………………………………………………………… 12
4.1. Storwize V7000 & DCS3700 Value Solution ……………………………………………... 12
4.2. Large CCTV/DVS solution ………………………………………………………………… 13
4.2.1. Sizing Calculations …………………………………………………………………… 15
5. SOLUTION BENEFITS ………………………………………………………………………… 16
6. Storwize V7000 & DCS3700 SYSTEM CONFIGURATIONS ……….……………………….. 17
6.1. Overview ………………………………………………………………………………….. 17
6.2. Benchmark System ……………………………………………………………………….. 17
6.3. Test Suite Setup …………………………………………………………………………... 18
6.4. Results ……………………………………………………………………………………. 19
7. Storwize V7000 & DCS3700 BEST PRACTICE RECOMMENDATIONS …………………. 20
8. SUMMARY ……………………………………………………………………………………. 21
9. APPENDIX ……………………………………………………………………………………. 22
10. REFERENCES ………………………………………………………………………………… 23
11. ACKNOWLEDGEMENTS …………………………………………………………………… 24
4
1. INTRODUCTION
This guide focuses on using the strengths and benefits of the IBM Storwize V7000 and IBM DCS3700 storage
systems to provide a compelling list of ground breaking solutions that IBM and their Partners can leverage to
enable their customers to maximize on storage efficiency without compromising on any of the performance and
cost of ownership benefits.
The rich functionality and set of essential technologies of the IBM Storwize V7000 enables storage efficiency,
benefitting customer in three key areas:
- Maintaining and growing their data, observing storage efficiency by utilizing data compression and data de-
duplication features of the solution.
- Moving data to the right place, observing storage efficiency by utilizing Automatic and Policy Based
Tiering features of the solution.
- Storing more with what they have, observing storage efficiency by storage virtualization and thin
provisioning features of the solution.
The high density, small footprint and extreme performance advantages of the IBM DCS3700 also enable
storage efficiency. When used in conjunction with the IBM Storwize V7000, the customer may benefit further
in their ready and proven solutions from a cost competitive perspective. Customers will benefit, achieving a
faster return on investment due to:
- Achieving a greater capacity per floor tile
- A reduced $ per TB cost, as well as
- Reduced Power and Cooling costs
This guide quantifies the reduction benefits as a percentage compared to other traditional solutions.
5
2. IBM Storwize V7000 plus IBM DCS3700 – Best of Breed, Best of Both Worlds
The Storwize V7000 is a midrange storage system that is based on the IBM proven SVC storage technology. It
can virtualize external storage and has the following key capabilities:
Dual-active, hot-swappable controllers
o 8GB of cache per controller – 16GB total
o Eight 8 Gbps FC ports (Usage optional)
- For external storage
- And/or for server attachment
- And/or Remote Copy/Mirroring
o Four 1Gb or 4x1Gb and 4x10 Gb iSCSI ports (model dependant)
Latest SAS-2 6Gb technology
o SAS network for enclosure expansion
o SSD, 10K/15K SAS and Nearline SAS
o Maximum 240 disk drives using 2.5‖ drives
o Maximum 120 disk drives using 3.5‖ drives
o 2.5‖ SAS – 2/3/400GB SDD, 146/300/450/600GB/1TB HDD
o 3.5‖ SAS-NL – 2TB/3TB HDD
Unified storage platform – Block + File
ACE – policy driven Hierarchical Storage Management. This feature is only available with V7000 Unified
offering.
The DCS3700 is the new high density storage system designed for compute- and bandwidth- intensive
applications. It is IBM’s densest disk system with 60 disks in a dual controller 4U enclosure. It scales to 540TB
per system (3TB Disks) and satisfies most capacity requirement. The DCS3700 is modular by design and
supports custom configurations to meet performance or capacity requirements. It also has superior serviceability
and easy instillation with industry unique front loading drawers. Its design also boasts bullet proof reliability
and availability offering continuous high speed data delivery. The key capabilities include:
Dual-active, intelligent 6Gb/s x4 SAS controller architecture
o Support for RAID 0, 1/10, 3, 5, 6
Two 6Gb/s x4 SAS host ports per controller standard with optional connectivity:
o Two 6 Gb/s x4 SAS ports per controller
o Four 8 Gb/s FC ports per controller (includes eight 8Gb shortwave SFP transceivers)
4GB cache (2GB per controller) upgradeable to 8GB (4GB per controller)
o Mirrored, battery-backed, de-staged to flash on power loss
Highly dense 4U 60-drive enclosure
o Five horizontal drawers with 12 drives per drawer
Support for up to 180 2TB 6Gb/s SAS NL drives per system with the attachment
of two DCS3700 Expansion Units
o 20 drives minimum drive quantity per enclosure
Feature-rich DS Storage Manager with integrated premium features
o Eight partitions standard with upgrade options (16, 32, 64 and 128)
o Two FlashCopies standard with upgrade option for 8 FlashCopies plus Volume Copy
o Optional enhanced remote mirroring supports up to 16 remote mirror image pairs
across FC host ports
6
The two with their unique features and benefits complement each other and when selected to use in tandem
offer compelling solution benefits.
2.1. Storwize V7000 features and Benefits
Virtualization of data without data loss, including External Storage Virtualization
Easy-Tier: Automatic relocation of hot and cold extents
The Storwize V7000 Easy-Tier feature dynamically re-distributes active data across multiple tiers of
storage class based on workload characteristics. The goal being to minimize hot spots and reduce response
times!
Users have automatic and semi-automatic extent based placement and migration management.
Solid State Storage has orders of magnitude better throughput and response times, especially with random
reads. SSD’s were not available for the tests conducted and are therefore not part of the results at this time.
Thin Provisioning: Storwize V7000 allocates and uses physical disk capacity when data is written. This
feature supports all hosts with traditional volumes and all advanced functions including Easy-Tier.
2.2. DCS3700 features and Benefits
Extreme density ensures highest capacity per U for efficient use of floor space. The great capacity per
floor tile advantage is ideal for space constrained environments that offer footprint reduction as well as
savings in power and consumption.
Compared to the traditional 2U-12/24 enclosures the DCS3700 brings 10U down to 4U. See Figure 2.0
below:
Figure 2.0 – IBM DCS3700 4U60 comparison
7
Power and Cooling cost savings ensure substantial savings available with the solution giving the end-
customer substantial TCO (Total Cost of Ownership) advantages. See Figures 2.1 and 2.2 below, outlining
TCO advantages comparing fully populated 4U60 and 2U12 with 60 drives per solution.
Figure 2.1 – DCS3700 4U-60 Power & Cooling Calculations
Figure 2.2 – 2U12 Comparable Power & Cooling Calculations (60 Disks)
With just a single 4U-60 fully populated system there is greater than 3% power efficiency benefit in VA,
WATT, BTU/HR and Amps consumption. Depending on the cost of electricity with the installed
geography, this can translate into a substantial TCO advantage for the end-customer.
Typically the calculation to work out the cost advantage is:
{(Wattage x hours used / 1000) * price per Kwh} = Cost of Electricity
Enclosure Quantity VA Watts BTU/HR AMPS DCS3700 1 313.83 317.00 1,082.05 1.43 EXP 4U-60 0 0.00 0.00 0.00 0.00
Disk Drives Quantity VA Watts BTU/HR AMPS 2000 GB NL-SAS 60 594.00 600.00 2,048.04 2.70 1000 GB NL-SAS 0 0.00 0.00 0.00 0.00
None 0 0.00 0.00 0.00 0.00
Voltage VA Watts BTU/HR AMPS 220 907.83 917.00 3,130.09 4.13
This tool is designed to show maximum values for specified dual-controller configuration.
Totals
Enclosure Quantity VA Watts BTU/HR AMPS DS3512 1 137.02 138.40 472.41 0.62 EXP3512 4 277.20 280.00 955.75 1.26
Disk Drives Quantity VA Watts BTU/HR AMPS 2000 GB NL-SAS 12 104.54 105.60 360.46 0.48 2000 GB NL-SAS 48 418.18 422.40 1,441.82 1.90 2000 GB NL-SAS 0 0.00 0.00 0.00 0.00
Voltage VA Watts BTU/HR AMPS 220 936.94 946.40 3,230.44 4.26
This tool is designed to show maximum values for specified dual-controller configuration.
Totals
8
3. SOLUTION TYPES
As previously mentioned, this guide is intended to help those looking to provide their customers with leading
edge solutions to meet specific application needs. Utilizing the extensive IBM product portfolio and taking the
Storwize V7000 and the DCS3700 with their unique features and benefits that are complementary to each
provide an excellent solution base.
It is common knowledge that data volumes are exploding driven by social media, more devices and more
content been created. This trend is likely to continue and has been substantiated by almost all of the forecasting
agencies. Inexpensive storage makes it possible to keep more and for longer meeting the stringent and
conforming data retention directives companies are obliged to comply by.
The innovation of new and advanced software plus the advent of analytical tools that turn data into useful
information has also helped in excelling this trend.
A key requirement for customers to deal with this explosion in data is to have a good advanced analytical
strategy. Implementing any strategy requires lots of storage and in cases re-purposing existing storage.
This report outlines some of the solutions that that have been identified and in certain geographies successfully
implemented that other can also look into and benefit from:
3.1 Customers experiencing Data Explosion: Budget, Rack Space and Power & Cooling
Constrained.
The IBM top strategy for storage include: shrinking the data you have to store, so you stop storing so much;
moving the right data to the right storage technology to balance cost and performance; and getting more
utilization from the equipment you already have on the floor.
This is achievable by virtualizing the DCS3700 behind the Storwize V7000. The solution will allow you take
full advantage of the rich functionality, incredible ease-of-use and management as well as the great
performance, reliability and scalability of the Storwize V7000. This coupled with the high density, small
footprint and extreme performance of the DCS3700 you have a unique solution complementing both IBM
technologies that when implemented allows customer have a competitive edge over their completion that is
essential in today’s competitive market.
This solution of virtualizing the DCS3700 behind the Storwize V7000 has been successfully implemented with some
budget constrained opportunities within UKI. This guide helps provide some guidelines that are recommended for
consideration to help in identifying and spec’ing any such opportunities.
IBM Storwize V7000
SAN
100% Virtualized Storage
IBM DCS3700
Virtual Disks
9
As a ―Low Cost per TB‖ solution, consider deploying SSD and SAS 15K and 10K rpm drives exclusively within the
Storwize V7000. As a best practice recommendation only consider deploying small quantities of NL-SAS within the
Storwize V7000. The DCS3700 is ideal for deployment of NL-SAS, especially when large quantities are required.
3.2 Classic TSM Archive: Solution Opportunities
In line with the IBM top strategy for storage, one of the three aspects outlined above involves moving the data to the
right storage technology. This ensures a balanced cost and performance.
Below is a diagram of a typical solution that has been solved and used to customer satisfaction in the field.
The above setup offers an intelligent backup solution utilizing de-duplication as one of the many features within a
feature rich Storwize V7000 storage offering. This coupled with the performance and dense footprint of the
DCS3700 for storage plus the unique TSM (Tivoli® Storage Manager) attributes, the solution offers many
compelling advantages over competitor and traditional solutions. These benefits include Better Efficiency, Tighter
Control and Faster Recovery.
The standard method of backup used by TSM is progressive incremental. The terms differential and incremental are
often used to describe backups. A differential backup backs up files that have changed since the last full backup. An
incremental backup backs up only files that have changed since the last backup, whether that backup was a full
backup or another incremental backup. TSM takes incremental backup one step further. After the initial full backup
of a client, no additional full backups are necessary because the server, using its database, keeps track of whether
files need to be backed up. Only files that change are backed up, and then entire files are backed up, so that the
server does not need to reference base versions of the files. This means savings in resources, including the network
and storage.
24x7 availability of mission-critical data and applications is no longer a goal for today’s businesses — it’s a
necessity. The IBM TSM family of offerings is designed to provide centralized, automated data protection that can
help reduce the risks associated with data loss while helping to manage costs, reduce complexity, and address
compliance with regulatory data retention requirements. TSM enables you to protect your organization’s data from
failures and other errors by storing backup, archive, space management and bare-metal restore data, as well as
compliance and disaster-recovery data in a hierarchy of offline storage. Because it is highly scalable, TSM can help
protect computers running a variety of different operating systems, on hardware connected together on any storage
area networks (SANs). It uses Web-based management, intelligent data move-and-store techniques and
comprehensive policy-based automation that are working together to help increase data protection and potentially
decrease time and administration costs.
10
3.3 IBM® System Storage® Easy Tier™ - Solution Opportunities
The IBM Storwize V7000 also includes Easy Tier™ as another of their unique features available with the sub-
system. This unique feature responds to the presence of solid-state drives (SSDs) in a storage pool that may also
contain hard disk drives (HDDs) including SAS in both 15K and 10K revolutions per minute (rpm) as well as near
line (NL-SAS) at 7.2K rpm. The system automatically and non-disruptively moves frequently accessed data from
HDD MDisks to SSD MDisks, thus placing such data in a faster tier of storage.
Easy Tier eliminates manual intervention when assigning highly active data on volumes to faster responding storage.
In this dynamically tiered environment, data movement is seamless to the host application regardless of the storage
tier in which the data resides. Manual controls exist so that you can change the default behavior, for example, such
as turning off Easy Tier on storage pools that have both types of MDisks.
If you create a storage pool (managed disk group) with both generic SSD MDisks (classified with the generic_ssd
option) and generic HDD MDisks (generic_hdd or default option), Easy Tier is automatically turned on for pools
with both SSD MDisks and HDD MDisks. V7000 does not automatically identify external SSD MDisks; all external
MDisks are put into the HDD tier by default. You must manually identify external SSD MDisks and change their
tiers. To configure an external MDisk as an SSD MDisk, right-click the MDisk in the management GUI and click
Select Tier. Local (internal) MDisks are automatically classified as generic_ssd or generic_hdd and are placed in the
appropriate tier without user intervention.
3.4 Large CCTV & DVS Solution Opportunities
This is another opportunity where the unique features of both the Storwize V7000 and DCS3700 complement to
offer a value solution. The world of surveillance is growing. The world of physical security and surveillance is
becoming bigger and more important as both global threats increase and technology gets more advanced. Global
threats range from terrorism down to mere vandalism and surveillance deployments aren’t just to thwart these
threats and catch criminals but also to track customer behaviour in retail stores and traffic behaviour in cities. New
technologies such as 360 degree view cameras and motion tracking sensors are also creating more data than ever
before. Video management software has already been developed to handle the scale of all this new information;
recording video, audio, and data from 1000’s of cameras in geographically disperse environments all back to central
monitoring and recording for running analytics on all this new data. The problem created by all this new data is
scaling the infrastructure.
Analogue CCTV is still dominant. Sectors like retail, transportation, healthcare and government have immense
potential. There are new markets developing across the globe in Latin America, Asia, China, Middle East and
Eastern Europe. The paradigm shift is from analogue to Network based CCTV.
The three R’s of video surveillance describe how high performance storage must be foundational to a successful
large-scale video surveillance deployment.
Resolution – larger deployments mean more cameras. More cameras generate more video and increase the strain on
the infrastructure to transport and write all of the video feeds. Add to this, larger bandwidth requirements created by
higher resolution cameras and you quickly reach performance bottle necks on traditional network and storage
devices.
Retention – longer retention equals more storage. There is no way around it. If you need to keep more data for a
longer period of time, you need more disks to store them on.
Reliability – with a system of this importance and scale, downtime is not an option. Down time can mean missing a
criminal in act of committing a crime or not being able to supply key evidence to a trial. Furthermore, in the world
of analyzing trends and behavior, keeping more data leads to more accurate results.
11
Increasing the resolution and the number of cameras in the system directly equates to more bandwidth being
required in and out of the system. You don’t need just enough bandwidth for all the cameras to write, but also for the
analytics software and humans to play back the video. Longer retention periods directly equate to higher capacity.
The resolution and quantity cameras also require higher capacity, but if you go from a 7 day retention period to a 30
day period, that’s more the four times the storage requirement. Lastly, increased requirements for product reliability
directly equate to an enterprise class product. We all know that enterprise class doesn’t just mean the product itself.
While we can offer amazing up time and use all high quality parts, it’s the professional services and global, always
available, support that truly makes a solution enterprise class.
Below is a fairly typical block diagram of an IP-based video surveillance deployment.
There are five main components; the cameras, the servers running the applications, viewing workstations, storage,
and the network. All 5 pieces must work in harmony and take each other’s strengths and weaknesses into account
when designing a system. Refer to Solutions guideline session for sizing details.
12
4. SOLUTION GUIDELINES
4.1.Storwize V7000 plus DCS3700 Value Solutions
It is important to continue positioning the Storwize V7000 as a midrange storage offering with its enterprise class
and midrange packaging. This coupled with its rich functionality and feature rich architecture that includes it’s well
known and widely used Virtualization capabilities.
The virtualization capabilities of the Storwize V7000 add another competitive solution dimension for customers
constrained by Budget, Rack Space and Power & Cooling. How many Storwize V7000 opportunities have our
partners lost to the competition due to cost? This solution capability adds another dimension to our offerings that can
help us enhance our wins that we may have otherwise lost.
As a ―Low Cost per TB‖ solution, consider deploying SSD and SAS 15K and 10K rpm drives exclusively within the
Storwize V7000. As a best practice recommendation only consider deploying small quantities of NL-SAS within the
Storwize V7000. The DCS3700 is ideal for deployment of NL-SAS, especially when large quantities are required.
4.2. Large Closed Circuit TV (CCTV)/ Digital Video Surveillance (DVS) Solutions
The vast majority of the CCTV solutions can and have been filled adequately with the DS3500. We know of several
solutions in EMEA successfully integrated with iSCSI Host connectivity being in the forefront for small low cost
integrations. However, for large multi-PB requirements demanding high resolution, long retention times and high
enterprise reliability the DCS3700 on its own or as a combination with Storwize V7000 offering extreme value.
Increasing the resolution and the number of cameras in the system directly equates to more bandwidth being
required in and out of the system. For large, demanding systems you not only need to factor enough bandwidth for
all the cameras to write, but also the analytics software and humans to play back the video. This needs to be done in
parallel with fast response times for the system to meet with expectations.
Longer retention periods directly equate to higher capacity. The resolution and quantity cameras also require higher
capacity, but if you go from a 7 day retention period to a 30 day period, that’s more the four times the storage
requirement.
Increased requirements for product reliability directly equate to an enterprise class product. We all know that enterprise class doesn’t just mean the product itself. While we can offer amazing up time and use all high quality
parts, it’s the professional services and global, always available, support that truly makes a solution enterprise class.
13
Below is a list of parameters required in configuring a viable solution (See Figure 4.0)
Figure 4.0 – Parameters required for designing and calculating storage capacity
The vast majority of reputable CCTV vendors have their own tools specific to their product offerings. It is highly
recommended to utilize those tools in helping design and size the appropriate solution.
Typically, there are three simple steps in sizing a solution. These steps include i) identifying the video mode and
image size(s) ii) calculate the bandwidth and a first look at the required storage capacity iii) Calculate the overall
storage capacity, taking the ring, alarm, client and reserve requirements into account.
Below are examples of the three steps (See Figures 4.1, 4.2 and 4.3 below)
Figure 4.1 – Step 1: Identifying video mode and image sizing
Pos. CCTV Parameters, Values and Requirements Value
1 Camera video protocol (H.264, MPEG2, MPEG4, …) Required
2 Camera vendor (Arecont, Sony, Cisco, Bosch, …) Optional
3 Camara transfer protocol (IP, analog, 4CIF, …) Required
5 Video picture resolution (720x576 4CIF PAL, HD, FullHD, 1280x960, 1600x1200, …) Required
6 Frame rate, frames per second (fps) Required
7 Bandwith if available. Could be calculated. (800kbps, 1300kbps, 14 Mbps, …) Optional
8 No. of all cameras in CCTV infrastructure Required
9 No. of cameras in quite environment (office, stairways) Required
10 No. of cameras in medium environments (parking lot/atrium) Required
11 No. of cameras in busy environments (outdoor/trees&grass) Required
12 Percentage image complexity (minimum, medium, maximum) Required
13 Percentage motion detection activity within 24hrs (10%, 20%, …, 100%) Required
14 Storage duration time for the video ring buffer (hours, days, …) Required
15 Storage duration time for the video alarm recording (hours, days, …) Required
16 Client video workstations (No. of clients accessing video stream parallel) Required
17 Video server management software (NetAvis Observer, Siemens Fusion, …) Optional
18 Host transfer protocol (NFS, CIFS, iSCSI, FCP, …) Required
19 Mirroring required (Host or storage based) Required
Video Compression Modes H.264 / MPEG-4 / MPEGAll image sizes are for 50% Image Complexity, 50% Motion and 15 FPS
Camera Resolution CompressionSize of Image
(KByte)
MPEG (big image size, highes bandwith)704x480 (4CIF, NTSC) MPEG-10 High Quality 51,0
704x480 (4CIF, NTSC) MPEG-20 Good Quality 41,0
704x480 (4CIF, NTSC) MPEG-30 Average Quality 36,0
704x480 (4CIF, NTSC) MPEG-50 Low Quality 28,0
704x576 (4CIF, PAL) MPEG-10 High Quality 61,0
704x576 (4CIF, PAL) MPEG-20 Good Quality 50,0
704x576 (4CIF, PAL) MPEG-30 Average Quality 43,0
704x576 (4CIF, PAL) MPEG-50 Low Quality 33,0
1280x720 (HD) MPEG-10 High Quality 139,0
1280x720 (HD) MPEG-20 Good Quality 113,0
1280x720 (HD) MPEG-30 Average Quality 97,0
1280x720 (HD) MPEG-50 Low Quality 76,0
1280x1024 (1,3 MP) MPEG-10 High Quality 198,0
1280x1024 (1,3 MP) MPEG-20 Good Quality 160,0
1280x1024 (1,3 MP) MPEG-30 Average Quality 138,0
1280x1024 (1,3 MP) MPEG-50 Low Quality 108,0
1920x1080 (Full HD) MPEG-10 High Quality 314,0
1920x1080 (Full HD) MPEG-20 Good Quality 253,0
1920x1080 (Full HD) MPEG-30 Average Quality 218,0
1920x1080 (Full HD) MPEG-50 Low Quality 171,0
14
Figure 4.2 – Step 2: Calculating bandwidth and 1
st look at the required storage capacity
Figure 4.2 – Step 3: Calculating the overall storage capacity
It is highly recommended to use the vendor sites for sizing the opportunities. You may also want to reference some
third party sites for your sizing that comply by the Joint Video Surveillance Group. This is a universal global
standard and may require a license to prescribe.
4.2.1. Sizing Calculations
Network Bandwidth (MB/s) of a single Camera:
Bandwidth (MByte/s) = [Picture Size (KByte) * Frames per Second (FPS) / 1024]
Storage Capacity (GB) of a single Camera with 24 hours non-stop recording time:
Capacity (GByte) = [Picture Size (KByte) * Frames per Second (FPS) / 1048576 ] *(24*3600)
Storage Sub-System Usable Capacity Formula:
Capacity SUM (Gbyte) = (# of Data Drives * Disk Capacity * 0.93) * (# of Arrays)
Note: Recommendation is to configure 1 x volume per Array for optimal performance
Example: For 6 x R6 (8+P+Q) array configuration with 3TB NL-SAS drives -> Capacity = 24TB x 0.93 x 6 = 133.92TB
Example: For 2 x R5 (4+1) array configurations using 3TB NL-SAS drives -> Capacity = 12TB x 0.93 x 2 = 22.32TB
Frame / PictureSize
Frames perSecond
Number of Cameras
DurationTime
Daily Recording
Motion Detection during Recording
Image Complexity
Bandwidth Bandwidth Bandwith BandwithStorageCapacity
StorageCapacity
StorageCapacity
KByte FPS No. Days Hrs % % kbits/s Mbits/s kBytes/s MBytes/s GByte TByte PByte
11 15 700 120 24 100 100 924.000,00 924,00 115.500,00 112,79 1.142.028,81 1.115,26 1,09
17 15 300 120 24 100 100 612.000,00 612,00 76.500,00 74,71 756.408,69 738,68 0,72
12 25 100 90 24 50 100 240.000,00 240,00 30.000,00 29,30 111.236,57 108,63 0,11
8 11 80 90 24 75 100 56.320,00 56,32 7.040,00 6,88 39.155,27 38,24 0,04
27 23 330 90 12 75 100 1.639.440,00 1.639,44 204.930,00 200,13 569.892,77 556,54 0,54
21 23 120 90 12 75 100 463.680,00 463,68 57.960,00 56,60 161.181,79 157,40 0,15
0 0 0 0 24 100 100 0,00 0,00 0,00 0,00 0,00 0,00 0,00
0 0 0 0 24 100 100 0,00 0,00 0,00 0,00 0,00 0,00 0,00
0 0 0 0 24 100 100 0,00 0,00 0,00 0,00 0,00 0,00 0,00
0 0 0 0 24 100 100 0,00 0,00 0,00 0,00 0,00 0,00 0,00
0 0 0 0 24 100 100 0,00 0,00 0,00 0,00 0,00 0,00 0,00
0 0 0 0 24 100 100 0,00 0,00 0,00 0,00 0,00 0,00 0,00
0 0 0 0 24 100 100 0,00 0,00 0,00 0,00 0,00 0,00 0,00
0 0 0 0 24 100 100 0,00 0,00 0,00 0,00 0,00 0,00 0,00
0 0 0 0 24 100 100 0,00 0,00 0,00 0,00 0,00 0,00 0,00
0 0 0 0 24 100 100 0,00 0,00 0,00 0,00 0,00 0,00 0,00
0 0 0 0 24 100 100 0,00 0,00 0,00 0,00 0,00 0,00 0,00
0 0 0 0 24 100 100 0,00 0,00 0,00 0,00 0,00 0,00 0,00
0 0 0 0 24 100 100 0,00 0,00 0,00 0,00 0,00 0,00 0,00
0 0 0 0 24 100 100 0,00 0,00 0,00 0,00 0,00 0,00 0,00
0 0 0 0 24 100 100 0,00 0,00 0,00 0,00 0,00 0,00 0,00
0 0 0 0 24 100 100 0,00 0,00 0,00 0,00 0,00 0,00 0,00
0 0 0 0 24 100 100 0,00 0,00 0,00 0,00 0,00 0,00 0,00
1630 not used 3.935.440,00 3.935,44 491.930,00 480,40 2.779.903,91 2.714,75 2,65
Calculation for: 704x576 (4CIF, PAL), 15 FPS ring, no alarm, MPEG4-20 Good Quality
Buffer # of cameras Bandwith kbps Network Load Mbps Reading Speed MB/s Writing Speed MB/s Capacity TB Duration # Days / hrs Total Capacity TB
Ring buffer 700 1.320 902,34 112,79 9,29 per Day 120 1.115,26
Alarm buffer 0 0 0,00 0,00 0,00 per hour 0 0,00
Live viewing 20 1.320 25,78 3,22
Netto 1.115,26
Reserve % 10,00%
928,13 3,22 112,79 incl. Reserve 1.226,79
Calculation for: 704x576 (4CIF, PAL), 15 FPS ring, 25 FPS alarm, MPEG4-20 Good Quality
# of cameras Bandwith kbps Network Load Mbps Reading Speed MB/s Writing Speed MB/s Capacity TB Duration # Days / hrs Total Capacity TB
Ring buffer 330 1.320 425,39 53,17 4,38 per Day 90 394,32
Alarm buffer 100 2.200 214,84 26,86 0,09 per hour 24 2,21
Live viewing 10 1.320 12,89 1,61
396,54
Reserve % 25,00%
653,13 1,61 80,03 incl. Reserve 495,67
Calculation for: Put your text here
# of cameras Bandwith kbps Network Load Mbps Reading Speed MB/s Writing Speed MB/s Capacity TB Duration # Days / hrs Total Capacity TB
Ring buffer 0 0 0,00 0,00 0,00 per Day 0 0,00
Alarm buffer 0 0 0,00 0,00 0,00 per hour 24 0,00
Live viewing 0 0 0,00 0,00
0,00
Reserve % 25,00%
0,00 0,00 0,00 incl. Reserve 0,00
Blue cells are variables and parameters you will get from the customer and out of the two tables (Video Modes & Sizing CCTV) within this excel sheet.
15
5. SOLUTION BENEFITS
As already mentioned earlier in this document, the outlined solutions covered are outside of the HPC opportunities
where the DCS3700 benefits from high performance, dense footprint and low power and consumption are the key
compelling reasons for recommending this storage as a solution in that market space. The two compelling building
block solutions in HPC for the DCS3700 include i) Maximum Capacity and ii) Balanced Performance/Capacity.
Please refer to the IBM best practice guide for details in HPC as that’s not part of this guide.
It is important to remember that the Storwize V7000 with its feature rich functionality and architecture remains a
storage solution for the mid-range market segment. It continues correctly to be positioned as an enterprise class mid-
range platform with its virtualization capabilities. For customers constrained by budget or those demanding a dense
solution the Storwize V7000 can add another competitive dimension by utilizing its virtualization capabilities and
adding a DCS3700 behind it. This adds in available options to those already offered with the Storwize V7000.
Customers requiring Power and Cooling as a major criteria will also benefit from this solution. Enabling this
additional feature we feel will help ensure we can maximize on our midrange wins as the additional solutions add
another ―string to the bow‖ in our customers’ armoury.
16
6. Storwize V7000 & DCS3700 SYSTEM CONFIGURATIONS
6.1. Overview
As summarized in the executive summary, the performance data covered in this guide does not in any way stress the
storage systems to its full capabilities. However, given the compute power available for this activity, the tests
conducted will assist in identifying the best practice recommendations for both the Storwize V7000 and DCS3700
storage systems for all the solution types covered within this document.
The solutions covered in this guide work within a direct attach architecture as well as a SAN environment. For this
reason we have included the switch configurations that can be used as a reference in any instillations.
We have also outlined the performance results from individual volumes. Multiple identical tests were run with
varying volumes and system cache settings to determine the best performance settings both within the Storwize
V7000 and DCS3700.
The volume variations included the cache properties and segment size settings of the configured volumes. Cache
properties were inclusive of Read Caching, Write Caching, Write Caching With Batteries and Dynamic Cache Read
Prefetch. The Segment Size variations included the Segments Sizes, taking Optimal Stripe Width into consideration.
The System variations included Cache Block Size and Cache Flush Settings.
6.2. Benchmark System
DCS3700, No expansion trays
DCS3700 Firmware Version 07.77.19.00
SMclient Version SM 90.77.G0.00
Server x4140
Windows 2008
V7000 Block Head
SDDDSM x64 110328 Multi-path Driver
6.3. Test Suite Setup
The key configuration details of the SAN setup are identified below. These details include the profile summary and
the configuration layout of the test suite.
DCS3700 Storage Sub-System
Below is the profile summary from the DCS3700. The DCS3700 has no expansion trays. The controller firmware is
0.77.19.00 and SMclient version used is 90.77.G0.00 of Storage Manager. Highlighted in bold are some key features
recommended. The available server was the x4150 running Windows 2008 and IOMETER version 2006.07.27 as
the benchmark utility.
PROFILE FOR STORAGE SUBSYSTEM: ibsto37k01rk3s (Wed Apr 04 15:09:42 BST 2012)
SUMMARY------------------------------
Number of controllers: 2
High performance tier controllers: Enabled
Number of arrays: 6
RAID 6: Enabled
Total number of logical drives used: 7
Number of standard logical drives: 6
17
Number of access logical drives: 1
Total number of logical drives allowed: 512
Drive Limit Management:
Number of drive slots discovered: 60
Number of drive slots allowed: 180
FlashCopy Logical Drives: Enabled
Number of flashcopies used: 0
Number of flashcopies allowed: 2
Number of flashcopies allowed per base logical drive: 2
Solid State Disk Support: Enabled
Number of drives used: 0
Number of drives allowed: 20
Enhanced Remote Mirroring (ERM): Disabled/Deactivated
Number of mirrors used: 0
Number of mirrors allowed: 0
VolumeCopy: Disabled
Number of copies used: 0
Number of copies allowed: 0
Number of drives: 60
Mixed drive types: Enabled
Current media type(s): Hard Disk Drive (60)
Current interface type(s): Serial Attached SCSI (SAS) (60)
Total hot spare drives: 0
Standby: 0
In use: 0
Storage Partitioning: Enabled
Number of partitions used: 0
Number of partitions allowed: 8
Number of logical drives allowed per partition: 256
Access logical drive: LUN 31
Default host OS: IBM TS SAN VCE (Host OS index 12)
Current configuration
Firmware version: 07.77.19.00
NVSRAM version: N1818D37R0777V05
SMW version: 10.77.G5.28
Pending configuration
Staged firmware download supported: Yes
Firmware version: None
NVSRAM version: None
Transferred on: None
NVSRAM configured for batteries: Yes
Start cache flushing at (in percentage): 80
Stop cache flushing at (in percentage): 80
Cache block size (in KB): 8
Media scan frequency (in days): 30
Failover alert delay (in minutes): 5
Feature Enable Identifier (FEI): 3134383838203134393233204F3B6CDA
Feature pack: High Density Bundle
Feature pack sub-model ID: 162
Storage Subsystem world-wide identifier (ID): 60080E500023AB60000000004F3B6CC8
DCS3700, Storwize V7000 & X4150 Configuration Details
This section outlines the configuration of the arrays and logical drives within the DCS3700 level before presenting
them to the Storwize V7000. It is highly recommended that only one logical drive (volume) be created per array,
ensuring optimal performance. RAID 6 (8+P+Q) is the preferred RAID type and also commonly used within the
HPC environment.
18
The figure below (see Figure 6.0) outlines the typical disk layout as recommended and used within these tests.
Figure 6.0 – DCS3700 Disk Layout
The table below (see Figure 6.1) outlines the disk to array mappings as recommended and as used in this
configuration. The goal for the benchmark was to achieve a balanced configuration utilizing both available
controllers with a balanced workload between them.
Three logical drives (one logical drive per array) were allocated to each of the two controllers. This ensured that the
workload was evenly distributed between the two available and redundant controllers.
Figure 6.1 – DCS3700 Disk to Array Mapping
As already described in this document, the DCS3700 was configured with six logical drives in a RAID 6 (8+P+Q)
configuration. Three of these logical drives were allocated as primary to Controller A as their preferred controller.
The remaining three were configured with Controller B as their preferred controller.
The preferred ownership of a logical drive or array is the controller of an active – active pair that is designated to
―own‖ these logical drives. The preferred owner is the controller that currently owns the logical drive or the array. If
the preferred owner is being replaced or undergoing a firmware upgrade, ownership of the logical drives
automatically transfer to the other controller. The other controller becomes the current owner of the logical drives.
This change is considered a routine ownership change and is reported with an informational entry in the Event Log.
All six logical drives were presented to the Storwize V7000. The table below (see Figure 6.2) shows the
corresponding logical drives (now Mdisk) under V7000 i.e. LD0 = MD0, LD1 = MD4, LD2 = MD5 etc….
Under Storwize V7000, two pools (Pool 1 and Pool 2) were created comprising of three Mdisk per pool. Each pool
has Mdisk with preferred ownership to both the DCS3700 controllers’ i.e. Logical disks 0 and 2 have preferred
ownership to controller A and logical disk 1 has preferred ownership to controller B. All three logical disks are part
1 2 3 4 5 6 7 8 9 10 11 12
1 A A B B C C D D E E F F
2 A A B B C C D D E E F F
3 A A B B C C D D E E F F
4 A A B B C C D D E E F F
5 A A B B C C D D E E F F
T
r
a
y
#
Disk #
Controller A "owns" Arrays A, C & E
Controller B "owns" Arrays B, D & F
All Arrays R6 (8+P+Q)
19
of the same pool i.e. Pool 0. Similarly logical disks 3, 4 and 5 belong to the same pool (Pool 1) with access to both
DCS3700 controllers.
The switch was zoned ensuring both HBA ports within the x4150 running Windows 2008 had access to both Vdisk.
Zoning was done ensuring single initiator to single target.
Figure 6.2 – DCS3700, Storwize V7000 and x4150 Configuration Details
6.4. Results
IO was run simultaneously using IOMETER to both Vdisks. The IO pattern was both random and sequential for all
the tests. The DCS3700 constants for all the tests include a dual-active, turbo configuration with 2GB Cache
memory set to 80-80 cache flush setting. The controller firmware and NVSRAM was also not altered. The RAID
level was also set constant to RAID 6 (8+P+Q) throughout the tests.
The variables in the tests included using different cache block settings (4KB, 8KB and 16KB) for the controller
cache. All the test results were saved and recorded but only the best results are listed in this document that form the
basis of the best practice recommendations you may want to consider as a starting point for any instillation.
The cache parameters (Read Cache, Write Cache, Mirroring, Prefetch, PRRC) and segment size (4K, 8K, 16K, 32K,
64K, 128K, 256K and 512K) of the volumes were varied and results compared to work out the best configuration for
the mixed workload.
Below is a table (See Figure 6.3) of the best performance attained from the specific mixed workload including the
variable configuration settings used.
Figure 6.3 – Performance Figures per Volume
V7000 & DCS3700 - Segment Size = 256K
Test Pattern = Read 67%, Write 33%
DCS3700 - Cache ON
0%
0%
0%
0%
Sequential
100%
100%
100%
100%
100%
100%
100%
Read Cache
OFF
OFF
OFF
OFF
OFF
OFF
Random
0%
0%
0%
0%
100%
OFF
OFF
Write Cache
ON
OFF
ON
OFF
ON
OFF
ON
OFF
Cache Page
4
4
8
8
4
4
8
8
OFF
ON
OFF
ON
MB/s
686
650
821
724
Cache Mirror
ON
OFF
ON
OFF
943
228
236
IOPS
3472
2600
3284
2897
920
954
911
230
238
L_Disks P_Ctrl S.Size Mdisk Pool Vdisk P1 P2
LD0 CA 256 MD0 0 0 0,1 0,1
LD1 CB 256 MD4 0 0 0,1 0,1
LD2 CA 256 MD5 0 0 0,1 0,1
LD3 CB 256 MD6 1 1 0,1 0,1
LD4 CA 256 MD7 1 1 0,1 0,1
LD5 CB 256 MD8 1 1 0,1 0,1
DCS3700 V7000 x4150
20
7. Storwize V7000 & DCS3700 Best Practice Recommendations
Below is a chart (See Figure 7.0) outlining the variable configurations selected that provided the best results for the
configuration and workloads used. Please be aware that the storage was not stressed to its full capability as the
compute power available for the activity was restricted. We will endeavor to revise this document and add additional
information from any new tests that conduct as additional equipment becomes available.
We are looking to source the additional compute resource that will help baseline the maximum performance possible
both at the Storwize V7000 and DCS3700 level and also include SSD drives for the Storwize V7000 as part of the
test.
The results below are specific to the generated IO load and may vary in specific workload conditions. This
document in its current form is designed to provide guidance as the best configuration to aim before as a starting
point for most instillations and solutions outlined in this document.
Figure 7.0 – Configuration settings providing best performance for the given IO
V7000
Segment Size 256K
DCS3700
Segment Size 256K
Cache Page Size 8K
Read Cache ON
Write Cache ON
Cache Mirror ON
21
8. SUMMARY
This paper offers an insight to some solution offering our partners can enable over and above those already known
and implemented specifically around the hugely successful Storwize V7000 and the DCS3700. The solutions utilize
the unique and industry leading strengths of both the storage offerings that complement each other. The outcome by
complimenting the two, results in enabling IBM and their partners with yet other unrivaled solutions that will benefit
the install base at large.
This paper also provides some guidance that will help equip partners enable solutions in the field with the best
practice guidance as a starting point for any implementation.
22
9. APPENDIX
The DCS3700 supports IBM’s tradition of balanced and sustainable performance. Depending on the configuration, the sub-system is capable of
delivering up to 4000 MBps in bandwidth performance. For random application needs it is capable of up to 65K IOPs in sustained derive reads.
Unlike bandwidth, IOPS scales with the addition of disk drives – the more the number of ―data‖ disks the higher the overall expected IOPS. For
bandwidth specific applications, nearly 60 disks can achieve the full streaming bandwidth of a single DCS3700 system. Two DCS3700 units are
therefore nearly twice as fast as a single sub-system plus one expansion tray.
Sustained disk (as opposed to cache) is typically the real world performance requirement of the sub-system and is depended on the read and write
mix of the application type(s). Following are capabilities of the DCS3700 for this application type:
Sustained throughput disk read (512K) - capable of delivering 4000MBps throughput with turbo feature enabled
Sustained throughput disk write (CME 512K) - capable of delivering 1400MBps throughput with turbo feature enabled
Sustained I/O rate disk reads (4K) – capable of delivering 65K IOPS with turbo feature enabled in a fully populated configuration
Sustained I/O rate disk write (4K) – capable of delivering 15K IOPS with turbo feature enabled in a fully populated configuration
23
10.0 REFRENCES
IBMDSSERIES.COM site
http://ibmdsseries.com/
IBM Storage Offerings included in this guide
http://www-03.ibm.com/systems/storage/disk/?lnk=mprST-dsys
Video Surveillance Site – Useful Calculator Tool
http://www.axis.com/products/video/design_tool/calculator.htm
Video Surveillance Site
http://www.x-vision.co.uk/
Video Surveillance Bandwidth Calculator
http://www.arecontvision.com/supports/bandwidth-calculator
Video Surveillance Storage Calculator
http://www.arecontvision.com/supports/storage%20-calculator
SPC Performance Site
http://www.storageperformance.org/home/
IP Video System Design Software
http://www.jvsg.com/ip-video-system-design-tool/
CCTV Design Tool
http://www.jvsg.com/cctv-design-tool/
IBM Redbooks
http://www.redbooks.ibm.com/
24
11. ACKNOWLEDGEMENTS
The authors of this document would like to both acknowledge and extend thanks to the following team members for
making this guide possible:
Martin Bruce, Mid-Range Disk Sales Leader, STG (IBM)
Gary Gibbings, IBM Systems Engineer (AVNET)
Marco Pozzoni, IBM Business Development Manager – EMEA (NetApp)
