Subscribe

SAP on NetApp

Hi,

I have a question regarding SAP on NetApp.Basically I was told that each node has it's own set of disk drives and volumes that is controls. For failover, it takes 30 seconds or more for the disk drivers to move to the other node, so this will affect the OSes running on the failed controllers, since the Luns/Disk Drives would be unresponsive for over 30 seconds. I'd like to get confirmation from if this is really true or not, plus what alternative solution can NetApp provide?

We are looking at two storage solutions for our company. Below is a throughput & DB size info for your reference.

Current Disk Usage All Current Requirement3 Year GrowthTotal After 3 YearsDeduplication PercentageNetapp Requrirements with DeduplicationNetapp Flexclone Requirements (30%)XIV SNAPShot Requirements (40%)Netapp at Shaw with DRNetapp at Q9 with DRNetapp at Shaw with no DRNetapp at Q9 with no DRXIV at Shaw Court with DRXIV at Q9 with DRXIV at Shaw Court with no DRXIV at Q9 with no DR
SAPSAP Production9,7092,69012,3990.00%123991611917359161191611916119 173591735917359
SAP Non-Production20,1775,38025,5570.00%255573322435780 3322433224 3578035780
SAP TSM1,457 1,4570.00%145718942040189418941894 204020402040
Future SAP Projects1,028 1,0280.00%1028133614396686681336 143914391439
Technical ServicesFile Services23407023,04230.00%21292768425927682768 276842594259 4259
Database8102431,0530.00%10531369147413691369 136914741474 1474
ESX173245197.222,52160.00%900811711315301171111711 117113153031530 31530
TSM43971319.15,7160.00%57167431800374317431 743180038003 8003
Email (Include this number with exchange for recovery)1135340.51,4760.00%14761918206619181918 191820662066 2066
Exchange (number from Netapp)88652659.511,5250.00%1152514982161341498214982 149821613416134 16134
Cardlock (Guess)20006002,6000.00%26003380364033803380 338036403640 3640
Intranet Re-Launch (Guess)20006002,6000.00%26003380364033803380 338036403640 3640
Office 2010 Project (Guess)20006002,6000.00%26003380364033803380 338036403640 3640
Total 73,24220,33293,574 79148102893131003690001022255257450319952231310035661874385

Re: SAP on NetApp

Yes, each controller in HA pair has own set of disks which are taken over by partner if controller fails.

Takeover time depends on many factors, but 30 seconds could be considered as rule of thumb average. Hosts are expected to be configured so that they won’t fail (by settings appropriate timeouts, number of retries etc).

Please understand that any vendor that offers failure tolerance against path failure will face exactly the same situation – there will be some timeout before host finally gives up on failed path and continues (retries) over remaining ones. Such timeouts are usually in order of 60 seconds. So there is nothing unusual in how NetApp behaves.

Re: SAP on NetApp

I have good experience with running SAP, its Oracle databases and virtual ESX servers over NFS on NetApp storage. When the timeout has been configured properly on your (virtual) hosts, storage failovers do not cause problems.

Re: SAP on NetApp

As other people have said on here, configured correctly it shouldn’t have impact on your database…

It also maybe a matter of what you are trying to achieve as well… for example technology such as metro cluster would allow you to spread the controllers across datacenters with automated failover of disks…and things like local syncmirror allows you to protect at a disk shelf level…

Of course you also have to look at your server builds for config purposes etc…

Then finally gets to the major value of NetApp in this environment, things like dedupe for space efficiency, the protection technologies for SAP to protect workloads with snapshot backups and snapmirror/snapvault to get this data to an alternate location.

Flexclone another excellent feature in a SAP environment, allowing for zero sized clones of production data to provision up to your dev, test, QA environments are hugely efficient in terms of space and speed of delivery…

So without giving to much of a netapp sales pitch… the NetApp value is a much bigger proposition than how quickly cluster failover works…and as has been said…cluster failovers work pretty much the same for all vendors…which is why I thought mentioning the rest of the value proposition maybe helpful…

Good luck with your decision…

Re: SAP on NetApp

Thanks for your reply.  I did a search about metro cluster and it seems that metro cluster for SAP does not really work, you need your app servers close to the Database. So 3-4 Hours to spin up at the alternate site meets the business requirement, so I would keep it simple. Also would need hot standby servers for Database and Application servers (high cost for something that mey never be used). I think Metro Cluster for email is good but maybe not on our SAP environment.

Re: SAP on NetApp

I think you’re right…metrocluster is a specialist technology but needed for people who don’t want downtime…it needs to work with a server environment capable of taking advantage of it…so for example we have some installations where we have vmware stretched between DC’s with metrocluster…so vm’s can be spun up immediately in the DR site if needed…no long delay…

In your case if you are going to mirror to another site, then flexclone will have massive value as you can clone you DR instances, without having to break the mirror relationship, to do full DR test.

Obviously flexclone great for SAP environments in terms of Dev, Test, QA etc…zero sized copies of production, created quickly and efficiently…

Anyway all I’d say look at what NetApp can bring, much more function that anyone else on the market…but then look at if that technology is relevant and has business value…if it does NetApp is your answer…if not…then maybe other platforms have validity…

Good luck on your search!

Feel free to drop me a question if you need to…