Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+Disk\s+layout\s+for\s+AIX\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+Disk\s+layout\s+for\s+AIX\s*$/: 8 ]

Total 8 documents matching your query.

1. [ADSM-L] Disk layout for AIX (score: 1): Author: "Huebner, Andy" <andy.huebner AT NOVARTIS DOT COM>; Date: Wed, 15 Jul 2015 13:02:34 +0000; I have an AIX admin that wants to build my new TSM server using two VGs for the database (6 file systems) and one VG for the various logs. We currently have 6 VGs for the DB and 3 VGs for the logs. E; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2015-07/msg00052.html (12,129 bytes)
2. Re: [ADSM-L] Disk layout for AIX (score: 1): Author: David Ehresman <david.ehresman AT LOUISVILLE DOT EDU>; Date: Wed, 15 Jul 2015 13:11:46 +0000; VGs are cheap. Why does your AIX admin want to reduce the number of VGs? David Ehresman I have an AIX admin that wants to build my new TSM server using two VGs for the database (6 file systems) and o; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2015-07/msg00053.html (12,568 bytes)
3. Re: [ADSM-L] Disk layout for AIX (score: 1): Author: "Huebner, Andy" <andy.huebner AT NOVARTIS DOT COM>; Date: Wed, 15 Jul 2015 13:32:47 +0000; He claims there is a queuing issue with too many at the HBA. I guess I missed that the last 12 years of being a storage/TSM admin. I told him the theory of using many was to allow more concurrency. B; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2015-07/msg00056.html (13,266 bytes)
4. Re: [ADSM-L] Disk layout for AIX (score: 1): Author: "Rhodes, Richard L." <rrhodes AT FIRSTENERGYCORP DOT COM>; Date: Wed, 15 Jul 2015 13:53:12 +0000; With your current vg setup you are dedicating one or more luns to each vg. The good is dedicated resources of that lun (iops+capacity) in each vg. But the converse is also true, you _only_ have the d; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2015-07/msg00057.html (15,938 bytes)
5. Re: [ADSM-L] Disk layout for AIX (score: 1): Author: "Barkes, Jason" <jason.barkes AT SSE DOT COM>; Date: Wed, 15 Jul 2015 13:54:12 +0000; Hi, Sorry David I don't understand the VG's are cheap statement. Your Volume groups are made up of 1 or more hdisks provided locally or from the SAN. I've split my VG's into 5 types of VGs Dbvg <- Da; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2015-07/msg00058.html (14,738 bytes)
6. Re: [ADSM-L] Disk layout for AIX (score: 1): Author: "Huebner, Andy" <andy.huebner AT NOVARTIS DOT COM>; Date: Wed, 15 Jul 2015 14:10:36 +0000; Each VG will be 2 or 4 LUNs from SVC. I am not worried about the logs and storage pools. Only the DB. Andy Huebner Hi, Sorry David I don't understand the VG's are cheap statement. Your Volume groups; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2015-07/msg00059.html (15,208 bytes)
7. Re: [ADSM-L] Disk layout for AIX (score: 1): Author: "Rhodes, Richard L." <rrhodes AT FIRSTENERGYCORP DOT COM>; Date: Wed, 15 Jul 2015 14:15:17 +0000; The concurrency I'm aware of is at the hdisk/lun level. There's a num_cmd_elems at on the fcs adapter which we set to 2k, and then queue_depth on the hdisk. That's why spreading I/O across as many hd; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2015-07/msg00060.html (14,465 bytes)
8. Re: [ADSM-L] Disk layout for AIX (score: 1): Author: "Rhodes, Richard L." <rrhodes AT FIRSTENERGYCORP DOT COM>; Date: Wed, 15 Jul 2015 15:20:29 +0000; What seems like not that long ago we ran our databases on JBOD disks (disks if 250m to 1gb). We setup oracle per design - logs on one disk, db files on another, redo logs on another, archive logs on; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2015-07/msg00062.html (18,886 bytes)

Current List: 1 - 8
Page: [1]