SAP filesystem layout on Solaris 10 Assistance

[former_member229542]

Hi Guys,

I'd like to ask who has experience running SAP over Solaris a few questions regarding filesystem. I have strong backgound on AIX server but little over Solaris, so im transitioning from AIX to Solaris to understand this

My goal is to identify/Analyse how a SAP instance was installed on a Solaris Server and if so, following Best Practices.

First of all is to determine if the /usr/sap/PRD and Oracle filesystems where mounted all on the root directory or if were mounted

on separate filesystems which is the recommended setup

As example i have this output for df -g

/oracle/PRD (/dev/dsk/c4t0d2s5 😞

/sapmnt/PRD (/dev/dsk/c4t0d6s5 )

/home/prdadm (/dev/dsk/c4t0d7s3 😞

/usr/sap/PRD (/dev/dsk/c4t0d5s3 😞

/oracle/PRD/oraarch(/dev/dsk/c4t0d9s0)

/oracle/PRD/sapdata14(/dev/dsk/c4t0d8s0 )

/oracle/PRD/sapdata15(/dev/dsk/c4t0d4s0 )

/oracle/PRD/origlogA(/dev/dsk/c4t0d7s0 😞

/dev/dsk/xxxxxxxxx does mean they are all on the "root" directory instead being splitted into multiple filesystems?

Which commands would be helpful to analyze the Disk layout of this Server so I can understand how SAP was mounted:

devices ( HDD )

Volume Groups

Logical Volumenes

and file systems

(On AIX lsvg, lslv would be the choices)

Any help would be highly appreciated

Regards!

[markus_doehr2 · Accepted solution]

> As example i have this output for df -g

>

> /oracle/PRD (/dev/dsk/c4t0d2s5 😞

> /sapmnt/PRD (/dev/dsk/c4t0d6s5 )

> /home/prdadm (/dev/dsk/c4t0d7s3 😞

> /usr/sap/PRD (/dev/dsk/c4t0d5s3 😞

>

> /oracle/PRD/oraarch(/dev/dsk/c4t0d9s0)

> /oracle/PRD/sapdata14(/dev/dsk/c4t0d8s0 )

> /oracle/PRD/sapdata15(/dev/dsk/c4t0d4s0 )

> /oracle/PRD/origlogA(/dev/dsk/c4t0d7s0 😞

>

> /dev/dsk/xxxxxxxxx does mean they are all on the "root" directory instead being splitted into multiple filesystems?

/dev/dsk/c4t0 is the hardware path, the following d2|d6 etc. is the disk, the s5 is the slice.

> Which commands would be helpful to analyze the Disk layout of this Server so I can understand how SAP was mounted:

>

> devices ( HDD )

> Volume Groups

> Logical Volumenes

> and file systems

Solaris has a builtin Volume manager, the setup is very different to AIX. For documentation see

http://download.oracle.com/docs/cd/E19253-01/816-4520/

According to what you posted no volume manager is used at all on this system, it has a fixed disk/slice configuration.

Most likely the filesystem used is UFS.

Markus

[former_member188883 · Accepted solution]

Hi ,

In addition to Marku's response, I would suggest you go for ZFS file system on Solaris. This has better performance capabilities as compared to UFS file systems. There are certain SAP notes available for the same.

Regards,

Deepak Kori

[former_member229542 · Accepted solution]

Indeed Markus, all the filesystems shows UFS type

/sapmnt/PRD (/dev/dsk/c4t0d6s5 😞 8192 block size 1024 frag size

2235806 total blocks 690536 free blocks 578746 available 268800 total files

249597 free files 80478317 filesys id

ufs fstype 0x00000004 flag 255 filename length

[former_member229542 · Accepted solution]

Regarding this Solaris Volume Manager, how can you verify is not being used at all on this system? Is there a Main Menu or command to access/verify this.

Using metastat is showing not found so i suppose is not installed.

Thanks a lot for the info supplied on this.

Edited by: Martin Luis Simois on Oct 20, 2011 5:51 PM

[markus_doehr2 · Accepted solution]

> Regarding this Solaris Volume Manager, how can you verify is not being used at all on this system? Is there a Main Menu or command to access/verify this.

>

> Using metastat is showing not found so i suppose is not installed.

yes - exactly. 'metastat' is the command to show the volumes.

The device names would then be /dev/md/XXX instead of the real disk names.

Markus

[former_member229542 · Accepted solution]

I have found two filesystems with /dev/md/dsk/xxx

/var/crash (/dev/md/dsk/d12 😞 8192 block size 1024 frag size

30986500 total blocks 30955728 free blocks 30645864 available 1869504 total files

1869499 free files 22282252 filesys id

ufs fstype 0x00000004 flag 255 filename length

/export/home (/dev/md/dsk/d6 😞 8192 block size 1024 frag size

145738384 total blocks 144923236 free blocks 143465854 available 8770944 total files

8770907 free files 22282246 filesys id

ufs fstype 0x00000004 flag 255 filename length

[markus_doehr2 · Accepted solution]

try

cat /etc/vfstab

Markus

[former_member229542 · Accepted solution]

Hi Markus, thanks a lot for your helpul assistance.

I have found the metastat command and this is the output (there are a few more lines which i cropped out)

d0: Mirror

Submirror 0: d1

State: Okay

Submirror 1: d2

State: Okay

Pass: 1

Read option: roundrobin (default)

Write option: parallel (default)

Size: 31464192 blocks (15 GB)

d1: Submirror of d0

State: Okay

Size: 31464192 blocks (15 GB)

Stripe 0:

Device Start Block Dbase State Reloc Hot Spare

c1t0d0s0 0 No Okay Yes

d2: Submirror of d0

State: Okay

Size: 31464192 blocks (15 GB)

Stripe 0:

Device Start Block Dbase State Reloc Hot Spare

c1t1d0s0 0 No Okay Yes

d6: Mirror

Submirror 0: d7

State: Okay

Submirror 1: d8

State: Okay

Pass: 1

Read option: roundrobin (default)

Write option: parallel (default)

Size: 147979392 blocks (70 GB)

d7: Submirror of d6

State: Okay

Size: 147979392 blocks (70 GB)

Stripe 0:

Device Start Block Dbase State Reloc Hot Spare

c1t0d0s5 0 No Okay Yes

d8: Submirror of d6

State: Okay

Size: 147979392 blocks (70 GB)

Stripe 0:

Device Start Block Dbase State Reloc Hot Spare

c1t1d0s5 0 No Okay Yes

d3: Mirror

Submirror 0: d4

State: Okay

Submirror 1: d5

State: Okay

Pass: 1

Read option: roundrobin (default)

Write option: parallel (default)

Size: 67120896 blocks (32 GB)

/dev/dsk/c4t0d0s0 47518960 42125738 4918033 90% /oracle/PRD/sapdata10

/dev/dsk/c4t0d6s1 595367 103529 432302 20% /oracle/PRD/mirrlogA

/dev/dsk/c4t0d4s1 21688320 19606011 1865426 92% /oracle/PRD/sapdata7

/dev/dsk/c4t0d2s0 21688320 19190074 2281363 90% /oracle/PRD/sapdata9

/dev/dsk/c4t0d1s4 21688320 19060970 2410467 89% /oracle/PRD/sapdata6

/dev/dsk/c4t0d2s1 21688320 19183908 2287529 90% /oracle/PRD/sapdata11

/dev/dsk/c4t0d1s5 4140798 3731204 368187 92% /oracle/PRD/102_64

/dev/dsk/c4t0d1s1 21688320 19667475 1803962 92% /oracle/PRD/sapdata4

/dev/dsk/c4t0d0s5 4140798 803382 3296009 20% /oracle/PRD/sapreorg

/dev/dsk/c4t0d2s3 21688320 19118355 2353082 90% /oracle/PRD/sapdata8

/dev/dsk/c4t0d2s4 21688320 19210108 2261329 90% /oracle/PRD/sapdata12

/dev/dsk/c4t0d6s3 595367 103529 432302 20% /oracle/PRD/mirrlogB

/dev/dsk/c4t0d1s3 21688320 19606010 1865427 92% /oracle/PRD/sapdata5

/dev/dsk/c4t0d0s4 4235310 4209 4188748 1% /oracle/PRD/920_64

/dev/dsk/c4t0d0s1 21688320 20619709 851728 97% /oracle/PRD/sapdata1

/dev/dsk/c4t0d1s0 21688320 19585518 1885919 92% /oracle/PRD/sapdata3

/dev/dsk/c4t0d0s3 21688320 19081466 2389971 89% /oracle/PRD/sapdata2

/dev/dsk/c4t0d3s3 52680950 48352676 3801465 93% /oracle/PRD/sapdata13

/dev/dsk/c4t0d1s6 4140798 21434 4077957 1% /oracle/PRD/saparch

/dev/dsk/c4t0d5s3 2483215 1747267 711116 72% /usr/sap/PRD

/dev/dsk/c4t0d8s0 36097748 30770868 4965903 87% /oracle/PRD/sapdata14

/dev/dsk/c4t0d4s0 73330400 64717106 7879990 90% /oracle/PRD/sapdata15

/dev/dsk/c4t0d7s0 595367 133682 402149 25% /oracle/PRD/origlogA

/dev/dsk/c4t0d7s1 595367 133682 402149 25% /oracle/PRD/origlogB

/dev/dsk/c4t0d5s0 3743550 2905577 800538 79% /usr/sap/put

/dev/dsk/c4t0d9s0 20611033 260483 20144440 2% /oracle/PRD/oraarch

I don see any dev/dsk/c4t0dxxx device listed on the metastat output, does this means any of the c4t0dxxx is being managed by the SVM?

[former_member229542 · Accepted solution]

$ cat /etc/vfstab

#device device mount FS fsck mount mount

#to mount to fsck point type pass at boot options

#

fd - /dev/fd fd - no -

/proc - /proc proc - no -

/dev/md/dsk/d3 - - swap - no -

/dev/md/dsk/d0 /dev/md/rdsk/d0 / ufs 1 no logging

/devices - /devices devfs - no -

ctfs - /system/contract ctfs - no -

objfs - /system/object objfs - no -

swap - /tmp tmpfs - yes -

/dev/md/dsk/d6 /dev/md/rdsk/d6 /export/home ufs 2 yes logging

/dev/md/dsk/d12 /dev/md/rdsk/d12 /var/crash ufs 2 yes logging

/dev/dsk/c4t0d0s6 /dev/rdsk/c4t0d0s6 /opt/JES ufs 2 yes -

/dev/dsk/c4t0d2s5 /dev/rdsk/c4t0d2s5 /oracle/PRD ufs 2 yes -

/dev/dsk/c4t0d2s0 /dev/rdsk/c4t0d2s0 /oracle/PRD/sapdata9 ufs 2 yes -

/dev/dsk/c4t0d2s1 /dev/rdsk/c4t0d2s1 /oracle/PRD/sapdata11 ufs 2 yes -

/dev/dsk/c4t0d2s4 /dev/rdsk/c4t0d2s4 /oracle/PRD/sapdata12 ufs 2 yes -

/dev/dsk/c4t0d0s1 /dev/rdsk/c4t0d0s1 /oracle/PRD/sapdata1 ufs 2 yes -

/dev/dsk/c4t0d0s5 /dev/rdsk/c4t0d0s5 /oracle/PRD/sapreorg ufs 2 yes -

/dev/dsk/c4t0d0s3 /dev/rdsk/c4t0d0s3 /oracle/PRD/sapdata2 ufs 2 yes -

/dev/dsk/c4t0d4s1 /dev/rdsk/c4t0d4s1 /oracle/PRD/sapdata7 ufs 2 yes -

/dev/dsk/c4t0d2s3 /dev/rdsk/c4t0d2s3 /oracle/PRD/sapdata8 ufs 2 yes -

/dev/dsk/c4t0d1s1 /dev/rdsk/c4t0d1s1 /oracle/PRD/sapdata4 ufs 2 yes -

/dev/dsk/c4t0d0s0 /dev/rdsk/c4t0d0s0 /oracle/PRD/sapdata10 ufs 2 yes -

/dev/dsk/c4t0d1s5 /dev/rdsk/c4t0d1s5 /oracle/PRD/102_64 ufs 2 yes -

/dev/dsk/c4t0d1s3 /dev/rdsk/c4t0d1s3 /oracle/PRD/sapdata5 ufs 2 yes -

/dev/dsk/c4t0d0s4 /dev/rdsk/c4t0d0s4 /oracle/PRD/920_64 ufs 2 yes -

/dev/dsk/c4t0d1s6 /dev/rdsk/c4t0d1s6 /oracle/PRD/saparch ufs 2 yes -

/dev/dsk/c4t0d1s0 /dev/rdsk/c4t0d1s0 /oracle/PRD/sapdata3 ufs 2 yes -

/dev/dsk/c4t0d1s4 /dev/rdsk/c4t0d1s4 /oracle/PRD/sapdata6 ufs 2 yes -

/dev/dsk/c4t0d6s1 /dev/rdsk/c4t0d6s1 /oracle/PRD/mirrlogA ufs 2 yes -

/dev/dsk/c4t0d6s3 /dev/rdsk/c4t0d6s3 /oracle/PRD/mirrlogB ufs 2 yes -

/dev/dsk/c4t0d5s0 /dev/rdsk/c4t0d5s0 /usr/sap/put ufs 2 yes -

#/dev/dsk/c4t0d6s0 /dev/rdsk/c4t0d6s0 /usr/sap/PRD ufs 2 yes -

/dev/dsk/c4t0d5s3 /dev/rdsk/c4t0d5s3 /usr/sap/PRD ufs 2 yes -

/dev/dsk/c4t0d6s5 /dev/rdsk/c4t0d6s5 /sapmnt/PRD ufs 2 yes -

/dev/dsk/c4t0d7s0 /dev/rdsk/c4t0d7s0 /oracle/PRD/origlogA ufs 2 yes -

/dev/dsk/c4t0d7s1 /dev/rdsk/c4t0d7s1 /oracle/PRD/origlogB ufs 2 yes -

/dev/dsk/c4t0d7s3 /dev/rdsk/c4t0d7s3 /home/prdadm ufs 2 yes -

/dev/dsk/c4t0d7s4 /dev/rdsk/c4t0d7s4 /instalar ufs 2 yes -

/dev/dsk/c4t0d7s5 /dev/rdsk/c4t0d7s5 /oracle/stage ufs 2 yes -

/dev/dsk/c4t0d3s3 /dev/rdsk/c4t0d3s3 /oracle/PRD/sapdata13 ufs 2 yes -

/dev/dsk/c4t0d8s0 /dev/rdsk/c4t0d8s0 /oracle/PRD/sapdata14 ufs 2 yes -

/dev/dsk/c4t0d4s0 /dev/rdsk/c4t0d4s0 /oracle/PRD/sapdata15 ufs 2 yes -

/dev/dsk/c4t0d9s0 /dev/rdsk/c4t0d9s0 /oracle/PRD/oraarch ufs 2 yes -

/dev/dsk/c4t0d3s0 /dev/rdsk/c4t0d3s0 /moniora ufs 2 yes -

sandboxifrs:/usr/sap/trans - /usr/sap/trans nfs - yes soft,bg

##10.18.251.34:/vol/ELOPESAPVOL - /REDOTEMPORAL nfs - yes soft,bg

10.18.251.37:/V490 - /RESPALDO nfs - yes soft,bg,vers=3

[markus_doehr2 · Accepted solution]

As you can see, all the /dev/md/* are volume manager devices and the rest with the direct block device path /dev/dsk/* are not done by the volume manager.

Markus

[former_member229542 · Accepted solution]

Thanks Markus for all your help