You are on page 1of 11

NetApp Test Plan for Evaluation

NetApp™ Test Plan for
Ver. 20
Amit Biswas

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

and resilience to component failure. business.  Show that performance of the proposed solution meets or exceeds that required by Affinity. 1. Our collaborative approach. means that you get a solution that is just right for you—on time and on budget. Affinity(at Hinjewadi) has agreed to evaluate and test a NetApp solution applicable to the PLM Environment. we’ll work with you to solve your problems and help you reach your goals. working as one team with one goal. 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. proof of functionality. 3.3 Success Criteria Any evaluation process must have clearly-defined success criteria in order to test and judge the exit process. Our dedication to principles of simplicity. We bring together the industry’s best partners and technology to deliver services that help you maximize what you are getting from your infrastructure.2 Objectives Affinity associated business issue may be summarized thusly: 1. 4. Discover our passion for helping companies around the world go further.NetApp Test Plan for Evaluation 1 Index This test plan contains the following sections: 1. 1. To support your global business. At a high level. and the timelines for the procedure form the core of this document.netapp. the testing procedure agreed upon. From London to and more. Customers around the world choose us for our “go beyond” approach and broad portfolio of solutions for business applications. and reputation. The details of the NetApp solution. or the like. performance tuning metrics. Examples of these may be time-sensitivity.  Define and test relevant scalability and availability metrics for this evaluation. Both Page 2 of 11 February 25 2016 . faster at www. 2. innovation. 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 . from Bangalore to Tokyo. and customer success has made us one of the fastest-growing storage and data management providers today. You can rely on our industry-leading solutions to lower the cost of protecting your data.1 Introduction NetApp creates innovative storage and data management solutions that help accelerate business breakthroughs and deliver outstanding cost efficiency. reliability. we provide highly-responsive support in local languages.  Demonstrate the advantages of the NetApp proposed solution with regards to disaster recovery. storage for virtual servers. disk-to-disk backup. 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.

In particular.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. 1.4 Prerequisites In order for Affinityto evaluate and test the NetApp solution. Leads should be involved in the scheduling and the tracking of all evaluation and test items. Note: Success in the accomplishment of the test plan should not imply success in all tests contained. 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 m Signature Email Signature AffinityContacts Title Customer Technical Name Address Phone Cell Page 3 of 11 February 25 2016 . only that the procedure herein described has been followed. and should consistently steer the accomplishment of all tests toward the Success Criteria mutually agreed upon above. on-site and dedicated resources from both parties are vital to the success of the endeavour. certain tasks must be completed prior to the beginning of the tests.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.biswas@netapp. 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. The Personnel below are assigned to the task(s) discussed above. NetApp Contacts Title NetApp Solution Consultan t Name Amit Biswas Address Pune Phone Cell 9921119995 Email/pager amit.

blanking of disk media.NetApp Test Plan for Evaluation Lead Customer Business Unit Lead 1. The SE is responsible for the support of the testing and evaluation process. signal the end of the evaluation process. Affinity and representatives from NetApp will meet together to discuss the completed plan. iSCSI and FCP protocol licenses Deduplication License Cluster license SnapRestore license 1. no other major equipment is to be provided by NetApp. After the tests are completed. CIFS. A similar or otherwise appropriate (approved for external distribution) version of the report shall be released to NetApp by 25th February.7 Duration and Timing of the Evaluation Evaluation and testing of the NetApp solution will be subject to the following timelines and durations. a completed report will be submitted by Affinity internally which details the results of the entire test/evaluation process. including third-party software licenses for evaluation purposes. and in solving any issues arising from the test process itself.Affinityis assumed to be responsible for infrastructure items not listed below which may be required to perform the evaluation.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. or the personnel to configure. as such. The entire test and evaluation process will begin on 31 st January and run until 15 th February. servers. Breakdown. disconnection of the systems. install or service such infrastructure for the duration of the test. crating and shipment of the system(s) shall be negotiated and planned in a mutually beneficial timeframe and manner between Affinity and NetApp. This meeting will happen no later than 20th February. Page 4 of 11 February 25 2016 . 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. etc. 1. Unless stated here below. Such a completed report shall be considered the “official” results documentation and. In addition to the post-test discussion. cables to IP switches. power and receptacles. NetApp is not responsible for providing such non-NetApp hardware as IP switches. Individual sections of this test plan may be executed on particular dates.8 Support During the Evaluation NetApp provides close customer support for evaluations of its solutions by prospective customers. Each test below contains a space where the date may be recorded. At the center of the NetApp support infrastructure is the System Engineer (SE) listed in the Contacts section above. Specifically.

NetApp Test Plan for Evaluation As a part of the testing process. the SE guides the contact process to the GSC and manages the call. and should proceed with that person’s guidance and full knowledge in all stages of the test cycle. For example. and the eventual closure of the issue/ticket. the SE will likely consult with internal resources such as the Global Support Center (GSC). the information transfer involved. as well as engineering/product development personnel within NetApp. In such a case. 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. the support process for any evaluation system in the field begins with the NetApp SE. other System Engineers and Professional Services Engineers. Page 5 of 11 February 25 2016 . 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 short.

g.1. Corresponding Performance tests may also be added.1.1.1. Note that functional tests (which reveal whether a certain feature or capability works correctly) do not imply load.3 2. FlexShare) will show results ONLY when the system is fully loaded and task prioritization could become operationally beneficial.9 2. thus are necessary but not sufficient conditions for judging a system’s run-time operational capabilities. ensure no data is corrupted.7 2. Confirm an aggregate can be dynamically extended by a group of disks without corrupting file system to demonstrate system scalability.1.1.2 2.NetApp Test Plan for Evaluation 2 Functional Tests of NetApp FAS Systems Specific Functional tests are categorized below. (halt.1.1 Hardware and Installation Tests The tests in this section are designed to show the resilience of the hardware platform to typical events. See Section 3 for Performance-oriented test guidelines. Some NetApp products (e.8 2.1. Remove a data disk while being accessed. then boot) Confirm warm boot time. and determine if any data corruption has occurred.1 2 Date or Time Assignee Page 6 of 11 February 25 2016 Notes Pass / Fail Cert.4 2. Define an aggregate.1. and determine if any data corruption has occurred.1.1 Confirm cold-boot time.5 2. Confirm an aggregate can be dynamically extended by a single disk without corrupting file system to demonstrate system scalability. Task # Task 2.6 2.1 0 2.1. (reboot) Run through system setup to install storage system on network and supply with a hostname. Hot-add a new disk shelf while system is running to demonstrate system scalability. Time how long to complete install process. Initials . 2. Confirm operation of redundant fans on storage system shelves and controllers. Time how long before 2. Perform at-the-wall power failure as described below.1. Confirm operation of redundant power supplies on storage system shelves and controllers.1 1 2. Unplanned interruption of power can cause more downtime to users than a simple planned shutdown. Remove two disks in a RAID-DP group while being accessed. Upon restart. Actual operation under significant load is necessary for full results.

5 Task Date or Time Assigne e Add storage system into Windows domain.3 Task Date or Time Assignee Add storage system into NIS domain. Pull the plug or cut the AC current suddenly (for example. Notes Pass / Fail Cert.1 3 2.3 2. then readd storage system to local domain.4.3.netapp. Add NFS exports to share storage system volumes.4.1 2. Utilize Non-Disruptive Upgrade (NDU) procedures. Please consult the Windows File Services Best Practices with NetApp Storage Systems Technical Report found at http://media.) and lastly signal the power supply to cut power to the hardware. Initials . e.1. Record effects on users and time length of outage. Windows and CIFS testing These tests are intended to show the level of integration with a standard Windows/CIFS environment. Page 7 of 11 February 25 2016 Notes Pas s/ Fail Cert.3. Create CIFS alias for storage system and add static WINS mapping. 2. Because some devices feature “soft” power buttons which shut down the system in an orderly manner (de-staging cache.4.2 2. Create a flexible volume. Task # 2. increase the size then decrease the size of the volume. simply hitting a button on the front of the unit switches is not an adequate simulation of power failure.14 users are able to access system again.1 2.g.NetApp Test Plan for Evaluation 2.2 UNIX and NFS testing These tests are intended to show the level of integration with a standard UNIX environment: Task # 2. * Note: Cutting the power off at the wall plug/switch is an important test.4 2.2 2. Initials Change /etc/exports on the controller or use FilerView.3 Record effects. Change properties of a share. at a breaker) instead.4. Change export options and re-test connectivity. Add.3. Browse storage system properties with server manager.1.4. Upgrade system software.pdf in order to configure and setup CIFS filesystems on your NetApp FAS system. remove.

Create two appropriate qtrees under the storage system’s target share to house the two source shares. Apply quotas on the qtrees.2 2.5. Initials . Make this read/writable to all hosts. See the Auditing Quick Start Guide at http://media. Avoid share collision when consolidating two or more Windows file servers by utilizing qtrees as a part of the migration process.netapp.6 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.5. Add disks and increase the volume size – note impact on users. 2. Simulate network failure and impact to users re: access to data.1 2.7 Task Date or Time Assigne e Notes Pass / Fail Cert. Confirm correct functionality.6.5. Page 8 of 11 February 25 2016 Notes Pass / Fail Cert.5 2.4 2. Copy files from the two source shares into the two qtrees on the storage system.5.3 2.5. These source shares should be hosted on different file servers.NetApp Test Plan for Evaluation 2. Verify that all files from the two source shares are present in the qtrees.6 Turn on CIFS auditing.6. Verify that quotas are enforced on disk capacity. Create a single target share on the NetApp storage system as a repository.2 /tr-3595.pdf 2.4.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.3 2. Initials Identify/create two CIFS shares located in the network with the same share names and contents.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.6. Logon to the user account from a workstation.: Task # 2.

so users can recover their own lost or damaged data from the Snapshot directories without operator/admin assistance.  Take a Snapshot. Just one restore per year from tape per five users can tie up whole system administrators at large sites. Create a Snapshot. NetApp’s Snapshots are easily enabled for user volumes to be browsed by users.8. Ensure that this is dynamic and that old Snapshots are retained.  Over-write at least 10% of the data.4 2.8.6 2.0.8 2. Simulate recovering a whole filesystem/volume:  Configure a large filesystem (100GB+). 80% full.2 2. Open a file in a Snapshot and take another Snapshot while opened. Page 9 of 11 February 25 2016 Pass / Fail Cert. 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.1 2.8. Restrict access to Snapshot Date or Time Assignee Notes Utilize the snap sched command or the SnapShot GUI in FilerView.7 2.8. (Note that Snapshot directories may also be restricted from user view by the storage system’s administrator. Take a new Snapshot during that file recovery.8.3 2.NetApp Test Plan for Evaluation 2.9 Task Create a Snapshot schedule to automatically create Snapshots at regular periods during the day. Update file from the Snapshot version (copy/paste).5 2.6 Snapshot™ and SnapRestore® Tests Recovering single files is a substantial burden at many sites.  Copy in data until the filesystem is approx.8.) Task # 2.  Recover to the previous filesystem state using SnapRestore. Initials .8. Recover large deleted file from Snapshot Hourly.8.8. Time how long this takes and how long before you are able to recover a deleted file.

Note that FAS deduplication is an asynchronous process run at specified times on all delta blocks written from the immediately previous process. All shipping NetApp storage systems (Data ONTAP® Ver. Note the size of the FlexVol (df –s or equivalent). check the space savings and compare with previous values.2.9. Test recurrent deduplication schedules. Initials . 2.7 2.9.8 2.9. Schedule deduplication runs. FAS Deduplication may be used for secondary data (data retention/archiving) and/or for primary storage environments as well.9.NetApp Test Plan for Evaluation 2. since subsequent operations only need run on delta blocks.6 2.3 releases: FAS3070: 6TB FAS3040: 3TB FAS3050: 2TB FAS3020: 1TB ) sis on <volname> sis start <volname> sis status <volname> sis config ­s  <volname> or sis help config  to set up individual schedules Change FlexVol contents between successive Page 10 of 11 February 25 2016 Pass / Fail Cert. (10-80% of the FlexVol size to see results).4P6 and later). both of which must be present on any standalone controller or on any controller in an HA pair. 7. Note also that initial deduplication of a large volume may take substantially longer than subsequent deduplications.5 and later) can realize the storage benefits of deduplication.8.1 2. regardless of how the data got there.9. and can be reversed (“undeduplicated”) at any time. NetApp recommends development of a schedule to initiate and run deduplication on target volumes at specified times and at specified intervals.3 2.9 2.4 2. When complete. Task # 2. Create FlexVol®. Perform initial scan.10 Task Assure Data ONTAP version compliance ( 2. NetApp’s FAS deduplication is enabled by two licenses (NearStore® and ASIS). can be scheduled.2.5 2. Date or Time Assignee Notes (Note that FlexVol volumes to be deduplicated must be sized under the following maxima for pre-7. Assure nearstore and asis licenses are installed on all controllers.10 directories and verify that access is indeed restricted. Enable deduplication on FlexVol. Populate the FlexVol with data to be deduplicated.9. NetApp’s FAS deduplication is enabled on a per-volume basis. Monitor the status of the deduplication while running. Show single-file SnapRestore capabilities.9.7 FAS Deduplication Tests FAS Deduplication deduplicates blocks anywhere in the active file system within the entire flexible volume.

sis off <volname> sis undo <volname> sis status <volname> Page 11 of 11 February 25 2016 .9. check the space inflation and compare with previous values.11 2. When complete. deduplication runs to test deltas.9.12 Show reversal (“undeduplication”) of a previously-deduplicated FlexVol.NetApp Test Plan for Evaluation 2.