Re: [ADSM-L] Best practices on filesystem for DB and ACTLOG on RHEL7

Robert:

According to this document:
http://www-01.ibm.com/support/knowledgecenter/SSGSG7_7.1.1/com.ibm.itsm.perf.doc/t_perf_diskos_lnx.html


   - Use Linux Logical Volume Manager (LVM) to create logical volumes on
   the disk LUNs for all disks that are used for Tivoli Storage Manager
    components.

   Set the LVM read-ahead to 0 for all logical volumes on disk systems that
   provide adaptive read-ahead capabilities, for example, enterprise-type disk
   systems.

   If more space is needed, the logical volumes provide an easy way to
   extend the volumes and file systems. LVM also provides striping, which can
   be used to improve sequential I/O performance.
   - For the Tivoli Storage Manager database and logs, use either the ext3
   or ext4 file system. As a best practice, use the following file system
   that is appropriate for your operating system and level:
      - For Red Hat Enterprise Linux x86_64, use the ext3 or ext4 file
      system. Use the ext4 file system only if Red Hat Enterprise Linux 6.4 or
      later is installed.
      - For SUSE Linux Enterprise Server and for Red Hat Enterprise Linux
      ppc64, use the ext3 file system.
   - For Tivoli Storage Manager storage pools, use the ext4 file system. The
   ext4 file system has the following advantages for use with storage pools:
      - You do not have to write out each block I/O to allocate the storage
      pool volume, which improves the performance of the DEFINE VOLUME
       command.
      - You can avoid file and free space fragmentation, which improves
      read and write performance.
      - When you define new volumes, the Tivoli Storage Manager server
      activities that are running are not negatively affected.


Best regards,

Mike, x7942
RMD IT Client Services

On Sun, Mar 22, 2015 at 5:04 PM, Robert Lejtorp <robert.lejtorp AT compose DOT 
se>
wrote:

> Hi
>
> I'm about to install a new TSM 7.1.1 server on RHEL7 and would like to
> have some input on what file system to use, and if I should consider any
> special options.
>
> My first concerns is about the volumes where I intend place the DB and the
> actlog.
> We have an IBM x3650 M4 and five 400 GB SSD-drives (SATA-connector) in an
> hw-RAID5 setup to be used by TSM-DB and the actlog.
> The OS, arch-log and some space to be used for meta-data from TSM4VE
> backups is located on another hw-RAID5 of five SAS-volumes.
>
> Default file system in RHEL7 is now xfs, and my question is if I should
> stick to what RedHat suggests or if I should go for EXT4 for some reason.
> Are there any special concerns to keep in mind for performance (like
> allocation group size and stripe units on xfs) or will "standard" do the
> work equally good ?
>
> The blueprint for TSM server on Linux_x86 specifies ext4, but it's for
> TSM7.1 and RHEL6.4
>
> Best regards
> Robert Lejtorp
> Compose IT
>