0% found this document useful (0 votes)
136 views11 pages

Netapp™ Test Plan For Affinity: Ver. 20 Amit Biswas Netapp

POC

Uploaded by

Mauj
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
136 views11 pages

Netapp™ Test Plan For Affinity: Ver. 20 Amit Biswas Netapp

POC

Uploaded by

Mauj
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 11

NetApp Test Plan for Evaluation

NetApp Test Plan for


Affinity
Ver. 20
Amit Biswas
NetApp

All rights reserved. Specifications are subject to change without notice. NetApp, the NetApp logo, Go further, faster,
Data ONTAP, Snapshot, SnapMirror, SnapRestore, SnapVault, SnapLock, FlexShare, FlexClone, FlexVol, Lifetime
Key Management Appliance, NearStore, NOW, RAID-DP, SnapDrive, SyncMirror and WAFL are trademarks or
registered trademarks of NetApp, Inc. in the United States and/or other countries. All other brands or products are
trademarks or registered trademarks of their respective holders and should be treated as such.

Page 1 of 11
February 25 2016

NetApp Test Plan for Evaluation

Index

This test plan contains the following sections:

1.1 Introduction
NetApp creates innovative storage and data management solutions that help accelerate business breakthroughs
and deliver outstanding cost efficiency. Our dedication to principles of simplicity, innovation, and customer success
has made us one of the fastest-growing storage and data management providers today.
Customers around the world choose us for our go beyond approach and broad portfolio of solutions for business
applications, storage for virtual servers, disk-to-disk backup, and more. Our solutions provide nonstop availability of
critical business data and simplify business processes so you can deploy new capabilities with confidence and get
to revenue faster than ever before. You can rely on our industry-leading solutions to lower the cost of protecting
your data, business, and reputation.
We bring together the industrys best partners and technology to deliver services that help you maximize what you
are getting from your infrastructure. Our collaborative approach, working as one team with one goal, means that
you get a solution that is just right for youon time and on budget. To support your global business, we provide
highly-responsive support in local languages. From London to Austin, from Bangalore to Tokyo, well work with you
to solve your problems and help you reach your goals.
Discover our passion for helping companies around the world go further, faster at www.netapp.com.
Affinity(at Hinjewadi) has agreed to evaluate and test a NetApp solution applicable to the PLM Environment. The
details of the NetApp solution, the testing procedure agreed upon, and the timelines for the procedure form the
core of this document.

1.2 Objectives
Affinity associated business issue may be summarized thusly:
1.
2.
3.
4.

Consolidation of the storage sub system


Centralised storage for all forms of data
Integration of Apple file system on NetApp Storage
Access of the Apple Files thru windows clients .

At a high level, the objectives of this evaluation and test are as follows:
Verify that the NetApp solution will meet or exceed Affinity requirements for a solution to the business
issue outlined above.
Demonstrate the advantages of the NetApp proposed solution with regards to disaster recovery, reliability,
and resilience to component failure.
Show that performance of the proposed solution meets or exceeds that required by Affinity.
Define and test relevant scalability and availability metrics for this evaluation.

1.3 Success Criteria


Any evaluation process must have clearly-defined success criteria in order to test and judge the exit process.
Examples of these may be time-sensitivity, proof of functionality, performance tuning metrics, or the like. Both
Page 2 of 11
February 25 2016

NetApp Test Plan for Evaluation


NetApp and Affinity should agree a priori to the individual criteria which constitute the successful accomplishment
of the test plan. Note: Success in the accomplishment of the test plan should not imply success in all tests
contained, only that the procedure herein described has been followed.
Criterion

NetApp
Signature

Measurement

Time Frame

Customer
Signature

All testing must be completed by DATE


Installation/setup must be completed by
DATE
Breakdown and shipment from customer
must occur by DATE
Etc.

1.4 Prerequisites
In order for Affinityto evaluate and test the NetApp solution, certain tasks must be completed prior to the beginning
of the tests. These may be divided as follows:
NetApp

Distribution of Evaluation Agreement to customer


Distribution of System Installation documentation
Development (with customer) of the Evaluation Test Plan
Contact information for all involved parties
Other items as necessary

Signed and exercised Evaluation Agreement


Completed NetApp Pre-Install Checklist (available from NetApp SE)
Contact information for all involved parties
Other items as necessary

Affinity

1.5 Contacts
The evaluation of the NetApp solution is assumed to be a joint process undertaken and supported by both NetApp
and representatives of Affinity. In particular, on-site and dedicated resources from both parties are vital to the
success of the endeavour. The Personnel below are assigned to the task(s) discussed above. Leads should be
involved in the scheduling and the tracking of all evaluation and test items, and should consistently steer the
accomplishment of all tests toward the Success Criteria mutually agreed upon above.
NetApp Contacts
Title
NetApp
Solution
Consultan
t

Name
Amit
Biswas

Address
Pune

Phone

Cell
9921119995

Email/pager
[email protected]
m

Signature

Email

Signature

AffinityContacts
Title
Customer
Technical

Name

Address

Phone

Cell

Page 3 of 11
February 25 2016

NetApp Test Plan for Evaluation


Lead
Customer
Business
Unit Lead

1.6 NetApp Equipment Provided


The following is a high-level listing of the components and equipment NetApp is providing for the purpose of this
test. Unless stated here below, no other major equipment is to be provided by NetApp. Specifically, NetApp is not
responsible for providing such non-NetApp hardware as IP switches, cables to IP switches, servers, or the
personnel to configure, install or service such infrastructure for the duration of the test.Affinityis assumed to be
responsible for infrastructure items not listed below which may be required to perform the evaluation, including
third-party software licenses for evaluation purposes, power and receptacles, etc.
NetApp Equipment list:
Model:
Number of Shelves
Disk Drive Size and Type:
Cards
Number of Racks:
FC Switches (Type and Qty)
NetApp software

none
NFS, CIFS, iSCSI and FCP protocol licenses
Deduplication License
Cluster license
SnapRestore license

1.7 Duration and Timing of the Evaluation


Evaluation and testing of the NetApp solution will be subject to the following timelines and durations. The entire test
and evaluation process will begin on 31 st January and run until 15 th February. Individual sections of this test plan
may be executed on particular dates. Each test below contains a space where the date may be recorded.
After the tests are completed, Affinity and representatives from NetApp will meet together to discuss the completed
plan. This meeting will happen no later than 20th February.
In addition to the post-test discussion, a completed report will be submitted by Affinity internally which details the
results of the entire test/evaluation process. A similar or otherwise appropriate (approved for external distribution)
version of the report shall be released to NetApp by 25th February. Such a completed report shall be considered the
official results documentation and, as such, signal the end of the evaluation process.
Breakdown, disconnection of the systems, blanking of disk media, crating and shipment of the system(s) shall be
negotiated and planned in a mutually beneficial timeframe and manner between Affinity and NetApp.

1.8 Support During the Evaluation


NetApp provides close customer support for evaluations of its solutions by prospective customers. At the center of
the NetApp support infrastructure is the System Engineer (SE) listed in the Contacts section above. The SE is
responsible for the support of the testing and evaluation process, and in solving any issues arising from the test
process itself.
Page 4 of 11
February 25 2016

NetApp Test Plan for Evaluation


As a part of the testing process, the SE will likely consult with internal resources such as the Global Support Center
(GSC), other System Engineers and Professional Services Engineers, as well as engineering/product development
personnel within NetApp.
Calls to 1-888-4NETAPP or opening a ticket on the NOW (NetApp on the Web) site should only be undertaken
with consultation and direction from the NetApp SE. For example, the acknowledgment of autosupport messages
or the navigation and knowledge transfer of the NOW site may be constructed as a part of the evaluation/testing
process of the solution as a whole. In such a case, the SE guides the contact process to the GSC and manages
the call, the information transfer involved, and the eventual closure of the issue/ticket.
In short, the support process for any evaluation system in the field begins with the NetApp SE, and should
proceed with that persons guidance and full knowledge in all stages of the test cycle.

Page 5 of 11
February 25 2016

NetApp Test Plan for Evaluation

2 Functional Tests of NetApp FAS Systems


Specific Functional tests are categorized below. Corresponding Performance tests may also be added. Note that
functional tests (which reveal whether a certain feature or capability works correctly) do not imply load, thus are
necessary but not sufficient conditions for judging a systems run-time operational capabilities. Actual operation
under significant load is necessary for full results. Some NetApp products (e.g. FlexShare) will show results ONLY
when the system is fully loaded and task prioritization could become operationally beneficial. See Section 3 for
Performance-oriented test guidelines.

2.1

Hardware and Installation Tests

The tests in this section are designed to show the resilience of the hardware platform to typical events. Unplanned
interruption of power can cause more downtime to users than a simple planned shutdown.
Task
#

Task

2.1.1

Confirm cold-boot time. (halt,


then boot)
Confirm warm boot time.
(reboot)
Run through system setup to
install storage system on
network and supply with a
hostname. Time how long to
complete install process.
Define an aggregate.
Confirm an aggregate can be
dynamically extended by a
single disk without corrupting file
system to demonstrate system
scalability.
Confirm an aggregate can be
dynamically extended by a
group of disks without corrupting
file system to demonstrate
system scalability.
Hot-add a new disk shelf while
system is running to
demonstrate system scalability.
Confirm operation of redundant
power supplies on storage
system shelves and controllers.
Confirm operation of redundant
fans on storage system shelves
and controllers.
Remove a data disk while being
accessed, and determine if any
data corruption has occurred.
Remove two disks in a RAID-DP
group while being accessed,
and determine if any data
corruption has occurred.
Perform at-the-wall power failure
as described below. Upon
restart, ensure no data is
corrupted. Time how long before

2.1.2
2.1.3

2.1.4
2.1.5

2.1.6

2.1.7

2.1.8

2.1.9

2.1.1
0
2.1.1
1

2.1.1
2

Date or
Time

Assignee

Page 6 of 11
February 25 2016

Notes

Pass
/ Fail

Cert.
Initials

NetApp Test Plan for Evaluation


2.1.1
3

2.1.14

users are able to access system


again.
Create a flexible volume,
increase the size then decrease
the size of the volume. Record
effects.
Upgrade system software.
Record effects on users and
time length of outage.

Utilize Non-Disruptive
Upgrade (NDU)
procedures.

* Note: Cutting the power off at the wall plug/switch is an important test. Because some devices feature soft
power buttons which shut down the system in an orderly manner (de-staging cache, e.g.) and lastly signal the
power supply to cut power to the hardware, simply hitting a button on the front of the unit switches is not an
adequate simulation of power failure. Pull the plug or cut the AC current suddenly (for example, at a breaker)
instead.

2.2

UNIX and NFS testing

These tests are intended to show the level of integration with a standard UNIX environment:
Task
#
2.3.1
2.3.2
2.3.3

2.3

Task

Date
or
Time

Assignee

Add storage system into


NIS domain.
Add NFS exports to share
storage system volumes.
Change export options and
re-test connectivity.

Notes

Pass
/ Fail

Cert.
Initials

Change /etc/exports on
the controller or use FilerView.

Windows and CIFS testing

These tests are intended to show the level of integration with a standard Windows/CIFS environment. Please
consult the Windows File Services Best Practices with NetApp Storage Systems Technical Report found at
http://media.netapp.com/documents/tr-3771.pdf in order to configure and setup CIFS filesystems on your NetApp
FAS system.
Task
#
2.4.1
2.4.2

2.4.3
2.4.4

2.4.5

Task

Date or
Time

Assigne
e

Add storage system into


Windows domain.
Browse storage system
properties with server
manager.
Change properties of a
share.
Create CIFS alias for
storage system and add
static WINS mapping.
Add, remove, then readd storage system to
local domain.
Page 7 of 11
February 25 2016

Notes

Pas
s/
Fail

Cert.
Initials

NetApp Test Plan for Evaluation


2.4.6

Turn on CIFS auditing.

See the Auditing Quick Start Guide


at
http://media.netapp.com/documents
/tr-3595.pdf

2.4 CIFS Consolidation


These tests are designed to plan for consolidation of many existing Windows Server shares and systems down to
one NetApp-hosted CIFS appliance. Avoid share collision when consolidating two or more Windows file servers by
utilizing qtrees as a part of the migration process.:
Task
#
2.5.1

2.5.2

2.5.3

2.5.4

2.5.5
2.5.6

2.5.7

Task

Date or
Time

Assigne
e

Notes

Pass
/ Fail

Cert.
Initials

Identify/create two CIFS shares


located in the network with the same
share names and contents. These
source shares should be hosted on
different file servers.
Create a single target share on the
NetApp storage system as a
repository. Make this read/writable to
all hosts.
Create two appropriate qtrees under
the storage systems target share to
house the two source shares.
Copy files from the two source shares
into the two qtrees on the storage
system.
Apply quotas on the qtrees.
Verify that all files from the two
source shares are present in the
qtrees.
Verify that quotas are enforced on
disk capacity.

2.5 Filename and File Access Tests


These tests are intended to test migration of users to the storage system from an existing user environment:
Task
#
2.6.1

2.6.2

2.6.3
2.6.4

Task

Date or
Time

Assigne
e

Copy at least 500 files and directories


with embedded spaces to and from
the storage system and determine if
corruption of filenames occurs
Configure a user account to use the
storage system as a home directory.
Logon to the user account from a
workstation. Confirm correct
functionality.
Add disks and increase the volume
size note impact on users.
Simulate network failure and impact
to users re: access to data.
Page 8 of 11
February 25 2016

Notes

Pass
/ Fail

Cert.
Initials

NetApp Test Plan for Evaluation

2.6 Snapshot and SnapRestore Tests


Recovering single files is a substantial burden at many sites. Just one restore per year from tape per five users can
tie up whole system administrators at large sites.
NetApps Snapshots are easily enabled for user volumes to be browsed by users, so users can recover their own
lost or damaged data from the Snapshot directories without operator/admin assistance. (Note that Snapshot
directories may also be restricted from user view by the storage systems administrator.)
Task
#
2.8.1

2.8.2

2.8.3

2.8.4

2.8.5

2.8.6

2.8.7

2.8.8

2.8.9

Task
Create a Snapshot
schedule to automatically
create Snapshots at regular
periods during the day.
Create a Snapshot. Time
how long this takes and
how long before you are
able to recover a deleted
file.
Update file from the
Snapshot version
(copy/paste).
Open a file in a Snapshot
and take another Snapshot
while opened.
Recover large deleted file
from Snapshot Hourly.0.
Take a new Snapshot
during that file recovery.
Configure Snapshot share
to allow administrator file
restores when Snapshots
are not visible to users
Change Snapshot reserve
to make more space for
new Snapshots. Ensure
that this is dynamic and that
old Snapshots are retained.
Simulate recovering a
whole filesystem/volume:
Configure a large
filesystem (100GB+).
Copy in data until the
filesystem is approx.
80% full.
Take a Snapshot.
Over-write at least 10%
of the data.
Recover to the previous
filesystem state using
SnapRestore.
Restrict access to Snapshot

Date
or
Time

Assignee

Notes
Utilize the snap sched
command or the SnapShot
GUI in FilerView.

Page 9 of 11
February 25 2016

Pass
/ Fail

Cert.
Initials

NetApp Test Plan for Evaluation


2.8.10

directories and verify that


access is indeed restricted.
Show single-file
SnapRestore capabilities.

2.7 FAS Deduplication Tests


FAS Deduplication deduplicates blocks anywhere in the active file system within the entire flexible volume,
regardless of how the data got there. FAS Deduplication may be used for secondary data (data retention/archiving)
and/or for primary storage environments as well.
All shipping NetApp storage systems (Data ONTAP Ver. 7.2.5 and later) can realize the storage benefits of
deduplication. NetApps FAS deduplication is enabled by two licenses (NearStore and ASIS), both of which must
be present on any standalone controller or on any controller in an HA pair. NetApps FAS deduplication is enabled
on a per-volume basis, can be scheduled, and can be reversed (undeduplicated) at any time. Note that FAS
deduplication is an asynchronous process run at specified times on all delta blocks written from the immediately
previous process. NetApp recommends development of a schedule to initiate and run deduplication on target
volumes at specified times and at specified intervals. Note also that initial deduplication of a large volume may take
substantially longer than subsequent deduplications, since subsequent operations only need run on delta blocks.
Task
#
2.9.1

2.9.2

2.9.3

2.9.4
2.9.5

2.9.6
2.9.7
2.9.8

2.9.9

2.9.10

Task
Assure Data ONTAP
version compliance
(7.2.4P6 and later).
Assure nearstore and asis
licenses are installed on all
controllers.
Create FlexVol.

Enable deduplication on
FlexVol.
Populate the FlexVol with
data to be deduplicated.
(10-80% of the FlexVol size
to see results). Note the
size of the FlexVol (dfs
or equivalent).
Perform initial scan.
Monitor the status of the
deduplication while running.
When complete, check the
space savings and
compare with previous
values.
Schedule deduplication
runs.

Test recurrent deduplication


schedules.

Date
or
Time

Assignee

Notes

(Note that FlexVol volumes to


be deduplicated must be sized
under the following maxima for
pre-7.3 releases:
FAS3070: 6TB
FAS3040: 3TB
FAS3050: 2TB
FAS3020: 1TB )
sison<volname>

sisstart<volname>
sisstatus<volname>

sisconfigs
<volname>
or sishelpconfig
to set up individual schedules
Change FlexVol contents
between successive
Page 10 of 11
February 25 2016

Pass
/ Fail

Cert.
Initials

NetApp Test Plan for Evaluation


2.9.11

2.9.12

Show reversal
(undeduplication) of a
previously-deduplicated
FlexVol.
When complete, check the
space inflation and
compare with previous
values.

deduplication runs to test


deltas.
sisoff<volname>
sisundo<volname>
sisstatus<volname>

Page 11 of 11
February 25 2016

You might also like