SnapManager for SQL Server - Disk Configs

Here's a quick one-pager for you.
Create three 1GB FlexVols and put a 500MB LUN in each.
Assign three drive letters (E, F and G in this case).
Databases are E. Transaction logs are F. SnapInfo is G.
System Databases:

• Create a FlexVol and LUN for each of them and mount those LUNs into the root of E.
• Create a FlexVol and LUN for all of them except temp and mount into the root of G.
• Run SMSQL Configuration wizard and move the files into the relevant locations in E and G.

There are no files in F because you keep the logs with the databases.
User databases:

• As above but create a FlexVol and LUN for the transaction logs.
• Run the configuration wizard and move the files.

Options?

• To keep your LUN count down you can use the same FlexVol and LUN for all the Snapinfo directories. Or not. The trick is to decide what RPO you need to maintain and lump everything that has a similar SLA into the one FlexVol. SnapMirror the FlexVols to suit your RPO.
• Remember that NetApp can do anything, anyhow and not to look at LUNs so much as look at what protection you want for your databases.
• Remember that in a DR environment you're going to want your Master database in your DR location so that needs to be SnapMirrored but you don't necessarily need the other system databases.
• Remember not to SnapMirror the temp database. You can't actually back it up so that's no problem.

And finally. I'm sorry. Yes. The GUI. Yes. Sorry. Engineering are on it.