Using oracle_test as an example, here is list of all the PV’s (first column) with associated VG (third column): If Linux doesn’t work that way (ie, if you have to add another VMDK in order to expand a disk) might need to re-evaluate the setup. I’m not sure how Linux handles it, but it would be nice if it was the same way: ie, when a disk needs to be increased, we could just increase the VMDK in vSphere and then increase the disk/volume in Linux. And if a VG needs to be increased, we just increase the existing PV that is in it (from the Pure GUI).
Since all PV’s/disks are virtual, there is no sense in having more than one PV per VG. ALL of our VG’s (volume groups) contain only one PV (physical volume), aka disk. I also know you can add additional disks and then add those to the pool but trying to just increase the disk in vCenter and then run a few commands on the Linux server to increase a specific mount that would be housing the database information, if that makes sense.ĪIX uses its version of LVM (logical volume manager).
When doing this with Windows you can rescan and then just expand the disk from within the GUI so I didn't know if System Storage Manager (SSM) had any additional features that would allow us to mirror or use the Oracle Linux environment like we are with AIX from the storage perspective. From what I have used in the past and read on Google searches we would need to alter the partition using fdisk, delete and then recreate with the additional space.
First disk would contain the OS information and partitions while the second disk would have the databases which we would want to setup in a similar fashion. What we were thinking is having two disks (vmdk files) per server. Apparently with AIX on pSeries you can just increase disk space, all storage is using Pure Storage, and then increase the disk space.
One question that came up was about expanding disks. We are looking at migrating our Oracle Databases off AIX (pSeries) and onto Oracle Linux running on VMware.
0 kommentar(er)
