pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedMoving from RHEL6 to RHEL8
3+ messages / 3 participants
[nested] [flat]
* Moving from RHEL6 to RHEL8
@ 2022-03-04 20:12 Ron <ronljohnsonjr@gmail.com>
0 siblings, 2 replies; 3+ messages in thread
From: Ron @ 2022-03-04 20:12 UTC (permalink / raw)
To: pgsql-admin@lists.postgresql.org
Can we "just" move the database LUNs (this is on a SAN, and the servers are
ESX VMs) from the old server to the new server, and then rebuild all indices
with text columns?
--
Angular momentum makes the world go 'round.
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Moving from RHEL6 to RHEL8
@ 2022-03-04 20:28 Victor Yegorov <vyegorov@gmail.com>
parent: Ron <ronljohnsonjr@gmail.com>
1 sibling, 0 replies; 3+ messages in thread
From: Victor Yegorov @ 2022-03-04 20:28 UTC (permalink / raw)
To: Ron <ronljohnsonjr@gmail.com>; +Cc: pgsql-admin@lists.postgresql.org
пт, 4 мар. 2022 г. в 22:12, Ron <ronljohnsonjr@gmail.com>:
> Can we "just" move the database LUNs (this is on a SAN, and the servers
> are
> ESX VMs) from the old server to the new server, and then rebuild all
> indices
> with text columns?
>
Pretty much yes. Though we do it slightly different:
- setup physical replica on the new host
- use amcheck for all btree indexes and add those that needs reindexing to
the list
- add all non-btree indexes where we can find attributes with
pg_collation.collname NOT IN ('C', 'POSIX') to the same list
- run reindexing in parallel via xargs to measure time required (replica
should be re-created after this of course).
--
Victor Yegorov
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Moving from RHEL6 to RHEL8
@ 2022-03-04 21:41 Kishore Dahlstrom <kishore.dahlstrom@gmail.com>
parent: Ron <ronljohnsonjr@gmail.com>
1 sibling, 0 replies; 3+ messages in thread
From: Kishore Dahlstrom @ 2022-03-04 21:41 UTC (permalink / raw)
To: Ron <ronljohnsonjr@gmail.com>; +Cc: pgsql-admin@lists.postgresql.org
I was a storage admin for 12 years. First I would recommend backing your
data on the source volume.
I have migrated data both by replication and by actually swinging the SAN
volumes from one host to another. The process for Windows and Linux
environments is different. I am sure there is a lot of Youtube video or
article written on this subject matter.
The windows environment running SQL server was easy to swing the volume
from the older OS to the new OS.
Linux environment was a little bit more challenging, but it can be done.
If it's VM, you should be able to import the volume via Vsphere, and then
attach the volume to the new Linux VM. Once attached you can run lsblk,
lvscan, or fdisk command to view the attached volume. You should be able
to work with the device and mount the file system.
Sorry, it's been a while but I know I have moved SAN volumes in Linux.
Hope this helps.
Kishore
infinitespices.com
On Fri, Mar 4, 2022 at 12:12 PM Ron <ronljohnsonjr@gmail.com> wrote:
>
> Can we "just" move the database LUNs (this is on a SAN, and the servers
> are
> ESX VMs) from the old server to the new server, and then rebuild all
> indices
> with text columns?
>
> --
> Angular momentum makes the world go 'round.
>
>
>
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2022-03-04 21:41 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2022-03-04 20:12 Moving from RHEL6 to RHEL8 Ron <ronljohnsonjr@gmail.com>
2022-03-04 20:28 ` Victor Yegorov <vyegorov@gmail.com>
2022-03-04 21:41 ` Kishore Dahlstrom <kishore.dahlstrom@gmail.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox