Beruflich Dokumente
Kultur Dokumente
Demo Guide
July 2015
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. The trademarks, logos, and service marks (collectively "Trademarks") appearing in this publication are
the property of EMC Corporation and other parties. Nothing contained in this publication should be construed as
granting any license or right to use any Trademark without the prior written permission of the party that owns the
Trademark.
EMC, EMC² AccessAnywhere Access Logix, AdvantEdge, AlphaStor, AppSync ApplicationXtender, ArchiveXtender,
Atmos, Authentica, Authentic Problems, Automated Resource Manager, AutoStart, AutoSwap, AVALONidm,
Avamar, Bus-Tech, Captiva, Catalog Solution, C-Clip, Celerra, Celerra Replicator, Centera, CenterStage,
CentraStar, EMC CertTracker. CIO Connect, ClaimPack, ClaimsEditor, Claralert ,cLARiiON, ClientPak, CloudArray,
Codebook Correlation Technology, Common Information Model, Compuset, Compute Anywhere, Configuration
Intelligence, Configuresoft, Connectrix, Constellation Computing, EMC ControlCenter, CopyCross, CopyPoint, CX,
DataBridge , Data Protection Suite. Data Protection Advisor, DBClassify, DD Boost, Dantz, DatabaseXtender, Data
Domain, Direct Matrix Architecture, DiskXtender, DiskXtender 2000, DLS ECO, Document Sciences,
Documentum, DR Anywhere, ECS, elnput, E-Lab, Elastic Cloud Storage, EmailXaminer, EmailXtender , EMC
Centera, EMC ControlCenter, EMC LifeLine, EMCTV, Enginuity, EPFM. eRoom, Event Explorer, FAST, FarPoint,
FirstPass, FLARE, FormWare, Geosynchrony, Global File Virtualization, Graphic Visualization, Greenplum,
HighRoad, HomeBase, Illuminator , InfoArchive, InfoMover, Infoscape, Infra, InputAccel, InputAccel Express,
Invista, Ionix, ISIS,Kazeon, EMC LifeLine, Mainframe Appliance for Storage, Mainframe Data Library, Max
Retriever, MCx, MediaStor , Metro, MetroPoint, MirrorView, Multi-Band Deduplication,Navisphere, Netstorage,
NetWorker, nLayers, EMC OnCourse, OnAlert, OpenScale, Petrocloud, PixTools, Powerlink, PowerPath,
PowerSnap, ProSphere, ProtectEverywhere, ProtectPoint, EMC Proven, EMC Proven Professional, QuickScan,
RAPIDPath, EMC RecoverPoint, Rainfinity, RepliCare, RepliStor, ResourcePak, Retrospect, RSA, the RSA logo,
SafeLine, SAN Advisor, SAN Copy, SAN Manager, ScaleIO Smarts, EMC Snap, SnapImage, SnapSure, SnapView,
SourceOne, SRDF, EMC Storage Administrator, StorageScope, SupportMate, SymmAPI, SymmEnabler, Symmetrix,
Symmetrix DMX, Symmetrix VMAX, TimeFinder, TwinStrata, UltraFlex, UltraPoint, UltraScale, Unisphere, Universal
Data Consistency, Vblock, Velocity, Viewlets, ViPR, Virtual Matrix, Virtual Matrix Architecture, Virtual
Provisioning, Virtualize Everything, Compromise Nothing, Virtuent, VMAX, VMAXe, VNX, VNXe, Voyence, VPLEX,
VSAM-Assist, VSAM I/O PLUS, VSET, VSPEX, Watch4net, WebXtender, xPression, xPresso, Xtrem, XtremCache,
XtremSF, XtremSW, XtremIO, YottaYotta, Zero-Friction Enterprise Storage.
DEMO 3: PART 1 – CREATE PROJECT AND UPLOAD MITREND SUMMARY XML ......................18
DEMO 3: PART 2 – CREATE SCENARIO, ADD AND MODIFY WORKLOADS ...............................19
DEMO 3: PART 3 – SIZE SCENARIO, VIEW REPORTS, EXPORT CONFIGURATION XML ...............21
DEMO 5: PART 1 – CREATE PROJECT, UPLOAD IMPL BIN, AND CREATE UPGRADE SCENARIO ..28
DEMO 5: PART 2 – UPGRADE CONFIGURATION ................................................................29
Purpose: This demo covers the use of VMAX Sizer to design a new
VMAX3 array with BTP/BIN Data from an older VMAX 20K
array. Sizing with Default Constraints.
Step Action
https://vmaxsizer.emc.com
e.g.
T1_20110920_120004_000192604253.bin
T1_20110920_120004_000192604253.btp
Hint: Click on the uploaded BTP file to see the Workload details.
Pay attention to the workload names to see if any workload is currently being
replicated.
Step Action
e.g.
Hover over the various colored circles to see details of each workload.
Hint: Click on Table View icon ( ) at the top right of the page.
For each workload look at the Capacity, IOPS, Skew, SLO, Remote Replication,
Snap, Clone etc.
6 Change the SLO and add Snap to the workloads that are being replicated with
SRDF/Asynchronous.
Step Action
1 Size Scenario
Hint: Click Size Scenario on the Workload page
Hint: Click on your Scenario in the Activity page after the sizing has completed.
IO Modules: ____________________________
Hint: Click the ellipsis (…) icon and choose View Reports.
Observe the % Utilization of the various components in the Load Analysis tab.
Hint: Click the ellipsis (…) icon and choose Export as XML.
Hint: Click the Sizer Report icon ( ) at the top right of the page.
Sizer Report PPTx and CSV file will be e-mailed to the Sizer user.
End of Demo
Step Action
Hint: Hover over the ellipsis (…) icon and then click on the Copy icon ( ).
The action will automatically make a copy and navigate to the Workload – Graph
View of the copied scenario.
The default name of the copied scenario is the original name appended with the
word “Copy”.
Add Asynchronous and Snap replication for these workloads. Set the number of
Mounted Snaps to 2.
Step Action
1 Size Scenario
IO Modules: ____________________________
Observe the % Utilization of the various components in the Load Analysis tab.
Hint: Click the ellipsis (…) icon and choose What if Analysis. Set IOPS Growth % to
20. Click What If.
Observe the % Utilization of the various components in the Load Analysis tab.
End of Demo
Purpose: This demo covers the use of VMAX Sizer to size a new VMAX3
array with Mitrend data from multiple VNX arrays
Step Action
e.g.
VNX_Performance_DataSummary_Mitrend.xml
Hint: Click on the uploaded Mitrend XML file to see the Workload details.
Pay attention to the workload names and identify once with the word “VPLEX”.
The VPLEX workloads will not be part of the new VMAX3.
Also note that there are a number of workloads with less than 10 IOPS. These
workloads will not be part of the new VMAX3 either.
Step Action
e.g.
Hover over the various colored circles to see details of each workload. Note that
a number of workloads are near 0 IOPS.
Filter the list to see only the workloads with “vplex” in the name.
Hint: Click on the box in front of each of the “vplex” workloads and then click on
Sort the workloads by IOPS and then select and delete all the workloads with
less than 10 IOPS.
Sort by IOPS and enable Snap with 2 Mounted Snaps for the top 6 workloads.
Step Action
1 Size Scenario
________________________________________________
Observe the % Utilization for the various components in the Load Analysis tab.
End of Demo
Purpose: This demo covers the use of Sizer to size a new VMAX3 array
with block and eNAS workloads. We will show the addition of
an eNAS instance and the addition of Custom/Template block
workloads when real customer data is unavailable.
eNAS Instance
Template Workload
Custom Workload
Size Scenario.
Step Action
e.g.
e.g.
eNAS Properties: Total Data Mover Capacity 200 TiB, use defaults for the rest.
General Tab: Custom, Name – MyCustom, 51200 GiB, 10000 IOPS, 90/10 Skew
Workload Mix Tab: Set all block sizes to 8 KB, Read Hit 35%, Read Miss 25%,
Write Hit 25%, and Write Miss 15%.
Step Action
1 Size Scenario
Observe the details of both configurations. Ensure that the configurations are
Dual Engine Configurations with D@RE.
IO Modules: ____________________________
Observe the % Utilization of the various components in the Load Analysis tab.
End of Demo
Upgrade Configuration
Drives
IO Modules
Step Action
e.g.
impl0141.bin
e.g.
Upgrade Scenario
The view will switch to the Configuration Option page with the current
configuration shown.
Step Action
Hint: Click the ellipsis (…) icon and choose Upgrade Config
2 Drive Tab:
3 IO Modules:
In this example we did not have the license file, so the Current column for all but
HYPERMAX OS Pack will be unchecked.
For this case we know that the Advance Suite was sold. So check the VMAX
Advanced Suite box.
Any desired software can be added here by clicking in the Desired column.
Compare the Upgrade Config with the Current Config. Ensure that the Upgrade
Config reflects the changes that were made.
IO Modules: ____________________________
End of Demo
Purpose: This demo covers the design process for a Business Continuity
Remote Replication Solution.
Run modeling.
Step Action
1 Proposed Configuration:
2 Data requirements:
3 Proposed Network
Configuration for SRDF/S
Primary DR
VMAX 200k VMAX 200k
FC FC
100 KM
FC FC
DWDM
Step Action
c) Compression Ratio: 2
d) Growth(%): 0
4 In Project “SRDFS Model” - Create two new Sites: Call one “Local” and the other “Remote”
5 In site “Local” – Create a new Symmetrix Array with the following specifications.
• One (1) Replication Port Group named Local Port Group with Two (2) 8 Gb Fibre
ports, No Compression (None), With SiRT enabled
• One (1) Replication Group named Local Replication Group with: Rep Flag: Source,
Rep Port Group: use the one you just created (Local Port Group), Sub Qty: 2
• SRDF/A settings – Host Type: OS - (Set this even though we are modeling SRDF/S)
• Qty: 1
7 In site “Remote” – Create a new Symmetrix Array with the following specifications.
• Name: DR, Hardware Version: VMAX3, Family: VMAX 200K, Engines: 4, Microcode:
5977, Usable Cache (GB): 512
• One (1) Replication Port Group named Remote Port Group with Two (2) 8 Gb Fibre
ports, No Compression (None), With SiRT enabled
• One (1) Replication Group named Remote Replication Group with: Rep Flag: Target,
Rep Port Group: use the one you just created (Local Port Group), Sub Qty: 2
• SRDF/A settings – Host Type: OS - (Set this even though we are modeling SRDF/S)
• Qty: 1
d) Circuit Qty: 2
f) Distance: 100 KM
c) Use the drop down lists for all the other required information – Only the appropriate
names will show up in the drop down lists
b) Product: SRDF/S
e) Source Rep Group: Choose the Replication Group created on the Primary Array
f) Target Rep Group: Choose the Replication Group created on the DR Array
12 Load the AIX iostat Data into BCSD (Tools Load Performance Data).
b) Load Tag: 1
d) File Selection: Use the Add button and browse and locate the AIX iostat file
b) Click on the “1” load tag in the “Load Tags to Include” box
d) Set the Volumes radio button to “Include”, then click on the “Browse” button and locate
the TXT file with the volumes that should be included
e) Rep/Con Group: Choose the replication group on the Primary array from the drop
down list
a) Click on the “Primary Array” in the tree panel, then click on the “Replication Group List”
tab
b) Double click on the Replication Group that you had created earlier. You should see the
devices from the TXT file in the Volumes list. The mapping was successful if you see
volumes in this list. Redo the mapping if you don’t see any volumes.
c) Click on the Cancel button to get out of the Replication Group window.
BCSD will validate the project. Fix any errors, warnings can be ignored.
2 In the tree panel, click on the Logical Relationships – “SRDF Logical”. Click on the “Modeling
Charts” tab.
View the Write Profile Chart. What is the Max Writes per sec? ________________
View the “Write Skew Top 15 Volumes” Chart. What volumes have a high write I/O profile?
__________________________________________________________________________
View the “Volume Exceptions” Tab. What Volumes (if any) are flagged for Tuning?
__________________________________________________________________________
3 Click on the “Modeling Charts” tab.
View the “Raw Throughput” Chart. What is the amount of raw throughput required for this
configuration?
Available Throughput _______
View the “Compressed Throughput” Chart. What is the amount of compressed throughput
required for this configuration?
What is the specified Compression Ratio? ________________
Is there any difference between the Raw and Compressed Throughput charts? _________
Can the current Bandwidth sustain the peak workload for SRDF in Synchronous mode?
__________________________________________________________________________
Is the proposed Remote Adapter configuration able to sustain the peak workload for SRDF in
Synchronous mode? _________________________________________________________
What are the problem volumes that must be addressed prior to enabling SRDF Synchronous
mode? ____________________________________________________________________
End of Demo
Step Action
1 Current Situation:
2 Desired Solution:
Step Action
Name: SRDFS_BTP
Compression Ratio: 2
Growth Factor: 0
Name: Primary Array, Hardware Version: VMAX3, Family: VMAX 200K, Engines:
2, Microcode: 5977, Usable Cache (GB): 1024
One Replication Port Group named Primary Port Group, with two (2), 8 Gb FC
ports, no compression, with SiRT enabled
One Replication Group named Primary Rep Group, with: Rep Flag: Source, Rep
Port Group: use the one you just created, Sub Qty: 2
For SRDF/S modeling, do not check the Delta Set Ext box
SRDF/A settings – Host Type: OS (set this even though we are modeling SRDF/S)
Qty: 1
One Replication Port Group named Secondary Port Group, with two (2), 8 Gb FC
ports, no compression, with SiRT enabled
One Replication Group named Secondary Rep Group, with: Rep Flag: Target, Rep
Port Group: use the one you just created, Sub Qty: 2
For SRDF/S modeling, do not check the Delta Set Ext box
SRDF/A settings – Host Type: OS (set this even though we are modeling SRDF/S)
Qty: 1
Circuit Qty: 1
Use the drop down lists for all the other required information – Only the
appropriate names will show up in the drop down lists.
Product: SRDF/S
Source Rep Group: Choose the Replication Group created on the Local Array
Target Rep Group: Choose the Replication Group created on the Remote Array
12 Load the Customers BTP data into BCSD with a load tag of SRDFS.
Hint: Tools Load Performance Data
File name: T1_20141007_200012.btp, T1_20141008_000013.btp,
T1_20141008_040011.btp,
T1_20141008_080013.btp
14 Map the BTP data to the Replication Group of the Primary Array.
Hint: Tools Map Replication Groups
Make sure to use the Include option and specify the volume list: SYNC_DEVS.txt
Step Action
BCSD will validate the project. Fix any errors, warnings can be ignored.
Are there any volumes that exceed the number of writes that can be sustained
with SRDF/S? ________________________
Step Action
1 Current Situation:
2 Desired Solution:
Recommended Configuration:
Step Action
Name: SRDFA
Compression Ratio: 2
Name: Local Array, Hardware Version: VMAX3, Family: VMAX 200K, Engines: 3,
Microcode: 5977, Usable Cache (GB): 1536
One Replication Port Group with Eight (8), 1 Gb GigE ports with Hardware
Compression
One Replication Group with: Rep Flag: Source, Rep Port Group: use the one you
just created, Sub Qty: 8, Transmit Idle Time (seconds): 150, with Delta Set Ext
Name: Remote Array, Hardware Version: VMAX3, Family: VMAX 200K, Engines:
3, Microcode: 5977, Usable Cache (GB): 1536
One Replication Port Group with Eight (8), 1 Gb GigE ports with Hardware
Compression
One Replication Group with: Rep Flag: Target, Rep Port Group: use the one you
just created, Sub Qty: 8, Transmit Idle Time (seconds): 150, with Delta Set Ext
Circuit Qty: 1
Use the drop down lists for all the other required information – Only the
appropriate names will show up in the drop down lists
11 In project SRDFA – Create a new Logical SRDF Relationship.
Product: SRDF/A
Source Rep Group: Choose the Replication Group created on the Local Array
Target Rep Group: Choose the Replication Group created on the Remote Array
14 Map the BTP data to the Replication Group of the Local Array.
Hint: Tools Map Replication Groups
Make sure to use the Include option and specify the volume list:
Boston_RDF1_list.txt
15 Verify that the Replication Group mapping was successful.
Hint: Look at the Replication Group that you had defined on the Local Array.
Step Action
BCSD will validate the project. Fix any errors, warnings can be ignored.
End of Demo
Step Action
1 Current Situation:
2 Desired Solution:
Array 1
Array 2
4 Proposed Solution
Step Action
Name: MSC
Compression Ratio: 2
Call the first Local Array 1 and the second Local Array 2
Both arrays should be VMAX 200K, 2 Engine, 5977 with 2048 GB of usable
cache.
Each array should have one Replication Port group with 4 10 GigE ports, with
hardware compression.
Each array should have one Source Replication Group which uses all the ports in
the Replication Port group – Delta set extension should be enabled.
For each array the SRDF/A settings should be – Host Type of OS with 8000
Logical Volumes
5 In site Local – Create a new Switch
Call the first Remote Array 1 and the second Remote Array 2
Both arrays should be VMAX 200K, 2 Engine, 5977 with 2048 GB of usable
cache.
Each array should have one Replication Port group with 4 10 GigE ports, with
hardware compression.
Each array should have one Target Replication Group which uses all the ports in
the Replication Port group – Delta set extension should be enabled.
For each array the SRDF/A settings should be – Host Type of OS with 8000
Logical Volumes
7 In site Remote – Create a new Switch
Circuit Qty: 1
Call the first MSC Physical 1 and the second MSC Physical 2
Call the first MSC Logical 1 and the second MSC Logical 2
14 Map the BTP data to the corresponding Replication Groups of the Local Arrays.
Step Action
BCSD will validate the project. Fix any errors, warnings can be ignored.
2 View the Model Properties tab of both the MSC Logical Relationships and record
the following:.
End of Demo