ProvidenceNAS Upgrade Project

Will EvansPete Bluett

Tom ConleeRick Alsop

September 8, 2011

2

Project Background• Current NetApp v3140 in Tigard is coming off lease and needs to be replaced.• New Data Center being build. Need plan to migrate File System data to new data center with

minimal impact to user community.• Current method of backing up NetApp filers with NDMP protocol is proving inadequate.

Backups do not consistently complete within a single day window.» This is inadequate in terms of getting full copies of production data offsite daily.

• Current method of providing normal production backups is insufficient in that only 2 weeks of data is maintained in Snapshot copies. All data over 2 weeks old must be restored from tape with administrative support.

• There do not appear to be any performance bottlenecks.• Current NetApp v3140 in Sabey is also coming off lease soon and it may be appropriate to

address both centers at the same time. Sabey v3140 is out of capacity.

• This project will address the “Operational” backups only. It is understood that this project should ultimately support legal retention and archival but those are not directly addressed in this solution.

3

Performance - Tigard• Current understanding of performance of existing v3140 production

environment in Tigard:» There are approximately 12,000 IOPS between both filer controllers at

absolute peak usage.» Disk utilization in the current environment is relatively low averaging around

10%.» There do not appear to be any performance bottlenecks.» Controller utilization averages close to 50% with peaks near 90%.» The vast majority of IO operations during the production day are read

operations.

4

Performance - Sabey• Current understanding of performance of existing v3140 production

environment in Sabey:» There are approximately 2,500 IOPS between both filer controllers during

regular day. 4,500 IOPS at peak night time usage.» Disk utilization in the current environment is relatively low averaging around 10%

- 20%.» Controller utilization:

– Nas7464 is generally under 20% with night time peaks ~50%– Nas7476 is generally under 30% with night time peaks over 50%

» The vast majority of IO operations during the production day are read operations. >95%

» There do not appear to be any performance bottlenecks.» nas7464 is less utilized than nas7476. All NFS traffic is on nas7476.» Sabey system needs additional capacity to address current requirements.

5

6

7

vSeries OptionsPPMC Quincy Sabey

Req’d IOPS 12,000 12,500 2,500

Req’d Usable TB ~50 100+ ~50

Option A:SATA SpindlesSATA Usable TB

192 1TB 104 TiB (20% Reserve)

192 1TB 104 TiB (20% Reserve)

120 1TB 58 TiB (20% Reserve)

Option B:SAS SpindlesSAS Usable TB

120 600GB48 TiB (20% Reserve)

Same as Option A:

Same as Option A.

Option C:SATA SpindlesSATA Usable TB

120 1TB 58 TiB (20% Reserve)

Same as Option A: with Sabey120 1TB drives without Sabey.

Same as Option A.

8

9

10

11

12

13

14

15

16

Summary• Solution provides interim storage to accommodate data center

move• Solution provides new NetApp v3270 in PPMC on new lease

schedule with increased capacity and throughput.• Solution provides new NetApp v3270 in Quincy to address

offsite data repository.» V3270 will have capacity to support replication data from both Sabey

and PPMC. » V3270 will be able to support production throughput for either PPMC or

Sabey but not both concurrently.• Solution optionally provides new NetApp v3240 in Sabey on

new lease schedule with increased capacity and throughput.• Solution improves production backup and restore. 90 days of

Snapshots can be maintained in PPMC, Sabey and Quincy. Tapes are potentially no longer required for production backups. This solution does not directly address the requirements for archival and legal retention.

17

Questions or

Comments?

Next Steps?