Directory-ontainers on AIX, best practices?

[Rigido]

Hi,
yesterday I had to define a DC "on the fly" on a customer site with a full DataDomain and this made me think about DC physical management on an AIX system. Does "SP blue print" document help about this?
Let's say we have a 100TB enterprise storage, what's the best practice?
1 100TB LUN or 10 10TB LUNs? If we go with 10 LUNs, we should define a single VG, a reasonable number of VGs or 1 VG per PV? How about Logical Volumes? Inline log or a separate log volume? Spread LV among different PVs or go with 1 PV = 1 VG = 1 LV = 1FS?

Thank you.

 

[marclant]

You can find the Blueprint here:
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli Storage Manager/page/IBM Spectrum Protect Blueprints

First, you need to determine if the environment is a Small, Medium or Large depends. Page 3, table 1 will help you make that determination.

Once you know which size Blueprint to use, you can check the disk the layout at Page 10, table 6. Note that the database layout is extremely important too. I have seen too many performance problems from inadequate database disks configuration.

Chapter 4, Step 4 (page 30) gives you all the commands to setup your file systems.

After configuring the DB and storage pool disks, make sure to use tsmdiskperf.pl (Chapter 4, Step 6, page 35) from the BluePrint utilities and make sure your results match those in Appendix A. If you can't get the same IOPS and throughput, address it immediately. It's much easier to change the config before it's in production.

More best practice info:
https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.0/perf/t_srv_hw_check.html
View attachment 1515

 

[Rigido]

This is a good starting point

Assign directories to a storage pool by using the DEFINE STGPOOLDIRECTORY command.
Create multiple storage pool directories and ensure that each directory is backed up to a separate disk volume (LUN).

So it looks like 1PV:1VG:1LV:1FS is an easy start, so you don't have to mess with LV mapping, etc.

Thanks.

 

[marclant]

This is a good starting point

So it looks like 1PV:1VG:1LV:1FS is an easy start, so you don't have to mess with LV mapping, etc.

Thanks.

Nope. Check: Chapter 4, Step 4 (page 30)

 

[booman55]

If the Data Domain is doing dedup you may run into performance issues getting data off of it. Dedup on top of dedup is not a good recipe. We had a customer that insisted on using a Data Domain and it's now been replaced with v5000 storage since restoring a large DB was taking 10x the amount of time it took to do the backup.