Download HDS NetApp Filer Test Plan

NETAPP FILER TESTING
NetApp Filer Test Document
Draft 0.3
12/08/17
Page 1 of 9
NETAPP FILER TESTING
Compatibility Testing
Compatibility testing is required to demonstrate full interoperability with the existing environment.
The test plan comprises the following sections:
NetApp Filer Test Document
....................................................................................1
Compatibility Testing.....................................................................................................................................................................2
1.1
Hardware and Install Tests .............................................................................................................................................3
1.2
Unix testing ....................................................................................................................................................................4
1.3
CIFS testing ....................................................................................................................................................................4
1.4
Cluster Tests ...................................................................................................................................................................4
1.5
NDMP / Backup over a share Test ................................................................................................................................5
1.6
iSCSI ..............................................................................................................................................................................5
1.7
Virus Scan ......................................................................................................................................................................5
1.8
Filename and File Access Tests .....................................................................................................................................6
1.9
Snapshot, Snapmirror, Snaprestore Tests .......................................................................................................................6
1.10 Performance Testing ......................................................................................................................................................7
1.11 Quotas ............................................................................................................................................................................8
1.12 Networks and performance ............................................................................................................................................9
1.13 SNMP Monitoring/Autosupport .....................................................................................................................................9
12/08/17
Page 2 of 9
NETAPP FILER TESTING
1.1
Hardware and Install Tests
These tests 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.
To test dirty reboot time:
 Place the storage device under a write-intensive load,
 Give it some time to “wind up”, and
 Turn the power off at the wall.
Turning the power off at the wall is important because some devices feature “soft” power switches which tell the
device to shut down in an orderly manner and then signal the power supply to cut power. Hitting the power switch
on these devices is not an adequate simulation of power failure.
Task
Confirm Cold-Boot time (halt, then boot)
Confirm Warm Boot time (reboot)
Run through system setup to install filer
on network and supply with a hostname.
Time how long to complete install
process.
Confirm file system can be dynamically
extended by a single disk without
corrupting file system to demonstrate
system scaleability
Confirm file system can be dynamically
extended by a group of disks without
corrupting file system to demonstrate
system scaleability
Confirm operation of redundant power
supplies on Filer
Confirm operation of redundant power
supplies on Filer Disk Cage
Perform ‘Dirty Shutdown Test’ as
described above. Ensure no data is
corrupted and time how long before users
are able to access system again.
Swap out Filer head and then replace to
simulate replacement/upgrade of system.
Destroy entire data volume and recreate a
blank Volume.
Upgrade system software. Record effects
on users and time length of outage.
12/08/17
Result
Pass / Fail
Page 3 of 9
NETAPP FILER TESTING
1.2
Unix testing
These tests are intended to show the level of integration with a standard UNIX environment
Task
Add filer into NIS domain
Add NFS exports to share filer volumes
Create filer Qtree and share
Share the qtree to a specific IP address
only to test security
Share the qtree to a UNIX netgroup to test
security
Change permissions on qtree and ensure
that they are correct.
1.3
Result
Pass / Fail
CIFS testing
These tests are intended to show the level of integration with a standard NT environment
Task
Add filer into Windows domain
Browse filer properties with server
manager
Create a new share from server manager
Change properties of a share
Create CIFS alias for filer and add static
WINS mapping
Ensure clients can browse filer via both
names
Add, remove, then re-add Filer to Local
Domain
Create local groups on filer with
usermanager
Create Dfs root on a server and use as a
redirect to shares created on filer.
1.4
Result
Pass / Fail
Cluster Tests
Not applicable at this time but included for future reference.
Task
Manually initiate Fail Over between
Cluster Nodes. Time Failover. Check the
Virtual Names/Aliases
Initiate Fail Over by powering off one
cluster node. Time Failover.
Manually initiate Fail Back between
Cluster Nodes. Time Failback.
Initiate Fail Back by powering off live
cluster node. Time failback.
Force Failover by switching filer off. Once
Takeover is complete, switch off partner.
12/08/17
Result
Pass / Fail
Page 4 of 9
NETAPP FILER TESTING
Reboot 1st Filer. Can this filer see the
disks?
Use 2 different subnets, 1 per filer.
Simulate Failover. Ensure that remaining
filer can take over management of both
subnets.
Ensure that MAC addresses are correctly
failed over between units.
1.5
NDMP / Backup over a share Test
Build Window's server and install Legato
client.
Test data backup from window's server
perform restore
Attach tape drive(low voltage) to backend of
Netapp filer
Test data backup from window's server
Perform a complete restore
Build Window's server and install Legato
client.
Attach tape drive(low voltage) to backend of
window's server
Test data backup from window's server
Perform restore
1.6
iSCSI
Install the Microsoft iSCSI driver on a
Windows 2000 server and configure it to
connect to the filer after creating an iSCSI
LUN.
Verify that the LUN can be expanded “on-thefly” with no downtime.
Create a SnapShot on the LUN and then
destroy some data and then snaprestore the
data.
1.7
Virus Scan
Build dedicated Virus Scan server
Install Gig-E fiber card to direct connect to
filer
Test by unplugging virus scanner to validate
that all CIFS file sharing stops.
12/08/17
Page 5 of 9
NETAPP FILER TESTING
1.8
Filename and File Access Tests
These tests are intended to test migration of users to the filer from an existing user environment.
Task
Result
Pass / Fail
Copy at least 500 files and directories with
embedded spaces to and from the Filer
and determine if corruption of filenames
occurs
Configure a user account, to use the Filer
as a Home Directory. Logon to the user
account from a workstation. Confirm
correct functionality.
Add disks & increase the Volume size –
note impact on users.
Simulate network failure and impact to
users re access to data.
Management and Security Tests
These tests are intended to demonstrate the level of administration required and that the filer is a secure storage
system.
Task
Create local administration users for
configuration
Test Use of RSH for remote access and
configuration
Test Use of Telnet for remote access and
configuration
Test Use of Filerview for remote access
and configuration
Can SSL be used to provide
management, if required?
Test use of RSH for running scripted
commands on the filer from cron
Use syslog messages file to monitor
system
Export an area of filesystem only to root
users
Export an area of filesystem only to a
group of (non-root) users
Export an area of filesystem to a particular
netgroup of machines
1.9
Result
Pass / Fail
Snapshot, Snapmirror, 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.
If snapshots can be accessed from within the filesystem, users can recover their own lost or damaged data without
operator assistance.
If snapshots must be separately mounted, as for all non-integrated and most or all partially integrated snapshot
technologies, users might require help desk and/or system administrator assistance to recover damaged data.
12/08/17
Page 6 of 9
NETAPP FILER TESTING
To simulate common single-file data recovery from snapshots:
 Copy a large directory tree to a test volume
 Take a snapshot, or permit sufficient time for one to be taken automatically
 Make changes to the tree – adding, deleting, and modifying files
 Take another snapshot
 Make more changes and take more snapshots as required
 Delete some files
 Attempt to recover the previous contents of deleted or modified files.
To simulate the worst-case recovery of a whole filesystem due to database upgrade failure or application failure:
 Configure a large filesystem ( ie.100GB+)
 Copy in data until the filesystem is approximately 80% full
 Take a snapshot
 Over-write at least 10% of the data
Attempt to recover to the previous filesystem state.
Task
Create Snapshot Schedule to
automatically create snapshots at regular
periods during the day
Create Snapshot. Time how long this
takes and how long before you are able to
recover a deleted file (hint, this process is
described above).
Update file from Snapshot version
Open file in snapshot & roll over snapshot
Recover large deleted file from Snapshot
Hourly.0. Roll over a new Snapshot
during 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 whole filesystem as
described above.
Result
Pass / Fail
1.10 Performance Testing
Performance testing requires care and attention to detail. Designing accurate benchmarks is sometimes difficult,
and it’s all too easy to fall into the following trap:
We need to measure something.
Copying files is something.
Let’s do that!
Unfortunately, the vast majority of workloads don’t greatly resemble file copying. Peak throughput rarely predicts
usable application performance for anything but seismic analysis and digital film compositing, especially when
comparing filesystems with different head-seeking characteristics.
Like file copying, many “professional” benchmarks also concentrate on throughput (total bytes shipped per second)
rather than response times (how long it takes a user to get hold of the specific bytes they requested). SPEC SFS is
a notable exception.
12/08/17
Page 7 of 9
NETAPP FILER TESTING
Finally, many benchmarks are affected by client-side caching.
The easiest way to predict your application’s eventual performance on a given system is to employ the application
itself (or a cut down but representative portion) to do the testing.
The questions to ask when designing a performance test plan are:




What is the peak load that must be supported and what are the units of measure?
o For batch jobs, duration is usually the key measure.
o For interactive workloads, response times are usually the key measure.
Is test data available, or can it be automatically generated?
Can the existing application be used to generate the desired load?
Do random transactions need to be generated to test the applications?
If so, is a tool available to run and measure the transactions?
To test performance under real conditions, all tests should be run with snapshots turned on for that volume. Also,
some snapshot architectures incur a performance penalty when snapshots are taken because the manner in which
filesystem writes are handled changes.
The following tests will help establish the level of performance impact:


Configure a filesystem
Run a write benchmark that generates new data in the filesystem. The working set should be larger than any
memory buffer in the storage device used for write staging.
 Copy in data until the filesystem is approximately 50% full
 Take a snapshot
 Run the write benchmark again
An observable write performance impact indicates a non-integrated snapshot technology.

Repeat the above benchmark, but using write benchmarks that over-write existing files.
An observable write performance impact indicates a partially integrated snapshot technology. On file sharing
volumes, which have a “write new file, erase old file” workload, write performance would also be impacted
whenever total data updates exceed free disk space over the lifetime of the snapshot. To simulate the use of
snapshots for a typical grandfather/father/son backup policy, create at least 10 snapshots running performance
tests each time and ensure no write performance degradation.
Task
Result
Pass / Fail
1.11 Quotas
These tests are intended to demonstrate the use of quotas as a logical filesystem within a volume. Quota use
enhances manageability through the use of dynamic space allocation and management to groups, projects and
users. User quotas are particularly important as they prevent individual users claiming too much disk space.
Task
Use the QTREE function to set up a
quota’d area of filer disk (qtree create…).
This will behave as a logical partition of a
large volume into smaller volumes
12/08/17
Result
Pass / Fail
Page 8 of 9
NETAPP FILER TESTING
Configure UID based user quotas
Configure group quotas on a qtree
Run quota report to monitor quotas
1.12 Networks and performance
These tests demonstrate the ability of the filer to cope with a network failure and demonstrate the level of
interruption visible to users.
Task
Configure multiple NIC cards in filer for
redundancy and remove a link to test
Failover. Time how long Failover takes to
occur and note effects of Failover to a
user.
Confirm Operation of Autosupport Email
Notification
Change the IP address of a network
interface. Is a reboot required to make
this change work?
Result
Pass / Fail
1.13 SNMP Monitoring/Autosupport
These tests demonstrate the automatic notification and enhanced monitoring functions of the filer. This in turn is
intended to simplify the monitoring and management process.
Task
Setup Filer SNMP to report to a
management station.
Setup autosupport to report to
administration team
Switched off power supply in head unit.
Check SNMP/autosupport
Switched off one power supply in disk
shelf. Check SNMP/autosupport
Remove assigned 'spare' disk from array.
Check SNMP/autosupport
Remove assigned Raid Disk from array.
Check SNMP/autosupport
Removed fan from head unit. Check
SNMP/autosupport
Removed fan from shelf unit. Check
SNMP/autosupport
Reboot a filer. Check SNMP/autosupport
12/08/17
Result
Pass / Fail
Page 9 of 9